How to judge a carrier public IP whether can traverse other carrier link in multi-carriers access network

Publication Date:  2012-10-15 Views:  188 Downloads:  0
Issue Description
For customer, to ensure network access of high reliability and link load, the network demand using multiple carriers in extranet access layer will be generally. But this kind of situation, deploy the network equipment, and routing setting is commonly according to carriers network configuration detailed route, return data flow go the nearest link. It is the networking, the client of IP address through the telecommunication link access telecommunication public IP, and data flow back from Unicom link, lead to the network does not pass. This kind of situation, we need through the test to judge whether is the carriers limit problem or other problems.

Alarm Information
none
Handling Process
The above network export equipment using the firewall as an example, if it is router, method is similar, the test specific steps are as follows:
1, confirm the network client can ping firewall telecommunication gateway
2, check the configuration, confirm the network client to firewall ping not be banned.
3, through the client go to the Internet such as www.ip138.com, confirm client export public IP
4, ping pass firewall telecom interface public IP, check the routing export to the extranet client in the firewall, if it is Unicom export, means the Unicom link do not to limit the Telecom IP restrictions. Check Telecom link limit or not like this; Other enter the next step
5, if can't ping pass firewall Telecom interface public IP, add 32 host routes in the firewall, to the client export public IP next hop is Telecom export, and test again, such as ping is normal, then explaining carriers link do have limit.
Root Cause
maybe the configuration problem or the carrier limit problem
Suggestions
In the project can according to the above methods to make flexible test and verification, not only positioning whether is our product problem, but also need to pay attention to the problem is probably caused by the around network environment.

END