Tcp/Ip Network Management; Typical Tcp/Ip Network Management System - Zhone IMACS 8000 User Manual

Running Head

TCP/IP Network Management

7.4 TCP/IP Network Management
This section presents another type of Network Management System (NMS) for diagnosing
and reporting trouble at unsupervised locations. The SNMP and TELNET configuration can
connect using this alternate method. Both formats can use the 4 kbps FDL (Facility Data Link)
of an ESF-framed T1 link, the SA4 on an E1 link, a Nx64 on a T1 or E1 link (see Section 7.5.1
on page 7-47), or the computer port of the Interface card via SLIP or PPP protocol.
If you do not understand the NMS concepts of IP addressing, SNMP, SLIP or PPP, TELNET,
and Ping, please consult with your network administrator before attempting to install or repair
components presented in this section.
If you have a small number of remote units to manage, one of the Network Management
System options is to use a B7R (Bit-7 Redundant) card at the NMS site. Up to eight remote
system units send alarm information on the FDL/SA4 of a T1/E1 link to either a DACSII
eight individual DS0s, and multiplex the contents into a single 38.4 kbps asynchronous circuit
via the SLIP protocol. This data is used by a communication server or terminal server for
routing to a Local Area Network.
If the FDL is used to transmit and receive information, a DACSII or DACSII ISX (3.0 or
higher) is used to convert the FDL/IP information to a full DS0 time slot. On a point-to-point
circuit, a DACSII
System
#1
System
#2
System
#3
System
#4
System
#5
System
#6
System
#7
System
#8
Figure 7-7.Typical TCP/IP Network Management System
7-18

is not needed. See Figure 7-7.
4Kbps TCP/IP
FDL Circuits
T1/E1
DACS II
Up to 8 DS-0s
Single 38.4Kbps
B
Asynch SLIP Circuit
7
R
Concentrator Unit
Model No.
CPU Card

or
Terminal
Server
LAN
Workstations
System Cards