Table Of Contents
HSRP Debug Commands on Cisco IOS XR Software
debug hsrp all
debug hsrp edm
debug hsrp events
debug hsrp packets
debug hsrp terse
HSRP Debug Commands on Cisco IOS XR Software
This chapter describes the commands used to debug Hot Standby Router Protocol (HSRP) problems.
debug hsrp all
To enable the debugging of all Hot Standby Router Protocol (HSRP) server activity including HSRP errors, events, and packets, use the debug hsrp all command in EXEC mode. To disable the debugging of all HSRP server activity, use the no form of this command.
debug hsrp all [interface-type interface-instance] [group group-id]
no debug hsrp all [interface-type interface-instance] [group group-id]
Syntax Description
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) 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.
|
group group-id
|
(Optional) Restricts debug messages to a particular group. Range is 0 to 255.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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
|
hsrp
|
read, write
|
Examples
The following example shows how to enable HSRP server activity debugging:
RP/0/RP0/CPU0:router# debug hsrp all TenGigE 0/2/0/1
debug hsrp edm
To enable Hot Standby Router Protocol (HSRP) external data manager (EDM) activity debugging, use the debug hsrp edm command in EXEC mode. To disable HSRP EDM activity debugging, use the no form of this command.
debug hsrp edm
no debug hsrp edm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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
|
hsrp
|
read, write
|
Examples
The following example shows how to enable HSRP EDM activity debugging:
RP/0/RP0/CPU0:router# debug hsrp edm
debug hsrp events
To enable Hot Standby Router Protocol (HSRP) event activity debugging, use the debug hsrp events command in EXEC mode. To disable HSRP event activity debugging, use the no form of this command.
debug hsrp events [all | protocol [errors | detail] | redundancy | track] [detail] [interface-type
interface-instance] [group group-id]
no debug hsrp events [all | protocol [errors | detail] | redundancy | track] [detail] [interface-type
interface-instance] [group group-id]
Syntax Description
all
|
(Optional) Displays all HSRP events.
|
protocol
|
(Optional) Displays HSRP protocol events, such as change of HSRP state.
|
errors
|
(Optional) Displays HSRP protocol event errors.
|
detail
|
(Optional) Displays HSRP protocol event details.
|
redundancy
|
(Optional) Displays HSRP IP redundancy events.
|
track
|
(Optional) Displays HSRP tracking events, such as when the tracked interface goes up or down, priority changes, and entering or leaving active or standby state.
|
detail
|
(Optional) Displays more debugging detail.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) 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.
|
group group-id
|
(Optional) Restricts debug messages to a particular group. Range is 0 to 255.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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
|
hsrp
|
read, write
|
Examples
The following example shows how to enable HSRP event activity debugging:
RP/0/RP0/CPU0:router# debug hsrp events
debug hsrp packets
To enable Hot Standby Router Protocol (HSRP) packet debugging, use the debug hsrp packets command in EXEC mode. To disable HSRP packet debugging, use the no form of this command.
debug hsrp packets [advertise | all | coup | hello | resign | statechanges | terse] [detail]
[interface-type interface-instance] [group group-id]
no debug hsrp packets {advertise | all | coup | hello | resign | statechanges | terse} [detail]
[interface-type interface-instance] [group group-id]
Syntax Description
advertise
|
(Optional) Displays HSRP advertisement packets.
|
all
|
(Optional) Displays all HSRP packets.
|
coup
|
(Optional) Displays HSRP coup packets.
|
hello
|
(Optional) Displays HSRP hello packets.
|
resign
|
(Optional) Displays HSRP resign packets.
|
statechanges
|
(Optional) Displays HSRP statechange packets.
|
terse
|
(Optional) Displays all HSRP packets except hellos and advertisements.
|
detail
|
(Optional) Displays HSRP packet details.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) 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.
|
group group-id
|
(Optional) Restricts debug messages to a particular group. Range is 0 to 255.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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
|
hsrp
|
read, write
|
Examples
The following example shows how to enable HSRP packet debugging:
RP/0/RP0/CPU0:router# debug hsrp packets all
Related Commands
Command
|
Description
|
debug hsrp terse
|
Displays the HSRP errors, events, and packets.
|
debug hsrp terse
To enable Hot Standby Router Protocol (HSRP) error, event, and packet debugging, use the debug hsrp terse command in EXEC mode. This command does not display HSRP hellos and advertisements. To disable HSRP error, event, and packet debugging, use the no form of this command.
debug hsrp terse [interface-type interface-instance] [group group-id]
no debug hsrp terse [interface-type interface-instance] [group group-id]
Syntax Description
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) 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.
|
group group-id
|
(Optional) Restricts debug messages to a particular group. Range is 0 to 255.
|
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
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
|
hsrp
|
read, write
|
Examples
The following example shows how to enable HSRP errors, events, and packets debugging:
RP/0/RP0/CPU0:router# debug hsrp terse TenGigE 0/2/0/1
Related Commands