You are on page 1of 21


Infrastructure Events and Alerts

Event Management and Correlation
Event Rules Condition Correlation Event Procedures Event Integration South-Bound-GW

Event Notifications

SSA 3.0: Service AND Event/Alert Umbrella

Infrastructure Events and Alerts

An alarm is a SPECTRUM object that indicates that a user-actionable. Can be created also manually through Event Configuration Editor. Typically. SPECTRUM generates an alarm when an event specifies that one should be created. imported via MIB Tools or created by editing the Event Configuration Files. SPECTRUM can also generate an alarm based on the results of a SpectroWATCH violation. abnormal condition exists in a model. or as a result of SPECTRUM detecting an abnormal situation not based on an event (inference handler based).  Alarms . .What is an Event versus an Alarm?  Events An event is a SPECTRUM object that indicates that something significant has occurred within SPECTRUM itself or within the managed environment.

Events in Spectrum Oneclick .

Alarms in Spectrum Oneclick ECE .

 The dynamic alarm title attribute can be populated with an Event Variable.  PCause files are static. See Event Configuration User Guide. event variables information.Alarms information in Spectrum Oneclick  PCause code is specified for each alarm that displays the Probable Cause information for an alarm.pdf . The dynamic varbind ID is 76620 (or 0x12b4c).  PCause files control what is displayed in the Probable Cause information. This allows for a single Probable cause to have a dynamic alarm title.

1. PROBABLE CAUSES: 1) A Trap from the firewall system was send 2) Firewall System has to high system usage RECOMMENDED ACTIONS: 1) Check the Event Message in the SPECTRUM Alarm Manager 2) Inform the Firewall Administrator 3) Check the thresholds on the Firewall System --------------------------------------------- .11.1.U -----------------------------------------File: CsEvFormat/00561001 > Event Message Content: {d "%w.0x00561001.(event [{e}]) --------------------------------------------File: CsPCause/Prob00561001 > Alarm Message Content: FIREWALL STATUS ALARM SYMPTOMS: A Firewall System status is over the treshold.6.4. Event Message is: {S 101}.%T"} .1.Device {m} of type {t} generated.1.%d %m-.0(101.2620. -------------------------------------------File: EventDisp > Maps Event to Alarm 0x00561001 Content: 0x00561001 E 50 A 0x561001 1.6.Example: Trap Forwarding of external Managers and Event/Alarming in SPECTRUM Example: Checkpoint FW Manager File AlertMap > Maps Trap to Event 00561001 SS/CsVendor/<customer>_Checkpoint Content: 1.6.2620. %Y .1.1.

Event Management and Correlation .

 Alarm Filtering  from alarm console. .Spectrum Event Correlation  Fault Suppression  Downstream device fault suppression (including VPM)  Child (Port/Process) suppression  Port flapping  Other default EventRules based Correlations  Alarm De-duplication  Recurring events for the same field of the existing alarm. Secondary alarms are just those with a lesser severity.

Event Procedures Complex expressions that allow for events to be manipulated at a very granular level. 2. including creating new event variables and asserting events on models other than the source (between different models(types)). 4. Simple Event Configuration updates This includes specifying which events generate/clear alarms and event variables to discriminate. event and alarm descriptions can be modified and enriched. Events (or the be inferred. They are listed below: 1. 5. In addition. 3.Extending Event Correlation  There are a number of ways that SPECTRUM Event Correlation capabilities can be updated and enhanced. You can also influence the automatic Faultisoltion Event and Alarming behavior . Condition Correlation Condition correlation allows for multiple events to be correlated across groups of models. Event Rules Event rules allow for events to be correlated on individual models (of the same modeltype).

pdf . Settings in Component Details view of the VNM model See also for example Modeling and Managing Your IT Infrastructure Administrator Guide. 2.Inductive Modeling Technology Setting Fault Isolation Parameters 1.

 Event rules allow you to correlate multiple events on the same model. not to groups of models.  Event Rules available:  Event Condition  Event Pair  Event Rate  Event Series  Event Counter  Hearbeat  Single Event  Solo Event .Event Rules  Event Rules permit you to specify a more INTELLIGENT decision-making to indicate how an event is to be processed.

"regexp({v 1}. "0xfffffffa 1:1.1 (SPM-Test name) starts with AUA .EventCondition.Examples: Event Pair & Event Condition GUI ConditionEventRule for SPM Tests: Generate event(alarm) 0xfffffffa only.9 0x0456000b E 20 R Aprisma. if var.9:9" EventDisp File . and deliver Var 1.2:2.3:3.2.{S \ \*\"})".3.

Example: SPECTRUM Condition Correlation Editor LSP Alarms generate one MPLS Backbone Error Alarm Create Condition: left side (eg Error Backbone Error (type: counts) these but show as symptomes .

\ CreateEventWithAttributes( \ { V portModel }. d. wird ein neuer Event auf ihm generiert (0xbeecc002). führe folgende Procedure aus ( Johannes Kroupa .h. \ GetEventVariable( { U 1 } )). Dann Check. Falls der Port nichts matched.B. CA) # Ziel: wenn dieser SPM-Event/Alarm auf dem Device erzeugt wird. \ ReadAttribute( \ { C CURRENT_MODEL }. \ { H 0x129fa } )). mit denselben Varbinds wie der ursprüngliche Event. \ { V dummyRetValue }. alle Ports (und Apps. um den richtigen Port zu finden. . (z. \ Nil()))" Die Proc findet zuerst mal alle Modelle (GetModelsByAttrValue). wird auch nichts gemacht (Nil()). \ { H 0xbeecc002 }. falls der Port matched (hier z. \ { H 0x11348 } ). dann soll auch ein Event/Alarm auf dem entsprechenden Port erzeugt und ausgewertet werden 0xbeecc001 E 50 P " \ ForEach( \ GetModelsByAttrValue( \ { H 0x10069 }. in der Schleife behandelt). hier dann IP Adresse) Dann. ob ifIndex (0x11348) am Port derselbe ist wie Varbind 1 im Event. \ If( \ Equals( \ ReadAttribute( \ { V portMh }. \ GetEventAttributeList()). ifIndex).. \ { V portMh }.Example: Event Procedures (in EventDisp Files) # wenn Event beecc001 erzeugt wird.) des Devices.B. \ { U 0 }.

CA Event Integration (EI) .Architecture .


Southbound Gateway Non-SNMP.24 and others Events and Traps from different Sources For example Logfiles. Element Managers via XML. SNMP and CORBA etc. V. LogFiles (SYSLOGs !). Vendor Specific EMS via Trap Vendor Specific EMS via XML double click . Traps. DBs .

Event Notification .

alarm-processing applications and SANM (Policy Manager) work together in the alarm monitoring process.Alarm Notification CA Spectrum. .

thank you .