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>Search

Reminder

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

upgrade

The Association Between One-Arm BFD Echo Sessions and Sub-Interfaces Fails on an NE20E-S V800R008)

Publication Date:  2019-04-24 Views:  110 Downloads:  0

Issue Description

The association between one-arm BFD echo sessions and sub-interfaces fails on an NE20E-S V800R008. The process-interface-status sub-if command fails to be configured.

[~DeviceA] bfd
[*DeviceA-bfd] quit
[*DeviceA] bfd atob bind peer-ip 10.x.x.2 interface gigabitEthernet0/1/0 one-arm-echo
[*DeviceA-bfd-session-atob] discriminator local 1
[*DeviceA-bfd-session-atob] min-echo-rx-interval 100
[*DeviceA-bfd-session-atob]process-interface-status sub-if //This command fails to be configured.

Handling Process

Check the precautions for running the process-interface-status command.

This command applies only to single-hop BFD sessions configured with multicast addresses.

Single-arm BFD echo sessions use unicast addresses. Therefore, this command does not apply to single-arm BFD echo sessions.

Root Cause

This command applies only to single-hop BFD sessions configured with multicast addresses.

For single-arm BFD echo sessions , a unicast address is specified using the peer-ip x.x.x.x command.

 

Solution

Do not associate single-arm BFD echo sessions with sub-interfaces.

Suggestions

In the bfd atob bind peer-ip default-ip interface GigabitEthernet0/1/0 command, peer-ip followed by default-ip indicates the multicast mode.

In the bfd atob bind peer-ip 10.x.x.2 interface gigabitEthernet0/1/0 one-arm-echo command, peer-ip followed by an IP address indicates the unicast mode.

 

END