-
Cisco IOS High Availability Command Reference
-
Introduction
-
action cli through configure replace
-
control-plane through debug mpls ldp checkpoint
-
debug mpls ldp graceful-restart through event wdsysmon
-
frame-relay redundancy auto-sync lmi-sequence-numbers through issu set rollback-timer
-
match mpls-label through route-target
-
service call-home through show ip pim interface
-
show ip pim neighbor through show ppp subscriber statistics
-
show pppatm statistics through vrrp timers learn
-
Table Of Contents
debug archive config differences ha
debug archive config timestamp
debug ip dhcp server redundancy
debug mpls checkpoint label-binding
debug mpls l2transport checkpoint
control-plane
To enter control-plane configuration mode, which allows users to associate or modify attributes or parameters (such as a service policy) that are associated with the control plane of the device, use the control-plane command in global configuration mode. To remove an existing control-plane configuration from the router, use the no form of this command.
Syntax for T Releases
control-plane [host | transit | cef-exception]
no control-plane [host | transit | cef-exception]
Syntax for 12.0S Releases
control-plane [slot slot-number] [host | transit | cef-exception]
no control-plane [slot slot-number] [host | transit | cef-exception]
Syntax for 12.2S Releases for Cisco 7600 Series Routers
control-plane
no control-plane
Syntax for ASR 1000 Series Routers
control-plane [host]
no control-plane [host]
Syntax Description
Command Default
No control-plane service policies are defined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
After you enter the control-plane command, you can apply a control-plane policing (CoPP), port-filter, or queue-threshold policy to police traffic destined for the control plane. You can define aggregate CoPPs for the route processor (RP) and configure a service policy to police all traffic destined to the control plane:
•
From all line cards on the router (aggregate CP services)
•
Aggregate CP services manage traffic destined for the control plane and received on the central switch engine from all line cards in the router.
Distributed CP services manage CP traffic from interfaces on a specified line card before CP packets are forwarded to the central switch engine where aggregate CP services are applied.
Note
Control-plane policing includes enhanced control-plane functionality. It provides a mechanism for early dropping of packets directed toward closed or nonlistened Cisco IOS TCP/UPD ports on the router. It also provides the ability to limit protocol queue usage such that no single misbehaving protocol process can wedge the control plane interface hold queue.
Note
With this enhancement, you can classify control-plane traffic into different categories of traffic. These categories are as follows:
•
•
•
Examples
The following example shows how to configure trusted hosts with source addresses 10.1.1.1 and 10.1.1.2 to forward Telnet packets to the control plane without constraint, while allowing all remaining Telnet packets to be policed at the specified rate. The QoS policy is then applied for aggregate CP services to all packets that are entering the control plane from all line cards in the router.
! Allow 10.1.1.1 trusted host traffic.Router(config)# access-list 140 deny tcp host 10.1.1.1 any eq telnet! Allow 10.1.1.2 trusted host traffic.Router(config)# access-list 140 deny tcp host 10.1.1.2 any eq telnet! Rate-limit all other Telnet traffic.Router(config)# access-list 140 permit tcp any any eq telnet! Define class map "telnet-class."Router(config)# class-map telnet-classRouter(config-cmap)# match access-group 140Router(config-cmap)# exitRouter(config)# policy-map control-plane-inRouter(config-pmap)# class telnet-classRouter(config-pmap-c)# police 80000 conform transmit exceed dropRouter(config-pmap-c)# exitRouter(config-pmap)# exit! Define aggregate control-plane service for the active route processor.Router(config)# control-planeRouter(config-cp)# service-policy input control-plane-inRouter(config-cp)# endThe next example also shows how to configure trusted hosts with source addresses 10.1.1.1 and 10.1.1.2 to forward Telnet packets to the control plane without constraint, while allowing all remaining Telnet packets that enter through slot 1 to be policed at the specified rate. The QoS policy is applied for distributed CP services to all packets that enter through the interfaces on the line card in slot 1 and that are destined for the control plane.
! Allow 10.1.1.1 trusted host traffic.Router(config)# access-list 140 deny tcp host 10.1.1.1 any eq telnet! Allow 10.1.1.2 trusted host traffic.Router(config)# access-list 140 deny tcp host 10.1.1.2 any eq telnet! Rate-limit all other Telnet traffic.Router(config)# access-list 140 permit tcp any any eq telnet! Define class map "telnet-class."Router(config)# class-map telnet-classRouter(config-cmap)# match access-group 140Router(config-cmap)# exitRouter(config)# policy-map control-plane-inRouter(config-pmap)# class telnet-classRouter(config-pmap-c)# police 80000 conform transmit exceed dropRouter(config-pmap-c)# exitRouter(config-pmap)# exit! Define aggregate control-plane service for the active route processor.Router(config)# control-plane slot 1Router(config-cp)# service-policy input control-plane-inRouter(config-cp)# endThe following shows how to apply an aggregate CoPP policy to the host control-plane traffic by applying it to the host control-plane feature path:
Router(config)# control-plane hostRouter(config-cp)# service-policy input cpp-policy-hostThe following shows how to apply an aggregate CoPP policy to the transit control-plane traffic by applying it to the control-plane transit feature path:
Router(config)# control-plane transitRouter(config-cp)# service-policy input cpp-policy-transitThe following shows how to apply an aggregate CoPP policy to the CEF-exception control-plane traffic by applying it to the control-plane CEF-exception feature path:
Router(config)# control-plane cef-exceptionRouter(config-cp)# service-policy input cpp-policy-cef-exceptionRelated Commands
crashdump-timeout
To set the longest time that the newly active Route Switch Processor (RSP) will wait before reloading the formerly active RSP, use the crashdump-timeout command in redundancy mode. To reset the default time that the newly active RSP will wait before reloading the formerly active RSP, use the no form of this command.
crashdump-timeout [mm | hh:mm]
no crashdump-timeout
Syntax Description
Command Default
The default timeout for this command is 5 minutes.
Command Modes
Redundancy
Command History
Usage Guidelines
Use this command to specify the length of time that the newly active RSP will wait before reloading the previously active RSP. This time can be important when considering how long to wait for a core dump to complete before reloading the RSP.
In networking devices that support stateful switchover (SSO), the newly active primary processor runs the core dump operation after the switchover has taken place. Following the switchover, the newly active RSP will wait for a period of time for the core dump to complete before attempting to reload the formerly active RSP.
In the event that the core dump does not complete within the time period provided, the standby RSP is reset and reloaded based on the crashdump timeout command setting, regardless of whether it is still performing a core dump.
Note
Examples
The following example sets the time before the previously active RSP is reloaded to 10 minutes:
Router(config-r)# crashdump-timeout 10dampening
To configure a router to automatically dampen a flapping interface, use the dampening command in interface configuration mode. To disable automatic route dampening, use the no form of this command.
dampening [half-life-period reuse-threshold] [suppress-threshold max-suppress-time [restart-penalty]]
no dampening
Syntax Description
Defaults
This command is disabled by default. To manually configure the timer for the restart-penalty argument, the value for all arguments must be manually entered.
Command Modes
Interface configuration
Command History
Usage Guidelines
The IP Event Dampening feature will function on a subinterface but cannot be configured on only the subinterface. Only the primary interface can be configured with this feature. Primary interface configuration is applied to all subinterfaces by default.
When an interface is dampened, the interface is dampened to both IP and Connectionless Network Services (CLNS) routing equally. The interface is dampened to both IP and CLNS because integrated routing protocols such as Intermediate System-to-Intermediate System (IS-IS), IP, and CLNS routing protocols are closely interconnected, so it is impossible to apply dampening separately.
Copying a dampening configuration from virtual templates to virtual access interfaces is not supported because dampening has limited usefulness to existing applications using virtual templates. Virtual access interfaces are released when an interface flaps, and new connections and virtual access interfaces are acquired when the interface comes up and is made available to the network. Because dampening states are attached to the interface, the dampening states would not survive an interface flap.
If the dampening command is applied to an interface that already has dampening configured, all dampening states are reset and the accumulated penalty will be set to 0. If the interface has been dampened, the accumulated penalty will fall into the reuse threshold range, and the dampened interface will be made available to the network. The flap counts, however, are retained.
Examples
The following example sets the half life to 30 seconds, the reuse threshold to 1500, the suppress threshold to 10000, and the maximum suppress time to 120 seconds:
interface Ethernet 0/0dampening 30 1500 10000 120The following example configures the router to apply a penalty of 500 on Ethernet interface 0/0 when the interface comes up for the first time after the router is reloaded:
interface Ethernet 0/0dampening 5 500 1000 20 500Related Commands
debug acircuit checkpoint
To enable the display of attachment circuit (AC) events when Any Transport over MPLS (AToM) is configured for nonstop forwarding/stateful switchover (NSF/SSO) and Graceful Restart, use the debug acircuit checkpoint command in privileged EXEC mode. To disable the display of these messages, use the no form of this command.
debug acircuit checkpoint
no debug acircuit checkpoint
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging of the AToM NSF/SSO and Graceful Restart feature is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use debug commands with care. They use a significant amount of CPU time and can affect system performance.
Examples
The debug acircuit checkpoint command is issued on the active RP:
Router# debug mpls l2transport checkpointRouter# debug acircuit checkpointRouter# show debugAToM HA:AToM checkpointing events and errors debugging is onAC HA:Attachment Circuit Checkpoint debugging is onRouter# conf terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Fa5/1/1.2Router(config-subif)# xconnect 10.55.55.2 1002 pw-class mplsAToM HA [10.55.55.2, 1002]: Build provision msg, SSM sw/seg 8192/8194 [0x2000/0x2002] PW i d 9216 [0x2400] local label 21AC HA: Dynamic Sync. Event:4 Sw:8192[2000] Se:16385[4001]AToM HA: CF sync send completeAC HA CF: Sync send complete. Code:0On the standby RP, the following messages indicate that it receives checkpointing data:
AC HA [10.55.55.2, 1002]: Add to WaitQ. Flags:1AToM HA [10.55.55.2, 1002]: Received 32-byte provision version 1 CF messageAC HA CF: ClientId:89, Entity:0 Length:40AToM HA [10.55.55.2, 1002]: Process chkpt msg provision [1], ver 1AToM HA [10.55.55.2, 1002]: Reserved SSM sw/seg 8192/8194 [0x2000/0x2002] PW id 9216 [0x24 00]AC HA: Process Msg:35586. Ptr:44CBFD90. Val:0AC HA: Sync. Event:4 CktType:4 Sw:8192[2000] Se:16385[4001]AC HA [10.55.55.2, 1002]: Remove from WaitQ. Flags:1[OK][OK]During a switchover from the active to the backup Route Processor, the debug messages look similar to the following:
%HA-5-MODE: Operating mode is hsa, configured mode is sso.AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Opr:5, St:STANDBY HO T, PSt:ACTIVEAToM HA: CID 84, Seq 715, Status RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Op 5, State STANDB Y HOT, Peer ACTIVEAC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:STANDBY HOT, PSt:ACTIVEAToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_PRESENCE, Op 0, State STANDBY HOT, Peer AC TIVEAC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_COMM, Opr:0, St:STANDBY HOT, PSt:DISABLEDAToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_COMM, Op 0, State STANDBY HOT, Peer DISABL ED%HA-2-CUTOVER_NOTICE: Cutover initiated. Cease all console activity until system restarts.%HA-2-CUTOVER_NOTICE: Do not add/remove RSPs or line cards until switchover completes.%HA-2-CUTOVER_NOTICE: Deinitializing subsystems...%OIR-6-REMCARD: Card removed from slot 4, interfaces disabled%OIR-6-REMCARD: Card removed from slot 5, interfaces disabled%OIR-6-REMCARD: Card removed from slot 9, interfaces disabled%HA-2-CUTOVER_NOTICE: Reinitializing subsystems...%HA-2-CUTOVER_NOTICE: System preparing to restart...%HA-5-NOTICE: Resuming initialization...AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_REDUNDANCY_MODE_CHANGE, Opr:7, St:STANDBY HOT, PS t:DISABLED...%LDP-5-GR: LDP restarting gracefully. Preserving forwarding state for 250 seconds.AC HA RF: CId:83, Seq:710, Sta:RF_PROG_ACTIVE, Opr:0, St:ACTIVE, PSt:DISABLEDAToM HA: CID 84, Seq 715, Event RF_PROG_ACTIVE, Op 0, State ACTIVE, Peer DISABLEDAC HA: Process Msg:35588. Ptr:0. Val:0AC HA: Switchover: Standby->ActiveAC HA RF: ReconcilingRelated Commands
debug mpls l2transport checkpoint
Enables the display of AToM events when AToM is configured for NSF/SSO and Graceful Restart.
debug archive config differences ha
To display configuration differences in the Route Processor (RP) synchronization procedure, use the debug archive config differences ha command in privileged EXEC mode. To disable the display, use the no form of this command.
debug archive config differences ha
no debug archive config differences ha
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Consult Cisco Technical Support before using this command.
Examples
The following example allows configuration differences in the RP synchronization procedure to be displayed:
Router# debug archive config differences hadebug archive config timestamp
To enable debugging of the processing time for each integral step of a configuration replace operation and the size of the configuration files being handled, use the debug archive config timestamp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug archive config timestamp
no debug archive config timestamp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug archive config timestamp command:
Router# debug archive config timestampRouter# configure replace disk0:myconfig forceTiming Debug Statistics for IOS Config Replace operation:Time to read file slot0:sample_2.cfg = 0 msec (0 sec)Number of lines read:55Size of file :1054Starting Pass 1Time to read file system:running-config = 0 msec (0 sec)Number of lines read:93Size of file :2539Time taken for positive rollback pass = 320 msec (0 sec)Time taken for negative rollback pass = 0 msec (0 sec)Time taken for negative incremental diffs pass = 59 msec (0 sec)Time taken by PI to apply changes = 0 msec (0 sec)Time taken for Pass 1 = 380 msec (0 sec)Starting Pass 2Time to read file system:running-config = 0 msec (0 sec)Number of lines read:55Size of file :1054Time taken for positive rollback pass = 0 msec (0 sec)Time taken for negative rollback pass = 0 msec (0 sec)Time taken for Pass 2 = 0 msec (0 sec)Total number of passes:1Rollback DoneRelated Commands
debug archive versioning
Enables debugging of the Cisco IOS configuration archive activities.
debug archive versioning
To enable debugging of the Cisco IOS configuration archive activities, use the debug archive versioning command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug archive versioning
no debug archive versioning
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug archive versioning command:
Router# debug archive versioningJan 9 06:46:28.419:backup_running_configJan 9 06:46:28.419:Current = 7Jan 9 06:46:28.443:Writing backup file disk0:myconfig-7Jan 9 06:46:29.547: backup workedRelated Commands
debug atm ha-error
To debug ATM) high-availability (HA errors on a networking device, use the debug atm ha-error command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug atm ha-error
no debug atm ha-error
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding ATM HA errors on the networking device:
Router# debug atm ha-errorRelated Commands
debug atm ha-events
Debugs ATM HA events on the networking device.
debug atm ha-state
Debugs ATM HA state information on the networking device.
debug atm ha-events
To debug ATM high-availability (HA) events on the networking device, use the debug atm ha-events command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug atm ha-events
no debug atm ha-events
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding ATM HA events on the networking device:
Router# debug atm ha-eventsRelated Commands
debug atm ha-error
Debugs ATM HA errors on the networking device.
debug atm ha-state
Debugs ATM HA state information on the networking device.
debug atm ha-state
To debug ATM high-availability (HA) state information on the networking device, use the debug atm ha-state command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug atm ha-state
no debug atm ha-state
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding the ATM HA state on the networking device:
Router# debug atm ha-stateRelated Commands
debug atm ha-error
Debugs ATM HA errors on the networking device.
debug atm ha-events
Debugs ATM HA events on the networking device.
debug bfd
To display debugging messages about Bidirectional Forwarding Detection (BFD), use the debug bfd command in privileged EXEC mode. To disable debugging output, use the no form of this command.
Cisco IOS Release 12.2(18)SXE, 12.4(4)T, and 12.2(33)SRA
debug bfd {event | packet [ip-address | ipv6-address]}
no debug bfd {event | packet [ip-address | ipv6-address]}
Cisco IOS Release 12.0(31)S
debug bfd {event | packet [ip-address] | ipc-error | ipc-event | oir-error | oir-event}
no debug bfd {event | packet [ip-address] | ipc-error | ipc-event | oir-error | oir-event}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bfd command can be used to troubleshoot the BFD feature.
Note
Examples
The following example shows output from the debug bfd packet command. The IP address has been specified in order to limit the packet information to one interface:
Router# debug bfd packet 172.16.10.5BFD packet debugging is on*Jan 26 14:47:37.645: Tx*IP: dst 172.16.10.1, plen 24. BFD: diag 2, St/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 1, tx 1000000, rx 1000000 100000, timer 1000 ms, #103*Jan 26 14:47:37.645: %OSPF-5-ADJCHG: Process 10, Nbr 172.16.10.12 on Ethernet1/4 from FULL to DOWN, Neighbor Down: BFD node down*Jan 26 14:47:50.685: %OSPF-5-ADJCHG: Process 10, Nbr 172.16.10.12 on Ethernet1/4 from LOADING to FULL, Loading Done*Jan 26 14:48:00.905: Rx IP: src 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (1/0/0/0), mult 4, len 24, loc/rem discr 2 1, tx 1000000, rx 1000000 100000, timer 4000 ms, #50*Jan 26 14:48:00.905: Tx IP: dst 172.16.10.1, plen 24. BFD: diag 2, St/D/P/F (2/0/0/0), mult 5, len 24, loc/rem discr 1 2, tx 1000000, rx 1000000 100000, timer 1000 ms, #131*Jan 26 14:48:00.905: Rx IP: src 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (3/0/0/0), mult 4, len 24, loc/rem discr 2 1, tx 1000000, rx 1000000 100000, timer 4000 ms, #51*Jan 26 14:48:00.905: Tx IP: dst 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (3/0/0/0), mult 5, len 24, loc/rem discr 1 2, tx 1000000, rx 1000000 100000, timer 1000 ms, #132The following example shows output from the debug bfd event command when an interface between two BFD neighbor routers fails and then comes back online:
Router# debug bfd event22:53:48: BFD: bfd_neighbor - action:DESTROY, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.222:53:48: BFD: bfd_neighbor - action:DESTROY, proc:512, idb:FastEthernet0/1, neighbor:172.16.10.222:53:49: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event DETECT TIMER EXPIRED, state UP -> FAILING...22:56:35: BFD: bfd_neighbor - action:CREATE, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.222:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state FAILING -> DOWN22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state DOWN -> INIT22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 1, state INIT -> UPTable 11 describes the significant fields shown in the display.
The following example shows output from the debug bfd packet command when an interface between two BFD neighbor routers fails and then comes back online. The diagnostic code changes from 0 (No Diagnostic) to 1 (Control Detection Time Expired) because no BFD control packets could be sent (and therefore detected by the BFD peer) after the interface fails. When the interface comes back online, the diagnostic code changes back to 0 to signify that BFD packets can be sent and received by the BFD peers.
Router# debug bfd packet23:03:25: Rx IP: src 172.16.10.2, plen 24. BFD: diag 0, H/D/P/F (0/0/0/0), mult 3, len 24, loc/rem discr 5 1, tx 1000000, rx 10000723:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (0/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 100000823:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 1000009Table 12 describes the significant fields shown in the display.
debug condition glbp
To display debugging messages about Gateway Load Balancing Protocol (GLBP) conditions, use the debug condition glbp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug condition glbp interface-type interface-number group [forwarder]
no debug condition glbp interface-type interface-number group [forwarder]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug condition glbp command:
Router# debug condition glbp fastethernet 0/0 10 1Condition 1 set5d23h: Fa0/0 GLBP10.1 Debug: Condition 1, glbp Fa0/0 GLBP10.1 triggered, count 1Related Commands
debug dampening
To display debug trace information messages for interface dampening, use the debug dampening command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dampening [all | interface]
no debug dampening [all | interface]
Syntax Description
all
(Optional) Enables trace debugging for all dampening features.
interface
(Optional) Enables trace debugging for IP event dampening.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output is similar to the output that will be displayed when the debug dampening command is entered with the interface keyword. The sample output shows the following information:
•
•
Router# debug dampening interface00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to DOWN00:07:17:EvD(Ethernet1/1):charge penalty 1000, new accum. penalty 1000, flap count 100:07:17:EvD(Ethernet1/1):accum. penalty 1000, now suppressed with a reuse intervals of 3000:07:17:IF-EvD(Ethernet1/1):update CLNS Routing state to DOWN, interface is suppressed00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from DOWN to DOWN00:07:17:IF-EvD(Ethernet1/1):update IP Routing state to DOWN, interface is suppressed00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from DOWN to UP00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to DOWN00:07:17:EvD(Ethernet1/1):accum. penalty decayed to 1000 after 0 second(s)00:07:17:EvD(Ethernet1/1):charge penalty 1000, new accum. penalty 2000, flap count 200:07:17:EvD(Ethernet1/1):accum. penalty 2000, now suppressed with a reuse intervals of 6000:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from DOWN to UP00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to DOWN00:07:17:EvD(Ethernet1/1):accum. penalty decayed to 2000 after 0 second(s)00:07:17:EvD(Ethernet1/1):charge penalty 1000, new accum. penalty 3000, flap count 300:07:17:EvD(Ethernet1/1):accum. penalty 3000, now suppressed with a reuse intervals of 7800:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from DOWN to UP00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP00:07:20:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to UP00:07:20:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP00:07:47:IF-EvD:unsuppress interfaces00:08:36:IF-EvD:unsuppress interfaces00:08:36:EvD(Ethernet1/1):accum. penalty decayed to 483 after 79 second(s)00:08:36:EvD(Ethernet1/1):accum. penalty 483, now unsuppressed00:08:36:IF-EvD(Ethernet1/1):update IP Routing state to UP, interface is not suppressed00:08:36:IF-EvD(Ethernet1/1):update CLNS Routing state to UP, interface is not suppressed00:08:36:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to UPTable 13 describes the significant fields shown in the display.
debug dhcp redundancy
To display debugging information about DHCP proxy client redundancy events, use the debug dhcp redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug dhcp redundancy
no debug dhcp redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging output is disabled for DHCP redundancy events.
Command Modes
Privileged EXEC
Command History
12.2(31)SB2
This command was introduced.
12.2(31)SRB1
This command was integrated into Cisco IOS Release 12.2(31)SRB1.
Examples
The following example displays debug messages regarding DHCP redundancy events. The last line is output when the debug dhcp redundancy command is enabled. The line indicates that the active Route Processor has sent a dynamic lease synchronization message for IP address 10.1.1.1:
Router# debug dhcp redundancy*Mar 15 10:32:21: DHCPD: assigned IP address 10.1.1.1 to client*Mar 15 10:32:21: DHCPD: dynamic sync sent for 10.1.1.1Related Commands
debug ip dhcp server redundancy
Displays debugging information about DHCP server and relay agent redundancy events.
debug eigrp nsf
To display nonstop forwarding (NSF) events in the console of the router, use the debug eigrp nsf command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp nsf
no debug eigrp nsf
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The output from the debug eigrp nsf command displays NSF-specific events. This command can be issued on either an NSF-capable or an NSF-aware router.
Examples
The following example shows how to enable Enhanced Interior Gateway Routing Protocol (EIGRP) NSF debugging and display information about neighbor devices:
Router# debug eigrp nsfEIGRP NSF debugging is onRouter# show ip eigrp neighbors detailEIGRP-IPv4 Neighbors for AS(100)H Address Interface Hold Uptime SRTT RTO Q Seq(sec) (ms) Cnt Num0 1.1.2.1 Et1/0 11 00:00:25 10 200 0 5Version 5.1/3.0, Retrans: 2, Retries: 0, Prefixes: 1Topology-ids from peer - 0Router#*Sep 23 18:57:19.423: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 1.1.2.1 (Ethernet1/0) is resync: peer graceful-restartRouter#*Sep 23 18:57:19.423: EIGRP: NSF: AS100, NSF or GR initiated by 1.1.2.1, flags 0x4:(RS)Router#*Sep 23 18:57:36.028: EIGRP: NSF: AS100, Receive EOT from 1.1.2.1, Flags 0x8:(EOT)*Sep 23 18:57:36.028: EIGRP: NSF: route hold timer set to flush stale routes*Sep 23 18:57:36.038: EIGRP: NSF: AS100. route hold timer expiry*Sep 23 18:57:36.038: EIGRP: NSF: EIGRP-IPv4: Search for stale routes from 1.1.2.1Router#Router# show ip eigrp neighbors detailEIGRP-IPv4 Neighbors for AS(100)H Address Interface Hold Uptime SRTT RTO Q Seq(sec) (ms) Cnt Num0 1.1.2.1 Et1/0 11 00:02:31 12 200 0 6Time since Restart 00:01:34Version 5.1/3.0, Retrans: 2, Retries: 0, Prefixes: 1Topology-ids from peer - 0Router#The following sample output shows when a router was unable to handle an event with NSF-Awareness:
*Sep 23 18:59:56.040: EIGRP: NSF: AS100: Checking if Graceful Restart is possible with neighbor 1.1.2.1, peer_down reason 'peer restarted'*Sep 23 18:59:56.040: EIGRP: NSF: Not possible: 'peer_down was called with a HARD resync flag'Router#*Sep 23 18:59:56.040: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 1.1.2.1 (Ethernet1/0) is down: peer restartedRouter#*Sep 23 19:00:00.170: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 1.1.2.1 (Ethernet1/0) is up: new adjacencyRouter#*Sep 23 19:00:00.170: EIGRP: NSF: Enqueuing NULL update to 1.1.2.1, flags 0x1:(INIT)debug event manager
To turn on the debugging output of Embedded Event Manager (EEM) processes, use the debug event manager command in privileged EXEC mode. To turn off debugging output, use the no form of this command or the undebug command.
debug event manager {action cli | action cns | action mail | all | api calls | api errors | common | detector all | detector appl | detector cli | detector config | detector counter | detector env | detector gold | detector interface | detector ioswdsysmon | detector ipsla | detector nf | detector none | detector oir | detector resource | detector rf | detector routing | detector rpc | detector snmp | detector snmp-notification | detector syslog | detector test | detector timer | detector track | metricdir | policydir | server ISSU | server events | server scheduling | snap calls | snap errors | tcl cli_library | tcl commands | tcl smtp_library | xml parser}
no debug event manager {action cli | action cns | action mail | all | api calls | api errors | common | detector all | detector appl | detector cli | detector config | detector counter | detector env | detector gold | detector interface | detector ioswdsysmon | detector ipsla | detector nf | detector none | detector oir | detector resource | detector rf | detector routing | detector rpc | detector snmp | detector snmp-notification | detector syslog | detector test | detector timer | detector track | metricdir | policydir | server ISSU | server events | server scheduling | snap calls | snap errors | tcl cli_library | tcl commands | tcl smtp_library | xml parser}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug event manager command to troubleshoot EEM command operations.
Caution
Examples
The following example turns on debugging messages about EEM server events and then configures an applet to write a message—Test message—to syslog. The debug output that follows displays the various EEM operations that occur as the applet is processed.
Router# debug event manager server eventsDebug Embedded Event Manager server events debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# event manager applet timer-testRouter(config-applet)# event timer countdown time 20Router(config-applet)# action label1 syslog msg "Test message"Router(config-applet)# end03:46:55: fh_server: fh_io_msg: received msg 6 from client jobid 1103:46:55: fh_server: fh_io_msg: handling event register with esid = 2303:46:55: fh_msg_send_to_fd: receive a reply msg, minor: 503:46:55: fh_server: fh_io_msg: received msg 26 from client jobid 1103:46:55: fh_msg_send_to_fd: receive a reply msg, minor: 503:46:55: %SYS-5-CONFIG_I: Configured from console by console03:47:15: fd_pulse_hndlr: received a pulse from /dev/fm/fd_timer03:47:15: fh_msg_send_to_fd: receive a reply msg, minor: 503:47:15: fd_pulse_hndlr: received FH_MSG_EVENT_PUBLISH03:47:15: fh_schedule_callback: fh_schedule_callback: cc=632C0B68 prev_epc=0; epc=63A4167003:47:15: fh_io_msg: received FH_MSG_API_INIT; jobid=13, processid=82, client=3, job name=EEM Callback Thread03:47:15: fh_server: fh_io_msg: received msg 10 from client jobid 1303:47:15: %HA_EM-6-LOG: timer-test: Test message03:47:15: fh_server: fh_io_msg: received msg 62 from client jobid 1303:47:15: fh_schedule_callback: fh_schedule_callback: cc=632C0B68 prev_epc=63A41670; epc=003:47:15: fh_server: fh_io_msg: received msg 1 from client jobid 1303:47:15: fh_io_msg: received FH_MSG_API_CLOSE client=3Table 14 describes the significant fields shown in the display.
debug frame-relay redundancy
To debug Frame Relay and Multilink Frame Relay redundancy on the networking device, use the debug frame-relay redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug frame-relay redundancy
no debug frame-relay redundancy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to debug Frame Relay synchronization problems. The debug frame-relay redundancy command logs synchronization events and errors.
Examples
The following example displays debug messages regarding Frame Relay redundancy on the networking device:
Router# debug frame-relay redundancyRelated Commands
frame-relay redundancy auto-sync lmi-sequence-numbers
Configures LMI synchronization parameters.
debug glbp errors
To display debugging messages about Gateway Load Balancing Protocol (GLBP) error conditions, use the debug glbp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp errors
no debug glbp errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug glbp errors command:
Router# debug glbp errorsGLBP Errors debugging is on1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not foundRelated Commands
debug condition glbp
Displays debugging messages about GLBP that match specific conditions.
debug glbp events
To display debugging messages about Gateway Load Balancing Protocol (GLBP) events that are occurring, use the debug glbp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp events [all | api | cache | detail | ha | icmp | protocol | redundancy | terse | track]
no debug glbp events [all | api | cache | detail | ha | icmp | protocol | redundancy | terse | track]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug glbp events command when the terse keyword is specified:
Router# debug glbp events terseGLBP Events debugging is on(protocol, redundancy, track)The following is sample output from the debug glbp events command on an active RP displaying an interface shutdown event:
Router# debug glbp eventsGLBP Events debugging is on*Sep 15 09:14:53.583: GLBP: Et0/0 API Software interface going down*Sep 15 09:14:53.583: GLBP: Et0/0 API Software interface going down*Sep 15 09:14:53.583: GLBP: Et0/0 Interface down*Sep 15 09:14:53.583: GLBP: Et0/0 1.1 Listen: e/Forwarder disabled*Sep 15 09:14:53.583: GLBP: Et0/0 1.1 Listen -> Init*Sep 15 09:14:53.583: GLBP: Et0/0 Fwd 1.1 HA Encoded (state Init) into sync buffer*Sep 15 09:14:53.583: GLBP: Et0/0 1.2 Active: e/Forwarder disabled*Sep 15 09:14:53.583: GLBP: Et0/0 1.2 Active -> Init*Sep 15 09:14:53.583: %GLBP-6-FWDSTATECHANGE: Ethernet0/0 Grp 1 Fwd 2 state Active -> Init*Sep 15 09:14:53.583: GLBP: Et0/0 Fwd 1.2 HA Encoded (state Init) into sync buffer*Sep 15 09:14:53.583: GLBP: Et0/0 1 Standby: e/GLBP disabled*Sep 15 09:14:53.583: GLBP: Et0/0 1 Active router IP is unknown, was 172.24.1.2*Sep 15 09:14:53.583: GLBP: Et0/0 1 Standby router is unknown, was local*Sep 15 09:14:53.583: GLBP: Et0/0 1 Standby -> Init*Sep 15 09:14:53.583: GLBP: Et0/0 Grp 1 HA Encoded (state Init) into sync buffer*Sep 15 09:14:55.583: %LINK-5-CHANGED: Interface Ethernet0/0, changed state to administratively down*Sep 15 09:14:55.587: GLBP: API Hardware state change*Sep 15 09:14:56.595: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0, changed state to downThe following is sample output from the debug glbp events command on a standby RP displaying an interface shutdown event:
RouterRP-standby# debug glbp eventsGLBP Events debugging is on...*Sep 15 09:14:53.691: GLBP: Et0/0 Fwd 1.1 HA sync, state Listen -> Init*Sep 15 09:14:53.691: GLBP: Et0/0 Fwd 1.2 HA sync, state Active -> Init*Sep 15 09:14:53.691: GLBP: Et0/0 Grp 1 HA sync, state Standby -> InitThe following is sample output from the debug glbp events command when the cache keyword is specified:
Router# debug glbp events cacheGLBP Events debugging is on (cache)Jun 30 08:57:50.171: GLBP: Et0/0 1 Added client cache entry for 7bcf.e03d.d3bdJun 30 08:57:50.171: GLBP: Et0/0 1 Added client cache entry for c5e8.46eb.8a86Jun 30 08:57:50.171: GLBP: Et0/0 1 Added client cache entry for 69e5.9d95.0f7eJun 30 08:57:50.171: GLBP: Et0/0 1 Added client cache entry for 986e.d98a.1607Jun 30 08:57:50.171: GLBP: Et0/0 1 Added client cache entry for 1843.ee62.f62eJun 30 08:57:50.171: GLBP: Et0/0 1 Added client cache entry for 5f4c.cfc4.5dc1Related Commands
debug condition glbp
Displays debugging messages about GLBP that match specific conditions.
debug glbp packets
To display summary information about Gateway Load Balancing Protocol (GLBP) packets being sent or received, use the debug glbp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp packets [all | detail | hello | reply | request | terse]
no debug glbp packets [all | detail | hello | reply | request | terse]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug glbp packets command shows debugging output about GLBP hello packets:
Router# debug glbp packets helloGLBP Packets debugging is on(Hello)1d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 11d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 11d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 11d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 1Related Commands
debug condition glbp
Displays debugging messages about GLBP that match specific conditions.
debug glbp terse
To display a limited range of debugging messages about Gateway Load Balancing Protocol (GLBP) errors, events, and packets, use the debug glbp terse command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp terse
no debug glbp terse
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug glbp terse command:
Router# debug glbp terseGLBP:GLBP Errors debugging is onGLBP Events debugging is on(protocol, redundancy, track)GLBP Packets debugging is on(Request, Reply)Related Commands
debug ip bgp sso
To display Border Gateway Protocol (BGP)-related stateful switchover (SSO) events or debugging information for BGP-related interactions between the active Route Processor (RP) and the standby RP, use the debug ip bgp sso command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip bgp sso {events | transactions} [detail]
no debug ip bgp sso {events | transactions} [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(28)SB
This command was introduced.
12.2(33)SRB1
This command was integrated into Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
The debug ip bgp sso command is used to display BGP-related SSO events or debugging information for BGP-related interactions between the active RP and the standby RP. This command is useful for monitoring or troubleshooting BGP sessions on a provider edge (PE) router during an RP switchover or during a planned In-Service Software Upgrade (ISSU).
Examples
The following is sample output from the debug ip bgp sso command with the events keyword. The following output indicates that the 10.34.32.154 BGP session is no longer SSO capable.
*Mar 28 02:29:43.526: BGPSSO: 10.34.32.154 reset SSO and decrement count
Tip
The following is sample output from the debug ip bgp sso command with the transactions keyword. The following output shows an SSO notification indicating that the SSO capability is pending for 602 BGP neighbors. This notification is generated as the state between the active and standby RP is being synchronized during the bulk synchonization phase of SSO initialization. During this phase, the Transmission Control Blocks (TCBs) must be synchronized with the TCBs on the standby RP before SSO initialization is complete.
*Mar 28 02:32:12.102: BGPSSO: tcp sso notify pending for 602 nbrsdebug ip bgp vpnv4 checkpoint
To display the events for the Virtual Routing and Forwarding (VRF) checkpointing system between the active and standby Route Processors, use the debug ip bgp vpnv4 checkpoint command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug ip bgp vpnv4 checkpoint
no debug ip bgp vpnv4 checkpoint
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows command output on the active Route Processor:
Router# debug ip bgp vpnv4 checkpoint3d18h: %HA-5-SYNC_NOTICE: Config sync started.3d18h: vrf-nsf: vrf vpn2 tableid 1 send OK3d18h: vrf-nsf: vrf tableid bulk sync complete msg send OK3d18h: vrf-nsf: CF send ok3d18h: vrf-nsf: CF send ok3d18h: %HA-5-SYNC_NOTICE: Config sync completed.3d18h: %HA-5-SYNC_NOTICE: Standby has restarted.3d18h: %HA-5-MODE: Operating mode is sso, configured mode is sso.Related Commands
debug ip bgp vpnv4 nsf
Displays the nonstop forwarding events for the VRF table-id synchronization subsystem between the active and standby route processors.
debug ip bgp vpnv4 nsf
To display the nonstop forwarding events for the VRF table-id synchronization subsystem between the active and standby Route Processors, use the debug ip bgp vpnv4 nsf command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug ip bgp vpnv4 nsf
no debug ip bgp vpnv4 nsf
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the command output on the active Route Processor:
Router# debug ip bgp vpnv4 nsfMPLS VPN NSF Processing debugging is onRouter(config)# ip vrf vpn33d18h: vrf-nsf: vrf vpn3 tableid 2 send rpc OKRouter(config-vrf)# no ip vrf vpn3% IP addresses from all interfaces in VRF vpn3 have been removed3d18h: vrf-nsf: rx vrf tableid delete complete msg, tid = 2, name = vpn3The following example shows the command output on the standby Route Processor:
Router# debug ip bgp vpnv4 nsfMPLS VPN NSF Processing debugging is on00:05:21: vrf-nsf: rx vrf tableid rpc msg, tid = 2, name = vpn3% IP addresses from all interfaces in VRF vpn3 have been removed00:06:22: vrf-nsf: vrf vpn3 tableid 2 , delete complete, send OKRelated Commands
debug ip bgp vpnv4 checkpoint
Display the events for the VRF checkpointing system between the active and standby Route Processors.
debug ip dhcp server redundancy
To display debugging information about DHCP server and relay agent redundancy events, use the debug ip dhcp server redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug ip dhcp server redundancy
no debug ip dhcp server redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging output is disabled for DHCP server and relay agent redundancy events.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command with caution. Many bindings being synchronized between the active and standby Route Processor (RP) can trigger a large amount of debugging output.
Examples
The following example displays debug messages regarding DHCP server and relay agent redundancy events. The last line (and only that line) is output when the debug ip dhcp server redundancy command is enabled. The line indicates that a binding update message has been sent to the standby for the IP address 10.0.0.2 in the pool named "test."
Router# debug ip dhcp server redundancy*Mar 22 10:32:21: DHCPD: assigned IP address 10.0.0.2 to client 0063.6973.636f.2d30.3030.342e.3465.6130.2e30.3831.632d.4661.312f.302e.31.*Mar 22 10:32:21: DHCPD: lease time = 3600*Mar 22 10:32:21: DHCPD: dhcpd_lookup_route: host = 10.0.0.2*Mar 22 10:32:21: DHCPD: dhcpd_lookup_route: index = 0*Mar 22 10:32:21: DHCPD: dhcpd_create_and_hash_route: host = 10.0.0.2*Mar 22 10:32:21: DHCPD: dhcpd_create_and_hash_route index = 0*Mar 22 10:32:21: DHCPD: dhcpd_add_route: lease = 3600*Mar 22 10:32:21: DHCPD: dynamic sync completed for 10.0.0.2 in pool testRelated Commands
debug dhcp redundancy
Displays debugging information about DHCP proxy client redundancy events.
debug ip eigrp notifications
To display Enhanced Interior Gateway Routing Protocol (EIGRP) events and notifications in the console of the router, use the debug ip eigrp notifications command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip eigrp notifications
no debug ip eigrp notifications
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The output of the debug ip eigrp notifications command displays EIGRP events and notifications.
Examples
The following example output shows that the NSF-aware router has received the restart notification. The NSF-aware router will now wait for end of transmission (EOT) to be sent from the restarting neighbor (NSF-capable).
Router# debug ip eigrp notifications*Oct 4 11:39:18.092:EIGRP:NSF:AS2. Rec RS update from 135.100.10.1,00:00:00. Wait for EOT.*Oct 4 11:39:18.092:%DUAL-5-NBRCHANGE:IP-EIGRP(0) 2:Neighbor135.100.10.1 (POS3/0) is up:peer NSF restarteddebug ip mrouting
To display information about activity in the multicast route (mroute) table, use the debug ip mrouting command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip mrouting [vrf vrf-name] [rpf-events | timers] [group-address]
no debug ip mrouting [vrf vrf-name] [rpf-events | timers] [group-address]
Command Syntax in Cisco IOS 12.2(33)SXH and Subsequent 12.2SX Releases
debug ip mrouting [vrf vrf-name] [high-availability | rpf-events [group-address] | timers group-address]
no debug ip mrouting [vrf vrf-name] [high-availability | rpf-events [group-address] | timers group-address]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command indicates when the router has made changes to the mroute table. Use the debug ip pim and debug ip mrouting commands consecutively to obtain additional multicast routing information. In addition, use the debug ip igmp command to learn why an mroute message is being displayed.
This command generates a substantial amount of output. Use the optional group-address argument to limit the output to a single multicast group.
In Cisco IOS 12.2(33)SXH and subsequent 12.2SX releases, the high-availability keyword was added in support of the PIM Triggered Joins feature to monitor HA events in the event of a supervisor engine switchover on a Catalyst 6500 series switch. The PIM Triggered Joins feature is an HA multicast enhancement that improves the reconvergence of mroutes after a supervisor engine switchover on a Catalyst 6500 series switch. After a service engine switchover, all instances of PIM running on the newly active supervisor engine will modify the value of the Generation ID (GenID) that is included in PIM hello messages sent to adjacent PIM neighbors. When an adjacent PIM neighbor receives a PIM hello message on an interface with a new GenID, the PIM neighbor will interpret the modified GenID as an indication that all mroutes states on that interface have been lost. A modified GenID, thus, is utilized as a mechanism to alert all adjacent PIM neighbors that PIM forwarding on that interface has been lost, which then triggers adjacent PIM neighbors to send PIM joins for all (*, G) and (S, G) mroute states that use that interface as an RPF interface.
Examples
The following is sample output from the debug ip mrouting command:
Router# debug ip mrouting 224.2.0.1MRT: Delete (10.0.0.0/8, 224.2.0.1)MRT: Delete (10.4.0.0/16, 224.2.0.1)MRT: Delete (10.6.0.0/16, 224.2.0.1)MRT: Delete (10.9.0.0/16, 224.2.0.1)MRT: Delete (10.16.0.0/16, 224.2.0.1)MRT: Create (*, 224.2.0.1), if_input NULLMRT: Create (224.69.15.0/24, 225.2.2.4), if_input Ethernet0, RPF nbr 224.69.61.15MRT: Create (224.69.39.0/24, 225.2.2.4), if_input Ethernet1, RPF nbr 0.0.0.0MRT: Create (10.0.0.0/8, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.4.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.6.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.9.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.16.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0The following lines show that multicast IP routes were deleted from the routing table:
MRT: Delete (10.0.0.0/8, 224.2.0.1)MRT: Delete (10.4.0.0/16, 224.2.0.1)MRT: Delete (10.6.0.0/16, 224.2.0.1)The (*, G) entries are generally created by receipt of an Internet Group Management Protocol (IGMP) host report from a group member on the directly connected LAN or by a Protocol Independent Multicast (PIM) join message (in sparse mode) that this router receives from a router that is sending joins toward the Route Processor (RP). This router will in turn send a join toward the RP that creates the shared tree (or RP tree).
MRT: Create (*, 224.2.0.1), if_input NULLThe following lines are an example of creating an (S, G) entry that shows that an IP multicast packet (mpacket) was received on Ethernet interface 0. The second line shows a route being created for a source that is on a directly connected LAN. The RPF means "Reverse Path Forwarding," whereby the router looks up the source address of the multicast packet in the unicast routing table and determines which interface will be used to send a packet to that source.
MRT: Create (224.69.15.0/24, 225.2.2.4), if_input Ethernet0, RPF nbr 224.69.61.15MRT: Create (224.69.39.0/24, 225.2.2.4), if_input Ethernet1, RPF nbr 0.0.0.0The following lines show that multicast IP routes were added to the routing table. Note the 224.0.0.0 as the RPF, which means the route was created by a source that is directly connected to this router.
MRT: Create (10.9.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0MRT: Create (10.16.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 224.0.0.0If the source is not directly connected, the neighbor address shown in these lines will be the address of the router that forwarded the packet to this router.
The shortest path tree state maintained in routers consists of source (S), multicast address (G), outgoing interface (OIF), and incoming interface (IIF). The forwarding information is referred to as the multicast forwarding entry for (S, G).
An entry for a shared tree can match packets from any source for its associated group if the packets come through the proper incoming interface as determined by the RPF lookup. Such an entry is denoted as
(*, G). A (*, G) entry keeps the same information a (S, G) entry keeps, except that it saves the rendezvous point address in place of the source address in sparse mode or as 24.0.0.0 in dense mode.Table 15 describes the significant fields shown in the display.
Table 15 debug ip mrouting Field Descriptions
MRT
Multicast route table.
RPF
Reverse Path Forwarding.
nbr
Neighbor.
Related Commands
debug ip multicast redundancy
To display information about IP multicast redundancy events, use the debug ip multicast redundancy command in privileged EXEC mode. To disable debugging output for IP multicast redundancy events, use the no form of this command.
debug ip multicast [default-vrf | vrf vrf-name] [group group-address] redundancy [verbose]
no debug ip multicast [default-vrf | vrf vrf-name] [group group-address] redundancy [verbose]
Syntax Description
Command Default
IP multicast events related to all multicast groups and all MVRFs are displayed. Logging events enabled with the verbose keyword are not displayed.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SXI
This command was introduced.
12.2(33)SRE
This command was integrated into Cisco IOS Release 12.2(33)SRE.
Usage Guidelines
Use this command to display IP multicast redundancy events.
This command logs events that are important in verifying nonstop forwarding (NSF) with stateful switchover (SSO) for IP multicast. The classes of events logged by debug ip multicast redundancy command include stateful switchover events during a Route Processor (RP) switchover and dynamic synchronization events that occur during steady state operation.
Use the optional verbose keyword to log events that may occur very frequently during normal operation, but which may be useful for tracking in short intervals.
Examples
The following output is from the debug ip multicast redundancy command. The output shows the initial logging messages that display when the system detects an RP switchover.
00:10:33: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_DOWN_INTERRUPT)00:10:33: %REDUNDANCY-5-PEER_MONITOR_EVENT: Standby received a switchover (raw-event=PEER_DOWN_INTERRUPT(11))*Aug 7 02:31:28.051: MCAST-HA: Received cf status CHKPT_STATUS_PEER_NOT_READY*Aug 7 02:31:28.063: MCAST-HA: Received cf status CHKPT_STATUS_PEER_NOT_READY*Aug 7 02:31:28.063: MCAST-HA-RF: Status event: status=RF_STATUS_PEER_COMM Op=0 RFState=STANDBY HOT*Aug 7 02:31:28.063: MCAST-HA-RF: Status event: status=RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE Op=0 RFState=STANDBY HOT*Aug 7 02:31:28.063: MCAST-HA-RF: Status event: status=RF_STATUS_REDUNDANCY_MODE_CHANGE Op=0 RFState=STANDBY HOT*Aug 7 02:31:28.063: MCAST-HA-RF: Status event: status=RF_STATUS_PEER_PRESENCE Op=0 RFState=STANDBY HOT*Aug 7 02:31:28.063: MCAST-HA-RF: Status event: status=RF_STATUS_MAINTENANCE_ENABLE Op=0 RFState=ACTIVE-FAST*Aug 7 02:31:28.063: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_ACTIVE_FAST RFState=ACTIVE-FAST*Aug 7 02:31:28.091: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_ACTIVE_DRAIN RFState=ACTIVE-DRAIN*Aug 7 02:31:28.091: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_ACTIVE_PRECONFIG RFState=ACTIVE_PRECONFIG*Aug 7 02:31:28.091: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_ACTIVE_POSTCONFIG RFState=ACTIVE_POSTCONFIG*Aug 7 02:31:28.103: MCAST-HA: Received cf status CHKPT_STATUS_IPC_FLOW_ON*Aug 7 02:31:28.103: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_ACTIVE RFState=ACTIVEThe following output is from the debug ip multicast redundancy command. As interfaces come up on the new active RP, unicast convergence occurs in parallel with multicast route refresh from Protocol Independent Multicast (PIM) neighbors. Unicast convergence is followed by Reverse Path Forwarding (RPF) adjustments to the refreshed mroute information.
*Aug 7 02:31:28.107: MCAST-HA: Triggering unicast convergence notification process handling for MVRF IPv4 default*Aug 7 02:31:28.107: MCAST-HA: Triggering unicast convergence notification process handling for MVRF blue*Aug 7 02:31:28.107: MCAST-HA: Triggering unicast convergence notification process handling for MVRF green*Aug 7 02:31:28.107: MCAST-HA: Triggering unicast convergence notification process handling for MVRF red*Aug 7 02:31:28.107: MCAST-HA: Triggering unicast convergence notification process handling for all MVRFs*Aug 7 02:31:28.111: MCAST-HA: Beginning unicast convergence notification process handling.*Aug 7 02:31:28.111: MCAST-HA: Unicast convergence completed for MVRF IPv4 default: Triggering RPF updates*Aug 7 02:31:28.111: MCAST-HA: Beginning unicast convergence notification process handling.*Aug 7 02:31:28.111: MCAST-HA: Unicast convergence completed for MVRF blue: Triggering RPF updates*Aug 7 02:31:28.111: MCAST-HA: Beginning unicast convergence notification process handling.*Aug 7 02:31:28.111: MCAST-HA: Unicast convergence completed for MVRF green: Triggering RPF updates*Aug 7 02:31:28.111: MCAST-HA: Beginning unicast convergence notification process handling.*Aug 7 02:31:28.111: MCAST-HA: Unicast convergence completed for MVRF red: Triggering RPF updates*Aug 7 02:31:28.111: MCAST-HA: Unicast convergence notification has been received for the only unconverged VRF.Stopping the unicast routing convergence failsafe timer.*Aug 7 02:31:28.111: MCAST-HA: Beginning unicast convergence notification process handling.*Aug 7 02:31:28.111: MCAST-HA: Unicast convergence notification received for the wildcard tableid (all VRFs).Triggering RPF updates for all MVRFs and stopping the unicast IGP convergence failsafe timer.00:10:34: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 172.16.1.1 on interface Loopback000:10:34: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 172.31.10.1 on interface Loopback100:10:35: %PIM-5-DRCHG: VRF green: DR change from neighbor 0.0.0.0 to 172.16.1.1 on interface Tunnel100:10:35: %PIM-5-DRCHG: VRF red: DR change from neighbor 0.0.0.0 to 172.16.1.1 on interface Tunnel200:10:35: %LINK-3-UPDOWN: Interface Null0, changed state to up00:10:35: %LINK-3-UPDOWN: Interface Loopback0, changed state to up00:10:35: %LINK-3-UPDOWN: Interface Loopback1, changed state to up00:10:35: %LINK-3-UPDOWN: Interface Tunnel0, changed state to up00:10:35: %LINK-3-UPDOWN: Interface Tunnel1, changed state to up00:10:35: %LINK-3-UPDOWN: Interface Tunnel2, changed state to up00:10:35: %LINK-5-CHANGED: Interface Ethernet0/0, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet0/1, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet0/2, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet0/3, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet1/0, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet1/1, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet1/2, changed state to administratively down00:10:35: %LINK-5-CHANGED: Interface Ethernet1/3, changed state to administratively down00:10:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, changed state to up00:10:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up00:10:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback1, changed state to up00:10:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up00:10:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel1, changed state to up00:10:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel2, changed state to up00:10:38: %PIM-5-DRCHG: VRF blue: DR change from neighbor 0.0.0.0 to 172.16.1.1 on interface Tunnel0The following output is from the debug ip multicast redundancy command. After the processing of unicast and multicast route convergence, time is allowed for IGMP reporting. Following Internet Group Management Protocol (IGMP) reporting, the control plane then sends out requests for the Multicast Forwarding Information Base (MFIB) replay of data driven events (DDEs) to retrigger multicast route information that cannot be obtained from PIM neighbors or directly connected hosts. After this processing completes, the control plane waits for the NSF holdoff time period to terminate. The refreshed multicast control plane information is then downloaded to the forwarding plane; once completed, the stale multicast forwarding plane information is subsequently flushed.
*Aug 7 02:31:43.651: MCAST-HA: IGMP response timer expired. Ready for DDE replay for MVRF red*Aug 7 02:31:43.651: MCAST-HA: Sending DDE replay request for MVRF red.*Aug 7 02:31:43.651: MCAST-HA: MFIB DDE replay completed for mvrf red*Aug 7 02:31:43.651: MCAST-HA: No NSF Holdoff extension requested for mvrf red at completion of DDE replay.*Aug 7 02:31:43.651: MCAST-HA: Terminating multicast NSF holdoff for MVRF red*Aug 7 02:31:43.651: MCAST-HA: Still awaiting MFIB DDE replay for mvrf greenDDE replay: NOT COMPLETED, MRIB update: NOT PENDING*Aug 7 02:31:43.651: MCAST-HA: IGMP response timer expired. Ready for DDE replay for MVRF green*Aug 7 02:31:43.651: MCAST-HA: Sending DDE replay request for MVRF green.*Aug 7 02:31:43.651: MCAST-HA: MFIB DDE replay completed for mvrf green*Aug 7 02:31:43.651: MCAST-HA: No NSF Holdoff extension requested for mvrf green at completion of DDE replay.*Aug 7 02:31:43.651: MCAST-HA: Terminating multicast NSF holdoff for MVRF green*Aug 7 02:31:43.651: MCAST-HA: Still awaiting MFIB DDE replay for mvrf blueDDE replay: NOT COMPLETED, MRIB update: NOT PENDING*Aug 7 02:31:43.651: MCAST-HA: IGMP response timer expired. Ready for DDE replay for MVRF blue*Aug 7 02:31:43.651: MCAST-HA: Sending DDE replay request for MVRF blue.*Aug 7 02:31:43.651: MCAST-HA: MFIB DDE replay completed for mvrf blue*Aug 7 02:31:43.651: MCAST-HA: No NSF Holdoff extension requested for mvrf blue at completion of DDE replay.*Aug 7 02:31:43.651: MCAST-HA: Terminating multicast NSF holdoff for MVRF blue*Aug 7 02:31:43.651: MCAST-HA: Still awaiting MFIB DDE replay for mvrf IPv4 defaultDDE replay: NOT COMPLETED, MRIB update: NOT PENDING*Aug 7 02:31:43.651: MCAST-HA: IGMP response timer expired. Ready for DDE replay for MVRF IPv4 default*Aug 7 02:31:43.651: MCAST-HA: Sending DDE replay request for MVRF IPv4 default.*Aug 7 02:31:43.651: MCAST-HA: MFIB DDE replay completed for mvrf IPv4 default*Aug 7 02:31:43.651: MCAST-HA: No NSF Holdoff extension requested for mvrf IPv4 default at completion of DDE replay.*Aug 7 02:31:43.651: MCAST-HA: Terminating multicast NSF holdoff for MVRF IPv4 default*Aug 7 02:31:43.651: MCAST-HA: MFIB DDE replay completed for all MVRFs.*Aug 7 02:31:43.651: MCAST-HA: Stopping the MFIB DDE replay failsafe timer.*Aug 7 02:32:13.651: MCAST-HA: Flush timer expired. Starting final RPF check for MVRF IPv4 default*Aug 7 02:32:13.651: MCAST-HA: Flush timer expired. Starting final RPF check for MVRF blue*Aug 7 02:32:13.651: MCAST-HA: Flush timer expired. Starting final RPF check for MVRF green*Aug 7 02:32:13.651: MCAST-HA: Flush timer expired. Starting final RPF check for MVRF red*Aug 7 02:32:14.151: MCAST-HA: Flushing stale mcast state. RP failover processing complete for MVRF IPv4 default.*Aug 7 02:32:14.151: MCAST-HA: Flushing stale mcast state. RP failover processing complete for MVRF blue.*Aug 7 02:32:14.151: MCAST-HA: Flushing stale mcast state. RP failover processing complete for MVRF green.*Aug 7 02:32:14.151: MCAST-HA: Flushing stale mcast state. RP failover processing complete for MVRF red.*Aug 7 02:32:14.151: MCAST-HA: RP failover processing complete for all MVRFs.The following is sample output from the debug ip multicast redundancy command. This output shows the events related to the reloading of the standby RP, in particular, ISSU negotiation between the active and standby RP and synchronization of dynamic multicast forwarding information from the active RP to the standby RP. Synchronization events are also logged in steady state for events that occur which affect dynamic group-to-RP mapping information or dynamic tunnel state.
00:11:50: %HA-6-MODE: Operating RP redundancy mode is SSO*Aug 7 02:32:45.435: MCAST-HA-RF: Status event: status=RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE Op=7 RFState=ACTIVE*Aug 7 02:32:45.435: MCAST-HA-RF: Status event: status=RF_STATUS_REDUNDANCY_MODE_CHANGE Op=7 RFState=ACTIVE*Aug 7 02:32:45.435: MCAST-HA-RF: Status event: status=RF_STATUS_PEER_PRESENCE Op=1 RFState=ACTIVE*Aug 7 02:32:45.463: MCAST-HA-RF: Status event: status=RF_STATUS_PEER_COMM Op=1 RFState=ACTIVE*Aug 7 02:32:45.563: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_ISSU_NEGOTIATION RFState=ACTIVE*Aug 7 02:32:46.039: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_PLATFORM_SYNC RFState=ACTIVE*Aug 7 02:32:46.979: MCAST-HA: Received cf status CHKPT_STATUS_PEER_READY*Aug 7 02:32:46.979: MCAST-ISSU Handling communication up transition for PIM HA transport type 0, RF comm = TRUE, renegotiation NOT PENDING*Aug 7 02:32:46.979: MCAST-HA: Received cf status CHKPT_STATUS_IPC_FLOW_ON*Aug 7 02:32:47.043: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_STANDBY_ISSU_NEGOTIATION_LATE RFState=ACTIVE*Aug 7 02:32:50.943: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_STANDBY_CONFIG RFState=ACTIVE*Aug 7 02:32:50.947: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.947: MCAST-HA-RF: Started PIM ISSU negotiation on the primary RP.*Aug 7 02:32:50.947: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.947: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.951: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.951: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.951: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.951: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.955: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.955: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.955: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.955: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.959: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.959: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.959: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.959: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.959: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.963: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.963: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.963: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.963: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.967: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.967: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.967: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.967: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.967: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.971: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.971: MCAST-ISSU Negotiation message sent from primary, rc = 0*Aug 7 02:32:50.971: MCAST-ISSU Negotiation completed for PIM Checkpoint Facility client, negotiation rc = 4, negotiation result = COMPATIBLE*Aug 7 02:32:59.927: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_STANDBY_FILESYS RFState=ACTIVE*Aug 7 02:32:59.963: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_STANDBY_BULK RFState=ACTIVE*Aug 7 02:32:59.963: MCAST-HA-RF: Starting Bulk Sync.*Aug 7 02:32:59.963: MCAST-HA: Successfully created the bulk sync process*Aug 7 02:32:59.963: MCAST-HA: Starting Bulk sync*Aug 7 02:32:59.963: MCAST HA Executing RP mapping bulk sync.*Aug 7 02:32:59.963: MCAST HA Executing Bidir RP route bulk sync.*Aug 7 02:32:59.963: MCAST HA Executing BSR cache bulk sync.*Aug 7 02:32:59.963: MCAST-HA BSR cache sync request received for mvrf IPv4 default*Aug 7 02:32:59.963: MCAST-HA: Creating Bootstrap cache sync request chunk size=112 max=585 align=8*Aug 7 02:32:59.963: MCAST-HA: Allocating Bootstrap cache sync request sync request*Aug 7 02:32:59.963: MCAST-HA Formatting BSR cache sync message:search for mvrf IPv4 default result is 0 mvrf at 0x4A21680*Aug 7 02:32:59.971: MCAST-HA BSR cache sync request received for mvrf blue*Aug 7 02:32:59.971: MCAST-HA: Allocating Bootstrap cache sync request sync request*Aug 7 02:32:59.971: MCAST-HA Formatting BSR cache sync message:search for mvrf blue result is 0 mvrf at 0x50EE660*Aug 7 02:32:59.983: MCAST-HA BSR cache sync request received for mvrf green*Aug 7 02:32:59.983: MCAST-HA: Allocating Bootstrap cache sync request sync request*Aug 7 02:32:59.983: MCAST-HA Formatting BSR cache sync message:search for mvrf green result is 0 mvrf at 0x5103300*Aug 7 02:32:59.991: MCAST-HA BSR cache sync request received for mvrf red*Aug 7 02:32:59.991: MCAST-HA: Allocating Bootstrap cache sync request sync request*Aug 7 02:32:59.991: MCAST-HA Formatting BSR cache sync message:search for mvrf red result is 0 mvrf at 0x5135FE0*Aug 7 02:33:00.003: MCAST HA Executing AutoRP discovery IDB bulk sync.*Aug 7 02:33:00.003: MCAST-HA AutoRP discovery IDB sync request received formvrf IPv4 default*Aug 7 02:33:00.003: MCAST-HA: Creating Autorp discovery IDB sync request chunk size=112 max=585 align=8*Aug 7 02:33:00.003: MCAST-HA: Allocating Autorp discovery IDB sync request sync request*Aug 7 02:33:00.003: MCAST-HA Formatting AutoRP discovery IDB sync message:search for mvrf IPv4 default result is 0 mvrf at 0x4A21680*Aug 7 02:33:00.011: MCAST-HA AutoRP discovery IDB sync request received formvrf blue*Aug 7 02:33:00.011: MCAST-HA: Allocating Autorp discovery IDB sync request sync request*Aug 7 02:33:00.011: MCAST-HA Formatting AutoRP discovery IDB sync message:search for mvrf blue result is 0 mvrf at 0x50EE660*Aug 7 02:33:00.023: MCAST-HA AutoRP discovery IDB sync request received formvrf green*Aug 7 02:33:00.023: MCAST-HA: Allocating Autorp discovery IDB sync request sync request*Aug 7 02:33:00.023: MCAST-HA Formatting AutoRP discovery IDB sync message:search for mvrf green result is 0 mvrf at 0x5103300*Aug 7 02:33:00.031: MCAST-HA AutoRP discovery IDB sync request received formvrf red*Aug 7 02:33:00.031: MCAST-HA: Allocating Autorp discovery IDB sync request sync request*Aug 7 02:33:00.031: MCAST-HA Formatting AutoRP discovery IDB sync message:search for mvrf red result is 0 mvrf at 0x5135FE0*Aug 7 02:33:00.043: MCAST HA Executing dummy bulk sync function.*Aug 7 02:33:00.043: MCAST HA Executing dummy bulk sync function.*Aug 7 02:33:00.043: MCAST HA Executing dummy bulk sync function.*Aug 7 02:33:00.043: MCAST HA Executing MDT tunnel bulk sync.*Aug 7 02:33:00.043: MCAST-HA MDT tunnel sync request received for mvrf blue*Aug 7 02:33:00.043: MCAST-HA: Creating MDT tunnel sync request chunk size=112 max=585 align=8*Aug 7 02:33:00.043: MCAST-HA: Allocating MDT tunnel sync request sync request*Aug 7 02:33:00.043: MCAST-HA Formatting MDT tunnel sync message:search for mvrf blue result is 0 mvrf at 0x50EE660*Aug 7 02:33:00.051: MCAST-HA MDT tunnel sync request received for mvrf green*Aug 7 02:33:00.051: MCAST-HA: Allocating MDT tunnel sync request sync request*Aug 7 02:33:00.051: MCAST-HA Formatting MDT tunnel sync message:search for mvrf green result is 0 mvrf at 0x5103300*Aug 7 02:33:00.063: MCAST-HA MDT tunnel sync request received for mvrf red*Aug 7 02:33:00.063: MCAST-HA: Allocating MDT tunnel sync request sync request*Aug 7 02:33:00.063: MCAST-HA Formatting MDT tunnel sync message:search for mvrf red result is 0 mvrf at 0x5135FE0*Aug 7 02:33:00.071: MCAST HA Executing Bidir RP DF bulk sync.*Aug 7 02:33:00.071: MCAST HA Executing register tunnel bulk sync.*Aug 7 02:33:00.071: MCAST-HA: Completed enqueuing of bulk sync messages.*Aug 7 02:33:00.071: MCAST-HA: Bulk sync message queue has drained.*Aug 7 02:33:00.071: MCAST-HA: Received acknowledgement from standby for all bulk sync messages.*Aug 7 02:33:00.071: MCAST-HA Creating bulk sync completion message for peer.*Aug 7 02:33:00.071: MCAST-HA: Primary has notified standby of bulk sync completion. Waiting for final bulk sync ACK from stby.*Aug 7 02:33:00.075: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.075: MCAST-HA: Sent message type is 2*Aug 7 02:33:00.075: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.075: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 2. Cleanup is complete.*Aug 7 02:33:00.075: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.075: MCAST-HA: Sent message type is 2*Aug 7 02:33:00.075: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.075: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 2. Cleanup is complete.*Aug 7 02:33:00.075: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.075: MCAST-HA: Sent message type is 2*Aug 7 02:33:00.075: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.075: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 2. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 2*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 2. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 3*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 3. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 3*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 3. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 3*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 3. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 3*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 3. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 8*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 8. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 8*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 8. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 8*Aug 7 02:33:00.087: MCAST-HA Searching for sync request corresponding to the successfully received message.*Aug 7 02:33:00.087: MCAST-HA Transmission from primary and reception by standby confirmed for sync type 8. Cleanup is complete.*Aug 7 02:33:00.087: MCAST-HA: Received cf status CHKPT_STATUS_SEND_OK*Aug 7 02:33:00.087: MCAST-HA: Sent message type is 11*Aug 7 02:33:00.087: MCAST-HA Process: Primary RP received standby ACK for reception of bulk sync completion message.*Aug 7 02:33:00.087: MCAST-HA Notifying RF to continue progression.*Aug 7 02:33:00.087: MCAST-HA: Wakeup received for bulk sync completion.major = 4, minor = 2.*Aug 7 02:33:00.091: MCAST-HA Process: Primary RP received bulk sync completion confirmation from standby.*Aug 7 02:33:00.091: MCAST-HA RF notification previously sent.*Aug 7 02:33:00.455: MCAST-HA-RF: Progression event: RF_Event=RF_PROG_STANDBY_HOT RFState=ACTIVE00:12:05: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded00:12:05: %HA-6-STANDBY_READY: Standby RP in slot 7 is operational in SSO mode00:12:05: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)debug ip ospf nsf
To display debugging messages about Open Shortest Path First (OSPF) during a Cisco nonstop forwarding (NSF) restart, use the debug ip ospf nsf command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug ip ospf nsf [detail]
no debug ip ospf nsf [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug ip ospf nsf command to diagnose problems with OSPF link-state database (LSDB) resynchronization and NSF operations.
Examples
The following example shows that OSPF NSF events debugging is enabled:
Router# debug ip ospf nsfRelated Commands
debug ip pim
To display Protocol Independent Multicast (PIM) packets received and sent, and to display PIM-related events, use the debug ip pim command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip pim [vrf vrf-name] [group-address | atm | auto-rp | bsr | df [rp-address] | hello | tag]
no debug ip pim [vrf vrf-name] [group-address | atm | auto-rp | bsr | df [rp-address] | hello | tag]
Syntax Description
Defaults
All PIM packets are displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
PIM uses Internet Group Management Protocol (IGMP) packets to communicate with routers and advertise reachability information.
Use this command with the debug ip igmp and debug ip mrouting commands to display additional multicast routing information.
Examples
The following is sample output from the debug ip pim command:
Router# debug ip pim 224.2.0.1PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Tunnel0 from 10.3.84.1PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received RP-Reachable on Ethernet1 from 172.16.20.31PIM: Update RP expiration timer for 224.2.0.1PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Prune-list (10.221.196.51/32, 224.2.0.1)PIM: Set join delay timer to 2 seconds for (10.221.0.0/16, 224.2.0.1) on Ethernet1PIM: Received Join/Prune on Ethernet1 from 172.16.37.6PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Tunnel0 from 10.3.84.1PIM: Join-list: (*, 224.2.0.1) RP 172.16.20.31PIM: Add Tunnel0 to (*, 224.2.0.1), Forward statePIM: Join-list: (10.0.0.0/8, 224.2.0.1)PIM: Add Tunnel0 to (10.0.0.0/8, 224.2.0.1), Forward statePIM: Join-list: (10.4.0.0/16, 224.2.0.1)PIM: Prune-list (172.16.84.16/28, 224.2.0.1) RP-bit set RP 172.16.84.16PIM: Send Prune on Ethernet1 to 172.16.37.6 for (172.16.84.16/28, 224.2.0.1), RPPIM: For RP, Prune-list: 10.9.0.0/16PIM: For RP, Prune-list: 10.16.0.0/16PIM: For RP, Prune-list: 10.49.0.0/16PIM: For RP, Prune-list: 10.84.0.0/16PIM: For RP, Prune-list: 10.146.0.0/16PIM: For 10.3.84.1, Join-list: 172.16.84.16/28PIM: Send periodic Join/Prune to RP via 172.16.37.6 (Ethernet1)The following lines appear periodically when PIM is running in sparse mode and indicate to this router the multicast groups and multicast sources in which other routers are interested:
PIM: Received Join/Prune on Ethernet1 from 172.16.37.33PIM: Received Join/Prune on Ethernet1 from 172.16.37.33The following lines appear when a rendezvous point (RP) message is received and the RP timer is reset. The expiration timer sets a checkpoint to make sure the RP still exists. Otherwise, a new RP must be discovered.
PIM: Received RP-Reachable on Ethernet1 from 172.16.20.31PIM: Update RP expiration timer for 224.2.0.1PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0The prune message in the following line states that this router is not interested in the Source-Active (SA) information. This message tells an upstream router to stop forwarding multicast packets from this source. The address 10.221.196.51/32 indicates a host route with 32 bits of mask.
PIM: Prune-list (10.221.196.51/32, 224.2.0.1)In the following line, a second router on the network wants to override the prune message that the upstream router just received. The timer is set at a random value so that if additional routers on the network still want to receive multicast packets for the group, only one will actually send the message. The other routers will receive the join message and then suppress sending their own message.
PIM: Set join delay timer to 2 seconds for (10.221.0.0/16, 224.2.0.1) on Ethernet1In the following line, a join message is sent toward the RP for all sources:
PIM: Join-list: (*, 224.2.0.1) RP 172.16.20.31In the following lines, the interface is being added to the outgoing interface (OIF) of the (*, G) and
(S, G) multicast route (mroute) table entry so that packets from the source will be forwarded out that particular interface:PIM: Add Tunnel0 to (*, 224.2.0.1), Forward statePIM: Add Tunnel0 to (10.0.0.0/8, 224.2.0.1), Forward stateThe following line appears in sparse mode only. There are two trees on which data may be received: the RP tree and the source tree. In dense mode there is no RP. After the source and the receiver have discovered one another at the RP, the first-hop router for the receiver will usually join to the source tree rather than the RP tree.
PIM: Prune-list (172.16.84.16/28, 224.2.0.1) RP-bit set RP 172.16.84.16The send prune message in the next line shows that a router is sending a message to a second router saying that the first router should no longer receive multicast packets for the (S, G). The RP at the end of the message indicates that the router is pruning the RP tree and is most likely joining the source tree, although the router may not have downstream members for the group or downstream routers with members of the group. The output shows the specific sources from which this router no longer wants to receive multicast messages.
PIM: Send Prune on Ethernet1 to 172.16.37.6 for (172.16.84.16/28, 224.2.0.1), RPThe following lines indicate that a prune message is sent toward the RP so that the router can join the source tree rather than the RP tree:
PIM: For RP, Prune-list: 10.9.0.0/16PIM: For RP, Prune-list: 10.16.0.0/16PIM: For RP, Prune-list: 10.49.0.0/16In the following line, a periodic message is sent toward the RP. The default period is once per minute. Prune and join messages are sent toward the RP or source rather than directly to the RP or source. It is the responsibility of the next hop router to take proper action with this message, such as continuing to forward it to the next router in the tree.
PIM: Send periodic Join/Prune to RP via 172.16.37.6 (Ethernet1)Related Commands
debug ip rsvp
Caution
To display debug messages for RSVP categories, use the debug ip rsvp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip rsvp [all | api | authentication | cli | data-pkts | database | detail | dump-messages | errors | events | fast-reroute | filter [acl | vrf {* | vrf-name [acl]]} | function | handles | hello | messages | msg-mgr | path | policy | proxy | rate-limit | reliable-msg | resv | routing | sbm | signalling | snmp | summary-refresh | svc | timeouts | timer | traffic-control | wfq]
no debug ip rsvp
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Examples
RSVP Source Address and Interface Examples
The following output appears in source-address: source-address format after you configure a source address and enable the debug ip rsvp cli command:
Router# debug ip rsvp cli
RSVP cli debugging is on
*Sep 11 06:33:27.203: RSVP: RSVP source-address is enabled on interface Ethernet1/0. source-address: 10.1.3.13The following output appears in source-interface::address: source-interface::address format after you configure a source interface address and enable the debug ip rsvp cli command:
*Sep 11 06:33:27.203: RSVP: RSVP source-interface is enabled on interface Ethernet1/0. source-interface::address: Loopback0::10.1.1.1The following output appears when you enable the debug ip rsvp path command and configure a source address in the HOP object of PATH, PATHTEAR, or PATHERROR messages:
*Sep 12 08:56:46.267: RSVP: 10.1.1.1_200->10.4.4.4_100[0.0.0.0]: building hop object with src addr: 10.2.3.23RSVP Signaling and Messages Examples
The following commands show how to enable debugging for RSVP signaling and messages:
Router# debug ip rsvp signallingRSVP signalling messages (Summary) debugging is onRouter# debug ip rsvp messagesRSVP messages (sent/received via IP) debugging is onThe following output displays RSVP signaling-related events that include sending and receiving PATH and RESV messages, admitting new reservations, establishing sessions, sending and receiving acknowledgments (ACKs), and sending and receiving summary refresh messages:
01:14:56:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:Received Path message from 10.20.1.1 (on sender host)01:14:56:RSVP:new path message passed parsing, continue...01:14:56:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:Refresh Path psb = 61646BB0 refresh interval = 0mSec01:14:56:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:Sending Path message to 10.4.4.201:14:56:RSVP session 10.75.1.1_100[10.20.1.1]:Path sent by IP to 10.4.4.2 length=216 checksum=B1E4 TOS=0xC0 prerouted=YESrouter_alert=YES udp=NO (Ethernet1)01:14:56:RSVP:Resv received from IP layer (IP HDR 10.4.4.2->10.4.4.1)01:14:56:RSVP session 10.75.1.1_100[10.20.1.1]:Received RESV for 10.75.1.1 (Ethernet1) from 10.4.4.201:14:56:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:reservation not found--new one01:14:56:RSVP-RESV:Admitting new reservation:6165D0E401:14:56:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:RSVP bandwidth is available01:14:56:RSVP-RESV:reservation was installed:6165D0E401:14:57:RSVP:Sending Unknown message to 10.4.4.201:14:57:RSVP:Ack sent by IP to 10.4.4.2 length=20 checksum=34A7 TOS=0x00 prerouted=NO router_alert=NO udp=NO (Ethernet1)01:14:57:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:Refresh Path psb = 61646BB0 refresh interval = 937mSec01:14:58:%LINK-3-UPDOWN:Interface Tunnel100, changed state to up01:14:59:%LINEPROTO-5-UPDOWN:Line protocol on Interface Tunnel100, changed state to up01:15:26:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:Refresh Path psb = 61646BB0 refresh interval = 30000mSec01:15:26:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:Sending Path message to 10.4.4.201:15:26:RSVP session 10.75.1.1_100[10.20.1.1]:Path sent by IP to 10.4.4.2 length=216 checksum=B1E4 TOS=0xC0 prerouted=YESrouter_alert=YES udp=NO (Ethernet1)01:15:26:RSVP:Resv received from IP layer (IP HDR 10.4.4.2->10.4.4.1)01:15:26:RSVP session 10.75.1.1_100[10.20.1.1]:Received RESV for 10.75.1.1 (Ethernet1) from 10.4.4.201:15:26:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:reservation found--processing possible change:6165D0E401:15:26:RSVP 10.20.1.1_19->10.75.1.1_100[10.20.1.1]:No change in reservation01:15:27:RSVP:Sending Ack message to 10.4.4.201:15:27:RSVP:Ack sent by IP to 10.4.4.2 length=20 checksum=34A7 TOS=0x00 prerouted=NO router_alert=NO udp=NO (Ethernet1)01:15:56:RSVP:Sending Srefresh message to 10.4.4.201:15:56:RSVP:Srefresh sent by IP to 10.4.4.2 length=32 checksum=CA0D TOS=0x00 prerouted=NO router_alert=NO udp=NO (Ethernet1)01:15:56:RSVP:Ack received from IP layer (IP HDR 10.4.4.2->10.4.4.1)01:15:56:RSVP:Srefresh received from IP layer (IP HDR 10.4.4.2->10.4.4.1)01:15:56:RSVP-RESV:Resv state is being refreshed for 0x9101:15:56:RSVP:Sending Ack message to 10.4.4.201:15:56:RSVP:Ack sent by IP to 10.4.4.2 length=20 checksum=34A5 TOS=0x00 prerouted=NO router_alert=NO udp=NO (Ethernet1)01:16:26:RSVP:Sending Srefresh message to 10.4.4.201:16:26:RSVP:Srefresh sent by IP to 10.4.4.2 length=32 checksum=CA0C TOS=0x00 prerouted=NO router_alert=NO udp=NO (Ethernet1)01:16:26:RSVP:Ack received from IP layer (IP HDR 10.4.4.2->10.4.4.1)01:16:26:RSVP:Srefresh received from IP layer (IP HDR 10.4.4.2->10.4.4.1)01:16:26:RSVP-RESV:Resv state is being refreshed for 0x9101:16:26:RSVP:Sending Ack message to 10.4.4.201:16:26:RSVP:Ack sent by IP to 10.4.4.2 length=20 checksum=34A3 TOS=0x00 prerouted=NO router_alert=NO udp=NO (Ethernet1)Related Commands
debug ip tcp ha
To display TCP high availability (HA) events or debugging information for TCP stack interactions between the active Route Processor (RP) and the standby RP, use the debug ip tcp ha command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip tcp ha {events | transactions} [detail]
no debug ip tcp ha {events | transactions} [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ip tcp ha command is used to display TCP stateful switchover (SSO) events or debugging information for TCP stack interactions between the active RP and the standby RP. This is command is useful for troubleshooting SSO-aware TCP connections.
Use the debug ip tcp ha command with the transactions keyword to display failed TCP stack interactions between the active RP and standby RP. This form of the command displays failed TCP HA messages, RF redundancy-related client-application transactions, IPC client-application transactions, and In-Service Software Upgrade (ISSU) transactions.
Use the debug ip tcp ha command with the transactions and detail keywords to display successful TCP stack interactions between the active and standby RP. This form of the command displays successful TCP HA messages, RF redundancy-related client-application transactions, IPC client-application transactions, and ISSU transactions.
Use the debug ip tcp ha command with the events keyword to display TCP HA failures. This form of the command displays TCP HA failed encode or decode messages, system resources failures (such as memory allocation failures in the context of TCP HA), failed state changes, and failures that occur when SSO is enabled or disabled.
Use the debug ip tcp ha command with the events and detail keywords to display successful TCP HA operations and useful informational messages. This form of the command displays successful TCP encode or decode messages, state changes, and operations that occur when SSO is enabled or disabled.
Examples
The following is sample output from the debug ip tcp ha command with the transactions and detail keywords. The following output shows packet flow from the active to the standby RP for an established TCP SSO connection:
*Feb 19 23:28:23.324: TCPHA: Sending pkt msg, conn_id = 39, seq no = 2727115707*Feb 19 23:28:23.324: TCPHA: Sending pkt msg, conn_id = 396, seq no = 2959469308*Feb 19 23:28:23.324: TCPHA: Sending pkt msg, conn_id = 41, seq no = 1270243395*Feb 19 23:28:23.932: TCPHA: Sending pkt msg, conn_id = 42, seq no = 974255741*Feb 19 23:28:23.932: TCPHA: Sending pkt msg, conn_id = 475, seq no = 3059612402*Feb 19 23:28:24.544: TCPHA: Sending dummy pkt to standby; cid=109, size=19*Feb 19 23:28:42.976: TCPHA: Recd IPC msg len 24, type 3*Feb 19 23:28:42.976: TCPHA: Recd IPC msg len 24, type 3*Feb 19 23:28:43.172: TCPHA: Recd IPC msg len 79, type 2*Feb 19 23:28:43.172: TCPHA: Recd IPC msg len 79, typedebug isis nsf
To display information about the Intermediate System-to-Intermediate System (IS-IS) state during a Cisco nonstop forwarding (NSF) restart, use the debug isis nsf command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug isis nsf [detail]
no debug isis nsf [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug isis nsf command to display basic information about the IS-IS state during an NSF restart. Use the debug isis nsf detail command to display additional IS-IS state detail during an NSF restart.
Examples
The following example displays IS-IS state information during an NSF restart:
router# debug isis nsfIS-IS NSF events debugging is onThe following example displays detailed IS-IS state information during an NSF restart:
router# debug isis nsf detailIS-IS NSF events (detailed) debugging is onrouter#Jan 24 20:04:54.090:%CLNS-5-ADJCHANGE:ISIS:Adjacency to gsr1 (GigabitEthernet2/0/0) Up, Standby adjacencyJan 24 20:04:54.090:ISIS-NSF:ADJ:000C.0000.0000 (Gi2/0/0), type 8/1, cnt 0/1, ht 10 (NEW)Jan 24 20:04:54.142:ISIS-NSF:Rcv LSP - L2 000B.0000.0000.00-00, seq 251, csum B0DC, ht 120, len 123 (local)Jan 24 20:04:55.510:ISIS-NSF:Rcv LSP - L1 000B.0000.0000.00-00, seq 23E, csum D20D, ht 120, len 100 (local)Jan 24 20:04:56.494:ISIS-NSF:ADJ:000C.0000.0000 (Gi2/0/0), type 8/0, cnt 0/1, ht 30Jan 24 20:04:56.502:ISIS-NSF:Rcv LSP - L1 000B.0000.0000.01-00, seq 21C, csum 413, ht 120, len 58 (local)Jan 24 20:04:58.230:ISIS-NSF:Rcv LSP - L2 000C.0000.0000.00-00, seq 11A, csum E197, ht 1194, len 88 (Gi2/0/0)Jan 24 20:05:00.554:ISIS-NSF:Rcv LSP - L1 000B.0000.0000.00-00, seq 23F, csum 1527, ht 120, len 111 (local)Related Commands
debug mpls checkpoint label-binding
To display the events for the checkpoint label bindings of Multiprotocol Label Switching (MPLS) applications running on the router, use the debug mpls checkpoint label-binding command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug mpls checkpoint label-binding
no debug mpls checkpoint label-binding
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command with caution. The command displays the events for every label binding.
Examples
The following example shows the output when you issue the command on the standby Route Processor:
Router# debug mpls checkpoint label-bindingMPLS Label Binding Checkpoint debugging is on3d17h: mpls_lbl_bind_chkpt: client ID 13 up, total client 13d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1action 56, len 0, state 4, peer 133d17h: mpls_lbl_bind_chkpt: post msg type 13d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1action 56, len 0, state 4, peer 133d17h: mpls_lbl_bind_chkpt: post msg type 13d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1action 56, len 0, state 4, peer 133d17h: mpls_lbl_bind_chkpt: post msg type 13d17h: mpls_lbl_bind_chkpt: appl_id 13, KEY 000C8000188882003d17h: mpls_chkpt_db: AVL insert successful, Key 000C800018888200 action Add, label 193d17h: mpls_lbl_bind_chkpt: appl_id 13, KEY 000C8000132000803d17h: mpls_chkpt_db: AVL insert successful, Key 000C800013200080 action Add, label 203d17h: mpls_lbl_bind_chkpt: appl_id 13, KEY 000C80001383838382003d17h: mpls_chkpt_db: AVL insert successful, Key 000C8000138383838200 action Add, label 213d17h: Stby RP OR CF peer not ready, don't send msg3d17h: mpls_lbl_bind_chkpt: client ID 13 down, total client 03d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1action 56, len 2, state 4, peer 133d17h: mpls_lbl_bind_chkpt: post msg type 13d17h: mpls_lbl_bind_chkpt: appl_id 13, KEY action NSF unconfig, appl id 13Related Commands
debug ip bgp vpnv4 checkpoint
Display the events for the VRF checkpointing system between the active and standby Route Processors.
debug mpls ip iprm
To display debugging information for the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm command in privileged EXEC mode. To disable the display of this information, use the no form of this command.
debug mpls ip iprm
no debug mpls ip iprm
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays all output related to IPRM.
Examples
The command in the following examples display all IPRM debugging for the global routing table.
Cisco 7500 Series Example
Router# debug mpls ip iprmIPRM debugging is on for global routing tableiprm: prefix deleted: 10.0.0.44/32(glbl)iprm: delete mfi rewrite: 10.0.0.44/32(glbl)...iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: announce prefix local labels: lcatm; trans #80; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: omit rewrite create: 10.0.0.44/32(glbl)iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: announce prefix local labels: lcatm; trans #81; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: get path labels: 10.0.0.44/32(glbl); nh 10.0.0.55(glbl), Et4/0/1; trans #81; recurs tree changeiprm: ldm get path labels: 10.0.0.44/32(glbl), ldp; flags 0x8000iprm: announce prefix local labels: ldp; trans #81; 10.0.0.44/32(glbl); 1 label; flags 0x0iprm: lab 21, ltbl 0iprm: announce path labels: ldp; trans #81; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: path: nh 10.0.0.55(glbl), Et4/0/1iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: lcl lab 21, ltbl 0, ldpiprm: path lab -, nh 10.0.0.55(glbl), Et4/0/1; ldpiprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 moisiprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbliprm: fpi[1] LBL, owner LDP; 21, ltbl 0iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 10.0.0.55; nh if Et4/0/1 (nsf)Cisco 10000 Series Example
Router# debug mpls ip iprmIPRM debugging is on for global routing tableiprm: prefix deleted: 10.0.0.44/32(glbl)iprm: delete mfi rewrite: 10.0.0.44/32(glbl)...iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: omit rewrite create: 10.0.0.44/32(glbl)iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: get path labels: 10.0.0.44/32(glbl); nh 10.0.0.55(glbl), GigabitEthernet4/0/0; trans #81; recurs tree changeiprm: ldm get path labels: 10.0.0.44/32(glbl), ldp; flags 0x8000iprm: announce prefix local labels: ldp; trans #81; 10.0.0.44/32(glbl); 1 label; flags 0x0iprm: lab 21, ltbl 0iprm: announce path labels: ldp; trans #81; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: path: nh 10.0.0.55(glbl), GigabitEthernet4/0/0iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: lcl lab 21, ltbl 0, ldpiprm: path lab -, nh 10.0.0.55(glbl), GigabitEthernet4/0/0; ldpiprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 moisiprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbliprm: fpi[1] LBL, owner LDP; 21, ltbl 0iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 10.0.0.55; nh if GigabitEthernet4/0/0 (nsf)Table 16 describes the significant fields shown in the display. The field descriptions also apply to the output of following debug commands:
•
•
•
•
Related Commands
debug mpls ip iprm cef
To display debugging information for interactions between Cisco Express Forwarding and the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm cef command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug mpls ip iprm cef [table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name]
no debug mpls ip iprm cef
Syntax Description
Defaults
Debugging is not enabled. If you do not supply an optional keyword, all the debugging events are displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command limits the debug output to the IPRM interactions with Cisco Express Forwarding.
Examples
In the following example, IPRM events related to Cisco Express Forwarding are displayed.
Cisco 7500 Series Example
Router# debug mpls ip iprm cefIPRM CEF interaction debugging is on for global routing tableiprm: prefix deleted: 10.0.0.44/32(glbl)iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002iprm: announce prefix local labels: lcatm; trans #94; 10.0.0.44/32(glbl); 0 labels; flags 0x0...iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000iprm: announce prefix local labels: lcatm; trans #97; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: get path labels: 10.0.0.44/32(glbl); nh 10.0.0.55(glbl), Et4/0/1; trans #97; recurs tree changeiprm: announce prefix local labels: ldp; trans #97; 10.0.0.44/32(glbl); 1 label; flags 0x0iprm: lab 21, ltbl 0iprm: announce path labels: ldp; trans #97; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: path: nh 10.0.0.55(glbl), Et4/0/1Cisco 10000 Series Example
Router# debug mpls ip iprm cefIPRM CEF interaction debugging is on for global routing tableiprm: prefix deleted: 10.0.0.44/32(glbl)iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002...iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000iprm: get path labels: 10.0.0.44/32(glbl); nh 10.0.0.55(glbl), GigabitEthernet4/0/0; trans #97; recurs tree changeiprm: announce prefix local labels: ldp; trans #97; 10.0.0.44/32(glbl); 1 label; flags 0x0iprm: lab 21, ltbl 0iprm: announce path labels: ldp; trans #97; 10.0.0.44/32(glbl); 0 labels; flags 0x0iprm: path: nh 10.0.0.55(glbl), GigabitEthernet4/0/0See the field descriptions for the debug mpls ip iprm command for an explanation of the fields displayed in the output.
Related Commands
debug mpls ip iprm events
To display events related to the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm events command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug mpls ip iprm events
no debug mpls ip iprm events
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
See the command page for debug mpls ip iprm for sample command output and an explanation of the fields displayed in the output.
Related Commands
debug mpls ip iprm ldm
To display debugging information for interactions between the IP Label Distribution Modules (LDMs) and the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm ldm command in privileged EXEC mode. To disable the display of this information, use the no form of this command.
debug mpls ip iprm ldm [bgp | lcatm | ldp | vpnv4 | 6pe | table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name]
no debug mpls ip iprm ldm
Cisco 10000 Series Routers
debug mpls ip iprm ldm [bgp | ldp | vpnv4 | table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name]
no debug mpls ip iprm ldm
Syntax Description
Defaults
Debugging is not enabled. If you do not supply an optional keyword, all the debugging events are displayed.
Command Modes
Privileged EXEC
Command History
Examples
See the debug mpls ip iprm command page for sample output and an explanation of the fields displayed in the output.
Related Commands
debug mpls ip iprm mfi
To display debugging information for interactions between the Multiprotocol Label Switching (MPLS) Forwarding Infrastructure (MFI) and the MPLS IP Rewrite Manager (IPRM), use the debug mpls ip iprm mfi command in privileged EXEC mode. To disable the display of this information, use the no form of this command.
debug mpls ip iprm mfi [table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name]
no debug mpls ip iprm mfi
Syntax Description
Defaults
Debugging is not enabled. If you enable debugging but do not supply an optional keyword, all the debugging events are displayed.
Command Modes
Privileged EXEC
Command History
Examples
The command in the following example displays MFI events.
Cisco 7500 Series Example
Router# debug mpls ip iprm mfiIPRM MFI interaction debugging is on for global routing tableiprm: delete mfi rewrite: 10.0.0.44/32(glbl)...iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: omit rewrite create: 10.0.0.44/32(glbl)...iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: lcl lab 21, ltbl 0, ldpiprm: path lab -, nh 10.0.0.55(glbl), Et4/0/1; ldpiprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 moisiprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbliprm: fpi[1] LBL, owner LDP; 21, ltbl 0iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 10.0.0.55; nh if Et4/0/1 (nsf)Cisco 10000 Series Example
Router# debug mpls ip iprm mfiIPRM MFI interaction debugging is on for global routing tableiprm: delete mfi rewrite: 10.0.0.44/32(glbl)...iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: omit rewrite create: 10.0.0.44/32(glbl)...iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 moisiprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label infoiprm: lcl lab 21, ltbl 0, ldpiprm: path lab -, nh 10.0.0.55(glbl), GigabitEthernet4/0/0; ldpiprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 moisiprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbliprm: fpi[1] LBL, owner LDP; 21, ltbl 0iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 10.0.0.55; nh if GigabitEthernet4/0/0 (nsf)See the debug mpls ip iprm command page for an explanation of the fields displayed in the output.
Related Commands
debug mpls l2transport checkpoint
To enable the display of Any Transport over MPLS (AToM) events when AToM is configured for nonstop forwarding/stateful switchover (NSF/SSO) and Graceful Restart, use the debug mpls l2transport checkpoint command in privileged EXEC mode. To disable the display of these messages, use the no form of this command.
debug mpls l2transport checkpoint
no debug mpls l2transport checkpoint
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging of the AToM NSF/SSO and Graceful Restart feature is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use debug commands with care. They use a significant amount of CPU time and can affect system performance.
Examples
In the following example, the output shows that NSF/SSO and Graceful Restart synchronize the data between the active and backup Route Processors after an AToM virtual circuit (VC) is created. (Both the debug mpls l2transport checkpoint and the debug acircuit checkpoint commands are enabled in this example.)
The debug mpls l2transport checkpoint command is enabled on the active RP:
Router# debug mpls l2transport checkpointRouter# debug acircuit checkpointRouter# show debugAToM HA:AToM checkpointing events and errors debugging is onAC HA:Attachment Circuit Checkpoint debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Fa5/1/1.2Router(config-subif)# xconnect 10.55.55.2 1002 pw-class mplsAToM HA [10.55.55.2, 1002]: Build provision msg, SSM sw/seg 8192/8194 [0x2000/0x2002] PW i d 9216 [0x2400] local label 21AC HA: Dynamic Sync. Event:4 Sw:8192[2000] Se:16385[4001]AToM HA: CF sync send completeAC HA CF: Sync send complete. Code:0On the standby Route Processor, the following messages indicate that it receives checkpointing data:
AC HA [10.55.55.2, 1002]: Add to WaitQ. Flags:1AToM HA [105.55.55.2, 1002]: Received 32-byte provision version 1 CF messageAC HA CF: ClientId:89, Entity:0 Length:40AToM HA [10.55.55.2, 1002]: Process chkpt msg provision [1], ver 1AToM HA [10.55.55.2, 1002]: Reserved SSM sw/seg 8192/8194 [0x2000/0x2002] PW id 9216 [0x24 00]AC HA: Process Msg:35586. Ptr:44CBFD90. Val:0AC HA: Sync. Event:4 CktType:4 Sw:8192[2000] Se:16385[4001]AC HA [10.55.55.2, 1002]: Remove from WaitQ. Flags:1[OK][OK]During a switchover from the active to the backup Route Processor, the debug messages look similar to the following:
%HA-5-MODE: Operating mode is hsa, configured mode is sso.AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Opr:5, St:STANDBY HO T, PSt:ACTIVEAToM HA: CID 84, Seq 715, Status RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Op 5, State STANDB Y HOT, Peer ACTIVEAC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:STANDBY HOT, PSt:ACTIVEAToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_PRESENCE, Op 0, State STANDBY HOT, Peer AC TIVEAC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_COMM, Opr:0, St:STANDBY HOT, PSt:DISABLEDAToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_COMM, Op 0, State STANDBY HOT, Peer DISABL ED%HA-2-CUTOVER_NOTICE: Cutover initiated. Cease all console activity until system restarts.%HA-2-CUTOVER_NOTICE: Do not add/remove RSPs or line cards until switchover completes.%HA-2-CUTOVER_NOTICE: Deinitializing subsystems...%OIR-6-REMCARD: Card removed from slot 4, interfaces disabled%OIR-6-REMCARD: Card removed from slot 5, interfaces disabled%OIR-6-REMCARD: Card removed from slot 9, interfaces disabled%HA-2-CUTOVER_NOTICE: Reinitializing subsystems...%HA-2-CUTOVER_NOTICE: System preparing to restart...%HA-5-NOTICE: Resuming initialization...AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_REDUNDANCY_MODE_CHANGE, Opr:7, St:STANDBY HOT, PS t:DISABLED...%LDP-5-GR: LDP restarting gracefully. Preserving forwarding state for 250 seconds.AC HA RF: CId:83, Seq:710, Sta:RF_PROG_ACTIVE, Opr:0, St:ACTIVE, PSt:DISABLEDAToM HA: CID 84, Seq 715, Event RF_PROG_ACTIVE, Op 0, State ACTIVE, Peer DISABLEDAC HA: Process Msg:35588. Ptr:0. Val:0AC HA: Switchover: Standby->ActiveAC HA RF: ReconcilingRelated Commands
debug acircuit checkpoint
Enables the display of AToM attachment circuit events when AToM is configured for NSF/SSO and Graceful Restart.
debug mpls ldp checkpoint
Note
To enable the display of Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) checkpoint debugging information, use the debug mpls ldp checkpoint command in privileged EXEC mode. To disable the display of MPLS LDP checkpoint debugging information, use the no form of this command.
debug mpls ldp checkpoint
no debug mpls ldp checkpoint
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging of MPLS LDP checkpointing is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The following examples show sample output from the debug mpls ldp checkpoint command:
Sample Output on the Active Route Processor or PRE
Router# debug mpls ldp checkpointLDP Checkpointing events and errors debugging is onLDP-CF: 0:10.3.3.3/32,20:: checkpointing local bindingLDP-CF: 0:10.3.3.3/32,20:: changing checkpoint state from none to add-sendLDP-CF: 0:10.3.3.3/32,20:: changing checkpoint state from add-send to add-waitLDP-CF: received CF send-ackLDP-CF: 0:10.3.3.3/32,20:: changing checkpoint state from add-wait to addedSample Output on the Backup Route Processor or PRE
Router# debug mpls ldp checkpointLDP-CF: received 16-byte CF message: client 28 [0], ver 1, type 1LDP-CF: 0:10.3.3.3/32,20:: adding checkpointed local bindingTable 17 describes the significant field in the sample display.
Table 17 debug mpls ldp checkpoint Command Field Descriptions
0:10.3.3.3/32,20::
The table ID, prefix, prefix length, and label of the checkpointed label binding.
Related Commands
show mpls ldp checkpoint
Displays information about the LDP checkpoint system on the active Route Processor.
