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>

Reminder

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

upgrade

NE40E Cannot Establish a BGP Peer Relationship with an Alcatel-Lucent Device

Publication Date:  2013-09-03 Views:  52 Downloads:  0
Issue Description
After upgraded from V600R001 to V600R003, the NE40E-X16 cannot establish a BGP peer relationship with an Alcatel-Lucent device. On the dual-plane live network, routes from the NE40E on one plane are reflected by the RR on the other plane to the connected Alcatel-Lucent device without affecting services.

However, the BGP peer relationship fails to be established.
Handling Process
In the lab, perform the ping test between the NE40E and an Alcatel-Lucent device. The problem on the live network is simulated.
1. Configure outbound route filtering (ORF) on the Alcatel-Lucent device according to the configuration on the live network. The BGP peer relationship fails to go Up, which is the same as that on the live network.
2. Disable ORF on the Alcatel-Lucent device. The BGP peer relationship is established.
Capture packets and verify conflicts between the Alcatel-Lucent device and standard protocol. The result is the same as that on the live network.
Root Cause

Difference between the two versions:
The NE40E of versions earlier than V600R003 does not support ORF and cannot identify the ORF type in an Open message. Therefore, the NE40E ignores the Open message and does not parse ORF, and the BGP peer relationship can be established. The NE40E of V600R003 supports ORF and completely analyzes the ORF type in an Open message. The ORF type in the Open message from the Alcatel-Lucent device is different from that defined in RFC 5292, leading to a failure in establishing a BGP peer relationship.

Interoperation between Huawei NE40E and Cisco or Juniper devices:
The NE40E can establish a BGP peer relationship with a Cisco or Juniper device. These devices support the same ORF type.

The BGP ORF function on the Alcatel-Lucent device does not comply with the standard RFC 5292. RFC 5292 defines the ORF type field as 64. The Alcatel-Lucent device sends Open message with the ORF type field of 3, which is different from the standard. When the NE40E parses the Open message from the Alcatel-Lucent device in the way defined in RFC 5292, the NE40E fails to identify the ORF type in the Open message, leading to a failure in establishing a BGP peer relationship
Solution
1. On the Alcatel-Lucent device, disable ORF for devices with which the Alcatel-Lucent device fails to establish BGP peer relationships.
2. The subsequent patches of the NE40E support the non-standard ORF type on the Alcatel-Lucent device. This compatibility allows the BGP peer relationship to be successfully established.

END