Local and Remote Management Console are intended for the graphical representation of network
map, device icons and device views. It accepts the user actions such as mouse clicks, zooming,
key pressings, etc. The Management Console interacts with the SNMP Server via the Remote
Procedure Call (RPC) data in TCP/IP envelope. The Management Console can coexist with the
SNMP-Server on the same PC or work on a separate computer.
Network Elements are copper and fiber modems, converters and other network devices. Network
Elements support the following versions of SNMP protocol:
• V1, is initial version of SNMP protocol
• V2c, is the updated version of SNMP protocol featured bulk requests and long counters
• V3, is the latest version featured authentication and message encryption. Two users are
actually supported.
Depending on the SNMP protocol version, the following SNMP messages are supported:
• for the SNMP V1: GET, GET NEXT, SET, TRAP
• for the SNMP V2c: GET, GET NEXT, GET BULK, SET, TRAP
• for the SNMP V3: READ, WRITE, TRAP
GET and READ messages initialized by the SNMP Server and intended for getting information
from the Network Element.
SET or WRITE message initialized by the SNMP Server and intended for changing the SNMP
variable of the Network Element.
TRAP messages initiated by the Network Element. These messages carry information about
status change of the Network Element. For example, if port goes Down or Up, if the device have
been restarted, or if the alarm appeared, the TRAP message will be send to the direction of the
SNMP Server. Two destinations are supported for TRAP messages.
The following TRAP messages are supported:
• cold Start (RFC-1215)
• authentication Failure (RFC-1215)
• linkUp (RFC-1213-MIB, IF-MIB)
• linkDown (RFC-1213-MIB, IF-MIB)
• dsx1LineStatusChange (DS1-MIB)
• device specific traps (nateks.mib)
• newRoot and topologyChange (RFC-4188, BRIDGE-MIB)
• RMON Event (RMON-MIB)
To Next Page
Loading...
