Table Of Contents
Async Multilink PPP Troubleshooting Diagnostic Output
Cisco IOS show isdn status Command Output
Cisco IOS debug isdn q931 Command Output
Cisco IOS show modem summary Command Output
Cisco IOS debug ppp authentication Command Output
Cisco IOS show ppp multilink Command Output
Cisco IOS debug ppp negotiation Command Output
Cisco IOS show processes cpu Command Output
Cisco IOS show ip route Command Output
Async Multilink PPP Troubleshooting Diagnostic Output
The diagnostic output provided in this chapter present examples illustrating the process of diagnosing problems addressed in "Async MPPP Troubleshooting Tables." Diagnostic output provided here includes the following:
•
Cisco IOS show isdn status Command Output
•
Cisco IOS debug isdn q931 Command Output
•
Cisco IOS show modem summary Command Output
•
Cisco IOS debug ppp authentication Command Output
•
Cisco IOS show ppp multilink Command Output
•
Cisco IOS debug ppp negotiation Command Output
•
Cisco IOS show processes cpu Command Output
•
Cisco IOS show ip route Command Output
You can use the Output Interpreter tool to analyze the output from some of the commands listed in this chapter. The Output Interpreter is available from the following page Cisco Connection Online:
•
http://www.cisco.com/support/OutputInterpreter/
Refer to the Output Interpreter for a list of the commands it accepts.
3.1 Cisco IOS show isdn status Command Output
In the following example, the ISDN status messages are as expected: Layer 1 status is ACTIVE; Layer 2 status is in State=MULTIPLE_FRAME_ESTABLISHED.
![]()
Note
Layer 1 must be in ACTIVE state and Layer 2 must be in STATE=MULTIPLE_FRAME_ESTABLISHED for a connection to be successfully completed.
NAS#
show isdn status
Global ISDN Switchtype = primary-5ess
ISDN Serial0:23 interface
dsl 0, interface ISDN Switchtype = primary-5ess
Layer 1 Status:
ACTIVELayer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
The Free Channel Mask: 0x807FFFFF
Refer to Table 2-2 for related symptom, problem, and diagnostic notes.
The following is the output interpreter result for the above output indicating that the connection is behaving properly.
========================================
SHOW ISDN STATUS NOTIFICATIONS (if any):
========================================
Layers 1 and 2 (Q.921) of the ISDN interfaces are operating normally.![]()
Note
Access the Output Interpreter from this location:
http://www.cisco.com/support/OutputInterpreter/
3.2 Cisco IOS debug isdn q931 Command Output
In the following example output, the NAS receives a call setup message from the switch. (If the NAS does not receive a setup message verify that the PRI is functioning correctly.) The NAS then transmits a call processing message. The last line of this output shows that the call is successfully connected.
NAS#debug isdn q931ISDN Q931 packets debugging is onNAS#Aug 31 19:12:25.890 UTC: ISDN Se0:23: RX <- SETUP pd = 8 callref = 0x015DAug 31 19:12:25.890 UTC: Bearer Capability i = 0x9090A2Aug 31 19:12:25.890 UTC: Channel ID i = 0xA98381Aug 31 19:12:25.890 UTC: Called Party Number i = 0xC1, '3241937'Aug 31 19:12:25.894 UTC: ISDN Se0:23: TX -> CALL_PROC pd = 8 callref = 0x815DAug 31 19:12:25.894 UTC: Channel ID i = 0xA98381Aug 31 19:12:25.894 UTC: ISDN Se0:23: TX -> ALERTING pd = 8 callref = 0x815DAug 31 19:12:25.998 UTC: ISDN Se0:23: TX -> CONNECT pd = 8 callref = 0x815DAug 31 19:12:26.030 UTC: ISDN Se0:23: RX <- CONNECT_ACK pd = 8 callref = 0x015DAug 31 19:12:26.030 UTC: ISDN Se0:23: CALL_PROGRESS: CALL_CONNECTED call id 0x190, bchan -1, dsl 0Refer to Table 2-2 for related symptom, problem, and diagnostic notes.
3.3 Cisco IOS show modem summary Command Output
In the following example command output, 48 available incoming modems and 48 available outgoing modems are detected.
NAS#show modem summaryAvg Hold Incoming calls Outgoing calls Busied Failed No SuccTime Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.00:00:24 1 0 48 0 0 48 0 0 0 100%Refer to Table 2-2 for related symptom, problem, and diagnostic notes.
3.4 Cisco IOS debug ppp authentication Command Output
In the following example command output, the first and second connections are authencticated, but the third connection fails authentication.
NAS#debug ppp authenticationPPP authentication debugging is onNAS#Sep 1 13:11:27.683 UTC: As47 PPP: Treating connection as a callinSep 1 13:11:31.843 UTC: As47 CHAP: O CHALLENGE id 5 len 36 from "NAS"Sep 1 13:11:32.019 UTC: As47 CHAP: I RESPONSE id 5 len 37 from "clearlake-lan-01"Sep 1 13:11:32.019 UTC: As47 CHAP: O SUCCESS id 5 len 4Sep 1 13:11:32.123 UTC: Vi3 PPP: Treating connection as a dedicated lineSep 1 13:12:43.957 UTC: As35 PPP: Treating connection as a callinSep 1 13:12:48.041 UTC: As35 CHAP: O CHALLENGE id 5 len 36 from "NAS"Sep 1 13:12:48.277 UTC: As35 CHAP: I RESPONSE id 5 len 37 from "clearlake-lan-01"Sep 1 13:12:48.281 UTC: As35 CHAP: O SUCCESS id 5 len 4NAS#NAS#Sep 1 13:16:36.802 UTC: As19 PPP: Treating connection as a callinSep 1 13:16:40.834 UTC: As19 CHAP: O CHALLENGE id 4 len 36 from "NAS"Sep 1 13:16:41.026 UTC: As19 CHAP: I RESPONSE id 4 len 37 from "clearlake-lan-01"Sep 1 13:16:41.026 UTC: As19 CHAP: Unable to validate Response. Username clearlake-lan-01: Authentication failureSep 1 13:16:41.026 UTC: As19 CHAP: O FAILURE id 4 len 26 msg is "Authentication failure"NAS#NAS#Refer to Table 2-2 for related symptom, problem, and diagnostic notes.
3.5 Cisco IOS show ppp multilink Command Output
The following show ppp multilink Cisco IOS command output illustrates a situation where a bundle was created using both username and endpoint discriminator and where the bundle has two member links.
NAS#show ppp multilinkVirtual-Access1, bundle name is clearlake-lan-01/b07502c88ec4420014be1fc15537000000 lost fragments, 0 reordered, 0 unassigned, sequence 0x23/0x8 rcvd/sent0 discarded, 0 lost received, 1/255 loadMember links: 2 (max not set, min not set)Async48Async46Refer to Table 2-3,Table 2-4 and Table 2-8 for related symptom, problem, and diagnostic notes.
3.6 Cisco IOS debug ppp negotiation Command Output
The following output from debug ppp negotiation and debug ppp multilink events Cisco IOS commands combine to illustrates a situation in which a bundle was created using both username and endpoint discriminator and that the bundle has two member links.
![]()
Note
If either end of the link does not support multilink (or is not properly configured for multilink), the debug ppp negotiation Cisco IOS command output will show a
CONFREJ
(aREJect
) for MRRU and EndPoint Discriminator. If you see such an error output, ensure that your configuration is correct.
The debug command output example that follows illustrates the following events:
1.
The MRRU is CONFACKed (agreed upon by both sides) for a connection.
2.
The connection is virtualized.
3.
A bundle is created (first link joins bundle).
4.
A second connection attempted is detected.
5.
The MRRU for the second connection is agreed upon by both sides.
6.
The second connection is virtualized.
7.
The second connection is added to multilink bundle
NAS#debug ppp negotiationPPP protocol negotiation debugging is onNAS#debug ppp multilink eventsMultilink events debugging is onNAS#NAS#NAS#show debugPPP:PPP protocol negotiation debugging is onMultilink events debugging is onNAS#NAS#terminal monitorNAS#Sep 1 13:52:39.298 UTC: As2 IPCP: Install route to 172.21.104.25Sep 1 13:52:41.299 UTC: As2 PPP: Treating connection as a callinSep 1 13:52:41.299 UTC: As2 PPP: Phase is ESTABLISHING, Passive OpenSep 1 13:52:41.299 UTC: As2 LCP: State is ListenSep 1 13:52:42.287 UTC: As2 LCP: I CONFREQ [Listen] id 3 len 46Sep 1 13:52:42.287 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:42.287 UTC: As2 LCP: MagicNumber 0x0042C48F (0x05060042C48F)Sep 1 13:52:42.287 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:42.287 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:42.287 UTC: As2 LCP: Callback 6 (0x0D0306)Sep 1 13:52:42.287 UTC: As2 LCP: MRRU 1500 (0x110405DC)Sep 1 13:52:42.287 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:42.287 UTC: As2 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:52:42.287 UTC: As2 LCP: (0x370000)Sep 1 13:52:42.287 UTC: As2 LCP: O CONFREQ [Listen] id 12 len 47Sep 1 13:52:42.291 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:42.291 UTC: As2 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:52:42.291 UTC: As2 LCP: MagicNumber 0xA53BCC27 (0x0506A53BCC27)Sep 1 13:52:42.291 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:42.291 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:42.291 UTC: As2 LCP: MRRU 1524 (0x110405F4)Sep 1 13:52:42.291 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:42.291 UTC: As2 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:52:42.291 UTC: As2 LCP: (0x3031)Sep 1 13:52:42.291 UTC: As2 LCP: O CONFREJ [Listen] id 3 len 7Sep 1 13:52:42.291 UTC: As2 LCP: Callback 6 (0x0D0306)Sep 1 13:52:44.287 UTC: As2 LCP: TIMEout: State REQsentSep 1 13:52:44.287 UTC: As2 LCP: O CONFREQ [REQsent] id 13 len 47Sep 1 13:52:44.287 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:44.287 UTC: As2 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:52:44.287 UTC: As2 LCP: MagicNumber 0xA53BCC27 (0x0506A53BCC27)Sep 1 13:52:44.287 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:44.287 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:44.287 UTC: As2 LCP: MRRU 1524 (0x110405F4)Sep 1 13:52:44.287 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:44.287 UTC: As2 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:52:44.287 UTC: As2 LCP: (0x3031)Sep 1 13:52:44.479 UTC: As2 LCP: I CONFACK [REQsent] id 13 len 47Sep 1 13:52:44.479 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:44.479 UTC: As2 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:52:44.479 UTC: As2 LCP: MagicNumber 0xA53BCC27 (0x0506A53BCC27)Sep 1 13:52:44.483 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:44.483 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:44.483 UTC: As2 LCP: MRRU 1524 (0x110405F4)Sep 1 13:52:44.483 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:44.483 UTC: As2 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:52:44.483 UTC: As2 LCP: (0x3031)Sep 1 13:52:45.279 UTC: As2 LCP: I CONFREQ [ACKrcvd] id 4 len 46Sep 1 13:52:45.283 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:45.283 UTC: As2 LCP: MagicNumber 0x0042C48F (0x05060042C48F)Sep 1 13:52:45.283 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:45.283 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:45.283 UTC: As2 LCP: Callback 6 (0x0D0306)Sep 1 13:52:45.283 UTC: As2 LCP: MRRU 1500 (0x110405DC)Sep 1 13:52:45.283 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:45.283 UTC: As2 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:52:45.283 UTC: As2 LCP: (0x370000)Sep 1 13:52:45.283 UTC: As2 LCP: O CONFREJ [ACKrcvd] id 4 len 7Sep 1 13:52:45.283 UTC: As2 LCP: Callback 6 (0x0D0306)Sep 1 13:52:45.475 UTC: As2 LCP: I CONFREQ [ACKrcvd] id 5 len 43Sep 1 13:52:45.475 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:45.475 UTC: As2 LCP: MagicNumber 0x0042C48F (0x05060042C48F)Sep 1 13:52:45.475 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:45.475 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:45.475 UTC: As2 LCP: MRRU 1500 (0x110405DC)Sep 1 13:52:45.475 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:45.475 UTC: As2 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:52:45.475 UTC: As2 LCP: (0x370000)Sep 1 13:52:45.475 UTC: As2 LCP: O CONFACK [ACKrcvd] id 5 len 43Sep 1 13:52:45.475 UTC: As2 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:52:45.475 UTC: As2 LCP: MagicNumber 0x0042C48F (0x05060042C48F)Sep 1 13:52:45.475 UTC: As2 LCP: PFC (0x0702)Sep 1 13:52:45.475 UTC: As2 LCP: ACFC (0x0802)Sep 1 13:52:45.475 UTC: As2 LCP: MRRU 1500 (0x110405DC)Sep 1 13:52:45.475 UTC: As2 LCP: EndpointDisc 1 LocalSep 1 13:52:45.475 UTC: As2 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:52:45.475 UTC: As2 LCP: (0x370000)Sep 1 13:52:45.475 UTC: As2 LCP: State is OpenSep 1 13:52:45.475 UTC: As2 PPP: Phase is AUTHENTICATING, by this endSep 1 13:52:45.475 UTC: As2 CHAP: O CHALLENGE id 5 len 36 from "NAS"Sep 1 13:52:45.667 UTC: As2 CHAP: I RESPONSE id 5 len 37 from "clearlake-lan-01"Sep 1 13:52:45.667 UTC: As2 CHAP: O SUCCESS id 5 len 4Sep 1 13:52:45.667 UTC: As2 MLP: Multilink up event pendingSep 1 13:52:45.667 UTC: As2 PPP: Phase is VIRTUALIZEDSep 1 13:52:45.667 UTC: Vi1 PPP: Phase is DOWN, SetupSep 1 13:52:45.667 UTC: Vi1 MLP: VP: Clone from Vtemplate 1 block=1Sep 1 13:52:45.767 UTC: Vi1 PPP: Treating connection as a dedicated lineSep 1 13:52:45.767 UTC: Vi1 PPP: Phase is ESTABLISHING, Active OpenSep 1 13:52:45.771 UTC: Vi1 LCP: O CONFREQ [Closed] id 1 len 37Sep 1 13:52:45.771 UTC: Vi1 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:52:45.771 UTC: Vi1 LCP: MagicNumber 0xA53BD9C1 (0x0506A53BD9C1)Sep 1 13:52:45.771 UTC: Vi1 LCP: MRRU 1524 (0x110405F4)Sep 1 13:52:45.771 UTC: Vi1 LCP: EndpointDisc 1 LocalSep 1 13:52:45.771 UTC: Vi1 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:52:45.771 UTC: Vi1 LCP: (0x3031)Sep 1 13:52:45.771 UTC: Vi1 PPP: Phase is UPSep 1 13:52:45.771 UTC: Vi1 IPCP: O CONFREQ [Closed] id 1 len 10Sep 1 13:52:45.771 UTC: Vi1 IPCP: Address 172.21.104.254 (0x0306AC1568FE)Sep 1 13:52:45.771 UTC: As2 MLP: clearlake-lan-01/b07502c88ec4420014be1fc155370000, multilink up, first linkSep 1 13:52:45.771 UTC: As2 IPCP: Remove route to 172.21.104.25Sep 1 13:52:45.843 UTC: Vi1 IPCP: I CONFREQ [REQsent] id 1 len 40Sep 1 13:52:45.843 UTC: Vi1 IPCP: CompressType VJ 15 slots CompressSlotID (0x0206002D0F01)Sep 1 13:52:45.843 UTC: Vi1 IPCP: Address 0.0.0.0 (0x030600000000)Sep 1 13:52:45.843 UTC: Vi1 IPCP: PrimaryDNS 0.0.0.0 (0x810600000000)Sep 1 13:52:45.843 UTC: Vi1 IPCP: PrimaryWINS 0.0.0.0 (0x820600000000)Sep 1 13:52:45.843 UTC: Vi1 IPCP: SecondaryDNS 0.0.0.0 (0x830600000000)Sep 1 13:52:45.843 UTC: Vi1 IPCP: SecondaryWINS 0.0.0.0 (0x840600000000)Sep 1 13:52:45.843 UTC: Vi1 IPCP: Pool returned 172.21.104.48Sep 1 13:52:45.843 UTC: Vi1 IPCP: O CONFREJ [REQsent] id 1 len 22Sep 1 13:52:45.843 UTC: Vi1 IPCP: CompressType VJ 15 slots CompressSlotID (0x0206002D0F01)Sep 1 13:52:45.843 UTC: Vi1 IPCP: PrimaryWINS 0.0.0.0 (0x820600000000)Sep 1 13:52:45.843 UTC: Vi1 IPCP: SecondaryWINS 0.0.0.0 (0x840600000000)Sep 1 13:52:45.843 UTC: Vi1 CCP: I CONFREQ [Not negotiated] id 1 len 15Sep 1 13:52:45.843 UTC: Vi1 CCP: MS-PPC supported bits 0x00000001 (0x120600000001)Sep 1 13:52:45.843 UTC: Vi1 CCP: Stacker history 1 check mode EXTENDED (0x1105000104)Sep 1 13:52:45.843 UTC: Vi1 LCP: O PROTREJ [Open] id 2 len 21 protocol CCPSep 1 13:52:45.843 UTC: Vi1 LCP: (0x80FD0101000F12060000000111050001)Sep 1 13:52:45.843 UTC: Vi1 LCP: (0x04)Sep 1 13:52:45.939 UTC: Vi1 IPCP: I CONFACK [REQsent] id 1 len 10Sep 1 13:52:45.939 UTC: Vi1 IPCP: Address 172.21.104.254 (0x0306AC1568FE)Sep 1 13:52:47.771 UTC: Vi1 IPCP: TIMEout: State ACKrcvdSep 1 13:52:47.771 UTC: Vi1 IPCP: O CONFREQ [ACKrcvd] id 2 len 10Sep 1 13:52:47.771 UTC: Vi1 IPCP: Address 172.21.104.254 (0x0306AC1568FE)Sep 1 13:52:47.923 UTC: Vi1 IPCP: I CONFACK [REQsent] id 2 len 10Sep 1 13:52:47.923 UTC: Vi1 IPCP: Address 172.21.104.254 (0x0306AC1568FE)Sep 1 13:52:48.835 UTC: Vi1 IPCP: I CONFREQ [ACKrcvd] id 2 len 34Sep 1 13:52:48.835 UTC: Vi1 IPCP: Address 0.0.0.0 (0x030600000000)Sep 1 13:52:48.835 UTC: Vi1 IPCP: PrimaryDNS 0.0.0.0 (0x810600000000)Sep 1 13:52:48.835 UTC: Vi1 IPCP: PrimaryWINS 0.0.0.0 (0x820600000000)Sep 1 13:52:48.835 UTC: Vi1 IPCP: SecondaryDNS 0.0.0.0 (0x830600000000)Sep 1 13:52:48.835 UTC: Vi1 IPCP: SecondaryWINS 0.0.0.0 (0x840600000000)Sep 1 13:52:48.835 UTC: Vi1 IPCP: O CONFREJ [ACKrcvd] id 2 len 16Sep 1 13:52:48.835 UTC: Vi1 IPCP: PrimaryWINS 0.0.0.0 (0x820600000000)Sep 1 13:52:48.835 UTC: Vi1 IPCP: SecondaryWINS 0.0.0.0 (0x840600000000)Sep 1 13:52:49.011 UTC: Vi1 IPCP: I CONFREQ [ACKrcvd] id 3 len 22Sep 1 13:52:49.011 UTC: Vi1 IPCP: Address 0.0.0.0 (0x030600000000)Sep 1 13:52:49.011 UTC: Vi1 IPCP: PrimaryDNS 0.0.0.0 (0x810600000000)Sep 1 13:52:49.011 UTC: Vi1 IPCP: SecondaryDNS 0.0.0.0 (0x830600000000)Sep 1 13:52:49.011 UTC: Vi1 IPCP: O CONFNAK [ACKrcvd] id 3 len 22Sep 1 13:52:49.011 UTC: Vi1 IPCP: Address 172.21.104.48 (0x0306AC156830)Sep 1 13:52:49.011 UTC: Vi1 IPCP: PrimaryDNS 172.22.53.210 (0x8106AC1635D2)Sep 1 13:52:49.011 UTC: Vi1 IPCP: SecondaryDNS 171.68.10.70 (0x8306AB440A46)Sep 1 13:52:49.203 UTC: Vi1 IPCP: I CONFREQ [ACKrcvd] id 4 len 22Sep 1 13:52:49.203 UTC: Vi1 IPCP: Address 172.21.104.48 (0x0306AC156830)Sep 1 13:52:49.203 UTC: Vi1 IPCP: PrimaryDNS 172.22.53.210 (0x8106AC1635D2)Sep 1 13:52:49.203 UTC: Vi1 IPCP: SecondaryDNS 171.68.10.70 (0x8306AB440A46)Sep 1 13:52:49.203 UTC: Vi1 IPCP: O CONFACK [ACKrcvd] id 4 len 22Sep 1 13:52:49.203 UTC: Vi1 IPCP: Address 172.21.104.48 (0x0306AC156830)Sep 1 13:52:49.203 UTC: Vi1 IPCP: PrimaryDNS 172.22.53.210 (0x8106AC1635D2)Sep 1 13:52:49.203 UTC: Vi1 IPCP: SecondaryDNS 171.68.10.70 (0x8306AB440A46)Sep 1 13:52:49.207 UTC: Vi1 IPCP: State is OpenSep 1 13:52:49.207 UTC: Vi1 IPCP: Install route to 172.21.104.48NAS#NAS#Sep 1 13:53:41.928 UTC: As5 IPCP: Install route to 172.21.104.24Sep 1 13:53:43.928 UTC: As5 PPP: Treating connection as a callinSep 1 13:53:43.928 UTC: As5 PPP: Phase is ESTABLISHING, Passive OpenSep 1 13:53:43.928 UTC: As5 LCP: State is ListenSep 1 13:53:44.792 UTC: As5 LCP: I CONFREQ [Listen] id 3 len 46Sep 1 13:53:44.792 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:44.792 UTC: As5 LCP: MagicNumber 0x0043B7F1 (0x05060043B7F1)Sep 1 13:53:44.792 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:44.792 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:44.792 UTC: As5 LCP: Callback 6 (0x0D0306)Sep 1 13:53:44.792 UTC: As5 LCP: MRRU 1500 (0x110405DC)Sep 1 13:53:44.792 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:44.792 UTC: As5 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:53:44.792 UTC: As5 LCP: (0x370000)Sep 1 13:53:44.792 UTC: As5 LCP: O CONFREQ [Listen] id 17 len 47Sep 1 13:53:44.792 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:44.792 UTC: As5 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:53:44.792 UTC: As5 LCP: MagicNumber 0xA53CC053 (0x0506A53CC053)Sep 1 13:53:44.792 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:44.792 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:44.792 UTC: As5 LCP: MRRU 1524 (0x110405F4)Sep 1 13:53:44.796 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:44.796 UTC: As5 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:53:44.796 UTC: As5 LCP: (0x3031)Sep 1 13:53:44.796 UTC: As5 LCP: O CONFREJ [Listen] id 3 len 7Sep 1 13:53:44.796 UTC: As5 LCP: Callback 6 (0x0D0306)Sep 1 13:53:46.792 UTC: As5 LCP: TIMEout: State REQsentSep 1 13:53:46.792 UTC: As5 LCP: O CONFREQ [REQsent] id 18 len 47Sep 1 13:53:46.792 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:46.792 UTC: As5 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:53:46.792 UTC: As5 LCP: MagicNumber 0xA53CC053 (0x0506A53CC053)Sep 1 13:53:46.792 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:46.792 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:46.792 UTC: As5 LCP: MRRU 1524 (0x110405F4)Sep 1 13:53:46.792 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:46.792 UTC: As5 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:53:46.792 UTC: As5 LCP: (0x3031)Sep 1 13:53:47.032 UTC: As5 LCP: I CONFACK [REQsent] id 18 len 47Sep 1 13:53:47.032 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:47.032 UTC: As5 LCP: AuthProto CHAP (0x0305C22305)Sep 1 13:53:47.032 UTC: As5 LCP: MagicNumber 0xA53CC053 (0x0506A53CC053)Sep 1 13:53:47.032 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:47.032 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:47.032 UTC: As5 LCP: MRRU 1524 (0x110405F4)Sep 1 13:53:47.032 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:47.032 UTC: As5 LCP: (0x131201626F62736C616B652D6E61732D)Sep 1 13:53:47.032 UTC: As5 LCP: (0x3031)Sep 1 13:53:47.800 UTC: As5 LCP: I CONFREQ [ACKrcvd] id 4 len 46Sep 1 13:53:47.800 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:47.800 UTC: As5 LCP: MagicNumber 0x0043B7F1 (0x05060043B7F1)Sep 1 13:53:47.800 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:47.800 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:47.800 UTC: As5 LCP: Callback 6 (0x0D0306)Sep 1 13:53:47.800 UTC: As5 LCP: MRRU 1500 (0x110405DC)Sep 1 13:53:47.804 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:47.804 UTC: As5 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:53:47.804 UTC: As5 LCP: (0x370000)Sep 1 13:53:47.804 UTC: As5 LCP: O CONFREJ [ACKrcvd] id 4 len 7Sep 1 13:53:47.804 UTC: As5 LCP: Callback 6 (0x0D0306)Sep 1 13:53:48.008 UTC: As5 LCP: I CONFREQ [ACKrcvd] id 5 len 43Sep 1 13:53:48.008 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:48.008 UTC: As5 LCP: MagicNumber 0x0043B7F1 (0x05060043B7F1)Sep 1 13:53:48.008 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:48.008 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:48.008 UTC: As5 LCP: MRRU 1500 (0x110405DC)Sep 1 13:53:48.012 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:48.012 UTC: As5 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:53:48.012 UTC: As5 LCP: (0x370000)Sep 1 13:53:48.012 UTC: As5 LCP: O CONFACK [ACKrcvd] id 5 len 43Sep 1 13:53:48.012 UTC: As5 LCP: ACCM 0x000A0000 (0x0206000A0000)Sep 1 13:53:48.012 UTC: As5 LCP: MagicNumber 0x0043B7F1 (0x05060043B7F1)Sep 1 13:53:48.012 UTC: As5 LCP: PFC (0x0702)Sep 1 13:53:48.012 UTC: As5 LCP: ACFC (0x0802)Sep 1 13:53:48.012 UTC: As5 LCP: MRRU 1500 (0x110405DC)Sep 1 13:53:48.012 UTC: As5 LCP: EndpointDisc 1 LocalSep 1 13:53:48.012 UTC: As5 LCP: (0x131301B07502C88EC4420014BE1FC155)Sep 1 13:53:48.012 UTC: As5 LCP: (0x370000)Sep 1 13:53:48.012 UTC: As5 LCP: State is OpenSep 1 13:53:48.012 UTC: As5 PPP: Phase is AUTHENTICATING, by this endSep 1 13:53:48.012 UTC: As5 CHAP: O CHALLENGE id 6 len 36 from "NAS"Sep 1 13:53:48.264 UTC: As5 CHAP: I RESPONSE id 6 len 37 from "clearlake-lan-01"Sep 1 13:53:48.268 UTC: As5 CHAP: O SUCCESS id 6 len 4Sep 1 13:53:48.268 UTC: As5 MLP: Multilink up event pendingSep 1 13:53:48.268 UTC: As5 PPP: Phase is VIRTUALIZEDSep 1 13:53:48.268 UTC: As5 MLP: clearlake-lan-01/b07502c88ec4420014be1fc155370000, multilink upSep 1 13:53:48.268 UTC: As5 IPCP: Remove route to 172.21.104.24NAS#NAS#Refer to Table 2-3,Table 2-4 and Table 2-8 for related symptom, problem, and diagnostic notes.
3.7 Cisco IOS show processes cpu Command Output
In the following example command output, the CPU utilization is very low.
NAS#show processes cpuCPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process1 110876 1344651 82 0.00% 0.00% 0.00% 0 Load Meter2 356 3895 91 0.24% 0.02% 0.00% 50 Virtual Exec3 6619420 904515 7318 0.00% 0.06% 0.06% 0 Check heapsRefer to Table 2-3 and Table 2-5 for related symptom, problem, and diagnostic notes.
3.8 Cisco IOS show ip route Command Output
The following show ip route client-IP-address Cisco IOS command output illustrates the use of this command to determine whether a route to a specific IP address exists. In this case, the route exists and is directly connected via Virtual-Access1.
NAS#show ip route 172.21.104.48Routing entry for 172.21.104.48/32Known via "connected", distance 0, metric 0 (connected, via interface)Redistributing via eigrp 1Advertised by eigrp 1Routing Descriptor Blocks:* directly connected, via Virtual-Access1Route metric is 0, traffic share count is 1Another option is to use the generic form of the command. However, using this command can result in a long output when large routing tables exist in a NAS or router. The following is an example of a show ip route output (with a very small routing table) where the client IP address (172.21.104.48) is found.
NAS#show ip routeCodes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGPi - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area* - candidate default, U - per-user static route, o - ODRP - periodic downloaded static routeGateway of last resort is 172.21.101.1 to network 0.0.0.0172.21.0.0/16 is variably subnetted, 12 subnets, 2 masksD 172.21.200.0/24 [90/284160] via 172.21.101.1, 3w6d, FastEthernet0D 172.21.10.1/32 [90/156160] via 172.21.101.20, 2w6d, FastEthernet0D 172.21.10.7/32 [90/412160] via 172.21.101.1, 2w6d, FastEthernet0D 172.21.10.6/32 [90/156160] via 172.21.101.1, 6w0d, FastEthernet0D 172.21.10.5/32 [90/412160] via 172.21.101.1, 3w6d, FastEthernet0C 172.21.10.10/32 is directly connected, Loopback0C 172.21.104.0/24 is directly connected, Loopback1D 172.21.99.0/24 [90/309760] via 172.21.101.1, 3w6d, FastEthernet0C 172.21.101.0/24 is directly connected, FastEthernet0D 172.21.100.0/24 [90/309760] via 172.21.101.1, 3w6d, FastEthernet0D 172.21.102.0/24 [90/309760] via 172.21.101.1, 2w6d, FastEthernet0C 172.21.104.48/32 is directly connected, Virtual-Access1D EX 172.22.0.0/16 [170/297272576] via 172.21.101.1, 3w6d, FastEthernet0D*EX 0.0.0.0/0 [170/309760] via 172.21.101.1, 3w6d, FastEthernet0Refer to Table 2-4 for related symptom, problem, and diagnostic notes.