Cisco Systems 3.6 specifications Viewing a Detailed Report For the Affected Pair

Page 54

Chapter 7 Impact Analysis

Impact Analysis GUI

Name—The subinterface (site) name or business tag name of the affected element, if it exists. For more information, refer to the Cisco Active Network Abstraction Managing MPLS User Guide.

Type—The business tag type.

IP Address—If the affected element is an IP interface, the IP address of the subinterface site is displayed. For more information, refer to the Cisco Active Network Abstraction Managing MPLS User Guide.

Highest Affected Severity—The severest affected severity for the affected pair (destination). The same source can be part of multiple pairs, and therefore each pair can have different affected severities. The highest affected severity reflects the highest among these. The affected pair can have one of the following severities:

Potential

Real

Recovered

N/A—From the Links view this indicates not relevant.

When an affected side (a row) is selected in the Source area, the selected element’s related affected pairs are displayed in the Destination area.

The following additional columns are displayed in the Destination area table in the Ticket Properties window:

Affected Severity—The severity of the affected pair as calculated by the client according to the rules defined above.

Alarm Clear State—An indication for each pair of the clear state of the alarm. The following states exist:

Not cleared—There are one or more alarms that have not been cleared for this pair.

Cleared—All the related alarms for this pair have been cleared.

In addition, you can view a detailed report for every affected pair that includes a list of the events that contributed to this affected pair.

Viewing a Detailed Report For the Affected Pair

You can view a detailed report for every affected pair in NetworkVision. The detailed report includes a list of the events that contributed to the affected pair.

For information about how to reach a detailed affected report, refer to the Cisco Active Network Abstraction NetworkVision User Guide.

The Affected Parties Destination Properties dialog box is displayed.

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

7-4

OL-14284-01

 

 

Image 54
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 Sources of Alarms On a Device Alarm IntegrityIntegrity Service Fault Detection and Isolation Integrity Service Event Suppression Cisco ANA Event Correlation and SuppressionRoot-Cause Correlation Process Cisco ANACorrelation by Key Root-Cause AlarmsCorrelation Flows Correlation by FlowUsing Weights DC Model Correlation CacheCorrelating TCA Device Unreachable Alarm Advanced Correlation ScenariosConnectivity 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 BGP Process Down Alarm Mpls Interface Removed AlarmLDP Neighbor Down Alarm OL-14284-01 Correlation Over Unmanaged Segments Cloud VNETypes 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 DefinitionEvent Sub-Type Configuration Parameters Root Cause Configuration ParametersGeneral Event Parameters Correlation Configuration Parameters Network Correlation ParametersSystem Correlation Configuration Parameters Flapping Event Definitions Parameters Impact 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 an Alarm Accumulating the Affected Parties In the Correlation TreeUpdating 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 Rx Dormant Tx DormantLink Over Utilized OL-14284-01 Event and Alarm Correlation Flow Software Function Architecture Figure B-1 Event Correlation Flow VNE levelEvent Correlation Flow Event Creation VNE levelEvent Correlation Alarm Sending Event Correlator Correlation Logic Event CorrelatorPost-Correlation Rule Event Correlator
Related manuals
Manual 4 pages 36.46 Kb