Specifications

Section 360-381-202
14
T1 restore to Red Alarm retired 15 Sec. 1 Sec. 1 Sec.
Yellow alarm detected to declared < 1 Sec. < 1 Sec. < 1 Sec.
Yellow alarm not detected to retired < 1 Sec. < 1 Sec. < 1 Sec.
Yellow alarm transmitted during alarm Yes No No
8. NETWORK MANAGEMENT
The 360-80 channel bank can be managed via three different interfaces. Each interface has a slightly different
look and feel however each of them offers similar capabilities. The interfaces available include:
 Craft Interface
 The Network Management System (NMS)
 Network Node Manager (NNM)
8.1 Craft Interface
The craft interface is a menu based ASCII interface that utilizes the RS232 port on the front of the T1-S. This in-
terface utilizes any generic terminal emulation program loaded on a PC or similar equipment to operate. In this
configuration the craft interface can only provision and monitor the 360-80 channel bank it is connected to. Visibil-
ity to other remote or local 360-80 channel banks is not provided.
The craft interface is used to establish the IP address required by the other management interfaces. It is also
used to establish the SNMP community parameters required when using the NNM interface.
A cable adaptor is available to connect between the RJ11 connector on the card front panel and a standard DB-9
connection to a terminal or PC serial port. See the documentation provided with the craft interface for more infor-
mation.
8.2 Network Management System Interface
The NMS interface is a Graphical User Interface (GUI) based software package that is shipped with each unit on
CD-ROM. This interface assumes that the NMS software package is loaded and running on a PC connected to
the same Ethernet network as the T1-S card. Up to 16 local 360-80 channel banks can be provisioned and moni-
toring with the NMS interface. Each local 360-80 can support up to 7 remote 360-80s connected to each local
360-80. To use this interface the IP address for the local T1-S card must be provisioned using the craft interface.
A local 360-80 channel bank is a 360-80 that is connected directly to the same network as the managing PC. A
remote 360-80 channel bank is a 360-80 that is connected to a local 360-80 over a T1 and the T1 has been provi-
sioned for remote control between the local and remote 360-80s. Remote control can utilize either the Embedded
Operations Channel (EOC), if the T1 is utilizing EFS format, or can utilize a timeslot on the T1. This is done
through the optioning of the T1-S card.
For drop and reinsert applications where a remote 360-80 may be connected to another remote 360-80, each
360-80’s T1-S and Secondary T1 card must be optioned for a remote control method between each 360-80. Each
remote 360-80 is identified through an addressing scheme utilizing the NMS address of the local 360-80 and the
Address ID switch setting on the remote T1-S card. See the NMS documentation for more information.
8.3 Network Node Manager Interface
The NNM interface is a Simple Network Management Protocol (SNMP) based interface that utilizes a central
SNMP manager software package. This interface assumes that an SNMP manager is present on the same Ether-
net network as the T1-S card. In order for the SNMP manager to operate correctly, the Management Information
Base (MIB) file included on the CD-ROM that was shipped with the product must be loaded. The NNM interface
allows provisioning and monitoring of as many local 360-80s as can be supported by the Ethernet network. Each
local 360-80 can support up to 7 remote 360-80s connected to each local 360-80. To use this interface the IP ad-
dress and the community information for the T1-S card must be provisioned using the craft interface.
A local 360-80 channel bank is a 360-80 that is connected directly to the same network as the managing PC. A
remote 360-80 channel bank is a 360-80 that is connected to a local 360-80 over a T1 and the T1 has been provi-
sioned for remote control between the local and remote 360-80s. Remote control can either utilize the Embedded