|
|
Table Of Contents
debug archive config timestamp
debug archive log config persistent
debug backhaul-session-manager session
debug backhaul-session-manager set
debug appn pc
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Path Control (PC) component activity, use the debug appn pc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn pc
no debug appn pc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The PC component is responsible for passing Message Units (MUs) between the Data Link Control (DLC) layer and other APPN components. PC implements transmission priority by passing higher priority MUs to the DLC before lower priority MUs.
Examples
The following is sample output from the debug appn pc command. In this example an MU is received from the network.
Router# debug appn pcTurned on event 040000FFAPPN: ----- PC-----PC Deq REMOTE msg variant_name 2251APPN: --PC-- mu received to PC lpid: A80AECAPPN: --PC-- mu received from p_cep_id: 67C6F8APPN: ----- PC-----PC Deq LSA_IPS from DLCAPPN: --PCX dequeued a DATA.INDAPPN: --- PC processing DL_DATA.indAPPN: --PC-- mu_error_checker with no error, calling frrAPPN: --PC-- calling frr for packet received on LFSID: 1 2 3APPN: ----- PC-----PC is sending MU to SC A90396APPN: ----- SC-----send mu: A90396, rpc: 0, nws: 7, rh.b1: 90APPN: SC: Send mu.snf: 8, th.b0: 2E, rh.b1: 90, dcf: 8Table 15 describes the significant fields shown in the display.
Related Commands
debug appn ps
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Presentation Services (PS) component activity, use the debug appn ps command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn ps
no debug appn ps
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The PS component is responsible for managing the Transaction Programs (TPs) used by APPN. TPs are used for sending and receiving searches, receiving resource registration, and sending and receiving topology updates.
Examples
The following is sample output from the debug appn ps command. In this example a CP capabilities exchange is in progress.
Router# debug appn psTurned on event 200000FFAPPN: ---- CCA --- CP_CAPABILITIES_TP has startedAPPN: ---- CCA --- About to wait for Partner to send CP_CAPAPPN: ---- CCA --- Partner LU name: NETA.PATTYAPPN: ---- CCA --- Mode Name: CPSVCMGAPPN: ---- CCA --- CGID: 78APPN: ---- CCA --- About to send cp_cp_session_act to SSAPPN: ---- CCA --- Waiting for cp_cp_session_act_rsp from SSAPPN: ---- CCA --- Received cp_cp_session_act_rsp from SSAPPN: ---- CCA --- About to send CP_CAP to partnerAPPN: ---- CCA --- Send to partner completed with rc=0, 0APPN: ---- RCA --- Allocating conversationAPPN: ---- RCA --- Sending CP_CAPABILITIESAPPN: ---- RCA --- Getting conversation attributesAPPN: ---- RCA --- Waiting for partner to send CP_CAPABILITIESAPPN: ---- RCA --- Normal processing complete with cgid = 82APPN: ---- RCA --- Deallocating CP_Capabilities conversationTable 16 describes the significant fields shown in the display.
Table 16 debug appn ps Field Descriptions
APPN
APPN debugging output.
CCA
CP Capabilities TP output.
RCA
Receive CP Capabilities TP output.
Related Commands
debug appn scm
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Session Connector Manager (SCM) component activity, use the debug appn scm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn scm
no debug appn scm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The SCM component is responsible for the activation and deactivation of the local resources that route an intermediate session through the router.
Examples
The following is sample output from the debug appn scm command. In this example an intermediate session traffic is being routed.
Router# debug appn scmTurned on event 020000FFRouter#APPN: ----- SCM-----SCM Deq a MUAPPN: ----- SCM-----SCM send ISR_INIT to SSIAPPN: ----- SCM-----(i05) Enter compare_fqpcid()APPN: ----- SCM-----Adding new session_info table entry. addr=A93160APPN: ----- SCM-----SCM Deq ISR_CINIT messageAPPN: ----- SCM-----(i05) Enter compare_fqpcid()APPN: ----- SCM-----SCM sends ASSIGN_LFSID to ASMAPPN: ----- SCM-----SCM Rcvd sync ASSIGN_LFSID from ASMAPPN: ----- SCM-----SCM PQenq a MU to ASMAPPN: ----- SCM-----SCM Deq a MUAPPN: ----- SCM-----(i05) Enter compare_fqpcid()APPN: ----- SCM-----SCM PQenq BIND rsp to ASMTable 17 describes the significant fields shown in the display.
Table 17 debug appn scm Field Descriptions
APPN
APPN debugging output.
SCM
SCM component output.
Related Commands
debug appn ss
To display session services (SS) events, use the debug appn ss command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn ss
no debug appn ss
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The SS component generates unique session identifiers, activates and deactivates control point-to-control point (CP-CP) sessions, and assists logical units (LUs) in initiating and activating LU-LU sessions.
Examples
The following is sample output from the debug appn ss command. In this example CP-CP sessions between the router and another node are being activated.
Router# debug appn ssTurned on event 100000FFAPPN: ----- SS ----- Deq ADJACENT_CP_CONTACTED messageAPPN: ----- SS ----- Deq SESSST_SIGNAL messageAPPN: ----- SS ----- Deq CP_CP_SESSION_ACT messageAPPN: Sending ADJACENT_NN_1015 to SCM, adj_node_p=A6B980,cp_name=NETA.PATTYAPPN: ----- SS ----- Sending REQUEST_LAST_FRSN message to TRSAPPN: ----- SS ----- Receiving REQUEST_LAST_FRSN_RSP from TRSAPPN: ----- SS ----- Sending ACTIVE CP_STATUS CONLOSER message to DSAPPN: ----- SS ----- Sending ACTIVE CP_STATUS CONLOSER message to MSAPPN: ----- SS ----- Sending ACTIVE CP_STATUS CONLOSER message to TRSAPPN: ----- SS ----- Sending CP_CP_SESSION_ACT_RSP message to CCA TPAPPN: ----- SS ----- Sending PENDING_ACTIVE CP_STATUS CONWINNER message to DSAPPN: ----- SS ----- Sending REQUEST_LAST_FRSN message to TRSAPPN: ----- SS ----- Receiving REQUEST_LAST_FRSN_RSP from TRSAPPN: ----- SS ----- Sending ACT_CP_CP_SESSION message to RCA TPAPPN: ----- SS ----- Deq ASSIGN_PCID messageAPPN: ----- SS ----- Sending ASSIGN_PCID_RSP message to someoneAPPN: ----- SS ----- Deq INIT_SIGNAL messageAPPN: ----- SS ----- Sending REQUEST_COS_TPF_VECTOR message to TRSAPPN: ----- SS ----- Receiving an REQUEST_COS_TPF_VECTOR_RSP from TRSAPPN: ----- SS ----- Sending REQUEST_SINGLE_HOP_ROUTE message to TRSAPPN: ----- SS ----- Receiving an REQUEST_SINGLE_HOP_ROUTE_RSP from TRSAPPN: ----- SS ----- Sending ACTIVATE_ROUTE message to CSAPPN: ----- SS ----- Deq ACTIVATE_ROUTE_RSP messageAPPN: ----- SS ----- Sending CINIT_SIGNAL message to SMAPPN: ----- SS ----- Deq ACT_CP_CP_SESSION_RSP messageAPPN: -- SS----SS ssp00, act_cp_cp_session_rsp received, sense_code=0, cgid=5C, ips@=A93790APPN: Sending ADJACENT_NN_1015 to SCM, adj_node_p=A6B980,cp_name=18sAPPN: ----- SS ----- Sending ACTIVE CP_STATUS CONWINNER message to DSAPPN: ----- SS ----- Sending ACTIVE CP_STATUS CONWINNER message to MSAPPN: ----- SS ----- Sending ACTIVE CP_STATUS CONWINNER message to TRSTable 18 describes the significant fields shown in the display.
Table 18 debug appn ss Field Descriptions
APPN
APPN debugging output.
SS
SS component output.
Related Commands
debug appn trs
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Topology and Routing Services (TRS) component activity, use the debug appn trs command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn trs
no debug appn trs
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The TRS component is responsible for creating and maintaining the topology database, creating and maintaining the class of service database, and computing and caching optimal routes through the network.
Examples
The following is sample output from the debug appn trs command:
Router# debug appn trsTurned on event 400000FFAPPN: ----- TRS ----- Received a QUERY_CPNAMEAPPN: ----- TRS ----- Received a REQUEST_ROUTEAPPN: ----- TRS ----- check_node node_name=NETA.LISAAPPN: ----- TRS ----- check_node node_index=0APPN: ----- TRS ----- check_node node_weight=60APPN: ----- TRS ----- add index 484 to origin description listAPPN: ----- TRS ----- add index 0 to dest description listAPPN: ----- TRS ----- origin tg_vector is NULLAPPN: ----- TRS ----- weight_to_origin = 0APPN: ----- TRS ----- weight_to_dest = 0APPN: ----- TRS ----- u_b_s_f weight = 30APPN: ----- TRS ----- u_b_s_f prev_weight = 2147483647APPN: ----- TRS ----- u_b_s_f origin_index = 484APPN: ----- TRS ----- u_b_s_f dest_index = 0APPN: ----- TRS ----- b_r_s_f weight = 30APPN: ----- TRS ----- b_r_s_f origin_index = 484APPN: ----- TRS ----- b_r_s_f dest_index = 0APPN: ----- TRS ----- Received a REQUEST_ROUTEAPPN: ----- TRS ----- check_node node_name=NETA.LISAAPPN: ----- TRS ----- check_node node_index=0APPN: ----- TRS ----- check_node node_weight=60APPN: ----- TRS ----- check_node node_name=NETA.BARTAPPN: ----- TRS ----- check_node node_index=484APPN: ----- TRS ----- check_node node_weight=60APPN: ----- TRS ----- add index 484 to origin description listAPPN: ----- TRS ----- add index 0 to dest description listAPPN: ----- TRS ----- origin_tg_weight to non-VN=30APPN: ----- TRS ----- origin_node_weight to non-VN=60APPN: ----- TRS ----- weight_to_origin = 90APPN: ----- TRS ----- weight_to_dest = 0APPN: ----- TRS ----- u_b_s_f weight = 120APPN: ----- TRS ----- u_b_s_f prev_weight = 2147483647APPN: ----- TRS ----- u_b_s_f origin_index = 484APPN: ----- TRS ----- u_b_s_f dest_index = 0APPN: ----- TRS ----- b_r_s_f weight = 120APPN: ----- TRS ----- b_r_s_f origin_index = 484APPN: ----- TRS ----- b_r_s_f dest_index = 0Table 19 describes the significant fields shown in the display.
Table 19 debug appn trs Field Descriptions
APPN
APPN debugging output.
TRS
TRS component output.
debug arap
To display AppleTalk Remote Access Protocol (ARAP) events, use the debug arap command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug arap {internal | memory | mnp4 | v42bis} [linenum [aux | console | tty | vty]]
no debug arap {internal | memory | mnp4 | v42bis} [linenum [aux | console | tty | vty]]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug arap command with the debug callback command on access servers to debug dialin and callback events.
Use the debug modem command to help catch problems related to ARAP autodetection (that is, autoselect arap). These problems are very common and are most often caused by modems, which are the most common cause of failure in ARAP connection and configuration sessions.
Examples
The following is sample output from the debug arap internal command:
Router# debug arap internalARAP: ---------- SRVRVERSION ----------ARAP: ---------- ACKing 0 ----------ARAP: ---------- AUTH_CHALLENGE ----------arapsec_local_account setting up callbackARAP: ---------- ACKing 1 ----------ARAP: ---------- AUTH_RESPONSE ----------arap_startup initiating callback ARAP 2.0ARAP: ---------- CALLBACK ----------TTY7 Callback process initiated, user: dialback dialstring 40TTY7 Callback forced wait = 4 secondsTTY7 ARAP Callback Successful - await exec/autoselect pickupTTY7: Callback in effectARAP: ---------- STARTINFOFROMSERVER ----------ARAP: ---------- ACKing 0 ----------ARAP: ---------- ZONELISTINFO ----------ARAP: ---------- ZONELISTINFO ----------ARAP: ---------- ZONELISTINFO ----------ARAP: ---------- ZONELISTINFO ----------ARAP: ---------- ZONELISTINFO ----------Related Commands
debug archive config timestamp
To enable debugging of the processing time for each integral step of a configuration replace operation and the size of the configuration files being handled, use the debug archive config timestamp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug archive config timestamp
no debug archive config timestamp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.3(7)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
Examples
The following is sample output from the debug archive config timestamp command:
Router# debug archive config timestampRouter# configure replace disk0:myconfig forceTiming Debug Statistics for IOS Config Replace operation:Time to read file slot0:sample_2.cfg = 0 msec (0 sec)Number of lines read:55Size of file :1054Starting Pass 1Time to read file system:running-config = 0 msec (0 sec)Number of lines read:93Size of file :2539Time taken for positive rollback pass = 320 msec (0 sec)Time taken for negative rollback pass = 0 msec (0 sec)Time taken for negative incremental diffs pass = 59 msec (0 sec)Time taken by PI to apply changes = 0 msec (0 sec)Time taken for Pass 1 = 380 msec (0 sec)Starting Pass 2Time to read file system:running-config = 0 msec (0 sec)Number of lines read:55Size of file :1054Time taken for positive rollback pass = 0 msec (0 sec)Time taken for negative rollback pass = 0 msec (0 sec)Time taken for Pass 2 = 0 msec (0 sec)Total number of passes:1Rollback DoneRelated Commands
debug archive versioning
Enables debugging of the Cisco IOS configuration archive activities.
debug archive log config persistent
To turn on debugging of configuration logging persistent events and display the results, use the debug archive log config persistent command in privileged EXEC mode. To disable debugging and display the archived events, use the no form of this command.
debug archive log config persistent
no debug archive log config persistent
Syntax Description
This command has no arguments or keywords.
Command Default
If you do not enter this command, you cannot debug or display the configuration logging persistent events in the archive.
Command Modes
Privileged EXEC
Command History
12.2(33)SRA
This command was introduced.
12.4(11)T
This command was integrated into Cisco IOS Release 12.4(11)T.
Usage Guidelines
The Configuration Logger Persistency feature must be enabled in order for debug to work.
Examples
The following example shows how to turn on the debugging feature and display configuration logging persistent events:
Router# debug archive log config persistentRouter# archive log config persistent saveConfiguration logging persistent save triggered.Saving the config log to disk0:IOS-Config-Logger-database'.Command `interface eth0' savedCommand `ip address 10.1.1.1 255.255.255.255' savedCommand `no shut' savedRelated Commands
archive log config persistent save
Saves the persisted commands in the configuration log to the Cisco IOS secure file system.
debug archive versioning
To enable debugging of the Cisco IOS configuration archive activities, use the debug archive versioning command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug archive versioning
no debug archive versioning
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.3(7)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
Examples
The following is sample output from the debug archive versioning command:
Router# debug archive versioningJan 9 06:46:28.419:backup_running_configJan 9 06:46:28.419:Current = 7Jan 9 06:46:28.443:Writing backup file disk0:myconfig-7Jan 9 06:46:29.547: backup workedRelated Commands
debug arp
To display information on Address Resolution Protocol (ARP) transactions, use the debug arp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug arp
no debug arp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command when some nodes on a TCP/IP network are responding, but others are not. It shows whether the router is sending ARP packets and whether it is receiving ARP packets.
Examples
The following is sample output from the debug arp command:
Router# debug arpIP ARP: sent req src 172.16.22.7 0000.0c01.e117, dst 172.16.22.96 0000.0000.0000IP ARP: rcvd rep src 172.16.22.96 0800.2010.b908, dst 172.16.22.7IP ARP: rcvd req src 172.16.6.10 0000.0c00.6fa2, dst 172.16.6.62IP ARP: rep filtered src 172.16.22.7 aa92.1b36.a456, dst 255.255.255.255 ffff.ffff.ffffIP ARP: rep filtered src 172.16.9.7 0000.0c00.6b31, dst 172.16.22.7 0800.2010.b908In the output, each line of output represents an ARP packet that the router sent or received. Explanations for the individual lines of output follow.
The first line indicates that the router at IP address 172.16.22.7 and MAC address 0000.0c01.e117 sent an ARP request for the MAC address of the host at 172.16.22.96. The series of zeros (0000.0000.0000) following this address indicate that the router is currently unaware of the MAC address.
IP ARP: sent req src 172.16.22.7 0000.0c01.e117, dst 172.16.22.96 0000.0000.0000The second line indicates that the router at IP address 172.16.22.7 receives a reply from the host at 172.16.22.96 indicating that its MAC address is 0800.2010.b908:
IP ARP: rcvd rep src 172.16.22.96 0800.2010.b908, dst 172.16.22.7The third line indicates that the router receives an ARP request from the host at 172.16.6.10 requesting the MAC address for the host at 172.16.6.62:
IP ARP: rcvd req src 172.16.6.10 0000.0c00.6fa2, dst 172.16.6.62The fourth line indicates that another host on the network attempted to send the router an ARP reply for its own address. The router ignores meaningless replies. Usually, meaningless replies happen if a bridge is being run in parallel with the router and is allowing ARP to be bridged. This condition indicates a network misconfiguration.
IP ARP: rep filtered src 172.16.22.7 aa92.1b36.a456, dst 255.255.255.255 ffff.ffff.ffffThe fifth line indicates that another host on the network attempted to inform the router that it is on network 172.16.9.7, but the router does not know that the network is attached to a different router interface. The remote host (probably a PC or an X terminal) is misconfigured. If the router were to install this entry, it would deny service to the real machine on the proper cable.
IP ARP: rep filtered src 172.16.9.7 0000.0c00.6b31, dst 172.16.22.7 0800.2010.b908debug ase
To gather Automatic Signature Extraction (ASE) error, log, messaging, reporting, status, and timer information, use the debug ase command in privileged EXEC mode. To disable error, log, messaging, reporting, status, and timer information, use the no form of this command.
debug ase {errors | log | messages | reports | status | timing}
no debug ase {errors | log | messages | reports | status | timing}
Syntax Description
Command Default
Disabled
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command is used on the Cisco 1800, 2800, and 7200 series routers, Cisco 7301 router, and Integrated Services Routers (ISRs) as ASE sensors.
Related Commands
debug asnl events
To trace event logs in the Application Subscribe Notify Layer (ASNL), use the debug asnl events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug asnl events
no debug asnl events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command traces the event logs in the ASNL, which serves as the interface layer between the application and protocol stacks. Event logs are generated during normal subscription processing, when the application responds to the notification request and when the session history table is updated.
Examples
The following example shows the ASNL subscription table being generated and the associated subscription timers as the application responds to the subscription request. The response timer is started to determine if the application responds to the notification request. If the application that made the subscription does not respond to the notification request within 5 seconds, the system automatically removes the subscription. The session-history-record deletion timer is also started. When the timer expires, the history record is removed from the active subscription table.
Router# debug asnl eventsApplication Subscribe Notify Layer Events debugging is on*May 4 06:26:19.091://-1//ASNL:SUB-1:/asnl_process_is_up:Creating subscription table*May 4 06:26:19.091://5//ASNL:SUB1:/asnl_subscribe:resp = ASNL_SUBCRIBE_PENDING[2]*May 4 06:26:19.615://5//ASNL:SUB1:/asnl_start_timer:timer (0x63146C44)starts - delay (5000)*May 4 06:26:19.619://-1//ASNL:SUB1:/asnl_stop_timer:timer(0x63146C44) stops*May 4 06:26:19.619://-1//ASNL:SUB1:/asnl_notify_ack:ret=0x0c5300-5#*May 4 06:26:24.631://5//ASNL:SUB1:/asnl_start_timer:timer (0x63146C44)starts - delay (5000)*May 4 06:26:24.631://-1//ASNL:SUB1:/asnl_stop_timer:timer(0x63146C44) stops*May 4 06:26:24.635://-1//ASNL:SUB1:/asnl_notify_ack:ret=0x0c5300-5#*May 4 06:26:29.647://5//ASNL:SUB1:/asnl_start_timer:timer (0x63146C44)starts - delay (5000)*May 4 06:26:29.647://-1//ASNL:SUB1:/asnl_stop_timer:timer(0x63146C44) stops*May 4 06:26:29.651://-1//ASNL:SUB1:/asnl_notify_ack:ret=0x0*May 4 06:26:34.663://5//ASNL:SUB1:/asnl_start_timer:timer (0x63146C44)starts - delay (5000)*May 4 06:26:34.663://-1//ASNL:SUB1:/asnl_stop_timer:timer(0x63146C44) stops*May 4 06:26:34.667://-1//ASNL:SUB-1:/asnl_create_session_history:Creating Session History*May 4 06:26:34.667://-1//ASNL:SUB-1:/asnl_insert_session_history_record:starting history record deletion_timer of 15 minutes*May 4 06:26:34.667://-1//ASNL:SUB1:/asnl_notify_ack:ret=0x0Related Commands
debug asp packet
To display information on all asynchronous security protocols (ASPs) operating on the router, use the debug asp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug asp packet
no debug asp packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The router uses asynchronous security protocols from companies including ADT Security Systems, Inc., Adplex, and Diebold to transport alarm blocks between two devices (such as a security alarm system console and an alarm panel). The alarm blocks are transported in pass-through mode using BSTUN encapsulation.
Examples
The following is partial sample output from the debug asp packet command for asynchronous security protocols when packet debugging is enabled on an asynchronous line carrying Diebold alarm traffic. In this example, two polls are sent from the Diebold alarm console to two alarm panels that are multidropped from a single EIA/TIA-232 interface. The alarm panels have device addresses F0 and F1. The example trace indicates that F1 is responding and F0 is not responding. At this point, you need to examine the physical link and possibly use a datascope to determine why the device is not responding.
Router# debug asp packet12:19:48: ASP: Serial5: ADI-Rx: Data (4 bytes): F1FF4C4212:19:49: ASP: Serial5: ADI-Tx: Data (1 bytes): 8812:19:49: ASP: Serial5: ADI-Rx: Data (4 bytes): F0FF9B9412:20:47: ASP: Serial5: ADI-Rx: Data (4 bytes): F1FF757B12:20:48: ASP: Serial5: ADI-Tx: Data (1 bytes): F312:20:48: ASP: Serial5: ADI-Rx: Data (4 bytes): F0FFB1BE12:21:46: ASP: Serial5: ADI-Rx: Data (4 bytes): F1FFE6E812:21:46: ASP: Serial5: ADI-Tx: Data (1 bytes): 6F12:21:46: ASP: Serial5: ADI-Rx: Data (4 bytes): F0FFC1CETable 20 describes the significant fields shown in the display.
debug aspp event
To display asynchronous point of sale (APOS) event debug messages, use the debug aspp event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aspp event
no debug aspp event
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug aspp event command should be used with the debug aspp packet command to display all available details of the APOS call flow.
Examples
The following is sample output from the debug aspp event command for a simple transaction:
Router# debug aspp eventASPP event debugging is onRouter#ASPP APOS: Serial0/1: Serial HayesAT: state = DISCONNECTEDASPP APOS: Serial0/1: Received HayesAT DIAL: state = DISCONNECTEDASPP APIP: Serial0/1: Serial ENABLE: state = CONNECTINGASPP APIP: Serial0/1: Network ENABLE: state = CONNECTINGASPP APOS: Serial0/1: Send HayesAT CONNECT 9600: state = CONNECTEDASPP APOS: Serial0/1: Response timer expired: state = CONNECTEDASPP APOS: Serial0/1: Response timer expired: state = CONNECTEDASPP APOS: Serial0/1: Serial DATA: state = CONNECTEDASPP APIP: Serial0/1: Serial DATA: state = CONNECTEDASPP APIP: Serial0/1: Network DATA: state = CONNECTEDASPP APOS: Serial0/1: Serial ACK: state = CONNECTEDASPP APOS: Serial0/1: Disconnect timer expired: state = DISCONNECT WAITASPP APIP: Serial0/1: Serial DISABLE: state = DISCONNECTINGASPP APIP: Serial0/1: Network DISABLE: state = DISCONNECTINGTable 21 describes the significant fields shown in the display.
Related Commands
debug aspp packet
To display asynchronous point of sale (APOS) packet debug messages, use the debug aspp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aspp packet
no debug aspp packet
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug aspp packet command should be used with the debug aspp event command to display all available details of the APOS call flow.
Examples
The following is sample output from the debug aspp packet command for a simple transaction:
Router# debug aspp packetASPP event debugging is onRouter#ASPP:Serial1/7:ADI-rx:Data (14 bytes): 415456302644325331313D35300DASPP:Serial1/7:ADI-tx:Data (2 bytes): 300DASPP:Serial1/7:ADI-rx:Data (27 bytes): 4154583453393D3153373D323444543138303039ASPP:Serial1/7:ADI-tx:Data (3 bytes): 31320DASPP:Serial1/7:ADI-tx:Data (1 bytes): 05ASPP:Serial1/7:ADI-rx:Data (5 bytes): 0212340325ASPP:Serial1/7:ADI-tx:Data (5 bytes): 025678032DASPP:Serial1/7:ADI-rx:Data (1 bytes): 06ASPP:Serial1/7:ADI-tx:Data (1 bytes): 04Table 22 describes the significant fields shown in the display.
Related Commands
debug async async-queue
To display debug messages for asynchronous rotary line queueing, use the debug async async-queue command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug async async-queue
no debug async async-queue
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example starts the asynchronous rotary line queueing debugging display:
Router# debug async async-queue*Mar 2 03:50:28.377: AsyncQ: First connection to be queued - starting the AsyncQ manager*Mar 2 03:50:28.377: AsyncQ: Enabling the AsyncQ manager*Mar 2 03:50:28.377: AsyncQ: Started the AsyncQ manager process with pid 98*Mar 2 03:50:28.381: AsyncQ: Created a Waiting TTY on TTY66 with pid 99*Mar 2 03:50:30.164: WaitingTTY66: Did Authentication on waiting TTY (VTY)*Mar 2 03:50:30.168: AsyncQ: Received ASYNCQ_MSG_ADD*Mar 2 03:50:30.168: AsyncQ: New queue, adding this connection as the first element*Mar 2 03:50:34.920: AsyncQ: Created a Waiting TTY on TTY67 with pid 100*Mar 2 03:50:36.783: WaitingTTY67: Did Authentication on waiting TTY (VTY)*Mar 2 03:50:36.787: AsyncQ: Received ASYNCQ_MSG_ADD*Mar 2 03:50:36.787: AsyncQ: Queue exists, adding this connection to the end of the queueRelated Commands
debug atm bundle error
To display debug messages for switched virtual circuit (SVC) bundle errors, use the debug atm bundle error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm bundle error
no debug atm bundle error
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example provides output for the debug atm bundle error command:
Router# debug atm bundle errorRelated Commands
debug atm bundle events
To display switched virtual circuit (SVC) bundle events, use the debug atm bundle events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm bundle events
no debug atm bundle events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example provides output for the debug atm bundle events command:
Router# debug atm bundle events01:14:35:BUNDLE EVENT(test):b_update_vc for four with bstate 1, vc_state401:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x01 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x02 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x04 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x08 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x10 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x20 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x40 001:14:35:BUNDLE EVENT(test):bmupdate active precedence 0x80 0 -01:14:35:BUNDLE EVENT(test):bundle precedence updatedTable 23 describes the significant fields shown in the display.
.
Related Commands
debug atm events
To display ATM events, use the debug atm events command in privileged EXEC mode. To disable event debugging output, use the no form of this command.
debug atm events
no debug atm events
Syntax Description
This command has no arguments or keywords.
Defaults
ATM event debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays ATM events that occur on the ATM interface processor and is useful for diagnosing problems in an ATM network. It provides an overall picture of the stability of the network. In a stable network, the debug atm events command does not return any information. If the command generates numerous messages, the messages can indicate the possible source of problems.
When configuring or making changes to a router or interface for ATM, enable the debug atm events command. Doing so alerts you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.
Examples
The following is sample output from the debug atm events command:
Router# debug atm eventsRESET(ATM4/0): PLIM type is 1, Rate is 100Mbpsaip_disable(ATM4/0): state=1config(ATM4/0)aip_love_note(ATM4/0): asr=0x201aip_enable(ATM4/0)aip_love_note(ATM4/0): asr=0x4000aip_enable(ATM4/0): restarting VCs: 7aip_setup_vc(ATM4/0): vc:1 vpi:1 vci:1aip_love_note(ATM4/0): asr=0x200aip_setup_vc(ATM4/0): vc:2 vpi:2 vci:2aip_love_note(ATM4/0): asr=0x200aip_setup_vc(ATM4/0): vc:3 vpi:3 vci:3aip_love_note(ATM4/0): asr=0x200aip_setup_vc(ATM4/0): vc:4 vpi:4 vci:4aip_love_note(ATM4/0): asr=0x200aip_setup_vc(ATM4/0): vc:6 vpi:6 vci:6aip_love_note(ATM4/0): asr=0x200aip_setup_vc(ATM4/0): vc:7 vpi:7 vci:7aip_love_note(ATM4/0): asr=0x200aip_setup_vc(ATM4/0): vc:11 vpi:11 vci:11aip_love_note(ATM4/0): asr=0x200Table 24 describes the significant fields shown in the display.
The following line indicates that the AIP was reset. The PLIM TYPE detected was 1, so the maximum rate is set to 100 Mbps.
RESET(ATM4/0): PLIM type is 1, Rate is 100MbpsThe following line indicates that the AIP was given a shutdown command, but the current configuration indicates that the AIP should be up:
aip_disable(ATM4/0): state=1The following line indicates that a configuration command has been completed by the AIP:
aip_love_note(ATM4/0): asr=0x201The following line indicates that the AIP was given a no shutdown command to take it out of shutdown:
aip_enable(ATM4/0)The following line indicates that the AIP detected a carrier state change. It does not indicate that the carrier is down or up, only that it has changed.
aip_love_note(ATM4/0): asr=0x4000The following line of output indicates that the AIP enable function is restarting all permanent virtual circuits (PVCs) automatically:
aip_enable(ATM4/0): restarting VCs: 7The following lines of output indicate that PVC 1 was set up and a successful completion code was returned:
aip_setup_vc(ATM4/0): vc:1 vpi:1 vci:1aip_love_note(ATM4/0): asr=0x200debug atm lfi
To display multilink PPP (MLP) over ATM link fragmentation and interleaving (LFI) debug information, use the debug atm lfi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm lfi
no debug atm lfi
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following examples show output from the debug atm lfi command. Each example is preceded by an explanation of the output.
•
The following output indicates that the packet has dequeued from the per-VC queue that is associated with the virtual circuit (VC):
00:17:27: MLP-ATM(Virtual-Access3) pak dequeued from per VC Q 15/200,qcount:0•
00:17:27: MLP-ATM(Virtual-Access3) pak enqueued to per VC Q 15/200, qcount:0•
00:17:27: MLP-ATM(Virtual-Access3) pak dequeued from MP Bundle 15/200, qcount:0•
00:17:27: MLP-ATM(Virtual-Access3) encapsulation failure - dropping packet•
00:17:27: MLP-ATM(Virtual-Access3) No VC to transmit- dropping packet•
00:17:27: MLP-ATM(Virtual-Access3) mlp de-configured for PVC 15/200•
00:17:27: MLP-ATM(Virtual-Access3) MLPoATM re-configured for PVC 15/200•
00:17:27: MLP-ATM(Virtual-Access3) Memory allocation error•
00:17:27: MLP-ATM(Virtual-Access3) MLPoATM configured for PVC 15/200Related Commands
debug atm native
To display ATM switched virtual circuit (SVC) signaling events, use the debug atm native command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm native {api | conn | error | filter}
no debug atm native
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Native ATM API is the layer above the signaling API. Static map and Resource Reservation Protocol (RSVP) clients use the native ATM API to interact with the signaling API to create ATM SVCs.
Use the debug atm native command to diagnose problems in the creation of static map and RSVP ATM SVCs.
Examples
The following is sample output for the debug atm native command with the api keyword:
Router# debug atm native api0:24:59:NATIVE ATM :associate endpoint00:24:59:NATIVE ATM :ID (3) prep outgoing call, conn_type 000:24:59:NATIVE ATM :ID (3) set connection attribute for 500:24:59:NATIVE ATM :ID (3) query connection attribute 800:24:59:NATIVE ATM :ID (3) set connection attribute for 800:24:59:NATIVE ATM :ID (3) set connection attribute for 900:24:59:NATIVE ATM :ID (3) set connection attribute for 1000:24:59:NATIVE ATM :ID (3) set connection attribute for 700:24:59:NATIVE ATM :ID (3) set connection attribute for 600:24:59:NATIVE ATM :ID (3) set connection attribute for 200:24:59:NATIVE ATM :ID (3) set connection attribute for 000:24:59:NATIVE ATM :ID (3) query connection attribute 1200:24:59:NATIVE ATM :ID (3) set connection attribute for 1200:24:59:NATIVE ATM :ID (3) query connection attribute 1300:24:59:NATIVE ATM :ID (3) set connection attribute for 1300:24:59:NATIVE ATM :ID (3) connect outgoing call00:24:59:NATIVE ATM :ID (3) callback, CONNECT receiveddebug atm nbma
To display setup and teardown events for ATM switched virtual circuits (SVCs) configured using the Resource Reservation Protocol (RSVP), use the debug atm nbma command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm nbma [api]
no debug atm nbma
Syntax Description
api
(Optional) Nonbroadcast multiaccess (NBMA) ATM application programming interface (API). Displays events that occur as a result of the exchange between RSVP and the NBMA API.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug atm nbma command to diagnose problems in the creation of RSVP SVCs.
The RSVP application creates SVCs by using the NBMA API. The debug atm nbma command with the api keyword displays events that occur as a result of the exchange between RSVP and the NBMA API.
Examples
The following is sample output for the debug atm nbma command:
Router# debug atm nbma api00:52:50:NBMA-ATM-API - atm_setup_req00:52:50:NBMA_ATM-API - nbma_atm_fill_blli00:52:50:NBMA_ATM-API - nbma_atm_fill_bhli00:52:50:NBMA_ATM-API - nbma_atm_callbackMsg - NATIVE_ATM_OUTGOING_CALL_ACTIVE00:52:50:NBMA_ATM-API - rcv_outgoing_call_active00:52:50:NBMA_ATM-API - nbma_svc_lookupdebug atm oam cc
To display ATM operation, administration, and maintenance (OAM) F5 continuity check (CC) management activity, use the debug atm oam cc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm oam cc [interface atm number]
no debug atm oam cc [interface atm number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.2(2)XB
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Examples
The following sample output for the debug atm oam cc command records activity beginning with the entry of the oam-pvc manage cc command and ending with the entry of the no oam-pvc manage cc command. The ATM 0 interface is specified, and the "both" segment direction is specified. The output shows an activation request sent and confirmed, a series of CC cells sent by the routers on each end of the segment, and a deactivation request and confirmation.
Router# debug atm oam cc interface atm0Generic ATM:ATM OAM CC cells debugging is onRouter#00:15:05: CC ACTIVATE MSG (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAMType:8 OAM Func:1 Direction:3 CTag:500:15:05: CC ACTIVATE CONFIRM MSG (ATM0) O:VCD#1 VC 1/40 OAM CellType:4 OAM Type:8 OAM Func:1 Direction:3 CTag:500:15:06: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:100:15:07: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:08: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:09: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:10: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:11: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:12: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:13: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:14: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:15: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:16: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:17: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:18: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:19: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:19: CC DEACTIVATE MSG (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAMType:8 OAM Func:1 Direction:3 CTag:600:15:19: CC DEACTIVATE CONFIRM MSG (ATM0) O:VCD#1 VC 1/40 OAM CellType:4 OAM Type:8 OAM Func:1 Direction:3 CTag:6Table 25 describes the significant fields shown in the display.
Related Commands
oam-pvc manage cc
Configures ATM OAM F5 CC management.
show atm pvc
Displays all ATM PVCs and traffic information.
debug atm oc3 pom
To display debug messages for ATM-OC3 Provisioning Object Manager (POM) modules, use the debug atm oc3 pom command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm oc3 pom {data | flow | pa | sar | sfp | trace}
no debug atm oc3 pom {data | flow | pa | sar | sfp | trace}
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
debug atm oc3 pom data command
Use the debug atm oc3 pom data command to display packet indications for incoming packets. Each incoming packet transferred by direct memory access (DMA) to the host memory by the SAR will cause a packet indication.
debug atm oc3 pom flow command
Use the debug atm oc3 pom flow command to display flow control indications.
When traffic sent to the SAR exceeds the peak cell rate for a particular virtual circuit (VC), the SAR indicates this to the host by sending flow control indications. These indications inform the host that either the high water mark or the low water mark has been reached for that VC queue.
When a high water mark is received from the SAR, indicating that the VC queue is full, the host will stop sending packets to the SAR until a low water mark indication is received. A low water mark indicates that the VC queue has been drained sufficiently to receive additional packets.
debug atm oc3 pom pa command
Use the debug atm oc3 pom pa command on those platforms supporting OIR to display the indications generated when the port adapter (the ATM-OC3 POM network module) is subjected to OIR. This command is used principally during the port adapter initialization phase.
debug atm oc3 pom sar command
Use the debug atm oc3 pom sar command to display blocking commands or indications sent to or received from the SAR. This includes commands or indications of the creation or deletion of virtual circuits or virtual paths.
debug atm oc3 pom sfp command
Use the debug atm oc3 pom sfp command to display the indications generated when a module in the SFP port is subjected to OIR.
debug atm oc3 pom trace command
Use the debug atm oc3 pom trace command to display the hexadecimal representation of commands sent to or received from the SAR. To facilitate debugging, use this command in conjunction with the debug atm oc3 pom sar command.
Examples
Example for the debug atm oc3 pom data command
The following example illustrates the output from the debug atm oc3 pom data command:
Router# debug atm oc3 pom dataDATA debugging is onRouter#*Jun 27 22:03:17.996: Packet Indication:*Jun 27 22:03:17.996: word 0: 0x00007D24*Jun 27 22:03:17.996: word 1: 0x00002F02*Jun 27 22:03:17.996: word 2: 0xEE323464*Jun 27 22:03:17.996: word 3: 0x006C006DTable 26 describes the significant fields shown in the display.
Example for the debug atm oc3 pom flow command
The following example illustrates the output from the debug atm oc3 pom flow command:
Router# debug atm oc3 pom flowFLOW CNTL INDICATION debugging is onRouter#*Jun 27 15:14:13.123: Flow Indication:*Jun 27 15:14:13.123: word 0: 0x00000001*Jun 27 15:14:13.123: word 1: 0x300012C0*Jun 27 15:14:13.123: word 2: 0x18001060*Jun 27 15:14:13.123: word 3: 0x00080021*Jun 27 15:14:13.456: Flow Indication:*Jun 27 15:14:13.456: word 0: 0x00000001*Jun 27 15:14:13.456: word 1: 0x300012C0*Jun 27 15:14:13.456: word 2: 0x18001060*Jun 27 15:14:13.456: word 3: 0x00090022Table 27 describes the significant fields shown in the display.
Examples for the debug atm oc3 pom pa command
The following examples illustrate the output from the debug atm oc3 pom pa command.
The first example gives the output when the network module is removed.
Router# debug atm oc3 pom paPA debugging is on*Jun 27 22:40:56.110: %OIR-6-REMCARD: Card removed from slot 2, interfaces disabled*Jun 27 22:40:56.122: *** Freed 6146 buffersThe second example gives the output when the network module is inserted, and gives the values of internal registers of the module.
*Jun 27 22:41:08.654: %OIR-6-INSCARD: Card inserted in slot 2, interfaces administratively shut down*Jun 27 22:41:11.402: sar_base_addr 0x5C800000*Jun 27 22:41:11.402: PCI_MEMBAR2_REG after configuring:0x5E000008*Jun 27 22:41:11.402: PCI_MEMBAR3_REG after configuring:0x5F000000*Jun 27 22:41:11.402: PCI_COMMAND_REG: Offset= 0x4; value= 0x2A00006*Jun 27 22:41:11.402: FPGA Base address is 0x5C900000*Jun 27 22:41:11.402: FPGA PCI config Reg is 0x02200002Examples for the debug atm oc3 pom sar command
The following examples illustrate the output from the debug atm oc3 pom sar command.
The first example displays command indications for setting up a VC and opening the reassembly channel and the segmentation channel in the SAR
Router# debug atm oc3 pom sarSAR debugging is onRouter# configure terminalRouter(config)# interface atm 2/0Router(config-if)# pvc 2/2Router(config-if-atm-vc)# exitRouter(config-if)#*Jun 27 22:12:28.816: ATM2/0: Setup_VC: vc:3 vpi:2 vci:2*Jun 27 22:12:28.816: ATM2/0: Open_Channel(RSY): CH (1), VPI (2), VCI (2)*Jun 27 22:12:28.816: ATM2/0: HI/LO watermarks: 526/263; PeakRate: 149760*Jun 27 22:12:28.816: ATM2/0: Open_Channel(SEG): CH (1), VPI (2), VCI (2)*Jun 27 22:12:28.820: ATM2/0: Setup_Cos: vc:3 wred_name:- max_q:0The second example displays the commands sent to the SAR and the acknowledgements returned when the VC is deleted and the segmentation and reassembly channels are closed.
Router(config-if)# no pvc 2/2Router(config-if)#*Jun 27 22:12:59.016: ATM2/0: Sent pending EOP successfully*Jun 27 22:12:59.016: ATM2/0: Close_Channel(RSY): Chan_ID (0x104)*Jun 27 22:12:59.016: ATM2/0: Close_Channel(RSY): Chan_ID (0x104) CLOSE*Jun 27 22:12:59.016: ATM2/0: Close_Channel: CLOSE_PENDING*Jun 27 22:12:59.016: ATM2/0: Close_Channel(SEG): Chan_ID (0x105)*Jun 27 22:12:59.016: ATM2/0: Close_Channel: CLOSEExamples for the debug atm oc3 pom sfp command
The following examples illustrate the output from the debug atm oc3 pom sfp command.
The first example gives the output when the module is removed from the SFP port.
Router# debug atm oc3 pom sfpSFP debugging is on*Jun 27 22:27:40.792: SFP TX FAULT detected*Jun 27 22:27:40.808: SFP LOS detected*Jun 27 22:27:40.812: SFP removal detected*Jun 27 22:27:41.464: NM-1A-OC3-POM: SFP 2/0 - Removed unique*Jun 27 22:27:43.464: %LINK-3-UPDOWN: Interface ATM2/0, changed state to down*Jun 27 22:27:44.464: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM2/0, changed state to downThe second example gives the output when the module is inserted in the SFP port.
*Jun 27 22:27:47.776: SFP LOS cleared*Jun 27 22:27:47.776: SFP TX FAULT detected*Jun 27 22:27:48.276: SFP present detected*Jun 27 22:27:48.276: SFP TX FAULT cleared*Jun 27 22:27:48.496: Set the Container_id to 17*Jun 27 22:27:50.496: %LINK-3-UPDOWN: Interface ATM2/0, changed state to up*Jun 27 22:27:51.496: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM2/0, changed state to upExamples for the debug atm oc3 pom trace command
The first example illustrates the output from the debug atm oc3 pom trace command when it is run without the debug atm oc3 sar command being activated:
Router# debug atm oc3 pom traceSAR CMD/ACK debugging is onRouter# configure terminalRouter(config)# interface atm 2/0router(config-if)# pvc 2/2Router(config-if-atm-vc)# exitRouter(config-if)#*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x00000480*Jun 27 22:15:09.284: word 1: 0x00012010*Jun 27 22:15:09.284: word 2: 0x00000000*Jun 27 22:15:09.284: word 3: 0x00000000*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x00000000*Jun 27 22:15:09.284: word 6: 0x00000000*Jun 27 22:15:09.284: word 7: 0x00000000*Jun 27 22:15:09.284: word 8: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00000000*Jun 27 22:15:09.284: word 1: 0x01042110*Jun 27 22:15:09.284: word 2: 0x01050000*Jun 27 22:15:09.284: word 3: 0x0000003B*Jun 27 22:15:09.284: ACK received = 200 usecs*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x01050480*Jun 27 22:15:09.284: word 1: 0x00011010*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x00010003*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x64B30000*Jun 27 22:15:09.284: word 6: 0x10C00000*Jun 27 22:15:09.284: word 7: 0x86850000*Jun 27 22:15:09.284: word 8: 0x00010040*Jun 27 22:15:09.284: word 9: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00010000*Jun 27 22:15:09.284: word 1: 0x00011110*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x0001003D*Jun 27 22:15:09.284: ACK received = 200 usecsTable 28 describes the significant fields shown in the display.
The second example illustrates the output from the debug atm oc3 pom trace command run in conjunction with the debug atm oc3 pom sar command.
In this example, each command sent to the SAR is displayed by the debug atm oc3 pom sar command. Then the hexadecimal representation of the command and its acknowledgement is displayed by the debug atm oc3 pom trace command.
Router# debug atm oc3 pom traceSAR CMD/ACK debugging is onRouter# debug atm oc3 pom sarSAR debugging is onRouter# configure terminalRouter(config)# interface atm 2/0router(config-if)# pvc 2/2Router(config-if-atm-vc)# exitRouter(config-if)#*Jun 27 22:15:09.284: ATM2/0: Setup_VC: vc:4 vpi:2 vci:2*Jun 27 22:15:09.284: ATM2/0: Open_Channel(RSY): CH (1), VPI (2), VCI (2)*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x00000480*Jun 27 22:15:09.284: word 1: 0x00012010*Jun 27 22:15:09.284: word 2: 0x00000000*Jun 27 22:15:09.284: word 3: 0x00000000*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x00000000*Jun 27 22:15:09.284: word 6: 0x00000000*Jun 27 22:15:09.284: word 7: 0x00000000*Jun 27 22:15:09.284: word 8: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00000000*Jun 27 22:15:09.284: word 1: 0x01042110*Jun 27 22:15:09.284: word 2: 0x01050000*Jun 27 22:15:09.284: word 3: 0x0000003B*Jun 27 22:15:09.284: ACK received = 200 usecs*Jun 27 22:15:09.284: ATM2/0: HI/LO watermarks: 526/263; PeakRate: 149760*Jun 27 22:15:09.284: ATM2/0: Open_Channel(SEG): CH (1), VPI (2), VCI (2)*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x01050480*Jun 27 22:15:09.284: word 1: 0x00011010*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x00010003*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x64B30000*Jun 27 22:15:09.284: word 6: 0x10C00000*Jun 27 22:15:09.284: word 7: 0x86850000*Jun 27 22:15:09.284: word 8: 0x00010040*Jun 27 22:15:09.284: word 9: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00010000*Jun 27 22:15:09.284: word 1: 0x00011110*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x0001003D*Jun 27 22:15:09.284: ACK received = 200 usecs*Jun 27 22:15:09.284: ATM2/0: Setup_Cos: vc:4 wred_name:- max_q:0debug atm t3e3
To display debug messages for ATM T3/E3 network modules, use the debug atm t3e3 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm t3e3 {data | flow | pa | sar | trace}
no debug atm t3e3 {data | flow | pa | sar | trace}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
debug atm t3e3 data command
Use the debug atm t3e3 data command to display the incoming packet indications. Each incoming packet transferred by direct memory access (DMA) to the host memory by the SAR will cause a packet indication.
debug atm t3e3 flow command
Use the debug atm t3e3 flow command to display flow control indications.
When traffic sent to the SAR exceeds the peak cell rate for a particular virtual circuit (VC), the SAR indicates this to the host by sending flow control indications. These indications inform the host that either the high watermark or the low watermark has been reached for that VC queue.
When a high watermark is received from the SAR, indicating that the VC queue is full, the host will stop sending packets to the SAR until a low watermark indication is received. A low watermark indicates that the VC queue has been drained sufficiently to receive additional packets.
debug atm t3e3 pa command
Use the debug atm t3e3 pa command on those platforms supporting OIR to display the indications generated when the port adapter (the ATM T3/E3 network module) is subjected to OIR. This command is used principally during the port adapter initialization phase.
debug atm t3e3 sar command
Use the debug atm t3e3 sar command to display blocking commands or indications sent to or received from the SAR. This includes commands or indications of the creation or deletion of virtual circuits or virtual paths.
debug atm t3e3 trace command
Use the debug atm t3e3 trace command to display the hexadecimal representation of commands sent to or received from the SAR. To facilitate debugging, use this command in conjunction with the debug atm t3e3 sar command.
Examples
Example for the debug atm t3e3 data command
The following is sample output from the debug atm t3e3 data command:
Router# debug atm t3e3 dataDATA debugging is onRouter#*Jun 27 22:03:17.996: Packet Indication:*Jun 27 22:03:17.996: word 0: 0x00007D24*Jun 27 22:03:17.996: word 1: 0x00002F02*Jun 27 22:03:17.996: word 2: 0xEE323464*Jun 27 22:03:17.996: word 3: 0x006C006DTable 26 describes the significant fields shown in the display.
Example for the debug atm t3e3 flow command
The following example illustrates the output from the debug atm t3e3 flow command:
Router# debug atm t3e3 flowFLOW CNTL INDICATION debugging is onRouter#*Jun 27 15:14:13.123: Flow Indication:*Jun 27 15:14:13.123: word 0: 0x00000001*Jun 27 15:14:13.123: word 1: 0x300012C0*Jun 27 15:14:13.123: word 2: 0x18001060*Jun 27 15:14:13.123: word 3: 0x00080021*Jun 27 15:14:13.456: Flow Indication:*Jun 27 15:14:13.456: word 0: 0x00000001*Jun 27 15:14:13.456: word 1: 0x300012C0*Jun 27 15:14:13.456: word 2: 0x18001060*Jun 27 15:14:13.456: word 3: 0x00090022Table 27 describes the significant fields shown in the display.
Examples for the debug atm t3e3 pa command
The following examples illustrate the output from the debug atm t3e3 pa command.
The first example gives the output when the network module is removed:
Router# debug atm t3e3 paPA debugging is on*Jun 27 22:40:56.110: %OIR-6-REMCARD: Card removed from slot 2, interfaces disabled*Jun 27 22:40:56.122: *** Freed 6146 buffersThe second example gives the output when the network module is inserted, and gives the values of internal registers of the module:
*Jun 27 22:41:08.654: %OIR-6-INSCARD: Card inserted in slot 2, interfaces administratively shut down*Jun 27 22:41:11.402: sar_base_addr 0x5C800000*Jun 27 22:41:11.402: PCI_MEMBAR2_REG after configuring:0x5E000008*Jun 27 22:41:11.402: PCI_MEMBAR3_REG after configuring:0x5F000000*Jun 27 22:41:11.402: PCI_COMMAND_REG: Offset= 0x4; value= 0x2A00006*Jun 27 22:41:11.402: FPGA Base address is 0x5C900000*Jun 27 22:41:11.402: FPGA PCI config Reg is 0x02200002Examples for the debug atm t3e3 sar command
The following examples illustrate the output from the debug atm t3e3 sar command.
The first example displays command indications for setting up a VC and opening the reassembly channel and the segmentation channel in the SAR:
Router# debug atm t3e3 sarSAR debugging is onRouter# configure terminalRouter(config)# interface atm 2/0Router(config-if)# pvc 2/2Router(config-if-atm-vc)# exitRouter(config-if)#*Jun 27 22:12:28.816: ATM2/0: Setup_VC: vc:3 vpi:2 vci:2*Jun 27 22:12:28.816: ATM2/0: Open_Channel(RSY): CH (1), VPI (2), VCI (2)*Jun 27 22:12:28.816: ATM2/0: HI/LO watermarks: 526/263; PeakRate: 149760*Jun 27 22:12:28.816: ATM2/0: Open_Channel(SEG): CH (1), VPI (2), VCI (2)*Jun 27 22:12:28.820: ATM2/0: Setup_Cos: vc:3 wred_name:- max_q:0The second example displays the commands sent to the SAR and the acknowledgements returned when the VC is deleted and the segmentation and reassembly channels are closed:
Router(config-if)# no pvc 2/2Router(config-if)#*Jun 27 22:12:59.016: ATM2/0: Sent pending EOP successfully*Jun 27 22:12:59.016: ATM2/0: Close_Channel(RSY): Chan_ID (0x104)*Jun 27 22:12:59.016: ATM2/0: Close_Channel(RSY): Chan_ID (0x104) CLOSE*Jun 27 22:12:59.016: ATM2/0: Close_Channel: CLOSE_PENDING*Jun 27 22:12:59.016: ATM2/0: Close_Channel(SEG): Chan_ID (0x105)*Jun 27 22:12:59.016: ATM2/0: Close_Channel: CLOSEExamples for the debug atm t3e3 trace command
The first example illustrates the output from the debug atm t3e3 trace command when it is run without the debug atm t3e3 sar command being activated:
Router# debug atm t3e3 traceSAR CMD/ACK debugging is onRouter# configure terminalRouter(config)# interface atm 2/0router(config-if)# pvc 2/2Router(config-if-atm-vc)# exitRouter(config-if)#*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x00000480*Jun 27 22:15:09.284: word 1: 0x00012010*Jun 27 22:15:09.284: word 2: 0x00000000*Jun 27 22:15:09.284: word 3: 0x00000000*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x00000000*Jun 27 22:15:09.284: word 6: 0x00000000*Jun 27 22:15:09.284: word 7: 0x00000000*Jun 27 22:15:09.284: word 8: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00000000*Jun 27 22:15:09.284: word 1: 0x01042110*Jun 27 22:15:09.284: word 2: 0x01050000*Jun 27 22:15:09.284: word 3: 0x0000003B*Jun 27 22:15:09.284: ACK received = 200 usecs*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x01050480*Jun 27 22:15:09.284: word 1: 0x00011010*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x00010003*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x64B30000*Jun 27 22:15:09.284: word 6: 0x10C00000*Jun 27 22:15:09.284: word 7: 0x86850000*Jun 27 22:15:09.284: word 8: 0x00010040*Jun 27 22:15:09.284: word 9: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00010000*Jun 27 22:15:09.284: word 1: 0x00011110*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x0001003D*Jun 27 22:15:09.284: ACK received = 200 usecsTable 28 describes the significant fields shown in the display.
The second example illustrates the output from the debug atm t3e3 trace command run in conjunction with the debug atm t3e3 sar command.
In this example, each command sent to the SAR is displayed by the debug atm t3e3 sar command. Then the hexadecimal representation of the command and its acknowledgement are displayed by the debug atm t3e3 trace command.
Router# debug atm t3e3 traceSAR CMD/ACK debugging is onRouter# debug atm t3e3 sarSAR debugging is onRouter# configure terminalRouter(config)# interface atm 2/0router(config-if)# pvc 2/2Router(config-if-atm-vc)# exitRouter(config-if)#*Jun 27 22:15:09.284: ATM2/0: Setup_VC: vc:4 vpi:2 vci:2*Jun 27 22:15:09.284: ATM2/0: Open_Channel(RSY): CH (1), VPI (2), VCI (2)*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x00000480*Jun 27 22:15:09.284: word 1: 0x00012010*Jun 27 22:15:09.284: word 2: 0x00000000*Jun 27 22:15:09.284: word 3: 0x00000000*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x00000000*Jun 27 22:15:09.284: word 6: 0x00000000*Jun 27 22:15:09.284: word 7: 0x00000000*Jun 27 22:15:09.284: word 8: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00000000*Jun 27 22:15:09.284: word 1: 0x01042110*Jun 27 22:15:09.284: word 2: 0x01050000*Jun 27 22:15:09.284: word 3: 0x0000003B*Jun 27 22:15:09.284: ACK received = 200 usecs*Jun 27 22:15:09.284: ATM2/0: HI/LO watermarks: 526/263; PeakRate: 149760*Jun 27 22:15:09.284: ATM2/0: Open_Channel(SEG): CH (1), VPI (2), VCI (2)*Jun 27 22:15:09.284: Command Sent:*Jun 27 22:15:09.284: word 0: 0x01050480*Jun 27 22:15:09.284: word 1: 0x00011010*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x00010003*Jun 27 22:15:09.284: word 4: 0x00200020*Jun 27 22:15:09.284: word 5: 0x64B30000*Jun 27 22:15:09.284: word 6: 0x10C00000*Jun 27 22:15:09.284: word 7: 0x86850000*Jun 27 22:15:09.284: word 8: 0x00010040*Jun 27 22:15:09.284: word 9: 0x00000000*Jun 27 22:15:09.284: Command Indication:*Jun 27 22:15:09.284: word 0: 0x00010000*Jun 27 22:15:09.284: word 1: 0x00011110*Jun 27 22:15:09.284: word 2: 0x02000000*Jun 27 22:15:09.284: word 3: 0x0001003D*Jun 27 22:15:09.284: ACK received = 200 usecs*Jun 27 22:15:09.284: ATM2/0: Setup_Cos: vc:4 wred_name:- max_q:0
debug audit
To display debug messages for the audit subsystem, use the debug audit command in privileged EXEC mode. To disable debugging for the audit subsystem, use the no form of this command.
debug audit
no debug audit
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(18)S
This command was introduced.
12.0(27)S
This feature was integrated into Cisco IOS Release 12.0(27)S.
Usage Guidelines
Audit files allow you to track changes that have been made to your router. Each change is logged as a syslog message, and all syslog messages are kept in the audit file, which is kept in the audit subsystem.
Examples
The following example is sample output from the debug audit command:
Router# debug audit*Sep 14 18:37:31.535:disk0:/forensics.log -> File not found*Sep 14 18:37:31.535:%AUDIT-1-RUN_VERSION:Hash:24D98B13B87D106E7E6A7E5D1B3CE0AD User:*Sep 14 18:37:31.583:%AUDIT-1-RUN_CONFIG:Hash:4AC2D776AA6FCA8FD7653CEB8969B695 User:*Sep 14 18:37:31.587:Audit:Trying to hash nvram:startup-config*Sep 14 18:37:31.587:Audit:nvram:startup-config Done.*Sep 14 18:37:31.587:Audit:Trying to hash nvram:private-config*Sep 14 18:37:31.591:Audit:nvram:private-config Done.*Sep 14 18:37:31.591:Audit:Trying to hash nvram:underlying-config*Sep 14 18:37:31.591:Audit:nvram:underlying-config Done.*Sep 14 18:37:31.591:Audit:Trying to hash nvram:persistent-data*Sep 14 18:37:31.591:Audit:nvram:persistent-data Done.*Sep 14 18:37:31.595:Audit:Trying to hash nvram:ifIndex-table*Sep 14 18:37:31.595:Audit:Skipping nvram:ifIndex-table*Sep 14 18:37:31.595:%AUDIT-1-STARTUP_CONFIG:Hash:95DD497B1BB61AB33A629124CBFEC0FC User:*Sep 14 18:37:31.595:Audit:Trying to hash filesystem disk0:*Sep 14 18:37:31.775:Audit:Trying to hash attributes ofdisk0:c7200-p-mz.120-23.S*Sep 14 18:37:32.103:Audit:disk0:c7200-p-mz.120-23.S DONE*Sep 14 18:37:32.103:Audit:disk0:DONE*Sep 14 18:37:32.103:Audit:Trying to hash filesystem bootflash:*Sep 14 18:37:32.103:Audit:Trying to hash attributes ofbootflash:c7200-kboot-mz.121-8a.E*Sep 14 18:37:32.107:Audit:bootflash:c7200-kboot-mz.121-8a.E DONE*Sep 14 18:37:32.107:Audit:Trying to hash attributes ofbootflash:crashinfo_20030115-182547*Sep 14 18:37:32.107:Audit:bootflash:crashinfo_20030115-182547 DONE*Sep 14 18:37:32.107:Audit:Trying to hash attributes ofbootflash:crashinfo_20030115-212157*Sep 14 18:37:32.107:Audit:bootflash:crashinfo_20030115-212157 DONE*Sep 14 18:37:32.107:Audit:Trying to hash attributes ofbootflash:crashinfo_20030603-155534*Sep 14 18:37:32.107:Audit:bootflash:crashinfo_20030603-155534 DONE*Sep 14 18:37:32.107:Audit:bootflash:DONE*Sep 14 18:37:32.107:%AUDIT-1-FILESYSTEM:Hash:330E7111F2B526F0B850C24ED5774EDE User:*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for 7206VXR chassis,Hw Serial#:28710795, Hw Revision:A*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for NPE 400 Card, HwSerial#:28710795, Hw Revision:A*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for I/O DualFastEthernet Controller*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for i82543(Livengood)*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for i82543(Livengood)*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot*Sep 14 18:37:32.107:%AUDIT-1-HARDWARE_CONFIG:Hash:32F66463DDA802CC9171AF6386663D20 User:Related Commands
Command
Description
audit filesize
Changes the size of the audit file.
audit interval
Changes the time interval that is used for calculating hashes.
debug auto-config
To enable debugging for auto-configuration applications, use the debug auto-config command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug auto-config {all | errors | events | parser}
no debug auto-config {all | errors | events | parser}
Syntax Description
all
Displays all auto-config debug trace.
errors
Displays auto-config errors.
events
Displays auto-config events.
parser
Displays auto-config parser.
Command Default
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the debug auto-config command used to enable debugging for auto-configuration applications and to display auto-config events:
Router# debug auto-config events...Feb 8 02:17:31.119: dnld_app_check_state(0x628C8164)...Feb 8 02:17:31.123: dnld_chk_app_handle(0x628C8164)Feb 8 02:17:31.123: dnld_app_check_state: appl = 0x628C8164, state = 0x11...Table 32 describes significant fields shown in the display.
Related Commands
debug autoupgrade
To display the debug output of the Cisco IOS Auto-Upgrade Manager (AUM), use the debug autoupgrade command in privileged EXEC mode. To disable debug output, use the no form of this command.
debug autoupgrade
no debug autoupgrade
Syntax Description
This command has no arguments or keywords.
Command Default
The debug output is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug autoupgrade command when you encounter a problem with AUM and provide the output to TAC. Run the debug autoupgrade command and then run AUM to view the debug messages.
Examples
The following example shows how to enable the debugging of Cisco IOS Auto-Upgrade Manager:
Router# debug autoupgradeAuto Upgrade Manager debugging ONRouter#Router# upgrade automatic getversion tftp://10.1.0.1/username/aaaImage not found.Router#Jun 14 14:23:08.251 IST: AUM: Currently running software: flash:c3825-adventerprisek9-mz.CALVIN_AUM_EFT1Jun 14 14:23:08.251 IST: AUM: Reload type:2 hour:0 min:0Jun 14 14:23:08.251 IST: AUM: Disk management: 1Jun 14 14:23:08.251 IST: AUM: Get image tftp://10.1.0.1/username/aaa from local server and upgrade:Jun 14 14:23:08.251 IST: AUM: Extracted image name: aaaJun 14 14:23:08.339 IST: AUM: get image info: failed to open urlJun 14 14:23:08.339 IST: AUM: get image info: image size unknownRelated Commands
upgrade automatic getversion
Downloads a Cisco IOS software image directly from www.cisco.com or from a non-Cisco server.
debug backhaul-session-manager session
To debug all the available sessions or a specified session, use the debug backhaul-session-manager session command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug backhaul-session-manager session {state | xport} {all | session-id}
no debug backhaul-session-manager session {state | xport} {all | session-id}
Caution
Syntax Description
Defaults
Debugging for backhaul-session-manager session is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is output for the debug backhaul-session-manager session all command:
Router# debug backhaul-session-manager session allRouter# debug_bsm_command:DEBUG_BSM_SESSION_ALL23:49:14:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:19:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:24:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:29:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:49:34:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 1 (CONN-FAILED)23:49:34:SESSION:STATE:(33) old-state:OPEN, new-state:CLOSE_WAITThe following example displays output for the debug backhaul-session-manager session state all command:
Router# debug backhaul-session-manager session state allRouter# debug_bsm_command:DEBUG_BSM_SESSION_STATE_ALL23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOSThe following example displays output for the debug backhaul-session-manager session xport all command:
Router# debug backhaul-session-manager session xport allRouter# debug_bsm_command:DEBUG_BSM_SESSION_XPORT23:51:39:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)23:51:42:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 5 (CONN-RESET)23:51:44:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)Related Commands
debug backhaul-session-manager set
Traces state changes and receives messages and events for all available session-sets or a specified session-set.
debug backhaul-session-manager set
To trace state changes and receive messages and events for all the available session sets or a specified session set, use the debug backhaul-session-manager set command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug backhaul-session-manager set {all | name set-name}
no debug backhaul-session-manager set {all | name set-name}
Syntax Description
Defaults
Debugging for backhaul session sets is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is output for the debug backhaul-session-manager set command for all available session sets:
Router# debug backhaul-session-manager set allRouter# debug_bsm_command:DEBUG_BSM_SET_ALLFunction set_proc_event() is calledSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_OOSActive-Grp :NONESession-Grp :g-11Old State :Group-NoneNew State :Group-NoneEvent rcvd :EVT_GRP_INSBSM:Event BSM_SET_UP is sent to userSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_ACTIVE_ISActive-Grp :g-11Session-Grp :g-11Old State :Group-NoneNew State :Group-ActiveEvent rcvd :BSM_ACTIVE_TYPEThe following is output for the debug backhaul-session-manager set name set1 command:
Router# debug backhaul-session-manager set name set1Router# debug_bsm_command:DEBUG_BSM_SET_NAMERouter# Function set_proc_event() is calledSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_OOSActive-Grp :NONESession-Grp :g-11Old State :Group-NoneNew State :Group-NoneEvent rcvd :EVT_GRP_INSRouter#BSM:Event BSM_SET_UP is sent to userSession-Set :test-setOld State :BSM_SET_OOSNew State :BSM_SET_ACTIVE_ISActive-Grp :g-11Session-Grp :g-11Old State :Group-NoneNew State :Group-ActiveEvent rcvd :BSM_ACTIVE_TYPERelated Commands
debug backhaul-session-manager session
Debugs all available sessions or a specified session.
debug backup
To monitor the transitions of an interface going down then back up, use the debug backup command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug backup
no debug backup
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug backup command is useful for monitoring dual X.25 interfaces configured as primary and backup in a Telco data communication network (DCN).
Examples
The following example shows how to start the debug backup command:
Router# debug backupRelated Commands
backup active interface
Activates primary and backup lines on specific X.25 interfaces.
show backup
Displays interface backup status.
debug bert
To display information on the bit error rate testing (BERT) feature, use the debug bert command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bert
no debug bert
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bert command output is used primarily by Cisco technical support representatives. The debug bert command displays debugging messages for specific areas of executed code.
Examples
The following is output from the debug bert command:
Router# debug bertBit Error Rate Testing debugging is onRouter# no debug bertBit Error Rate Testing debugging is offRelated Commands
debug bfd
To display debugging messages about Bidirectional Forwarding Detection (BFD), use the debug bfd command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bfd [event | packet | ipc-error | ipc-event | oir-error | oir-event]
no debug
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bfd command can be used to troubleshoot the BFD feature.
Note
Examples
The following example shows output from the debug bfd event command when an interface between two BFD neighbor routers fails and then comes back online:
Router# debug bfd event22:53:48: BFD: bfd_neighbor - action:DESTROY, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.222:53:48: BFD: bfd_neighbor - action:DESTROY, proc:512, idb:FastEthernet0/1, neighbor:172.16.10.222:53:49: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event DETECT TIMER EXPIRED, state UP -> FAILING...22:56:35: BFD: bfd_neighbor - action:CREATE, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.222:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state FAILING -> DOWN22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state DOWN -> INIT22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 1, state INIT -> UPTable 33 describes the significant fields shown in the display.
The following example shows output from the debug bfd packet command when an interface between two BFD neighbor routers fails and then comes back online. The diagnostic code changes from 0 (No Diagnostic) to 1 (Control Detection Time Expired) because no BFD control packets could be sent (and therefore detected by the BFD peer) after the interface fails. When the interface comes back online, the diagnostic code changes back to 0 to signify that BFD packets can be sent and received by the BFD peers:
Router# debug bfd packet23:03:25: Rx IP: src 172.16.10.2, plen 24. BFD: diag 0, H/D/P/F (0/0/0/0), mult 3, len 24, loc/rem discr 5 1, tx 1000000, rx 10000723:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (0/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 100000823:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 1000009Table 34 describes the significant fields shown in the display.
debug bgp ipv6 dampening
To display debugging messages for IPv6 Border Gateway Protocol (BGP) dampening, use the debug bgp ipv6 dampening command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp ipv6 dampening [prefix-list prefix-list-name]
no debug bgp ipv6 dampening [prefix-list prefix-list-name]
Syntax Description
Defaults
Debugging for IPv6 BGP dampening packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp ipv6 dampening command is similar to the debug ip bgp dampening command, except that it is IPv6-specific.
Use the prefix-list keyword and an argument to filter BGP IPv6 dampening debug information through an IPv6 prefix list.
Note
Examples
The following is sample output from the debug bgp ipv6 dampening command:
Router# debug bgp ipv6 dampening00:13:28:BGP(1):charge penalty for 2000:0:0:1::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:13:28:BGP(1):charge penalty for 2000:0:0:1:1::/80 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:13:28:BGP(1):charge penalty for 2000:0:0:5::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:16:03:BGP(1):charge penalty for 2000:0:0:1::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:16:03:BGP(1):flapped 2 times since 00:02:35. New penalty is 189200:18:28:BGP(1):suppress 2000:0:0:1:1::/80 path 2 1 for 00:27:30 (penalty 2671)00:18:28:halflife-time 15, reuse/suppress 750/200000:18:28:BGP(1):suppress 2000:0:0:1::/64 path 2 1 for 00:27:20 (penalty 2664)00:18:28:halflife-time 15, reuse/suppress 750/2000The following example shows output for the debug bgp ipv6 dampening command filtered through the prefix list named "marketing":
Router# debug bgp ipv6 dampening prefix-list marketing00:16:08:BGP(1):charge penalty for 1234::/64 path 30 with halflife-time 15 reuse/suppress 750/200000:16:08:BGP(1):flapped 1 times since 00:00:00. New penalty is 10Table 35 describes the significant fields shown in the display.
Related Commands
debug bgp ipv6 updates
To display debugging messages for IPv6 Border Gateway Protocol (BGP) update packets, use the debug bgp ipv6 updates command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp ipv6 updates [ipv6-address] [prefix-list prefix-list-name] [in | out]
no debug bgp ipv6 updates [ipv6-address] [prefix-list prefix-list-name] [in | out]
Syntax Description
Defaults
Debugging for IPv6 BGP update packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp ipv6 updates command is similar to the debug ip bgp updates command, except that it is IPv6-specific.
Use the prefix-list keyword to filter BGP IPv6 updates debugging information through an IPv6 prefix list.
Note
Examples
The following is sample output from the debug bgp ipv6 updates command:
Router# debug bgp ipv6 updates14:04:17:BGP(1):2000:0:0:2::2 computing updates, afi 1, neighbor version 0, table version 1, starting at ::14:04:17:BGP(1):2000:0:0:2::2 update run completed, afi 1, ran for 0ms, neighborversion 0, start version 1, throttled to 114:04:19:BGP(1):sourced route for 2000:0:0:2::1/64 path #0 changed (weight 32768)14:04:19:BGP(1):2000:0:0:2::1/64 route sourced locally14:04:19:BGP(1):2000:0:0:2:1::/80 route sourced locally14:04:19:BGP(1):2000:0:0:3::2/64 route sourced locally14:04:19:BGP(1):2000:0:0:4::2/64 route sourced locally14:04:22:BGP(1):2000:0:0:2::2 computing updates, afi 1, neighbor version 1, tableversion 6, starting at ::14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (format) 2000:0:0:2::1/64, next 2000:0:0:2::1,metric 0, path14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (format) 2000:0:0:2:1::/80, next 2000:0:0:2::1,metric 0, path14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (prepend, chgflags:0x208) 2000:0:0:3::2/64,next 2000:0:0:2::1, metric 0, path14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (prepend, chgflags:0x208) 2000:0:0:4::2/64,next 2000:0:0:2::1, metric 0, pathThe following is sample output from the debug bgp ipv6 updates command filtered through the prefix list named "sales":
Router# debug bgp ipv6 updates prefix-list sales00:18:26:BGP(1):2000:8493:1::2 send UPDATE (prepend, chgflags:0x208) 7878:7878::/64,next 2F02:3000::36C, metric 0, pathTable 36 describes the significant fields shown in the display.
Related Commands
debug bgp ipv6 dampening
Displays debugging messages for IPv6 BGP dampening packets.
debug bgp nsap
To enable the display of Border Gateway Protocol (BGP) debugging information specific to the network service access point (NSAP) address family, use the debug bgp nsap command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp nsap
no debug bgp nsap
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging of BGP NSAP address-family code is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp nsap command is similar to the debug ip bgp command, except that it is specific to the NSAP address family.
Note
Examples
The following example shows output for the debug bgp nsap command. The BGP(4) identifies that BGP version 4 is operational.
Router# debug bgp nsap00:46:46: BGP(4): removing CLNS route to 49.010100:46:46: BGP(4): removing CLNS route to 49.030300:46:46: BGP(4): removing CLNS route to 49.040400:46:46: BGP(4): 10.1.2.1 removing CLNS route 49.0101.1111.1111.1111.1111.00 toeBGP-neighbor00:46:46: BGP(4): 10.2.4.4 removing CLNS route 49.0303.4444.4444.4444.4444.00 toeBGP-neighbor00:46:59: BGP(4): Applying map to find origin for prefix 49.0202.222200:46:59: BGP(4): Applying map to find origin for prefix 49.0202.3333Related Commands
debug bgp nsap dampening
Displays debug messages for BGP NSAP prefix dampening events.
debug bgp nsap updates
Displays debug messages for BGP NSAP prefix update packets.
debug bgp nsap dampening
To display debug messages for Border Gateway Protocol (BGP) network service access point (NSAP) prefix address dampening, use the debug bgp nsap dampening command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp nsap dampening [filter-list access-list-number]
no debug bgp nsap dampening [filter-list access-list-number]
Syntax Description
filter-list access-list-number
(Optional) Displays debug messages for BGP NSAP dampening events that match the access list. The acceptable access list number range is from 1 to 199.
Defaults
Debugging for BGP NSAP dampening events is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp nsap dampening command is similar to the debug ip bgp dampening command, except that it is specific to the NSAP address family.
Note
Examples
The following example shows output for the debug bgp nsap dampening command:
Router# debug bgp nsap dampening16:21:34: BGP(4): Dampening route-map modified.Only one line of output is displayed unless the bgp dampening command is configured with a route map in NSAP address family configuration mode. The following example shows output for the debug bgp nsap dampening command when a route map is configured:
20:07:19: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15reuse/suppress 750/200020:07:19: BGP(4): flapped 1 times since 00:00:00. New penalty is 100020:08:59: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15reuse/suppress 750/200020:08:59: BGP(4): flapped 2 times since 00:01:39. New penalty is 192820:10:04: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15reuse/suppress 750/200020:10:04: BGP(4): flapped 3 times since 00:02:44. New penalty is 283920:10:48: BGP(4): suppress 49.0404 path 65202 65404 for 00:28:10 (penalty 2752)20:10:48: halflife-time 15, reuse/suppress 750/2000Table 37 describes the significant fields shown in the display.
Related Commands
debug bgp nsap
Displays debug messages for BGP NSAP packets.
debug bgp nsap updates
Displays debug messages for BGP NSAP update events.
debug bgp nsap updates
To display debug messages for Border Gateway Protocol (BGP) network service access point (NSAP) prefix address update packets, use the debug bgp nsap updates command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bgp nsap updates [ip-address] [in | out] [filter-set clns-filter-set-name]
no debug bgp nsap updates [ip-address] [in | out] [filter-set clns-filter-set-name]
Syntax Description
Defaults
Debugging for BGP NSAP prefix update packets is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug bgp nsap updates command is similar to the debug ip bgp updates command, except that it is specific to the NSAP address family.
Use the ip-address argument to display the BGP update debug messages for a specific BGP neighbor.
Use the clns-filter-set-name argument to display the BGP update debug messages for a specific NSAP prefix.
Note
Examples
The following example shows output for the debug bgp nsap updates command:
Router# debug bgp nsap updates02:13:45: BGP(4): 10.0.3.4 send UPDATE (format) 49.0101, next 49.0303.3333.3333.3333.3333.00, metric 0, path 65202 6510102:13:45: BGP(4): 10.0.3.4 send UPDATE (format) 49.0202, next 49.0303.3333.3333.3333.3333.00, metric 0, path 6520202:13:45: BGP(4): 10.0.3.4 send UPDATE (format) 49.0303, next 49.0303.3333.3333.3333.3333.00, metric 0, path02:13:45: BGP(4): 10.0.2.2 send UPDATE (format) 49.0404, next 49.0303.3333.3333.3333.3333.00, metric 0, path 65404Table 38 describes the significant fields shown in the display.
Related Commands
debug bgp nsap
Displays debug messages for BGP NSAP packets.
debug bgp nsap dampening
Displays debug messages for BGP NSAP prefix dampening events.
debug bri-interface
To display debugging information on ISDN BRI routing activity, use the debug bri-interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bri-interface
no debug bri-interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug bri-interface command indicates whether the ISDN code is enabling and disabling the B channels when attempting an outgoing call. This command is available for the low-end router products that have a multi-BRI network interface module installed.
Caution
Examples
The following is sample output from the debug bri-interface command:
Router# debug bri-interfaceBRI: write_sid: wrote 1B for subunit 0, slot 1.BRI: write_sid: wrote 15 for subunit 0, slot 1.BRI: write_sid: wrote 17 for subunit 0, slot 1.BRI: write_sid: wrote 6 for subunit 0, slot 1.BRI: write_sid: wrote 8 for subunit 0, slot 1.BRI: write_sid: wrote 11 for subunit 0, slot 1.BRI: write_sid: wrote 13 for subunit 0, slot 1.BRI: write_sid: wrote 29 for subunit 0, slot 1.BRI: write_sid: wrote 1B for subunit 0, slot 1.BRI: write_sid: wrote 15 for subunit 0, slot 1.BRI: write_sid: wrote 17 for subunit 0, slot 1.BRI: write_sid: wrote 20 for subunit 0, slot 1.BRI: Starting Power Up timer for unit = 0.BRI: write_sid: wrote 3 for subunit 0, slot 1.BRI: Starting T3 timer after expiry of PUP timeout for unit = 0, current state is F4.BRI: write_sid: wrote FF for subunit 0, slot 1.BRI: Activation for unit = 0, current state is F7.BRI: enable channel B1BRI: write_sid: wrote 14 for subunit 0, slot 1.%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!!BRI: disable channel B1BRI: write_sid: wrote 15 for subunit 0, slot 1.%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to downThe following line indicates that an internal command was written to the interface controller. The subunit identifies the first interface in the slot.
BRI: write_sid: wrote 1B for subunit 0, slot 1.The following line indicates that the power-up timer was started for the named unit:
BRI: Starting Power Up timer for unit = 0.The following lines indicate that the channel or the protocol on the interface changed state:
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!!%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to downThe following line indicates that the channel was disabled:
BRI: disable channel B1Lines of output not described are for use by support staff only.
Related Commands
debug bsc event
To display all events occurring in the Binary Synchronous Communications (Bisync) feature, use the debug bsc event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bsc event [number]
no debug bsc event [number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command traces all interfaces configured with a bsc protocol-group number command.
Examples
The following is sample output from the debug bsc event command:
Router# debug bsc eventBSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFileBSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFileBSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFile0:04:32: BSC: Serial2 :SDI-rx: 9 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEtx old_st:CU_Down new_st:TCU_EOFile0:04:32: BSC: Serial2 :SDI-rx: 5 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEnq old_st:CU_Down new_st:TCU_EOFileBSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Down new_st:TCU_InFileBSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Idle new_st:TCU_InFile%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2, changed state to up%LINK-3-UPDOWN: Interface Serial2, changed state to upBSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Idle new_st:TCU_InFile0:04:35: BSC: Serial2 :SDI-rx: 9 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEtx old_st:CU_Idle new_st:TCU_InFile0:04:35: BSC: Serial2 :SDI-rx: 5 bytesBSC: Serial2 POLLEE-FSM inp:E_RxEnq old_st:CU_Idle new_st:TCU_InFile0:04:35: BSC: Serial2 :NDI-rx: 3 bytesRelated Commands
debug bsc packet
Displays all frames traveling through the Bisync feature.
debug bstun events
Displays BSTUN connection events and status.
debug bsc packet
To display all frames traveling through the Binary Synchronous Communications (Bisync) feature, use the debug bsc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bsc packet [group number] [buffer-size bytes]
no debug bsc packet [group number] [buffer-size bytes]
Syntax Description
group number
(Optional) Group number.
buffer-size bytes
(Optional) Number of bytes displayed per packet (defaults to 20).
Defaults
The default number of bytes displayed is 20.
Command Modes
Privileged EXEC
Usage Guidelines
This command traces all interfaces configured with a bsc protocol-group number command.
Examples
The following is sample output from the debug bsc packet command:
Router# debug bsc packet0:23:33: BSC: Serial2 :NDI-rx : 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D40130:23:33: BSC: Serial2 :SDI-tx : 12 bytes 00323237FF3232606040402D0:23:33: BSC: Serial2 :SDI-rx : 2 bytes 10700:23:33: BSC: Serial2 :SDI-tx : 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D40130:23:33: BSC: Serial2 :SDI-rx : 2 bytes 10610:23:33: BSC: Serial2 :SDI-tx : 5 bytes 00323237FFRelated Commands
debug bsc event
Displays all events occurring in the Bisync feature.
debug bstun events
Displays BSTUN connection events and status.
debug bstun events
To display BSTUN connection events and status, use the debug bstun events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bstun events [number]
no debug bstun events [number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
When you enable the debug bstun events command, messages showing connection establishment and other overall status messages are displayed.
You can use the debug bstun events command to assist you in determining whether the BSTUN peers are configured correctly and are communicating. For example, if you enable the debug bstun packet command and you do not see any packets, you may want to enable event debugging.
Note
Examples
The following is sample output from the debug bstun events command of keepalive messages working correctly. If the routers are configured correctly, at least one router will show reply messages.
Router# debug bstun eventsBSTUN: Received Version Reply opcode from (all[2])_172.16.12.2/1976 at 1360BSTUN: Received Version Request opcode from (all[2])_172.16.12.2/1976 at 1379BSTUN: Received Version Reply opcode from (all[2])_172.16.12.2/1976 at 1390
Note
The following is sample output from the debug bstun events output of an event trace in which the wrong TCP address has been specified for the remote peer. These are non-keepalive related messages.
Router# debug bstun eventsBSTUN: Change state for peer (C1[1])172.16.12.22/1976 (closed->opening)BSTUN: Change state for peer (C1[1])172.16.12.22/1976 (opening->open wait)%BSTUN-6-OPENING: CONN: opening peer (C1[1])172.16.12.22/1976, 3BSTUN: tcpd sender in wrong state, dropping packetBSTUN: tcpd sender in wrong state, dropping packetBSTUN: tcpd sender in wrong state, dropping packetRelated Commands
debug bstun packet
To display packet information on packets traveling through the BSTUN links, use the debug bstun packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bstun packet [group number] [buffer-size bytes]
no debug bstun packet [group number] [buffer-size bytes]
Syntax Description
group number
(Optional) BSTUN group number.
buffer-size bytes
(Optional) Number of bytes displayed per packet (defaults to 20).
Defaults
The default number of bytes displayed is 20.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug bstun packet command:
Router# debug bstun packetBSTUN bsc-local-ack: 0:00:00 Serial2 SDI: Addr: 40 Data: 02C1C1C1C1C1C1C1C1C1BSTUN bsc-local-ack: 0:00:00 Serial2 SDI: Addr: 40 Data: 02C1C1C1C1C1C1C1C1C1BSTUN bsc-local-ack: 0:00:06 Serial2 NDI: Addr: 40 Data: 0227F5C31140C11D60C8Related Commands
debug bundle errors
To enable the display of information on bundle errors, use the debug bundle errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug bundle errors
no debug bundle errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to enable the display of error information for a bundle, such as reports of inconsistent mapping in the bundle.
Related Commands
debug bundle events
To enable display of bundle events when use occurs, use the debug bundle events command in privileged EXEC mode. To disable the display, use the no form of this command.
debug bundle events
no debug bundle events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to enable the display of bundle events, such as occurrences of VC bumping, when bundles were brought up, when they were taken down, and so forth.
Related Commands
Posted: Wed Jul 25 06:38:38 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
