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

Eth-Trunk 0 Between the NE80E-1 and NE80E-2 Is Down After the NE80E-1 Is Upgraded

Publication Date:  2012-07-27 Views:  27 Downloads:  0
Issue Description
 Version: V300R006C01B297
Networking description: The NE80E-1 connects to the NE80E-2 directly through Eth-Trunk 0.
Fault symptom:
After the NE80E-1 is upgraded, Eth-Trunk 0 between the NE80E-1 and NE80E-2 is down. 
 
Alarm Information
 Null 
Handling Process
 1. Establish Eth-Trunk 10, and add Eth-Trunk 0 to Eth-Trunk 10. Both Eth-Trunk 10 and Eth-Trunk 0 are Up.
2. Delete the BFD configuration after the interface configuration when the fault occurs is recovered. Eth-Trunk 0 is Up.
3. After comparing the BFD configuration of the NE80E-1 with that of the NE80E-2, you find that the BFD configuration of the NE80E-1 lacks the commit command.
4. Recover the BFD configuration of the NE80E-1 and add the commit command to the configuration. Both the BFD session and Eth-Trunk0 are Up.
5. After querying logs, you will find that the BFD configuration is modified after the session is successful and the commit command is not executed. Instead, the configuration mode and system are exited directly.
BFD configuration of NE80E-1:
#
bfd ne80_to_ne80_1 bind peer-ip default-ip interface GigabitEthernet1/0/23
discriminator local 10
discriminator remote 20
process-interface-status
#
bfd ne80_to_ne80_2 bind peer-ip default-ip interface GigabitEthernet9/0/0
discriminator local 11
discriminator remote 21
process-interface-status
#
BFD configuration of NE80E-2:
#
bfd ne80_to_ne80_1 bind peer-ip default-ip interface GigabitEthernet1/0/23
discriminator local 20
discriminator remote 10
process-interface-status
commit
#
bfd ne80_to_ne80_2 bind peer-ip default-ip interface GigabitEthernet9/0/0
discriminator local 21
discriminator remote 11
process-interface-status
commit

 
Root Cause

 BFD is configured between the NE80E-1 and NE80E-2. The BFD configuration of the NE80E-1 lacks the commit command. The NE80E-1 needs to redeliver the configuration after being upgraded and restarted. If the BFD configuration lacks the commit command, the system cannot send BFD packets and the BFD session is always Down, which results in the Down of Eth-Trunk. The BFD session is Up before the upgrade and down after the upgrade, because the BFD configuration is modified after the session is Up and the commit command is not entered to make the modified configuration take effect. Instead, you directly exit the BFD configuration mode and system. 

Suggestions
 After the BFD configuration is complete and the session is Up, enter the commit command each time the BFD configuration or parameters of the BFD configuration are modified to make the modified configuration take effect. 

END