D-Link Co.,_______________________________________________________________________ FAQ
FAQ: 24
1) Put the most restrictive things at the front. This syslog.conf
will get everything from local 0,1,2, no matter what level it is,
and send it to D-Link_log
2) USE TABS!!!! No spaces!
7.
What are the debugging commands for the Router? Can I debug my
problems?
Debugging problems on the Router can be an extremely involved
process. We recommend that you follow the general procedure for
some common problems defined below.
7.a
ISDN initialization failed
Check the error log (menu 24.3.1), and look for ‘ISDN init
failed. code<X>’.
If ‘X’ = 1: This means that the link is not up. A possible
reason is that the ISDN line is not active or not connected to
the Router properly.
If ‘X’ = 2: This refers to a SPID error. Check the SPIDs entered
in menu 2 and try again.
If ‘X’ is any other code, then check the ISDN switch type you
have configured in menu 2, as well as the country code in menu
24.1. If these are correct, then you need to turn on the
protocol analyzer to analyze the ISDN traces. To do this, you
need to be connected to the Router via the RS-232 cable with the
terminal mode set to ANSI. To scroll the screen, you can use the
PgUP and PgDn keys.
Go to CI (menu 24.8)
> isdn ana on
> isdn init
> isdn ana off
> isdn ana disp
7.b
Can’t connect to the Internet/remote node
After you have configured menu 4, go to menu 11 and check which
remote node is used for this ‘(ISP)’, for example, let’s say it
is number 1.
Go to menu 24.4 and select ‘Manual Call’, and select 1 as the
Remote Node. You should be able to see the traces for the
connection setup process.
If you are familiar with the PPP negotiation, you can turn on the
PPP tracing mechanism while you start an outcall to the remote
node in question.
Go to CI (menu 24.8)
> sys trcl cl
> sys trcl sw on
> sys trcp sw on
