Table Of Contents
Bidirectional Forwarding Detection Commands on Cisco IOS XR Software
address-family ipv4 unicast (BFD)
bfd
bfd fast-detect
bfd minimum-interval
bfd multiplier
clear bfd counters
echo disable
interface (BFD)
show bfd
show bfd client
show bfd counters
show bfd mib session
show bfd session
Bidirectional Forwarding Detection Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor Bidirectional Forwarding Detection (BFD).
address-family ipv4 unicast (BFD)
To enable Bidirectional Forwarding Detection (BFD) fast-detection on a specific IPV4 unicast destination address prefix and on the forwarding next-hop address, use the address-family ipv4 unicast command in static route configuration mode. To return the router to the default setting, use the no form of this command.
address-family ipv4 unicast address nexthop bfd fast-detect [minimum interval interval]
[multiplier multiplier]
no address-family ipv4 unicast address nexthop bfd fast-detect [minimum interval interval]
[multiplier multiplier]
Syntax Description
address
|
Specifies the IPv4 unicast destination address and prefix on which to enable BFD fast-detection.
|
nexthop
|
Specifies the next-hop address on which to enable BFD fast-detection.
|
bfd fast-detect
|
Enables BFD fast-detection on the specified IPV4 unicast destination address prefix and on the forwarding next-hop address.
|
minimum interval interval
|
(Optional) Ensures that the next hop is assigned with the same hello interval. Replace interval with a number that specifies the interval in milliseconds. Range is from 10 through 10000.
|
multiplier multiplier
|
(Optional) Ensures that the next hop is assigned with the same detect multiplier. Replace multiplier with a number that specifies the detect multiplier. Range is from 1 through 10.
|
Defaults
interval: 100
multiplier: 3
Command Modes
Static route configuration mode
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 Carrier Routing System.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
No modification.
|
.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If the multiplier is changed using the bfd multiplier command, the new parameter is used to update all existing BFD sessions for the protocol (BGP, IS-IS, MPLS-TE, or OSPF).
Task ID
Task ID
|
Operations
|
static
|
read, write
|
Examples
The following example shows how to enable BFD on a static route. In this example, BFD sessions are established with the next-hop 3.3.3.3 when it becomes reachable.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# router static
RP/0/RP0/CPU0:router (config-static)# address-family ipv4 unicast 2.2.2.0/24 3.3.3.3 bfd
fast-detection
Related Commands
Command
|
Description
|
bfd fast-detect
|
Enables BFD for communication failure detection.
|
show bfd
|
Displays BFD information.
|
bfd
To enter Bidirectional Forwarding Detection (BFD) configuration mode, use the bfd command in global configuration mode. To exit BFD configuration mode and return to the global configuration mode, use the no form of this command.
bfd
no bfd
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 3.4.0
|
This command was introduced on the Cisco CRS-1 router and Cisco XR 12000 Series Router.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When you issue the bfd command in global configuration mode, the CLI prompt changes to "config-bfd," indicating that you have entered BFD configuration mode. In the following sample output, the question mark (?) online help function displays all the commands available under BFD configuration mode:
RP/0/RP0/CPU0:router(config)# bfd
RP/0/RP0/CPU0:router(config-bfd)#?
commit Commit the configuration changes to running
describe Describe a command without taking real actions
echo Configure BFD echo parameters
exit Exit from this submode
interface Configure BFD on an interface
no Negate a command or set its defaults
root Exit to the global configuration mode
show Show contents of configuration
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
ospf
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
Examples
The following example shows how to enter BFD configuration mode:
RP/0/RP0/CPU0:router # configure
RP/0/RP0/CPU0:router(config)# bfd
RP/0/RP0/CPU0:router(config-bfd)#
Related Commands
Command
|
Description
|
echo disable
|
Disables echo mode on an individual interface or on the entire router.
|
interface (BFD)
|
Enters BFD interface configuration mode.
|
show bfd
|
Displays BFD information.
|
bfd fast-detect
To enable Bidirectional Forwarding Detection (BFD) to detect failures in the path between adjacent forwarding engines, use the bfd fast-detect command in the appropriate configuration mode. To return the software to the default state in which BFD is not enabled, use the no form of this command.
bfd fast-detect [disable | ipv4]
no bfd fast-detect
Syntax Description
disable
|
Disables the detection of failures in the path between adjacent forwarding engines for a specified entity, such as a BGP neighbor or OSPF interface.
Note The disable keyword is available in the following modes only: BGP configuration, OSPF area configuration, OSPF area interface configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
|
ipv4
|
Enables Intermediate System-to-Intermediate System (IS-IS) BFD detection of failures in the path between adjacent forwarding engines.
Note The ipv4 keyword is available in IS-IS router configuration mode only.
|
Defaults
BFD detection of failures in the path between adjacent forwarding engines is disabled.
Command Modes
BGP router configuration mode
Neighbor configuration
Session group configuration
Neighbor group configuration
IS-IS router configuration mode
Interface configuration
MPLS TE configuration mode
Interface configuration
OSPF router configuration mode
Router configuration
Area configuration
Area interface configuration
OSPFv3 router configuration mode
Router configuration
Area configuration
Area interface configuration
Router PIM configuration mode
Interface configuration
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
The bfd fast-detect command was supported in router PIM interface configuration mode.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
The bfd fast-detect command was supported on the Cisco CRS-1 router in the following modes: OSPFv3 router configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Note
BFD is supported on IPv4 directly connected external BGP peers.
Use the bfd fast-detect command to provide protocol- and media-independent, short-duration failure detection of the path between adjacent forwarding engines, including the interfaces and data links.
BFD must be configured on directly connected neighbors for a BFD session to be established between the neighbors.
When MPLS-TE tunnels are protected by backup tunnels, BFD failure triggers fast reroute on affected tunnels.
In OSPF and OSPFv3 environments, the setting of the bfd fast-detect command is inherited from the highest-level configuration mode in which the command was configured. From the lowest to the highest configuration modes, the inheritance rules are as follows:
•
If you enable BFD in area interface configuration mode, it is enabled on the specified interface only.
•
If you enable BFD in area configuration mode, it is enabled on all interfaces in the specified area.
•
If you enable BFD in router configuration mode, it is enabled on all areas and all associated interfaces in the specified routing process.
The disable keyword is available in the following modes: BGP configuration, OSPF area configuration, OSPF area interface configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration. In OSPF and OSPFv3 environments, the disable option enables you to override the inheritance rules described previously. For example, if you enable BFD in an OSPF area, BFD is enabled on all interfaces in that area. If you do not want BFD running on one of the interfaces in that area, you must specify the bfd fast-detect disable command for that interface only.
To disable BFD or return the software to the default state in which BFD is not enabled in IS-IS router configuration mode and MPLS-TE configuration mode, you must enter the no bfd fast-detect command.
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
ospf
|
read, write
|
multicast
|
read, write
|
Examples
The following example shows how to configure BFD on a BGP router:
RP/0/RP0/CPU0:router # configure
RP/0/RP0/CPU0:router(config)# router bgp 65000
RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.70.24
RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2
RP/0/RP0/CPU0:router(config-bgp-nbr)# bfd fast-detect
The following example shows the configuration of an OSPFv3 routing process named san_jose. The example shows two areas, each of which includes Gigabit Ethernet interfaces. In area 0, BFD is enabled at the area level, which means that by virtue of the inheritance rules, BFD is enabled on all interfaces within the area except those on which BFD is explicitly disabled. Given this rule, BFD is enabled on Gigabit Ethernet interfaces 1/0/0/0 and 2/0/0/0 and is disabled on interface 3/0/0/0.
In area 1, BFD is enabled on Gigabit Ethernet interface 5/0/0/0 only. Because BFD is not enabled at the area level nor explicitly enabled on interface 4/0/0/0, it is disabled on this interface.
Related Commands
bfd minimum-interval
To set the Bidirectional Forwarding Detection (BFD) hello interval, use the bfd minimum-interval command in the appropriate configuration mode. To return the router to the default setting, use the no form of this command.
bfd minimum-interval milliseconds
no bfd minimum-interval [milliseconds]
Syntax Description
milliseconds
|
Interval between sending BFD hello packets to the neighbor. The ranges are as follows:
• On the Cisco CRS-1 router
– BGP—15 to 30000 milliseconds.
– IS-IS—15 to 30000 milliseconds.
– MPLS-TE—15 to 200 milliseconds.
– OSPF and OSPFv3—15 to 30000 milliseconds.
– PIM—15 to 30000 milliseconds.
• On the Cisco XR 12000 Series Router
– BGP—15 to 30000 milliseconds
– IS-IS—15 to 30000 milliseconds.
– MPLS-TE—50 to 200 milliseconds.
– OSPF—15 to 30000 milliseconds.
– PIM—15 to 30000 milliseconds.
|
Defaults
BGP interval: 333 milliseconds
IS-IS interval on the Cisco CRS-1 router: 150 milliseconds
IS-IS interval on the Cisco XR 12000 Series Router: 250 milliseconds
OSPF and OSPFv3 interval: 150 milliseconds
MPLS-TE interval on the Cisco CRS-1 router: 15 milliseconds
MPLS-TE interval on the Cisco XR 12000 Series Router: 50 milliseconds
PIM interval: 150 milliseconds
Command Modes
BGP configuration mode
Router configuration
IS-IS configuration mode
Interface configuration
MPLS-TE configuration mode
MPLS TE configuration
OSPF router configuration mode
Router configuration
Area configuration
Area interface configuration
OSPFv3 router configuration mode
Router configuration
Area configuration
Area interface configuration
Router PIM configuration mode
Interface configuration
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
The bfd minimum-interval command was supported in router PIM interface configuration mode.
|
Release 3.5.0
|
modification
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
The bfd minimum-interval command was supported on the Cisco CRS-1 router in the following modes: OSPFv3 router configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
In OSPF and OSPFv3 environments, the setting of the bfd minimum-interval command is inherited from the highest-level configuration mode in which the command was configured. From the lowest to the highest configuration modes, the inheritance rules are as follows:
•
If you configure the minimum interval in area interface configuration mode, the updated interval affects the BFD sessions on the specified interface only.
•
If you configure the minimum interval in area configuration mode, the updated interval affects the BFD sessions on all interfaces in the specified area.
•
If you configure the minimum interval in router configuration mode, the updated interval affects the BFD sessions in all areas and all associated interfaces in the specified routing process.
If desired, you can override these inheritance rules by explicitly configuring the bfd minimum-interval command for a specific area interface or area.
Keep the following router-specific rules in mind when configuring the minimum BFD interval:
•
When asynchronous mode is available on the Cisco CRS-1 router, the minimum interval must be greater than or equal to 15 milliseconds for up to 100 sessions on the line card. If you are running the maximum of 1024 sessions, the failure detection interval must be greater than or equal to 150 milliseconds.
•
When asynchronous mode is available on the Cisco XR 12000 Series Router, the minimum interval must be greater than or equal to 250 milliseconds, with a multiplier of 3 for up to 100 sessions per line card
•
When echo mode is available on the Cisco CRS-1 router, the minimum interval must be greater than or equal to 15 milliseconds for up to 100 sessions on the line card. If you are running the maximum of 1024 sessions, the failure detection interval must be less than or equal to 150 milliseconds.
•
When echo mode is available on the Cisco XR 12000 Series Router, the minimum interval must be 50 milliseconds with a multiplier of 3.
Note
When multiple applications share the same BFD session, the application with the most aggressive timer wins locally. Then, the result is negotiated with the peer router.
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
ospf
|
read, write
|
multicast
|
read, write
|
Examples
The following example shows how to set the BFD minimum interval for a BGP routing process:
RP/0/RP0/CPU0:router(config)# router bgp 6500
RP/0/RP0/CPU0:router(config-bgp)# bfd minimum-interval 275
The following example shows the configuration of an OSPFv3 routing process named san_jose. The example shows two areas, each of which includes Gigabit Ethernet interfaces. In area 0, the minimum interval is set to 200 at the area level, which means that by virtue of the inheritance rules, the same value is set on all interfaces within the area except those on which a different value is explicitly configured. Given this rule, Gigabit Ethernet interface 1/0/0/0 uses the interval of 200, which is inherited from the area, while interface 2/0/0/0 uses the explicitly configured value of 300.
In area 1, the minimum interval is not configured at the area or interface levels, which means that interfaces 3/0/0/0 and 4/0/0/0 use the default interval of 150.
Related Commands
bfd multiplier
To set the Bidirectional Forwarding Detection (BFD) multiplier, use the bfd multiplier command in the appropriate configuration mode. To return the router to the default setting, use the no form of this command.
bfd multiplier multiplier
no bfd multiplier [multiplier]
Syntax Description
multiplier
|
Number of times a packet is missed before BFD declares the neighbor down. On the Cisco CRS-1 router, the ranges are as follows:
• BGP—2 to 16
• IS-IS—2 to 50
• MPLS-TE—2 to 10
• OSPF and OSPFv3—2 to 50
• PIM—2 to 50
One the Cisco XR 12000 Series Router, the ranges are as follows:
• BGP—2 to 16
• IS-IS—2 to 50
• MPLS-TE—2 to 10
• OSPF—2 to 50
• PIM—2 to 50
|
Defaults
multiplier: 3
Command Modes
BGP configuration mode
Router configuration
IS-IS configuration mode
Interface configuration
MPLS-TE configuration mode
MPLS-TE configuration
OSPF router configuration mode
Router configuration
Area configuration
Area interface configuration
OSPFv3 router configuration mode
Router configuration
Area configuration
Area interface configuration
Router PIM configuration mode
Interface configuration
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
The bfd multiplier command was supported in router PIM interface configuration mode.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
The bfd multiplier command was supported on the Cisco CRS-1 router in the following modes: OSPFv3 router configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
|
.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
In OSPF and OSPFv3 environments, the setting of the bfd multiplier command is inherited from the highest-level configuration mode in which the command was configured. From the lowest to the highest configuration modes, the inheritance rules are as follows:
•
If you configure a multiplier in area interface configuration mode, the updated multiplier affects the BFD sessions on the specified interface only.
•
If you configure a multiplier in area configuration mode, the updated multiplier affects the BFD sessions on all interfaces in the specified area.
•
If you configure a multiplier in router configuration mode, the updated multiplier affects the BFD sessions in all areas and all associated interfaces in the specified routing process.
If desired, you can override these inheritance rules by explicitly configuring the bfd multiplier command for a specific area interface or area.
If the multiplier is changed using the bfd multiplier command, the new value is used to update all existing BFD sessions for the protocol (BGP, IS-IS, MPLS-TE, OSPF, or OSPFv3).
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
ospf
|
read, write
|
multicast
|
read, write
|
Examples
The following example shows how to set the BFD multiplier in a BGP routing process:
RP/0/RP0/CPU0:router(config)# router bgp 65000
RP/0/RP0/CPU0:router(config-bgp)# bfd multiplier 2
The following example shows the configuration of an OSPFv3 routing process named san_jose. The example shows two areas, each of which includes Gigabit Ethernet interfaces. In area 0, the multiplier is set to 5 at the area level, which means that by virtue of the inheritance rules, the same value is set on all interfaces within the area except those on which a different value is explicitly configured. Given this rule, Gigabit Ethernet interface 1/0/0/0 uses a multiplier of 5, which is inherited from the area, while interface 2/0/0/0 uses the explicitly configured multiplier of 2.
In area 1, a multiplier is not configured at the area or interface levels, which means that interfaces 3/0/0/0 and 4/0/0/0 use the default value of 3.
Related Commands
clear bfd counters
To clear Bidirectional Forwarding Detection (BFD) counters, use the clear bfd counters command in EXEC mode.
clear bfd counters [ipv4 | ipv6 | all] [packet] [timing] [interface type interface-path-id] location
node-id
Syntax Description
ipv4
|
(Optional) Clears BFD over IPv4 information only.
|
ipv6
|
(Optional) Clears BFD over IPv6 information only.
|
all
|
(Optional) Clears both BFD over IPv4 and BFD over IPv6 information.
|
packet
|
(Optional) Specifies that packet counters are cleared.
|
timing
|
(Optional) Specifies that timing counters are cleared.
|
interface
|
(Optional) Specifies the interface from which the BFD packet counters are cleared.
|
type
|
Specifies the interface type. For more information, use the question mark (?) online help function.
|
interface-path-id
|
Physical interface or virtual interface.
Note Use the show interfaces command to see a list of all interfaces currently configured on the router.
For more information about the syntax for the router, use the question mark (?) online help function.
|
location node-id
|
Clears BFD counters from the specified location. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or IPv6.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
The ipv4 | ipv6 | all keywords were added.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
For the interface-path-id argument, use the following guidelines:
•
If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
–
rack: Chassis number of the rack.
–
slot: Physical slot number of the line card.
–
module: Module number. A physical layer interface module (PLIM) is always 0.
–
port: Physical port number of the interface.
•
If specifying a virtual interface, the number range varies, depending on interface type.
Both IPv4 and IPv6 BFD sessions can run simultaneously on the same line card.
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
ospf
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
Examples
The following example shows how to clear the BFD IPv6 packet counters on a POS interface:
RP/0/RP0/CPU0:router# clear bfd counters packet ipv6 interface POS 0/1/0/0 location
0/1/cpu0
The following example shows how to clear the BFD IPv6 timing counters:
RP/0/RP0/CPU0:router# clear bfd counters ipv6 timing location 0/5/cpu0
Related Commands
echo disable
To disable echo mode on a router or on an individual interface or bundle, use the echo disable command in Bidirectional Forwarding Detection (BFD) configuration mode. To return the router to the default configuration where echo mode is enabled, use the no form of this command.
echo disable
no echo disable
Syntax Description
This command has no arguments or keywords.
Defaults
.No default behavior or values
Command Modes
BFD configuration
BFD interface configuration
Command History
Release
|
Modification
|
Release 3.4.0
|
This command was introduced on the Cisco CRS-1 router and Cisco XR 12000 Series Router.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
If you are using BFD with Unicast Reverse Path Forwarding (uRPF), you need to use the echo disable command to disable echo mode; otherwise, echo packets are rejected.
Note
To enable or disable IPv4 uRPF checking on an IPv4 interface, use the [no] ipv4 verify unicast source reachable-via command in interface configuration mode. To enable or disable loose IPv6 uRPF checking on an IPv6 interface, use the [no] ipv6 verify unicast source reachable-via any command in interface configuration mode.
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
ospf
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
Examples
The following example shows how to disable echo mode on a router:
RP/0/RP0/CPU0:router # configure
RP/0/RP0/CPU0:router(config)# bfd
RP/0/RP0/CPU0:router(config-bfd)# echo disable
The following example shows how to disable echo mode on an individual interface:
RP/0/RP0/CPU0:router # configure
RP/0/RP0/CPU0:router(config)# bfd
RP/0/RP0/CPU0:router(config-bfd)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-bfd-if)# echo disable
Related Commands
Command
|
Description
|
bfd
|
Enters BFD configuration mode.
|
interface (BFD)
|
Enters BFD interface configuration mode.
|
ipv4 verify unicast source reachable-via
|
Enables and disables IPv4 uRPF checking on an IPv4 interface.
|
ipv6 verify unicast source reachable-via any
|
Enables and disables loose IPv6 uRPF checking on an IPv6 interface.
|
show bfd
|
Displays BFD information.
|
interface (BFD)
To enter Bidirectional Forwarding Detection (BFD) interface configuration mode, where you can disable echo mode on an interface, use the interface command in BFD configuration mode. To return to BFD configuration mode, use the no form of this command.
interface type interface-path-id
no interface type interface-path-id
Syntax Description
type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-path-id
|
Physical interface or virtual interface.
Note Use the show interfaces command to see a list of all interfaces currently configured on the router.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
.No default behavior or values
Command Modes
BFD configuration
Command History
Release
|
Modification
|
Release 3.4.0
|
This command was introduced on the Cisco CRS-1 router and Cisco XR 12000 Series Router.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
For the interface-path-id argument, use the following guidelines:
•
If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
–
rack: Chassis number of the rack.
–
slot: Physical slot number of the line card.
–
module: Module number. A physical layer interface module (PLIM) is always 0.
–
port: Physical port number of the interface.
•
If specifying a virtual interface, the number range varies, depending on interface type.
If you are using BFD with Unicast Reverse Path Forwarding (uRPF) on a particular interface, then you need to use the echo disable command in BFD interface configuration mode to disable echo mode on that interface; otherwise, echo packets are rejected by the interface.
Note
To enable or disable IPv4 uRPF checking on an IPv4 interface, use the [no] ipv4 verify unicast source reachable-via command in interface configuration mode. To enable or disable loose IPv6 uRPF checking on an IPv6 interface, use the [no] ipv6 verify unicast source reachable-via any command in interface configuration mode.
Task ID
Task ID
|
Operations
|
bgp
|
read, write
|
ospf
|
read, write
|
isis
|
read, write
|
mpls-te
|
read, write
|
Examples
The following example shows how to enter BFD interface configuration mode for a Packet-over-SONET/SDH (POS) interface:
RP/0/RP0/CPU0:router # configure
RP/0/RP0/CPU0:router(config)# bfd
RP/0/RP0/CPU0:router(config-bfd)# interface pos 0/1/0/0
RP/0/RP0/CPU0:router(config-bfd-if)#
Related Commands
Command
|
Description
|
bfd
|
Enters BFD configuration mode.
|
echo disable
|
Disables echo mode on an individual interface or on the entire router.
|
ipv4 verify unicast source reachable-via
|
Enables and disables IPv4 uRPF checking on an IPv4 interface.
|
ipv6 verify unicast source reachable-via any
|
Enables and disables loose IPv6 uRPF checking on an IPv6 interface.
|
show bfd
|
Displays BFD information.
|
show bfd
To display Bidirectional Forwarding Detection (BFD) information for a specific location, use the show bfd command in EXEC mode.
show bfd [ipv4 | ipv6 | all] [location node-id]
Syntax Description
ipv4
|
(Optional) Displays BFD over IPv4 information only.
|
ipv6
|
(Optional) Displays BFD over IPv6 information only.
|
all
|
(Optional) Displays both BFD over IPv4 and BFD over IPv6 information.
|
location node-id
|
Displays BFD information for the specified location. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or IPv6.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
Support for IPv6 was added on the Cisco CRS-1 router and Cisco XR 12000 Series Router.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
bgp
|
read
|
ospf
|
read
|
isis
|
read
|
mpls-te
|
read
|
Examples
The following example shows the output from the show bfd command:
RP/0/RP0/CPU0:router# show bfd
IPV4 Sessions Up: 0, Down: 0, Total: 0
The following example shows the output from the show bfd all command:
RP/0/RP0/CPU0:router# show bfd all
IIPV4 Sessions Up: 0, Down: 1, Standby: 0, Total: 1
The following example shows the output from the show bfd ipv4 command:
RP/0/RP0/CPU0:router# show bfd ipv4
IPV4 Sessions Up: 0, Down: 0, Total: 0
The following example shows the output from the show bfd ipv6 command:
RP/0/RP0/CPU0:router# show bfd ipv6
IPV4 Sessions Up: 0, Down: 0, Total: 0
The following example shows the output from the show bfd ipv4 location command:
RP/0/RP0/CPU0:router# show bfd ipv4 location 0/3/cpu0
IPV4 Sessions Up: 0, Down: 1, Standby: 0, Total: 1
Related Commands
show bfd client
To display Bidirectional Forwarding Detection (BFD) client information, use the show bfd client command in EXEC mode.
show bfd client [detail]
Syntax Description
detail
|
(Optional) Specifies detailed client information including number of sessions and client reconnects.
|
Defaults
Enter the show bfd client command without specifying the detail keyword to display summarized BFD client information.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
No modification.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Task ID
|
Operations
|
bgp
|
read
|
ospf
|
read
|
isis
|
read
|
mpls-te
|
read
|
Examples
The following example shows the output from the show bfd client command:
RP/0/RP0/CPU0:router# show bfd client
--------------- ---------- --------------
Table 13 describes the significant fields shown in the display.
Table 13 show bfd client Field Descriptions
Field
|
Description
|
Name
|
Name of the BFD client.
|
Node
|
Location of the BFD client.
|
Num sessions
|
Number of active sessions for the BFD client.
|
Related Commands
show bfd counters
To display Bidirectional Forwarding Detection (BFD) counter information, use the show bfd counters command in EXEC mode.
show bfd counters [ipv4 | ipv6 | all] packet [interface type interface-path-id] location node-id
Syntax Description
ipv4
|
(Optional) Displays BFD over IPv4 information only.
|
ipv6
|
(Optional) Displays BFD over IPv6 information only.
|
all
|
(Optional) Displays both BFD over IPv4 and BFD over IPv6 information.
|
packet
|
Specifies that packet counters are displayed.
|
interface
|
(Optional) Specifies the interface for which to show counters.
|
type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-path-id
|
Physical interface or virtual interface.
Note Use the show interfaces command to see a list of all interfaces currently configured on the router.
For more information about the syntax for the router, use the question mark (?) online help function.
|
location node-id
|
Displays BFD counters from the specified location. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or IPv6.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first support the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
The ipv4 | ipv6 | all keywords were added.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
For the interface-path-id argument, use the following guidelines:
•
If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
–
rack: Chassis number of the rack.
–
slot: Physical slot number of the line card.
–
module: Module number. A physical layer interface module (PLIM) is always 0.
–
port: Physical port number of the interface.
•
If specifying a virtual interface, the number range varies, depending on interface type.
Task ID
Task ID
|
Operations
|
bgp
|
read
|
ospf
|
read
|
isis
|
read
|
mpls-te
|
read
|
Examples
The following example shows the output from the show bfd counters packet command for both IPv4 and IPv6:
RP/0/RP0/CPU0:router# show bfd counters packet all interface POS 0/1/0/0 location 0/1/cpu0
Mon Nov 5 08:49:51.950 UTC
POS 0/1/0/0 Recv Xmit Recv Xmit
Async: 520 515 Echo: 9400 9400
POS 0/1/0/0 Recv Xmit Recv Xmit
Table 14 describes the significant fields shown in the display.
Table 14 show bfd counters packet Field Descriptions
Field
|
Description
|
Async
|
Number of asynchronous mode (control) packets that were received or transmitted on the specified interface.
|
Echo
|
Number of echo packets that were received or transmitted on the specified interface.
|
Related Commands
show bfd mib session
To display IPv4 and IPv6 Bidirectional Forwarding Detection (BFD) MIB session information, use the show bfd mib session command in EXEC mode.
show bfd mib session [location node-id]
Syntax Description
location node-id
|
(Optional) Displays all IPv4 and IPv6 BFD MIB session information stored on the specified node. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
When node-id is not specified, information for all IPv4 and IPv6 BFD MIB sessions, stored on the route processor node, is displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.8.0
|
This command was introduced on the Cisco CRS-1 router and Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When node-id is not specified, information for all IPv4 and IPv6 BFD MIB sessions, stored on the route processor node, is displayed, and this information is populated and updated only after SNMP operations for those BFD MIB sessions are performed.
When node-id is specified, information for all IPv4 and IPv6 BFD MIB sessions, stored on the specified node (linecard), is displayed, and this information is updated automatically without SNMP operations being performed.
Task ID
Task ID
|
Operations
|
bgp
|
read
|
ospf
|
read
|
isis
|
read
|
mpls-te
|
read
|
Examples
The following example displays all IPv4 and IPv6 BFD MIB session information stored on the RP node:
RP/0/RP0/CPU0:router# show bfd mib session
Tue Sep 9 07:49:30.828 PST DST
Local Discr: 327681(0x50001), Remote Discr: 0(0x0)
BFD session: GigabitEthernet0_1_5_2(0x11800c0), 10.27.4.7
Current State: ADMIN DOWN, Number of Times UP: 0
Running Version: 0, Last Down Diag: None
Last Down Time (s.ns): 0.0
Desired Min TX Interval: 0
Required Min RX Interval: 0
Required Min RX Echo Interval: 0
Last Time Cached: Not yet cached
The following example displays all IPv4 and IPv6 BFD MIB session information stored on 0/1/CPU0:
RP/0/RP0/CPU0:router# show bfd mib session location 0/1/CPU0
Tue Sep 9 07:44:49.190 PST DST
Local Discr: 327681(0x50001), Remote Discr: 0(0x0)
BFD session: GigabitEthernet0_1_5_2(0x11800c0), 10.27.4.7
Last Down Time (s.ns): 0.0
Packets in/out: 0/1140134
Table 15 describes the significant fields shown in the display.
Table 15 show bfd mib Field Descriptions
Field
|
Description
|
date and timestamp
|
Date and time stamp during which a snapshot of the BFD MIB session information is taken.
|
Local Discr
|
Local discriminator (in decimal and hexadecimal) that uniquely identifies the BFD MIB session.
|
Remote Discr
|
Session discriminator (in decimal and hexadecimal) that was chosen by the remote system for the BFD MIB session.
|
BFD session
|
Index of interface upon which the BFD MIB session is running. Also, neighboring IP address that is monitored with the BFD MIB session.
|
Current State
|
Current state of the BFD MIB session.
|
Number of Times UP
|
Number of times the BFD MIB session has gone into the up state since the router was last rebooted.
|
Running Version
|
BFD protocol version number in which the BFD MIB session is running.
|
Last Down Diag
|
Diagnostic value associated with the last time the BFD MIB session went down.
|
Last Up Time (s.ns)
|
Value of sysUpTime, in seconds.nanoseconds, during which the BFD MIB session last came up. If such an event does not exist, a zero is displayed.
|
Last Down Time (s.ns)
|
Value of sysUpTime, in seconds.nanoseconds, during which communication was last lost with the neighbor. If such an event does not exist, a zero is displayed.
|
Detection Multiplier
|
Failure detection multiplier.
|
Desired Min TX Interval
|
Minimum interval, in microseconds, preferred by the local system when transmitting BFD control packets.
|
Required Min RX Interval
|
Minimum interval, in microseconds, that the local system supports between received BFD control packets.
|
Required Min RX Echo Interval
|
Minimum interval, in microseconds, that the local system supports between received BFD echo packets.
|
Packets in/out
|
Total number of BFD messages received and transmitted for the BFD MIB session.
|
Current Trap Bitmap
|
Bits that control the trap for the BFD MIB session. A nonzero value indicates that the trap is generated when the next trap event is triggered.
|
Last Time Cached
|
When information for the BFD MIB session was last cached. Typically, the information is cached when SNMP operations for the BFD MIB session are performed.
|
Related Commands
show bfd session
To display Bidirectional Forwarding Detection (BFD) session information, use the show bfd session command in EXEC mode.
show bfd [ipv4 | ipv6 | all] session [interface type interface-path-id [destination ip-address]
[detail]] [location node-id]
Syntax Description
ipv4
|
(Optional) Displays BFD over IPv4 information only.
|
ipv6
|
(Optional) Displays BFD over IPv6 information only.
|
all
|
(Optional) Displays both BFD over IPv4 and BFD over IPv6 information.
|
interface
|
(Optional) Specifies the interface for which to show information.
|
type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-path-id
|
Physical interface or virtual interface.
Note Use the show interfaces command to see a list of all interfaces currently configured on the router.
For more information about the syntax for the router, use the question mark (?) online help function.
|
destination ip-address
|
(Optional) Displays the BFD session destined for the specified IP address.
|
detail
|
(Optional) Displays detailed session information, including statistics and number of state transitions.
|
location node-id
|
(Optional) Displays BFD sessions hosted from the specified location. The node-id argument is entered in the rack/slot/module notation.
|
Defaults
The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or IPv6.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.2
|
This command was introduced on the Cisco CRS-1 router.
|
Release 3.3.0
|
This command was first supported on the Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Release 3.7.0
|
The ipv4 | ipv6 | all keywords were added.
|
Release 3.8.0
|
No modification.
|
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
For the interface-path-id argument, use the following guidelines:
•
If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values is required as part of the notation. An explanation of each component of the naming notation is as follows:
–
rack: Chassis number of the rack.
–
slot: Physical slot number of the line card.
–
module: Module number. A physical layer interface module (PLIM) is always 0.
–
port: Physical port number of the interface.
•
If specifying a virtual interface, the number range varies, depending on interface type.
Task ID
Task ID
|
Operations
|
bgp
|
read
|
ospf
|
read
|
isis
|
read
|
mpls-te
|
read
|
Examples
The following example shows the output from the show bfd session command with the detail keyword and IPv4 as the default:
RP/0/RP0/CPU0:router# show bfd session detail
I/f:TenGigE0/2/0/0.6, Location:0/2/CPU0, dest:10.0.6.2, src:10.0.6.1
State:UP for 0d:0h:3m:4s, number of times UP:1
Version:1, desired tx interval:2 s, required rx interval:2 s
Required echo rx interval:1 ms, multiplier:3, diag:None
My discr:589830, your discr:590028, state UP, D/F/P/C/A:0/0/0/1/0
Version:1, desired tx interval:2 s, required rx interval:2 s
Required echo rx interval:1 ms, multiplier:3, diag:None
My discr:590028, your discr:589830, state UP, D/F/P/C/A:0/0/0/1/0
Local negotiated async tx interval:2 s
Remote negotiated async tx interval:2 s
Desired echo tx interval:250 ms, local negotiated echo tx interval:250 ms
Echo detection time:750 ms(250 ms*3), async detection time:6 s(2 s*3)
Intervals between async packets:
Tx:Number of intervals=100, min=952 ms, max=2001 ms, avg=1835 ms
Last packet transmitted 606 ms ago
Rx:Number of intervals=100, min=1665 ms, max=2001 ms, avg=1828 ms
Last packet received 1302 ms ago
Intervals between echo packets:
Tx:Number of intervals=100, min=250 ms, max=252 ms, avg=250 ms
Last packet transmitted 188 ms ago
Rx:Number of intervals=100, min=250 ms, max=252 ms, avg=250 ms
Last packet received 187 ms ago
Latency of echo packets (time between tx and rx):
Number of packets:100, min=1 ms, max=2 ms, avg=1 ms
Session owner information:
Client Desired interval Multiplier
---------------- -------------------- --------------
The following example shows the output from the show bfd session command with the all keyword, which displays both IPv4 and IPv6 information:
RP/0/RP0/CPU0:router# show bfd all session location 0/1/CPU0
Mon Nov 5 08:51:50.339 UTC
Interface Dest Addr Local det time(int*mult) State
-------------------- --------------- ---------------- ---------------- ---------
PO0/1/0/0 10.0.0.2 300ms(100ms*3) 6s(2s*3) UP
Local det time(int*mult) State
-------------------- ----------------------------------------------
Table 16 describes the significant fields shown in the display.
Table 16 show bfd session detail command Field Descriptions
Field
|
Description
|
I/f
|
Interface type.
|
Location
|
Location of the node that hosts the local endpoint of the connection, in the rack/slot/module notation
|
dest
|
IP address of the destination endpoint.
|
src
|
IP address of the source endpoint.
|
State
|
Current state of the connection, and the number of days, hours, minutes, and seconds that this connection has been active.
|
number of times UP
|
Number of times this connection has been brought up.
|
Received parameters
|
Provides information on the last transmitted control packet for the session:
• Version—Version number of the BFD protocol.
• desired tx interval—Desired transmit interval.
• required rx interval—Required receive interval.
• Required echo rx interval—Required echo receive interval.
• multiplier— Number of times a packets is missed before BFD declares the neighbor down.
• diag—diagnostic code specifying the peer system's reason for the last transition of the session from Up to some other state.
• My discr —unique, nonzero discriminator value generated by the transmitting system, used to demultiplex multiple BFD sessions between the same pair of systems.
• your discr— discriminator received from the corresponding remote system. This field reflects back the received value of My discr, or is zero if that value is unknown.
|
Transmitted parameters
|
Provides information on the last transmitted control packet for the session:
• Version—Version number of the BFD protocol.
• desired tx interval—Desired transmit interval.
• required rx interval—Required receive interval
• Required echo rx interval—Required echo receive interval
• multiplier— Number of times a packets is missed before BFD declares the neighbor down.
• diag—diagnostic code specifying the local system's reason for the last transition of the session from Up to some other state.
• My discr —unique, nonzero discriminator value generated by the transmitting system, used to demultiplex multiple BFD sessions between the same pair of systems.
• your discr— discriminator received from the corresponding remote system. This field reflects back the received value of My discr, or is zero if that value is unknown.
|
Timer Values
|
Provides information on the timer values used by the local and remote ends, as follows:
• Local negotiated async tx interval—interval at which control packets are being transmitted by the local end.
• Remote negotiated async tx interval—interval at which control packets should be transmitted by the remote end.
• Desired echo tx interval—interval at which the local end would like to transmit echo packets.
• local negotiated echo tx interval—interval at which echo packets are being transmitted by the local end.
• Echo detection time—local failure detection time of echo packets. It is the product of the local negotiated echo tx interval and the local multiplier.
• async detection time—local failure detection time of the asynchronous mode (control packets). It is the product of the remote negotiated async tx interval and the remote multiplier.
|
Local Stats
|
Displays the local transmit and receive statistics,
• Intervals between async packets—provides measurements on intervals between control packets (tx and rx):
– Number of intervals—number of sampled intervals between control packets
– min—minimum measured interval between 2 consecutive control packets
– max—maximum measured interval between 2 consecutive control packets
– avg—average measured interval between 2 consecutive control packets
– Last packet received/transmitted—indicates how long ago the last control packet was received/transmitted.
• Intervals between echo packets—provides measurements on intervals between echo packets (tx and rx). The measurements have the same meaning as for async packets.
• Latency of echo packets (time between tx and rx)—provides measurements on latency of echo packets, i.e. the time between tx and rx of echo packets:
– Number of packets—number of sampled echo packets.
– min—minimum measured latency for echo packets.
– max—maximum measured latency of echo packets.
– avg—average measured latency of echo packets.
|
Session owner information
|
Provides the following information about the session owner.
• Client—name of the client application process.
• Desired interval—desired interval provided by the client, in milliseconds.
• Multiplier—multiplier value provided by the client.
|
Related Commands