15
Ridgeline Concepts and Solutions Guide
219
To disable an alarm you must modify its alarm definition:
1
Open Alarm Manager, and click the Alarm Definition tab.
2
Click the
Modify
button to open the Modify Alarm Definition window with the selected alarm
definition displayed.
3
Uncheck the
Enabled
checkbox to disable the alarm, then click
OK
.
Note that disabling alarms that are not likely to occur will not have much performance impact. For
example, if you do not use ESRP, the disabling the ESRP State Change alarm is not likely to have an
impact, as those alarms should never occur. However, if you do use ESRP but do not want to know
about state changes, disabling that alarm could have some performance impact.
One way to determine which alarms could be disabled for maximum performance impact is to look at
the alarms that actually do occur within your network. You can use the Alarm Log Browser to show
you which alarms occur in your network:
1
In the Alarm Log Browser, filter the alarm list to show all alarms. You can filter the log using
“Log ID > 0”
as the filter criterion to show all alarm log entries.
2
Sort the alarm list by the Name column. This groups all occurrences of a given alarm together. Using
this list you can see both which alarms occur in your network, and the volume of alarms generated
for each type of event.
3
If this list shows large number of alarm instances for an alarm that you don’t care about, disabling
that alarm could potentially have a beneficial impact on Ridgeline system performance.
Another possibility is that a specific device is generating a large number of alarms. If this is the case,
you may be able to eliminate some of this load by either reconfiguring, maintaining or repairing the
device to eliminate the fault, or by changing the scope of one or more alarms to remove the problematic
device from the alarm scope. By removing a device from the alarm scope, Ridgeline will ignore traps for
the device, and will not trigger an alarm even though the device itself may still generate those trap
events.
Limiting the Scope of Alarms
One way to potentially reduce the load created by alarm processing is to use the Alarm scope to limit
an Alarm to only selected devices. For example, you may want to create link down and link up alarms
to monitor the status of certain critical links in your network, but ignore such events on non-critical
links.
When you create an alarm, the default scope is to all devices and all ports. The
Scope
tab of the Add
Alarm Definition or Modify Alarm Definition dialogs lets you specify a scope for the alarm (
Figure 167
).
Содержание Ridgeline 3.0
Страница 14: ...Related Publications Ridgeline Concepts and Solutions Guide 12 ...
Страница 26: ...Ridgeline Overview Ridgeline Concepts and Solutions Guide 24 ...
Страница 52: ...Getting Started with Ridgeline Ridgeline Concepts and Solutions Guide 50 ...
Страница 78: ...Using Map Views Ridgeline Concepts and Solutions Guide 76 ...
Страница 88: ...Provisioning Network Resources Ridgeline Concepts and Solutions Guide 86 ...
Страница 103: ...6 Ridgeline Concepts and Solutions Guide 101 Figure 63 E Line Service Details Window ...
Страница 104: ...Managing Ethernet Services Ridgeline Concepts and Solutions Guide 102 ...
Страница 113: ...7 Ridgeline Concepts and Solutions Guide 111 Figure 72 Importing E Line Service Dialog with Validation Errors ...
Страница 114: ...Importing Services Ridgeline Concepts and Solutions Guide 112 ...
Страница 132: ...Managing and Monitoring VPLS Domains Ridgeline Concepts and Solutions Guide 130 ...
Страница 146: ...Managing VLANs Ridgeline Concepts and Solutions Guide 144 ...
Страница 190: ...Managing Your EAPS Configuration Ridgeline Concepts and Solutions Guide 188 ...
Страница 202: ...Managing Network Security Ridgeline Concepts and Solutions Guide 200 ...
Страница 350: ...Book Title Ridgeline Concepts and Solutions Guide 348 ...
Страница 372: ...Book Title Ridgeline Concepts and Solutions Guide 370 ...