“ [My 5th Success Story] Failure of NE40E to Established BGP Peer“

aamallik
aamallik  Diamond  (1)
7 years 4 months ago  View: 1431  Reply: 2
1F

Dear admin,


one day when I  was performing cutover services from NE40EV600R001C00SPC800 equipment to NE40EV600R003C00SPC300 equipment. During the cutover, it was found that newly installed NE40E 

fails to establish BGP peer relationships.


On comparing log information before and after, it was found NE40E fails to establish BGP peer relationships with 16 ALU 7750 devices. When examine the event, we enable the bgp debugging.


After examination of the ORF type and it was concluded that ORF type value of the Open packets received f

rom the ALU devices is not in conformity with the standard of RFC 5292, where the ORF-type sent was 3. When NE40EV600R003C00SPC300 received this, it does not recognize the type and drop the session. After some 

discussion with the expert, it was found that ORF type 3 that ALU implements follows some recommendation i

n the expired old Internet draft, but was never really standardized in the RFC.


The BGP peer relationship becomes normal with 

ALU7750 after applying the patch. And I got this solution from Huawe HEDEX document.


Thanks to HUawei support website



Pema Wangdi
Pema Wangdi  Diamond 
7 years 4 months ago
2F
Thanks great success story .............
sumon_ahsan
sumon_ahsan  Diamond 
7 years 4 months ago
3F
very good work & keep it up...