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

The Association Between a BFD Session and a Static Route Fails Because the Configured BFD Name Is Case-Insensitive

Publication Date:  2013-01-08 Views:  41 Downloads:  0
Issue Description

When a BFD session is associated with a static route on an NE40E running V300R003C02B697, an error message is prompted indicating that the association fails. The configuration is as follows:

1.         The BFD instance is created. The configuration example is as follows.

[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]

2.         The preceding configuration shows that configuring the name of the BFD instance using capital letters "TO-BSC45" succeeds.

When the BFD session is associated with a static route, an error message is prompted indicating that the association fails. The configuration example is as follows.

[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

The on-site Huawei technical support personnel check the BFD configuration and find that the name of the BFD instance is displayed in low-case letters "to-bsc45". However, the name of the BFD instance is configured using capital 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

.....

They check the BFD configuration and find that the commit command is not run and the BFD session is not associated with the interface. That is why BFD fails to take effect and cannot detect an interface Down event.

Root Cause

A BFD instance can be created on an NE40E running a version earlier than V600R003 with the name case-insensitive. If the BFD instance name is configured using capital letters, the system automatically changes its name to low-case letters. In this case, when the BFD session was associated with a static route based on the configured BFD instance with the name displayed in capital letters, the system prompted an error message indicating that the association failed.

Solution

Configure the name of the BFD instance using low-case letters.

END