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

Binding a Static Route to a BFD Session Fails Due to the Case Insensitive BFD Session Name

Publication Date:  2013-09-13 Views:  10 Downloads:  0
Issue Description

On an NE40E V300R003C02B697, binding a static route to a BFD session fails. Specific configurations are as follows:

1. Configuring the name of a BFD session succeeds.

[CE01-NE40E]bfd TO-BSC45 bind peer-ip 10.31.40.132 vpn-instance test interface GigabitEthernet1/0/1.1022 source-ip 10.31.40.130

[CE01-NE40E-bfd-session-to-bsc45]

Uppercase "TO-BSC45" name is successfully configured.

2. Binding a static route to the BFD session fails.

[CE01-NE40E]IP route-static vpn-instance test 10.31.100.1 255.255.255.255 GigabitEthernet 1/0/1.1022 10.31.40.132 track bfd-session TO-BSC45

Error: The specified BFD session does not exist.
Handling Process

1. Check the BFD configurations.
The letters in the BFD session name are changed to lowercase letters.
disp cu  | include bfd

......

bfd to-bsc45 bind peer-ip 10.31.40.132 vpn-instance test interface GigabitEthernet1/0/1.1022 source-ip 10.31.40.130

.....

2. Check new BFD configurations and find that no commit or BFD-port association is configured.
BFD fails to take effect and cannot shut down a port upon detecting a fault.
Root Cause
For NE40E earlier than V600R003, BFD session names are case insensitive, and the uppercase letters are automatically changed to lowercase letters. However, a static route is bound to a BFD session with the uppercase name. Therefore, the binding fails.
Solution
The BFD session name with lowercase letters is configured.

END