Configuring Events and Alarms

Jayashree Arunkumar

ca.com
Event Sources

pmd
ipmap Event
netmon
Processing

ovtrapd
snmp UDP ovtopmd
Collect port 162

SNMP SNMP
agent agent

Managed Node Managed Node

Slide I - 2 ca.com
Event Processing

Alarm Config A
NNM Processes Categorize as Error Alarm
raise a sound alarm

Alarm Config B
Incoming ovtrapd pmd Categorize as Threshold Alarm
trap
pop-up window with xyz message

Alarm Config C
Event Send email to Y
Binary Event Correlation
Store System

Slide I - 3 ca.com
Event Envelope and Data

 Event envelope
– Enterprise event ID
– Generic event ID
– Specific event ID
– IP address of node which generated event
 Event contents
– Event variables containing specific
information about the event

Slide I - 4 ca.com
Event Envelope

 Enterprise event ID
– .1.3.6.1.4.1.11.2.17.1 – for events sent by
OpenView entity
– .1.3.6.1.2.1.16 – for events sent by RMON
monitoring unit
– .1.3.6.1.6.3.1.1.5 – for SNMP trap events is the
sysobjID of the node with SNMP agent
 Specific event ID
– Enterprise specific events have their own
definitions indicated by this ID

Slide I - 5 ca.com
Event Envelope

 Generic event ID – tells ovtrapd which

standard SNMP trap was generated
SNMPv1 SNMPv2 Generic Trap Name

0 1 Cold Start trap

1 2 Warm Start trap
2 3 Link Down trap
3 4 Link Up trap
4 5 Authentication failure
5 6 EGP Neighbor loss
6 0 Enterprise specific trap

Slide I - 6 ca.com
Event Configuration Overview

 Edit  Events  Modify

 Configure events to
– customize event notification messages
– define the type of event notification
– define automatic actions for events
– configure new event categories
– configure additional actions that operator
might take while using the browser

Slide I - 7 ca.com
Event Configuration

Slide I - 8 ca.com
Configuring commands for Automatic Actions

 ovactiond responsible for executing

automatic actions
 Commands or scripts must be listed
under the directory
\install_dir\conf\trustedCmds.conf
 ALLOW_ALL file disables this feature

Slide I - 9 ca.com
Creating a new event configuration

 MIB for the specific event must be

loaded
 Enterprise specific traps must be known
 Copy an existing event configuration
and modify it
 eg: OV_IF_Down

Slide I - 10 ca.com
Alarm Categories

 Standard alarm categories

– Error
– Threshold
– Status
– Configuration
– Application alert
– All
 Custom alarm categories

Slide I - 11 ca.com
Testing Event Configuration

 To verify that alarms and actions occur

as planned
– ovevent – sends an NNM-formatted event
to pmd
 ovevent node .1.3.6.1.4.1.11.2.17.1.0.58916867
– snmptrap – sends an SNMP trap to
ovtrapd
– snmpnotify – sends an SNMP trap or
inform request to ovtrapd

Slide I - 12 ca.com
Configuring Alarms to launch Dynamic Views

 To configure an alarm to give easy

access to specific view from the Alarm
Browser
– edit \install_dir\conf\C\xnmeventsExt.conf
– new menu item appears in the Alarms
Browser Actions  Views menu
– Item is activated when you select the
specified alarm

Slide I - 13 ca.com
Configuring Additional Actions

 Instead of automatic execution,

operator can select these additional
actions from the Alarm Browser
 Additional actions executed by
xnmevents
 Complete path to the command must
be specified, otherwise xnmevents
cannot find the command to execute

Slide I - 14 ca.com
Event Correlation

Slide I - 15 ca.com
Event Correlation Circuits

Slide I - 16 ca.com