Step 1 |
show checkpoint clients Use this command to display information about checkpoint clients:
Example:
Router# show checkpoint clients
Check Point List of Clients
CHKPT on ACTIVE server.
--------------------------------------------------------------------------------
Client Name Client Entity Bundle
ID ID Mode
--------------------------------------------------------------------------------
CHKPT Test client 1 -- On
Total API Messages Sent: 0
Total IPC Sent: 0
Total Message Len: 0
Total Bytes Allocated: 0
Buffers Held: 0
IPC Frag Count: 0
IPC HW mark: 0
IPC Sends w/Flow Off: 0
Send Errs: 0
Send Peer Errs: 0
Rcv Xform Errs: 0
Xmit Xform Errs: 0
Incompatible Messages: 0
--------------------------------------------------------------------------------
Client Name Client Entity Bundle
ID ID Mode
--------------------------------------------------------------------------------
Network RF Client 3 -- Off
Total API Messages Sent: 10
Total IPC Sent: 10
Total Message Len: 2144
Total Bytes Allocated: 2904
Buffers Held: 0
IPC Frag Count: 0
IPC HW mark: 0
IPC Sends w/Flow Off: 0
Send Errs: 0
Send Peer Errs: 0
Rcv Xform Errs: 0
Xmit Xform Errs: 0
Incompatible Messages: 0
--------------------------------------------------------------------------------
Client Name Client Entity Bundle
ID ID Mode
--More--
.
.
.
|
Step 2 |
show vfi [name vfi-name ] checkpoint [summary] Use this command to display checkpoint information related to a specific virtual forwarding instance (VFI) named H-VPLS-A-VFI:
Example:
Router# show vfi name H-VPLS-A-VFI checkpoint
VFI Active RP
Checkpointing: Allowed
ISSU Client id: 2092, Session id: 65543, Compatible with peer
VFI VFI AC VFI PW
Bulk-sync 1 1 3
Checkpoint failures: 0 3 21
Recovered at switchover: 0 0 0
Recovery failures: 0 0 0
Legend: C=Checkpointed
VFI name: H-VPLS-A-VFI, state: up, type: multipoint
VPN ID: 12, Internal ID 1 C
Local attachment circuits:
Vlan200 16387 / 8195 C
Neighbors connected via pseudowires:
Peer ID VC ID SSM IDs
10.0.0.12 12 4096 / 12292 C
10.0.0.15 12 8193 / 16389 C
10.0.0.14 12 12290 / 20486 C
|
Step 3 |
debug cwan atom Use this command to enable debugging of Any Transport over MPLS (AToM) platform events. The following example shows debug message output that appears when debugging is enabled and a PW port is configured and then unconfigured:
Example:
Router# debug cwan atom
ConstWan Generic AToM debugging is on
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router#(config)# l2 vfi VPLS-2000 manual
Router#(config-vfi)# vpn id 2000
Router#(config-vfi)# neighbor 10.1.1.1 encapsulation mpls
Router#(config-vfi)#
01:16:36: cwan_rp_vfi_atom_provision_vlan PROV[VFI-ATOM]: plat_index(0xC7D00084) vlanid(2000) pseudo_port(0x84) vfi_plat_index(0xC7D00084) seginfo(0x53D38220) segtype(25) seghandle(0x53AEE074) split-horizon(On) cwan_atom_intfs(3) vfi_vcs(3) spoke_vcs(0)
Router#(config-vfi)# end
Router# debug cwan atom
ConstWan Generic AToM debugging is on
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# l2 vfi VPLS-2000
Router(config-vfi)# no neighbor 10.1.1.1 encapsulation mpls
Router(config-vfi)#
01:27:18: cwan_rp_vfi_atom_unprovision_vlan: UNPROV[VFI-ATOM]: circ_index(0xC7D00084) is_vfi(1) vlan(2000) vfi_vcs(3) spoke_vcs(0) split_horizon(On)
01:27:18: cwan_atom_vlan_remove_rp: Vlan2000 ip_iw(0) ip_enabled(0)
Router#(config-vfi)# end
|
Step 4 |
debug cwan ltl Use this command to enable debugging of Local Target Manager (LTL) debugging events and errors. The following example shows debug message outputs that appear when debugging is enabled and a PW port is configured and then unconfigured:
Example:
Router# debug cwan ltl
ConstWan LTL manager debugging is on
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router#(config)# l2 vfi VPLS-2000 manual
Router#(config-vfi)# vpn id 2000
Router#(config-vfi)# neighbor 10.1.1.1 encapsulation mpls
Router#(config-vfi)#
01:17:35: CWAN LTL MGR: Port 133 is free to use for VPLS with vlan 2000 - tx_tvc(0x9F404)
Router#(config-vfi)# end
Router# debug cwan ltl
ConstWan LTL manager debugging is on
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# l2 vfi VPLS-2000 manual
Router(config-vfi)# no neighbor 10.1.1.1 encapsulation mpls
Router(config-vfi)#
01:29:05: CWAN LTL MGR: DELETE VPLS PW vlan(2000) pseudo_slotunit(133)
Router(config-vfi)# end
|
Step 5 |
debug issu client negotiation Use this command to enable debugging of ISSU client negotiation events and errors:
Example:
Router# debug issu client negotiation
*Jun 5 22:41:47.332: VFI ISSU: Negotiation rc ISSU_RC_NEGO_DONE, compatible
*Jun 5 22:41:47.332: AToM HA: CID 84 Seq 230 Event RF_PROG_STANDBY_CONFIG Op 0 State ACTIVE Peer STANDBY COLD-CONFIG
*Jun 5 22:41:47.432: ATOM ISSU: Propose L2HW cap 0xFFF rc 0
*Jun 5 22:41:47.532: ATOM ISSU: Active negotiator, accept compatible L2HW cap 0xFFF
*Jun 5 22:41:48.232: ATOM ISSU: Negotiation rc ISSU_RC_NEGO_DONE, compatible
*Jun 5 22:41:50.836: cwan_atom_issu_start_nego_session: Start session negotiation
*Jun 5 22:41:50.836: cwan_atom_issu_start_nego_session: Started nego successfully, rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:41:50.836: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:41:50.840: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:41:50.940: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:41:50.940: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:41:51.040: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:41:51.040: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:41:51.140: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:41:51.140: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:41:51.240: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:41:51.240: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:41:51.340: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:50:40.156: VFI ISSU: Negotiation rc ISSU_RC_NEGO_DONE, compatible
*Jun 5 22:50:40.156: AToM HA: CID 84 Seq 230 Event RF_PROG_STANDBY_CONFIG Op 0 State ACTIVE Peer STANDBY COLD-CONFIG
*Jun 5 22:50:40.256: ATOM ISSU: Passive negotiator, accept compatible L2HW cap 0xFFF
*Jun 5 22:50:40.964: ATOM ISSU: Negotiation rc ISSU_RC_NEGO_DONE, compatible
*Jun 5 22:50:43.516: cwan_atom_issu_start_nego_session: Start session negotiation
*Jun 5 22:50:43.516: cwan_atom_issu_start_nego_session: Started nego successfully, rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:50:43.520: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:50:43.520: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:50:43.620: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:50:43.620: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:50:43.720: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:50:43.720: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:50:43.820: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:50:43.820: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:50:43.920: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
*Jun 5 22:50:43.920: cwan_atom_issu_receive_nego_msg: issu_receive_nego_msg rc=ISSU_RC_NEGO_NOT_DONE
*Jun 5 22:50:44.020: cwan_atom_issu_receive_nego_msg: Start, cwan_atom_issu_nego_done=0
|
Step 6 |
debug issu client registration Use this command to enable debugging of ISSU client registration events and errors. After the peer router reloads, the following debug messages appear:
Example:
Router# debug issu client registration
Router#
00:42:21: VFI ISSU: Unregistered ISSU session 0, ISSU_RC_OK
00:42:21: %LINK-3-UPDOWN: Interface GigabitEthernet6/2, changed state to down
00:42:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/2, changed state to down
00:42:21: %LINK-3-UPDOWN: Interface Vlan2000, changed state to down
00:42:21: %LINK-3-UPDOWN: Interface Vlan2001, changed state to down
00:42:21: %LINK-3-UPDOWN: Interface Vlan2002, changed state to down
Router#
00:42:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2000, changed state to down
00:42:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2001, changed state to down
00:42:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2002, changed state to down
Router#
00:49:01: %LINK-3-UPDOWN: Interface GigabitEthernet6/2, changed state to down
00:49:02: %LINK-3-UPDOWN: Interface GigabitEthernet6/2, changed state to up
PE-3#
00:49:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/2, changed state to up
Router#
00:49:35: %LINK-3-UPDOWN: Interface Vlan2000, changed state to up
00:49:35: %LINK-3-UPDOWN: Interface Vlan2001, changed state to up
00:49:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2000, changed state to up
00:49:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2001, changed state to up
00:49:35: %LINK-3-UPDOWN: Interface Vlan2002, changed state to up
Router#
00:49:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2002, changed state to up
Router#
00:49:48: VFI ISSU: Registered session 131171, ISSU_RC_OK
Router#
00:50:08: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
Router#
|
Step 7 |
debug issu client transform [clientID client-id] Use this command to enable debugging of ISSU client transform events and errors. The following command example enables debug output for a specific ISSU client (clientID 2092). After the peer router reloads, the following debug messages appear:
Example:
Router# debug issu client transform clientID 2092
Router#
05:35:15: %LINK-3-UPDOWN: Interface GigabitEthernet6/2, changed state to down
05:35:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6/2, changed state to down
05:35:15: %LINK-3-UPDOWN: Interface Vlan2000, changed state to down
05:35:15: %LINK-3-UPDOWN: Interface Vlan2001, changed state to down
05:35:15: %LINK-3-UPDOWN: Interface Vlan2002, changed state to down
Router#
05:35:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2000, changed state to down
05:35:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2001, changed state to down
05:35:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2002, changed state to down
Router#
05:41:55: %LINK-3-UPDOWN: Interface GigabitEthernet6/2, changed state to down
05:41:56: %LINK-3-UPDOWN: Interface GigabitEthernet6/2, changed state to up
.
.
.
05:43:02: VFI ISSU: Xmit transform message 5, rc ISSU_RC_OK
05:43:02: ISSU Buffer dump @ 0x0817EC7C
05:43:02: 00 00 00 00
05:43:02: VFI ISSU: Xmit transform message 1, rc ISSU_RC_OK
05:43:02: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED succeeded
Router#
|
Step 8 |
debug vfi checkpoint Use this command to enable debugging VFI checkpointing events and errors:
Example:
Router# debug vfi checkpoint
Router# $may24_v1 6 slavedisk0:s72033-adventerprisek9_wan-mz.cflow_may24_v1
Router#
*Jun 5 22:37:17.268: AToM HA: CF status 3 not processed
*Jun 5 22:37:17.268: VFI HA: CF status 3 not processed
*Jun 5 22:37:17.296: AC HA RF: CId:83, Seq:228, Sta:RF_STATUS_PEER_COMM, Opr:0, St:ACTIVE, PSt:STANDBY HOT
*Jun 5 22:37:17.296: VFI HA: CID 145, Seq 229, Status RF_STATUS_PEER_COMM, Op 0, State ACTIVE, Peer STANDBY HOT
*Jun 5 22:37:17.296: AToM HA: CID 84, Seq 230, Status RF_STATUS_PEER_COMM, Op 0, State ACTIVE, Peer STANDBY HOT
*Jun 5 22:37:17.444: AToM HA: CF status 3 not processed
*Jun 5 22:37:17.444: VFI HA: CF status 3 not processed
*Jun 5 22:37:17.268: %OIR-SP-3-PWRCYCLE: Card in module 6, is being power-cycled (RF request)
*Jun 5 22:37:17.792: AC HA RF: CId:83, Seq:228, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:ACTIVE, PSt:DISABLED
*Jun 5 22:37:17.792: VFI HA: CID 145, Seq 229, Status RF_STATUS_PEER_PRESENCE, Op 0, State ACTIVE, Peer DISABLED
*Jun 5 22:40:40.244: SP-STDBY: SP: Currently running ROMMON from S (Gold) region
*Jun 5 22:40:45.028: %DIAG-SP-STDBY-6-RUN_MINIMUM: Module 6: Running Minimal Diagnostics...
*Jun 5 22:40:56.492: %DIAG-SP-STDBY-6-DIAG_OK: Module 6: Passed Online Diagnostics
*Jun 5 22:41:53.436: %SYS-SP-STDBY-5-RESTART: System restarted --
*Jun 5 22:42:12.760: VFI HA: CID 145 Seq 229 Event RF_PROG_STANDBY_BULK Op 0 State ACTIVE Peer STANDBY COLD-BULK
*Jun 5 22:42:12.764: VFI HA: Ignore RF progression event, VFI Mgr process is not running, skipped bulk sync
.
.
.
*Jun 5 22:42:16.948: %ISSU_PROCESS-SP-7-DEBUG: Peer state is [ STANDBY HOT ]; Please issue the runversion command
*Jun 5 22:42:15.928: %PFREDUN-SP-STDBY-6-STANDBY: Ready for SSO mode
*Jun 5 22:42:16.956: %RF-SP-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
*Jun 5 22:42:16.112: %SYS-SP-STDBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
Router#
|