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.


Some Services Were Interrupted After a Physical Interface in an Eth-trunk Between Two NE5000Es on an IP MAN Was Faulty

Publication Date:  2013-10-08 Views:  170 Downloads:  0

Issue Description

Two physical interfaces (g4/0/0 and g5/0/0) were bound to Eth-trunk1 between NE5000E 1 (NE1) and NE5000E 2 (NE2) on an IP MAN. After g5/0/0 on NE2 was down, some services were interrupted, and OSPF and MPLS LDP neighbors were transiently down between the NE5000Es and ME60s.

Handling Process

Cause for interruption of some services:

After g5/0/0 on NE2 was down, NE2 failed to receive OSPF packets, and OSPF neighbors between NE1 and NE2 were down.
RT1 and RT2 controlled network-to-user traffic based on the MED value in BGP routes. Certain traffic from NE1/NE2 to RT1/RT2 need to pass between NE1 and NE2 before arriving at RT1/RT2. When OSPF neighbors were down between NE1 and NE2, IGP routes were re-iterated by IBGP routes for the traffic. Therefore, the traffic was routed to SRs or BRASs connected to the NE5000Es. The SRs and BRASs, on which the route to NE1 and that to NE2 had the same cost value, sent the traffic to NE1/NE2. As a result, a rooting loop occurred between the NE5000Es and SRs/BRASs and the services corresponding to the traffic were interrupted.

Cause for the down state of OSPF and LDP neighbors:

The TTL value of a packet decreased by 1 each time it passes a router. When the TTL value was reduced to 1, NE5000E sent the packet to the CPU of the LPU board. Because protocol packets were sent a dedicated channel, no OSPF packets were lost. Upon receiving OSPF and LDP packets with the TTL value being 1, the LPU board put the packets into an IP_INPUT queue before sending them to processing modules. Query results indicated that the CPUs of LPU 9 and LPU 12 of NE5000E were high. Once the queue was full, protocol packets were discarded and protocol timeout occurred.

Root Cause

A physical interface in Eth-trunk1 was down.


1. Delete Eth-trunk1 and create two OSPF neighbors.

2. Set valid-ttl-hops to 1 for IBGP neighbors, so IBGP neighbors are down upon OSPF down between NE5000Es. In this manner, the routing loop can be prevented.


NE5000E houses 10GE interfaces. When bound to an Eth-trunk, the interfaces do not support auto-negotiation. If one end is down, the other may be up. Eth-trunk is not recommended on such devices.