Table Of Contents

Bidirectional Forwarding Detection Debug Commands on Cisco IOS XR Software

debug bfd backtrace

debug bfd client-api

debug bfd errors

debug bfd filter

debug bfd fsm

debug bfd ipv4

debug bfd lib

debug bfd process

Bidirectional Forwarding Detection Debug Commands on Cisco IOS XR Software

---

This chapter describes the commands used to debug Bidirectional Forwarding Detection (BFD).

debug bfd backtrace

To turn on the backtrace function for bidirectional forwarding, use the debug bfd backtrace command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd backtrace function name prefix [location node-id]

no debug bfd backtrace function name prefix [location node-id]

Syntax Description

function name prefix	Specify a function name prefix to filter the backtrace.
location node-id	(Optional) Specifies debug information for a specified location. The node-id argument is entered in the rack/slot/module notation.

Defaults

When you use the debug bfd backtrace command, all the parallel processes that are impacted by the backtrace activity, are restarted.

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows sample output from a bfd backtrace activity using the debug bfd backtrace command:

RP/0/RP0/CPU0:router# debug bfd backtrace location 0/0/CPU0

RP/0/0/CPU0:Jan 14 02:09:09.763 : nd_

partner[284]: nd_stats_coll_handler: getting stats of type GENERIC for interface

 0x01000080

Related Commands

Command	Description
debug bfd client-api	Specifies debug information for the BFD server API with API clients.
debug bfd fsm	Specifies debug information within the FSM module.
debug bfd ipv4	Specifies debug information for IPv4 sessions.
debug bfd process	Specifies debug information for process and SysDB events.

debug bfd client-api

To debug information for the BFD server application programming interface (API) with API clients, use the debug bfd client-api command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd client-api

no debug bfd client-api

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows sample output with the debug bfd client-api command:

RP/0/RP0/CPU0:router# debug bfd client-api

RP/0/RP0/CPU0:router# bfd[122]: DBG-API[1]: Client registered: 

clinfo=482300cc, client=ospf, jid=362, node=node0_RP1_CPU0, recreate timer=60

Related Commands

Command	Description
debug bfd errors	Specifies debug information for all error conditions.

debug bfd errors

To debug information for all error conditions, use the debug bfd errors command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd errors [client-api] [fsm | ipv4 [packet] | oper | process] [location node-id]

no debug bfd errors [client-api] [fsm | ipv4 [packet] | oper | process] [location node-id]

Syntax Description

client-api	(Optional) Specifies debug information for errors with the BFD server API with clients.
fsm	(Optional) Specifies debug information for errors within the finite state machine (FSM) module.
ipv4 [packet]	(Optional) Specifies debug information for errors in IP Version 4 (IPv4) sessions. Packet is an additional filter for IPv4 packet errors.
oper	(Optional) Specifies debug information for operational errors.
process	(Optional) Specifies debug information for process and system database (SysDB) errors.
location node-id	(Optional) Specifies debug information to enable a specified location (for example, 0/2/CPU0). The node-id argument is entered in the rack/slot/module notation.

Defaults

When you use the debug bfd errors command, the default value is to enable all error debugging for all locations.

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpols-te	read

Examples

The following example shows sample output from a temporary failure during the process restart of the BFD server on the RP with the debug bfd errors command:

RP/0/RP0/CPU0:router# debug bfd errors location 0/0/CPU0

LC/0/0/CPU0:Jun 21 11:42:59 : bfd_agent[105]: ERR-Proc[1]: 

bfd_server_open_handler:1008, Error in ipi bind rc 6 (No such device or

address)

Related Commands

Command	Description
debug bfd client-api	Specifies debug information for the BFD server API with API clients.
debug bfd fsm	Specifies debug information within the FSM module.
debug bfd ipv4	Specifies debug information for IPv4 sessions.
debug bfd process	Specifies debug information for process and SysDB events.

debug bfd filter

To debug information based on the applicable parameters that are filtered, use the debug bfd filter command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd filter {interface type instance | ipv4 ACL name}

no debug bfd filter {interface type instance | ipv4 ACL name}

Syntax Description

interface	(Optional) Limit the output to the specified interface.
type	Interface type. For more information, use the question mark (?) online help function.
instance	Either a physical interface instance or a virtual interface instance as follows: •Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. –rack: Chassis number of the rack. –slot: Physical slot number of the modular services card or line card. –module: Module number. A physical layer interface module (PLIM) is always 0. –port: Physical port number of the interface. Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0. –Virtual interface instance. Number range varies depending on interface type. For more information about the syntax for the router, use the question mark (?) online help function.
ipv4 ACL name	Specifies the debug output that is filtered based on a match for the access list specified by name.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows how to enable debugging information for the POS interface with the debug bfd filter command:

RP/0/RP0/CPU0:router# debug bfd filter interface pos 0/2/0/0

RP/0/RP0/CPU0:router#

Related Commands

Command	Description
debug bfd ipv4	Debugs information for IPv4 sessions.

debug bfd fsm

To debug information within the FSM module, use the debug bfd fsm command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd fsm [location node-id]

no debug bfd fsm [location node-id]

Syntax Description

location node-id

(Optional) Specifies debug information to enable a specified location (for example, 0/2/CPU0). The node-id argument is entered in the rack/slot/module notation.

Defaults

If you do not enable the location filter, the default value is to enable debugging on all locations.

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows sample output with the debug bfd fsm command for a specified location:

RP/0/RP0/CPU0:router# debug bfd fsm location 0/0/CPU0

LC/0/0/CPU0:Jun 21 11:46:42 : bfd_agent[105]: Session [2.2.2.1,2.2.2.2,POS0_0_0_0,65539], 
event Remote state init, state DOWN -> UP

Related Commands

Command	Description
debug bfd client-api	Specifies debug information for the BFD server API with API clients.
debug bfd errors	Specifies debug information for all error conditions.
debug bfd ipv4	Specifies debug information for IPv4 sessions.

debug bfd ipv4

To debug information for IPv4 sessions, use the debug bfd ipv4 command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd ipv4 [packet] [location node-id]

no debug bfd ipv4 [packet] [location node-id]

Syntax Description

packet	(Optional) Specifies debug information for IPv4 packets that displays changes only in packets received and transmitted.
location node-id	(Optional) Specifies debug information to enable a specified location (for example, 0/2/CPU0). The node-id argument is entered in the rack/slot/module notation.

Defaults

If you do not enable the location filter, the default value is to enable debugging on all locations.

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows sample output with the debug bfd ipv4 command for a specified location:

RP/0/RP0/CPU0:router# debug bfd ipv4 packet location 0/0/CPU0

LC/0/0/CPU0:Jun 21 11:47:55 : bfd_agent[105]: Rx IP: src 2.2.2.2, dst 2.2.2.1, plen 24. 
BFD: diag 0, state 3, P/F/C/A/D (0/0/1/0/0), mult 3, len 24, loc/rem discr 65537 65539, tx 
2000000, rx 2000000, rx echo 1000

Related Commands

Command	Description
debug bfd client-api	Specifies debug information for the BFD server API with API clients.
debug bfd errors	Specifies debug information for all error conditions.
debug bfd fsm	Specifies debug information within the FSM module.
debug bfd process	Specifies debug information for process and SysDB events.

debug bfd lib

To debug information for the BFD clients for the client API, use the debug bfd lib command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd lib [errors | jid jobid] [location node-id]

no debug bfd lib [errors | jid jobid] [location node-id]

Syntax Description

errors	(Optional) Specifies debug information for errors only for the BFD clients for the client API.
jid jobid	(Optional) Specifies the filter to display debugging only for the client process specified by jobid.
location node-id	(Optional) Specifies debug information to enable a specified location (for example, 0/2/CPU0). The node-id argument is entered in the rack/slot/module notation.

Defaults

The default value is to enable debugging for all clients.

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows sample output with the debug bfd lib command for a specified location:

RP/0/RP0/CPU0:router# debug bfd lib location 0/0/CPU0

RP/0/RP0/CPU0:router# ospf[362]: DBG-Lib: bfd_api_bind:671, Client successfully registered

Related Commands

Command	Description
debug bfd client-api	Specifies debug information for the BFD server API with API clients.
debug bfd errors	Specifies debug information for all error conditions.

debug bfd process

To debug information for process and SysDB events, use the debug bfd process command in EXEC mode. To disable debugging, use the no form of this command.

debug bfd process [location node-id]

no debug bfd process [location node-id]

Syntax Description

location node-id

(Optional) Specifies debug information to enable a specified location (for example, 0/2/CPU0). The node-id argument is entered in the rack/slot/module notation.

Defaults

If you do not enable the location filter, the default value is to enable debugging on all locations.

Command Modes

EXEC

Command History

Release	Modification
Release 3.2	This command was introduced on the Cisco CRS-1.
Release 3.3.0	No modification.
Release 3.4.0	No modification.
Release 3.5.0	No modification.
Release 3.6.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID	Operations
bgp	read
ospf	read
isis	read
mpls-te	read

Examples

The following example shows sample output with the debug bfd process command for a specified location:

RP/0/RP0/CPU0:router# debug bfd process location 0/0/cpu0

LC/0/0/CPU0:Jun 21 11:49:41 : bfd_agent[105]: DBG-Proc[1]: Local discr is 0x10000, 
0x4824b0f4

Related Commands

Command	Description
debug bfd client-api	Specifies debug information for the BFD server API with API clients.
debug bfd errors	Specifies debug information for all error conditions.
debug bfd fsm	Specifies debug information within the FSM module.
debug bfd ipv4	Specifies debug information for IPv4 sessions.