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


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


The route-loops occur due to NE40 OSPF importing the invalid static routes

Publication Date:  2012-07-27 Views:  79 Downloads:  0

Issue Description


OSPF work between NE40 and Cxxxxx.The interconnecting network-segment between NE40 and Cxxxxx is,the interface address of Cxxxxx is Cxxxxx, release one OSPF default route.At the OSPF procesion of NE40,import one static route,its nexthop is tracert the packet oscillates between and

Alarm Information


Handling Process

For the limitation of NE40,currently only the single interface vlan forwarding is supported.To solve the problem, we must avoid it via the networking solution.If we configure multiple VLAN-interfaces or underlying layer 2 LSW,make the local VLAN interface contain one physical interface only.

Root Cause

The reason is that the static route is invalid,its nexthop is the address of some layer 3 VLAN interface address on NE40both the physical interface and VLANinterface are UPbut this VLAN interface contains three physical interfaces. If we want to do the routing forwarding via NE40 layer 2 boards, configure the Vlan to the routing mode via "property routing", but under this mode, each VLAN interface can contain one physical interface only. In this network, because we did not configure property routing, this VLAN cannot do the routing forwarding. So the packets accessing can match the default routes on NE40 onlythe packets are forwarded to Cxxxxx while on Cxxxxx,we learn the O_ASE routes of via OSPF, the nexthop of O_ASE is,it backs to NE40, loops form.