Comtech EF Data CRS-500, Installation And Operational Manual

Page: 144 / 220

CRS-500 1:N Redundancy System
Revision 4
Ethernet Interface Operation 9–2 MN-CRS-500
9.1.1 Ethernet Management Interface Protocols
The User PC provides access to Ethernet-based management of the CRS-500 1:N Redundancy
System through three separately operated protocols:
•
Simple Network Management Protocol (SNMP). This requires a user-supplied Network
Monitoring System (NMS) and a user-supplied Management Information Base (MIB) File
Browser.
Comtech EF Data recommends use of the Ethernet-based SNMP interface for
advanced users only. All other users are strongly encouraged to use the HTTP
(Web Server) Interface for remote Monitor and Control (M&C) of the unit.
•
Telnet Interface. You may use the serial remote control protocol via this interface. This
requires use of Windows Command-line, or a user-supplied terminal emulation program
such as HyperTerminal.
•
HTTP Interface. This requires a compatible user-supplied web browser such as Internet
Explorer.
9.2 Simple Network Management Protocol (SNMP) Interface
The SNMP is an Internet-standard protocol for managing devices on IP networks. An SNMP-
managed network consists of three key components:
•
The managed device. This includes the CRS-500.
•
The SNMP Agent. This is the software that runs on the CRS-500. The SNMP Agent
supports both SNMPv1 and SNMPv2c .
•
The user-supplied Network Management System (NMS). This is the software that runs
on the manager.
9.2.1 Management Information Base (MIB) Files
MIB files are used for SNMP remote management of a unique device. A MIB file consists of a tree
of nodes called Object Identifiers (OIDs). Each OID provides remote management of a particular
function. These MIB files should be compiled in a user-supplied MIB Browser or SNMP Network
Monitoring System server. In these modem MIB file names, the letter ‘x’ represents the revision of
the file.