4. Diagnostics
ROS® v3.11User Guide 89 RMC30
4.1.2. Passive Alarms
Passive alarms are historic in nature. They signify events that represented abnormal conditions
in the past, and do not affect the current operational status. Examples of passive alarms
include authentication failures or error rates that temporarily exceeded a certain threshold.
Passive alarms are cleared through the Clear Alarms option under the diagnostics menu.
RMON generated alarms are passive.
4.1.3. Alarms and the Critical Failure Relay
All active alarms will immediately de-energize the critical fail relay (thus signifying a problem).
The relay will be re-energized when the last outstanding active alarm is cleared.
Alarms are volatile in nature. All alarms (active and passive) are cleared at startup.
4.1.4. Configuring Alarms
ROS® provides a means for selectively configuring alarms in fine-grained detail. Some notes
on alarm configuration in ROS®:
• Alarms at levels CRITICAL or ALERT are not configurable nor can they be disabled.
• The "Level" field is read-only; the preconfigured alarm level is not a configurable option.
• Alarms cannot be added to or deleted from the system.
• Alarm configuration settings changed by a user will be saved in the configuration file.
• The "alarms" CLI command lists all alarms - configurable and non-configurable.
To Next Page
Loading...
Need help?
General