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
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.### |
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
P2864> isdn dial 1 Start dialing for node<1> ***Call failed, number is Blacklisted ### Hit any key to continue.### |
Zyxel> dev dial 1 $$$ Call is blocked |
- Call exceeded the Call budget, check Menu
24.9.3
P2864> isdn dial 1 Start dialing for node<1> ***Connect time exceeds budget ***startDialing failed ### Hit any key to continue.### |
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
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> |
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 |
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> 102 fe3792 15e PDI1 dialer Dialing chan<1>
phone(last 9-digit):40201 |
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 )
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 |
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:
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.