Operation Manual

Monitoring ISDN Connections 261

Important

NDS over ISDN Console - Monitoring NDS Traffic

- Load the ISDN Console (ISDNCON.NLM), go to Interfaces and

press <Del> on the barred interface. The threshold value(s) will be

reset and the interface released.

- Reconfigure threshold values in the Expert Configuration of the

barred interface and enter "reinitialize system" at the system

console prompt to bring changes into effect.

Barring interfaces is or course a very drastic measure. Since all WAN

connections over such an interface are cut off and users cannot access

distant networks any more, problems with routine processes and

existing sessions could arise. Therefore, this should be the last meas-

ure you take, and the threshold values should be as high as your

situation allows.

If you want to use the ISDN Connection Monitor, you should make sure that

it is used on all servers/routers in a WAN. If, for example, an interface of an

ISDN-Controller in a router is barred after a timeout expired, an incoming call

will be switched through to the ISDN-Controller by the local exchange and

will only be rejected by the barred interface itself.

Thus, if a remote router is configured to set up ISDN calls automatically, it

will perform endless attempts to set up a call to such a barred interface,

which will result in a high number of charge units within a very short time!

The NDS over ISDN Console monitors NDS traffic on ISDN lines.

NDS traffic can be divided in client-to-server traffic and server-to-

server traffic. Client-to-server traffic is caused when a client performs

a login in the network or executes nwadmin. Server-to-server traffic is

caused by NDS updates and time synchronization.

The NDS over ISDN Console is realized in the form of a NetWare

Loadable Module

(NLM

). To load the NDS over ISDN Console,

enter the following command at the server console prompt:

load ndscon <Enter>

The following screen appears:

MONITORI.PM6 27.05.97, 23:52261