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

Table Of Contents

Multicast MLIB Debug Commands on Cisco IOS XR Software

debug mlib connections

debug mlib errors

debug mlib events

debug mlib idb

debug mlib interface

debug mlib routes

debug mlib signal

debug mlib state

debug mlib warning

Multicast MLIB Debug Commands on Cisco IOS XR Software

This chapter describes the commands used to debug multicast MLIB on Cisco IOS XR software.

MLIB is the multicast library handling route and interface programming from software mfib to specific platform calls.

Note Debug messages are generated from both platform independent and platform dependent components.

debug mlib connections

To track platform server connection events, use the debug mlib connections command in EXEC mode. To disable debugging output, use the no form of this command.

debug mlib [ipv4 | ipv6] connections [type instance]
no debug mlib [ipv4 | ipv6] connections [type instance]
Syntax Description

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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 mlib connection command to track platform server connection events, including:

•mstat server

•platform library sysdb connection

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 mlib connection command:
RP/0/RP0/CPU0:router# debug mlib ipv4 connection
RP/0/RP0/CPU0:August 2 16:16:14.359: ipv4_mfwd_partner[147]: ML-DEBUG-CONN: 
ipv4_mfwd_hfr_edm_oper_handler 3757: Disconnected from SysDB at HFR oper
debug mlib errors

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

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

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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 Most errors in MLIB can be recovered automatically.

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 mlib errors command:
RP/0/RP0/CPU0:router# debug mlib ipv4 errors
RP/0/RP0/CPU0:August 2 16:26:14.359: ipv4_mfwd_partner[147]: ML-DEBUG-ERR: 
ipv4mc_queue_intf_change_request 1522: Null Table pointer
debug mlib events

To track software to hardware route programming actions, use the debug mlib events command in EXEC mode. To disable debugging output, use the no form of this command.

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

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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.

Software to hardware route programming actions include route creation and deletion.

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 mlib events command:
RP/0/RP0/CPU0:router# debug mlib ipv4 events
RP/0/RP0/CPU0:August 2 16:36:14.359: ipv4_mfwd_partner[147]: ML-DEBUG-EV: 
ipv4mc_intf_operation 4382: Processing Route (79.17.97.2,225.0.41.16/64) 
intf=Ha0x1580020 action=create
debug mlib idb

To to monitor interface control events, use the debug mlib idb command in EXEC mode. To disable debugging output, use the no form of this command.

debug mlib [ipv4 | ipv6] idb [type instance]
no debug mlib [ipv4 | ipv6] idb [type instance]
Syntax Description

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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.

Control events include enabling interface structure for multicast, adjacency changes, and interface ip addresses.

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 mlib idb command:
RP/0/RP0/CPU0:router# debug mlib ipv4 idb
RP/0/RP0/CPU0:August 2 16:45:52.030: ipv4_mfwd_partner[147]: ML-DEBUG-IDB: 
lcv4mc_update_aib 3082: Updated the adjacency of PO0/4/0/1 l2_load_info 
= 0x4201
RP/0/RP0/CPU0:August 2 16:45:52.030: ipv4_mfwd_partner[147]: ML-DEBUG-IDB: 
lcv4mc_update_aib 3125: Performed 0 routes walk for PO0/4/0/1 because 
adj changed from 0x0 to 0x4201
debug mlib interface

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

debug mlib [ipv4 | ipv6] interface [type instance]
no debug mlib [ipv4 | ipv6] interface [type instance]
Syntax Description

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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.

Track platform interface update events include flap 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 mlib interface command:
RP/0/RP0/CPU0:router# debug mlib ipv4 interface
RP/0/RP0/CPU0:August 2 16:52:03.939: ipv4_mfwd_partner[147]: ML-DEBUG-INTF: 
ipv4mc_platform_intf_operation 1891: Non-local intf uIDB commit 
Ha0x1580020 (A NS) to (79.17.97.2,225.0.84.219/64)
RP/0/RP0/CPU0:August 2 16:52:03.939: ipv4_mfwd_partner[147]: ML-DEBUG-INTF: 
ipv4mc_intf_operation 4603: Existing intf commit Ha0x1580020 (A NS) to 
(79.17.97.2,225.0.84.219/64)
debug mlib routes

To track basic route update events, use the debug mlib routes command in EXEC mode. To disable debugging output, use the no form of this command.

debug mlib [ipv4 | ipv6] routes [type instance]
no debug mlib [ipv4 | ipv6] routes [type instance]
Syntax Description

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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.

For detail event tracking, use the debug mlib events command.

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 mlib routes command:
RP/0/RP0/CPU0:router# debug mlib ipv4 routes
RP/0/RP0/CPU0:August 2 16:56:59.091: ipv4_mfwd_partner[147]: 
ML-DEBUG-ROUTE: ipv4mc_route_operation 4005: Existing route commit 
(79.17.97.2,225.0.23.239/64) (0 0 0)
RP/0/RP0/CPU0:August 2 16:56:59.091: ipv4_mfwd_partner[147]: 
ML-DEBUG-ROUTE: ipv4mc_route_operation 3551: Existing route create 
(79.17.97.2,225.0.24.7/64) (0 0 0)
debug mlib signal

To to monitor per route signalling event for PIM-SM and PIM-DM range in the platform library, use the the debug mlib signal command in EXEC mode. To disable debugging output, use the no form of this command.

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

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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 sample output for the debug mlib signal command:
RP/0/RP0/CPU0:router# debug mlib ipv4 signal
RP/0/RP0/CPU0:August 2 17:00:01.367: ipv4_mfwd_partner[147]: ML-DEBUG-SIG: 
ipv4mc_signal_lookup 7023: Signal Nf0x00000000 
(79.17.97.2,225.0.101.136/64) not found
debug mlib state

To monitor platform library state transition, use the debug mlib signal command in EXEC mode. To disable debugging output, use the no form of this command.

debug mlib [ipv4 | ipv6] state [type instance]
no debug mlib [ipv4 | ipv6] state [type instance]
Syntax Description

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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 sample output for the debug mlib state command:
RP/0/RP0/CPU0:router# debug mlib ipv4 state
RP/0/RP0/CPU0:August 2 17:04:02.156: ipv4_mfwd_partner[147]: 
ML-DEBUG-STATE: ipv4mc_idb_init 3881: IDB state changed from NOTREADY to 
CONNECTING
RP/0/RP0/CPU0:August 2 17:04:02.156: ipv4_mfwd_partner[147]: 
ML-DEBUG-STATE: ipv4mc_idb_init 4002: IDB state changed from CONNECTING 
to READY
debug mlib warning

To monitor warnings in MLIB, use the debug mlib warning command in EXEC mode. To disable debugging output, use the no form of this command.

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

[ipv4 | ipv6]

IP protocol versions 4 and 6.

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.

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.

Messages categorized as warnings are less critical and often fully recoverable using 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 mlib warning command:
RP/0/RP0/CPU0:router# debug mlib ipv4 warning
RP/0/RP0/CPU0:August 2 17:04:03.156: ipv4_mfwd_partner[147]: ML-DEBUG-WARN: 
ipv4mc_queue_intf_change_request 1536: Maximum number of queued requests 
exceeded