Votos - 0, Puntuación media: 0
(
)
)
|
Resumen del manual
ISDN Protocol Analyzer Display E-4 Using the Protocol Analyzer and Trace Tools Appetool.fm Page 5 Friday, October 6, 2000 5:35 PM Reference Guide for the Model RT338 ISDN Router Packet Tracing You can diagnose PPP connection failures using the packet trace feature of the Model RT338 router. To invoke the packet trace: 1. Access the internal Manager of the router using a serial or Telnet terminal connection. 2. If you are tracing an outgoing call, go to Menu 11 (Remote Node Setup) and note which remote node number, N, corresponds to the location you are calling. 3. Invoke the Command Interpreter Mode (Menu 24.8). 4. Clear any existing trace information by entering: rt338> sys trcl cl 5. Turn on the trace log by entering: rt338> sys trcl sw on 6. Turn on the packet trace by entering: rt338> sys trcp sw on 7. Trace the call. To trace an outgoing call, force the router to dial the remote node by entering: rt338> dev dial N (N is the remote node number shown in Menu 11.) To trace an incoming call, simply wait for the call. 8. Wait for all progress messages, and then (if necessary) force the router to drop the ISDN connection by entering: rt338> dev chan drop [bri0|bri1] In this command, bri0 refers to B1 and bri1 refers to B2. 9. Turn off the trace log by entering: rt338> sys trcl sw off rt338> sys trcp sw off 10. Wait for the desired activity, and then display the trace log by entering: rt338> sys trcl disp Using the Protocol Analyzer and Trace Tools E-5 Appetool.fm Page 6 Friday, October 6, 2000 5:35 PM Reference Guide for the Model RT338 ISDN Router The trace appears on the screen as in Figure E-2. Use PageUp and PageDown to inspect the entire trace. rt328> sys trcl cl Program Trace Switch OFF rt328> sys trcl sw on rt328> sys trcp sw on rt328> isdn dial 1 Start dialing for node<1> Dialing chan<1> phone(last 9-digit):40201 ### Hit any key to continue.### Call CONNECT speed<64000> chan<1> prot<1> LCP up CHAP send response CHAP login to remote OK! IPCP negotiation started BACP negotiation started BACP up <<< ------user strikes a key to get a prompt rt328> sys trcl disp 102 fe3792 15e PDI1 dialer Dialing chan<1> phone(last 9-digit):40201 103 fe3ea4 169 PDI1 dialer Call CONNECT speed<64000> chan<1> prot<1> 104 fe3eb8 0 POU1 ebp=4aa00,seqNum=17 PPP1-XMIT:24 len:40 0000: ff 03 c0 21 01 12 00 24 01 04 05 f4 02 06 00 00 0010: 00 00 08 02 0d 03 06 11 04 05 f4 13 09 03 00 a0 105 fe3f30 0 PNET ebp=4aa30,seqNum=18 PPP1-RECV:24 len:42 0000: ff 03 c0 21 01 30 00 26 01 04 05 f4 02 06 00 00 0010: 00 00 03 05 c2 23 05 08 02 11 04 05 f4 13 09 03 106 fe3f3a 0 POU1 ebp=4aa60,seqNum=19 PPP1-XMIT:24 len:42 0000: ff 03 c0 21 02 30 00 26 01 04 05 f4 02 06 00 00 0010: 00 00 03 05 c2 23 05 08 02 11 04 05 f4 13 09 03 107 fe3f44 0 PNET ebp=4aa90,seqNum=1a PPP1-RECV:24 len:40 0000: ff 03 c0 21 02 12 00 24 01 04 05 f4 02 06 00 00 0010: 00 00 08 02 0d 03 06 11 04 05 f4 13 09 03 00 a0 108 fe3f44 186 PNET ppp LCP up 109 fe3fc6 0 PNET ebp=4aac0,seqNum=1b PPP1-RECV:24 len:15 0000: c2 23 01 11 00 0d 08 00 00 48 e4 00 04 fc 6c 110 fe3fc6 190 PNET ppp CHAP send response 111 fe3fd0 0 POU1 ebp=4aaf0,seqNum=1c PPP1-XMIT:24 len:28 0000: c2 23 02 11 00 1a 10 ce f1 4c 9f fe 01 a9 85 04 0010: bb 0b 51 e5 17 3e 5e 50 32 38 36 34 112 fe4002 0 PNET ebp=4ab20,seqNum=1d PPP1-RECV:24 len:13 0000: c2 23 03 11 00 0b 57 65 6c 63 6f 6d 65 113 fe4002 195 PNET ppp CHAP login to remote OK! 114 fe400c 0 PNET ebp=4ab50,seqNum=1e PPP1-RECV:24 len:8 0000: c0 29 01 32 00 06 01 02 115 fe400c 0 POU1 ebp=4ab80,seqNum=1f PPP1-XMIT:24 len:8 0000: c0 29 02 32 00 06 01 02 116 fe402a 0 PNET ebp=4abb0,seqNum=20 PPP1-RECV:24 len:8 0000: c0 29 03 32 00 06 01 02 117 fe4034 225 PNET ppp IPCP negotiation started 118 fe403e 0 POU1 ebp=4abe0,seqNum=21 PPP1-XMIT:24 len:18 0000: 80 21 01 12 00 10 02 06 00 2d 0f 01 03 06 cc f7 0010: cb b7 E-6 Using the Protocol Analyzer and Trace Tools Appetool.fm Page 7 Friday, October 6, 2000 5:35 PM Reference Guide for the Model RT338 ISDN Router 119 fe403e 2d7 PNET ppp BACP negotiation started 120 fe4048 0 POU1 ebp=4ac10,seqNum=22 PPP1-XMIT:24 len:12 0000: 80 71 01 13 00 0a 01 06 00 00 00 01 121 fe4048 0 PNET ebp=4ac40,seqNum=23 PPP1-RECV:24 len:12 0000: 80 2b 01 16 00 0a 01 06 00 00 00 00 122 fe4048 0 POU1 ebp=4ac70,seqNum=24 PPP1-XMIT:24 len:20 0000: ff 03 c0 21 08 13 00 10 80 2b 01 16 00 0a 01 06 0010: 00 00 00 00 123 fe4052 0 PNET ebp=4aca0,seqNum=25 PPP1-RECV:24 len:12 0000: 80 71 01 17 00 0a 01 06 ff ff ff ff 124 fe4052 0 POU1 ebp=4acd0,seqNum=26 PPP1-XMIT:24 len:12 0000: 80 71 02 17 00 0a 01 06 ff ff ff ff 125 fe405c 0 PNET ebp=4ad00,seqNum=27 PPP1-RECV:24 len:26 0000: ff 03 c0 21 08 33 00 16 80 21 01 12 00 10 02 06 0010: 00 2d 0f 01 03 06 cc f7 cb b7 126 fe4066 0 PNET ebp=4ad30,seqNum=28 PPP1-RECV:24 len:12 0000: 80 71 02 13 00 0a 01 06 00 00 00 01 127 fe4066 2d8 PNET ppp BACP up Program Trace Switch OFF Packet Trace Switch OFF rt328> Figure E-2. Trace Screen Using the Protocol Analyzer and Trace Tools E-7 Appetool.fm Page 8 Friday, October 6, 2...