Troubleshooting -Remote Node/Dial-in User Connection

Related SMT screens and CI commands:

- SMT Menu 2
- SMT Menu 24.4.12
- SMT Menu 24.9

- isdn dial # (pre-ZyNOS) or dev dial # (ZyNOS)
- sys log disp

Cannot outcall to a Remote node

Use CI "isdn dial <node#>" to verify a outgoing call for a remote node. Use CI 'system event' an incoming call from a remote node.

The following are some possible failure reasons for a outgoing call:

- Dial failed ( please refer to previous chapter for more details. )
- ISDN protocol mismatched ( please refer to previous chapter for more details. )
- Incoming only remote node, check Menu 11

- Pre-ZyNOS:

`P2864> isdn dial 1` `* Dial not allowed, or No Channel ( Call to a incoming only remote node, or no free B chan )` `### Hit any key to continue.###`

- ZyNOS:

`Zyxel> dev dial 1` `### Hit any key to continue.### (hit any key)` `Dial Fail ***(null)` `Zyxel> sys log disp` `Zyxel> PP09 ERROR netMakeChannDial: err=-3001 rn_p=575de0` `(here 3001 means call out not allowed)`

Some common troubleshooting examples:

- Phone number is in Black List, check Menu 24.9.2
- Call exceeded the Call budget, check Menu 24.9.3
- Login to remote node failed, check the name and password again
- PPP negotiation failed
- IP address mismatched

- Phone number is in Black List, check Menu 24.9.2

- Pre-ZyNOS:

`P2864> isdn dial 1` `Start dialing for node<1>` `***Call failed, number is Blacklisted` `### Hit any key to continue.###`

- ZyNOS:

`Zyxel> dev dial 1` `$$$ Call is blocked`

- Call exceeded the Call budget, check Menu 24.9.3

- Pre-ZyNOS:

`P2864> isdn dial 1` `Start dialing for node<1>` `***Connect time exceeds budget` `***startDialing failed` `### Hit any key to continue.###`

- ZyNOS:

`Zyxel> dev dial 1` `Dial no budget` `Zyxel> sys log disp` `PP09 INFO Remote node 0 budget expired` `PP09 INFO Dial no budget`

- Login to remote node failed, check the name and password again

- Pre-ZyNOS:

`P2864> 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` `***Login to remote failed. Check name/passwd.` `Receive Terminate REQ` `LCP down` `Line Down chan<1>`

- ZyNOS:

`zyxel> dev dial 1` `Start dialing for node<1>` `Dialing chan<1> phone(last 9-digit):40201### Hit any key to continue.###` `Call CONNECT speed<64000> type<2> chan<0>` `LCP opened` `CHAP login to remote failed` `LCP closed` `Recv'd TERM-REQ` `Recv'd TERM-ACK state 5` `LCP stopped`

- PPP negotiation failed

`306Z> isdn dial 1 or dev 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` `CHAP send response` `CHAP login to remote OK!`

In the above case, the IPCP negotiation has started, but there is no 'IPCP up' message. This means that the IP negotiation failed, and even though the line is up, you can't ping from one end to the other. To identify the problem you must collect the PPP negotiation trace . Following are the steps to collect PPP negotiation packets. ( You can use these steps to collect traces for all PPP related problems . )

`P128> sys trcl cl` `Program Trace Switch OFF` `P128> sys trcl sw on` `P128> sys trcp sw on` `P128> isdn dial 1 or dev 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` `P128> 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` `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`

From the packet trace above, one can tell why the IPCP protocol was rejected by the far end. Please refer to PPP training material for more details. ( RFC 1661 )

- IP address mismatched

- Pre-ZyNOS:

`P128> isdn dial 4` `Start dialing for node<4>` `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` `IPCP up` `***Remote subnet mismatch, cfg'd 100.0.0.0` `***Remote subnet mismatch, neg'd 200.0.0.0` `LCP down` `IPCP down` `***Ip route: code=05 P1=00 P2=00 P3=00` `Receive Terminate ACK` `LCP stopped`

- ZyNOS:

`P128> dev dial 4` `Start dialing for node<4>` `Dialing chan<1> phone(last 9-digit):40201### Hit any key to continue.###` `Call CONNECT speed<64000> type<2> chan<0>` `LCP opened` `CHAP login to remote OK!` `IPCP negotiation started` `BACP negotiation started` `IPCP up` `LCP closed` `IPCP closed` `Recv'd TERM-ACK state 4` `LCP stopped` `P128> sys log disp` `18 417888 PP0a ERROR Remote subnet mismatch, cfg'd 100.1.1.1` `19 417889 PP0a ERROR neg'd 200.0.0.0` `20 417892 PP0a WARN ip_route: code=05 P1=00 P2=00 P3=00`

In this example, the IP address of the remote node is 100.1.1.1, but after PPP is up, the far-end claims that their IP is in 200.0.0.0 network. Prestige will drop the call, becuase of the IP address mismatch in this case.

Cannot answer incoming call from a Remote node or Dial-in User

The following are some of the possible reasons the Prestige not answering an incoming call:

- System can't answer call
- ISDN protocol mismatched
- System authentication not set correctly
- Far-end name/password not correct
- IP address mismatched

To collect the trace or to identify the problem, just use 'sys event' command in CI and wait for an incoming call. If it is a PPP related problem, then use the following steps to collect PPP trace:

1. sys trcl cl
2. sys trcl sw on
3. sys trcp sw on
4. <Wait for an incoming call ( or issue 'sys event' ), after the call stops >
5. sys trcl sw off
6. sys trcp sw off
7. sys trcl disp

Cannot callback to a Dial-in User

The Prestige only supports Microsoft's proprietary CallBack Control Protocol (CBCP). Thus, the Prestige will be able to do PPP callback to only to those devices that also support CBCP. This means that if a dial-in user is using a different package such as Trumpet which doesn't support CBCP, then the Prestige will not callback to the user.

All contents copyright © 1999 ZyXEL Communications Corporation.