METRObility Optical Systems 8100 - Manual (Page 10)

10 CenturyStack 8100 Managed Hub
period, and other parameters. Once samples are taken, the data is stored as
an entry in a media-specific table. Each entry defines one sample, and is
associated with the history Control Entry that caused the sample to be
taken. Each counter in the ether History Entry counts the same event as its
similarly named counterpart in the Ether Stats Entry, except that each
value here is a cumulative sum during a sampling period.
The user can create up to 16 History Control Entries.
RMON Alarm Group
RMON Alarm Group is used to define a set of thresholds for network
performance. Managed CenturyStack RMON Management enables users
to set up Alarm Groups. The Alarm Group periodically takes statistical
samples from variables in the probe and compares them to thresholds that
have been configured. The alarm table stores configuration entries that
define a variable, polling period, and threshold parameters. If a sample is
found to cross the threshold values, an event is generated. This function
generates one event as a threshold and is crossed in the appropriate
direction. No more events are generated for that threshold until the
opposite threshold is crossed.
Managed CenturyStack provides the threshold control function to support
the RMON Alarm Group. Up to 16 Alarm Control Entries can be created.
The syntax and semantic checking is performed to verify the value input
by the user before it can be set to the object of the Alarm Group. The valid
Alarm Group configuration data is saved into the system NVRAM.
Managed CenturyStack periodically monitors the threshold value of
counter objects that have been specified as the RMON Alarm Variable.
The associated RMON event is raised and the proper event action is
performed when the value of counter object crosses its threshold value as
specified in the RMON Alarm Threshold object.
RMON Event Group
RMON Event Group supports the definition of events. An event is
triggered by a condition located in the MIB, and an event can trigger an
action defined elsewhere in the MIB. An event may also cause informa-
tion to be logged in this group and may cause an SNMP trap message to