RingMaster Management Guide - Juniper Networks

Managing Alarms
❍ Performance
❍ Security
❍ System
❑ Faults are assigned one of several severities:
❍ Critical (Red)
❍ Info (Blue)
❍ Major (Orange)
❍ Minor (Yellow)
❑ Source information (MX, RingMaster) for a fault is provided.
❑ For each fault, you are provided information such as cause, fault object and event history.
❑ Overall status (consolidation of operational status and fault severity) is propagated to the
appropriate physical or logical entity in the Monitoring view.
❑ You can sort faults based on any of the displayed columns. When faults are sorted on time/date
of occurrence they are organized as Today, Yesterday.
❑ Filtering based on Category, Severity, and Type is available.
❑ Provides text search capability
In this view, there are Tasks panel items including the following:
❍View
◆Setup
◆Query
❍Manage
◆Acknowledge
◆Unacknowledge
◆Delete Active
◆Delete Cleared
❍Reports
◆Alarm Summary
◆Alarm History
Fault Management
❑ Each fault has an associated state — active, acknowledged, cleared).
❑ You can perform tasks such as Acknowledge, UnAcknowledge Delete Active and
Delete Cleared to manage faults.
❑ For some faults, there is a pre-determined task list to guide you on tasks/resolutions that can
be performed on a fault.
❑ If the RingMaster Server restarts after being down for a prolonged period of time, say 1 hour,
all faults are cleared on restart since we can no longer guarantee if these faults are valid.
❑ If a fault has already been cleared or acknowledged and a new event occurs which can be
correlated to this fault, this fault is made active again
❑ Whenever the state of a fault is changed — from active to acknowledge etc — the last update
time is updated
❑ You can multi-select faults and perform any fault management operations.
❑ RFDetect and Status summary subsystems generate relevant events which are displayed as a
fault.
Fault Storage and History
❑ Fault information is stored on the server so multiple clients can access it.
❑ For each fault, all correlated traps/events are stored.
❑ Active fault information and fault information history are maintained by the server (in the
database)
Copyright © 2011, Juniper Networks, Inc. Managing Alarms 131