Creating Or Modifying An Alarm Definition - Extreme Networks EPICenter Guide Manual

Concepts and solutions guide
Hide thumbs Also See for EPICenter Guide:
Table of Contents

Advertisement

Getting Started with EPICenter

Creating or Modifying an Alarm Definition

Although EPICenter provides a number of predefined alarms, you may find that you need to modify
those alarm definitions, or even create your own alarms to alert you to specific conditions. For example,
you may decide to modify the predefined SNMP Unreachable alarm to send an email to the network
administrator when a device becomes unreachable (the predefined alarms by default do not take any
actions other than to create an entry in the alarm log). Or, you may decide to create a new alarm that
alerts you when CPU utilization on a device exceeds a threshold (utilization rises above 80%, for
example).
An alarm definition has three parts:
• The basic alarm properties, which include the event-related parameters of the alarm: its name, severity,
the event that will trigger it, and so on.
• The alarm actions, which are functions that the alarm system executes when an alarm occurs, in
addition to logging the alarm event. Alarm actions can include sending e-mail, sounding an audible
alert, running a program or executing a script.
• The alarm scope, which defines the devices that can trigger an alarm.
The following examples show how you configure these three aspects to define an alarm.
Example 1: Modifying a Predefined Alarm to Send a Text Page
Modify the Overheat alarm so that it will page the network administrator at "4083236789@paging.com"
if an overheat condition is detected.
46
EPICenter Concepts and Solutions Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Epicenter 5.0

Table of Contents