Table Of Contents
Link Bundling Debug Commands on Cisco IOS XR Software
debug bundlemgr local packets
debug bundlemgr local state
debug bundlemgr distrib state
Link Bundling Debug Commands on Cisco IOS XR Software
This chapter contains commands for debugging link bundling on Cisco IOS XR software.
debug bundlemgr local packets
To enable the Link Aggregation Control Protocol (LACP) and Marker PDU traffic state machine debugging for the state machines that are implemented by the bundle manager process running on the modular service cards (MSCs), use the debug bundlemgr local packets command in EXEC mode. To disable debugging, use the no form of this command.
debug bundlemgr local packets [location node-id | port type instance]
no debug bundlemgr local packets [location node-id | port type instance]
Syntax Description
location node-id
|
(Optional) Specifies the line card to debug. The node-id argument is entered in the rack/slot/module notation.
|
port
|
(Optional) Specifies the physical interface that is running LACP. The type argument is entered in the rack/slot/module notation
|
type
|
Interface type. For more information, use the question mark (?) online help function.
|
instance
|
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 card.
• module—Module number. A physical layer interface module (PLIM) is always 0.
• port—Physical port number of the interface.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
The default value is off.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1.
|
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
|
bundle
|
read
|
Examples
The following example shows how to use the debug bundlemgr local packets command:
RP/0/RP0/CPU0:router# debug bundlemgr local packets location 0/3/CPU0
Related Commands
Command
|
Description
|
debug bundlemgr local state
|
Enables the LACP state machine debugging for the state machines that are implemented by the bundle manager process running on the route processor (RP).
|
debug bundlemgr distrib state
|
Enables the LACP state machine debugging for the state machines that are implemented by the bundle manager process running on the route processor (RP).
|
debug bundlemgr local state
To enable the Link Aggregation Control Protocol (LACP) state machine debugging for the state machines that are implemented by the bundle manager process running on the modular service cards (MSCs), use the debug bundlemgr local state command in EXEC mode. To disable debugging, use the no form of this command.
debug bundlemgr local state [location node-id | port type instance]
no debug bundlemgr local state [location node-id | port type instance]
Syntax Description
location node-id
|
(Optional) Specifies the line card to debug. The node-id argument is entered in the rack/slot/module notation.
|
port
|
(Optional) Specifies the physical interface that is running LACP.
|
type
|
Interface type. For more information, use the question mark (?) online help function.
|
instance
|
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 card.
• module—Module number. A physical layer interface module (PLIM) is always 0.
• port—Physical port number of the interface.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
The default value is off.
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
|
bundle
|
read
|
Examples
The following example shows all the transitions a link went through to negotiate LACP and be attached to the bundle with the debug bundlemgr local state command:
RP/0/RP0/CPU0:router# debug bundlemgr local state location 0/3/CPU0
LC/0/3/CPU0:Jun 30 12:57:15.573 : BM-LOCAL[108]: Actor's view of Partner's port, system,
key or aggregation capability is out of date for POS0_3_0_0
LC/0/3/CPU0:Jun 30 12:57:15.591 : BM-LOCAL[108]: Partner and Actor for POS0_3_0_0 agree on
their port, system and key
LC/0/3/CPU0:Jun 30 12:57:15.592 : BM-LOCAL[108]: Neither actor or partner view link
POS0_3_0_0 as individual
LC/0/3/CPU0:Jun 30 12:57:15.593 : BM-LOCAL[108]: Current status for POS0_3_0_0: actor 1,
partner 1
LC/0/3/CPU0:Jun 30 12:57:15.594 : BM-LOCAL[108]: Actor for POS0_3_0_0 is OUTOFSYNC - try
to go INSYNC
LC/0/3/CPU0:Jun 30 12:57:17.660 : BM-LOCAL[108]: Partner and Actor for POS0_3_0_0 agree on
their port, system and key
LC/0/3/CPU0:Jun 30 12:57:17.661 : BM-LOCAL[108]: Neither actor or partner view link
POS0_3_0_0 as individual
LC/0/3/CPU0:Jun 30 12:57:17.664 : BM-LOCAL[108]: Current status for POS0_3_0_0: actor 1,
partner 2
LC/0/3/CPU0:Jun 30 12:57:17.666 : BM-LOCAL[108]: Actor for POS0_3_0_0 is OUTOFSYNC - try
to go INSYNC
LC/0/3/CPU0:Jun 30 12:57:17.743 : BM-LOCAL[108]: Link POS0_3_0_0 changing state to IN
SYNC, but partner is INSYNC or above - go COLLECTING
LC/0/3/CPU0:Jun 30 12:57:17.772 : BM-LOCAL[108]: Partner and Actor for POS0_3_0_0 agree on
their port, system and key
LC/0/3/CPU0:Jun 30 12:57:17.772 : BM-LOCAL[108]: Neither actor or partner view link
POS0_3_0_0 as individual
LC/0/3/CPU0:Jun 30 12:57:17.774 : BM-LOCAL[108]: Current status for POS0_3_0_0: actor 3,
partner 3
LC/0/3/CPU0:Jun 30 12:57:17.775 : BM-LOCAL[108]: Actor for POS0_3_0_0 is COLLECT but
partner is COLLECT or DISTRIB - try to go DISTRIB
LC/0/3/CPU0:Jun 30 12:57:18.262 : BM-LOCAL[108]: Link POS0_3_0_0 changing state to
DISTRIBUTING
LC/0/3/CPU0:Jun 30 12:57:18.290 : BM-LOCAL[108]: Partner and Actor for POS0_3_0_0 agree on
their port, system and key
LC/0/3/CPU0:Jun 30 12:57:18.291 : BM-LOCAL[108]: Neither actor or partner view link
POS0_3_0_0 as individual
LC/0/3/CPU0:Jun 30 12:57:18.292 : BM-LOCAL[108]: Current status for POS0_3_0_0: actor 4,
partner 4
LC/0/3/CPU0:Jun 30 12:57:18.293 : BM-LOCAL[108]: Actor for POS0_3_0_0 is DISTRIB and
partner is COLLECT or DISTRIB - no change needed
Related Commands
debug bundlemgr distrib state
To enable the LACP state machine debugging for the state machines that are implemented by the bundle manager process running on the RP, use the debug bundlemgr distrib state command in EXEC mode. To disable debugging, use the no form of this command.
debug bundlemgr distrib state [port type instance]
no debug bundlemgr distrib state [port type instance]
Syntax Description
port
|
(Optional) Specifies the physical interface that is running LACP.
|
type
|
Interface type. For more information, use the question mark (?) online help function.
|
instance
|
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 card.
• module—Module number. A physical layer interface module (PLIM) is always 0.
• port—Physical port number of the interface.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
The default value is off.
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
|
bundle
|
read
|
Examples
The debug bundlegmr distrib state command lets you only get one message per link each time the selection logic runs. The following example shows a physical member interface for the port with the debug bundlemgr distrib state command:
RP/0/RP0/CPU0:router# debug bundlemgr distrib state port pos
RP/0/RP0/CPU0:router# BM-DISTRIB[124]: Loopback interface - link POS0_3_0_0 NOT
AGGREGATABLE
RP/0/RP0/CPU0:router# BM-DISTRIB[124]: LACP link POS0_3_0_0 is IN SYNC or COLLECTING
RP/0/RP0/CPU0:router# BM-DISTRIB[124]: LACP link POS0_3_0_0 is DISTRIBUTING
Related Commands