Managing Faults on Avaya Virtual Services Platform 7200 Series and 8000 Series Version 4.2.1

and falling values compare to the actual value of the variable that you choose. If the variable falls
outside of the rising or falling value range, an alarm triggers, and the system logs an event or trap.
When you create an alarm, you also select a sample type, which can be either absolute or delta.
Define absolute alarms for alarms based on the cumulative value of the alarm variable. An example
of an absolute alarm value is card operating status. Because this value is not cumulative, but
instead represents states, such as card up (value 1) and card down (value 2), you configure the
value as the absolute value. Therefore, you can create an alarm with a rising value of 2 and a falling
value of 1 to alert you whether the card is up or down.
Configure most alarm variables related to Ethernet traffic as a delta value. Define delta alarms for
alarms based on the difference in the value of the alarm variable between the start of the polling
period and the end of the polling period. The system samples delta alarms twice for each polling
period. For each sample, the system adds and compares the last two values to the threshold values.
This process increases precision and detects threshold crossings that span the sampling boundary.
Therefore, if you track the current values of a delta-valued alarm and add the current values, the
result is twice the actual value. This result is not an error in the software.
RMON1 history
The RMON1 history group records periodic statistical samples from a network. A sample is a history
and the system gathers the sample in time intervals referred to as buckets.
You can use RMON1 history for the MAC layer in the network. You cannot use RMON1 history for
application and network layer protocols.
You enable and create histories to establish a time-dependent method to gather RMON1 statistics
on a port. The following are the default values for history:
• Buckets are gathered at 30-minute intervals.
• The number of buckets gathered is 50.
You can configure both the time interval and the number of buckets. However, after the system
reaches the last bucket, the system dumps bucket 1 and recycles the bucket to hold a new bucket of
statistics. Then the system dumps bucket 2, and so forth.
RMON1 events
RMON1 events and alarms work together to notify you when values in your network go out of a
specified range. After a value passes the specified range, the alarm fires. The event specifies how
the system records the activity.
You can use RMON1 events for the MAC layer in the network. You cannot use RMON1 events for
application and network layer protocols.
An event specifies whether a trap, a log, or both a trap and a log generates to view alarm activity.
After you globally enable RMON, two default events generate:
• RisingEvent
• FallingEvent
The default events specify that after an alarm goes out of range, both a trap and a log track the firing
of the alarm. For example, after an alarm fires at the rising threshold, the rising event specifies to
send this information to both an SNMP trap to the NMS, and a log on the switch. Likewise, after an
alarm passes the falling threshold, the falling event specifies to send this information to a trap and a
log.
Fault management fundamentals
18 Managing Faults on Avaya VSP 7200 Series and 8000 Series June 2015
Comments on this document? [e-mail]