-
Cisco IOS Debug Command Reference
-
Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug auto-config
-
debug backhaul-session-manager session through debug channel packets
-
debug clns esis events through debug dbconn tcp
-
debug decnet adj through debug events
-
debug fax dmsp through debug gvrp
-
debug h225 asn1 through debug ip ftp
-
debug ip http all through debug ip rsvp
-
debug ip rtp header-compression through debug ipv6 icmp
-
debug ipv6 inspect through debug local-ack state
-
debug management event through debug mpls ldp bindings
-
debug mpls ldp checkpoint through debug mwi relay events
-
debug ncia circuit through debug pxf tbridge
-
debug qllc error through debug snmp sync
-
debug sntp adjust through debug tag-switching xtagatm vc
-
debug tag-template event through debug voip application vxml
-
debug voip avlist through debug vpm signaling
-
debug vpm spi through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug aaa dead-criteria transactions
debug archive config timestamp
debug archive log config persistent
Debug Commands
This chapter contains an alphabetical listing of the debug commands and their descriptions. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, sample output, and a description of that output.
debug aaa accounting
To display information on accountable events as they occur, use the debug aaa accounting command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa accounting
no debug aaa accounting
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Usage Guidelines
The information displayed by the debug aaa accounting command is independent of the accounting protocol used to transfer the accounting information to a server. Use the debug tacacs and debug radius protocol-specific commands to get more detailed information about protocol-level issues.
You can also use the show accounting command to step through all active sessions and to print all the accounting records for actively accounted functions. The show accounting command allows you to display the active "accountable events" on the system. It provides systems administrators a quick look at what is happening, and may also be useful for collecting information in the event of a data loss of some kind on the accounting server. The show accounting command displays additional data on the internal state of the authentication, authorization, and accounting (AAA) security system if debug aaa accounting is turned on as well.
Examples
The following is sample output from the debug aaa accounting command:
Router# debug aaa accounting16:49:21: AAA/ACCT: EXEC acct start, line 1016:49:32: AAA/ACCT: Connect start, line 10, glare16:49:47: AAA/ACCT: Connection acct stop:task_id=70 service=exec port=10 protocol=telnet address=172.31.3.78 cmd=glare bytes_in=308 bytes_out=76 paks_in=45 paks_out=54 elapsed_time=14Related Commands
debug aaa authentication
To display information on authentication, authorization, and accounting (AAA) TACACS+ authentication, use the debug aaa authentication command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa authentication
no debug aaa authentication
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug aaa authentication command to learn the methods of authentication being used.
Examples
The following is sample output from the debug aaa authentication command. A single EXEC login that uses the "default" method list and the first method, TACACS+, is displayed.
Router# debug aaa authenticationNov 17 03:06:40.805 PST: AAA/BIND(0000000F): Bind i/fNov 17 03:06:40.805 PST: AAA/AUTHEN/LOGIN (0000000F): Pick method list 'default'debug aaa authorization
To display information on authentication, authorization, and accounting (AAA) TACACS+ authorization, use the debug aaa authorization command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa authorization
no debug aaa authorization
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Usage Guidelines
Use this command to learn the methods of authorization being used and the results of these methods.
Examples
The following is sample output from the debug aaa authorization command. In this display, an EXEC authorization for user "carrel" is performed. On the first line, the username is authorized. On the second and third lines, the attribute value (AV) pairs are authorized. The debug output displays a line for each AV pair that is authenticated. Next, the display indicates the authorization method used. The final line in the display indicates the status of the authorization process, which, in this case, has failed.
Router# debug aaa authorization2:23:21: AAA/AUTHOR (0): user='carrel'2:23:21: AAA/AUTHOR (0): send AV service=shell2:23:21: AAA/AUTHOR (0): send AV cmd*2:23:21: AAA/AUTHOR (342885561): Method=TACACS+2:23:21: AAA/AUTHOR/TAC+ (342885561): user=carrel2:23:21: AAA/AUTHOR/TAC+ (342885561): send AV service=shell2:23:21: AAA/AUTHOR/TAC+ (342885561): send AV cmd*2:23:21: AAA/AUTHOR (342885561): Post authorization status = FAILThe aaa authorization command causes a request packet containing a series of AV pairs to be sent to the TACACS+ daemon as part of the authorization process. The daemon responds in one of the following three ways:
•
Accepts the request as is
•
•
Table 2 describes AV pairs associated with the debug aaa authorization command that may appear in the debug output.
debug aaa cache filterserver
To help troubleshoot your filter cache configurations, use the debug aaa cache filterserver command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa cache filterserver
no debug aaa cache filterserver
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug aaa cache filterserver command:
Router# debug aaa cache filterserverAAA/FLTSV: need "myfilter" (fetch), call 0x612DAC64AAA/FLTSV: send req, call 0x612DAC50AAA/FLTSV: method SERVER_GROUP myradiusAAA/FLTSV: recv reply, call 0x612DAC50 (PASS)AAA/FLTSV: create cacheAAA/FLTSV: add attr "call-inacl"AAA/FLTSV: add attr "call-inacl"AAA/FLTSV: add attr "call-inacl"AAA/FLTSV: skip attr "filter-cache-refresh"AAA/FLTSV: skip attr "filter-cache-time"AAA/CACHE: set "AAA filtserv cache" entry "myfilter" refresh? noAAA/CACHE: set "AAA filtserv cache" entry "myfilter" cachetime 15AAA/FLTSV: add attr to list "call-inacl" call 0x612DAC64AAA/FLTSV: add attr to list "call-inacl" call 0x612DAC64AAA/FLTSV: add attr to list "call-inacl" call 0x612DAC64AAA/FLTSV: PASS call 0x612DAC64AAA/CACHE: timer "AAA filtserv cache", next in 10 secs (0 entries)AAA/CACHE: timer "AAA filtserv cache", next in 10 secs (1 entry)AAA/CACHE: destroy "AAA filtserv cache" entry "myfilter"AAA/CACHE: timer "AAA filtserv cache", next in 10 secs (0 entries)Related Commands
aaa authorization cache filterserver
Enables AAA authorization caches and the downloading of ACL configurations from a RADIUS filter server.
debug aaa cache group
To debug the caching mechanism and ensure that entries are cached from authentication, authorization, and accounting (AAA) server responses and found when queried, use the debug aaa cache group command in privileged EXEC mode.
debug aaa cache group
Syntax Description
This command has no arguments or keywords.
Command Default
Debug information for all cached entries is displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display debug information about cached entries.
Examples
The following example displays the debug information about all cached entries:
Router# debug aaa cache groupRelated Commands
clear aaa cache group
Clears an individual entry or all entries in the cache.
show aaa cache group
Displays cache entries stored by the AAA cache.
debug aaa dead-criteria transactions
To display authentication, authorization, and accounting (AAA) dead-criteria transaction values, use the debug aaa dead-criteria transactions command in privileged EXEC mode. To disable dead-criteria debugging, use the no form of this command.
debug aaa dead-criteria transactions
no debug aaa dead-criteria transactions
Syntax Description
This command has no arguments or keywords.
Defaults
If the command is not configured, debugging is not turned on.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Dead-criteria transaction values may change with every AAA transaction. Some of the values that can be displayed are estimated outstanding transactions, retransmit tries, and dead-detect intervals. These values are explained in Table 3.
Examples
The following example shows dead-criteria transaction information for a particular server group:
Router# debug aaa dead-criteria transactionsAAA Transaction debugs debugging is on*Nov 14 23:44:17.403: AAA/SG/TRANSAC: Computed Retransmit Tries: 10, Current Tries: 3, Current Max Tries: 10*Nov 14 23:44:17.403: AAA/SG/TRANSAC: Computed Dead Detect Interval: 10s, Elapsed Time: 317s, Current Max Interval: 10s*Nov 14 23:44:17.403: AAA/SG/TRANSAC: Estimated Outstanding Transactions: 6, Current Max Transactions: 6Table 3 describes the significant fields shown in the display.
Related Commands
debug aaa per-user
To display debugging information about PPP session per-user activities, use the debug aaa per-user command in privileged EXEC mode. To turn off debugging, use the no form of this command.
debug aaa per-user
no debug aaa per-user
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The per-user module is responsible for installing per-user attributes for PPP sessions.
Examples
The following example displays the configuration commands that were generated by the per-user process:
Router# debug aaa per-userAAA/PER-USER: line=[ip access-list standard Virtual-Access2#31]AAA/PER-USER: line=[deny 10.0.0.2 0.0.0.0]AAA/PER-USER: line=[permit any]The fields in the display are self-explanatory.
Related Commands
debug aaa pod
To display debug messages related to packet of disconnect (POD) packets, use the debug aaa pod command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa pod
no debug aaa pod
Syntax Description
This command has no keywords or arguments.
Defaults
Debugging for POD packets is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows output from a successful POD request when using the show debug command:
Router# debug aaa podAAA POD packet processing debugging is onRouter# show debugGeneral OS:AAA POD packet processing debugging is onRouter#Apr 25 17:15:59.318:POD:172.19.139.206 request queuedApr 25 17:15:59.318:voice_pod_request:Apr 25 17:15:59.318:voip_populate_pod_attr_list:Apr 25 17:15:59.318:voip_pod_get_guid:Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=50Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr=h323-conf-idApr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=50 value_len=35Apr 25 17:15:59.318:voip_pod_get_guid:conf-id=FFA7785F F7F607BB00000000 993FB1F4 n_bytes=35Apr 25 17:15:59.318:voip_pod_get_guid:GUID = FFA7785F F7F607BB 00000000993FB1F4Apr 25 17:15:59.318:voip_populate_pod_attr_list:Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=23Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr=h323-originateApr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=23 value_len=6Apr 25 17:15:59.318:voip_get_call_direction:Apr 25 17:15:59.318:voip_get_call_direction:returning answerApr 25 17:15:59.318:voip_eval_pod_attr:Apr 25 17:15:59.318:cc_api_trigger_disconnect:Apr 25 17:15:59.322:POD:Sending ACK to 172.19.139.206/1700Apr 25 17:15:59.322:voip_pod_clean:Related Commands
debug aaa redundancy
To display debug output that displays authentication, authorization, and accounting (AAA) redundancy events during session activation, session synchronization to the standby device, and dynamic session updates to the standby device, use the debug aaa redundancy command in privileged EXEC mode. To disable debugging for AAA redundancy, use the no form of this command.
debug aaa redundancy
no debug aaa redundancy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command displays the AAA synchronization data for the session synchronization to the standby device. This information might be useful for diagnosing any AAA problems related to the session synchronization.
Examples
The following example shows sample output from the debug aaa redundancy command collected while a session is activated and synchronized to the standby device:
Router# debug aaa redundancyLogs on Active==============01:31:55: CCM: New State[Not Ready]01:31:55: CCM: PPPoE Required01:31:55: CCM: PPP Required01:31:55: CCM: LTERM Required01:31:55: CCM: PPPoE is Initiator01:31:55: AAA/BIND(0000000B): Bind i/f Virtual-Template101:31:55: CCM: AAA Ready01:31:55: AAA/CCM/(0000000B): AAA sso init completed successfully01:31:55: SSS INFO: Element type is Access-Type = 3 (PPPoE)01:31:55: SSS INFO: Element type is Protocol-Type = 0 (PPP)01:31:55: SSS INFO: Element type is Media-Type = 1 (Ethernet)01:31:55: SSS INFO: Element type is Switch-Id = 4105 (00001009)01:31:55: SSS INFO: Element type is Segment-Hdl = 4114 (00001012)01:31:55: SSS INFO: Element type is AAA-Id = 11 (0000000B)01:31:55: SSS INFO: Element type is AccIe-Hdl = 33554441 (02000009)01:31:55: SSS INFO: Element type is SHDB-Handle = 1476395017 (58000009)01:31:55: SSS INFO: Element type is Input Interface = "GigabitEthernet6/0/0"01:31:55: SSS MGR [uid:10]: Sending a Session Assert ID Mgr event01:31:55: SSS MGR [uid:10]: Updating ID Mgr with the following keys:aaa-unique-id 11 (0xB)01:31:55: SSS MGR [uid:10]: Handling Policy Service Authorize action (1 pending sessions)01:31:55: SSS PM [uid:10][63D5D594]: RM/VPDN disabled: RM/VPDN author not needed01:31:55: SSS PM [uid:10][63D5D594]: AAA author needed for registered user01:31:55: SSS MGR [uid:10]: Got reply Need More Keys from PM01:31:55: SSS MGR [uid:10]: Handling Need More Keys action01:31:57: SSS INFO: Element type is Unauth-User = "user1"01:31:57: SSS INFO: Element type is AccIe-Hdl = 33554441 (02000009)01:31:57: SSS INFO: Element type is AAA-Id = 11 (0000000B)01:31:57: SSS INFO: Element type is Access-Type = 0 (PPP)01:31:57: SSS INFO: Element type is Protocol-Type = 0 (PPP)01:31:57: SSS MGR [uid:10]: Sending a Session Update ID Mgr event01:31:57: SSS MGR [uid:10]: Updating ID Mgr with the following keys:username "user1"aaa-unique-id 11 (0xB)01:31:57: SSS MGR [uid:10]: Handling Policy Send More Keys action01:31:57: SSS PM [uid:10][63D5D594]: AAA author needed for registered user01:31:57: SSS PM [uid:10][63D5D594]: SGBP disabled: SGF author not needed01:31:57: SSS MGR [uid:10]: Got reply Local Terminate from PM01:31:57: SSS MGR [uid:10]: Handling Connect Local Service action01:31:57: SSS MGR [uid:10]: Need the resource type determined key01:31:57: SSS MGR [uid:10]: Handling Need More Keys action01:31:57: SSS MGR [uid:10]: Not yet ready to start the Local service01:31:57: AAA/AUTHEN/PPP (0000000B): Pick method list 'default'01:31:57: RADIUS/ENCODE(0000000B):Orig. component type = PPoE01:31:57: RADIUS: AAA Unsupported Attr: client-mac-address[42] 1401:31:57: RADIUS: 30 30 30 61 2E 34 32 37 64 2E 65 63 [ 000a.427d.ec]01:31:57: RADIUS: AAA Unsupported Attr: interface [171] 701:31:57: RADIUS: 36 2F 30 2F 30 [ 6/0/0]01:31:57: RADIUS(0000000B): Config NAS IP: 0.0.0.001:31:57: RADIUS/ENCODE(0000000B): acct_session_id: 1101:31:57: RADIUS(0000000B): sending01:31:57: RADIUS/ENCODE: Best Local IP-Address 9.2.76.2 for Radius-Server 9.2.36.25301:31:57: RADIUS(0000000B): Send Access-Request to 9.2.36.253:1645 id 1645/10, len 8601:31:57: RADIUS: authenticator FD E8 32 9A 71 15 50 44 - BE FF 19 D0 09 D4 8D 1501:31:57: RADIUS: Framed-Protocol [7] 6 PPP [1]01:31:57: RADIUS: User-Name [1] 9 "user1"01:31:57: RADIUS: User-Password [2] 18 *01:31:57: RADIUS: NAS-Port-Type [61] 6 Virtual [5]01:31:57: RADIUS: NAS-Port [5] 6 001:31:57: RADIUS: NAS-Port-Id [87] 9 "6/0/0/0"01:31:57: RADIUS: Service-Type [6] 6 Framed [2]01:31:57: RADIUS: NAS-IP-Address [4] 6 9.2.76.201:31:57: RADIUS: Received from id 1645/10 9.2.36.253:1645, Access-Accept, len 3201:31:57: RADIUS: authenticator E4 68 43 2C 2F E7 B4 57 - 05 70 FF B1 22 13 E8 0F01:31:57: RADIUS: Idle-Timeout [28] 6 20001:31:57: RADIUS: Service-Type [6] 6 Framed [2]01:31:57: RADIUS(0000000B): Received from id 1645/1001:31:57: SSS INFO: Element type is Auth-User = "user1"01:31:57: SSS INFO: Element type is AAA-Attr-List = C500010001:31:57: SSS INFO: Element type is idletime 200 (0xC8)01:31:57: SSS INFO: Element type is service-type 2 [Framed]01:31:57: SSS INFO: Element type is Resource-Determined = 1 (YES)01:31:57: SSS INFO: Element type is Access-Type = 0 (PPP)01:31:57: SSS INFO: Element type is Protocol-Type = 0 (PPP)01:31:57: SSS INFO: Element type is Final = 1 (YES)01:31:57: SSS MGR [uid:10]: Handling Connect Local Service action01:31:57: SSS MGR [uid:10]: Rcvd an AAA attr list from SIP, pushing it to the PM01:31:57: SSS MGR [uid:10]: Handling Send Policy Push Cng action01:31:57: SSS AAA AUTHOR [uid:10]: Root SIP PPPoE01:31:57: SSS AAA AUTHOR [uid:10]: Enable PPPoE parsing01:31:57: SSS AAA AUTHOR [uid:10]: Enable PPP parsing01:31:57: SSS AAA AUTHOR [uid:10]: Active key set to Unauth-User01:31:57: SSS AAA AUTHOR [uid:10]: Authorizing key user101:31:57: SSS AAA AUTHOR [uid:10]: Spoofed AAA reply sent for key user101:31:57: SSS MGR [uid:10]: Not yet ready to start the Local service01:31:57: SSS AAA AUTHOR [uid:10]: Received an AAA pass01:31:57: SSS AAA AUTHOR [uid:10]: SIP PPP[60A0504C] parsed as Success01:31:57: SSS AAA AUTHOR [uid:10]: SIP PPP[61571560] parsed as Ignore01:31:57: SSS AAA AUTHOR [uid:10]: SIP PPPoE[61599FB0] parsed as Success01:31:57: SSS AAA AUTHOR [uid:10]: SIP Root parser not installed01:31:57: SSS AAA AUTHOR [uid:10]: No service authorization info found01:31:57: SSS AAA AUTHOR [uid:10]: Active Handle present01:31:57: SSS AAA AUTHOR [uid:10]: Freeing Active Handle; SSS Policy Context Handle = 63D5D59401:31:57: SSS AAA AUTHOR [uid:10]: Free request01:31:57: SSS MGR [uid:10]: Got reply Apply Config from PM01:31:57: SSS MGR [uid:10]: Successfully applied policy config01:31:57: SSS MGR [uid:10]: Handling Connect Local Service action01:31:57: CCM: LTERM Required01:31:57: SSS LTERM [uid:10]: Processing Local termination request01:31:57: SSS LTERM [uid:10]: Sent create-clone request to vtemplate manager01:31:57: SSS LTERM [uid:10]: Created vaccess interface Vi301:31:57: CCM: LTERM Ready01:31:57: SSS LTERM [uid:10]: Segment provision successful01:31:57: SSS MGR [uid:10]: Handling Local Service Connected action01:31:57: SSS MGR [uid:10]: Apply for Vi3: segment 4114, owner 382520527701:31:57: SSS MGR [uid:10]: Interface config 212C27B801:31:57: SSS MGR [uid:10]: Per-user config 2146BD4801:31:57: SSS LTERM [uid:10]: Switching session provisioned01:31:57: SSS MGR [uid:10]: Handling Local Service Connected, Features Applied action01:31:57: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up01:31:57: SSS LTERM [uid:10]: Installed Vi3 process path switching vector01:31:57: SSS LTERM [uid:10]: Installed Vi3 fastsend path switching vector01:31:57: AAA/BIND(0000000B): Bind i/f Virtual-Access301:31:57: CCM: PPPoE Ready01:31:57: CCM: PPP Ready01:31:57: CCM: PPP Old State[Not Ready] Event[All Ready]01:31:57: CCM: New State[Ready]01:31:57: AAA/CCM/(0000000B): No of sync avps = 4 Total sync data len = 9401:31:57: CCM: PPP Adding Data Type[6] Subtype[0] Length[14]01:31:57: CCM: PPP Adding Data Type[5] Subtype[0] Length[10]01:31:57: CCM: PPP Adding Data Type[8] Subtype[0] Length[6]01:31:57: CCM: PPP Adding Data Type[7] Subtype[0] Length[0]01:31:57: CCM: PPP Adding Data Type[1] Subtype[0] Length[8]01:31:57: CCM: PPP Adding Data Type[41] Subtype[0] Length[4]01:31:57: CCM: PPPoE Adding Data Type[1] Subtype[0] Length[54]01:31:57: CCM: PPPoE Adding Data Type[2] Subtype[0] Length[2]01:31:57: CCM: PPPoE Adding Data Type[5] Subtype[0] Length[4]01:31:57: CCM: PPPoE Adding Data Type[6] Subtype[0] Length[4]01:31:57: CCM: PPPoE Adding Data Type[7] Subtype[0] Length[20]01:31:57: CCM: PPPoE Adding Data Type[8] Subtype[0] Length[16]01:31:57: CCM: AAA Adding Data Type[1] Subtype[0] Length[4]01:31:57: AAA/CCM/(0000000B): Adding sync avp [AAA Unique Id] Length = 401:31:57: CCM: AAA Adding Data Type[2] Subtype[0] Length[2]01:31:57: AAA/CCM/(0000000B): Adding sync avp [AAA Authen Method Index] Length = 201:31:57: CCM: AAA Adding Data Type[3] Subtype[0] Length[4]01:31:57: AAA/CCM/(0000000B): Adding sync avp [AAA Acct Sess id] Length = 401:31:57: CCM: AAA Adding Data Type[4] Subtype[0] Length[84]01:31:57: AAA/CCM/(0000000B): Adding sync avp [AAA Author Data] Length = 8401:31:57: AAA/CCM: Adding author data entry 3201:31:57: CCM: LTERM Adding Data Type[1] Subtype[0] Length[4]01:31:57: SSS LTERM [uid:10]: LTERM segment handle synced01:31:57: CCM: Send[Sync Session] Length[240] NumItems[17] Event[0x0]01:31:57: Client[PPP] Type[6] Subtype[0] Length[14]01:31:57: 01 04 05 D4 03 04 C0 23 05 06 03 F4 37 7901:31:57: Client[PPP] Type[5] Subtype[0] Length[10]01:31:57: 01 04 05 D4 05 06 9A 6B 68 FE01:31:57: Client[PPP] Type[8] Subtype[0] Length[6]01:31:57: 03 06 07 01 01 0101:31:57: Client[PPP] Type[7] Subtype[0] Length[0]01:31:57:01:31:57: Client[PPP] Type[1] Subtype[0] Length[8]01:31:57: 73 75 6D 61 6E 74 68 0001:31:57: Client[PPP] Type[41] Subtype[0] Length[4]01:31:57: 00 00 00 0201:31:57: Client[PPPoE] Type[1] Subtype[0] Length[54]01:31:57: 00 03 A0 10 22 90 00 0A 42 7D EC 38 88 63 11 1901:31:57: 00 00 00 22 01 02 00 06 61 61 61 5F 68 61 01 0401:31:57: 00 10 98 99 BB 6D 59 B8 35 33 0B FB 14 B9 07 EB01:31:57: 83 B4 01 01 00 0001:31:57: Client[PPPoE] Type[2] Subtype[0] Length[2]01:31:57: 00 0A01:31:57: Client[PPPoE] Type[5] Subtype[0] Length[4]01:31:57: 00 00 10 0901:31:57: Client[PPPoE] Type[6] Subtype[0] Length[4]01:31:57: 00 00 10 1201:31:57: Client[PPPoE] Type[7] Subtype[0] Length[20]01:31:57: 00 02 06 00 00 00 A6 B8 00 00 00 00 00 00 00 2A01:31:57: 00 00 FF FF01:31:57: Client[PPPoE] Type[8] Subtype[0] Length[16]01:31:57: 00 00 00 03 00 00 00 00 00 00 00 19 00 00 00 1D01:31:57:01:31:57: Client[AAA] Type[1] Subtype[0] Length[4]01:31:57: 00 00 00 0B01:31:57: Client[AAA] Type[2] Subtype[0] Length[2]01:31:57: 00 0001:31:57: Client[AAA] Type[3] Subtype[0] Length[4]01:31:57: 00 00 00 0B01:31:57: Client[AAA] Type[4] Subtype[0] Length[84]01:31:57: 00 00 00 00 00 00 00 00 63 E8 73 D0 00 00 00 0B01:31:57: 64 02 FE 71 00 00 00 00 00 00 00 00 00 00 00 0001:31:57: 00 00 00 04 00 00 00 01 00 00 00 20 00 00 00 0001:31:57: 58 00 00 09 02 0A 00 20 E4 68 43 2C 2F E7 B4 5701:31:57: 05 70 FF B1 22 13 E8 0F 1C 06 00 00 00 C8 06 0601:31:57: 00 00 00 0201:31:57: Client[LTERM] Type[1] Subtype[0] Length[4]01:31:57: 00 00 20 1301:31:57: CCM: New State[Dyn Sync]01:31:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to upLogs on Standby================01:21:16: CCM ISSU: Received negotiation message type [ISSU_RC_USER_MESSAGE_COMP]01:21:16: CCM: Receive[Sync Session] Length[240] NumItems[17] Flags[0x0]01:21:16: CCM: New State[Not Ready]01:21:16: Client[PPP] Type[6] Subtype[0] Length[14]01:21:16: 01 04 05 D4 03 04 C0 23 05 06 03 F4 37 7901:21:16: Client[PPP] Type[5] Subtype[0] Length[10]01:21:16: 01 04 05 D4 05 06 9A 6B 68 FE01:21:16: Client[PPP] Type[8] Subtype[0] Length[6]01:21:16: 03 06 07 01 01 0101:21:16: Client[PPP] Type[7] Subtype[0] Length[0]01:21:16:01:21:16: Client[PPP] Type[1] Subtype[0] Length[8]01:21:16: 73 75 6D 61 6E 74 68 0001:21:16: Client[PPP] Type[41] Subtype[0] Length[4]01:21:16: 00 00 00 0201:21:16: Client[PPPoE] Type[1] Subtype[0] Length[54]01:21:16: 00 03 A0 10 22 90 00 0A 42 7D EC 38 88 63 11 1901:21:16: 00 00 00 22 01 02 00 06 61 61 61 5F 68 61 01 0401:21:16: 00 10 98 99 BB 6D 59 B8 35 33 0B FB 14 B9 07 EB01:21:16: 83 B4 01 01 00 0001:21:16: Client[PPPoE] Type[2] Subtype[0] Length[2]01:21:16: 00 0A01:21:16: Client[PPPoE] Type[5] Subtype[0] Length[4]01:21:16: 00 00 10 0901:21:16: Client[PPPoE] Type[6] Subtype[0] Length[4]01:21:16: 00 00 10 1201:21:16: Client[PPPoE] Type[7] Subtype[0] Length[20]01:21:16: 00 02 06 00 00 00 A6 B8 00 00 00 00 00 00 00 2A01:21:16: 00 00 FF FF01:21:16: Client[PPPoE] Type[8] Subtype[0] Length[16]01:21:16: 00 00 00 03 00 00 00 00 00 00 00 19 00 00 00 1D01:21:16:01:21:16: Client[AAA] Type[1] Subtype[0] Length[4]01:21:16: 00 00 00 0B01:21:16: Client[AAA] Type[2] Subtype[0] Length[2]01:21:16: 00 0001:21:16: Client[AAA] Type[3] Subtype[0] Length[4]01:21:16: 00 00 00 0B01:21:16: Client[AAA] Type[4] Subtype[0] Length[84]01:21:16: 00 00 00 00 00 00 00 00 63 E8 73 D0 00 00 00 0B01:21:16: 64 02 FE 71 00 00 00 00 00 00 00 00 00 00 00 0001:21:16: 00 00 00 04 00 00 00 01 00 00 00 20 00 00 00 0001:21:16: 58 00 00 09 02 0A 00 20 E4 68 43 2C 2F E7 B4 5701:21:16: 05 70 FF B1 22 13 E8 0F 1C 06 00 00 00 C8 06 0601:21:16: 00 00 00 0201:21:16: Client[LTERM] Type[1] Subtype[0] Length[4]01:21:16: 00 00 20 1301:21:16: CCM:PPPoE Recreate Session Active[0x58000009] Standby[0x98000009]01:21:16: CCM: PPPoE Required01:21:16: CCM: PPP Required01:21:16: CCM: LTERM Required01:21:16: CCM: PPPoE is Initiator01:21:16: AAA/CCM/: return checkpointed aaa id = 0000000B01:21:16: Adding cache entry for id B01:21:16: Author cache len 84 84 8401:21:16: AAA/CCM/(0000000B):return acct_sess_id = 1101:21:16: CCM: AAA Ready01:21:16: AAA/CCM/(0000000B): AAA sso init completed successfully01:21:16: SSS INFO: Element type is Access-Type = 3 (PPPoE)01:21:16: SSS INFO: Element type is Protocol-Type = 0 (PPP)01:21:16: SSS INFO: Element type is Media-Type = 1 (Ethernet)01:21:16: SSS INFO: Element type is Switch-Id = 4105 (00001009)01:21:16: SSS INFO: Element type is Segment-Hdl = 4114 (00001012)01:21:16: SSS INFO: Element type is AAA-Id = 11 (0000000B)01:21:16: SSS INFO: Element type is AccIe-Hdl = 4127195145 (F6000009)01:21:16: SSS INFO: Element type is SHDB-Handle = 2550136841 (98000009)01:21:16: SSS INFO: Element type is Input Interface = "GigabitEthernet6/0/0"01:21:16: SSS MGR [uid:10]: Sending a Session Assert ID Mgr event01:21:16: SSS MGR [uid:10]: Updating ID Mgr with the following keys:aaa-unique-id 11 (0xB)01:21:16: SSS MGR [uid:10]: Handling Policy Service Authorize action (1 pending sessions)01:21:16: SSS PM [uid:10][63D6963C]: RM/VPDN disabled: RM/VPDN author not needed01:21:16: SSS MGR [uid:10]: Got reply Need More Keys from PM01:21:16: SSS MGR [uid:10]: Handling Need More Keys action01:21:16: SSS INFO: Element type is Unauth-User = "user1"01:21:16: SSS INFO: Element type is AccIe-Hdl = 4127195145 (F6000009)01:21:16: SSS INFO: Element type is AAA-Id = 11 (0000000B)01:21:16: SSS INFO: Element type is Access-Type = 0 (PPP)01:21:16: SSS INFO: Element type is Protocol-Type = 0 (PPP)01:21:16: SSS MGR [uid:10]: Sending a Session Update ID Mgr event01:21:16: SSS MGR [uid:10]: Updating ID Mgr with the following keys:username "user1"aaa-unique-id 11 (0xB)01:21:16: SSS MGR [uid:10]: Handling Policy Send More Keys action01:21:16: SSS PM [uid:10][63D6963C]: SGBP disabled: SGF author not needed01:21:16: SSS MGR [uid:10]: Got reply Local Terminate from PM01:21:16: SSS MGR [uid:10]: Handling Connect Local Service action01:21:16: SSS MGR [uid:10]: Need the resource type determined key01:21:16: SSS MGR [uid:10]: Handling Need More Keys action01:21:16: SSS MGR [uid:10]: Not yet ready to start the Local service01:21:16: AAA/CCM/(0000000B):return authen_method_index = 001:21:16: RADIUS/ENCODE(0000000B):Orig. component type = PPoE01:21:16: RADIUS: AAA Unsupported Attr: client-mac-address[42] 1401:21:16: RADIUS: 30 30 30 61 2E 34 32 37 64 2E 65 63 [ 000a.427d.ec]01:21:16: RADIUS: AAA Unsupported Attr: interface [171] 701:21:16: RADIUS: 36 2F 30 2F 30 [ 6/0/0]01:21:16: RADIUS(0000000B): Config NAS IP: 0.0.0.001:21:16: RADIUS/ENCODE(0000000B): acct_session_id: 1101:21:16: RADIUS(0000000B): sending01:21:16: RADIUS/ENCODE: Best Local IP-Address 2.1.1.1 for Radius-Server 9.2.36.25301:21:16: RADIUS(0000000B): Send Access-Request to 9.2.36.253:1645 id 1645/10, len 8601:21:16: RADIUS: authenticator 14 48 25 90 A5 7B 53 02 - 11 05 01 13 6D 34 E2 0401:21:16: RADIUS: Framed-Protocol [7] 6 PPP [1]01:21:16: RADIUS: User-Name [1] 9 "user1"01:21:16: RADIUS: User-Password [2] 18 *01:21:16: RADIUS: NAS-Port-Type [61] 6 Virtual [5]01:21:16: RADIUS: NAS-Port [5] 6 001:21:16: RADIUS: NAS-Port-Id [87] 9 "6/0/0/0"01:21:16: RADIUS: Service-Type [6] 6 Framed [2]01:21:16: RADIUS: NAS-IP-Address [4] 6 2.1.1.101:21:16: RADIUS: Cached response01:21:16: RADIUS: authenticator E4 68 43 2C 2F E7 B4 57 - 05 70 FF B1 22 13 E8 0F01:21:16: RADIUS: Idle-Timeout [28] 6 20001:21:16: RADIUS: Service-Type [6] 6 Framed [2]01:21:16: RADIUS(0000000B): Received from id 1645/1001:21:16: SSS INFO: Element type is Auth-User = "user1"01:21:16: SSS INFO: Element type is AAA-Attr-List = 2000010001:21:16: SSS INFO: Element type is idletime 200 (0xC8)01:21:16: SSS INFO: Element type is service-type 2 [Framed]01:21:16: SSS INFO: Element type is Resource-Determined = 1 (YES)01:21:16: SSS INFO: Element type is Access-Type = 0 (PPP)01:21:16: SSS INFO: Element type is Protocol-Type = 0 (PPP)01:21:16: SSS INFO: Element type is Final = 1 (YES)01:21:16: SSS MGR [uid:10]: Handling Connect Local Service action01:21:16: SSS MGR [uid:10]: Rcvd an AAA attr list from SIP, pushing it to the PM01:21:16: SSS MGR [uid:10]: Handling Send Policy Push Cng action01:21:16: SSS MGR [uid:10]: Not yet ready to start the Local service01:21:16: SSS MGR [uid:10]: Got reply Apply Config from PM01:21:16: SSS MGR [uid:10]: Successfully applied policy config01:21:16: SSS MGR [uid:10]: Handling Connect Local Service action01:21:16: CCM: LTERM Required01:21:16: SSS LTERM [uid:10]: Processing Local termination request01:21:16: SSS LTERM [uid:10]: Sent create-clone request to vtemplate manager01:21:16: SSS LTERM [uid:10]: Created vaccess interface Vi301:21:16: CCM: LTERM Ready01:21:16: SSS LTERM [uid:10]: Segment provision successful01:21:16: SSS MGR [uid:10]: Handling Local Service Connected action01:21:16: SSS MGR [uid:10]: Apply for Vi3: segment 4114, owner 256691407701:21:16: SSS MGR [uid:10]: Interface config 218170B801:21:16: SSS MGR [uid:10]: Per-user config 63E0655001:21:16: SSS LTERM [uid:10]: Switching session provisioned01:21:16: SSS MGR [uid:10]: Handling Local Service Connected, Features Applied action01:21:16: SSS LTERM [uid:10]: Installed Vi3 process path switching vector01:21:16: SSS LTERM [uid:10]: Installed Vi3 fastsend path switching vector01:21:16: CCM: PPPoE Ready01:21:16: CCM: PPP Ready01:21:16: CCM: PPP Old State[Not Ready] Event[All Ready]01:21:16: CCM: New State[Ready]Table 4 describes the significant fields shown in the display.
Related Commands
debug aaa sg-server selection
To obtain information about why the RADIUS and TACACS+ server group system in a router is choosing a particular server, use the debug aaa sg-server selection command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa sg-server selection
no debug aaa sg-server selection
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows that debugging has been set to display information about server selection:
Router# debug aaa sg-server selectionThe following two debug outputs display the behavior of RADIUS transactions within a server group with the server-reorder-on-failure feature configured.
Debug 1
In the following sample output, the RADIUS server-reorder-on-failure feature is configured. The server retransmits are set to 0 (so each server is attempted only once before failover to the next configured server), and the transmissions per transaction are set to 4 (the transmissions will stop on the third failover). The third server in the server group (192.0.2.118) has accepted the transaction on the third transmission (second failover).
00:38:35: %SYS-5-CONFIG-I: Configured from console by console00:38:53: RADIUS/ENCODE(OOOOOOOF) : ask "Username: "00:38:53: RADIUS/ENCODE (0000000F) : send packet; GET-USER00:38:58: RADIUS/ENCODE (0000000F) : ask "Password: "00:38:58: RADIUS/ENCODE(0000000F) : send packet; GET-PASSWORD00:38:59: RADIUS: AAA Unsupported [152] 400:38:59: RADIUS: 7474 [tt]00:38:59: RADIUS (0000000F) : Storing nasport 2 in rad-db00:38:59: RADIUS/ENCODE(0000000F) : dropping service type, "radius-serverattribute 6 on-for-login-auth" is off00:38:59: RADIUS (0000000F) : Config NAS IP: 192.0.2.400:38:59: RADIUS/ENCODE (0000000F) : acct-session-id: 1500:38:59: RADIUS (0000000F) : sending00:38:59: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.100:38:59: RAPIUS(0000000F) : Send Access-Request to 192.0.2.1:1645 id 21645/11, len 7800:38:59: RADIUS:: authenticator 4481 E6 65 2D 5F 6F OA -lE F5 81 8F 4E 1478 9C00:38:59: RADIUS: User-Name [1] 7 "username"00:38:59: RADIUS: User-Password [2] 18 *00:38:59: RADIUS: NAS-Port fSl 6 200:~8:59: RADIUS: NAS-Port-Type [61] 6 Virtual [5]00:38:59: RADIUS: Calling-Station-Id [31] 15 "192.0.2.23"00:39:00: RADIUS: NAS-IP-Address [4] 6 192.0.2.13000:39:02: RADIUS: Fail-over to (192.0.2.2:1645,1646) for id 21645/1100:39:02: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.200:39:04: RADIUS: Fail-over to (192.0.2.118:1645,1646) for id 21645/1100:39:04: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server192.0.2.11800:39:05: RADIUS: Received from id 21645/11 192.0.2.118:1645, Access-Accept, len 2600:39:05: RADIUS: authenticator 5609 56 F9 64 4E DF 19- F3 A2 DD 73 EE 3F 982600:39:05: RADIUS: Service-Type [6] 6 Login [1]Debug 2
In the following sample output, the RADIUS server-reorder-on-failure feature is configured. The server retransmits are set to 0, and the transmissions per transaction are set to 8. In this transaction, the transmission to server 192.0.2.1 has failed on the eighth transmission.
00:42:30: RADIUS(00000011): Received from id 21645/1300:43:34: RADIUS/ENCODE(00000012) : ask "Username: "00:43:34: RADIUS/ENCODE(00000012) : send packet; GET-USER00:43:39: RADIUS/ENCODE(00000012) : ask "Password: "00:43:39: RADIUS/ENCODE(00000012) : send packet; GET-PASSWORD00:43:40: RADIUS: AAA Unsupported [152] 400:43:40: RADIUS: 7474 [tt]00:43:40: RADIUS(00000012) : Storing nasport 2 in rad-db00:43:40: RADIUS/ENCODE(00000012): dropping service type, "radius-server attribute 6on-for-login-auth" is off00:43:40: RADIUS(00000012) : Co~fig NAS IP: 192.0.2.400:43:40: RADIUS/ENCODE(00000012) : acct-session-id: 1800:43:40: RADIUS(00000012) : sending00:43:40: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.11800:43:40: RADIUS(00000012) : Send Access-Request to 192.0.2.118:1645 id 21645/14, len 7800:43:40: RADIUS: authenticator B8 OA 51 3A AF A6 0018 -B3 2E 94 5E 07 OB 2A00:43:40: RADIUS: User-Name [1] 7 "username"00:43:40: RADIUS: User-Password [2] 18 *00:43:40: RADIUS: NAS-Port [5] 6 200:43:40: RADIUS: NAS-Port-Type [61] 6 Virtual [5]00:43:40: RADIUS: Calling-Station-]d [31] 15 "192.0.2.23"00:43:40: RADIUS: NAS-IP-Address [4] 6 192.0.2.13000:43:42: RADIUS: Fail-over to (192.0.2,1:1645,1646) for id 21645/1400:43:42: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.100:43:44: RADius: Fail-over to (192.0.2.2:1645,1646) for id 21645/1400:43:44: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.200:43:46: RADIUS: Fail-over to (192.0.2.118:1645,1646) for id 21645/1400:43:46: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.11800:43:48: RADIUS: Fail-over to (192.0.2.1:1645,1646) for id 21645/1400:43:48: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.100:43:50: RADIUS: Fail-over to (192.0.2.2:1645,1646) for id 21645/1400:43:50: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.200:43:52: RADIUS: Fail-over to (192.0.2.118:1645,1646) for id 21645/1400:43:52: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.11800:43:54: RADIUS: Fail-over to (192.0.2.1:1645,1646) for id 21645/1400:43:54: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.100:43:56: RADIUS: No response from (192.0.2.1:1645,1646) for id 21645/1400:43:56:RADIUS/DECODE: parse response no app start; FAIL00:43:56: RADIUS/DECODE: parse response;FAILThe field descriptions are self-explanatory.
Debug 3
In the following sample output, the RADIUS server load balancing feature is enabled with a batch size of 3. The server selection, based on the load balancing algorithm, is shown as five access-requests that are being sent to the server group.
Router# debug aaa sg-server selectionJul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [3] transactions remaining in batch. Reusing server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [2] transactions remaining in batch. Reusing server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [1] transactions remaining in batch. Reusing server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: No more transactions in batch. Obtaining a new server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining a new least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Server[0] load: 3Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Server[1] load: 0Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Server[2] load: 0Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Selected Server[1] with load 0Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [3] transactions remaining in batch.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [2] transactions remaining in batch. Reusing server.
The field descriptions are self-explanatory.
Related Commands
debug aaa test
To show when the idle timer or dead timer has expired, when test packets are being sent, server response status, and the server state for RADIUS server load balancing, use the debug aaa test command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug aaa test
no debug aaa test
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
In the following sample output, the RADIUS server load balancing feature is enabled. The idle timer has expired.
Router# debug aaa testRouter#Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) quarantined.Jul 16 00:07:01: AAA/SG/TEST: Sending test request(s) to server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Sending 1 Access-Requests, 1 Accounting-Requests in current batch.Jul 16 00:07:01: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request.Jul 16 00:07:01: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request.Jul 16 00:07:01: AAA/SG/TEST: Obtained Test response from server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Obtained Test response from server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Necessary responses received from server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) marked ALIVE. Idle timer set for 60 sec(s).Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) removed from quarantine.Related Commands
debug acircuit
To display errors and events that occur on the attachment circuits (the circuits between the provider edge (PE) and customer edge (CE) routers), use the debug acircuit command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug acircuit {error | event}
no debug acircuit {error | event}
Syntax Description
error
Displays errors that occur in attachment circuits.
event
Displays events that occur in attachment circuits.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug acircuit command to identify provisioning events, setup failures, circuit up and down events, and configuration failures on attachment circuits.
An attachment circuit connects a PE router to a CE router. A router can have many attachment circuits. The attachment circuit manager controls all the attachment circuits from one central location. Therefore, when you enable the debug messages for the attachment circuit, you receive information about all the attachment circuits.
Examples
The following is sample output from the debug acircuit event command when you enable an interface:
Router# debug acircuit event*Jan 28 15:19:03.070: ACLIB: ac_cstate() Handling circuit UP for interface Se2/0*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: pthru_intf_handle_circuit_up() callingacmgr_circuit_up*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Connecting*Jan 28 15:19:03.070: ACMGR: Receive <Circuit Up> msg*Jan 28 15:19:03.070: Se2/0 ACMGR: circuit up event, SIP state chg down to connecting,action is service request*Jan 28 15:19:03.070: Se2/0 ACMGR: Sent a sip service request*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: AC updating switch context.*Jan 28 15:19:03.070: Se2/0 ACMGR: Rcv SIP msg: resp connect forwarded, hdl 9500001D,l2ss_hdl 700001E*Jan 28 15:19:03.070: Se2/0 ACMGR: service connected event, SIP state chg connecting toconnected, action is respond forwarded*Jan 28 15:19:03.070: ACLIB: pthru_intf_response hdl is 9500001D, response is 1*Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-ConnectedThe following is sample output from the debug acircuit event command when you disable an interface:
Router# debug acircuit event*Jan 28 15:25:57.014: ACLIB: SW AC interface INTF-DOWN for interface Se2/0*Jan 28 15:25:57.014: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Idle*Jan 28 15:25:57.014: ACLIB: SW AC interface INTF-DOWN for interface Se2/0*Jan 28 15:25:57.014: Se2/0 ACMGR: Receive <Circuit Down> msg*Jan 28 15:25:57.014: Se2/0 ACMGR: circuit down event, SIP state chg connected to end,action is service disconnect*Jan 28 15:25:57.014: Se2/0 ACMGR: Sent a sip service disconnect*Jan 28 15:25:57.014: ACLIB [11.0.1.1, 200]: AC deleting switch context.*Jan 28 15:25:59.014: %LINK-5-CHANGED: Interface Serial2/0, changed state toadministratively down*Jan 28 15:25:59.014: ACLIB: ac_cstate() Handling circuit DOWN for interface Se2/0*Jan 28 15:26:00.014:%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to downThe following example shows output from the debug acircuit command for an xconnect session on an Ethernet interface:
Router# debug acircuit23:28:35: ACLIB [10.0.3.201, 5]: SW AC interface UP for Ethernet interface Et2/123:28:35: ACLIB [10.0.3.201, 5]: pthru_intf_handle_circuit_up() calling acmgr_circuit_up23:28:35: ACLIB [10.0.3.201, 5]: Setting new AC state to Ac-Connecting23:28:35: ACLIB [10.0.3.201, 5]: SW AC interface UP for Ethernet interface Et2/123:28:35: ACLIB [10.0.3.201, 5]: pthru_intf_handle_circuit_up() ignoring up event. Already connected or connecting.23:28:35: ACMGR: Receive <Circuit Up> msg23:28:35: Et2/1 ACMGR: circuit up event, SIP state chg down to connecting, action is service request23:28:35: Et2/1 ACMGR: Sent a sip service request23:28:37: %LINK-3-UPDOWN: Interface Ethernet2/1, changed state to up23:28:38: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet2/1, changed state to up23:28:53: Et2/1 ACMGR: Rcv SIP msg: resp connect forwarded, hdl D6000002, sss_hdl 9E00000F23:28:53: Et2/1 ACMGR: service connected event, SIP state chg connecting to connected, action is respond forwarded23:28:53: ACLIB: pthru_intf_response hdl is D6000002, response is 123:28:53: ACLIB [10.0.3.201, 5]: Setting new AC state to Ac-ConnectedThe command output is self-explanatory.
Related Commands
debug acircuit checkpoint
To enable the display of attachment circuit (AC) events when Any Transport over MPLS (AToM) is configured for nonstop forwarding/stateful switchover (NSF/SSO) and Graceful Restart, use the debug acircuit checkpoint command in privileged EXEC mode. To disable the display of these messages, use the no form of this command.
debug acircuit checkpoint
no debug acircuit checkpoint
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging of the AToM NSF/SSO and Graceful Restart feature is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use debug commands with care. They use a significant amount of CPU time and can affect system performance.
Examples
The debug acircuit checkpoint command is issued on the active RP:
Router# debug mpls l2transport checkpointRouter# debug acircuit checkpointRouter# show debugAToM HA:AToM checkpointing events and errors debugging is onAC HA:Attachment Circuit Checkpoint debugging is onRouter# conf terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Fa5/1/1.2Router(config-subif)# xconnect 10.55.55.2 1002 pw-class mplsAToM HA [10.55.55.2, 1002]: Build provision msg, SSM sw/seg 8192/8194 [0x2000/0x2002] PW i d 9216 [0x2400] local label 21AC HA: Dynamic Sync. Event:4 Sw:8192[2000] Se:16385[4001]AToM HA: CF sync send completeAC HA CF: Sync send complete. Code:0On the standby RP, the following messages indicate that it receives checkpointing data:
AC HA [10.55.55.2, 1002]: Add to WaitQ. Flags:1AToM HA [10.55.55.2, 1002]: Received 32-byte provision version 1 CF messageAC HA CF: ClientId:89, Entity:0 Length:40AToM HA [10.55.55.2, 1002]: Process chkpt msg provision [1], ver 1AToM HA [10.55.55.2, 1002]: Reserved SSM sw/seg 8192/8194 [0x2000/0x2002] PW id 9216 [0x24 00]AC HA: Process Msg:35586. Ptr:44CBFD90. Val:0AC HA: Sync. Event:4 CktType:4 Sw:8192[2000] Se:16385[4001]AC HA [10.55.55.2, 1002]: Remove from WaitQ. Flags:1[OK][OK]During a switchover from the active to the backupRoute Processor, the debug messages look similar to the following:
%HA-5-MODE: Operating mode is hsa, configured mode is sso.AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Opr:5, St:STANDBY HO T, PSt:ACTIVEAToM HA: CID 84, Seq 715, Status RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Op 5, State STANDB Y HOT, Peer ACTIVEAC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:STANDBY HOT, PSt:ACTIVEAToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_PRESENCE, Op 0, State STANDBY HOT, Peer AC TIVEAC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_COMM, Opr:0, St:STANDBY HOT, PSt:DISABLEDAToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_COMM, Op 0, State STANDBY HOT, Peer DISABL ED%HA-2-CUTOVER_NOTICE: Cutover initiated. Cease all console activity until system restarts.%HA-2-CUTOVER_NOTICE: Do not add/remove RSPs or line cards until switchover completes.%HA-2-CUTOVER_NOTICE: Deinitializing subsystems...%OIR-6-REMCARD: Card removed from slot 4, interfaces disabled%OIR-6-REMCARD: Card removed from slot 5, interfaces disabled%OIR-6-REMCARD: Card removed from slot 9, interfaces disabled%HA-2-CUTOVER_NOTICE: Reinitializing subsystems...%HA-2-CUTOVER_NOTICE: System preparing to restart...%HA-5-NOTICE: Resuming initialization...AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_REDUNDANCY_MODE_CHANGE, Opr:7, St:STANDBY HOT, PS t:DISABLED...%LDP-5-GR: LDP restarting gracefully. Preserving forwarding state for 250 seconds.AC HA RF: CId:83, Seq:710, Sta:RF_PROG_ACTIVE, Opr:0, St:ACTIVE, PSt:DISABLEDAToM HA: CID 84, Seq 715, Event RF_PROG_ACTIVE, Op 0, State ACTIVE, Peer DISABLEDAC HA: Process Msg:35588. Ptr:0. Val:0AC HA: Switchover: Standby->ActiveAC HA RF: ReconcilingRelated Commands
debug mpls l2transport checkpoint
Enables the display of AToM events when AToM is configured for NSF/SSO and Graceful Restart.
debug adjacency
To enable the display of information about the adjacency database, use the debug adjacency command in privileged EXEC mode. To disable the display of these events, use the no form of this command.
debug adjacency [epoch | ipc | state | table] [prefix] [interface] [connectionid id] [link {ipv4 | ipv6 | mpls}]
no debug adjacency [epoch | ipc | state | table] [prefix] [interface] [connectionid id] [link {ipv4 | ipv6 | mpls}]
Syntax Description
Command Default
Debugging events are not displayed.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Also, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.
You can use any combination of the prefix, interface, connectionid id, and link {ipv4 | ipv6 | mpls} keywords and arguments (in any order) as a filter to enable debugging for a specified subset of adjacencies.
Note
Examples
The following example shows how to display information on the adjacency database:
Router# debug adjacency*Jan 27 06:22:50.543: ADJ-ios_mgr: repopulate adjs on up event for Ethernet3/0*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: init/update from interface*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: set bundle to IPv6 adjacency oce*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: allocated, setup and inserted OK*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) src IPv6 ND: source IPv6 ND added OK*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) src IPv6 ND: computed macstring (len 14): OK*Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 src IPv6 ND: made complete (macstring len 0 to 14/0 octets)00:04:40: %LINK-3-UPDOWN: Interface Ethernet3/0, changed state to up00:04:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/0, changedRelated Commands
debug adjacency (vasi)
To display debugging information for the VRF-Aware Service Infrastructure (VASI) adjacency, use the debug adjacency command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug adjacency{vasileft | vasiright} number
no debug interface {vasileft | vasiright} number
Syntax Description
vasileft
Displays information about the vasileft interface.
vasiright
Displays information about the vasiright interface.
number
Identifier of the VASI interface. The range is from 1 to 256.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following is sample output from the debug adjacency command:
Router# debug adjacency veasileft 1Condition 1 setRelated Commands
debug alarm-interface
To show real-time activities in the data channel or the management channel of the Alarm Interface Controller (AIC), use the debug alarm-interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug alarm-interface slot-number {data | management}
no debug alarm-interface slot-number {data | management}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command allows you to observe the management channel activity from the AIC in the specified slot. Such activity shows that the software running on the AIC CPU has reached a minimum level of working order.
Examples
The following is sample output from the debug alarm-interface command:
Router# debug alarm-interfaceAIC Slot 1:STATUS receivedThe following is sample output from the debug alarm-interface 1 data command:
Router# debug alarm-interface 1 dataAIC Slot 1:STATUS receivedaic_fastsend:particle count=1, len=1504aic_pak_to_txring:scattered particle count=1, tx bytes=1504, leftover=0aic_interrupt:# 30419 gstar=0x1000000aic_safe_start:particle count=1, len=524aic_pak_to_txring:scattered particle count=1, tx bytes=524, leftover=0aic_process_TXivq:ivq - 0x42040000 at 15, slice 1aic_interrupt:# 30420 gstar=0x1000000aic_process_TXivq:ivq - 0x42040000 at 16, slice 1aic_interrupt:# 30421 gstar=0x10000000aic_scc_rx_intr:sts_dlen=0xC5E10000, len=1504, RSTA=0xA0aic_serial_RX_interrupt:rxtype=1, len=1504, aic_scc_rx_intr:last_rxbd has aged, 2aic_process_RXivq:ivq - 0x60000 at 13, slice 1aic_interrupt:# 30422 gstar=0x10000000aic_scc_rx_intr:sts_dlen=0xC20D0000, len=524, RSTA=0xA0aic_serial_RX_interrupt:rxtype=1, len=524, aic_process_RXivq:ivq - 0x60000 at 14,slice 1aic_interrupt:# 30423 gstar=0x20000000aic_scc_rx_intr:sts_dlen=0xC00D0000, len=12, RSTA=0xA0aic_mgmt_RX_interrupt:len=12aic_mgmt_fastsend:particle count=1, len=20 / 20aic_pak_to_txring:scattered particle count=1, tx bytes=20, leftover=0aic_scc_rx_intr:last_rxbd has aged, 2aic_process_RXivq:ivq - 0x10060000 at 37, slice 1aic_interrupt:# 30424 gstar=0x2000000aic_process_TXivq:ivq - 0x52040000 at 24, slice 1Related Commands
alarm-interface
Enters the alarm interface mode and configures the AIC.
reset
Resets the AIC CPU.
debug alps ascu
To enable debugging for airline product set (ALPS) agent set control units (ASCUs) use the debug alps ascu command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug alps ascu {event | packet | detail | all | format {ipars | router | both}} [interface [ascu id]]
no debug alps ascu {event | packet | detail | all | format {ipars | router | both}} [interface [ascu id]]
Syntax Description
Defaults
Debugging is off.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To enable debugging for a group of ASCUs, enter a separate command for each ASCU interface and IA combination.
The interface option applies only to the event, packet, detail, and all keywords.
Note
Examples
The following output is from the debug alps ascu event command, showing events or protocol errors in router format for ASCU 42 on interface Serial7:
Router# debug alps ascu format routerRouter# debug alps ascu event Serial7 42ALPS ASCU: T1 expired for ascu 42 on i/f Serial7ALPS ASCU: DOWN event while UP for ascu 42 on i/f Serial7 : C1 count = 1
Note
The following output is from the debug alps ascu event command, showing events or protocol errors in ipars format for ASCU 42 on interface Serial7:
Router# debug alps ascu format iparsRouter# debug alps ascu event Serial7 42ALPS ASCU: T1 expired for ascu 42/2F on i/f Serial7ALPS ASCU: DOWN event while UP for ascu 42/2F on i/f Serial7 : C1 count = 1The following output is from the debug alps ascu detail command, showing all protocol events in router format for ASCU 42 on interface Serial6:
Router# debug alps ascu format routerRouter# debug alps ascu detail Serial6 42ALPS ASCU: Tx ALC POLL MSG (+ 0 pad bytes) to ascu 42 on i/f Serial6ALPS ASCU: ALC GO AHD MSG rcvd from ascu 42 on i/f Serial6ALPS ASCU: Tx ALC POLL MSG (+ 0 pad bytes) to ascu 42 on i/f Serial6ALPS ASCU: ALC GO AHD MSG rcvd from ascu 42 on i/f Serial6ALPS ASCU: Tx ALC POLL MSG (+ 0 pad bytes) to ascu 42 on i/f Serial6ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42 on i/f Serial6, fwd to cktRTP_MATIPALPS ASCU: ALC GO AHD MSG rcvd from ascu 42 on i/f Serial6ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6ALPS ASCU: Tx ALC POLL MSG (3 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6
Note
The following output is from the debug alps ascu detail command, showing all protocol events in both format for ASCU 42 on interface Serial6:
Router# debug alps ascu format bothRouter# debug alps ascu detail Serial6 42ALPS ASCU: Tx ALC POLL MSG (+ 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS ASCU: ALC GO AHD MSG rcvd from ascu 42/2F on i/f Serial6ALPS ASCU: Tx ALC POLL MSG (+ 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS ASCU: ALC GO AHD MSG rcvd from ascu 42/2F on i/f Serial6ALPS ASCU: Tx ALC POLL MSG (+ 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42/2F on i/f Serial6, fwd to cktRTP_MATIPALPS ASCU: ALC GO AHD MSG rcvd from ascu 42/2F on i/f Serial6ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS ASCU: Tx ALC POLL MSG (3 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6The following output is from the debug alps ascu packet command, showing all packets sent or received in router format for ASCU 42 on interface Serial6:
Router# debug alps ascu packet format router Serial6 42ALPS ASCU: Tx ALC SERVICE MSG (18 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial602321D26 0C261616140C0D18 26163135 0611C6ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42 on i/f Serial6, fwd cktRTP_MATIP42607866 6571786665717966 755124ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6022038 2625313826253139 263511E4The following output is from the debug alps ascu packet command, showing all packets sent or received in ipars format for ASCU 42 on interface Serial6:
Router# debug alps ascu packet format ipars Serial6 42ALPS ASCU: Tx ALC SERVICE MSG (18 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS IPARS Format:2F2C1126 3326252535331339 26251C14 271DC6ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42/2F on i/f Serial6, fwd cktRTP_MATIPALPS IPARS Format:2F3E3826 161C3826161C1826 141D24ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS IPARS Format:2F3E38 26161C3826161C18 26141DE4The following output is from the debug alps ascu packet command, showing all packets sent or received in both formats for ASCU 42 on interface Serial6:
Router# debug alps ascu packet format both Serial6 42ALPS ASCU: Tx ALC SERVICE MSG (18 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS Router Format:02321D26 0C261616140C0D18 26163135 0611C6ALPS IPARS Format:2F2C1126 3326252535331339 26251C14 271DC6ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42/2F on i/f Serial6, fwd cktRTP_MATIPALPS Router Format:42607866 6571786665717966 755124ALPS IPARS Format:2F3E3826 161C3826161C1826 141D24ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6ALPS Router Format:022038 2625313826253139 263511E4ALPS IPARS Format:2F3E38 26161C3826161C18 26141DE4debug alps circuit event
To enable event debugging for airline product set (ALPS) circuits, use the debug alps circuit event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug alps circuit event [name]
no debug alps circuit event [name]
Syntax Description
name
(Optional) Name given to identify an ALPS circuit on the remote customer premises equipment (CPE).
Defaults
If no circuit name is specified, then debugging is enabled for every ALPS circuit.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To enable debugging for a single ALPS circuit, specify the name of the circuit.
To enable debugging for a group of circuits, enter a separate command for each circuit name.
Examples
The following is sample output from the debug alps circuit event command for circuit RTP_AX25:
alps-rcpe# debug alps circuit event RTP_AX25ALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= OPEN, Event= DISABLE:(CloseAndDisable)->DISCALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= DISC, Event= ENABLE:(TmrStartNullRetry)->INOPALPS P1024 CKT: Ckt= RTP_AX25, Open - peer set to 200.100.40.2ALPS P1024 CKT: Ckt= RTP_AX25, Open - peer open.ALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= INOP, Event= RETRY_TIMEOUT:(Open)->OPNGALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= OPNG, Event= CKT_OPEN_CFM:(CacheAndFwdAscuData)->OPENalps-ccpe# debug alps circuit event RTP_AX25ALPS AX.25 FSM: Ckt= RTP_AX25, State= OPEN, Event= CktClose, Rsn= 12:(PvcKill,CktRemove,TmrStartClose)->INOPALPS AX.25 FSM: Ckt= RTP_AX25, State= INOP, Event= X25PvcInact, Rsn= 0:(-,-,-)->INOPALPS AX.25 FSM: Ckt= RTP_AX25, State= INOP, Event= X25VcDeleted, Rsn= 0:(-,CktDestroy,TmrStop)->INOPALPS AX.25 FSM: Ckt= RTP_AX25, State= INOP, Event= CktOpReq, Rsn= 4:(PvcMake,CktAdd,TmrStartOpen)->OPNGALPS AX.25 FSM: Ckt= RTP_AX25, State= OPNG, Event= X25ResetTx, Rsn= 0:(-,-,-)->OPNGALPS AX.25 FSM: Ckt= RTP_AX25, State= OPNG, Event= X25VcUp, Rsn= 0:(-,OpnCfm,TmrStop)->OPENdebug alps peer
To enable event or packet debugging for airline product set (ALPS) peers, use the debug alps peer command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug alps peer {event | packet} [ip-address]
no debug alps peer {event | packet} [ip-address]
Syntax Description
event
Specifies debugging for an event.
packet
Specifies debugging for a packet.
ip-address
(Optional) Remote peer IP address.
Defaults
If no IP address is specified, then debugging is enabled for every peer connection.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To enable debugging for a single remote ALPS peer, specify the peer IP address.
To enable debugging for a set of remote peers, enter the command for each peer IP address.
Examples
The following is sample output from the debug alps peer packet command:
Router# debug alps peer packetALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - TX Peer Data Msg (18 bytes)040A5320: 01 00001241040A5330:45546B5F 6F4F7757 67477B5B 51ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - RX Peer Data Msg (18 bytes)04000550: 01000012 4145546B 5F6F4F7704000560:5767477B 5B51ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - TX Peer Data Msg (18 bytes)0409F6E0: 01 00001241 45546B5F0409F6F0:6F4F7757 67477B5B 51ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - RX Peer Data Msg (18 bytes)04000680: 01000012 4145546B04000690:5F6F4F77 5767477B 5B51debug alps peer event
To enable event debugging for airline product set (ALPS) peers, use the debug alps peer event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug alps peer event ipaddr
no debug alps peer event ipaddr
Syntax Description
Defaults
If no IP address is specified, debugging is enabled for every peer connection.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To enable debugging for a single remote ALPS peer, specify the peer IP address.
To enable debugging for a set of remote peers, enter the command for each peer IP address.
Examples
The following is sample output from the debug alps peer event command:
Router# debug alps peer eventALPS PEER: FSM - Peer 200.100.25.2, Event ALPS_CLOSED_IND, State OPENEDALPS PEER: peer 200.100.25.2 closed - closing peer circuits.ALPS PEER: Promiscuous peer created for 200.100.25.2ALPS PEER: TCP Listen - passive open 200.100.25.2(11003) -> 10000ALPS PEER: FSM - Peer 200.100.25.2, Event ALPS_OPEN_IND, State DISCONNALPS PEER: peer 200.100.25.2 opened OK.debug alps snmp
To enable debugging for airline product set (ALPS) Simple Network Management Protocol (SNMP) agents, use the debug alps snmp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug alps snmp
no debug alps snmp
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging for SNMP agents is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following output is from the debug alps snmp command. The first line shows a circuit event status change. The second line shows an ASCU status change. The third line shows a peer connection status change.
Router# debug alps snmpALPS CktStatusChange Notification for circuit CKT-1ALPS AscuStatusChange Notification for ascu (Serial3, 41)PeerConnStatusChange Notification for peer (10.227.50.106, MATIP_A_CKT-1)The following output shows that an open failure has occurred on circuit 1:
ALPS CktOpenFailure Notification for circuit CKT1The following output shows that a partial rejection to an ALPS circuit peer open request has occurred on circuit 1:
ALPS CktPartialReject Notification for ascu (Serial2, 41) on circuit CKT1debug ancp
To enable the display of debugging information related to the Access Node Control Protocol (ANCP), use the debug ancp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ancp {adjacency | details | errors | events | neighbor | packets [brief] | port-event {details | events} | port-management {details | events}}
no debug ancp {adjacency | details | errors | events | neighbor | packets [brief] | port-event {details | events} | port-management {details | events}}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
You can use the debug condition interface command to conditionalize all the debug commands where the ANCP TCP connections are terminated.
Examples
The following is sample output from the debug ancp adjacency command. The output fields are self-explanatory.
Router# debug ancp adjacency*Sep 20 08:23:53.833: Sending adj (SYN) msg nbr_info 0 nbr 10.1.1.1/46459 tcb 50C2050*Sep 20 08:23:53.834: ANCP: Using Mac address aabb.cc00.7a00*Sep 20 08:23:53.834: ANCP : Sending adj (SYN) msg to writeQ, msg len 48 interface Ethernet0/0.1 TCB 50C2050*Sep 20 08:23:53.836: ANCP: Received adjacency (SYN) message, from 10.1.1.1 port 46459 tcb 50C2050*Sep 20 08:23:53.836: ANCP: 2 capability tlv(s) received*Sep 20 08:23:53.837: Capability received (mask) : 9*Sep 20 08:23:53.837: Sending adj (SYNACK) msg nbr_info 6368300 nbr 10.1.1.1/46459 tcb 50C2050*Sep 20 08:23:53.837: ANCP: Using Mac address aabb.cc00.7a00*Sep 20 08:23:53.837: ANCP : Sending adj (SYNACK) msg to writeQ, msg len 48 interface Ethernet0/0.1 TCB 50C2050*Sep 20 08:23:53.837: ANCP ADJ: received SYN from nbr, state SYNSENT Sending SYNACK to nbr. State transitons to SYNRCVD*Sep 20 08:23:53.841: ANCP: Received adjacency (SYNACK) message, from 10.1.1.1 port 46459 tcb 50C2050*Sep 20 08:23:53.842: ANCP: 2 capability tlv(s) received*Sep 20 08:23:53.842: Capability received (mask) : 9*Sep 20 08:23:53.842: Sending adj (ACK) msg nbr_info 6368300 nbr 10.1.1.1/46459 tcb 50C2050*Sep 20 08:23:53.842: ANCP: Using Mac address aabb.cc00.7a00The following is sample output from the debug ancp events command:
Router# debug ancp eventsANCP protocol events debugging is onANCP: TCP accepted on address 10.1.1.2 for remote peer 10.1.1.1Sending adj msg, code 1 nbr_info 0 nbr 10.1.1.1/40224 tcb 549D930TCP read_notify called, calling ancp_io_read_request. ANCP IO should service the read requestANCP: Received adjacency message, code 1 Src 10.1.1.1 Src port 40224 tcb 549D930ANCP: 2 capability tlv(s) receivedSending adj msg, code 2 nbr_info 5FA92F0 nbr 10.1.1.1/40224 tcb 549D930ANCP ADJ: received SYN from nbr, state SYNSENT Sending SYNACK to nbr. State transitons to SYNRCVDTCP read_notify called, calling ancp_io_read_request. ANCP IO should service the read requestANCP: Received adjacency message, code 2 Src 10.1.1.1 Src port 40224 tcb 549D930ANCP: 2 capability tlv(s) receivedSending adj msg, code 3 nbr_info 5FA92F0 nbr 10.1.1.1/40224 tcb 549D930ANCP ADJ: received SYNACK from nbr, state SYNRCVD Sending ACK to nbr. State transtions to ESTABTCP read_notify called, calling ancp_io_read_request. ANCP IO should service the read requestANCP: Received adjacency message, code 3 Src 10.1.1.1 Src port 40224 tcb 549D930ANCP: 2 capability tlv(s) receivedANCP ADJ: received ACK from nbr, state ESTAB Sending ACK to nbr thou timer. State stays ESTABTCP read_notify called, calling ancp_io_read_request. ANCP IO should service the read requestSending adj msg, code 3 nbr_info 5FA92F0 nbr 10.1.1.1/40224 tcb 549D930ANCP: Received adjacency message, code 3 Src 10.1.1.1 Src port 40224 tcb 549D930ANCP: 2 capability tlv(s) receivedANCP ADJ: received ACK from nbr, state ESTAB Sending ACK to nbr thou timer. State stays ESTABSending adj msg, code 3 nbr_info 5FA92F0 nbr 10.1.1.1/40224 tcb 549D930TCP read_notify called, calling ancp_io_read_request. ANCP IO should service the read requestANCP: Received adjacency message, code 3 Src 10.1.1.1 Src port 40224 tcb 549D930ANCP: 2 capability tlv(s) receivedANCP ADJ: received ACK from nbr, state ESTAB Sending ACK to nbr thou timer. State stays ESTABTable 5 describes the significant fields shown in the display.
The following is sample output from the debug ancp port-event details command. The output fields are self-explanatory.
Router# debug ancp port-event details*Sep 20 08:24:55.608: ANCP: Found db entry based on access-loop-circuit-id alcid1, received in Port UP message*Sep 20 08:24:55.608: Advance 12 bytes (aligned) to next TLV.*Sep 20 08:24:55.609: ANCP: Processing DSL_LINE_ATTRIBUTES sub-TLVs: PORT UP*Sep 20 08:24:55.609: ANCP: Port UP: received DSL Line Attrs, tlv length in msg 32 aligned len 32*Sep 20 08:24:55.609: DSL_TYPE received. 4*Sep 20 08:24:55.609: Advance 8 bytes (aligned) to next sub-TLV.*Sep 20 08:24:55.609: ACTUAL_DATA_RATE_UP received. 7878*Sep 20 08:24:55.609: Advance 8 bytes (aligned) to next sub-TLV.*Sep 20 08:24:55.609: ACTUAL_DATA_RATE_DN received. 9090*Sep 20 08:24:55.610: Advance 8 bytes (aligned) to next sub-TLV.*Sep 20 08:24:55.610: DSL_LINE_STATE received. 1*Sep 20 08:24:55.610: Advance 8 bytes (aligned) to next sub-TLV.*Sep 20 08:24:55.610: Advance 36 bytes (aligned) to next TLV.The following is sample output from the debug ancp port-management details command. The output fields are self-explanatory.
Router# debug ancp port-management details*Sep 20 08:29:22.263:3120 35000000 00008001 00340000 00000000 00000000 00000000 09000000 00000020 05000001 00100001 0006616C 63696431 0000*Sep 20 08:29:22.266: ANCP_PORT_MGMT: Ethernet0/0.1 Port Mgmt message, Total TLVs : 1*Sep 20 08:29:22.266: ANCP_PORT_MGMT: Received Access-Loop-Cir-ID alcid1*Sep 20 08:29:22.266: ANCP_PORT_MGMT: Received Result: success(0x3) Code: Specified access line does not exist(0x500).*Sep 20 08:29:22.266: Advance 12 bytes (aligned) to next TLV.
Related Commands
debug appfw
To display debug messages about Cisco IOS Firewall events, use the debug appfw command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appfw {application protocol | function-trace | object-creation | object-deletion | events | timers | detailed}
no debug appfw {application protocol | function-trace | object-creation | object-deletion | events | timers | detailed}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following sample configuration shows how to configure an HTTP policy with application firewall debugging enabled:
Router(config)# appfw policy-name myPolicyAPPFW FUNC:appfw_policy_findAPPFW FUNC:appfw_policy_find -- Policy myPolicy is not foundAPPFW FUNC:appfw_policy_allocAPPFW FUNC:appfw_policy_alloc -- policy_alloc 0x65727278APPFW FUNC:appfw_policy_alloc -- Policy 0x65727278 is set to validAPPFW FUNC:appfw_policy_alloc -- Policy myPolicy has been createdAPPFW FUNC:appfw_policy_command -- memlock policy 0x65727278! Debugging sample for application (HTTP) creationRouter(cfg-appfw-policy)# application httpAPPFW FUNC:appfw_http_commandAPPFW FUNC:appfw_http_appl_findAPPFW FUNC:appfw_http_appl_find -- Application not foundAPPFW FUNC:appfw_http_appl_allocAPPFW FUNC:appfw_http_appl_alloc -- appl_http 0x64D7A25CAPPFW FUNC:appfw_http_appl_alloc -- Application HTTP parser structure 64D7A25C created! Debugging sample for HTTP-specific application inspectionRouter(cfg-appfw-policy-http)#Router(cfg-appfw-policy-http)# strict-http action reset alarmAPPFW FUNC:appfw_http_subcommandAPPFW FUNC:appfw_http_subcommand -- strict-http cmd turned onRouter# debug appfw detailedAPPFW Detailed Debug debugging is onfw7-7206a#debug appfw object-creationAPPFW Object Creations debugging is onfw7-7206a#debug appfw object-deletionAPPFW Object Deletions debugging is ondebug apple arp
To enable debugging of the AppleTalk Address Resolution Protocol (AARP), use the debug apple arp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple arp [type number]
no debug apple arp [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command is helpful when you experience problems communicating with a node on the network you control (a neighbor). If the debug apple arp display indicates that the router is receiving AARP probes, you can assume that the problem does not reside at the physical layer.
Examples
The following is sample output from the debug apple arp command:
Router# debug apple arpEther0: AARP: Sent resolve for 4160.26Ether0: AARP: Reply from 4160.26(0000.0c00.0453) for 4160.154(0000.0c00.8ea9)Ether0: AARP: Resolved waiting request for 4160.26(0000.0c00.0453)Ether0: AARP: Reply from 4160.19(0000.0c00.0082) for 4160.154(0000.0c00.8ea9)Ether0: AARP: Resolved waiting request for 4160.19(0000.0c00.0082)Ether0: AARP: Reply from 4160.19(0000.0c00.0082) for 4160.154(0000.0c00.8ea9)Explanations for representative lines of output follow.
The following line indicates that the router has requested the hardware MAC address of the host at network address 4160.26:
Ether0: AARP: Sent resolve for 4160.26The following line indicates that the host at network address 4160.26 has replied, giving its MAC address (0000.0c00.0453). For completeness, the message also shows the network address to which the reply was sent and its hardware MAC address (also in parentheses).
Ether0: AARP: Reply from 4160.26(0000.0c00.0453) for 4160.154(0000.0c00.8ea9)The following line indicates that the MAC address request is complete:
Ether0: AARP: Resolved waiting request for 4160.26(0000.0c00.0453)debug apple domain
To enable debugging of the AppleTalk domain activities, use the debug apple domain command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple domain
no debug apple domain
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug apple domain command to observe activity for domains and subdomains. Use this command in conjunction with the debug apple remap command to observe interaction between remapping and domain activity. Messages are displayed when the state of a domain changes, such as creating a new domain, deleting a domain, and updating a domain.
Examples
The following is sample output from the debug apple domain command intermixed with output from the debug apple remap command; the two commands show related events:
Router# debug apple domainRouter# debug apple remapAT-REMAP: RemapProcess for net 30000 domain AURP Domain 1AT-REMAP: ReshuffleRemapList for subdomain 1AT-REMAP: Could not find a remap for cable 3000-3001AT-DOMAIN: atdomain_DisablePort for Tunnel0AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]AT-DOMAIN: Disabling interface Ethernet1AT-DOMAIN: atdomain_DisablePort for Ethernet1AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]AT-DOMAIN: CleanSubDomain for inbound subdomain 1AT-REMAP: Remap for net 70 inbound subdomain 1 has been deletedAT-DOMAIN: DeleteAvRemapList for inbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1AT-DOMAIN: CleanSubDomain for outbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 Remapped Net 10000AT-REMAP: Remap for net 50 outbound subdomain 1 has been deletedAT-DOMAIN: DeleteAvRemapList for outbound subdomain 1AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]AT-DOMAIN: CleanSubDomain for inbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1AT-DOMAIN: CleanSubDomain for outbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1Related Commands
debug apple eigrp-all
To enable debugging output from the Enhanced IGRP routines, use the debug apple eigrp-all privileged EXEC command. The no form of this command disables debugging output.
debug apple eigrp-all
no debug apple eigrp-all
Syntax Description
This command has no arguments or keywords.
Command History
Usage Guidelines
The debug apple eigrp-all command can be used to monitor acquisition of routes, aging route table entries, and advertisement of known routes through Enhanced IGRP.
Caution
Examples
The following is sample output from the debug apple eigrp-all command:
Router# debug apple eigrp-all3:54:34: atigrp2_router: peer is 83.1953:54:37: AT: atigrp2_write: about to send packet3:54:37: Ethernet2: output AT packet: enctype UNKNOWN, size 653:54:37: 07FFFFFF0000FFFFFFFFFFFF00000C1485B00046|0041ACD100000053FF8F585858020591103:54:37: 000000000000000000000000000000010001000C010001000000000F0204000C00530053003:54:37: AT: atigrp2, src=Ethernet2:83.143, dst=83-83, size=52, EIGRP pkt sent3:54:39: atigrp2_router: peer is 83.1953:54:42: AT: atigrp2_write: about to send packet3:54:42: Ethernet2: output AT packet: enctype UNKNOWN, size 653:54:42: 07FFFFFF0000FFFFFFFFFFFF00000C1485B00046|0041ACD100000053FF8F585858020591103:54:42: 000000000000000000000000000000010001000C010001000000000F0204000C00530053003:54:42: AT: atigrp2, src=Ethernet2:83.143, dst=83-83, size=52, EIGRP pkt sentTable 6 describes the significant fields shown in the display.
debug apple errors
To display errors occurring in the AppleTalk network, use the debug apple errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple errors [type number]
no debug apple errors [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
In a stable AppleTalk network, the debug apple errors command produces little output.
To solve encapsulation problems, enable debug apple errors and debug apple packet together.
Examples
The following is sample output from the debug apple errors command when a router is brought up with a zone that does not agree with the zone list of other routers on the network:
Router# debug apple errors%AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19%AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19%AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19As the output suggests, a single error message indicates zone list incompatibility; this message is sent out periodically until the condition is corrected or the debug apple errors command is turned off.
Most of the other messages that the debug apple errors command can generate are obscure or indicate a serious problem with the AppleTalk network. Some of these other messages follow.
In the following message, RTMPRsp, RTMPReq, ATP, AEP, ZIP, ADSP, or SNMP could replace NBP, and "llap dest not for us" could replace "wrong encapsulation":
Packet discarded, src 4160.12-254,dst 4160.19-254,NBP,wrong encapsulationIn the following message, in addition to an invalid echo packet error, other possible errors are unsolicited AEP echo reply, unknown echo function, invalid ping packet, unknown ping function, and bad responder packet type:
Ethernet0: AppleTalk packet error; no source address availableAT: pak_reply: dubious reply creation, dst 4160.19AT: Unable to get a buffer for reply to 4160.19Processing error, src 4160.12-254,dst 4160.19-254,AEP, invalid echo packetThe debug apple errors command can print out additional messages when other debugging commands are also turned on. When you turn on both the debug apple errors and debug apple events commands, the following message can be generated:
Proc err, src 4160.12-254,dst 4160.19-254,ZIP,NetInfo Reply format is invalidIn the preceding message, in addition to the NetInfo Reply format is invalid error, other possible errors are NetInfoReply not for me, NetInfoReply ignored, NetInfoReply for operational net ignored, NetInfoReply from invalid port, unexpected NetInfoReply ignored, cannot establish primary zone, no primary has been set up, primary zone invalid, net information mismatch, multicast mismatch, and zones disagree.
When you turn on both the debug apple errors and debug apple nbp commands, the following message can be generated:
Processing error,...,NBP,NBP name invalidIn the preceding message, in addition to the NBP name invalid error, other possible errors are NBP type invalid, NBP zone invalid, not operational, error handling brrq, error handling proxy, NBP fwdreq unexpected, No route to srcnet, Proxy to "*" zone, Zone "*" from extended net, No zone info for "*", and NBP zone unknown.
When you turn on both the debug apple errors and debug apple routing commands, the following message can be generated:
Processing error,...,RTMPReq, unknown RTMP requestIn the preceding message, in addition to an unknown RTMP request error, other possible errors are RTMP packet header bad, RTMP cable mismatch, routed RTMP data, RTMP bad tuple, and Not Req or Rsp.
debug apple events
To display information about AppleTalk special events, neighbors becoming reachable or unreachable, and interfaces going up or down, use the debug apple events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple events [type number]
no debug apple events [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
Only significant events (for example, neighbor and route changes) are logged.
The debug apple events command is useful for solving AppleTalk network problems because it provides an overall picture of the stability of the network. In a stable network, the debug apple events command does not return any information. If the command generates numerous messages, those messages can indicate possible sources of the problems.
When configuring or making changes to a router or interface for AppleTalk, enable the debug apple events command to alert you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.
The debug apple events command is also useful to determine whether network flapping (nodes toggling online and offline) is occurring. If flapping is excessive, look for routers that only support 254 networks.
When you enable the debug apple events command, you will see any messages that the apple event-logging configuration command normally displays. Turning on the debug apple events command, however, does not cause the apple event-logging command to be maintained in nonvolatile memory. Only turning on the apple event-logging command explicitly stores it in nonvolatile memory. Furthermore, if the apple event-logging command is already enabled, turning on or off the debug apple events command does not affect the apple event-logging command.
Examples
The following is sample output from the debug apple events command that describes a nonseed router coming up in discovery mode:
As the output shows, the debug apple events command is useful in tracking the discovery mode state changes through which an interface progresses. When no problems are encountered, the state changes progress as follows:
1.
2.
3.
4.
5.
6.
7.
8.
Explanations for individual lines of output follow.
The following message indicates that a port is set. In this case, the zone multicast address is being reset.
Ether0: AT: Resetting interface address filtersThe following messages indicate that the router is changing to restarting mode:
%AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restartedEther0: AppleTalk state changed; unknown -> restartingThe following message indicates that the router is probing in the startup range of network numbers (65280 to 65534) to discover its network number:
Ether0: AppleTalk state changed; restarting -> probingThe following message indicates that the router is enabled as a nonrouting node using a provisional network number within its startup range of network numbers. This type of message only appears if the network address the router will use differs from its configured address. This is always the case for a discovery-enabled router; it is rarely the case for a nondiscovery-enabled router.
%AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148The following messages indicate that the router is sending out GetNetInfo requests to discover the default zone name and the actual network number range in which its network number can be chosen:
Ether0: AppleTalk state changed; probing -> acquiring%AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configurationNow that the router has acquired the cable configuration information, the following message indicates that it restarts using that information:
Ether0: AppleTalk state changed; acquiring -> restartingThe following messages indicate that the router is probing for its actual network address:
Ether0: AppleTalk state changed; restarting -> line downEther0: AppleTalk state changed; line down -> restartingEther0: AppleTalk state changed; restarting -> probingThe following message indicates that the router has found an actual network address to use:
%AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 4160.148The following messages indicate that the router is sending out GetNetInfo requests to verify the default zone name and the actual network number range from which its network number can be chosen:
Ether0: AppleTalk state changed; probing -> acquiring%AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configurationThe following message indicates that the router is requesting the list of zones for its cable:
Ether0: AppleTalk state changed; acquiring -> requesting zonesThe following messages indicate that the router is sending out GetNetInfo requests to make sure its understanding of the configuration is correct:
Ether0: AppleTalk state changed; requesting zones -> verifyingAT: Sent GetNetInfo request broadcast on Ethernet0The following message indicates that the router is rechecking its list of zones for its cable:
Ether0: AppleTalk state changed; verifying -> checking zonesThe following message indicates that the router is now fully operational as a routing node and can begin routing:
Ether0: AppleTalk state changed; checking zones -> operationalThe following shows sample debug apple events output that describes a nondiscovery-enabled router coming up when no other router is on the wire.
As the output shows, a nondiscovery-enabled router can come up when no other router is on the wire; however, it must assume that its configuration (if accurate syntactically) is correct, because no other router can verify it. Notice that the last line indicates this situation.
The following is sample output from the debug apple events command that describes a discovery-enabled router coming up when there is no seed router on the wire:
Router# debug apple eventsEther0: AT: Resetting interface address filters%AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restartedEther0: AppleTalk state changed; unknown -> restartingEther0: AppleTalk state changed; restarting -> probing%AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148Ether0: AppleTalk state changed; probing -> acquiringAT: Sent GetNetInfo request broadcast on Ether0AT: Sent GetNetInfo request broadcast on Ether0AT: Sent GetNetInfo request broadcast on Ether0AT: Sent GetNetInfo request broadcast on Ether0AT: Sent GetNetInfo request broadcast on Ether0As the output shows, when you attempt to bring up a nonseed router without a seed router on the wire, it never becomes operational; instead, it hangs in the acquiring mode and continues to send out periodic GetNetInfo requests.
The following is sample output from the debug apple events command when a nondiscovery-enabled router is brought up on an AppleTalk internetwork that is in compatibility mode (set up to accommodate extended as well as nonextended AppleTalk) and the router has violated internetwork compatibility:
The following three configuration command lines indicate the part of the configuration of the router that caused the configuration mismatch:
lestat(config)# interface ethernet 0lestat(config-if)# apple cab 41-41lestat(config-if)# apple zone MarketingThe router shown had been configured with a cable range of 41-41 instead of 40-40, which would have been accurate. Additionally, the zone name was configured incorrectly; it should have been "Marketing," rather than being misspelled as "Markting."
debug apple nbp
To display debugging output from the Name Binding Protocol (NBP) routines, use the debug apple nbp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple nbp [type number]
no debug apple nbp [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
To determine whether the router is receiving NBP lookups from a node on the AppleTalk network, enable debug apple nbp at each node between the router and the node in question to determine where the problem lies.
Caution
Examples
The following is sample output from the debug apple nbp command:
Router# debug apple nbpAT: NBP ctrl = LkUp, ntuples = 1, id = 77AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW LabAT: LkUp =:ciscoRouter@Low End SW LabAT: NBP ctrl = LkUp-Reply, ntuples = 1, id = 77AT: 4160.154, skt 254, enum 1, name: lestat.Ether0:ciscoRouter@Low End SW LabAT: NBP ctrl = LkUp, ntuples = 1, id = 78AT: 4160.19, skt 2, enum 0, name: =:IPADDRESS@Low End SW LabAT: NBP ctrl = LkUp, ntuples = 1, id = 79AT: 4160.19, skt 2, enum 0, name: =:IPGATEWAY@Low End SW LabAT: NBP ctrl = LkUp, ntuples = 1, id = 83AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW LabAT: LkUp =:ciscoRouter@Low End SW LabAT: NBP ctrl = LkUp, ntuples = 1, id = 84AT: 4160.19, skt 2, enum 0, name: =:IPADDRESS@Low End SW LabAT: NBP ctrl = LkUp, ntuples = 1, id = 85AT: 4160.19, skt 2, enum 0, name: =:IPGATEWAY@Low End SW LabAT: NBP ctrl = LkUp, ntuples = 1, id = 85AT: 4160.19, skt 2, enum 0, name: =:IPGATEWAY@Low End SW LabThe first three lines describe an NBP lookup request:
AT: NBP ctrl = LkUp, ntuples = 1, id = 77AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW LabAT: LkUp =:ciscoRouter@Low End SW LabTable 7 describes the fields in the first line of output.
Table 8 describes the fields in the second line of output.
The third line in the output essentially reiterates the information in the two lines above it, indicating that a lookup request has been made regarding name-address pairs for all objects of the ciscoRouter type in the Low End SW Lab zone.
Because the router is defined as an object of type ciscoRouter in zone Low End SW Lab, the router sends an NBP lookup reply in response to this NBP lookup request. The following two lines of output show the response of the router:
AT: NBP ctrl = LkUp-Reply, ntuples = 1, id = 77AT: 4160.154, skt 254, enum 1, name: lestat.Ether0:ciscoRouter@Low End SW LabIn the first line, ctrl = LkUp-Reply identifies this NBP packet as an NBP lookup request. The same value in the id field (id = 77) associates this lookup reply with the previous lookup request. The second line indicates that the network address associated with the entity name of the router (lestat.Ether0:ciscoRouter@Low End SW Lab) is 4160.154. The fact that no other entity name/network address is listed indicates that the responder only knows about itself as an object of type ciscoRouter in zone Low End SW Lab.
debug apple packet
To display per-packet debugging output, use the debug apple packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple packet [type number]
no debug apple packet [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
With this command, you can monitor the types of packets being slow switched. It displays at least one line of debugging output per AppleTalk packet processed.
The output reports information online when a packet is received or a transmission is attempted.
When invoked in conjunction with the debug apple routing, debug apple zip, and debug apple nbp commands, the debug apple packet command adds protocol processing information in addition to generic packet details. It also reports successful completion or failure information.
When invoked in conjunction with the debug apple errors command, the debug apple packet command reports packet-level problems, such as those concerning encapsulation.
Caution
Examples
The following is sample output from the debug apple packet command:
Router# debug apple packetEther0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000AT: src=Ethernet0:4160.47, dst=4160-4160, size=10, 2 rtes, RTMP pkt sentAT: ZIP Extended reply rcvd from 4160.19AT: ZIP Extended reply rcvd from 4160.19AT: src=Ethernet0:4160.47, dst=4160-4160, size=10, 2 rtes, RTMP pkt sentEther0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000Table 9 describes the fields in the first line of output.
Table 10 describes the fields in the second line of output.
The third line indicates the type of packet received and its source AppleTalk address. This message is repeated in the fourth line because AppleTalk hosts can send multiple replies to a given GetNetInfo request.
debug apple remap
To enable debugging of the AppleTalk remap activities, use the debug apple remap command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple remap
no debug apple remap
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug apple remap command with the debug apple domain command to observe activity between domains and subdomains. Messages from the debug apple remap command are displayed when a particular remapping function occurs, such as creating remaps or deleting remaps.
Examples
The following is sample output from the debug apple remap command intermixed with output from the debug apple domain command; the two commands show related events.
Router# debug apple remapRouter# debug apple domainAT-REMAP: RemapProcess for net 30000 domain AURP Domain 1AT-REMAP: ReshuffleRemapList for subdomain 1AT-REMAP: Could not find a remap for cable 3000-3001AT-DOMAIN: atdomain_DisablePort for Tunnel0AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]AT-DOMAIN: Disabling interface Ethernet1AT-DOMAIN: atdomain_DisablePort for Ethernet1AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]AT-DOMAIN: CleanSubDomain for inbound subdomain 1AT-REMAP: Remap for net 70 inbound subdomain 1 has been deletedAT-DOMAIN: DeleteAvRemapList for inbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1AT-DOMAIN: CleanSubDomain for outbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 Remaped Net 10000AT-REMAP: Remap for net 50 outbound subdomain 1 has been deletedAT-DOMAIN: DeleteAvRemapList for outbound subdomain 1AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]AT-DOMAIN: CleanSubDomain for inbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1AT-DOMAIN: CleanSubDomain for outbound subdomain 1AT-DOMAIN: DeleteRemapTable for subdomain 1AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1Related Commands
debug apple routing
To enable debugging output from the Routing Table Maintenance Protocol (RTMP) routines, use the debug apple routing command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple routing [type number]
no debug apple routing [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command can be used to monitor acquisition of routes, aging of routing table entries, and advertisement of known routes. It also reports conflicting network numbers on the same network if the network is misconfigured.
Caution
Examples
The following is sample output from the debug apple routing command:
Router# debug apple routingAT: src=Ethernet0:4160.41, dst=4160-4160, size=19, 2 rtes, RTMP pkt sentAT: src=Ethernet1:41069.25, dst=41069, size=427, 96 rtes, RTMP pkt sentAT: src=Ethernet2:4161.23, dst=4161-4161, size=427, 96 rtes, RTMP pkt sentAT: Route ager starting (97 routes)AT: Route ager finished (97 routes)AT: RTMP from 4160.19 (new 0,old 94,bad 0,ign 0, dwn 0)AT: RTMP from 4160.250 (new 0,old 0,bad 0,ign 2, dwn 0)AT: RTMP from 4161.236 (new 0,old 94,bad 0,ign 1, dwn 0)AT: src=Ethernet0:4160.41, dst=4160-4160, size=19, 2 rtes, RTMP pkt sentTable 11 describes the fields in the first line of sample debug apple routing output.
The following two messages indicate that the ager has started and finished the aging process for the routing table and that this table contains 97 entries:
AT: Route ager starting (97 routes)AT: Route ager finished (97 routes)Table 12 describes the fields in the following line of the debug apple routing command output:
AT: RTMP from 4160.19 (new 0,old 94,bad 0,ign 0, dwn 0)
debug apple zip
To display debugging output from the Zone Information Protocol (ZIP) routines, use the debug apple zip command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug apple zip [type number]
no debug apple zip [type number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command reports significant events such as the discovery of new zones and zone list queries. It generates information similar to that generated by the debug apple routing command, but generates it for ZIP packets instead of Routing Table Maintenance Protocol (RTMP) packets.
You can use the debug apple zip command to determine whether a ZIP storm is taking place in the AppleTalk network. You can detect the existence of a ZIP storm when you see that no router on a cable has the zone name corresponding to a network number that all the routers have in their routing tables.
Examples
The following is sample output from the debug apple zip command:
Router# debug apple zipAT: Sent GetNetInfo request broadcast on Ether0AT: Recvd ZIP cmd 6 from 4160.19-6AT: 3 query packets sent to neighbor 4160.19AT: 1 zones for 31902, ZIP XReply, src 4160.19AT: net 31902, zonelen 10, name US-FloridaThe first line indicates that the router has received an RTMP update that includes a new network number and is now requesting zone information:
AT: Sent GetNetInfo request broadcast on Ether0The second line indicates that the neighbor at address 4160.19 replies to the zone request with a default zone:
AT: Recvd ZIP cmd 6 from 4160.19-6The third line indicates that the router responds with three queries to the neighbor at network address 4160.19 for other zones on the network:
AT: 3 query packets sent to neighbor 4160.19The fourth line indicates that the neighbor at network address 4160.19 responds with a ZIP extended reply, indicating that one zone has been assigned to network 31902:
AT: 1 zones for 31902, ZIP XReply, src 4160.19The fifth line indicates that the router responds that the zone name of network 31902 is US-Florida, and the zone length of that zone name is 10:
AT: net 31902, zonelen 10, name US-Floridadebug appn all
To turn on all possible debugging messages for Advanced Peer-to-Peer Networking (APPN), use the debug appn all command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn all
no debug appn all
Note
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command shows all APPN events. Use other forms of the debug appn command to display specific types of events.
Caution
Caution
Examples
Refer to the documentation for specific debug appn commands for examples and explanations.
Related Commands
debug appn cs
To display Advanced Peer-to-Peer Networking (APPN) Configuration Services (CS) component activity, use the debug appn cs command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn cs
no debug appn cs
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The CS component is responsible for defining link stations, ports, and connection networks. It is responsible for the activation and deactivation of ports and link stations and handles status queries for these resources.
Examples
The following is sample output from the debug appn cs command. In this example a link station is being stopped.
Router# debug appn csTurned on event 008000FFRouter# appn stop link PATTYAPPN: ----- CS ----- Deq STOP_LS messageAPPN: ----- CS ----- FSM LS: 75 17 5 8APPN: ----- CS ----- Sending DEACTIVATE_AS - station PATTYAPPN: ----- CS ----- deactivate_as_p->ips_header.lpid = A80A60APPN: ----- CS ----- deactivate_as_p->ips_header.lpid = A80A60APPN: ----- CS ----- Sending DESTROY_TG to PC - station PATTY - lpid=A80A60APPN: ----- CS ----- Deq DESTROY_TG - station PATTYAPPN: ----- CS ----- FSM LS: 22 27 8 0APPN: ----- CS ----- Sending TG update for LS PATTY to TRSAPPN: ----- CS ----- ENTERING XID_PROCESSING: 4%APPN-6-APPNSENDMSG: Link Station PATTY stoppedTable 13 describes the significant fields and messages shown in the display.
Related Commands
debug appn ds
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Directory Services (DS) component activity, use the debug appn ds command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn ds
no debug appn ds
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The DS component manages searches for resources in the APPN network. DS is also responsible for registration of resources within the network.
Examples
The following is sample output from the debug appn ds command. In this example a search has been received.
Router# debug appn dsTurned on event 080000FFAPPN: NEWDS: LS: search from: NETA.PATTYAPPN: NEWDS: pcid: DD3321E8B5667111APPN: NEWDS: Invoking FSM NNSoluAPPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 0 col: 0 inp: 80200000APPN: NEWDS: LSfsm_parent: 00A89940 row: 0 col: 0 inp: 80000000APPN: NEWDS: Rcvd a LMRQAPPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 12 col: 1 inp: 40000000APPN: NEWDS: LSfsm_parent: 00A89940 row: 8 col: 1 inp: 40000000APPN: NEWDS: LSfsm_child: 00A89BE8 row: 0 col: 0 inp: 80000080APPN: NEWDS: PQenq REQUEST_ROUTE(RQ) to TRSAPPN: NEWDS: LSfsm_child: 00A8A1C0 row: 1 col: 0 inp: 80000008APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 5 col: 1 inp: 80C04000APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 7 col: 1 inp: 80844008APPN: NEWDS: Rcvd a LMRYAPPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 16 col: 6 inp: 40800000APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 14 col: 5 inp: 40800000APPN: NEWDS: LSfsm_parent: 00A89940 row: 3 col: 1 inp: 80840000APPN: NEWDS: send locate to node: NETA.PATTYTable 14 describes the significant fields shown in the display.
Related Commands
debug appn hpr
To display debugging information related to High Performance Routing (HPR) code execution, use the debug appn hpr command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn hpr
no debug appn hpr
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug appn hpr command:
Router# debug appn hprAPPN: -- ncl.ncl_map_dlc_type() -- mapping TOKEN_RING(4) to NCL_TR(3)APPN: -- ncl.ncl_port() -- called with port_type:3, cisco_idb:893A14, hpr_ssap:C8APPN: -- ncl.process_port_change() -- port coming upAPPN: -- ncl.process_port_change() -- PORT_UPAPPN: -- ncl.ncl_port_fsm -- FSM Invoked: Input:0, State:0->1, Action:0APPN: -- ncl.ncl_port_fsm -- FSM Invoked: Input:1, State:1->2, Action:1APPN: -- ncl.ncl_unmap_dlc_type() -- mapping NCL(3) to CLS(3)APPN: ----- ANR ----- Sending ACTIVATE_SAP.reqAPPN: -- cswncsnd.main() -- received LSA_IPS ips.APPN: -- ncl.ncl_port_fsm -- FSM Invoked: Input:3, State:2->3, Action:4APPN: -- ncl.ncl_assign_anr() -- Assigned ANR,anr:8002APPN: -- ncl.ncl_map_dlc_type() -- mapping TOKEN_RING(4) to NCL_TR(3)APPN: -- ncl.ncl_populate_anr() -- anr:8002, dlc_type:3, idb 893A14APPN: -- ncl.ncl_populate_anr() -- send anr_tbl_update to owning cswncsndAPPN: -- ncl.ncl_ls_fsm -- FSM Invoked: Input:0, State:0->1, Action:0APPN: ncl.ncl_send_reqopn_stn_reqAPPN: -- ncl.ncl_unmap_dlc_type() -- mapping NCL(3) to CLS(3)APPN: -- ncl.ncl_ls_fsm() -- send anr_tbl_update to owning cswncsndAPPN: -- cswncsnd.main() -- received ANR_TBL_UPDATE ips.APPN: -- cswncsnd.apply_anr_table_update() -- ANR:8002APPN: -- cswncsnd.main() -- received ANR_TBL_UPDATE ips.APPN: -- cswncsnd.apply_anr_table_update() -- ANR:8002APPN: -- cswncsnd.main() -- received LSA_IPS ips.APPN: -- ncl.ncl_ls_fsm -- FSM Invoked: Input:1, State:1->2, Action:1APPN: -- ncl.ncl_ls_fsm -- P_CEP_ID:AAF638APPN: -- ncl.ncl_ls_fsm() -- send anr_tbl_update to owning cswncsndAPPN: -- cswncsnd.main() -- received ANR_TBL_UPDATE ips.APPN: -- cswncsnd.apply_anr_table_update() -- ANR:8002APPN: rtpm: rtp_send() sent data over connection B9D5E8APPN: hpr timer: rtt start time clocked at 135952 msAPPN: -- cswncsnd.main() -- received NCL_SND_MSG ips.APPN: -- cswncsnd.process_nlp_from_rtp() -- label: 8002, send to p_cep 00AAF638.APPN: hpr timer: rtt end time clocked at 135972 msAPPN: hpr timer: round trip time measured at 20 msTable 15 describes the significant fields shown in the display.
Related Commands
debug appn ms
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Management Services (MS) component activity, use the debug appn ms command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn ms
no debug appn ms
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The MS component is responsible for generating, sending, and forwarding network management information in the form of traps and alerts to a network management focal point, such as Netview, in the APPN network.
Examples
The following is sample output from the debug appn ms command. In this example an error occurred that caused an alert to be generated.
Router# debug appn msAPPN: ----- MSS00 ---- Deq ALERT_MSU msgAPPN: --- MSP70 --- ALERT MV FROM APPN WITH VALID LGTHAPPN: --- MSCPL --- Find Active FPAPPN: --- MSP30 --- Entering Build MS TransportAPPN: --- MSP31 --- Entering Building Routing Info.APPN: --- MSP34 --- Entering Build GDSAPPN: --- MSP32 --- Entering Building UOW correlatorAPPN: --- MSP34 --- Entering Build GDSAPPN: --- MSP30 --- Building GDS 0x1310APPN: --- MSP30 --- Building MS TransportAPPN: --- MSP72 --- ACTIVE FP NOT FOUND, SAVE ONLYAPPN: --- MSUTL --- UOW <= 60, ALL COPIED in extract_uowAPPN: --- MSCAT --- by enq_cached_ms QUEUE SIZE OF QUEUE after enq 4Table 16 describes the significant fields shown in the display.
Table 16 debug appn ms Field Descriptions
APPN
Indicates that this is APPN debugging output.
MSP
Indicates that this is MS component output.
Related Commands
debug appn nof
To display debugging information on Advanced Peer-to-Peer Networking (APPN) Node Operator Facility (NOF) component activity, use the debug appn nof command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug appn nof
no debug appn nof
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The NOF component is responsible for processing commands entered by the user such as start, stop, show, and configuration commands. NOF forwards these commands to the proper component and waits for the response.
Examples
The following is sample output from the debug appn nof command. In this example, an APPN connection network is being defined.
Router# debug appn nofTurned on event 010000FFRouter# config termEnter configuration commands, one per line. End with CNTL/Z.Router(config)# appn connection-network NETA.CISCORouter(config-appn-cn)# port TR0Router(config-appn-cn)# completerouter(config)#APPN: ----- NOF ----- Define Connection Network Verb ReceivedAPPN: ----- NOF ----- send define_cn_t ips to csAPPN: ----- NOF ----- waiting for define_cn rsp from csrouter(config)#Table 17 describes the significant fields shown in the display.
Related Commands
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 18 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 19 describes the significant fields shown in the display.
Table 19 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 20 describes the significant fields shown in the display.
Table 20 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 21 describes the significant fields shown in the display.
Table 21 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 22 describes the significant fields shown in the display.
Table 22 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
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 the debugging and display of the archive 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 this command is not entered, there is no debugging or display of the configuration logging persistent events in the archive.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The configuration logger feature must be enabled in order for the debug capability to work.
Examples
The following example turns on the debugging feature and displays the configuration logging persistent events:
Router# debug archive config log 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.0' savedCommand `no shut' savedRouter#Related 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
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 enable debugging output for 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 [arp-entry-event | arp-table-event | ha | interface-interaction]
no debug arp [arp-entry-event | arp-table-event | ha | interface-interaction]
Syntax Description
Command Default
Debugging output is disabled for ARP transactions.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To enable ARP packet debugging, use this command without a keyword. The debugging information shows whether the router is sending ARP packets and whether it is receiving ARP packets. Use this command when some nodes on a TCP/IP network are responding, but others are not.
The amount of debug information displayed is filtered based on an interface, an access list, or both, as specified by the debug list command.
To list the debugging options enabled on this router, use the show debugging command.
Examples
The following example shows how to enable ARP packet debugging filtered on ARP table entries for the host at 192.0.2.10:
Router(config)# access-list 10 permit host 192.0.2.10Router(config)# exitRouter# debug list 10Router# debug arpARP packet debugging is onfor access list: 10The following is sample output from the debug arp command:
IP ARP: sent req src 192.0.2.7 0000.0c01.e117, dst 192.0.2.96 0000.0000.0000IP ARP: rcvd rep src 192.0.2.96 0800.2010.b908, dst 192.0.2.7IP ARP: rcvd req src 172.16.6.10 0000.0c00.6fa2, dst 192.0.2.62IP ARP: rep filtered src 192.0.2.7 aa92.1b36.a456, dst 255.255.255.255 ffff.ffff.ffffIP ARP: rep filtered src 192.0.2.240 0000.0c00.6b31, dst 192.0.2.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 192.0.2.7 and MAC address 0000.0c01.e117 sent an ARP request for the MAC address of the host at 192.0.2.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 192.0.2.7 0000.0c01.e117, dst 192.0.2.96 0000.0000.0000The second line indicates that the router at IP address 192.0.2.7 receives a reply from the host at 192.0.2.96 indicating that its MAC address is 0800.2010.b908:
IP ARP: rcvd rep src 192.0.2.96 0800.2010.b908, dst 192.0.2.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 192.0.2.62:
IP ARP: rcvd req src 172.16.6.10 0000.0c00.6fa2, dst 192.0.2.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 192.0.2.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 192.0.2.240, 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 192.0.2.240 0000.0c00.6b31, dst 192.0.2.7 0800.2010.b908Related Commands
debug ase
Note
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 23 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 24 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 25 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 autovc
To display information about autoprovisioned ATM permanent virtual circuit (PVC) events and errors, use the debug atm autovc command in privileged EXEC mode. To disable the display of information about autoprovisioned ATM PVC events and errors, use the no form of this command.
debug atm autovc {event | error | all}
no debug atm autovc {event | error | all}
Syntax Description
event
Displays all autoprovisioned PVC events.
error
Displays all autoprovisioned PVC errors.
all
Displays all autoprovisioned PVC events and errors.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows output for the debug atm autovc command for all autoprovisioned PVC events and errors:
Router# debug atm autovc allAutoVC all debugging is on00:09:03:AutoVC(ATM1/0):1/101 enqueuedThis message indicates that there is incoming traffic on PVC 1/101 and the PVC is enqueued to be processed.
00:09:03:AutoVC(ATM1/0):process VC 1/101This message indicates that PVC 1/101 is in the process of being autoprovisioned.
00:09:03:AutoVC(ATM1/0.1):bring up vc 1/101This message indicates that PVC 1/101 is being brought up.
00:09:03:%ATM-5-UPDOWN:Interface ATM1/0.1, Changing autovc 1/101 to UPThis message indicates that the PVC was brought up successfully.
Related Commands
create on-demand
Configures ATM PVC autoprovisioning, which enables a PVC or range of PVCs to be created automatically on demand.
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 26 describes the significant fields shown in the display.
.
Related Commands
debug atm cell-packing
To enable the display of ATM cell relay cell-packing debugging information, use the debug atm cell-packing command in privileged EXEC mode. To disable the display of debugging information, use the no form of this command.
debug atm cell-packing
no debug atm cell-packing
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example enables debugging for ATM virtual circuits (VCs) that have been configured with cell packing:
Router# debug atm cell-packingATM Cell Packing debugging is on00:09:04: ATM Cell Packing: vc 1/100 remote mncp 22 validatedThe following example enables debugging for permanent virtual paths (PVPs) that have been configured with cell packing:
Router# debug atm cell-packingATM Cell Packing debugging is on00:12:33: ATM Cell Packing: vp 1 remote mncp 22 validatedThe output indicates that the router received the MNCP information from the remote PE router.
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 27 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 ha-error
To debug ATM) high-availability (HA errors on a networking device, use the debug atm ha-error command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug atm ha-error
no debug atm ha-error
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding ATM HA errors on the networking device:
Router# debug atm ha-errorRelated Commands
debug atm ha-events
Debugs ATM HA events on the networking device.
debug atm ha-state
Debugs ATM HA state information on the networking device.
debug atm ha-events
To debug ATM high-availability (HA) events on the networking device, use the debug atm ha-events command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug atm ha-events
no debug atm ha-events
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding ATM HA events on the networking device:
Router# debug atm ha-eventsRelated Commands
debug atm ha-error
Debugs ATM HA errors on the networking device.
debug atm ha-state
Debugs ATM HA state information on the networking device.
debug atm ha-state
To debug ATM high-availability (HA) state information on the networking device, use the debug atm ha-state command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug atm ha-state
no debug atm ha-state
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding the ATM HA state on the networking device:
Router# debug atm ha-stateRelated Commands
debug atm ha-error
Debugs ATM HA errors on the networking device.
debug atm ha-events
Debugs ATM HA events on the networking device.
debug atm l2transport
To enable the display of debugging information related to ATM over MPLS, use the debug atm l2transport command in privileged EXEC mode. To disable the display of debugging information, use the no form of this command.
debug atm l2transport
no debug atm l2transport
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging of ATM over MPLS is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the events and messages when configuring ATM Cell Relay over MPLS in VP mode.
Router# debug atm l2transportATM L2transport Events and Errors debugging is onRouter# show debugATM L2transport:ATM L2transport Events and Errors debugging is onRouter(config-if)# atm pvp 24 l2transportRouter(cfg-if-atm-l2trans-pvp)# xconnect 11.11.11.11 700 pw-class vpRouter(cfg-if-atm-l2trans-pvp)# end00:14:51: ATM L2trans(ATM1/0): VP 24 is created00:14:51: ATM L2trans(ATM1/0): ckt_type 10, ckt_id 1000024 UP00:14:51: ATM L2trans(ATM1/0): VP 24, response is connect forwardedThe following example shows the events and messages when deleting a PVP.
Router(config-if)# no atm pvp 24 l2transport00:14:37: ATM L2trans(ATM1/0): ckt_type 10, ckt_id 1000024 DOWN00:14:37: ATM L2trans(ATM1/0): ckt_type 10, ckt_id 1000024 DOWN00:14:37: ATM L2trans(ATM1/0): remove xconnect circuit_type=10,circuit_id=100002400:14:37: ATM L2trans(ATM1/0): ckt_type 10, ckt_id 1000024 DOWNRelated Commands
show mpls l2transport vc
Displays information about AToM circuits that have been enabled to route Layer 2 packets on a router.
debug 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.
•
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
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
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 28 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) network 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 Modes
Privileged EXEC
Command History
Usage Guidelines
debug atm oc3 pom data command
Use the debug atm oc3 pom 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 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 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 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 is sample 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 29 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 30 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 31 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 are 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 32 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 33 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 34 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
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 authentication
To display debugging information about the Authentication Manager, use the debug authentication command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug authentication {all | errors | events | sync | feature {all | feature-name {all | errors | events}}}
no debug authentication {all | errors | events | sync | feature {all | feature-name {all | errors | events}}}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug authentication command to troubleshoot the Authentication Manager.
Examples
The following example shows sample output from the debug authentication command when the feature and events keywords are configured:
Router# debug authentication feature mda eventsAuth Manager mda events debugging is onRelated Commands
debug auto-config
To enable debugging for autoconfiguration 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 autoconfiguration debug trace.
errors
Displays autoconfiguration errors.
events
Displays autoconfiguration events.
parser
Displays autoconfiguration 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 autoconfiguration applications and to display autoconfiguration 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 35 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.
