Effective with Cisco IOS Release 12.2(33)SRA, the
debugmplsldpcheckpointcommand is replaced by the
debugmplsvpnhacommand. See the
debugmplsvpnhacommand for more information.
To enable the display of Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) checkpoint debugging information, use the
debugmplsldpcheckpointcommand in privileged EXEC mode. To disable the display of MPLS LDP checkpoint debugging information, use the
no form of this command.
debugmplsldpcheckpoint
nodebugmplsldpcheckpoint
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
Release
Modification
12.2(25)S
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
12.2(33)SRA
This command was replaced by the
debugmplsvpnhacommand.
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 checkpoint
LDP Checkpointing events and errors debugging is on
LDP-CF: 0:10.3.3.3/32,20:: checkpointing local binding
LDP-CF: 0:10.3.3.3/32,20:: changing checkpoint state from none to add-send
LDP-CF: 0:10.3.3.3/32,20:: changing checkpoint state from add-send to add-wait
LDP-CF: received CF send-ack
LDP-CF: 0:10.3.3.3/32,20:: changing checkpoint state from add-wait to added
Sample Output on the Backup Route Processor or PRE
Router# debug mpls ldp checkpoint
LDP-CF: received 16-byte CF message: client 28 [0], ver 1, type 1
LDP-CF: 0:10.3.3.3/32,20:: adding checkpointed local binding
The following table describes the significant field in the sample display.
Table 1 debug mpls ldp checkpoint Command Field Descriptions
Field
Description
0:10.3.3.3/32,20::
The table ID, prefix, prefix length, and label of the checkpointed label binding.
Related Commands
Command
Description
showmplsldpcheckpoint
Displays information about the LDP checkpoint system on the active Route Processor.
debug mpls ldp graceful-restart
To display debugging information for Multiprotocol (MPLS) Label Distribution Protocol (LDP) stateful switchover (SSO) nonstop forwarding (NSF) support and Graceful Restart, use the
debugmplsldpgraceful-restartcommand in privileged EXEC mode. To disable the display of this debugging information, use the
no form of this command.
debugmplsldpgraceful-restart
nodebugmplsldpgraceful-restart
Syntax Description
This command has no arguments or keywords.
Command Default
The display of debugging information is not enabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(29)S
This command was introduced.
12.3(14)T
This command was integrated into Cisco IOS Release 12.3(14)T.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
Usage Guidelines
This command shows events and errors related to LDP Graceful Restart.
Examples
The following example shows sample output from the debug mpls ldp graceful-restart command. The output shows that a session was lost. The status message show the events that happen during recovery of the bindings.
Router# debug mpls ldp graceful-restart
LDP GR: GR session 10.110.0.10:0:: lost
LDP GR: down nbr 10.110.0.10:0:: created [1 total]
LDP GR: GR session 10.110.0.10:0:: bindings retained
LDP GR: down nbr 10.110.0.10:0:: added all 7 addresses [7 total]
LDP GR: down nbr 10.110.0.10:0:: state change (None -> Reconnect-Wait)
LDP GR: down nbr 10.110.0.10:0:: reconnect timer started [120000 msecs]
LDP GR: down nbr 10.110.0.10:0:: added to bindings task queue [1 entries]
LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10)
LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0
LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0
LDP GR: Tagcon querying for up to 12 bindings update tasks
LDP GR: down nbr 10.110.0.10:0:: requesting bindings MARK for {10.110.0.10:0, 1}
LDP GR: down nbr 10.110.0.10:0:: removed from bindings task queue [0 entries]
LDP GR: Requesting 1 bindings update tasks [0 left in queue]
LDP GR: 10.1.0.0/8:: updating binding from 10.110.0.10:0, inst 1:: marking stale;
LDP GR: 10.2.0.0/16:: updating binding from 10.110.0.10:0, inst 1:: marking stale;
LDP GR: 10.0.0.14/32:: updating binding from 10.110.0.10:0, inst 1:: marking stale;
LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10)
LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0
LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0
LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10)
LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0
LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0
LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10)
LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0
LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0
LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10)
LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0
LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0
LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10)
LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0
LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0
LDP GR: Received FT Sess TLV from 10.110.0.10:0 (fl 0x1, rs 0x0, rconn 120000, rcov 120000)
LDP GR: GR session 10.110.0.10:0:: allocated instance, 2
LDP GR: GR session 10.110.0.10:0:: established
LDP GR: GR session 10.110.0.10:0:: found down nbr 10.110.0.10:0
LDP GR: down nbr 10.110.0.10:0:: reconnect timer stopped
LDP GR: down nbr 10.110.0.10:0:: state change (Reconnect-Wait -> Recovering)
LDP GR: down nbr 10.110.0.10:0:: recovery timer started [120000 msecs]
%LDP-5-GR: GR session 10.110.0.10:0 (inst. 2): starting graceful recovery
%LDP-5-NBRCHG: LDP Neighbor 10.110.0.10:0 is UP
LDP GR: 10.1.0.0//8:: refreshing stale binding from 10.110.0.10:0, inst 1 -> inst 2
LDP GR: 10.43.0.0//16:: refreshing stale binding from 10.110.0.10:0, inst 1 -> inst 2
LDP GR: down nbr 10.110.0.10:0:: recovery timer expired
%LDP-5-GR: GR session 10.110.0.10:0 (inst. 2): completed graceful recovery
LDP GR: down nbr 10.110.0.10:0:: destroying record [0 left]
LDP GR: down nbr 10.110.0.10:0:: state change (Recovering -> Delete-Wait)
LDP GR: down nbr 10.110.0.10:0:: added to bindings task queue [1 entries]
LDP GR: Tagcon querying for up to 12 bindings update tasks
LDP GR: down nbr 10.110.0.10:0:: requesting bindings DEL for {10.110.0.10:0, 1}
LDP GR: down nbr 10.110.0.10:0:: removed from bindings task queue [0 entries]
LDP GR: Requesting 1 bindings update tasks [0 left in queue]
LDP GR: GR session 10.110.0.10:0:: released instance, 1
The debug output is formatted in three general ways.
LDP GR: GR session 10.110.0.10:0:: found down nbr 10.110.0.10:0
down nbr 10.110.0.10:0:: removed from bindings task queue [0 entries]
The following table describes the fields for the debug command output.
Table 2 debug mpls ldp graceful-restart Command Field Descriptions
Field
Description
LDP GR
Identifies LDP Graceful Restart application
GR session 10.110.0.10:0
ID of the LDP session that is enabled for Graceful Restart.
found down nbr 10.110.0.10:0
Describes the event that is happening to that LDP session.
down nbr 10.110.0.10:0::
Identifies the Down Neighbor record, which logs the state of a recently lost Graceful Restart session.
removed from bindings task queue [0 entries]
Describes the event that is happening to the recently lost Graceful Restart session.
2.0.0.0/8::
Identifies the Forwarding Equivalence Class (FEC) associated with the remote label binding being modified. The FEC identifies the Label Information Base (LIB) entry.
updating binding
Lists the operation being performed on the remote label binding.
10.110.0.10:0, inst 1:: marking stale;
Identifies the LDP session during which the remote label binding was learned.
Related Commands
Command
Description
showmplsldpgraceful-restart
Displays a summary of the LDP Graceful Restart status.
debug mpls ldp igp sync
To enable the display of events related to the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP)-Interior Gateway Protocol (IGP) Synchronization feature, use the
debugmplsldpigpsynccommand in
privilegedEXECmode. To disable this feature, use the
no form of this command.
(Optional) Enables the display of MPLS LDP-IGP synchronization events for the specified interface.
peeracl
(Optional) Enables the display of MPLS LDP-IGP synchronization events for the specified peer access control list (ACL).
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(30)S
This command was introduced.
12.3(14)T
This command was integrated into Cisco IOS Release 12.3(14)T.
12.0(32)S
The command output was modified to display events related to the delay timer on interfaces running Open Shortest Path First (OSPF) processes, if the delay timer is configured.
12.0(32)SY
The command output was modified to display events related to synchronization on interfaces running Intermediate System-to-Intermediate System (IS-IS) processes.
12.4(12)
This command was integrated into Cisco IOS Release 12.4(12).
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Examples
The following example shows events related to MPLS LDP-IGP synchronization on interfaces running OSPF:
Router# debug mpls ldp igp sync
LDP-SYNC: Et0/0, OSPF 1: notify status (required, not achieved, no delay, holddown infinite) internal status (achieved, timer running)
LDP-SYNC: E1/0, 10.0.0.1: Adj being deleted, sync_achieved goes down
LDP-SYNC: E1/0, OSPF 1: notify status (required, not achieved, delay, holddown infinite)
LDP-SYNC: Et0/0: Session already up and interface address advertised, sync_achieved comes up.
LDP-SYNC: Et0/0, OSPF 1: notify status (required, achieved, no delay, holddown infinite)
The following example shows events associated when an IS-IS instance, ISIS-1, is configured for synchronization:
The following table describes the significant fields shown in the displays.
Table 3 debug mpls ldp igp sync Field Descriptions
Field
Description
sync_achieved
The first line of the output for an interface shows the status of the MPLS LDP-IGP Synchronization feature in relation to the status of the interface.
notify status
Notify status shows the following MPLS LDP-IGP synchronization information for each interface:
If MPLS LDP-IGP synchronization is required.
If MPLS LDP-IGP synchronization has been achieved.
If the IGP should wait for MPLS LDP-IGP synchronization to be achieved.
The length of time the IGP should wait for MPLS LDP-IGP synchronization to be achieved.
internal status
Internal status displays the LDP internal synchronization status and the state of the timer. The internal status can be achieved or not achieved. The timer state can be running or not running.
The following example shows events associated with MPLS LDP-IGP synchronization on interfaces running OSPF when you configured a delay timer:
Router# debug mpls ldp igp sync
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: notify status (required, not achieved, no delay, holddown infinite) internal status (achieved, timer running)
!
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Sync disabled by IGP. Stop delay timer
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: TAGSW subblock destroyed. Stop delay timer
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Sync down. Stop delay timer
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay notifying IGP of sync achieved for 60 seconds
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay timer expired, notify IGP of sync achieved
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay timer expired but sync is no longer required won't notify IGP of sync achieved
*Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay timer expired but sync is down won't notify IGP of sync achieved
Related Commands
Command
Description
mplsldpsync
Enables MPLS LDP-IGP synchronization on all interfaces that belong to an OSPF process or IS-IS process.
showmplsldpigpsync
Displays the status of the MPLS LDP-IGP synchronization process.
debug mpls ldp messages
To display specific information (such as message type, source, and destination) about Label Distribution Protocol (LDP) messages sent to and received from LDP peers, use the
debugmplsldpmessagescommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplsldpmessages
{ sent | received }
[all]
[ peer-aclacl ]
nodebugmplsldpmessages
{ sent | received }
[all]
[ peer-aclacl ]
Syntax Description
sent
Displays LDP messages sent to LDP peers permitted by the access control list (ACL).
received
Displays LDP messages received from LDP peers permitted by the
ACL.
all
(Optional) Displays all LDP messages sent to and received from LDP peers (including periodic keepalive messages) permitted by the ACL.
peer-aclacl
(Optional) Limits the messages displayed for LDP peers in accordance with the ACL.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
11.1CT
This command was introduced.
12.0(10)ST
This command was modified to reflect MPLS IETF command syntax and terminology.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
12.1(8a)E
This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(50)SY
This command was integrated into Cisco IOS Release 12.2(50)SY.
Usage Guidelines
LDP requires periodic transmission of keepalive messages. If you do not specify the
all keyword, periodic keepalive messages are not displayed.
Examples
The following is sample output from the
debugmplsldpmessages command:
Router# debug mpls ldp messages received
LDP received messages, excluding periodic Keep Alives debugging is on
Router# debug mpls ldp messages sent
LDP sent PDUs, excluding periodic Keep Alives debugging is on
ldp: Rcvd init msg from 192.168.10.1 (pp 0x0)
ldp: Sent init msg to 192.168.10.1:0 (pp 0x0)
ldp: Sent keepalive msg to 192.168.10.1:0 (pp 0x0)
ldp: Rcvd keepalive msg from 192.168.10.1:0 (pp 0x0)
ldp: Sent address msg to 192.168.10.1:0 (pp 0x610F00E0)
ldp: Sent label mapping msg to 192.168.10.1:0 (pp 0x610F00E0)
ldp: Sent label mapping msg to 192.168.10.1:0 (pp 0x610F00E0)
ldp: Sent label mapping msg to 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd address msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
ldp: Rcvd label mapping msg from 192.168.10.1:0 (pp 0x610F00E0)
The following table describes the significant fields shown in the display.
Table 4 debug mpls ldp messages Field Descriptions
Field
Description
ldp:
Identifies the source of the displayed information as LDP.
Rcvd xxx msg
Sent xxx msg
Type of message received or sent.
from a.b.c.d
Host that sent the message. Used in the early stages of the opening of an LDP session, when the LDP identifier is not yet known.
from a.b.c.d:e
to a.b.c.d:e
LDP identifier of the peer that sent the message or to which the message was sent.
(pp 0xnnnnnnnn)
Identifies the data structure used to represent the peer at the label distribution level. Useful for correlating debug output.
Related Commands
Command
Description
debugmplsldpsessionio
Displays the contents of LDP messages sent to and received from LDP peers.
debug mpls ldp nsr
To enable the display of Multiprotocol Label Switching (MPLS) Label Distribution
Protocol (LDP) nonstop routing (NSR) debugging events for all NSR sessions or for
a specified peer, use the debug mpls ldp nsr command in privileged EXEC mode.
To disable the display of MPLS LDP NSR debugging information, use the no form of
this command.
debugmplsldpnsr
[ peer-aclacl-name ]
nodebugmplsldpnsr
[ peer-aclacl-name ]
Syntax Description
peer-aclacl-name
(Optional) Displays LDP NSR events for the specified peer
access list.
Command Default
Debugging of MPLS LDP NSR events are not enabled.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
Cisco IOS XE Release 3.9S
This command was introduced.
Examples
The following is sample output from the debug mpls ldp nsr command:
Device# debug mpls ldp nsr
*Feb 5 22:14:55.666: LDP NSR is enabled
*Feb 5 22:14:55.666: LDP Non-Stop-Routing has been enabled
*Feb 5 22:14:55.871: LDP-CF: 0:0x2A9B99C9B8 for Serial4/0, adj_addr/xport_addr 10.2.4.4/10.4.0.1:: received standby session-up, 9, in state init-sent
*Feb 5 22:14:55.871: LDP NSR: Sess Sync Record created for peer 10.4.0.1:0, inst 2,type 1
*Feb 5 22:14:55.871: LDP NSR: Addr sync Rec added to tree for peer 10.4.0.1:0, inst 2, msg-id 0, num-rec 3
*Feb 5 22:14:55.871: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from none to send for msgid 0
*Feb 5 22:14:55.871: LDP NSR: Sess Sync Record created for peer 10.4.0.1:0, inst 2,type 3
*Feb 5 22:14:55.871: LDP NSR: Session Sync record deleted for peer 10.4.0.1:0, inst 2, type 3
*Feb 5 22:14:55.871: LDP NSR: Sess Sync Record created for peer 10.4.0.1:0, inst 2,type 2
*Feb 5 22:14:55.872: LDP NSR: Rbind sync Rec added to tree for peer 10.4.0.1:0, inst 2, msg-id 2, num-rec 9
*Feb 5 22:14:55.872: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from none to send for msgid 2
*Feb 5 22:14:55.872: LDP NSR: Sess Sync Record created for peer 10.4.0.1:0, inst 2,type 4
*Feb 5 22:14:55.872: LDP NSR: Cap sync Rec added to tree for peer 10.4.0.1:0, inst 2, msg-id 3, num-rec 10
*Feb 5 22:14:55.872: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from none to send for msgid 3
*Feb 5 22:14:55.872: LDP NSR: Sess Sync Addr Msg for Peer 10.4.0.1:0, inst 2, msg_id 0, num_records 3
*Feb 5 22:14:55.872: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from send to wait for msgid 0
*Feb 5 22:14:55.872: LDP NSR: Peer 10.4.0.1:0 Addr Session sync sent, action 9, state wait
*Feb 5 22:14:55.872: LDP NSR: Sess Sync Rbind Msg for Peer 10.4.0.1:0, msg_id 2, num_records 9
*Feb 5 22:14:55.872: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from send to wait for msgid 2
*Feb 5 22:14:55.872: LDP NSR: Peer 10.4.0.1:0 Session sync sent, action 11, state wait
*Feb 5 22:14:55.872: LDP NSR: Sess Sync Cap Msg for Peer 10.4.0.1:0, msg_id 3, num_records 10
*Feb 5 22:14:55.872: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from send to wait for msgid 3
*Feb 5 22:14:55.872: LDP NSR: Peer 10.4.0.1:0 Session sync sent, action 12, state wait
*Feb 5 22:14:55.873: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from wait to none for msgid 0
*Feb 5 22:14:55.873: LDP NSR: Session Sync record deleted for peer 10.4.0.1:0, inst 2, type 1
*Feb 5 22:14:55.873: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from wait to none for msgid 2
*Feb 5 22:14:55.873: LDP NSR: Session Sync record deleted for peer 10.4.0.1:0, inst 2, type 2
*Feb 5 22:14:56.488: LDP NSR: Peer10.4.0.1:0, Inst 2, Changing sync_rec state from wait to none for msgid 3
*Feb 5 22:14:56.488: LDP NSR: Session Sync record deleted for peer 10.4.0.1:0, inst 2, type 4
*Feb 5 22:14:56.488: LDP-CF: 0:0x2A9B99C9B8 for Serial4/0, adj_addr/xport_addr 10.2.4.4/10.4.0.1:: received Session Sync Done, 13, in state session-sync
*Feb 5 22:14:56.488: LDP NSR: Active Chkpt sess_sync_done for Peer 10.4.0.1:0, inst 2, type 11, seq 11
Related Commands
Command
Description
mpls ldp nsr
Enables or disables NSR for LDP sessions.
debug mpls ldp peer state-machine
To display information about state transitions for label distribution protocol (LDP) sessions, use the
debugmplsldppeerstate-machinecommand in privileged EXEC mode. To disable this feature, use the no form of this command.
debugmplsldppeerstate-machine
nodebugmplsldppeerstate-machine
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.0(10)ST
This command was modified to reflect MPLS IETF command syntax and terminology.
12.0(14)ST
This command was integrated into Cisco IOS Release 12.0(14)ST.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
12.1(8a)E
This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.0(21)ST
This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.0(23)S
This command was integrated into Cisco IOS Release 12.0(23)S.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
LDP manages peer sessions by means of two coupled state machines:
A low-level state machine that deals with session establishment and shutdown
A high-level state machine that deals with setting up and shutting down label advertisement
Use the
debugmplsldpsessionstate-machine command to monitor the lower-level session state machine.
Use the
debugmplsldppeerstate-machine command to monitor the higher-level session state machine.
Examples
The following shows sample output from the
debugmplsldppeerstate-machine command:
Router# debug mpls ldp peer state-machine
tagcon: start session TCP timers for 144.0.0.44:0 (pp 0x610EEC84)
tagcon: Enqueue peer up work for 144.0.0.44:0 (pp 0x610EEC84)
tagcon: peer 144.0.0.44:0 (pp 0x610EEC84): Event unsol open
unsol op pdg -> estab
tagcon: Send initial advertisements to peer 144.0.0.44:0
tagcon: Initial address advertisement to peer 144.0.0.44:0
tagcon: Initial label advertisement to peer 144.0.0.44:0
...
tagcon: peer 144.0.0.44:0 (pp 0x610EEC84): Event down
estab -> destroyed
tagcon: peer 144.0.0.44:0 (pp 0x610EEC84): Event cleanup done
destroyed -> non-ex
The following table describes the significant fields shown in the display.
Table 5 debug mpls ldp peer state-machine Field Descriptions
Field
Description
tagcon:
Identifies the source of the message as the label control subsystem.
a.b.c.d:e
LDP identifier of the peer for the session with the state change.
(pp 0xnnnnnnnn)
Address of the data structure used to represent the peer at the label distribution level. This address is useful for correlating debug output.
Event
E
Event causing the state change.
s1 -> s2
State of the LDP session has changed from state s1 to state s2.
Related Commands
Command
Description
debugmplsldpsessionio
Displays information about LDP messages sent to or received from LDP peers.
showmplsldpneighbor
Displays the status of LDP sessions.
debug mpls ldp prev-label
To display debug information when a local label binding associated with a prefix is withdrawn and freed, use the
debugmplsldpprev-labelcommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
(Optional) Limits the displayed binding information to that allocated for prefixes permitted by a prefix access control list (ACL).
peer-aclacl
(Optional) Limits the displayed binding withdraw information to those Label Distribution Protocol (LDP) peers permitted by a peer ACL.
Command Default
Debugging of previous local label binding changes is disabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(21)ST
This command was introduced.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
Usage Guidelines
Use this command to monitor LDP information when a local label binding associated with a prefix is withdrawn and freed. LDP withdraws a previously advertised label before advertising a new label.
If you enter the
debugmplsldpprev-labelcommand without an optional keyword and argument, the command displays output for all previous label binding changes. Use the
prefix-aclaclorpeer-aclaclkeywords and arguments to limit the output to prefixes defined by the respective ACLs.
Examples
The following is sample output from the
debugmplsldpprev-label command:
Router# debug mpls ldp prev-label
tagcon: Changing state to WITHDRAWN for prefix=10.0.1.1, label31
tagcon: Creating prev_lbl_info for prefix=10.0.1.1, label31
tagcon: noroute hold timer expired for 10.0.1.1/255.255.255.255, tag withdrawn, seqno 47
tagcon: tibent(10.0.1.1/32): label 32 from 10.0.0.2:0 removed
tagcon: Deleting prev label info for prefix = 10.0.1.1, tag = 31
The following table describes the significant fields shown in the display.
Table 6 debug mpls ldp prev-label Field Descriptions
Field
Description
tagcon:
Identifies the source of the message as the label control subsystem.
Changing state to WITHDRAWN
Describes the label binding change; in this case, the label is to be withdrawn.
for prefix=10.0.1.1
The prefix (10.0.1.1) from which the local label binding is to be withdrawn and freed.
label31
The local label binding (31) that is to be withdrawn from the prefix.
tibent(10.0.1.1/32)
The hostname, network, and mask for the destination that has a label binding change.
Related Commands
Command
Description
debugmplsldpbindings
Displays information about addresses and label bindings learned from LDP peers by means of LDP downstream unsolicited label distribution.
debug mpls ldp session io
To display the contents of Label Distribution Protocol (LDP) messages sent to and received from LDP peers, use the
debugmplsldpsessioniocommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplsldpsessionio [all]
[ peer-aclacl ]
nodebugmplsldpsessionio [all]
[ peer-aclacl ]
Syntax Description
all
(Optional) Includes the contents of periodic keepalive messages in the displayed message output to LDP peers.
peer-aclacl
(Optional) Limits the displayed message output to the LDP peers permitted by the access control list (ACL).
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
11.1CT
This command was introduced.
12.0(10)ST
This command was modified to reflect MPLS IETF command syntax and terminology.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
12.1(8a)E
This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(50)SY
This command was integrated into Cisco IOS Release 12.2(50)SY.
Usage Guidelines
Displays the contents of all messages sent and received, except for periodic keepalive messages.
Examples
The following is sample output from the
debugmplsldpsessionio command:
The following table describes the significant fields shown in the display.
Table 7 debug mpls ldp session io Field Descriptions
Field
Description
ldp:
Identifies the source of the message as LDP.
Rcvd xxx msg
Indicates that a message of the specified type has been received.
from a.b.c.d
Host to which the message has been sent. Used in the early stages of the opening of an LDP session when the LDP identifier is not yet known.
Sent xxx msg
Indicates that a message of the specified type has been sent.
to a.b.c.d
Host to which the message has been sent. Used in the early stages of the opening of an LDP session when the LDP identifier is not yet known.
to a.b.c.d:e
LDP identifier of the peer to which the message has been sent.
(pp 0xnnnnnnnn)
Identifies the data structure used to represent the peer at the label distribution level. Useful for correlating debug output.
LDP xxx msg
Type of message that has been sent.
PDU hdr: LDP Id: a.b.c.d:e
LDP identifier of the sender included in the LDP protocol data unit (PDU) header.
Msg contents: 0xnn ... 0xnn
Contents of the message represented as a sequence of bytes.
Related Commands
Command
Description
debugmplsldpmessages
Displays specific information (such as message type, source, and destination) regarding LDP messages sent to and received from LDP peers.
debugmplsldpsessionstate-machine
Displays information about state transitions for LDP sessions.
debug mpls ldp session protection
To enable the display of events related to MPLS LDP Session
Protection, use the
debugmplsldpsessionprotectioncommand in privileged EXEC mode. To disable this feature, use
the
no form of this command.
debugmplsldpsessionprotection
[ peer-aclacl ]
nodebugmplsldpsessionprotection
[ peer-aclacl ]
Syntax Description
peer-aclacl
(Optional) Enables the display of events for the peers
whose router IDs are listed in the access control list.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(30)S
This command was introduced.
12.3(14)T
This command was integrated into Cisco IOS Release
12.3(14)T.
12.2(28)SB
This command was integrated into Cisco IOS Release
12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release
12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release
12.2(33)SXH.
Examples
In the following example, the display of events related to MPLS LDP
Session Protection are enabled:
Router# debug mpls ldp session protection
Related Commands
Command
Description
clearmplsldpneighbor
Forcibly resets an LDP session.
showmplsldpneighbor
Displays the contents of the LDP.
debug mpls ldp session state-machine
To display information about state transitions for label distribution protocol (LDP) sessions, use the
debugmplsldpsessionstate-machinecommand in privileged EXEC mode. To disable this feature, use the no form of this command.
The following table describes the significant fields shown in the display.
Table 8 debug mpls ldp session state-machine Field Descriptions
Field
Description
ldp:
Identifies the source of the message as LDP.
ptcl_adj:a.b.c.d
Identifies the network address of the LDP peer.
(0xnnnnnnnn)
Identifies the data structure used to represent the peer at the protocol level. Useful for correlating debug output.
Event:
E
Event that caused the state transition.
s1 -> s2
State of the LDP session has changed from state s1 to state s2.
Related Commands
Command
Description
debugmplsldppeerstate-machine
Displays information about state transitions for LDP sessions.
debug mpls ldp targeted-neighbors
To display information about the target neighbor mechanism, use the
debugmplsldptargeted-neighborscommand in privileged EXEC mode. This mechanism establishes label distribution protocol (LDP) adjacencies to peers that are not directly adjacent, such as peers at either end of a tunnel. To disable this feature, use the no form of this command.
debugmplsldptargeted-neighbors
nodebugmplsldptargeted-neighbors
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.0(10)ST
This command was modified to reflect MPLS IETF command syntax and terminology.
12.0(14)ST
This command was integrated into Cisco IOS Release 12.0(14)ST.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
12.1(8a)E
This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.0(21)ST
This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.0(23)S
This command was integrated into Cisco IOS Release 12.0(23)S.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Platforms that are not directly connected may engage in LDP label distribution (for example, to support two-level labeling across an LSP tunnel).
An LDP session between nondirectly connected label switch routers (LSRs) is called a targeted session and is supported by LDP extended discovery which uses targeted Hello messages sent to specific IP addresses.
An LSR (Router 1) attempting to initiate an LDP targeted session with another LSR (Router 2) sends targeted Hello messages sent to a specific IP address of Router 2. If the configuration of Router 2 permits it to respond to targeted Hello messages from Router 1, it does so, and the LDP session can be established. In this situation, Router 1 is said to be an active LSR for the targeted session because it initiated the targeted Hello messages; Router 2 is said to be a passive LSR for the session because it responded to them.
As with LDP sessions between two directly connected LSRs, it is possible for a targeted session to be the result of multiple discovery activities which are targeted to different IP addresses for the same LSR. In addition, it is possible for both LSRs in a targeted session to be active and for both to be passive.
The debug messages enabled by debug mpls ldp targeted-neighbors report activity relating to targeted sessions.
Examples
The following shows sample output from the
debugmplsldptargeted-neighborscommand:
The following table describes the significant fields shown in the display.
Table 9 debug mpls ldp targeted-neighbors Field Descriptions
Field
Description
ldp-trgtnbr:
Identifies this as an LDP targeted neighbor debug statement.
144.0.0.44
IP address for the targeted neighbor.
Related Commands
Command
Description
showmplsldpneighbor
Displays the status of LDP protocol sessions.
debug mpls ldp transport connections
To display information about the Transmission Control Protocol (TCP) connections used to support label distribution protocol (LDP) sessions, use the
debugmplsldptransportconnectionscommand in privilegedEXEC mode. To disable this feature, use the no form of this command.
(Optional) Limits the displayed information to that for LDP peers permitted by the access control list (acl).
interfaceinterface
(Optional) Limits the displayed information to that for the specified interface.
Command Default
Display information about LDP TCP connection activity for all peers and all interfaces.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.0(10)ST
This command was modified to reflect MPLS IETF command syntax and terminology.
12.0(14)ST
This command was integrated into Cisco IOS Release 12.0(14)ST.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
12.1(8a)E
This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.0(21)ST
This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.0(23)S
This command was integrated into Cisco IOS Release 12.0(23)S.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use this command to monitor LDP activity relating to the establishment of the transport (TCP) connection for LDP sessions.
When two devices establish a TCP connection for an LDP session, the device with the larger transport address plays an active role and the other plays a passive role. The active device attempts to establish a TCP connection to the well-known LDP port at the passive device. The passive device waits for the connection to the well-known port to be established.
Examples
The following shows sample output from the
debugmplsldptransportconnections command:
Router#debug mpls ldp transport connections
Debug output at active peer:
ldp: Opening listen port 646 for 144.0.0.44, 34.0.0.44
ldp: Open LDP listen TCB 0x60E105BC; lport = 646; fhost = 144.0.0.44
ldp: Add listen TCB to list; tcb 0x60E105BC; addr 144.0.0.44
ldp: Incoming ldp conn 133.0.0.33:646 <-> 144.0.0.44:11042
ldp: create ptcl_adj: tp = 0x610ECD64, ipaddr = 144.0.0.44
Debug output at passive peer:
ldp: Opening ldp conn; adj 0x60BAC33C, 144.0.0.44 <-> 133.0.0.33
ldp: ldp conn is up; adj 0x60BAC33C, 144.0.0.44:11042 <-> 133.0.0.33:646
The following table describes the significant fields shown in the display.
Table 10 debug mpls ldp transport connections Field Descriptions
Field
Description
ldp:
Identifies the source of the message as LDP.
adj 0xnnnnnnnn
Identifies the data structure used to represent the peer at the transport level. Useful for correlating debug output.
a.b.c.d -> p.q.r.s
Indicates a TCP connection between a.b.c.d and p.q.r.s.
a.b.c.d:x -> p.q.r.s:y
Indicates a TCP connection between a.b.c.d, port x and p.q.r.s, port y.
Related Commands
Command
Description
debugmplsldptransportevents
Prints information about the events related to the LDP peer discovery mechanism.
debug mpls ldp transport events
To display information about events related to the label distribution protocol (LDP) peer discovery mechanism, use the
debugmplsldptransporteventscommand in privilegedEXEC mode. This mechanism is used to determine the devices with which you wish to establish LDP sessions. To disable this feature, use the no form of this command.
(Optional) Limits the displayed information to that for LDP peers permitted by the access control list (acl).
interface
(Optional) Limits the displayed information to that for the specified interface.
Command Default
Displays information about LDP discovery activity for all peers and all interfaces.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.0(10)ST
This command was modified to reflect MPLS IETF command syntax and terminology.
12.0(14)ST
This command was integrated into Cisco IOS Release 12.0(14)ST.
12.1(2)T
This command was integrated into Cisco IOS Release 12.1(2)T.
12.1(8a)E
This command was integrated into Cisco IOS Release 12.1(8a)E.
12.2(2)T
This command was integrated into Cisco IOS Release 12.2(2)T.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
12.0(21)ST
This command was integrated into Cisco IOS Release 12.0(21)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.0(23)S
This command was integrated into Cisco IOS Release 12.0(23)S.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use this command to monitor LDP discovery activity.
This command might generate a great deal of output. Use the peer-acl option or interface option, or both, to limit the output to peers or interfaces of interest.
Note
The command includes all of the output generated by the debug mpls ldp transport connection command.
Examples
The following shows sample output from thedebugmplsldptransportevents command:
Router#debug mpls ldp transport events
ldp: enabling ldp on Ethernet1/1/1
ldp: Set intf id: intf 0x611D684C, Ethernet1/1/1, not lc-atm, intf_id 0
ldp: Set intf id: intf 0x617C5638, ATM0/0.2, not lc-atm, intf_id 0
ldp: Send ldp hello; ATM3/0.1, src/dst 8.1.1.1/224.0.0.2, inst_id 1, tcatm
ldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt 0x8, tcatm
ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0
ldp: Rcvd ldp hello; Ethernet1/1/1, from 10.105.0.9 (7.1.1.1:0), intf_id 0, opt 0xC
ldp: ldp Hello from 10.105.0.9 (7.1.1.1:0) to 224.0.0.2, opt 0xC
ldp: New adj 0x617C5EBC from 10.105.0.9 (7.1.1.1:0), Ethernet1/1/1
ldp: Opening ldp conn; adj 0x617C5EBC, 8.1.1.1 <-> 7.1.1.1
ldp: ldp conn is up; adj 0x617C5EBC, 8.1.1.1:11013 <-> 7.1.1.1:646
ldp: Send ldp hello; ATM3/0.1, src/dst 8.1.1.1/224.0.0.2, inst_id 1, tcatm
ldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt 0x8, tcatm
ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0
ldp: Rcvd ldp hello; Ethernet1/1/1, from 10.105.0.9 (7.1.1.1:0), intf_id 0, opt 0xC
...
ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0
ldp: Send ldp hello; ATM3/0.1, src/dst 8.1no tag ip
.0.2, inst_id 1, tcatm
ldp: disabling ldp on Ethernet1/1/1
ldp: Hold timer expired for adj 0x617C5EBC, will close conn
ldp: Closing ldp conn 8.1.1.1:11013 <-> 7.1.1.1:646, adj 0x617C5EBC
ldp: Adjacency 0x617C5EBC, 10.105.0.9 timed out
ldp: Adj 0x617C5EBC; state set to closed
ldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt 0x8, tcatm
ldp: Ignore Hello from 10.105.0.9, Ethernet1/1/1; no intf
The following table describes the significant fields shown in the display.
Table 11 debug mpls ldp transport events Field Descriptions
Field
Description
ldp:
Identifies the source of the message as LDP.
adj 0xnnnnnnnn
Identifies the data structure used to represent the peer at the transport level. Useful for correlating debug output.
a.b.c.d (p.q.r.s:n)
Network address and LDP identifier of the peer.
intf_id
Interface identifier (non-zero for LC-ATM interfaces; 0 otherwise).
opt 0xn
Bits that describe options in the LDP discovery Hello packet:
0x1--Targeted Hello option
0x2--Send targeted Hello option
0x4--Transport address option
0x8--LDP Hello message (as opposed to TDP Hello message)
Related Commands
Command
Description
debugmplsldptransportconnections
Displays information about the TCP connections used to support LDP sessions.
showmplsldpdiscovery
Displays the status of the LDP discovery process.
debug mpls lfib cef
To print detailed information about label rewrites being created, resolved, and deactivated as Cisco Express Forwarding (CEF) routes are added, changed, or removed, use the
debugmplslfibcef command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplslfibcef
nodebugmplslfibcef
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Several lines of output are produced for each route placed into the label-forwarding information base (LFIB). If your router has thousands of labeled routes, be careful about issuing this command. When label switching is first enabled, each of these routes is placed into the LFIB, and several lines of output are displayed for each route.
Examples
The following is sample output from the
debugmplslfibcefcommand:
Router# debug mpls lfib cef
Cisco Express Forwarding related TFIB services debugging is on
tagcon: tc_ip_rtlookup fail on 10.0.0.0/8:subnet_lookup failed
TFIB: route tag chg 10.7.0.7/32,idx=1,inc=Withdrn,outg=Withdrn,enabled=0x2
TFIB: fib complete delete: prefix=10.7.0.7/32,inc tag=26,delete_info=1
TFIB: deactivate tag rew for 10.7.0.7/32,index=0
TFIB: set fib rew: pfx 10.7.0.7/32,index=0,add=0,tag_rew->adj=Ethernet2/3
TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parent
TFIB: fib scanner start:needed:1,unres:0,mac:0,loadinfo:0
TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parent
TFIB: fib upd loadinf 10.100.100.100/32,tag=Tun_hd,fib no loadin,tfib no loadin
TFIB: fib check cleanup for 10.100.100.100/32,index=0,return_value=0
TFIB: fib_scanner_end
TFIB: create dynamic entry for 10.11.0.11/32
TFIB: call find_route_tags,dist_method=1,next_hop=10.93.0.11,Et2/3
TFIB: route tag chg 10.11.0.11/32,idx=0,inc=26,outg=Unkn,enabled=0x3
TFIB: create tag info 10.11.0.11/32,inc tag=26,has no info
TFIB: resolve tag rew,prefix=10.11.0.11/32,has tag_info,no parent
TFIB: finish fib res 10.11.0.11/32:index 0,parent outg tag no parent
TFIB: fib upd loadinf 10.11.0.11/32,tag=26,fib no loadin,tfib no loadin
TFIB: set fib rew: pfx 10.11.0.11/32,index=0,add=1,tag_rew->adj=Ethernet2/3
tagcon: route_tag_change for: 10.250.0.97/32
intag 33, outtag 28, nexthop tsr 10.11.0.11:0
TFIB: route tag chg 10.250.0.97/32,idx=0,inc=33,outg=28,enabled=0x3
TFIB: deactivate tag rew for 10.250.0.97/32,index=0
TFIB: set fib rew: pfx 10.250.0.97/32,index=0,add=0,tag_rew->adj=Ethernet2/3
TFIB: create tag info 10.250.0.97/32,inc tag=33,has old info
On VIP:
TFIB: route tag chg 10.13.72.13/32,idx=0,inc=34,outg=Withdrn,enabled=0x3
TFIB: deactivate tag rew for 10.13.72.13/32,index=0
TFIB: set fib rew: pfx 10.13.72.13/32,index=0,add=0,tag_rew->adj=
TFIB: create tag info 10.13.72.13/32,inc tag=34,has old info
TFIB: resolve tag rew,prefix=10.13.72.13/32,has tag_info,no parent
TFIB: finish fib res 10.13.72.13/32:index 0,parent outg tag no parent
TFIB: set fib rew: pfx 10.100.100.100/32,index=0,add=0,tag_rew->adj=
TFIB: create tag info 10.100.100.100/32,inc tag=37,has old info
TFIB: resolve tag rew,prefix=10.100.100.100/32,has tag_info,no parent
TFIB: finish fib res 10.100.100.100/32:index 0,parent outg tag no parent
TFIB: fib upd loadinf 10.100.100.100/32,tag=37,fib no loadin,tfib no loadin
The following table lists the significant fields and a description of special labels that appear in the output of this
debug command shown in the display.
Table 12 debug mpls lfib cef Field Descriptions
Field
Description
tagcon
The name of the subsystem issuing the debug output (Label Control).
LFIB
The name of the subsystem issuing the debug output.
tc_ip_rtlookup fail on x.y.w.z/m: subnet_lookup failed
The destination with IP address and mask shown is not in the routing table.
route tag chg x.y.w.z/m
Request to create the LFIB entry for the specified prefix/mask.
idx=-1
The index within the FIB entry of the path whose LFIB entry is being created. The parameter -1 means all paths for this FIB entry.
inc=s
Incoming label of the entry being processed.
outg=s
Outgoing label of the entry being processed.
enabled=0xn
Bit mask indicating the types of label switching currently enabled:
0x1 = dynamic
0x2 = TSP tunnels
0x3 = both
fib complete delete
Indicates that the FIB entry is being deleted.
prefix=x.y.w.z/m
A destination prefix.
delete_info=1
Indicates that label_info is also being deleted.
deactivate tag rew for x.y.w.z/m
Indicates that label rewrite for specified prefix is being deleted.
index=n
Index of path in the FIB entry being processed.
set fib rew: pfx x.y.w.z/m
Indicates that label rewrite is being installed or deleted from the FIB entry for the specified destination for label imposition purposes.
add=0
Indicates that label rewrite is being deleted from the FIB (no longer imposing labels).
tag_rew->adj=s
Adjacency of label rewrite for label imposition.
resolve tag rew,prefix=x.y.w.z/m
Indicates that the FIB route to the specified prefix is being resolved.
no tag_info
Indicates that there is no label_info for the destination (destination not labeled).
no parent
Indicates that the route is not recursive.
fib scanner start
Indicates that the periodic scan of the FIB has started.
needed:1
Indicates that the LFIB needs the FIB to be scanned.
unres:n
Indicates the number of unresolved TFIB entries.
mac:n
Indicates the number of TFIB entries missing MAC strings.
loadinfo:n
Indicates whether the nonrecursive accounting state has changed and whether the loadinfo information in the LFIB needs to be adjusted.
fib upd loadinf x.y.w.z/m
Indicates that a check for nonrecursive accounting is being made and that the LFIB loadinfo information for the specified prefix is being updated.
tag=s
Incoming label of entry.
fib no loadin
Indicates that the corresponding FIB entry has no loadinfo.
tfib no loadin
Indicates that the LFIB entry has no loadinfo.
fib check cleanup for x.y.w.z/m
Indicates that a check is being made on the LFIB entry for the specified destination to determine if rewrite needs to be removed from the LFIB.
return_value=x
If x is 0, indicates that no change has occurred in the LFIB entry. If x is 1, there was a change.
fib_scanner_end
Indicates that the FIB scan has come to an end.
create dynamic entry for x.y.w.z/m
Indicates that the LFIB has been enabled and that an LFIB entry is being created for the specified destination.
call find_route_tags
Indicates that the labels for that destination are being requested.
dist_method=n
Identifies the label distribution method--TDP, TC-ATM, and so on.
next_hop=x.y.z.w
Identifies the next hop for the destination.
interface name
Identifies the outgoing interface for the destination.
create tag info
Indicates that a label_info data structure is being created for the destination.
has no info
Indicates that the destination does not already have label_info.
finish fib re x.y.z.w/m
Indicates that the LFIB entry for the specified route is being completed.
parent outg tag s
If recursive, specifies the outgoing label of the route through which it is recursive (the parent). If not recursive, s = “no parent.”
tagcon: route_tag_change for: x.y.z.w/m
Indicates that label control is notifying LFIB that labels are available for the specified destination.
intag s
Identifies the incoming label for the destination.
outtag s
Identifies the outgoing label for the destination.
nexthop tsr x.y.z.w.i
Identifies the TDP ID of the next hop that sent the tag.
Related Commands
Command
Description
debugmplslfiblsp
Prints detailed information about label rewrites being created and deleted as LSP tunnels are added or removed.
debugmplslfibstate
Traces what happens when label switching is enabled or disabled.
debugmplslfibstruct
Traces the allocation and freeing of LFIB-related data structures, including the LFIB itself, label rewrites, and label_info data.
debug mpls lfib enc
To print detailed information about label encapsulations while label rewrites are created or updated and placed in the label-forwarding information base (LFIB), use the
debugmplslfibenc command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplslfibenc
nodebugmplslfibenc
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Several lines of output are produced for each route placed into the LFIB. If your router has thousands of labeled routes, issue this command with care. When label switching is first enabled, each of these routes is placed into the LFIB and a label encapsulation is created. The command output shows you on which adjacency the label rewrite is being created and the labels assigned.
Examples
The following is sample output from the
debugmplslfibenc command. This example shows the encapsulations for three routes that have been created and placed into the LFIB.
Router# debug mpls lfib enc
TFIB: finish res:inc tag=28,outg=Imp_null,next_hop=10.93.72.13,Ethernet4/0/3
TFIB: update_mac, mac_length = 14,addr=10.93.72.13,idb=Ethernet4/0/3
TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7
TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79
TFIB: encaps:inc=28,outg=Imp_null,idb:Ethernet4/0/3,sizes 14,14,1504,type 0
TFIB: finish res:inc tag=30,outg=27,next_hop=10.93.72.13,Ethernet4/0/3
TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7
TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79
TFIB: encaps:inc=30,outg=27,idb:Ethernet4/0/3,sizes 14,18,1500,type 0
TFIB: finish res:inc tag=30,outg=10,next_hop=0.0.0.0,ATM0/0.1
TFIB: get ip adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=7
TFIB: get tag adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=79
TFIB: encaps:inc=30,outg=10,idb:ATM0/0,sizes 4,8,4470,type 1
The following table describes the significant fields shown in the display.
Table 13 debug mpls lfib enc Field Descriptions
Field
Description
TFIB
Identifies the source of the message as the LFIB subsystem.
finish res
Identifies that the LFIB resolution is being finished.
inc tag=x or inc=x
An incoming (local) label for the LFIB entry is being created. Labels can be numbers or special values.
outg=y
An outgoing (remote) label for the LFIB entry is being created.
next_hop=a.b.c.d
IP address of the next hop for the destination.
interface
The outgoing interface through which a packet will be sent.
get ip adj
Identifies that the IP adjacency to use in the LFIB entry is being determined.
get tag adj
Identifies that the label switching adjacency to use for the LFIB entry is being determined.
addr = a.b.c.d
The IP address of the adjacency.
is_p2p=x
If x is 1, this is a point-to-point adjacency. If x is 0, it is not.
fibidb = s
Indicates the interface of the adjacency.
linktype = x
The link type of the adjacency, as follows:
7 = LINK_IP
79 = LINK_TAG
sizes x,y,z
Indicates the following values:
x = length of macstring
y = length of tag encapsulation
z = tag MTU
type = x
Tag encapsulation type, as follows:
0 = normal
1 = TCATM
2 = TSP tunnel
idb:s
Indicates the outgoing interface.
update_mac
Indicates that the macstring of the adjacency is being updated.
The following table describes the special labels, which sometimes appear in the debug output, and their meanings.
Table 14 Special Labels Appearing in debug Command Output
Special Label
Meaning
Unassn--Inital value
No label assigned yet.
Unused
This destination does not have a label (for example, a BGP route).
Withdrn
The label for this destination has been withdrawn.
Unkn
This destination should have a label, but it is not yet known.
Get_res
A recursive route that will get a label when resolved.
Prints detailed information about label rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed.
debugmplslfiblsp
Prints detailed information about label rewrites being created and deleted as LSP tunnels are added or removed.
debugmplslfibstate
Traces what happens when label switching is enabled or disabled.
debugmplslfibstruct
Traces the allocation and freeing of LFIB-related data structures, including the LFIB itself, label rewrites, and label_info data.
debug mpls lfib fast-reroute database
To enable debugging information about changes to the fast reroute database, use the debug mpls lfib fast-reroute database command in privileged EXEC command. To disable debugging output, use to no form of this command.
debugmplslfibfast-reroutedatabase
nodebugmplslfibfast-reroutedatabase
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(10)ST
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Because using debug commands can use a great deal of bandwidth on your system, use caution when enabling the debug mpls lfib fast-reroute database command.
Examples
The following example displays debugging output for in Fast Reroute processing:
Router# debug mpls lfib fast-reroute database
LFIB-FRR:Clear headend FRR info for Tunnel1
LFIB-FRR:FRR info for Tunnel1 changed
LFIB-FRR:update headend FRR info for 10.8.0.1/32
LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):destroying entry for 10.8.0.1/32... [514 left]
LFIB-FRR:item B13D94 [Tu1]:removed from name tree
LFIB-FRR:item B13D94 [Tu1]:removed from group PO0/0->Tu4000 tree
%LINK-5-CHANGED:Interface Tunnel1, changed state to administratively down
LFIB-FRR:Clear headend FRR info for Tunnel1
LFIB-FRR:FRR info for Tunnel1 changed
LFIB-FRR:Clear headend FRR info for Tunnel1
LFIB-FRR:FRR info for Tunnel1 changed
LFIB-FRR:Set headend FRR info for Tunnel1 {main=PO0/0,backup=Tu4000,label=18}
LFIB-FRR:FRR info for Tunnel1 changed
%SYS-5-CONFIG_I:Configured from console by console
LFIB-FRR:update headend FRR info for 10.8.0.1/32
LFIB-FRR:item B13D94 [Tu1]:inserted in name tree
LFIB-FRR:item B13D94 [Tu1]:inserted in group PO0/0->Tu4000 tree
LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):full entry created for 10.8.0.1/32 [total 515]
LFIB-FRR:update headend FRR info for 10.8.0.1/32
LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):updating entry for 10.8.0.1/32...
LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):... updated
%LINK-3-UPDOWN:Interface Tunnel1, changed state to up
LFIB-FRR:update headend FRR info for 10.43.0.0/16
LFIB-FRR:item B04C2C [Tu486]:inserted in name tree
LFIB-FRR:item B04C2C [Tu486]:inserted in group PO0/0->Tu4000 tree
LFIB-FRR:item B04C2C [Tu486] (group PO0/0->Tu4000):full entry created for 10.43.0.0/16 [total 516]
LFIB-FRR:update headend FRR info for 10.43.0.0/16
LFIB-FRR:item B04BB4 [Tu481]:inserted in name tree
LFIB-FRR:item B04BB4 [Tu481]:inserted in group PO0/0->Tu4000 tree
LFIB-FRR:item B04BB4 [Tu481] (group PO0/0->Tu4000):full entry created for 10.43.0.0/16 [total 517]
LFIB-FRR:update headend FRR info for 10.2.0.0/16
LFIB-FRR:item B04B3C [Tu486]:inserted in name tree
LFIB-FRR:item B04B3C [Tu486]:inserted in group PO0/0->Tu4000 tree
LFIB-FRR:item B04B3C [Tu486] (group PO0/0->Tu4000):full entry created for 10.2.0.0/16 [total 518]
LFIB-FRR:update headend FRR info for 10.2.0.0/16
LFIB-FRR:item B04AC4 [Tu481]:inserted in name tree
LFIB-FRR:item B04AC4 [Tu481]:inserted in group PO0/0->Tu4000 tree
Related Commands
Command
Description
debugmplstraffic-engtunnelsfast-rerouteevents
Displays debugging information about fast reroute events.
debugmplstraffic-engtunnelsfast-reroutereroutes
Displays debugging information about the rerouting of traffic from link-protected interfaces to backup tunnels.
debug mpls lfib fast-reroute events
To display debugging information about fast reroute events, use the debug mpls lfib fast-reroute events command in privileged EXEC command. To disable debugging output, use to no form of this command.
debugmplslfibfast-rerouteevents
nodebugmplslfibfast-rerouteevents
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(10)ST
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Because using debug commands can use a great deal of bandwidth on your system, use caution when enabling the debug mpls lfib fast-reroute events command.
Examples
The following example reports on the rerouting of traffic to a backup tunnel because of a change of state at a link-protected physical interface.
Router# debug mpls lfib fast-reroute events
LFIB-FRR:enqueued interface DOWN event for PO0/0 (Up)
LFIB-FRR:discarded interface DOWN event for PO0/0 (Up)
LFIB-FRR:processing interface DOWN event for PO0/0 (Up)
LFIB-FRR:group PO0/0->Tu4000:output if fixup:Backup(Tu4000) -> Backup(Tu4000)
Note
The state given in parentheses reflects what the FRR database currently understands to be the state of the physical interface. This may or may not be the same as the event state reported earlier on that same display line.
Related Commands
Command
Description
debugmplstraffic-engtunnelsfast-reroutedatabase
Displays debugging information about changes to the fast reroute database.
debugmplstraffic-engtunnelsfast-reroutereroutes
Displays debugging information about the rerouting of traffic from link-protected interfaces to backup tunnels.
debug mpls lfib fast-reroute reroutes
To enable debugging information about the rerouting of protected Label Forwarding Information Base (LFIB) entries between the primary and backup outgoing interfaces, use the debug mpls lfib fast-reroute reroutes command in privileged EXEC command. To disable debugging output, use to no form of this command.
debugmplslfibfast-reroutereroutes
nodebugmplslfibfast-reroutereroutes
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(10)ST
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Because using debug commands can use a great deal of bandwidth on your system, use caution when enabling the debug mpls lfib fast-reroute reroutes command. The output of this command increases in proportion to the number of tunnels that utilize fast reroute.
Examples
The following example reports the results of reroute attempts:
Router# debug mpls lfib fast-reroute reroutes
LFIB-FRR:item B0E844 [Tu139]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0E8BC [Tu138]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0E934 [Tu387]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0E9AC [Tu137]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0EA24 [Tu136]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0EA9C [Tu135]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0EB14 [Tu384]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0EB8C [Tu134]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0EC04 [Tu133]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
LFIB-FRR:item B0EC7C [Tu132]:output if fixup, Main(PO0/0) -> Backup(Tu4000), succeeded
Related Commands
Command
Description
debugmplstraffic-engtunnelsfast-reroutedatabase
Displays debugging information about changes to the fast reroute database.
debugmplstraffic-engtunnelsfast-rerouteevents
Displays debugging information about fast reroute events.
debug mpls lfib lsp
To print detailed information about label rewrites being created and deleted as label-switched path ( LSP) tunnels are added or removed, use the
debugmplslfiblsp command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplslfiblsp
nodebugmplslfiblsp
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following is sample output from the
debugmplslfiblsp command:
Router# debug mpls lfib lsp
TSP-tunnel related TFIB services debugging is on
TFIB: tagtun,next hop=10.93.72.13,inc=35,outg=1,idb=Et4/0/3
TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=7,nh=10.93.72.13
TFIB: tagtun,next hop=10.92.0.7,inc=36,outg=1,idb=Et4/0/2
TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun tag chg linec,fiblc=0,in tg=36,o tg=1,if=6,nh=10.92.0.7
TFIB: tagtun_delete, inc = 36
tagtun tag del linec,itag=12
TFIB: tagtun_delete, inc = 35
tagtun tag del linec,itag=12
TFIB: tagtun,next hop=10.92.0.7,inc=35,outg=1,idb=Et4/0/2
TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=6,nh=10.92.0.7
On VIP:
TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7
TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6
TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7
TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6
TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.92.0.7,if=6
TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
The following table describes the significant fields shown in the sample display.
Table 15 debug mpls lfib lsp Field Descriptions
Field
Description
tagtun
Name of routine entered.
next hop=x.y.z.w
Next hop for the tunnel being created.
inc=x
Incoming label for this hop of the tunnel being created.
outg=x
Outgoing label (1 means Implicit Null label).
idb=s
Outgoing interface for the tunnel being created.
if_number=7
Interface number of the outgoing interface.
tsptunnel
Name of the routine entered.
tsptun update loadinfo
The procedure being performed.
tag=x
Incoming label of the LFIB slot whose loadinfo is being updated.
loadinfo_reqd=x
Indicates whether a loadinfo is expected for this entry (non-recursive accounting is on).
no new loadinfo
No change required in loadinfo.
no old loadinfo
No previous loadinfo available.
tagtun tag chg linec
Line card is being informed of the TSP tunnel.
fiblc=x
Indicates which line card is being informed (0 means all).
in tg=x
Indicates the incoming label of new TSP tunnel.
o tg=x
Indicates the outgoing label of new TSP tunnel.
if=x
Indicates the outgoing interface number.
nh=x.y.w.z
Indicates the next hop IP address.
tagtun_delete
Indicates that a procedure is being performed: delete a TSP tunnel.
tagtun tag del linec
Informs the line card of the TSP tunnel deletion.
tagtun chg msg
Indicates that the line card has received a message to create a TSP tunnel.
Related Commands
Command
Description
debugmplslfibcef
Prints detailed information about label rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed.
debugmplslfibstate
Traces what happens when label switching is enabled or disabled.
debugmplslfibstruct
Traces the allocation and freeing of LFIB-related data structures, including the LFIB itself, label rewrites, and label_info data.
debug mpls lfib state
To trace what happens when label switching is enabled or disabled, use the
debugmplslfibstatecommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplslfibstate
nodebugmplslfibstate
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use this command when you wish to trace what happens to the label-forwarding information base (LFIB) when you issue the
mplsip or the
mplstsp-tunnel command.
Examples
The following is sample output from the
debugmplslfibstate command:
Router# debug mpls lfib state
TFIB enable/disable state debugging is on
TFIB: Upd tag sb 6(status:0xC1,tmtu:1500,VPI:1-1 VC=0/32,et:0/0/0),lc 0x0
TFIB: intf status chg: idb=Et4/0/2,status=0xC1,oldstatus=0xC3
TFIB: interface dyntag change,change in state to Ethernet4/0/2
TFIB: enable entered, table exists,enabler type=0x2
TFIB: enable, TFIB already enabled, types now 0x3,returning
TFIB: enable entered, table exists,enabler type=0x1
TFIB: disable entered, table exists,type=0x1
TFIB: cleanup: tfib[32] still non-0
On linecard only:
TFIB: disable lc msg recvd, type=0x1
TFIB: Ethernet4/0/1 fibidb subblock message received
TFIB: enable lc msg recvd, type=0x1
TFIB: Tunnel301 set encapfix to 0x6016A97C
The following table describes the significant fields shown in the display.
Table 16 debug mpls lfib state Field Descriptions
Field
Description
LFIB
Identifies the source of the message as the LFIB subsystem.
Upd tag sb x
Indicates that the status of the “xth” label switching sub-block is being updated, where x is the interface number. There is a label switching sub-block for each interface on which label switching has been enabled.
Identifies the values of the fields in the label switching sub-block, as follows:
status byte
maximum transmission unit (tmtu)
range of ATM VPs
control VP
control VC (if this is a TC-ATM interface)
encapsulation type (et)
encapsulation information
tunnel interface number (lc)
line card number to which the update message is being sent (0 means all line cards)
intf status chg
Indicates that there was an interface status change.
idb=Et4/0/2
Identifies the interface whose status changed.
status=0xC1
Indicates the new status bits in the label switching sub-block of the idb.
oldstatus=0xC3
Indicates the old status bits before the change.
interface dyntag change, change in state to Ethernet4/0/2
Indicates that there was a change in the dynamic label status for the particular interface.
enable entered
Indicates that the code that enables the LFIB was invoked.
TFIB already enabled
Indicates that the LFIB was already enabled when this call was made.
table exists
Indicates that an LFIB table had already been allocated in a previous call.
cleanup: tfib[x] still non-0
Indicates that the LFIB is being deleted, but that slot x is still active.
disable lc mesg recvd, type=0x1
Indicates that a message to disable label switching type 1 (dynamic) was received by the line card.
disable entered, table exists,type=0x1
Indicates that a call to disable dynamic label switching was issued.
Ethernet4/0/1 fibidb subblock message received
Indicates that a message giving fibidb status change was received on the line card.
enable lc msg recvd,type=0x1
Indicates that the line card received a message to enable label switching type 1 (dynamic).
Tunnel301 set encapfix to 0x6016A97C
Shows that fibidb Tunnel301 on the line card received an encapsulation fixup.
types now 0x3, returning
Shows the value of the bitmask indicating the type of label switching enabled on the interface, as follows:
0x1--means dynamic label switching
0x2--means tsp-tunnels
0x3--means both
Related Commands
Command
Description
debugmplslfibcef
Prints detailed information about label rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed.
debugmplslfiblsp
Prints detailed information about label rewrites being created and deleted as LSP tunnels are added or removed.
debugmplslfibstruct
Traces the allocation and freeing of LFIB-related data structures, including the LFIB itself, label rewrites, and label_info data.
debug mpls lfib struct
To trace the allocation and freeing of label-forwarding information base ( LFIB)-related data structures, such as the LFIB itself, label rewrites, and label_info data, use the
debugmplslfibstruct command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplslfibstruct
nodebugmplslfibstruct
Syntax Description
This command has no keywords or arguments.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following is sample output from the
debugmplslfibstruct command:
Router# debug mpls lfib struct
TFIB data structure changes debugging is on
TFIB: delete tag rew, incoming tag 32
TFIB: remove from tfib,inc tag=32
TFIB: set loadinfo,tag=32,no old loadinfo,no new loadinfo
TFIB: TFIB not in use. Checking for entries.
TFIB: cleanup: tfib[0] still non-0
TFIB: remove from tfib,inc tag=Tun_hd
TFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo
TFIB: TFIB freed.
TFIB: enable, TFIB allocated, size 4024 bytes, maxtag = 500
TFIB: create tag rewrite: inc Tun_hd,outg Unkn
TFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0
TFIB: delete tag rew, incoming tag Tun_hd
TFIB: remove from tfib,inc tag=Tun_hd
TFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo
TFIB: create tag rewrite: inc Tun_hd,outg Unkn
TFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0
TFIB: create tag rewrite: inc 26,outg Unkn
TFIB: add to tfib at 26, first in circular list, mac=0,enc=0
TFIB: add to tfib at 27, added to circular list, mac=0,enc=0
TFIB: delete tag rew, incoming tag Tun_hd
TFIB: remove from tfib,inc tag=Tun_hd
TFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo
TFIB: add to tfib at 29, added to circular list, mac=4,enc=8
TFIB: delete tag rew, incoming tag 29
TFIB: remove from tfib,inc tag=29
The following table describes the significant fields shown in the display.
Table 17 debug mpls lfib struct Field Descriptions
Field
Description
TFIB
The subsystem issuing the message.
delete tag rew
A label rewrite is being freed.
remove from tfib
A label rewrite is being removed from the LFIB.
inc tag=s
The incoming label of the entry being processed.
set loadinfo
The loadinfo field in the LFIB entry is being set (used for nonrecursive accounting).
tag=s
The incoming label of the entry being processed.
no old loadinfo
The LFIB entry did not have a loadinfo before.
no new loadinfo
The LFIB entry should not have a loadinfo now.
TFIB not in use. Checking for entries.
Label switching has been disabled and the LFIB is being freed up.
cleanup: tfib[x] still non-0
The LFIB is being checked for any entries in use, and entry x is the lowest numbered slot still in use.
TFIB freed
The LFIB table has been freed.
enable, TFIB allocated, size x bytes, maxtag = y
Label switching has been enabled and an LFIB of x bytes has been allocated. The largest legal label is y.
create tag rewrite
A label rewrite is being created.
inc s
The incoming label.
outg s
The outgoing label.
add to tfib at s
A label rewrite has been placed in the LFIB at slots.
first in circular list
This LFIB slot had been empty and this is the first rewrite in the list.
mac=0,enc=0
Length of the MAC string and total encapsulation length, including labels.
added to circular list
A label rewrite is being added to an LFIB slot that already had an entry. This rewrite is being inserted in the circular list.
Related Commands
Command
Description
debugmplslfibcef
Prints detailed information about label rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed.
debugmplslfiblsp
Prints detailed information about label rewrites being created and deleted as LSP tunnels are added or removed.
debugmplslfibstate
Traces what happens when label switching is enabled or disabled.
debug mpls lspv
To display information related to the Multiprotocol Label Processing (MPLS) label switched path (LSP) Ping/Traceroute feature, use the
debugmplslspvcommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
(Optional) Displays MPLS) echo packet type, length, values (TLVs) information as it is being coded and decoded.
error
(Optional) Displays error conditions encountered during MPLS echo request and echo reply encoding and decoding. See the table below.
event
(Optional) Displays MPLS echo request and reply send and receive event information.
ipc
(Optional) Interprocess communication. Displays debug information regarding communication between the Route Processor and line cards.
packetdata
(Optional) Displays detailed debugging information for the MPLS echo packets sent and received. This output is seen only on the originating router and the router generating the reply.
packeterror
(Optional) Displays packet errors for MPLS echo request and reply. No output is expected for this command.
path-discovery
(Optional) Provides information regarding LSP traceroute path discovery operations.
multipath
(Optional) Displays multipath information.
all
(Optional) Enables all the command keywords.
Command Default
MPLS LSP debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(27)S
This command was introduced.
12.4(6)T
The following keywords were added:
ipc,
path-discovery,
multipath, and
all.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.28(SB) and implemented on the Cisco 10000 series router.
12.0(32)SY
This command was integrated into Cisco IOS Release 12.0(32)SY.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(31)SB2
This command was integrated into Cisco IOS Release 12.2(31)SB2.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.0(33)S
The following keywords were added for Cisco IOS Release 12.0(33)S:
ipc,
path-discovery,
multipath, and
all.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
12.2(33)SXI
This command was integrated into Cisco IOS Release 12.2(33)SXI.
Usage Guidelines
Use this command to monitor activity associated with the
pingmpls and the
tracempls commands.
The following table lists the messages displayed by the
debugmplslspverrorcommand and the reason for each error message.
Table 18 Messages Displayed by the debug mpls lspv error Command
Message
Reason Why Message Is Displayed
Echo reply discarded because not routable
An echo reply message is sent because the IP header indicates that the packet has the Router Alert set and the packet is not routable.
UDP checksum error, packet discarded
A packet is received on the port being used by Label Switched Path Verification (LSPV) and there is a checksum error on the packet.
Invalid echo message type
An MPLS echo packet with an invalid echo message type (neither a request nor a reply) is received.
Illegal Action
The state machine that drives the LSPV software detects an invalid condition.
Examples
The following is sample output from thepingmpls command when LSPV event debugging is enabled:
Router# debug mpls lspv event
LSPV event debugging is on
Router# ping mpls ipv4 10.131.159.252/32 repeat 1
Sending 1, 100-byte MPLS Echos to 10.131.159.252/32,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not transmitted,
'.' - timeout, 'U' - unreachable,
'R' - downstream router but not target
Type escape sequence to abort.
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 48/48/48 ms
Router#
*Dec 31 19:31:15.366: LSPV:
waiting for 2 seconds
*Dec 31 19:31:15.366: LSPV: sender_handle: 2000002D, Event Echo Requests Start,
[Idle->Waiting for Echo Reply]
*Dec 31 19:31:15.414: LSPV: sender_handle: 2000002D, Event Echo Reply Received,
[Waiting for Echo Reply->Waiting for Interval]
*Dec 31 19:31:15.466: LSPV: sender_handle: 2000002D, Event Echo Requests Cancel,
[Waiting for Interval->Idle]
Router# undebug all
All possible debugging has been turned off
The following is sample output from thepingmpls command when LSPV TLV debugging is enabled:
Router# debug mpls lspv tlv
LSPV tlv debugging is on
Router# ping mpls ipv4 10.131.159.252/32 repeat 1
Sending 1, 100-byte MPLS Echos to 10.131.159.252/32,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not transmitted,
'.' - timeout, 'U' - unreachable,
'R' - downstream router but not target
Type escape sequence to abort.
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 40/40/40 ms
Router#
*Dec 31 19:32:32.566: LSPV: Echo Hdr encode: version 1, msg type 1, reply mode 2
, return_code 0, return_subcode 0, sender handle 9400002E, sequence number 1,
timestamp sent 14:32:32 EST Wed Dec 31 2003, timestamp rcvd 19:00:00 EST Thu Dec 31 1899
*Dec 31 19:32:32.566: LSPV: IPV4 FEC encode: destaddr 10.131.159.252/32
*Dec 31 19:32:32.566: LSPV: Pad TLV encode: type 1, size 18, pattern 0xABCD
*Dec 31 19:32:32.606: LSPV: Echo Hdr decode: version 1, msg type 2, reply mode 2,
return_code 3, return_subcode 0, sender handle 9400002E, sequence number 1,
timestamp sent 14:32:32 EST Wed Dec 31 2003, timestamp rcvd 14:32:32 EST Wed Dec 31 2003
Router# undebug all
All possible debugging has been turned off
The following is sample output from the
tracemplsmultipath command when LSPV multipath debugging is on:
Discovers MPLS LSP routes that packets will actually take when traveling to their destinations.
debug mpls mldp all
To enable debugging output for all Multicast Label Distribution Protocol (MLDP) events, use the debugmplsmldpallcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpall
nodebugmplsmldpall
Syntax Description
This command has no arguments or keywords.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for all MLDP events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network MVPN core network. Issuing this command is equivalent to issuing the following commands:
debug mpls mldp filter opaque_type
debug mpls mldp generic
debug mpls mldp gr
debug mpls mldp mfi
debug mpls mldp mrib
debug mpls mldp neighbor
debug mpls mldp packet
Examples
The following example shows how to enable debugging output for all MLDP events:
Router# debug mpls mldp all
Related Commands
Command
Description
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgeneric
Enables debugging output for generic MLDP events.
debugmplsmldpgr
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp filter opaque_type
To enable filtering of Multicast Label Distribution Protocol (MLDP) debugging output using the opaque type, use the debugmplsmldpfilteropaque_typecommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpfilteropaque_typetype
nodebugmplsmldpopaque_typetype
Syntax Description
type
The opaque type to be used for filtering. The following types are supported:
ipv4source-group--this represents the “IPv4 Protocol Independent Source-Specific Transit” multicast application type. The IPv4 source address and group address are also specified.
ipv6source-group--this represents the “IPv6 Protocol Independent Source-Specific Transit” multicast application type.The IPv6 source address and group address are also specified.
mdtvpn-idmdt-number--this represents the “Multicast Virtual Private Network (MVPN)” multicast application type. The VPN identifier and the Multicast Distribution Tree (MDT) number are also specified.
vpnv4source-grouproute-distinguisher--this represents the “Direct MDT (VPNv4) ” multicast application type.The IPv4 source address, group address, and the VPN route distinguisher are also specified.
type-number--the type-number. Valid values are from 0-65535.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables filtering of MLDP debugging output using the opaque type. This output occurs when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network. The opaque type represents the type of multicast application (for example, MVPN) occurring across an MPLS core network.
Examples
The following example shows how to enable filtering of MLDP debugging output using the opaque type:
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp generic
To enable debugging output for generic Multicast Label Distribution Protocol (MLDP) events, use the debugmplsmldpgenericcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpgeneric
[ id ]
nodebugmplsmldpgeneric
[ id ]
Syntax Description
id
(Optional) The hexadecimal Label Switched Multicast (LSM) system ID.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for generic MLDP events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network.
Examples
The following example shows how to enable debugging output for generic MLDP events:
Router# debug mpls mldp generic
Related Commands
Command
Description
debugmplsmldpall
Enables debugging output for all MLDP events.
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgr
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp gr
To enable debugging output for Multicast Label Distribution Protocol (MLDP) graceful restart (GR) events, use the debugmplsmldpgrcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpgr [id]
nodebugmplsmldp [id]
Syntax Description
id
(Optional) The hexadecimal Label Switched Multicast (LSM) system ID.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for MLDP graceful restart events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network.
Examples
The following example shows how to enable debugging output for MLDP GR events:
Router# debug mpls mldp gr
Related Commands
Command
Description
debugmplsmldpall
Enables debugging output for all MLDP events.
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgeneric
Enables debugging output for generic MLDP events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp mfi
To enable debugging output for Multicast Label Distribution Protocol/Multicast Forwarding Information (MLDP/MFI) interaction events, use the debugmplsmldpmficommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpmfi [id]
nodebugmplsmldpmfi [id]
Syntax Description
id
(Optional) The hexadecimal Label Switched Multicast (LSM) system ID.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for MLDP/MFI interaction events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network.
Examples
The following example shows how to enable debugging output for MLDP/MFI interaction events:
Router# debug mpls mldp mfi
Related Commands
Command
Description
debugmplsmldpall
Enables debugging output for all MLDP events.
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgeneric
Enables debugging output for generic MLDP events.
debugmplsmldpgr
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp mrib
To enable debugging output for Multicast Label Distribution Protocol/Multicast Routing Information Base (MLDP/MRIB) interaction events, use the debugmplsmldpmribcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpmrib
nodebugmplsmldpmrib
Syntax Description
This command has no arguments or keywords.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for MLDP/MRIB interaction events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network.
Examples
The following example shows how to enable debugging output for MLDP/MRIB interaction events:
Router# debug mpls mldp mrib
Related Commands
Command
Description
debugmplsmldpall
Enables debugging output for all MLDP events.
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgeneric
Enables debugging output for generic MLDP events.
debugmplsmldpgr
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp neighbor
To enable debugging output for Multicast Label Distribution Protocol (MLDP) neighbor events, use the debugmplsmldpneighborcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldpneighbor
nodebugmplsmldpneighbor
Syntax Description
This command has no arguments or keywords.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for MLDP neighbor events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN)core network.
Examples
The following example shows how to enable debugging output for MLDP neighbor events:
Router# debug mpls mldp neighbor
Related Commands
Command
Description
debugmplsmldpall
Enables debugging output for all MLDP events.
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgeneric
Enables debugging output for generic MLDP events.
debugmplsmldpgr
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldppacket
Enables debugging output for MLDP-generated MPLS control plane events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls mldp packet
To enable debugging output for Multicast Label Distribution Protocol (MLDP)-generated Multiprotocol Label Switching (MPLS) control plane events, use the debugmplsmldppacketcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsmldppacket
nodebugmplsmldppacket
Syntax Description
This command has no arguments or keywords.
Command Default
The command is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
15.0(1)S
This command was introduced.
Usage Guidelines
Use this command when the MLDP-based MVPN feature appears not to be functioning. The command enables debugging output for MLDP-generated MPLS control plane events that occur when the MLDP-based MVPN feature is enabled. This feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network.
Examples
The following example shows how to enable debugging output for MLDP-generated MPLS control plane events:
Router# debug mpls mldp packet
Related Commands
Command
Description
debugmplsmldpall
Enables debugging output for all MLDP events.
debugmplsmldpfilteropaque_type
Enables filtering of MLDP debugging output using the opaque type.
debugmplsmldpgeneric
Enables debugging output for generic MLDP events.
debugmplsmldpgr
Enables debugging output for MLDP graceful restart events.
debugmplsmldpmfi
Enables debugging output for MLDP/MFI interaction events.
debugmplsmldpmrib
Enables debugging output for MLDP/MRIB interaction events.
debugmplsmldpneighbor
Enables debugging output for MLDP neighbor events.
showmplsmldpdatabase
Displays MLDP information.
debug mpls netflow
To display debug messages for MPLS egress NetFlow accounting, use the debugmplsnetflowcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsnetflow
nodebugmplsnetflow
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(10)ST
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXI4
This command was integrated into Cisco IOS Release 12.2(33)SXI4.
Examples
Here is sample output from the debugmplsnetflow command:
Router# debug mpls netflow
MPLS Egress NetFlow debugging is on
Router#
Router#
Router#
4d00h:Egress flow:entry created, dest 3.3.3.3/32, src 34.0.0.1/8
Router#
Router#
4d00h:Egress flow:entry created, dest 3.3.3.3/32, src 42.42.42.42/32
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# int eth1/4
Router(config-if)# no mpls netflow egress
Router(config-if)#
4d00h:MPLS output feature change, trigger TFIB scan
4d00h:tfib_scanner_walk, prefix 5.5.5.5/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 3.3.3.3/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 100.100.100.100/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 4.4.4.4/32, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 177.1.1.0/24, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1
Router(config-if)#
Router(config-if)# mpls netflow egress
Router(config-if)#
4d00h:Interface refcount with output feature enabled = 2
4d00h:MPLS output feature change, trigger TFIB scan
4d00h:tfib_scanner_walk, prefix 5.5.5.5/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 3.3.3.3/32, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 100.100.100.100/32, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 4.4.4.4/32, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0
4d00h:tfib_scanner_walk, prefix 177.1.1.0/24, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 1
4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1
4d00h:Egress flow:entry created, dest 3.3.3.3/32, src 42.42.42.42/32
Router(config-if)#
Router(config-if)# end
Router# show run int eth1/4
Building configuration...
Current configuration:
!
interface Ethernet1/4
ip vrf forwarding vpn1
ip address 180.1.1.1 255.255.255.0
no ip directed-broadcast
mpls netflow egress
end
Router#
Router#
4d00h:%SYS-5-CONFIG_I:Configured from console by console
Router#
Note
Flow flag 1 prefixes are reachable through this interface; therefore, MPLS egress NetFlow accounting is applied to all packets going out the destination prefix. Flow flag 0 prefixes are not reachable through this interface; therefore, MPLS egress NetFlow accounting is not applied to any packets going out the destination prefix.
Related Commands
Command
Description
showdebug
Displays active debug output.
debug mpls packets
To display Multiprotocol Label Switching (MPLS) labeled packets switched by the host router, use the
debugmplspacketscommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplspackets [interface]
nodebugmplspackets [interface]
Syntax Description
interface
(Optional) The interface or subinterface name.
Command Default
The debug output displays all labeled packets, regardless of the interface.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CT
This command was introduced.
12.1(3)T
This command was modified for new MPLS terminology and syntax.
12.2(25)S
The command ouput was enhanced to display MPLS high availability information.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
Usage Guidelines
The optional>
interface parameter restricts the display to only those packets received or sent on the indicated interface or subinterface.
Note
Use this command with care because it generates output for every packet processed. Furthermore, enabling this command causes fast and distributed label switching to be disabled for the selected interfaces. To avoid adversely affecting other system activity, use this command only when traffic on the network is at a minimum.
Examples
The following is sample output from the
debugmplspackets command:
The following table describes the significant fields shown in the display.
Table 19 debug mpls packets Field Descriptions
Field
Description
Hs0/0
The identifier for the interface on which the packet was received or sent.
recvd
Packet received.
xmit
Packet transmitted.
CoS
Class of Service field from the packet label header.
TTL
Time to live field from the packet label header.
(no tag)
Last label was popped off the packet and sent unlabeled.
Tag(s)
A list of labels on the packet, ordered from the top of the stack to the bottom.
Examples
The following is sample output from the
debugmplspackets command:
Router# debug mpls packets
Gi6/0/0: rx: Len 118 Stack {30 6 255} - ipv4 data
Gi6/1/1: tx: Len 118 Stack {22 6 254} - ipv4 data
Related Commands
Command
Description
showmplsforwarding-table
Displays the contents of the MPLS forwarding table.
debug mpls static binding
To display information related to static binding events, use the debugmplsstaticbinding command in privileged EXEC mode. To disable debugging output, use theno form of this command.
debugmplsstaticbinding
[ vrfvpn-name ]
nodebugmplsstaticbinding
[ vrfvpn-name ]
Syntax Description
vrfvpn-name
(Optional) Displays information only for the specified VPN routing and forwarding instance.
Command Default
Static binding event information is not displayed.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(23)S
This command was introduced.
12.0(26)S
This command was integrated into Cisco IOS Release 12.0(26)S.
12.3(14)T
This command was integrated into Cisco IOS Release 12.3(14)T.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.2(33)SB
This command was integrated into Cisco IOS Release 12.2(33)SB.
Usage Guidelines
Use the debugmplsstaticbinding command to troubleshoot problems related to Multiprotocol Lbel Switching (MPLS) static labels or VRF-aware MPLS static labels. If you specify the vrf keyword, debugging is enabled only for a specified VRF. You can enable debugging only for a VRF.
Examples
The following is sample output from the debugmplsstaticbinding command:
To enable debugging for Multiprotocol Label Switching (MPLS)-Transport Profile (TP), use the
debugmplstp command in privileged EXEC mode. To disable debugging, use the
no form of this command.
This command was integrated into Cisco IOS Release 15.1(3)S.
Cisco IOS Release 3.9S
This command was modified. The pscpacket and event keywords were added.
Examples
The following example enables the display of MPLS-TP endpoint LSP debug messages:
Router# debug mpls tp lsp-ep
debug mpls-tp endpoint lsp setup or use debugging is on
Related Commands
Command
Description
showmplstp
Displays information summary or detailed information about MPLS-TP) settings.
debug mpls traffic-eng areas
To print information about traffic engineering area configuration change events, use the debugmplstraffic-engareas command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engareas
nodebugmplstraffic-engareas
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)ST
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, information is printed about traffic engineering area configuration change events:
Router# debug mpls traffic-eng areas
TE-AREAS:isis level-1:up event
TE-PCALC_LSA:isis level-1
debug mpls traffic-eng autoroute
To print information about automatic routing over traffic engineering tunnels, use the debugmplstraffic-engautoroute command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engautoroute
nodebugmplstraffic-engautoroute
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)ST
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, information is printed about automatic routing over traffic engineering tunnels:
Router# debug mpls traffic-eng autoroute
TE-Auto:announcement that destination 0001.0000.0003.00 has 1 tunnels
Tunnel1 (traffic share 333, nexthop 10.112.0.12)
debug mpls traffic-eng auto-tunnel backup
To print system information about traffic engineering backup autotunnels, use the
debug mpls traffic-eng auto-tunnel backup command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplstraffic-engauto-tunnelbackup
[ all | events | state ]
nodebugmplstraffic-engauto-tunnelbackup
[ all | events | state ]
Syntax Description
all
(Optional) Enables all backup autotunnel debugging output.
events
(Optional) Prints backup autotunnel system events.
state
(Optional) Prints the system state of backup autotunnels.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(32)S
This command was introduced.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
15.2(2)S
This command was modified. The output was enhanced to show debugging information for autotunnel and automesh stateful switchover (SSO) tunnels.
Cisco IOS XE Release 3.6S
This command was modified. The output was enhanced to show debugging information for autotunnel and automesh stateful switchover (SSO) tunnels.
Examples
This command shows how to display debugging information about the system state of backup autotunnels:
Router# debug mpls traffic-eng auto-tunnel backup state
Related Commands
Command
Description
debug mpls traffic-eng auto-tunnel primary
Prints system information about traffic engineering primary tunnels.
debug mpls traffic-eng tunnels events
Prints information about traffic engineering tunnel management system events.
mpls traffic-eng auto-tunnel backup
Automatically builds NHOP and NNHOP backup tunnels.
show ip explicit-paths
Displays the configured IP explicit paths.
show mpls traffic-eng tunnels
Displays information about tunnels.
debug mpls traffic-eng auto-tunnel primary
To print system information about traffic engineering primary autotunnels, use the
debug mpls traffic-eng auto-tunnel primary command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplstraffic-engauto-tunnelprimary
[ all | events | state ]
nodebugmplstraffic-engauto-tunnelprimary
[ all | events | state ]
Syntax Description
all
(Optional) Enables all primary autotunnel debugging output.
events
(Optional) Prints primary autotunnel system events.
state
(Optional) Prints the system state of primary autotunnels.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(32)S
This command was introduced.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
15.2(2)S
This command was modified. The output was enhanced to show debugging information for autotunnel and automesh stateful switchover (SSO) tunnels.
Cisco IOS XE Release 3.6S
This command was modified. The output was enhanced to show debugging information for autotunnel and automesh stateful switchover (SSO) tunnels.
Examples
In the following example, debugging information is printed about system events of primary autotunnels:
In the following example, debugging information is printed about the system state of primary autotunnels:
Router# debug mpls traffic-eng auto-tunnel primary state
Sample for debug mpls traffic-eng auto-tunnel primary state: *Feb 6 18:11:44.363: TE_AUTO_TUN: Didn't find protected Up Tunnel3000 to router id 192.168.1.1 out POS2/0
Sample for debug mpls traffic-eng auto-tunnel backup events (this is one log that prints on multiple lines): *Feb 6 18:19:04.303: TE_AUTO_TUN: CLI command:
ip explicit-path name __dynamic_tunnel4000
index 1 next-address 192.168.1.2
Related Commands
Command
Description
debug mpls traffic-eng auto-tunnel backup
Prints system information about traffic engineering backup autotunnels.
debug mpls traffic-eng tunnels events
Prints information about traffic engineering tunnel management system events.
mpls mpls traffic-eng auto-tunnel primary config
Enables IP processing without an explicit address.
show ip explicit-paths
Displays the configured IP explicit paths.
show mpls traffic-eng tunnels
Displays information about tunnels.
debug mpls traffic-eng filter
To filter the display of Multiprotocol Label Switching (MPLS) traffic engineering messages by access control list (ACL), point-to-point (P2P) messages, or point-to-multipoint (P2MP) messages, use the
debugmplstraffic-engfilter command in Privileged EXEC configuration mode. To disable the display of these messages, use the
no form of this command.
Displays debug information for the specified ACL. Valid values are 1-199 and 1300-2699.
dest-mode
Displays debug information sorted by P2P or P2MP messages.
p2p
Displays debug information about P2P tunnels.
p2mp
Displays debug information about P2MP tunnels.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SRE
This command was introduced.
Examples
The following example enables the display of debug message for P2MP tunnels:
Router# debug mpls traffic-eng filter dest-mode p2mp
Setting filter for TE P2MP Tunnels/LSPs
Related Commands
Command
Description
showmplstraffic-engtunnels
Displays information about P2P and P2MP tunnels.
debug mpls traffic-eng forwarding-adjacency
To display debug messages for traffic engineering (TE) forwarding adjacency events, use the debugmplstraffic-engforwarding-adjacencycommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
A standard IP access list is in the range 1 to 199.
An extended IP access list is in the range 1300 to 2699.
Command Default
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(15)S
This command was introduced.
12.0(16)ST
This command was integrated into Cisco IOS Release 12.0(16)ST.
12.2(18)S
This command was integrated into Cisco IOS Release 12.2(18)S.
12.2(18)SXD
This command was integrated into Cisco IOS Release 12.2(18)SXD.
12.2(27)SBC
This command was integrated into Cisco IOS Release 12.2(27)SBC.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(20)T
This command was integrated into Cisco IOS Release 12.4(20)T.
Usage Guidelines
Use the debugmplstraffic-engforwarding-adjacencycommand to troubleshoot any problems that occur after you configure the tunnelmplstraffic-engforwarding-adjacency command.
If you enter the detail keyword before the access-list-number argument, you can specify an access list. However, if you enter an access list before you enter the detail keyword, you cannot specify the detail keyword.
Examples
The following is sample output from thedebugmplstraffic-engforwarding-adjacencycommand:
Router# debug mpls traffic-eng forwarding-adjacency
MPLS traffic-eng debugging is on
With a tunnel configured, the following output appears:
interface Tunnel0
ip unnumbered Loopback0
no ip directed-broadcast
tunnel destination 192.168.1.7
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng forwarding-adjacency
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng path-option 10 dynamic
end
When the tunnel comes up, the command generates the following debug output:
Displays TE tunnels being advertised as links in an IGP network.
tunnelmplstraffic-engforwarding-adjacency
Advertises a TE tunnel as a link in an IGP network.
debug mpls traffic-eng ha sso
To display debugging output for Multiprotocol Label Switching (MPLS) traffic engineering high availability (HA) activities during the graceful switchover from an active Route Processor (RP) to a redundant standby RP, use the
debug mpls traffic-eng ha sso command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
Displays information about autotunnel activity during the MPLS traffic engineering stateful switchover (SSO) process.
errors
Displays errors encountered during the MPLS traffic engineering SSO process.
link-management
Displays information about link management activity during the MPLS traffic engineering SSO process.
events
Displays significant events that occur during the MPLS traffic engineering SSO process.
standby
Displays information about the standby behavior during the MPLS traffic engineering SSO process.
recovery
Displays information about recovery activity during the MPLS traffic engineering SSO process.
checkpoint
Display information about checkpointing activities during the MPLS traffic engineering SSO process. Checkpointing occurs when a message is sent and acknowledged.
tunnel
Displays information about tunnel activity during the MPLS traffic engineering SSO process.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SRA
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
15.2(2)S
This command was modified. The output for the
debug mpls traffic-eng ha sso tunnel events, the
debug mpls traffic-eng ha sso standby, and the
debug mpls traffic-eng ha sso tunnel recovery commands was enhanced to show debugging information for autotunnel and automesh stateful switchover (SSO) tunnels.
Cisco IOS XE Release 3.6S
This command was modified. The output for the
debug mpls traffic-eng ha sso tunnel events, the
debug mpls traffic-eng ha sso standby, and the
debug mpls traffic-eng ha sso tunnel recovery commands was enhanced to show debugging information for autotunnel and automesh stateful switchover (SSO) tunnels.
Usage Guidelines
This command displays debugging output about the SSO process for MPLS traffic engineering tunnels, autotunnels, and link management systems. The SSO process occurs when the active router becomes unavailable and system control and routing protocol execution are transferred from the now inactive RP to the redundant standby RP, thus providing uninterrupted network services.
Examples
The following is sample output from the
debug mpls traffic-eng ha sso command when you have enabled debugging keywords to monitor the SSO process for tunnels and link management systems as the standby router becomes active:
Router# debug mpls traffic-eng ha sso link-management events
MPLS traffic-eng SSO link management events debugging is on
Router# debug mpls traffic-eng ha sso link-management recovery
MPLS traffic-eng SSO link management recovery debugging is on
Router# debug mpls traffic-eng ha sso link-management standby
MPLS traffic-eng SSO link management standby behavior debugging is on
Router# debug mpls traffic-eng ha sso link-management checkpoint
MPLS traffic-eng SSO link management checkpointed info debugging is on
Router# debug mpls traffic-eng ha sso tunnel standby
MPLS traffic-eng SSO tunnel standby behavior debugging is on
Router# debug mpls traffic-eng ha sso tunnel recovery
MPLS traffic-eng SSO tunnel head recovery debugging is on
Router# debug mpls traffic-eng ha sso tunnel events
MPLS traffic-eng SSO events for tunnel heads debugging is on
Router# debug mpls traffic-eng ha sso errors
MPLS traffic-eng SSO errors debugging is on
Router# show debug
<-----
This command displays the debugging that is enabled.
MPLS TE:
MPLS traffic-eng SSO link management events debugging is on
MPLS traffic-eng SSO link management recovery debugging is on
MPLS traffic-eng SSO link management standby behavior debugging is on
MPLS traffic-eng SSO link management checkpointed info debugging is on
MPLS traffic-eng SSO tunnel standby behavior debugging is on
MPLS traffic-eng SSO tunnel head recovery debugging is on
MPLS traffic-eng SSO events for tunnel heads debugging is on
MPLS traffic-eng SSO errors debugging is on
Router#
Standby-Router#
Following is the sample debugging output displayed during a successful SSO recovery on the standby router as it becomes active:
*May 12 20:03:15.303: RRR_HA_STATE: Told to wait for IGP convergence
*May 12 20:03:14.807: %FABRIC-SP-STDBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
*May 12 20:03:15.763: RRR_HA_REC: Attempting to recover last flooded info; protocol: OSPF, area: 0
*May 12 20:03:15.763: RRR_HA_REC: recovered ospf area 0 instance 0x48FFF240
*May 12 20:03:15.763: RRR_HA_REC: recovered system info
*May 12 20:03:15.763: RRR_HA_REC: recovered link[0] info
*May 12 20:03:15.763: RRR_HA: Recovered last flooded info for igp: OSPF, area: 0
*May 12 20:03:15.763: Pre announce tunnel 10
*May 12 20:03:15.763: TSPVIF_HA_EVENT: added Router_t10 to dest list
*May 12 20:03:15.763: TSPVIF_HA_EVENT: Completed announcement of 1 tunnel heads to IGP
*May 12 20:03:15.763: TSPVIF_HA_REC: Attempting to recover Tunnel10 after SSO
*May 12 20:03:15.763: LSP-TUNNEL-REOPT: Tunnel10 [61] set to recover
*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered number hops = 5
*May 12 20:03:15.763: TSPVIF_HA_REC: recovered ospf area 0 instance 0x48FFF240
*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 0: 10.0.3.1, Id: 10.0.0.3 Router Node (ospf) flag:0x0
*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 1: 10.0.3.2, Id: 10.0.0.7 Router Node (ospf) flag:0x0
*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 2: 10.0.6.1, Id: 10.0.0.7 Router Node (ospf) flag:0x0
*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 3: 10.0.6.2, Id: 10.0.0.9 Router Node (ospf) flag:0x0
*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 4: 10.0.0.9, Id: 10.0.0.9 Router Node (ospf) flag:0x0
*May 12 20:03:15.763: TSPVIF_HA_REC: signalling recovered setup for Tunnel10: popt 1
[61], weight 2
*May 12 20:03:15.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query
*May 12 20:03:15.891: TSPVIF_HA_REC: output_idb: GigabitEthernet3/2, output_nhop: 180.0.3.2
Standby-Router#
Router#
*May 12 20:03:25.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query
*May 12 20:03:25.891: TSPVIF_HA_REC: output_idb: GigabitEthernet3/2, output_nhop: 10.0.3.2
*May 12 20:03:35.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query
*May 12 20:03:35.891: TSPVIF_HA_REC: output_idb: GigabitEthernet3/2, output_nhop: 10.0.3.2
*May 12 20:03:35.895: RRR_HA_STATE: IGP flood prevented during IGP recovery
*May 12 20:03:38.079: LSP-TUNNEL-REOPT: Tunnel10 [61] received RESV for recovered setup
*May 12 20:03:38.079: LSP-TUNNEL-REOPT: Tunnel10 [61] removed as recovery
*May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying RSVP HA to add lsp_info using key 10.0.0.3->10.0.0.9 Tu10 [61] 10.0.0.3
*May 12 20:03:38.079: TSPVIF_HA_EVENT: updated 7600-1_t10 state; action = add; result = success
*May 12 20:03:38.079: TSPVIF_HA_EVENT: 7600-1_t10 fully recovered; rewrite refreshed
*May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying CBTS bundle about Router_t10
*May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying RSVP HA to remove lsp_info using key 10.0.0.3->10.0.0.9 Tu10 [61] 10.0.0.3
*May 12 20:03:38.079: RRR_HA: Received notification recovery has ended. Notify IGP to flood.
*May 12 20:03:38.079: TSPVIF_HA_EVENT: Received notification recovery has ended
*May 12 20:03:38.079: TSPVIF_HA_STANDBY: prevent verifying setups; IGP has not converged
*May 12 20:03:38.083: TSPVIF_HA_STANDBY: preventing new setups; reason: IGP recovering
*May 12 20:03:38.083: TSPVIF_HA_STANDBY: prevent verifying setups; IGP has not converged
*May 12 20:03:38.083: TSPVIF_HA_STANDBY: preventing new setups; reason: IGP recovering
*May 12 20:03:38.083: RRR_HA_STATE: IGP flood prevented during IGP recovery
7600-1#
*May 12 20:03:47.723: RRR_HA: Received notification that RIB table 0 has converged.
*May 12 20:03:47.723: RRR_HA: Received notification all RIBs have converged. Notify IGP to flood.
*May 12 20:03:47.723: RRR_HA_STATE: Told not to wait for IGP convergence
*May 12 20:03:47.723: RRR_HA_INFO: update flooded system info; action = add; result = success
*May 12 20:03:47.723: LM System key::
*May 12 20:03:47.723: Flooding Protocol: ospf
*May 12 20:03:47.723: IGP Area ID: 0
*May 12 20:03:47.723: LM Flood Data::
*May 12 20:03:47.723: LSA Valid flags: 0x0 Node LSA flag: 0x0
*May 12 20:03:47.723: IGP System ID: 10.0.0.3 MPLS TE Router ID: 10.0.0.3
*May 12 20:03:47.723: Flooded links: 1 TLV length: 0 (bytes)
*May 12 20:03:47.723: Fragment id: 0
*May 12 20:03:47.723: rrr_ha_lm_get_link_info_size: link size: 212 bytes; num TLVs: 0
*May 12 20:03:47.723: rrr_ha_sizeof_lm_link_info: link size: 212 bytes; num TLVs: 0
*May 12 20:03:47.723: RRR_HA_INFO: update flooded link[0] info; action = add;
result = success
*May 12 20:03:47.723: RRR HA Checkpoint Info Buffer::
*May 12 20:03:47.723: Info Handle: 0x490BB1C8
*May 12 20:03:47.723: Max Size: 212
*May 12 20:03:47.723: Info Size: 212
*May 12 20:03:47.723: Info Write Pointer: 0x490BB29C
*May 12 20:03:47.723: LM Link key::
*May 12 20:03:47.723: Flooding Protocol: ospf IGP Area ID: 0 Link ID: 0 (GigabitEthernet3/2)
*May 12 20:03:47.723: Ifnumber: 5 Link Valid Flags: 0x193B
*May 12 20:03:47.723 Link Subnet Type: Broadcast
*May 12 20:03:47.723: Local Intfc ID: 0 Neighbor Intf ID: 0
*May 12 20:03:47.723: Link IP Address: 10.0.3.1
*May 12 20:03:47.723: Neighbor IGP System ID: 10.0.3.2 Neighbor IP Address: 10.0.0.0
*May 12 20:03:47.723: IGP Metric: 1 TE Metric: 1
*May 12 20:03:47.723: Physical Bandwidth: 1000000 kbits/sec
*May 12 20:03:47.723: Res. Global BW: 3000 kbits/sec
*May 12 20:03:47.723: Res. Sub BW: 0 kbits/sec
*May 12 20:03:47.723: Upstream::
Router#
*May 12 20:03:47.723: Global Pool Sub Pool
*May 12 20:03:47.723: ----------- ----------
*May 12 20:03:47.723: Reservable Bandwidth[0]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[1]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[2]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[3]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[4]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[5]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[6]: 0 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[7]: 0 0 kbits/sec
*May 12 20:03:47.723: Downstream::
*May 12 20:03:47.723: Global Pool Sub Pool
*May 12 20:03:47.723: ----------- ----------
*May 12 20:03:47.723: Reservable Bandwidth[0]: 3000 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[1]: 3000 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[2]: 3000 0 kbits/sec
*May 12 20:03:47.723: Reservable Bandwidth[3]: 3000 0 kbits/sec
*May 12 20:03:47.727: Reservable Bandwidth[4]: 3000 0 kbits/sec
*May 12 20:03:47.727: Reservable Bandwidth[5]: 3000 0 kbits/sec
*May 12 20:03:47.727: Reservable Bandwidth[6]: 3000 0 kbits/sec
*May 12 20:03:47.727: Reservable Bandwidth[7]: 2900 0 kbits/sec
*May 12 20:03:47.727: Affinity Bits: 0x0
*May 12 20:03:47.727: Protection Type: Capability 0, Working Priority 0
*May 12 20:03:47.727: Number of TLVs: 0
*May 12 20:03:47.727: RRR_HA: Updated flood state for ospf area 0 with 1 links); result = success
Router#
The following example shows how to turn off debugging:
Router# no debug mpls traffic-eng ha sso link-management events
MPLS traffic-eng SSO link management events debugging is off
Router# no debug mpls traffic-eng ha sso link-management recovery
MPLS traffic-eng SSO link management recovery debugging is off
Router# no debug mpls traffic-eng ha sso link-management standby
MPLS traffic-eng SSO link management standby behavior debugging is off
Router# no debug mpls traffic-eng ha sso link-management checkpoint
MPLS traffic-eng SSO link management checkpointed info debugging is off
Router# no debug mpls traffic-eng ha sso tunnel standby
MPLS traffic-eng SSO tunnel standby behavior debugging is off
Router# no debug mpls traffic-eng ha sso tunnel recovery
MPLS traffic-eng SSO tunnel head recovery debugging is off
Router# no debug mpls traffic-eng ha sso tunnel events
MPLS traffic-eng SSO events for tunnel heads debugging is off
Router# no debug mpls traffic-eng ha errors
MPLS traffic-eng SSO errors debugging is off
Related Commands
Command
Description
debug ip rsvp high-availability
Displays debugging output for RSVP HA activities that improve the accessibility of network resources.
debug ip rsvp sso
Displays debugging output for RSVP activities during the graceful switchover from an active RP to a redundant RP.
To print information about traffic engineering label-switched path (LSP) admission control on traffic engineering interfaces, use the debugmplstraffic-englink-managementadmission-controlcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
To print information about resource advertisements for traffic engineering interfaces, use the
debugmplstraffic-englink-managementadvertisements command in privileged EXEC mode. To disable debugging output, use the
no form of this command.
To print detailed information about bandwidth allocation for traffic engineering label-switched paths (LSPs), use the debugmplstraffic-englink-managementbandwidth-allocation command in privileged EXEC mode. To disable debugging output, use the no form of this command.
Prints information about traffic engineering LSP admission control on traffic engineering interfaces.
debugmplstraffic-englink-managementerrors
Prints information about errors encountered during any traffic engineering link management procedure.
debug mpls traffic-eng link-management errors
To print information about errors encountered during any traffic engineering link management procedure, use the debugmplstraffic-englink-managementerrors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about errors encountered during a traffic engineering link management procedure:
Router# debug mpls traffic-eng link-management errors detail
00:04:48 TE-LM-ROUTING: link Et1/1/1: neighbor 0010.0000.0012.01: add to IP peer db failed
Prints information about bandwidth allocation for traffic engineering LSPs.
debugmplstraffic-englink-managementevents
Prints information about traffic engineering link management system events.
debugmplstraffic-englink-managementigp-neighbors
Prints information about changes to the link management databases of IGP neighbors.
debugmplstraffic-englink-managementlinks
Prints information about traffic engineering link management interface events.
debug mpls traffic-eng link-management events
To print information about traffic engineering link management system events, use the debugmplstraffic-englink-managementevents command in privileged EXEC mode. To disable debugging output, use the no form of this command.
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering link management system events:
Router# debug mpls traffic-eng link-management events detail
TE-LM-EVENTS:stopping MPLS TE Link Management process
TE-LM-EVENTS:MPLS TE Link Management process dying now
To print information about changes to the link management database of Interior Gateway Protocol (IGP) neighbors, use the debugmplstrafficenglink-managementigp-neighbors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
Prints information about traffic engineering-related ISIS events.
debug mpls traffic-eng link-management links
To print information about traffic engineering link management interface events, use the debugmplstraffic-englink-managementlinks command in privileged EXEC mode. To disable debugging output, use the no form of this command.
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering link management interface events:
Router# debug mpls traffic-eng link-management links detail
TE-LM-LINKS:link AT0/0.2:RSVP enabled
TE-LM-LINKS:link AT0/0.2:increasing RSVP bandwidth from 0 to 5000000
TE-LM-LINKS:link AT0/0.2:created [total 2]
TE-LM-LINKS:Binding MPLS TE LM Admission Control as the RSVP Policy Server on ATM0/0.2
TE-LM-LINKS:Bind attempt succeeded
TE-LM-LINKS:link AT0/0.2:LSP tunnels enabled
debug mpls traffic-eng link-management preemption
To print information about traffic engineering label-switched path (LSP) preemption, use the debugmplstraffic-englink-managementpreemption command in privileged EXEC mode. To disable debugging output, use the no form of this command.
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering LSP preemption:
Router# debug mpls traffic-eng link-management preemption detail
TE-LM-BW:preempting Downstream bandwidth, 1000000, for tunnel 10.106.0.6 2_2
TE-LM-BW:building preemption list to get bandwidth, 1000000, for tunnel 10.106.0.6 2_2 (priority 0)
TE-LM-BW:added bandwidth, 3000000, from tunnel 10.106.0.6 1_2 (pri 1) to preemption list
TE-LM-BW:preemption list build to get bw, 1000000, succeeded (3000000)
TE-LM-BW:preempting bandwidth, 1000000, using plist with 1 tunnels
TE-LM-BW:tunnel 10.106.0.6 1_2:being preempted on AT0/0.2 by 10.106.0.6 2_2
TE-LM-BW:preemption of Downstream bandwidth, 1000000, succeeded
debug mpls traffic-eng link-management routing
To print information about traffic engineering link management routing resolutions that can be performed to help Resource Reservation Protocol (RSVP) interpret explicit route objects, use the debugmplstraffic-englink-managementrouting command in privileged EXEC mode. To disable debugging output, use the no form of this command.
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering link management routing resolutions that can be performed to help RSVP interpret explicit route objects:
Router# debug mpls traffic-eng link-management routing detail
TE-LM-ROUTING:route options to 10.42.0.10:building list (w/ nhop matching)
TE-LM-ROUTING:route options to 10.42.0.10:adding {AT0/0.2, 10.42.0.10}
TE-LM-ROUTING:route options to 10.42.0.10:completed list has 1 links
Related Commands
Command
Description
debugiprsvp
Prints information about RSVP signalling events.
debug mpls traffic-eng load-balancing
To print information about unequal cost load balancing over traffic engineering tunnels, use the debugmplstraffic-engload-balancing command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engload-balancing
nodebugmplstraffic-engload-balancing
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)ST
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, information is printed about unequal cost load balancing over traffic engineering tunnels:
Router# debug mpls traffic-eng load-balancing
TE-Load:10.210.0.0/16, 2 routes, loadbalancing based on MPLS TE bandwidth
TE-Load:10.200.0.0/16, 2 routes, loadbalancing based on MPLS TE bandwidth
debug mpls traffic-eng lsd-client
To display the Application Programming Interface (API) messages sent to the Label Switching Database (LSD) from the Traffic Engineering (TE) client, use the debug mpls traffic-eng lsd-client command in privileged EXEC mode. To disable the display of these messages, use the no form of this command.
debugmplstraffic-englsd-client
nodebugmplstraffic-englsd-client
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(25)S
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(28)SRA.
12.2(33)SXH
This command was integrated into Cisco IOS Release 12.2(28)SXH.
Examples
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand enable TE globally:
00:10:23: TE-LSD-CLIENT: register with LSD OK; conn_id = 23, recov time = 60000 s
00:10:23: TE-LSD-CLIENT: LSD is now up
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand disable TE globally:
00:09:50: TE-LSD-CLIENT: unregister LSD client; result = OK; conn_id 23
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand enable TE on specific interfaces on Cisco 7500 series routers:
00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Ethernet1/0; status = OK
00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial2/0; status = OK
00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial3/0; status = OK
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand disable TE on specific interfaces on Cisco 7500 series routers:
00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Ethernet1/0; status = OK
00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial2/0; status = OK
00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial3/0; status = OK
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand enable TE on specific interfaces on Cisco 10000 series routers:
00:10:23: TE-LSD-CLIENT: enabled TE LSD client on GigabitEthernet1/0/0; status = OK
00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial2/0/0; status = OK
00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial3/0/0; status = OK
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand disable TE on specific interfaces on Cisco 10000 series routers:
00:09:50: TE-LSD-CLIENT: disabled TE LSD client on GigabitEthernet1/0/0; status = OK
00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial2/0/0; status = OK
00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial3/0/0; status = OK
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommand, allocate labels on tunnel midpoints, and create tunnel midpoint rewrites on Cisco 7500 series routers:
00:14:04: TE-LSD-CLIENT: label alloc OK; label = 16, conn_id = 23
00:14:04: TE-LSD-CLIENT: Create TE mid rewrite for 10.100.100.100 1 [5], Result: OK
00:14:04: In: Serial3/0, 16 Out: Serial2/0, 3
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommand,allocate labels on tunnel midpoints, and create tunnel midpoint rewrites on a Cisco 10000 series router:
00:14:04: TE-LSD-CLIENT: label alloc OK; label = 16, conn_id = 23
00:14:04: TE-LSD-CLIENT: Create TE mid rewrite for 10.100.100.100 1 [5], Result: OK
00:14:04: In: Serial3/0/0, 16 Out: Serial2/0/0, 3
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommand, free labels on tunnel midpoints, and delete tunnel midpoints on a Cisco 7500 series router:
00:13:13: TE-LSD-CLIENT: Delete TE mid rewrite for iou-100_t1, Result: OK
00:13:13: In: Serial3/0, 16 Out: Serial2/0, 1
00:13:13: TE-LSD-CLIENT: free label 16 result = OK; conn_id = 23
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommand, free labels on tunnel midpoints, and delete tunnel midpoints on a Cisco 10000 series router:
00:13:13: TE-LSD-CLIENT: Delete TE mid rewrite for iou-100_t1, Result: OK
00:13:13: In: Serial3/0/0, 16 Out: Serial2/0/0, 1
00:13:13: TE-LSD-CLIENT: free label 16 result = OK; conn_id = 23
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand create tunnel headend rewrites on a Cisco 7500 series router:
00:09:10: TE-LSD-CLIENT: Create TE he rewrite for iou-100_t1, Result = OK
00:09:10: tun_inst: 7 Out: Serial3/0, 16 Dest: 10.0.0.2
ps_flags: 0x60003
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand create tunnel headend rewrites on a Cisco 10000 series router:
00:09:10: TE-LSD-CLIENT: Create TE he rewrite for iou-100_t1, Result = OK
00:09:10: tun_inst: 7 Out: Serial3/0/0, 16 Dest: 10.0.0.2
ps_flags: 0x60003
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand delete tunnel headend rewrites on a Cisco 7500 series router:
00:09:15: TE-LSD-CLIENT: Delete TE he rewrite for iou-100_t1, Result: OK
00:09:15: tun_inst: 7 Out: Serial3/0, 16 ps_flags: 0x60003
The following messages are displayed when you issue the debugmplstraffic-englsd-clientcommandand delete tunnel headend rewrites on a Cisco 10000 series router:
00:09:15: TE-LSD-CLIENT: Delete TE he rewrite for iou-100_t1, Result: OK
00:09:15: tun_inst: 7 Out: Serial3/0/0, 16 ps_flags: 0x60003
Related Commands
Command
Description
debugmplsipiprmevents
Displays events related to the MPLS IPRM.
debugmplsipiprmldm
Displays debugging information for interactions between the IP LDMs and the MPLS IPRM.
debugmplsipiprmmfi
Displays debugging information for interactions between the MFI and the MPLS IPRM.
debug mpls traffic-eng path
To display information about Multiprotocol Label Switching (MPLS) traffic engineering path calculation, use the debugmplstraffic-engpath command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engpath
{ api | dump | errors | num | lookup | spf | verify }
nodebugmplstraffic-engpath
{ api | dump | errors | num | lookup | spf | verify }
To display information about process restarts for reporting to your technical support representative, use the debugmplstraffic-engprocess-restartcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engprocess-restart
nodebugmplstraffic-engprocess-restart
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SXH
This command was introduced.
Usage Guidelines
If you report a problem and the showmplstraffic-engprocess-restartiprouting displays abnormal results, your technical support representative might ask you to issue the debugmplstraffic-engprocess-restartcommand, then perform an IP routing process restart and capture the output for analysis.
Examples
The following example shows partial output from an IP routing process restart:
Router# debug mpls traffic-eng process-restart
02:24:22: SM: ---TE ION Process Restart 0x78EF9050: process restart (3)
02:24:22: SM: NORM (1) --> AWAIT-CFG (3)
02:24:22: TE ION Restart timer started, proc_idx:0 delay:120000
02:24:22: SM: ---TE ION Process Restart 0x78EF9050: process cfg replay start (4)
02:24:22: SM: AWAIT-CFG (3) --> CFG (4)
02:24:22: TE ION Restart timer started, proc_idx:0 delay:300000
02:24:22: SM: ---TE ION Process Restart 0x78EF9050: reg invoke succeeded (2)
02:24:22: SM: CFG (4) --> CFG (4)
02:24:22: SM: ---TE ION Process Restart 0x78EF9050: process cfg replay done (5)
02:24:22: SM: CFG (4) --> SYNC (5)
02:24:22: TE ION Restart timer started, proc_idx:0 delay:900000
The output shows typical process restart information that your technical support representative might request if you report a problem after an IP routing process restart. The information displayed can vary, depending on the conditions that caused the restart.
Related Commands
Command
Description
showmplstraffic-engprocess-restartiprouting
Displays the status of IP routing and MPLS traffic engineering synchronization after an IP routing process restarts.
debug mpls traffic-eng topology change
To print information about traffic engineering topology change events, use the debugmplstraffic-engtopologychange command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engtopologychange
nodebugmplstraffic-engtopologychange
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)ST
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, information is printed about traffic engineering topology change events:
To print information about traffic engineering topology link state advertisement (LSA) events, use the debugmplstraffic-engtopologylsa command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engtopologylsa
nodebugmplstraffic-engtopologylsa
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)ST
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, information is printed about traffic engineering topology LSA events:
To print information about errors encountered during any traffic engineering tunnel management procedure, use the debugmplstraffic-engtunnelserrors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engtunnelserrors [detail]
nodebugmplstraffic-engtunnelserrors [detail]
Syntax Description
detail
(Optional) Prints detailed debugging information.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about errors encountered during a traffic engineering tunnel management procedure:
Router# debug mpls traffic-eng tunnels errors
00:04:14: LSP-TUNNEL-SIG: Tunnel10012[1]: path verification failed (unprotected) [Can’t use link 10.12.4.4 on node 10.0.0.4]
debug mpls traffic-eng tunnels events
To print information about traffic engineering tunnel management system events, use the debugmplstraffic-engtunnelsevents command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplstraffic-engtunnelsevents [detail]
nodebugmplstraffic-engtunnelsevents [detail]
Syntax Description
detail
(Optional) Prints detailed debugging information.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel management system events:
Router# debug mpls traffic-eng tunnels events detail
LSP-TUNNEL:received event:interface admin. down [Ethernet4/0/1]
LSP-TUNNEL:posting action(s) to all-tunnels:
check static LSPs
LSP-TUNNEL:scheduling pending actions on all-tunnels
LSP-TUNNEL:applying actions to all-tunnels, as follows:
check static LSPs
debug mpls traffic-eng tunnels labels
To print information about Multiprotocol Label Switching (MPLS) label management for traffic engineering tunnels, use the debugmplstraffic-engtunnelslabels command in privileged EXEC mode. To disable debugging output, use the no form of this command.
(Optional) Uses the specified access list to filter the debugging information. Prints information only about traffic engineering tunnels that match the access list.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-numberargument were added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about MPLS label management for traffic engineering tunnels:
Router# debug mpls traffic-eng tunnels labels detail
LSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:fabric PROGRAM request
LSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:programming label 16 on output interface ATM0/0.2
LSP-TUNNEL-LABELS:descriptor 71FA64:continuing “Program” request
LSP-TUNNEL-LABELS:descriptor 71FA64:set “Interface Point Out State” to, allocated
LSP-TUNNEL-LABELS:# of resource points held for “default” interfaces:2
LSP-TUNNEL-LABELS:descriptor 71FA64:set “Fabric State” to, enabled
LSP-TUNNEL-LABELS:descriptor 71FA64:set “Fabric Kind” to, default (LFIB)
LSP-TUNNEL-LABELS:descriptor 71FA64:set “Fabric State” to, set
LSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:fabric PROGRAM reply
To restrict output to information about a single tunnel, you can configure an access list and supply it to the debug command. Configure the access list as follows:
Router(config-ext-nacl)# permit udp host scr_address host dst_address eq tun intfc
For example, if tunnel 10012 has destination 10.0.0.11 and source 10.0.0.4, as determined by the showmplstraffic-engtunnelscommand, the following access list could be configured and added to the debug command:
To print information about traffic engineering tunnel reoptimizations, use the debugmplstraffic-engtunnelsreoptimize command in privileged EXEC mode. To disable debugging output, use the no form of this command.
(Optional) Uses the specified access list to filter the debugging information. Prints information about only those traffic engineering tunnel reoptimizations that match the access list.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-numberargument were added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel reoptimizations that match access list number 101:
Router# debug mpls traffic-eng tunnels reoptimize detail 101
LSP-TUNNEL-REOPT:Tunnel1 curr option 2 (0x6175CF8C), activate new option 2
LSP-TUNNEL-REOPT:Tunnel1 new path:option 2 [10002], weight 20
LSP-TUNNEL-REOPT:Tunnel1 old path:option 2 [2], weight 110
LSP-TUNNEL-REOPT:Tunnel1 [10002] set as reopt
LSP-TUNNEL-REOPT:Tunnel1 path option 2 [10002] installing as current
LSP-TUNNEL-REOPT:Tunnel1 [2] removed as current
LSP-TUNNEL-REOPT:Tunnel1 [2] set to delayed clean
LSP-TUNNEL-REOPT:Tunnel1 [10002] removed as reopt
LSP-TUNNEL-REOPT:Tunnel1 [10002] set to current
debug mpls traffic-eng tunnels signalling
To print information about traffic engineering tunnel signalling operations, use the debugmplstraffic-engtunnelssignalling command in privileged EXEC mode. To disable debugging output, use the no form of this command.
(Optional) Uses the specified access list to filter the debugging information. Prints information about only those traffic engineering tunnel signalling operations that match the access list.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-numberargument were added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel signalling operations that match access list number 101:
Router# debug mpls traffic-eng tunnels signalling detail 101
LSP-TUNNEL-SIG:tunnel Tunnel1 [2]:RSVP head-end open
LSP-TUNNEL-SIG:tunnel Tunnel1 [2]:received Path NHOP CHANGE
LSP-TUNNEL-SIG:Tunnel1 [2]:first hop change:0.0.0.0 --> 10.1.0.10
LSP-TUNNEL-SIG:received ADD RESV request for tunnel 10.106.0.6 1 [2]
LSP-TUNNEL-SIG:tunnel 10.106.0.6 1 [2]:path next hop is 10.1.0.10 (Et4/0/1)
LSP-TUNNEL-SIG:Tunnel1 [2] notified of new label information
LSP-TUNNEL-SIG:sending ADD RESV reply for tunnel 10.106.0.6 1 [2]
debug mpls traffic-eng tunnels state
To print information about state maintenance for traffic engineering tunnels, use the debugmplstraffic-engtunnelsstate command in privileged EXEC mode. To disable debugging output, use the no form of this command.
(Optional) Uses the specified access list to filter the debugging information. Prints information about state maintenance for traffic engineering tunnels that match the access list.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(3)T
This command was introduced.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.0(22)S
This command was integrated into Cisco IOS Release 12.0(22)S.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about state maintenance for traffic engineering tunnels that match access list number 99:
Router# debug mpls traffic-eng tunnels state detail 99
LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: “Connected” -> “Disconnected”
LSP-TUNNEL:Tunnel1 received event:LSP has gone down
LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: “Disconnected” -> “Dead”
LSP-TUNNEL-SIG:Tunnel1:changing state from up to down
LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: “Dead” -> “Connected”
debug mpls traffic-eng tunnels timers
To print information about traffic engineering tunnel timer management, use the debugmplstraffic-engtunnelstimers command in privileged EXEC mode. To disable debugging output, use the no form of this command.
(Optional) Uses the specified access list to filter the debugging information. Prints information about traffic engineering tunnel timer management that matches the access list.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-numberargument were added.
12.0(10)ST
This command was integrated into Cisco IOS Release 12.0(10)ST.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel timer management:
Router# debug mpls traffic-eng tunnels timers detail
LSP-TUNNEL-TIMER:timer fired for Action Scheduler
LSP-TUNNEL-TIMER:timer fired for Tunnel Head Checkup
debug mpls vpn ha
To enable the display of Virtual Private Network (VPN) high availability (HA) debugging information, use the debugmplsvpnhacommand in privileged EXEC mode. To disable the display of VPN HA debugging information, use the no form of this command.
debugmplsvpnha
nodebugmplsvpnha
Syntax Description
This command has no arguments or keywords.
Command Default
VPN HA debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(33)SRA
This command was introduced.
12.2(31)SB
This command was integrated into Cisco IOS Release 12.2(31)SB.
Examples
The following example shows sample output from the debug mpls vpn ha command:
Router# debug mpls vpn ha
VPN HA debugging is on.
debug mpls xtagatm cross-connect
Note
Effective Cisco IOS Release 12.4(20)T, the
debugmplsxtagatmcross-connect command is not available in Cisco IOS software.
To display requests and responses for establishing and removing cross-connects on the controlled ATM switch, use the
debugmplsxtagatmcross-connectcommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplsxtagatmcross-connect
nodebugmplsxtagatmcross-connect
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(20)T
This command was removed.
Usage Guidelines
This command monitors requests to establish or remove cross-connects from XmplsATM interfaces to the Virtual Switch Interface (VSI) master, as well as the VSI master responses to these requests.
Note
Use this command with care, because it generates output for each cross-connect operation performed by the label switch controller (LSC). In a network configuration with many label virtual circuits (LVCs), the volume of output generated can interfere with system timing and the proper operation of other router functions. Use this command only in situations in which the LVC setup or teardown rate is low.
Examples
The following is sample output from the
debugmplsxtagatmcross-connect command:
The following table describes the significant fields shown in the display.
Table 21 debug mpls xtagatm cross-connect Field Descriptions
Field
Description
XTagATM
The source of the debugging message as an XmplsATM interface.
cross-conn
An indicator that the debugging message pertains to a cross-connect setup or teardown operation.
request
A request from an XmplsATM interface to the VSI master to set up or tear down a cross-connect.
response
Response from the VSI master to an XmplsATM interface that a cross-connect was set up or removed.
SETUP
A request for the setup of a cross-connect.
TEARDOWN
A request for the teardown of a cross-connect.
UP
The cross-connect is established.
DOWN
The cross-connect is not established.
userdata, userbits
Values passed with the request that are returned in the corresponding fields in the matching response.
prec
The precedence for the cross-connect.
result
The status of the completed request.
0xC0100 (Ctl-If) 1/32
Information about the interface:
One endpoint of the cross-connect is on the interface whose logical interface number is 0xC0100.
The interface is the VSI control interface.
The virtual path identifier (VPI) value at this endpoint is 1.
The virtual channel identifier (VCI) value at this end of the cross-connect is 32.
<->
The type of cross-connect (unidirectional or bidirectional).
0xC0200 (XTagATM0) 0/32
Information about the interface:
The other endpoint of the cross-connect is on the interface whose logical interface number is 0xC0200.
The interface is associated with XmplsATM interface 0.
The VPI value at this endpoint is 0.
The VCI value at this end of the cross-connect is 32.
->
The response pertains to a unidirectional cross-connect.
Related Commands
Command
Description
showxtagatmcross-connect
Displays information about remotely connected ATM switches.
debug mpls xtagatm errors
Note
Effective with Cisco IOS Release 12.4(20)T, thedebugmplsxtagatmerrors command is not available in Cisco IOS software.
To display
information about error and abnormal conditions that occur on XmplsATM interfaces, use the debugmplsxtagatmerrorscommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmplsxtagatmerrors
nodebugmplsxtagatmerrors
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.4(20)T
This command was removed.
Usage Guidelines
Use the debugmplsxtagatmerrors command to display information about abnormal conditions and events that occur on XmplsATM interfaces.
Examples
The following is sample output from the debugmplsxtagatmerrors command:
This message indicates a failed attempt to set up a
cross-connect for a terminating a virtual circuit (VC) on XmplsATM0. The reason for the failure was a lack of resources on the controlled ATM switch.
debug mpls xtagatm events
Note
Effective with Cisco IOS Release 12.4(20)T, thedebugmplsxtagatmevents command is not available in Cisco IOS software.
To display information about major events that occur on XmplsATM interfaces, not including events for specific XmplsATM virtual circuits (VCs) and switch cross-connects, use the
debugmplsxtagatmeventscommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplsxtagatmevents
nodebugmplsxtagatmevents
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Command
Modification
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.4(20)T
This command was removed.
Usage Guidelines
Use the
debugmplsxtagatmevents command to monitor major events that occur on XmplsATM interfaces. This command monitors events that pertain only to XmplsATM interfaces as a whole and does not include any events that pertain to individual XmplsATM VCs or individual switch cross-connects. The specific events that are monitored when the
debugmplsxtagatmevents command is in effect include the following:
Receiving asynchronous notifications that the VSI master sent through the external ATM application programming interface (ExATM API) to an XmplsATM interface.
Resizing of the table that is used to store switch cross-connect information. This table is resized automatically as the number of cross-connects increases.
Marking of XmplsATM VCs as stale when an XmplsATM interface shuts down, thereby ensuring that the stale interfaces are refreshed before new XmplsATM VCs can be created on the interface.
Examples
The following is sample output from the
debugmplsxtagatmevents command:
Router# debug mpls xtagatm events
XTagATM: desired cross-connect table size set to 256
XTagATM: ExATM API intf event Up, port 0xA0100 (None)
XTagATM: ExATM API intf event Down, port 0xA0100 (None)
XTagATM: marking all VCs stale on XTagATM0
The following table describes the significant fields shown in the display.
Table 22 debug mpls xtagatm events Field Descriptions
Field
Description
XTagATM
The source of the debugging message.
desired cross-connect table size set to 256
The table of cross-connect information has been set to hold 256 entries. A single cross-connect table is shared among all XmplsATM interfaces. The cross-connect table is automatically resized as the number of cross-connects increases.
ExATM API
The information in the debug output pertains to an asynchronous notification sent by the Virtual Switch Interface (VSI) master to the XmplsATM driver.
event Up/Down
The specific event that was sent by the VSI master to the XmplsATM driver.
port 0xA0100 (None)
The event pertains to the VSI interface whose logical interface number is 0xA0100, and that this logical interface is not bound to an XmplsATM interface.
marking all VCs stale on XTagATM0
All existing XmplsATM VCs on interface XmplsATM0 are marked as stale, and that XmplsATM0 remains down until all of these VCs are refreshed.
debug mpls xtagatm vc
Note
Effective with Cisco IOS Release 12.4(20)T, the
debugmplsxtagatmvc command is not available in Cisco IOS software.
To display information about events that affect individual XmplsATM terminating virtual circuits (VCs), use the
debugmplsxtagatmvccommand in privileged EXEC mode. To disable debugging output, use the
no form of this command.
debugmplsxtagatmvc
nodebugmplsxtagatmvc
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.4(20)T
This command was removed.
Usage Guidelines
Use the
debugmplsxtagatmvc command to display detailed information about all events that affect individual XmplsATM terminating VCs.
Note
Use this command with care, because it results in extensive output when many XmplsATM VCs are set up or torn down. This output can interfere with system timing and normal operation of other router functions. Use the
debugmplsxtagatmvc command only when a few XmplsATM VCs are created or removed.
Examples
The following is sample output from the
debugmplsxtagatmvc command:
The following table describes the significant fields shown in the display.
Table 23 debug mpls xtagatm vc Field Descriptions
Field
Description
XTagATM VC
The source of the debugging message.
XTagATM <ifnum>
The particular XmplsATM interface number for the terminating VC.
vcd vpi/vci
The virtual circuit descriptor (VCD) and virtual path identifier/virtual channel identifier (VPI/VCI) values for the terminating VC.
(ctl-if vcd vpi/vci)
The control interface, the VCD, and the VPI and VCI values for the private VC corresponding to the XmplsATM VC on the control interface.
Setup, Complete, Teardown
The name of the event that occurred for the indicated VC.
oldstate -> newstate
The state of the terminating VC before and after the processing of the event.
debug mpoa client
Note
Effective with Cisco IOS Release 15.1M, the debugmpoaclientcommand is not available in Cisco IOS software.
To display Multiprotocol over ATM (MPOA) client debug information, use the debugmpoaclientcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
MPOA :debugmpoaclientcommanddebugmpoaclientcommanddebugmpoaclient
{ all | data | egress | general | ingress | keep-alives | platform-specific }
[ namempc-name ]
nodebugmpoaclient
{ all | data | egress | general | ingress | keep-alives | platform-specific }
[ namempc-name ]
Syntax Description
all
Displays debugging information for all MPC activity.
data
Displays debugging information for data plane activity only. This option applies only to routers.
egress
Displays debugging information for egress functionality only.
general
Displays general debugging information only.
ingress
Displays debugging information for ingress functionality only.
keep-alives
Displays debugging information for keep-alive activity only.
platform-specific
Displays debugging information for specific platforms only. This option applies only to the Catalyst 5000 series ATM module.
namempc-name
(Optional) Specifies the name of the MPC with the specified name.
Command Default
Debugging is turned on for all MPOA Clients (MPCs).
Command Modes
Privileged EXEC
Command History
Release
Modification
11.3
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
15.1M
This command was removed.
Examples
The following shows how to turn on debugging for the MPC ip_mpc:
ATM# debug mpoa client all name ip_mpc
Related Commands
Command
Description
debugmpoaserver
Displays information about the MPOA server.
debug mpoa server
Note
Effective with Cisco IOS Release 15.1M, the debugmpoaservercommand is not available in Cisco IOS software.
To display information about the Multiprotocol over ATM (MPOA) server, use the debugmpoaserver command in privileged EXEC mode. To disable debugging output, use the no form of this command.
This command was integrated into Cisco IOS Release 12.2(33)SRA.
15.1M
This command was removed.
Usage Guidelines
The debugmpoaservercommand optionally limits the output only to the specified MPOA Server (MPS).
Examples
The following turns on debugging only for the MPS named ip_mps:
Router# debug mpoa server name ip_mps
debug mrcp
To display debugging messages for Media Resource Control Protocol (MRCP) operations, use the debugmrcpcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmrcp
{ all | api | detail | error | pmh | session | socket | state }
nodebugmrcp
{ all | api | detail | error | pmh | session | socket | state }
Syntax Description
all
Displays all MRCP debugging messages.
api
Displays messages between the application and the MRCP stack.
detail
Displays detailed MRCP version 2 (MRCP v2) debugging messages.
error
Displays MRCP error messages.
pmh
Displays protocol message handler (PMH) messages.
session
Displays messages about active MRCP sessions.
socket
Displays MRCP v2 socket debugging messages
state
Displays Finite State Machine (FSM) messages.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(11)T
This command was introduced on the Cisco 3640, Cisco 3660, Cisco AS5300, Cisco AS5350, and Cisco AS5400.
12.4(15)T
This command was modified to support MRCP v2. The detail and socket keywords were added.
Examples
The following example shows output from the debugmrcpapicommand:
Router# debug mrcp api
The first four lines show Real Time Streaming Protocol (RTSP) socket commands for Text-To-Speech (TTS) operations:
The following example shows output from the debugmrcpsocketcommand:
Router# debug mrcp socket
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_tcp_socket_connect:
Socket=0,Dest=10.1.2.201:51001
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_connect_to_server:
SocketConnectStatus[MRCPV2_SOCK_CONNECT_PENDING(2)], SocketId=0,
ServerSession=0xC0732278, Dest=10.1.2.201:51001
*Sep 1 21:52:58.392: //-1//MRCP:/mrcpv2_handle_socket_read:
Before Execute: Socket=0, SocketStatus=MRCPV2_SOCK_CONNECT_PENDING(2)
*Sep 1 21:52:58.392: //-1//MRCP:/mrcpv2_handle_socket_read:
After Execute: Socket=0, SocketStatus=MRCPV2_SOCK_CONNECTED(1)
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send:
(Socket:0 Length:87) 600 bytes of data
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send:
Buffer Sent Successfully; fd=0, Sent=87
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send:
(Socket:0 Length:64) 600 bytes of data
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send:
Buffer Sent Successfully; fd=0, Sent=64
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send:
(Socket:0 Length:94) 600 bytes of data
*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send:
Buffer Sent Successfully; fd=0, Sent=94
Related Commands
Command
Description
showmrcpclientsessionactive
Displays information about active MRCP sessions.
showmrcpclientsessionhistory
Displays information about past MRCP sessions.
showmrcpclientstatisticshostname
Displays statistics about MRCP sessions.
debug mspi receive
Note
Effective with release 12.3(8)T, the debugmspireceivecommand is replaced by the debugfaxmspicommand. See the debugfaxmspicommand for more information.
To display debugging messages for the receiving mail Service Provider Interface (MSPI), use the debugmspireceivecommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmspireceive
nodebugmspireceive
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(3)XI
This command was introduced on the Cisco AS5300 universal access server.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
12.2(4)T
This command was implemented on the Cisco 1750 access router.
12.3(8)T
This command was replaced by the debugfaxmspicommand.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following is sample output from the debugmspireceivecommand:
Router# debug mspi receive
Jan 1 05:09:33.890: mspi_tel_num_trans: from: Radhika,
ph#in: fax=5271714 ph#dial: 5271714
Jan 1 05:09:33.890: incoming destPat(5271714), matched(7), tag(22)
Jan 1 05:09:33.890: out destPat(5......), tag(20), dgt strip enabled
Jan 1 05:09:33.890: mspi_off_new_rcpt: envlp_to [fax=5271714@smith.abccompany.com], 30
Jan 1 05:09:33.890: tel_numb_dial: 5271714, subaddr:[], cover page
Jan 1 05:09:39.122: mspi_offramp_rfc822_header: msgType=0
Jan 1 05:09:39.122: envlp_from: [Radhika], 8
Jan 1 05:09:39.122: mspi_off_put_buff: ignore mime type=1, st=CONNECTING, len=0
Jan 1 05:09:39.122: moff_save_buffer: cid=0x1F, mime=9, len=4
Jan 1 05:09:39.122: offramp disabled receiving!
Dec 31 21:09:44.078: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 5271714
Jan 1 05:09:52.154: mspi_bridge: cid=0x1F, dst cid=0x22, data dir=OFFRAMP, conf dir=DEST
Jan 1 05:09:52.154: mspi_offramp_send_buffer: cid=0x1F, mime=9
Jan 1 05:09:52.154: buffer with only CR/LF - set buff_len=0
Jan 1 05:09:52.154: mspi_offramp_send_buffer: cid=0x1F, mime=9 rx BUFF_END_OF_PART, offramp rcpt enabled
Jan 1 05:09:54.126: mspi_offramp_send_buffer: cid=0x1F, mime=11
Jan 1 05:09:54.134: mspi_offramp_send_buffer: cid=0x1F, mime=11
Related Commands
Command
Description
debugmspisend
Displays debugging messages for MSPI send.
debug mspi send
Note
Effective with Cisco IOS Release 12.3(8)T, the debugmspisendcommand is replaced by the debugfaxmspicommand. See the debugfaxmspicommand for more information.
To display debugging messages for the sending mail Service Provider Interface (MSPI), use the debugmspisendcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmspisend
nodebugmspisend
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(3)XI
This command was introduced on the Cisco AS5300 universal access server.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
12.2(4)T
This command was introduced on the Cisco 1750 access router.
12.3(8)T
This command was replaced by the debugfaxmspicommand.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following is sample output from the debugmspisend command:
Effective with release 12.3(8)T, the debugmtareceivallcommand is replaced by the debugfaxmtacommand. See the debugfaxmtacommand for more information.
To show output relating to the activity on the Simple Mail Transfer Protocol (SMTP) server, use the debugmtareceiveallcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmtareceiveall
nodebugmtareceiveall
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(4)T
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
12.2(4)T
This command was implemented on the Cisco 1750 access router.
12.2(8)T
This command was implemented on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.
12.2(13)T
This feature was implemented on the Cisco 7200 series routers.
12.3(8)T
This command was replaced by the debugfaxmtacommand.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following example shows the messages exchanged (for example, the handshake) between the e-mail server and the off-ramp gateway:
Router# debug mta receive all
Jan 1 05:07:41.314: esmtp_server_work: calling helo
Jan 1 05:07:43.354: esmtp_server_work: calling mail
Jan 1 05:07:45.386: esmtp_server_work: calling rcpt
Jan 1 05:07:47.426: esmtp_server_work: calling data
Jan 1 05:07:49.514: (S)R: 'Content-Type: multipart/mixed; boundary="------------11F7CD9D2EB3E8B8D5627C62"'
Jan 1 05:07:49.514: (S)R: ''
Jan 1 05:07:49.514: esmtp_server_engine_new_part:
Jan 1 05:07:49.514: (S)R: 'Content-Type: text/plain; charset=us-ascii'
Jan 1 05:07:49.514: (S)R: 'Content-Transfer-Encoding: 7bit'
Jan 1 05:07:49.514: (S)R: ''
Jan 1 05:07:49.514: esmtp_server_engine_new_part:
Jan 1 05:07:49.514: esmtp_server_work: freeing temp header
Jan 1 05:07:49.514: (S)R: 'Content-Type: image/tiff; name="DevTest.8.1610.tif"'
Jan 1 05:07:49.514: (S)R: 'Content-Transfer-Encoding: base64'
Jan 1 05:07:49.514: (S)R: 'Content-Disposition: inline; filename="DevTest.8.1610.tif"'
Jan 1 05:07:49.514: (S)R: ''
Jan 1 05:07:49.514: esmtp_server_engine_update_recipient_status: status=6
Jan 1 05:07:49.514: esmtp_server_engine_new_part:
Jan 1 05:07:49.518: esmtp_server_work: freeing temp header
Jan 1 05:08:03.014: esmtp_server_engine_update_recipient_status: status=7
Jan 1 05:08:04.822: esmtp_server_engine_update_recipient_status: status=6
Jan 1 05:08:33.042: esmtp_server_engine_update_recipient_status: status=7
Jan 1 05:08:34.906: esmtp_server_engine_getline: Unexpected end of file on socket 1
Jan 1 05:08:34.906: esmtp_server_work: error occurred with ctx=0x61FFF710, socket=1
Related Commands
Command
Description
debugmtasendall
Displays output for all the on-ramp client connections.
debug mta send all
Note
Effective with release 12.3(8)T, the debugmtasendallcommand is replaced by the debugfaxmtacommand. See the debugfaxmtacommand for more information.
To display output for all of the on-ramp client connections, use the debugmtasendallcommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmtasendall
nodebugmtasendall
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(4)T
This command was introduced.
12.2(4)T
This command was implemented on the Cisco 1750 access router.
12.2(8)T
This command was implemented on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.
12.2(13)T
This feature was implemented on the Cisco 7200 series routers.
12.3(8)T
This command was replaced by the debugfaxmta command.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following example shows the messages exchanged (for example, the handshake) between the e-mail server and the on-ramp gateway:
Router# debug mta send all
*Oct 16 09:04:13.055: esmtp_client_engine_open: from=5551212@fax.cisco.com, to=madeup@abccompany.com
*Oct 16 09:04:13.055: esmtp_client_engine_add_headers: from_comment=
*Oct 16 09:04:13.111: esmtp_client_work: socket 0 attempting to connect to IP address 171.71.154.56
*Oct 16 09:04:13.111: esmtp_client_work: socket 0 readable for first time
*Oct 16 09:04:13.135: esmtp_client_work: socket 0 readable for first time
*Oct 16 09:04:13.135: (C)R: 220 madeup.abccompany.com ESMTP Sendmail 8.8.4-Cisco.1/8.6.5 ready at Wed, 27 Sep 2000 11:45:46 -0700 (PDT)
*Oct 16 09:04:13.135: (C)S: EHLO mmoip-c.cisco.com
*Oct 16 09:04:13.183: (C)R: 250-madeup.abccompany.com Hello [172.22.95.16], pleased to meet you
*Oct 16 09:04:13.183: (C)R: 250-EXPN
*Oct 16 09:04:13.183: (C)R: 250-VERB
Related Commands
Command
Description
debugmtasendrcpt-to
Displays output for a specific on-ramp SMTP client connection during an e-mail transmission.
debug mta send rcpt-to
Note
Effective with release 12.3(8)T, the debugmtasendrcpt-tocommand is no longer available in Cisco IOS.
To display output for a specific on-ramp Simple Mail Transfer Protocol (SMTP) client connection during an e-mail transmission, use the debugmtasendrcpt-tocommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmtasendrcpt-tostring
nodebugmtasendrcpt-tostring
Syntax Description
string
E-mail address.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0(4)T
This command was introduced.
12.2(4)T
This command was implemented on the Cisco 1750 access router.
12.2(8)T
This command was implemented on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.
12.2(13)T
This feature was implemented on the Cisco 7200 series routers.
12.3(8)T
This command was removed and is no longer available in Cisco IOS software.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Examples
The following example shows debugging information displayed when the debugmtasendrcpt-tocommand has been enabled and the SMTP client is sending an e-mail message:
Router# debug mta send rcpt-to 5551212
Router# socket 0 attempting to connect to IP address 100.00.00.00
socket 0 readable for first time - let's try to read it
R:220 madeup.abc.com ESMTP Sendmail 8.8.4-abc.1/8.6.5 ready at Tue, 6
Apr 1999 13:35:39 -0700 (PDT)
S:EHLO mmoip-c.abc.com
R:250-quisp.cisco.com Hello [100.00.00.00], pleased to meet you
R:250-EXPN
R:250-VERB
R:250-8BITMIME
R:250-SIZE
R:250-DSN
R:250-ETRN
R:250-XUSR
R:250 HELP
S:MAIL FROM:<testing@> RET=HDRS
R:250 <testing@>... Sender ok
S:RCPT TO:<madeup@abc.com> NOTIFY=SUCCESS ORCPT=rfc822;testing@
R:250 <madeup@abc.com>... Recipient ok
R:354 Enter mail, end with "." on a line by itself
S:Received:(Cisco Powered Fax System) by mmoip-c.cisco.com for
<madeup@abc.com> (with Cisco NetWorks); Fri, 17 Oct 1997 14:54:27 +0800
S:To: <madeup@abc.com>
S:Message-ID:<000F1997145427146@mmoip-c.cisco.com>
S:Date:Fri, 17 Oct 1997 14:54:27 +0800
S:Subject:mmoip-c subject here
S:X-Mailer:IOS (tm) 5300 Software (C5300-IS-M)
S:MIME-Version:1.0
S:Content-Type:multipart/mixed;
S: boundary="yradnuoB=_000E1997145426826.mmoip-ccisco.com"
S:From:"Test User" <testing@>
S:--yradnuoB=_000E1997145426826.mmoip-ccisco.com
S:Content-ID:<00101997145427150@mmoip-c.cisco.com>
S:--yradnuoB=_000E1997145426826.mmoip-ccisco.com--
Sending terminating dot ...(socket=0)
S:.
R:250 NAA09092 Message accepted for delivery
S:QUIT
R:221 madeup@abc.com closing connection
Freeing SMTP ctx at 0x6121D454
returned from work_routine, context freed
Related Commands
Command
Description
debugmtasendall
Displays output for all the on-ramp client connections.
debug mvrp
To display debugging information for Multiple VLAN Registration Protocol (MVRP) configurations, use the debugmvrp command in privileged EXEC mode. To disable debugging of MVRP configurations, use the no form of this command.
debugmvrp
[ all | config | error | event | ha | packets | switch ]
nodebugmvrp
Syntax Description
all
(Optional) Enables all levels of debugging
config
(Optional) Displays user configuration information.
error
(Optional) Enables error-level debugging.
event
(Optional) Enables event-level debugging.
ha
(Optional) Enables high availability-level debugging.
packets
(Optional) Enables packet-level debugging.
switch
(Optional) Enables switch-level debugging.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
12.2(33)SXI
This command was introduced.
Usage Guidelines
Conditional interface debugging can be used to limit the scope of output messages related to an interface.
Cisco Catalyst 6000 Series Platforms
On switches with a Switch Processor (SP) or Route Processor (RP), this command can be used only on the SP console.
Examples
The following example shows switch-level debugging enabled:
Router# debug mvrp switch
Related Commands
Command
Description
clearmvrpstatistics
Clears statistics related to MVRP and recorded on one (or all) MVRP-enabled ports.
showmvrp
Displays statistics for configured MVRP attributes on a device or specified ports on a device.
debug mwi relay errors
To debug message waiting indication (MWI) relay errors, use the debugmwirelayerrorscommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmwirelayerrors
nodebugmwirelayerrors
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(2)XT
This command was introduced on the following platforms: Cisco 1750, Cisco 1751, Cisco 2600 series and Cisco 3600 series multiservice routers; and Cisco IAD2420 series Integrated Access Devices (IADs).
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 3725 and Cisco 3745 routers.
12.2(8)T1
This command was implemented on the Cisco 2600-XM and Cisco 2691 routers.
12.2(11)T
This command was implemented on the Cisco 1760 routers.
Usage Guidelines
The debugmwirelayerrors command provides a debug monitor display of any error messages, when MWI Relay Server (Cisco IOS Telephony Server) is trying to do MWI Relay to extensions on remote Cisco IOS Telephony Service (ITS).
Examples
The following examples show errors when MWI Relay Server tries to do an MWI Relay to extension 7004, but location of 7004 is not known to the MWI Relay Server:
Router#debug mwi relay errors
mwi-relay error info debugging is on
01:46:48: MWI-APP: mwi_notify_status: No ClientID (7004) registered
Related Commands
Command
Description
debugephonemwi
Sets MWI debugging for the Cisco IOS Telephony Service router.
debugmwirelayevents
Sets MWI relay events debugging for the Cisco IOS Telephony Service router.
debug mwi relay events
To set message waiting indication (MWI) relay events debugging, use the debugmwirelayeventscommand in privileged EXEC mode. To disable debugging output, use the no form of this command.
debugmwirelayevents
nodebugmwirelayevents
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
Modification
12.2(2)XT
This command was introduced on the following platforms: Cisco 1750, Cisco 1751, Cisco 2600 series and Cisco 3600 series multiservice routers; and Cisco IAD2420 series Integrated Access Devices (IADs).
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 3725 and Cisco 3745 routers.
12.2(8)T1
This command was implemented on the Cisco 2600-XM and Cisco 2691 routers.
12.2(11)T
This command was implemented on the Cisco 1760 routers.
Usage Guidelines
The debugmwirelayevents command provides a debug monitor display of events, when MWI Relay Server (Cisco IOS Telephony Server) is trying to do MWI Relay to extensions on remote Cisco IOS Telephony Services (ITS).
Examples
The following debugging messages are shown when the MWI Relay server tries to send MWI Information to remote client 7001 and the location of 7001 is known by the MWI Relay Server:
Router# debug mwi relay events
mwi-relay events info debugging is on
01:45:34: mwi_notify_status: Queued event for mwi_app_queue
01:45:34: MWI-APP: mwi_app_process_event:
01:45:34: MWI-APP: mwi_app_process_event: MWI Event for ClientID(7001)@(1.8.17.22)
Related Commands
Command
Description
debugephonemwi
Sets MWI debugging for the Cisco IOS Telephony Service router.
debugmwirelayerrors
Sets MWI relay errors debugging for the Cisco IOS Telephony Service router.