Cisco Systems 3.6 specifications Rx Dormant, Tx Dormant, Link Over Utilized

Page 63

Appendix A Supported Service Alarms

Rx Dormant

Rx Dormant

An Rx Dormant alarm is issued when the traffic received over a physical port (measured as a percentage of the port’s capacity) drops below a predefined threshold. The alarm description includes the current traffic percentage compared with the defined threshold. This alarm provides service providers with a method for identifying customer services that have slowed down significantly or stopped altogether. An Rx Dormant Normal alarm is issued after the traffic percentage exceeds a predefined upper threshold. By default, the Rx Dormant alarm is disabled. This alarm is enabled and its thresholds are configured using the Cisco ANA Registry Editor.

Note Changes to the registry should be carried out only with the support of Cisco Professional Services.

Tx Dormant

A Tx Dormant alarm is issued when the traffic transmitted over a physical port (measured as a percentage of the port’s capacity) drops below a predefined threshold. The alarm description includes the current traffic percentage compared with the defined threshold. This alarm provides service providers with a method for identifying customer services that have slowed down significantly or stopped altogether. A Tx Dormant Normal alarm is issued after the traffic percentage exceeds a predefined upper threshold. By default, the Tx Dormant alarm is disabled. This alarm is enabled and its thresholds are configured using the Cisco ANA Registry Editor.

Link Over Utilized

A link over utilized alarm is issued when the traffic transmitted over a port that is connected to another port via a network link (measured as a percentage of the port’s capacity) exceeds a predefined threshold. The port over utilization alarm is correlated into a link over utilized alarm. If the ports at both ends of a link are overutilized, the two port over utilization alarms are correlated into a single link over utilization alarm. The alarm description includes the direction of the overutilization. A link utilization normal alarm is issued when the utilization level falls below a predefined threshold. The overutilization thresholds are configured using the Cisco ANA Registry Editor.

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

	OL-14284-01	A-5

Image 63

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 Sources of Alarms On a Device Alarm IntegrityIntegrity Service Fault Detection and Isolation Integrity Service Cisco ANA Event Correlation and Suppression Event SuppressionCisco ANA Root-Cause Correlation ProcessCorrelation by Flow Root-Cause AlarmsCorrelation Flows Correlation by KeyUsing Weights DC Model Correlation CacheCorrelating TCA Device Unreachable Alarm Advanced Correlation ScenariosConnectivity 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 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 Correlation Example Cloud Problem AlarmOL-14284-01 Alarm Type Definition Event and Alarm Configuration ParametersEvent Sub-Type Configuration Parameters Root Cause 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 an Alarm Accumulating the Affected Parties In the Correlation TreeUpdating Affected Severity Over Time OL-14284-01 BGP process up Shut down on a device Supported Service Alarms All 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 Figure B-1 Event Correlation Flow VNE level Software Function ArchitectureEvent 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