No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

Communication Fails Because of Routes with Different Priorities

Publication Date:  2012-07-27  |   Views:  101  |   Downloads:  0  |   Author:  Mao Zhengjun  |   Document ID:  EKB0000302831

Contents

Issue Description

Networking:
Terminal---R2611------------AR46---NMS
The gateway of the terminal is R2611. The gateway of the NMS is AR46.
Phenomenon: The terminal cannot ping through the NMS. The terminal, however, can ping through the IP address of the downstream interface on the R2611 that connects the AR26. The AR46 can ping through the NMS.

Alarm Information

Null

Handling Process

1. It is a route problem of the NMS. Check and find that there is a default route to the AR46 in the routing table of the NMS.
2. It is a route problem of the R2611. Check and find that the static route to the NMS is not configured on the R2611. Add a route to the routing table. The terminal still cannot ping through the NMS. Check the routing table of the R2611 and find that the route to the NMS is a direct route. The outbound interface is another port other than the port configured. Check and find that an IP address is assigned to this port and the IP address belongs to the same network segment as that of the NMS. The port is in the Up state. Thus, a direct route is generated. Because the direct route has the higher priority than the static route, data packets are forwarded to another port.
3. Delete the IP address of this outbound port on the R2611. Then, the problem is solved.

Root Cause

1. It is a route problem.

Suggestions

When the ping fails, you can check whether there are routes with different priorities.