Cisco Systems 3.6 Correlation Configuration Parameters, Network Correlation Parameters

Page 49

Chapter 6 Event and Alarm Configuration Parameters

Event (Sub-Type) Configuration Parameters

Name

Description

Permitted Values

 

 

 

select-root-cause-method

Used to determine the most fitting alarm

Select the class name

 

from the set of possible root causes sets.

to be used from the

 

This set may be a result of a correlation flow

set of classes

 

or may represent all alarms in the local

 

 

Event Correlator component having a

 

 

correlation key that matches one of the

 

 

EventData object correlation keys.

 

 

 

 

correlation-filters

Used to define a set of filters that will

Select the class name

 

remove, from the potential set of alarms,

to be used from the

 

unnecessary root causes. For example,

set of classes

 

remove from the list all the root causes that

 

 

have a weight lower than the event that

 

 

wants to correlate.

 

 

 

 

post-correlation-

Used to define a set of applications that will

Select the class name

applications

be invoked after the event was correlated.

to be used from the

 

For example, running affected is such an

set of classes

 

application.

 

 

 

 

For more information about root cause see Correlation By Root Cause, page 1-5.

Correlation Configuration Parameters

These parameters define the behavior of the alarm in finding its root-cause alarm:

Name

Description

Permitted values

 

 

 

correlate

Determines whether the alarm should attempt to

True or false

 

find and correlate to a root-cause alarm. If this

 

 

parameter is set to true at least box level

 

 

correlation will be performed.

 

 

 

 

Network Correlation Parameters

These parameters control the alarm’s behavior in initiating an active correlation-search flow:

Name

Description

Permitted values

 

 

 

activate-flow

Determines whether to initiate network level

True or false

 

correlation.

 

 

 

 

weight

Defines the weight of an alarm as a correlation

Positive integer

 

candidate. The heavier the alarm, the more

 

 

likely it will be chosen as the root cause.

 

 

 

 

Note All delays should be smaller than the expiration time to allow correlation to take place. Flow activation delay is being counted only when the correlation delay has expired.

Cisco Active Network Abstraction Fault Management User Guide, Version 3.6 Service Pack 1

 

OL-14284-01

6-3

 

 

 

Image 49
Contents Americas Headquarters Page N T E N T S Multi Route Correlation Cloud VNE Alarm Sending Event Correlator Vii About This GuideViii Managing Events Fault Management OverviewBasic Concepts and Terms AlarmEvent Sequence EventFlapping Events Repeating Event SequenceTicket Correlation By Root CauseSequence Association and Root Cause Analysis Severity PropagationEvent Processing Overview OL-14284-01 Unreachable Network Elements Fault Detection and IsolationVNE Alarm Integrity Sources of Alarms On a DeviceIntegrity Service Fault Detection and Isolation Integrity Service Cisco ANA Event Correlation and Suppression Event SuppressionCisco ANA Root-Cause Correlation ProcessCorrelation Flows Root-Cause AlarmsCorrelation by Key Correlation by FlowDC Model Correlation Cache Using WeightsCorrelating TCA Advanced Correlation Scenarios Device Unreachable AlarmConnectivity Test Device Unreachable Example Device Fault IdentificationIP Interface Failure Scenarios IP Interface Status Down AlarmCorrelation of Syslogs and Traps IP Interface Failure Examples All IP Interfaces Down AlarmInterface Example 10.200.1.2 General Interface Example Ethernet, Fast Ethernet, Giga Ethernet Examples ATM ExamplesIp interface status down Parameters Interface Registry ParametersMulti Route Correlation Example Multi Route Correlation11 Multi Route Correlation Example Generic Routing Encapsulation GRE Tunnel Down/Up GRE Tunnel Down/Up Alarm14 GRE Tunnel Down Example 1 Single GRE Tunnel GRE Tunnel Down Correlation Example15 GRE Tunnel Down Example 2 Multiple GRE Tunnels 16 Alarms Correlation to GRE Tunnel Down Ticket Mpls Interface Removed Alarm BGP Process Down AlarmLDP Neighbor Down Alarm OL-14284-01 Cloud VNE Correlation Over Unmanaged SegmentsTypes of Unmanaged Networks Supported Supported When Logical Inventory Physical Inventory Cloud Correlation Example Cloud Problem Alarm OL-14284-01 Alarm Type Definition Event and Alarm Configuration ParametersRoot Cause Configuration Parameters Event Sub-Type Configuration ParametersGeneral Event Parameters Network Correlation Parameters Correlation Configuration ParametersFlapping Event Definitions Parameters System Correlation Configuration ParametersImpact Analysis Options Impact AnalysisAffected Severities Impact Report StructureAffected Parties Tab Impact Analysis GUIViewing a Detailed Report For the Affected Pair Detailed Report For the Affected Pair Accumulating Affected Parties Disabling Impact AnalysisAccumulating the Affected Parties In the Correlation Tree Accumulating the Affected Parties In an AlarmUpdating Affected Severity Over Time OL-14284-01 BGP process up Shut down on a device Supported Service AlarmsAll ip interfaces Sent when all IP interfaces True Warnin Shelf Out Tx Dormant Rx DormantLink Over Utilized OL-14284-01 Event and Alarm Correlation Flow Figure B-1 Event Correlation Flow VNE level Software Function ArchitectureEvent Creation VNE level Event Correlation FlowEvent Correlation Correlation Logic Event Correlator Alarm Sending Event CorrelatorPost-Correlation Rule Event Correlator
Related manuals
Manual 4 pages 36.46 Kb