Performance Management on Virtual Services Platform 4000 Series Version 5.1.2

Table Of Contents
For information about SFPs, SFP+s and QSFPs see Installing Transceivers and Optical
components on VSP Operating System Software, NN47227-301.
Remote Monitoring
This section provides information on Remote Monitoring (RMON).
RMON has two versions:
RMON1
RMON2
Remote Monitoring
Remote Monitoring (RMON) is a management information base (MIB) or a group of management
objects that you use to obtain or configure values using the Simple Network Management Protocol
(SNMP). Use ACLI, or EDM, to globally enable RMON on the system. After you globally enable
RMON, you enable monitoring for individual devices on a port-by-port basis.
RMON1 is the original version of the protocol, which collects information for OSI Layer 1 and Layer
2 in Ethernet networks. RMON1 provides traffic statistics at the MAC layer, and provides statistics
on Ethernet segments for packets and bytes received and transmitted.
You can use RMON1 to:
Configure alarms for user-defined events.
Collect Ethernet statistics.
Log events.
Send traps for events.
Within EDM, you can configure RMON1 alarms that relate to specific events or variables. You can
also specify events associated with alarms to trap or log-and-trap. In turn, the system traps or logs
tripped alarms.
You can view all RMON1 information using ACLI or EDM. Alternatively, you can use any
management application that supports SNMP traps to view RMON1 trap information.
This section describes RMON1 alarms, RMON1 history, RMON1 events, and RMON1 statistics.
RMON1 alarms
You can configure alarms to alert you if the value of a variable goes out of range. You can define
RMON1 alarms on any MIB variable that resolves to an integer value. You cannot use string
variables (such as system description) as alarm variables.
You can use RMON1 alarm to monitor anything that has a MIB OID associated with it and a valid
instance.
Performance management fundamentals
January 2017 Performance Management on Avaya VSP 4000 Series 16
Comments on this document? infodev@avaya.com