Basic System Configuration Guide System Management
Edition: 01 3HE 11010 AAAC TQZZA 341
rmon-event-type — specifies the type of notification action to be taken when this event
occurs
Values log — an entry is made in the RMON-MIB log table for each event
occurrence. This does not create a TiMOS logger entry. The RMON-
MIB log table entries can be viewed using the
show>system>thresholds CLI command.
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 — both an entry in the RMON-MIB logTable and a TiMOS
logger event are generated
none — no action is taken
Default both
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, 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 rising, falling, either
Default either
Configuration example:
cflash-cap-warn cf1-B: rising-threshold 2000000 falling-
threshold 1999900 interval 240 rmon-event-type trap start-alarm either
memory-use-alarm
Syntax memory-use-alarm rising-threshold threshold [falling-threshold threshold] interval
seconds [rmon-event-type] [startup-alarm alarm-type]
no memory-use-alarm
Context config>system>thresholds
Description The memory thresholds are based on monitoring the TIMETRA-SYSTEM-MIB
sgiMemoryUsed 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 memory threshold alarm.
To Next Page
Loading...
