Cisco IOS XR Multicast Debug Command Reference, Release 3.3 - Multicast MFIB Debug Commands on Cisco IOS XR Software [Cisco IOS XR Software (End-of-Sale)]

Table Of Contents

Multicast MFIB Debug Commands on Cisco IOS XR Software

debug mfib adjacency

debug mfib download

debug mfib errors

debug mfib events

debug mfib ha

debug mfib interface

debug mfib ma

debug mfib netio

debug mfib nsf

debug mfib route

debug mfib signal

debug mfib sysdb

debug mfib warning

Multicast MFIB Debug Commands on Cisco IOS XR Software

This chapter describes the commands used to debug multicast routing and forwarding on Cisco IOS XR software.

debug mfib adjacency

To track interface events, use the debug mfib adjacency command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] adjacency [type instance]
no debug mfib [ipv4 | ipv6] adjacency [type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

The degub mfib adjacency command tracks interface events, including interaction with:

•adjacency information base (AIB)

•inter-interface relationships (IIR)

•interface specific configuration updates

•ip address changes

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib adjacency command using the ipv4 keyword and type instance argument:
RP/0/RP0/CPU0:router# debug mfib ipv4 adjacency MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 13:22:48.714: ipv4_mfwd_partner[215]: BCDL: Got 1 BCDL messages 
RP/0/RP0/CPU0:Aug 2 13:22:48.745: ipv4_mfwd_partner[215]: RD: Got 1 new 0 existing route 
updates
debug mfib download

To download route updates to MFIB line cards, use the debug mfib download command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] download [bcdl type instance | location type instance]
no debug mfib [ipv4 | ipv6] download [bcdl type instance | location type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

bcdl

Displays download routes received by the LC MFWD.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib download command using the bcdl keyword and type instance arguments:
RP/0/RP0/CPU0:router# debug mfib download bcdl MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 13:22:48.714: ipv4_mfwd_partner[215]: BCDL: Got 1 BCDL messages 
RP/0/RP0/CPU0:Aug 2 13:22:48.745: ipv4_mfwd_partner[215]: RD: Got 1 new 0 existing route 
updates 
debug mfib errors

To monitor and debug critical errors in line card multicast forwarding, use the debug mfib errors command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] errors [location type instance]
no debug mfib [ipv4 | ipv6] errors [location type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib errors command:
RP/0/RP0/CPU0:router# debug mfib errors MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 13:22:48.714: ipv4_mfwd_partner[215]: ERR: Mismatch in partial updates 
received in ipv4_mfwd_mrib_update. Expected - (1.1.1.1,239.1.1.1/32). Got - 
(2.2.2.2,239.1.1.1/32)
debug mfib events

To debug multicast forwarding server connectivity events, use the debug mfib events command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] events [location type instance]
no debug mfib [ipv4 | ipv6] events [location type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Use the debug mfib events command to monitor connects, disconnects, registrations, binds, and initializations with various servers, including MRIB and IPARMS.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib events command:
RP/0/RP0/CPU0:router# debug mfib events MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 13:41:10.934: ipv4_mfwd_partner[215]: EV: Connected to MRIB 
RP/0/RP0/CPU0:Aug 2 13:41:10.974: ipv4_mfwd_partner[215]: EV: MRIB download complete 
RP/0/RP0/CPU0:Aug 2 13:41:12.878: ipv4_mfwd_partner[215]: EV: Mcast already enabled
debug mfib ha

To track package installation, hot upgrades and downgrades, and sysmgr signal handling, use the debug mfib ha command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] ha [install location type instance | total-clean location type instance]
no debug mfib [ipv4 | ipv6] ha [install location type instance | total-clean location type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

install location

Displays mfib DLL upgrade and downgrade events.

total-clean location

Displays mfib share memory window cleanup events; for example, when mfib restarts during a route transaction, the new mfib process cleans up the share memory window.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib ha command:
RP/0/RP0/CPU0:router# debug mfib ha MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 13:44:50.357: ipv4_mfwd_partner[215]: CLEAN: 
ipv4_mfwd_ha_init_handle_frequent_restart Restart information has been updated 
RP/0/RP0/CPU0:Aug 2 13:44:51.184: ipv4_mfwd_partner[215]: INST: 
ipv4_mfwd_upgrade_init 1508: Successfully registered with Sys mgr cleanup 
RP/0/RP0/CPU0:Aug 2 13:44:51.346: ipv4_mfwd_partner[215]: INST: 
ipv4_mfwd_upgrade_init 1584: Successfully registered for hot upgrade/downgrade
debug mfib interface

To debug interface events, use the debug mfib interface command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib interface [location]
no debug mfib interface [location]
Syntax Description

location

(Optional) Interface type and fully qualified location or group ip address.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows how to debug interface events:
RP/0/RP0/CPU0:router# debug mfib interface replications MgmtEth0/RP1/CPU0/0
debug mfib ma

To track mfib management agent events, use the debug mfib ma command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] ma [interface type interface | sysdb]
no debug mfib [ipv4 | ipv6] ma [interface type interface | sysdb]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

interface

Interface type.

type

(Optional) 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.

sysdb

Displays interactions with sysdb and configuration-related events.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

The multicast forwarding management agent is a management agent running on the route processor. It distributes global multicast configuration to line card multicast forwarding and handles forward referencing for interface configuration.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib ma command:
RP/0/RP0/CPU0:router# debug mfib ma MgmtEth0/RP1/CPU0/0
RP/0/0/CPU0:Aug 2 14:04:11.559: ipv4_mfwd_ma[315]: Added GigabitEthernet0_3_1_0 to FRIS in 
idb_get 
RP/0/0/CPU0:Aug 2 14:04:11.569: ipv4_mfwd_ma[315]: Multicast disabled [set] on 
GigabitEthernet0_3_1_0
debug mfib netio

To track software-switched multicast packets on a specific location, use the debug mfib netio command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] netio [drop [aclname] [location type instance] | packet [aclname] [detail] [location type instance]]
no debug mfib [ipv4 | ipv6] netio [drop [aclname] [location type instance] | packet [aclname] [detail] [location type instance]]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

drop

Displays packets dropped in software mfib.

packet

Displays software switched multicast packet.

aclname

Displays the access list name to limit the debug message to the permitted addresses.

detail

Displays verbose debug output.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Use the debug mfib netio command to track software- switched multicast packets on a specific interface.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib netio command:
RP/0/RP0/CPU0:router# debug mfib netio
RP/0/RP0/CPU0:Aug 2 14:11: 26.471: netio[66]: MFIB-ingress: Pkt (44.0.0.201, 239.1.1.1) 
[0xda3150fc] received. Incoming intf GigabitEthernet0/3/0/0 [0x4000200]
debug mfib nsf

To track mfwd nsf events if multicast NSF is turned on for multicast forwarding NSF events, use the debug mfib nsf command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] nsf [location type instance]
no debug mfib [ipv4 | ipv6] nsf [location type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was initially documented.

Release 3.3.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.

Multicast NSF must be enabled to use the debug mfib nsf command.

Use the debug mfib netio command to track software-switched multicast packets on a specific interface.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib nsf command:
RP/0/RP0/CPU0:router# debug mfib ipv4 nsf location type instance
RP/0/RP0/CPU0:Aug 2 14:18:10.085: ipv4_mfwd_partner[215]: [NSF] MFWD started as NSF 'MNSF' 
mode 
RP/0/RP0/CPU0:Aug 2 14:18:10.089: ipv4_mfwd_partner[215]: [NSF] Started multicast NSF 
timer: 900 secs 
RP/0/RP0/CPU0:Aug 2 14:18:10.098: ipv4_mfwd_partner[215]: [NSF] Old MFIB entries have been 
marked as stale
debug mfib route

To track per route update event in software MFIB, use the debug mfib route command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] route [group address | type instance]
no debug mfib [ipv4 | ipv6] route [group address | type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

group address

Displays the group option to filter on group address.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

The debug mfib route command displays detailed information about route entry and route interface updates.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib route command:
RP/0/RP0/CPU0:router# debug mfib ipv4 route MgmtEth0/RP1/CPU0 /0]
RP/0/RP0/CPU0:Aug 2 16:00:07.698: ipv4_mfwd_partner[215]: (*,
239.1.1.1/32) received: [GigabitEthernet0_3_0_0!A !DP NS IC !SP EG !EI ] 
RP/0/RP0/CPU0:Aug 2 16:00:07.700: ipv4_mfwd_partner[215]: (*,
239.1.1.1/32) received: C !S !IA !IF !D 
debug mfib signal

To track per route signalling events for PIM-SM and PIM-DM ranges in software MFIB, use the debug mfib signal command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] signal [type instance]
no debug mfib [ipv4 | ipv6] signal [type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib signal command:
RP/0/RP0/CPU0:router # debug mfib ipv4 signal MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 16:06:18.142: ipv4_mfwd_partner[215]: SIG: 
ipv4_mfwd_mrib _post: Successfully posted 1 signals in 44 bytes to MRIB
debug mfib sysdb

To track MFIB sysdb local plane events, show client and show server events, use the debug mfib signal command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] sysdb [type instance]
no debug mfib [ipv4 | ipv6] sysdb [type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib sysdb command:
RP/0/RP0/CPU0:router# debug mfib ipv4 sysdb MgmtEth0/RP1/CPU0/0
RP/0/RP0/CPU0:Aug 2 16:15:33.195: ipv4_mfwd_partner[215]: SysDB: 
ttl_threshold: TTL for FI0/3/CPU0 is zero but we got notification to unconfig TTL (stale 
flag set) 
RP/0/RP0/CPU0:Aug 2 16:15:33.196: ipv4_mfwd_partner[215]: SysDB: 
ttl_threshold: TTL for Gi0/3/0/0 is zero but we got notification to unconfig TTL (stale 
flag set) 
RP/0/RP0/CPU0:Aug 2 16:15:33.197: ipv4_mfwd_partner[215]: SysDB: 
Successfully removed all stale configs. 
debug mfib warning

To monitor warnings in MFIB for any anomalies, use the debug mfib warning command in EXEC mode. To disable debugging output, use the no form of this command.

debug mfib [ipv4 | ipv6] warning [type instance]
no debug mfib [ipv4 | ipv6] warning [type instance]
Syntax Description

[ipv4 | ipv6]

(Required) IP protocol versions 4 and 6.

type

(Optional) 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.

Defaults

The default protocol is ipv4.

Command Modes

EXEC

Command History

Release

Modification

Release 3.2

This command was supported on the Cisco CRS-1 and Cisco XR 12000 Series Router.

Release 3.3.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.

Messages categorized as warnings are less critical and often fully-recoverable through automatic retry.

Note All debug commands apply to both ipv4 and ipv6 address families. If you do not specify ipv4 or ipv6, and if the default-afi is not set, ipv4 is the default.

Task ID

Task ID

Operations

multicast

read

Examples

The following example shows sample output for the debug mfib warning command:
RP/0/RP0/CPU0:router# debug mfib ipv4 warning MgmtEth0/RP1/CPU0/0 
RP/0/RP0/CPU0:Aug 2 16:16:36.321: ipv4_mfwd_partner[215]: WARN: 
ipv4_mfwd_sysdb_cfg_if_remove_enable_disable: Got remove enable/disable config on 
Gi0/3/0/0 but there was no config before (stale cfg)