Cisco Systems 3.6 specifications Impact Report Structure, Affected Severities

Page 52

Chapter 7 Impact Analysis

Impact Report Structure

Note Each fault which has been identified as potentially service affecting triggers a generation of impact analysis calculation event if it is reoccurring in the network.

This chapter describes the automatic impact analysis. For more information about proactive impact analysis, refer to the Cisco Active Network Abstraction NetworkVision User Guide.

Impact Report Structure

The impact report contains a list of pairs of endpoints when the service between them has been affected.

Each endpoint has the following details:

•Endpoint physical or logical location—An endpoint can be a physical entity (for example, a port) or a logical one (for example, a subinterface). The impact report contains the exact location of the entity. All the location identifiers start with the ID of the device which holds the endpoint. The other details in the location identifier are varied according to the endpoint type, for example VC, VP, IP interface.

•Business tag properties—Key, name, type (if attached to the entity).

Note For specific information about the report structure in MPLS networks, refer to the Cisco Active Network Abstraction MPLS User Guide.

Affected Severities

In automatic mode, the affected parties can be marked with one of the following severities:

•Potentially affected—The service might be affected but its actual state is not yet known.

•Real affected—The service is affected.

•Recovered—The service is recovered. This state relates only to entries that were marked previously as potentially affected. It indicates only the fact that there is an alternate route to the service, regardless of the service quality level.

•The initial impact report might mark the services as either potentially or real affected. As time progresses and more information is accumulated from the network, the system might issue additional reports to indicate which of the potentially affected parties are real or recovered.

•The indications for these states are available both through the API and in the GUI.

Note The reported impact severities vary between fault scenarios. For more information about fault scenarios in an MPLS network see the Cisco Active Network Abstraction MPLS User Guide.

Note There is no clear state for the affected services when the alarm is cleared.

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

7-2

OL-14284-01

 

 

Page 51 Page 53
Image 52
Page 51 Page 53
Contents Americas Headquarters Page N T E N T S Multi Route Correlation Cloud VNE Alarm Sending Event Correlator About This Guide ViiViii Fault Management Overview Managing EventsAlarm Basic Concepts and TermsEvent Event SequenceRepeating Event Sequence Flapping EventsCorrelation By Root Cause TicketSeverity Propagation Sequence Association and Root Cause AnalysisEvent Processing Overview OL-14284-01 Fault Detection and Isolation Unreachable Network ElementsVNE Alarm Integrity Sources of Alarms On a DeviceIntegrity Service Fault Detection and Isolation Integrity Service Event Suppression Cisco ANA Event Correlation and SuppressionRoot-Cause Correlation Process Cisco ANARoot-Cause Alarms Correlation FlowsCorrelation by Key Correlation by FlowDC Model Correlation Cache Using WeightsCorrelating TCA Advanced Correlation Scenarios Device Unreachable AlarmConnectivity Test Device Fault Identification Device Unreachable ExampleIP Interface Status Down Alarm IP Interface Failure ScenariosCorrelation of Syslogs and Traps All IP Interfaces Down Alarm IP Interface Failure ExamplesInterface Example 10.200.1.2 General Interface Example ATM Examples Ethernet, Fast Ethernet, Giga Ethernet ExamplesInterface Registry Parameters Ip interface status down ParametersMulti Route Correlation Multi Route Correlation Example11 Multi Route Correlation Example GRE Tunnel Down/Up Alarm Generic Routing Encapsulation GRE Tunnel Down/UpGRE Tunnel Down Correlation Example 14 GRE Tunnel Down Example 1 Single GRE Tunnel15 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 Problem Alarm Cloud Correlation ExampleOL-14284-01 Event and Alarm Configuration Parameters Alarm Type DefinitionRoot Cause Configuration Parameters Event Sub-Type Configuration ParametersGeneral Event Parameters Correlation Configuration Parameters Network Correlation ParametersSystem Correlation Configuration Parameters Flapping Event Definitions ParametersImpact Analysis Impact Analysis OptionsImpact Report Structure Affected SeveritiesImpact Analysis GUI Affected Parties TabViewing a Detailed Report For the Affected Pair Detailed Report For the Affected Pair Disabling Impact Analysis Accumulating Affected PartiesAccumulating the Affected Parties In the Correlation Tree Accumulating the Affected Parties In an AlarmUpdating Affected Severity Over Time OL-14284-01 Supported Service Alarms BGP process up Shut down on a deviceAll 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 Software Function Architecture Figure B-1 Event Correlation Flow VNE levelEvent 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
Top Page Image Contents