Zhone Technologies, Inc. | IMACS Product Book, Version 4 |
The system will switch to the backup clock source upon detection of one of the following conditions in the currently active source:
•CGA Red Alarm.
•CGA Yellow Alarm.
•
•Clock source is placed in loop back mode.
•Clock source is placed in standby mode.
IMACS System Management
When the IMACS’ active CPU runs the IP protocol stack, it provides SNMP and Telnet support for management of local and remote IMACS units as well as provides for routing of IP datagrams to other IMACS systems. The Telnet protocol is a remote terminal protocol that allows any PC or workstation equipped with a TELNET client application to establish terminal sessions with an IMACS.
The Simple Network Management Protocol (SNMP) is a widely adopted industry standard method of providing common network management control. A typical SNMP management architecture involves a Manager, such as Zhone Technologies’ Element Management System (EMS) product and an SNMP Agent, which is responsible for providing device management data to the manager. Agents come in two forms: Embedded and Proxy. Embedded agents run directly on the device being managed, while Proxy agents require an intermediate system to translate from a proprietary messaging format. The IMACS uses Embedded SNMP agents to report management information to the manager.
SNMP is a protocol standard that specifies how management data should be transported between an Agent and a Manager. SNMP MIBs (Management Information Base) specifies what comprises the management data. There are multiple MIBs that address many types of computer and telecommunications equipment. Some of these are defined as standards and are referred to by their RFC (Request For Comment) number. Other MIBs are specific to the device being managed and are referred to as Enterprise MIBs. The IMACS supports the following standard and enterprise MIBs:
•
•DS1 MIB (RFC 1406)
•Alarm MIB (Traps to RFC 1215)
•Cross Connect MIB
•Frame Relay MIB RFC1604
•Frame Relay DTE MIB - RFC 1315
•MCC MIB
•ATM Forum UNI3.0 MIB
•DS3 MIB (RFC 1495)
•AToM MIB (RFC 1595)
Standard MIBs are written to provide management data on a wide number of devices, and in some cases not all of the parameters of a MIB are appropriate for the device being managed. Therefore extensions or omissions may be required in any standards based MIB.
The IMACS offers several methods of transporting the SNMP and Telnet traffic from remote sites to the Network Management.
These methods include transport via:
•PPP or SLIP.
•FDL for T1 ESF mode or E1 National Bit 4.
•B7R Encoded Time Slots 24 (T1) or 31 (E1).
•Nx64 HDLC or FR available on CPU5.
•Frame Relay Management PVC.
•ATM Management PVC.
March 2001 | Page 8 |