Specifications

Reference Guide
5-11
CPU Card TCP/IP Network Management
(Facility Data Link) of an ESF-framed T1 link, the SA4 on an E1 link, a B7R formatted DS0
on a T1 or E1 link, server cards P1-P3 such as MCC, FRS, IPR, nx64 ports C1- C4, 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

or
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 B7R formatted DS0 time slot. On a
point-to-point circuit, a DACSII

is not needed. See Figure 5-5.
Figure 5-5. Typical TCP/IP Network Management System
Using IP addresses, you can communicate directly with the affected system, diagnose the
problem, and dispatch a technician if necessary.
Terminal Server
4Kbps TCP/IP
Single 38.4Kbps
Asynch SLIP Circuit
System #1
FDL Circuits
System #2
System #3
System #4
System #5
System #6
System #7
System #8
DACSII
T1/E1
LAN
Workstations
B
7
R
Up to 8 DS0s
Concentrator
Unit