Tài liệu ISDN Debug Information docx

11 220 0
Tài liệu ISDN Debug Information docx

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

Thông tin tài liệu

Cisco - ISDN Debug Information ISDN Debug Information This tech tip contains some common ISDN/PPP/CHAP debug messages, what they indicate, and suggestions for resolving them. Check out the following examples: ● Example 1: DEBUG ISDN EVENT ● Example 2: DEBUG ISDN Q931 ● Example 3: DEBUG DIALER ● Example 4: DEBUG PPP CHAP, DEBUG PPP NEGOTIATION ● Example 5: DEBUG ISDN EVENT, DEBUG ISDN Q931 ● Example 6: DEBUG ISDN Q921 ● Example 7: DEBUG ISDN EVENT, DEBUG ISDN Q931 ● Example 8: DEBUG ISDN Q931 ● Example 9: DEBUG PPP NEGOTIATION, DEBUG PPP CHAP ● Related Information Example 1 Debug: DEBUG ISDN EVENT BRI0: ISDN Event: incoming ces value = 1 BRI0: received HOST_TERM_REGISTER_NACK - invalid EID/SPID or TEI not assigned Cause i = 0x8082 - No route to specified network Indication: Usually a SPID problem. To verify that TEI is assigned, try show isdn status. Layer 2 information will tell if TEI is assigned. Suggestions: 1. Check the configuration to see if the SPIDs are configured correctly. 2. Have your service provider verify the SPIDs, and if necessary have them track the SPIDs. http://www.cisco.com/warp/public/129/18.html (1 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information Example 2 Debug: DEBUG ISDN Q931 BRI0: Dialing cause: BRI0: ip PERMIT BRI0: Attempting to dial 6968900 TX -> SETUP dsl = 0 pd = 8 callref = 0x01 Bearer Capability i = 0x8890218F Channel ID i = 0x83 Called Party Number i = 0x80, '6968900' RX <- CALL_PROC dsl = 0 pd = 8 callref = 0x81 Channel ID i = 0x89 RX <- PROGRESS dsl = 0 pd = 8 callref = 0x81 Progress Ind i = 0xC48A - Delay in response at called interface Signal i = 0x01. RX <- DISCONNECT dsl = 0 pd = 8 callref = 0x81 Cause i = 0x8295 - Call rejected Signal i = 0x01 TX -> RELEASE dsl = 0 pd = 8 callref = 0x01 RX <- RELEASE_COMP dsl = 0 pd = 8 callref = 0x81 Signal i = 0x3F Indication: Remote router does not answer call. Suggestions: Verify the telephone number and SPIDs. Example 3 Debug: DEBUG DIALER BRI0: Dialing cause: BRI0: ip PERMIT BRI0: No dialer string defined. Dialing cannot occur BRI0: Dialing cause: BRI0: ip PERMIT BRI0: No dialer string defined. Dialing cannot occur http://www.cisco.com/warp/public/129/18.html (2 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information BRI0: Dialing cause: BRI0: ip PERMIT BRI0: No dialer string defined. Dialing cannot occur BRI0: Dialing cause: BRI0: ip PERMIT BRI0: No dialer string defined. Dialing cannot occur BRI0: Dialing cause: BRI0: ip PERMIT BRI0: No dialer string defined. Dialing cannot occur Indication: Dialing cannot occur. Suggestions: Check the configuration (dialer map, dialer string, dialer group). Example 4 Debug: DEBUG PPP CHAP, DEBUG PPP NEGOTIATION pico#ping 192.9.198.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.9.198.1, timeout is 2 seconds: %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEEF99 ppp: received config for type = 3 (AUTHTYPE) value = C223 value = 5 acked ppp: received config for type = 5 (MAGICNUMBER) value = 1E23F5C acked PPP BRI0: B-Channel 1: state = ACKSENT fsm_rconfack(C021): rcvd id E4 ppp: config ACK received, type. = 3 (CI_AUTHTYPE), value = C223 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 28CEEF99 BRI0: B-Channel 1: PPP AUTH CHAP input code = 1 id = 82 len = 16 BRI0: B-Channel 1: PPP AUTH CHAP input code = 2 id = 95 len = 28 BRI0: B-Channel 1: PPP AUTH CHAP input code = 4 id = 82 len = 21 BRI0: B-Channel 1: Failed CHAP authentication with remote. Remote message is: MD compare failed ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEEFDB %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 http://www.cisco.com/warp/public/129/18.html (3 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEF76C ppp: received config for type = 3 (AUTHTYPE) value = C223 value = 5 acked ppp: received conf.ig for type = 5 (MAGICNUMBER) value = 1E24718 acked PPP BRI0: B-Channel 1: state = ACKSENT fsm_rconfack(C021): rcvd id E6 ppp: config ACK received, type = 3 (CI_AUTHTYPE), value = C223 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 28CEF76C BRI0: B-Channel 1: PPP AUTH CHAP input code = 1 id = 83 len = 16 BRI0: B-Channel 1: PPP AUTH CHAP input code = 2 id = 96 len = 28 BRI0: B-Channel 1: PPP AUTH CHAP input code = 4 id = 83 len = 21 BRI0: B-Channel 1: Failed CHAP authentication with remote. Remote message is: MD compare failed Indication: CHAP authentication failed. Suggestions: Check username and passwords for the correct spelling and use of lower and upper case letters. Check the dialer map command for name keyword and the correct hostname. Example 5 Debug: DEBUG ISDN EVENT, DEBUG ISDN Q931 TX -> RRp dsl = 1 sapi = 0 tei = 96 nr = 98 RX <- RRf dsl = 1 sapi = 0 tei = 96 nr = 108 RX <- UI dsl = 1 sapi = 0 tei = 127 i = 0x08015805040288901801893401407008C135353434373336 SETUP dsl = 1 pd = 8 callref = 0x58 Bearer Capability i = 0x8890 Channel ID i = 0x89 Signal i = 0x40 Called Party Number i = 0xC1, '5544736' ISDN Event: incoming ces value = 1 received HOST_INCOMING_CALL Bearer Capability i = 0x080010 ------------------- Channel ID i = 0x0101 Called Party Number i = 0x0401, '5544736' IE out of order or end of 'private' IEs -- http://www.cisco.com/warp/public/129/18.html (4 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information Bearer Capability i = 0x8890 Channel ID i = 0x89 Signal i = 0x40 Called Party Number i = 0xC1, '5544736' ISDN Event: Received a call from on B1 at 64 Kb/s ISDN Event: Accepting the call %LINK-3-UPDOWN: Interface BRI1: B-Channel 1, changed state to up TX -> INFOc dsl = 1 sapi = 0 tei = 96 ns = 108 nr = 98 i = 0x0801D807180189 CONNECT dsl = 1 pd = 8 callref = 0xD8 Channel ID i = 0x89 RX <- RRr dsl = 1 sapi = 0 tei = 96 nr = 109 RX <- INFOc dsl = 1 sapi = 0 tei = 96 ns = 98 nr = 109 i = 0x0801580F18018934014F CONNECT_ACK dsl = 1 pd = 8 callref = 0x58 Channel ID i = 0x89 Signal i = 0x4F TX -> RRr dsl = 1 sapi = 0 tei = 96 nr = 99 ISDN Event: incoming ces value = 1 received HOST_CONNECT Channel ID i = 0x0101 ------------------- Channel ID i = 0x89 Signal i = 0x4F ISDN Event: Connected to on B1 at 64 Kb/s %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1: B-Channel 1, changed state to up TX -> RRp dsl = 1 sapi = 0 tei = 105 nr = 17 RX <- RRf dsl = 1 sapi = 0 tei = 105 nr = 1 TX -> RRp dsl = 1 sapi = 0 tei = 96 nr = 99 RX <- RRf dsl = 1 sapi = 0 tei = 96 nr = 109 %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1: B-Channel 1, changed state to down ISDN Event: Hangup call to call id 0x3C on dsl 1, ces = 1 TX -> INFOc dsl = 1 sapi = 0 tei = 96 ns = 109 nr = 99 i = 0x0801D84508028090 DISCONNECT dsl = 1 pd = 8 callref = 0xD8 Cause i = 0x8090 - Normal call clearing RX <- RRr dsl = 1 sapi = 0 tei = 96 nr = 110 RX <- INFOc dsl = 1 sapi = 0 tei = 96 ns = 99 nr = 110 i = 0x0801584D RELEASE dsl = 1 pd = 8 callref = 0x58 TX -> RRr dsl = 1 sapi = 0 tei = 96 nr = 100 ISDN Event: incoming ces value = 1 received HOST_DISCONNECT_ACK %LINK-3-UPDOWN: Interface BRI1: B-Channel 1, changed state to down TX -> INFOc dsl = 1 sapi = 0 tei = 96 ns = 110 nr = 100 i = http://www.cisco.com/warp/public/129/18.html (5 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information 0x0801D85A RELEASE_COMP dsl = 1 pd = 8 callref = 0xD8 ISDN Event: Hangup call to call id 0x3C on dsl 1, ces = 1 CCBRI Mail NULL InPkt public is 0 ccb is 3C53E0 ISDN Event: incoming ces value = 1 received HOST_QUERY_RESPONSE Call State i = 0x00 ------------------- RX <- RRr dsl = 1 sapi = 0 tei = 96 nr = 111 TX -> RRp dsl = 1 sapi = 0 tei = 105 nr = 17 Indication: Call connected, but then disconnected. Suggestions: Turn on debug ppp negotiation and debug ppp chap to see if ppp negotiation and ppp authentication is good. Example 6 Debug: DEBUG ISDN Q921 Kisdn-SCAL# 19:27:31: TX -> IDREQ ri = 19354 ai = 127 dsl = 0 19:27:33: TX -> IDREQ ri = 1339 ai = 127 dsl = 0 19:27:35: TX -> IDREQ ri = 22764 ai = 127 dsl = 0 19:27:37: TX -> IDREQ ri = 59309 ai = 127 dsl = 0 19:27:39: TX -> IDREQ ri = 25214 ai = 127 dsl = 0 19:27:41: TX -> IDREQ ri = 35423 ai = 127 dsl = 0 19:27:43: TX -> IDREQ ri = 12368 ai = 127 dsl = 0 19:27:45: TX -> IDREQ ri = 13649 ai = 127 dsl = 0 19:27:47: TX -> IDREQ ri = 35426 ai = 127 dsl = 0 19:27:49: TX -> IDREQ ri = 12419 ai = 127 dsl = 0 19:27:51: TX -> IDREQ ri = 14516 ai = 127 dsl = 0 19:28:04: TX -> IDREQ ri = 50165 ai = 127 dsl = 0 19:28:06: TX -> IDREQ ri = 838 ai = 127 dsl = 0 19:28:08: TX -> IDREQ ri = 14247 ai = 127 dsl = 0 19:28:34: TX -> IDREQ ri = 45592 ai = 127 dsl = 0 19:28:36: TX -> IDREQ ri = 54169 ai = 127 dsl = 0 19:28:38: TX -> IDREQ ri = 3370 ai = 127 dsl = 0 http://www.cisco.com/warp/public/129/18.html (6 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information 19:29:09: TX -> IDREQ ri = 57291 ai = 127 dsl = 0 19:29:11: TX -> IDREQ ri = 56444 ai = 127 dsl = 0 19:29:13: TX -> IDREQ ri = 42045 ai = 127 dsl = 0 19:29:44: TX -> IDREQ ri = 59406 ai = 127 dsl = 0 19:29:46: TX -> IDREQ ri = 26863 ai = 127 dsl = 0 19:29:48: TX -> IDREQ ri = 63456 ai = 127 dsl = 0 19:30:19: TX -> IDREQ ri = 30177 ai = 127 dsl = 0 19:30:21: TX -> IDREQ ri = 54258 ai = 127 dsl = 0 19:30:23: TX -> IDREQ ri = 4883 ai = 127 dsl = 0 19:30:54: TX -> IDREQ ri = 17476 ai = 127 dsl = 0 19:30:56: TX -> IDREQ ri = 34949 ai = 127 dsl = 0 19:30:58: TX -> IDREQ ri = 4310 ai = 127 dsl = 0 19:31:24: TX -> IDREQ ri = 7735 ai = 127 dsl = 0 19:31:26: TX -> IDREQ ri = 424 ai = 127 dsl = 0 Indication: The router is sending IDREQs to the CO switch, but is not getting a response from the CO switch. Suggestions: Check the following: ● the correct configuration of SPIDs, ● verify the SPIDs with the telco, ● if neccessary, have the telco track the SPIDs. Example 7 Debug: DEBUG ISDN EVENT, DEBUG ISDN Q931 0:05:44: BRI0: ISDN Event: incoming ces value = 1 0:05:44: BRI0: received HOST_PROCEEDING Channel ID i = 0x0101 0:05:44: ------------------- Channel ID i = 0x89 0:05:44: Locking Shift to Codeset 5 0:05:44: Codeset 5 IE 0x2A i = 0x80880B,'12149398003', 0x8001098001148 00114800114 0:05:44: BRI0: RX <- DISCONNECT pd = 8 callref = 0x89 0:05:44: Cause i = 0x82EF - Protocol error, unspecified http://www.cisco.com/warp/public/129/18.html (7 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information 0:05:44: BRI0: ISDN Event: incoming ces value = 1 0:05:44: BRI0: received HOST_DISCONNECT 0:05:44: BRI0: ISDN Event: Call to 12149398003 was hung up. 0:05:44: BRI0: TX -> RELEASE pd = 8 callref = 0x09 0:05:44: BRI0: RX <- RELEASE_COMP pd = 8 callref = 0x89 0:05:44: BRI0: ISDN Event: incoming ces value = 1 0:05:44: BRI0: received HOST_DISCONNECT_ACK 0:05:45: BRI0: ISDN Event: Call to 12149398003 at 56 Kb/s 0:05:46: BRI0: TX -> SETUP pd = 8 callref = 0x0A 0:05:46: Bearer Capability i = 0x8890218F 0:05:46: Channel ID i = 0x83 0:05:46: Called Party Number i = 0x80, '12149398003' 0:05:46: BRI0: RX <- CALL_PROC pd = 8 callref = 0x8A 0:05:46: Channel ID i = 0x89 0:05:46: Locking Shift to Codeset 5 0:05:46: Codeset 5 IE 0x2A i = 0x80880B, '12149398003', 0x8001098001148 00114800114 0:05:46: BRI0: ISDN Event: incoming ces value = 1 0:05:46: BRI0: received HOST_PROCEEDING Channel ID i = 0x0101 0:05:46: ------------------- Channel ID i = 0x89 0:05:46: Locking Shift to Codeset 5 0:05:46: Codeset 5 IE 0x2A i = 0x80880B, '12149398003', 0x8001098001148 00114800114 0:05:46: BRI0: RX <- DISCONNECT pd = 8 callref = 0x8A 0:05:46: Cause i = 0x82EF - Protocol error, unspecified 0:05:46: BRI0: ISDN Event: incoming ces value = 1 0:05:46: BRI0: received HOST_DISCONNECT 0:05:46: BRI0: ISDN Event: Call to 12149398003 was hung up. 0:05:46: BRI0: TX -> RELEASE pd = 8 callref = 0x0A 0:05:46: BRI0: RX <- RELEASE_COMP pd = 8 callref = 0x8A 0:05:46: BRI0: ISDN Event: incoming ces value = 1 0:05:46: BRI0: received HOST_DISCONNECT_ACK 0:05:59: BRI0: RX <- SETUP pd = 8 callref = 0x01 0:05:59: Bearer Capability i = 0x8890 0:05:59: Channel ID i = 0x89 Indication: Switch type or switch type configuration. Suggestions: ● Verify the switch type. http://www.cisco.com/warp/public/129/18.html (8 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information ● Verify the switch type in the configuration. Example 8 Debug: DEBUG ISDN Q931 %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:22, changed state to up ISDN Event: Call to 9086154535 dsl 3 at 64 Kb/s TX -> SETUP dsl = 3 pd = 8 callref = 0x188C Bearer Capability i = 0x8890 Channel ID i = 0xE1808397 Called Party Number i = 0xA1, '9086154535' RX <- RELEASE_COMP dsl = 3 pd = 8 callref = 0x988C Cause i = 0x83E020 - Mandatory IE missing ISDN PRI 3: entering process_rxstate, CALL_CLEARED ISDN PRI 3: received message 1F ISDN Event: Hangup call to call id 0xCE2 on dsl 2 Indication: NSF IE is not sent. Suggestions: See CSCdi46101. Example 9 Debug: DEBUG PPP NEGOTIATION, DEBUG PPP CHAP 3:22:53: ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 3:22:53: ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = C6091F. 3:22:55: ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 3:22:55: ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = C6091F 3:22:55: PPP BRI0: B-Channel 1: received config for type = 0x0 (??) 3:22:55: PPP BRI0: B-Channel 1: rcvd unknown option 0x0 rejected http://www.cisco.com/warp/public/129/18.html (9 of 11) [5/6/2001 3:50:03 PM] Cisco - ISDN Debug Information 3:22:55: PPP BRI0: B-Channel 1: received config for type = 0x1 (MRU) value = 0x5 F4 rejected 3:22:55: PPP BRI0: B-Channel 1: received config for type = 0x3 (AUTHTYPE) value = 0xC223 value = 0x5 acked 3:22:55: PPP BRI0: B-Channel 1: received config for type = 0x11 (MULTILINK_MRRU) rejected 3:22:55: PPP BRI0: B-Channel 1: received config for type = 0x13 (UNKNOWN) 3:22:55: PPP BRI0: B-Channel 1: rcvd unknown option 0x13 rejected 3:22:55: ppp: config REJ received, type = 3 (CI_AUTHTYPE), value = C223/5 3:22:55: ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 3:22:55: ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = C6091F 3:22:55: PPP BRI0: B-Channel 1: received config for type = 0x3 (AUTHTYPE) value = 0xC2. Success rate is 0 percent (0/5) moog#23 value = 0x5 acked 3:22:55: ppp: config REJ received, type = 3 (CI_AUTHTYPE), value = C223/5 3:22:55: ppp: BRI0: B-Channel 1 closing connection because remote won't authenti cate. 3:22:55: ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 3:22:55: ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = C6091F 3:22:55: %ISDN-6-DISCONNECT: Interface BRI0: B-Channel 1 disconnected from 0123 5820040 , call lasted 2 seconds 3:22:56: %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down Indication: The remote device does not authenticate itself. This can be seen usually with non-Cisco devices. Suggestion: Use IOS 10.3(9), 11.0(5), 11.(1) or later. These versions support a new feature for ppp authentication: ● ppp authentication chap callin or ● ppp authentication pap callin Related Information ● Designing ISDN Internetworks ● ISDN Technology Overveiw ● ISDN Switch Types, Codes, and Values http://www.cisco.com/warp/public/129/18.html (10 of 11) [5/6/2001 3:50:03 PM] [...]...Cisco - ISDN Debug Information q q q q Provisioning the ISDN line Access Technologies Support Page Access Dial Top Issues Access Products Support Page All contents are Copyright © 1992 2001 Cisco Systems Inc All rights reserved Important . ISDN EVENT, DEBUG ISDN Q931 ● Example 6: DEBUG ISDN Q921 ● Example 7: DEBUG ISDN EVENT, DEBUG ISDN Q931 ● Example 8: DEBUG ISDN Q931 ● Example 9: DEBUG PPP. Example 1: DEBUG ISDN EVENT ● Example 2: DEBUG ISDN Q931 ● Example 3: DEBUG DIALER ● Example 4: DEBUG PPP CHAP, DEBUG PPP NEGOTIATION ● Example 5: DEBUG ISDN

Ngày đăng: 21/12/2013, 19:15

Tài liệu cùng người dùng

Tài liệu liên quan