Table of Contents
Advertisement
Values
Default
startup-alarm alarm-type — Specifies the alarm that may be sent when this alarm is first created. If the
first sample is greater than or equal to the rising threshold value and startup-alarm is equal to rising or
either, then a single rising threshold crossing event is generated. If the first sample is less than or equal
to the falling threshold value and startup-alarm is equal to falling or either, a single falling threshold
crossing event is generated.
Values
Default
Configuration example:
memory-use-alarm rising-threshold 50000000 falling-threshold 45999999 interval 500 rmon-event-type
both start-alarm either
memory-use-warn
Syntax
memory-use-warn rising-threshold threshold [falling-threshold threshold] interval seconds
[rmon-event-type] [startup-alarm alarm-type]
no memory-use-warn
Context
config>system>thresholds
Description
The memory thresholds are based on monitoring MemoryUsed object. This object contains the amount of
memory currently used by the system. The severity level is Alarm.
The absolute sample type method is used.
The no form of this command removes the configured compact flash threshold warning.
Parameters
rising-threshold threshold — The rising-threshold specifies a threshold for the sampled statistic. When the
current sampled value is greater than or equal to this threshold, and the value at the last sampling
interval was less than this threshold, a single threshold crossing event will be generated. A single
threshold crossing event will also be generated if the first sample taken is greater than or equal to this
threshold and the associated startup-alarm is equal to rising or either.
7950 SR OS Basic System Configuration Guide
log — In the case of log, an entry is made in the RMON-MIB log table for each event
occurrence. This does not create an OS logger entry. The RMON-MIB log table entries
can be viewed using the CLI command.
trap — In the case of trap, a TiMOS logger event is generated. The TiMOS logger utility
then distributes the notification of this event to its configured log destinations which may
be CONSOLE, telnet session , memory log, cflash file, syslog, or SNMP trap destinations
logs.
both — In the case of both, both a entry in the RMON-MIB logTable and a TiMOS logger
event are generated.
none — In the case of none, no action is taken.
both
rising, falling, either
either
System Management
Page 351
Advertisement
Table of Contents
