Cisco Systems 3.6 specifications All IP Interfaces Down Alarm, IP Interface Failure Examples

Page 29

Chapter 4 Advanced Correlation Scenarios

IP Interface Failure Scenarios

Where there is a multipoint setup and only some circuits under an IP interface go down, and this does not cause the state of the IP interface to change to down, then no “ip interface status down” alarm is created. All the circuit down syslogs correlate by flow to the possible root cause, for example, Device unreachable on a customer edge (CE) device.

All IP Interfaces Down Alarm

When all the IP interfaces configured above a physical interface change their state to down, the All ip interfaces down alarm is sent.

When at least one of the IP interfaces changes its state to up, a clearing (active ip interfaces found) alarm is sent.

The ip interface status down alarm for each of the failed IP interfaces is correlated to the All ip interfaces down alarm.

Note When an All ip interfaces down alarm is cleared by the active ip interfaces down alarm but there are still correlated ip interface status down alarms for some IP interfaces, the severity of the parent ticket is the highest severity among all the correlated alarms. For example, if there is an uncleared interface status down alarm, the severity of the ticket remains major, despite the fact that the Active ip interfaces found alarm has a cleared severity.

Table 4-2

All IP Interfaces Down

 

 

 

 

 

 

 

 

 

 

 

Name

 

Description

Ticketable

Correlation allowed

Correlated to

Severity

 

 

 

 

 

 

 

All ip interfaces

 

Sent when all the IP interfaces

Yes

Yes

Link

Major

down/Active ip

 

configured above a physical port

 

 

Down/Configuration

 

interfaces found

 

change their oper status to down

 

 

Change

 

 

 

 

 

 

 

 

The All ip interfaces down alarm is sourced to the Layer1 component. All alarms from “the other side”, for example, device unreachable correlate to the All ip interfaces down alarm.

IP Interface Failure Examples

Note In all the examples that follow it is assumed that the problems that result in the unmanaged cloud, or the problems that occurred on the other side of the cloud (for example, an unreachable CE device from a provider edge (PE) device) cause the relevant IP interfaces’ state to change to down. This in turn causes the ip interface status down alarm to be sent.

If this is not the case, as in some Ethernet networks, and there is no change to the state of the IP interface, all the events on the subinterfaces that are capable of correlation flow will try to correlate to other possible root causes, including “cloud problem”.

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

 

OL-14284-01

4-5

 

 

 

Image 29
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 Integrity Service Sources of Alarms On a DeviceAlarm Integrity 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 FlowCorrelating TCA Using WeightsDC Model Correlation Cache Connectivity Test Device Unreachable AlarmAdvanced Correlation Scenarios 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 LDP Neighbor Down Alarm BGP Process Down AlarmMpls Interface Removed Alarm OL-14284-01 Types of Unmanaged Networks Supported Correlation Over Unmanaged SegmentsCloud VNE Supported When Logical Inventory Physical Inventory Cloud Correlation Example Cloud Problem AlarmOL-14284-01 Alarm Type Definition Event and Alarm Configuration ParametersGeneral Event Parameters Event Sub-Type Configuration ParametersRoot Cause Configuration 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 AnalysisUpdating Affected Severity Over Time Accumulating the Affected Parties In an AlarmAccumulating the Affected Parties In the Correlation Tree 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 Link Over Utilized Rx DormantTx Dormant OL-14284-01 Event and Alarm Correlation Flow Figure B-1 Event Correlation Flow VNE level Software Function ArchitectureEvent Correlation Event Correlation FlowEvent Creation VNE level Post-Correlation Rule Event Correlator Alarm Sending Event CorrelatorCorrelation Logic Event Correlator
Related manuals
Manual 4 pages 36.46 Kb

3.6 specifications

Cisco Systems 3.6 marks a significant advancement in network technology, presenting an innovative suite of features and capabilities designed to enhance performance, security, and flexibility for modern networks. As a leader in networking solutions, Cisco continues to evolve its offerings, ensuring they meet the demands of businesses operating in increasingly complex environments.

One of the standout features of Cisco Systems 3.6 is the introduction of enhanced automation capabilities. Automation reduces the manual effort required for network management, allowing IT teams to focus on strategic initiatives rather than routine maintenance. The system leverages advanced machine learning algorithms to analyze network behavior, detect anomalies, and suggest optimizations, which enhances operational efficiency and uptime.

In terms of security, Cisco Systems 3.6 integrates robust cybersecurity measures directly into its architecture. It incorporates Cisco's SecureX framework, which provides centralized visibility and control across the entire security stack. This feature allows organizations to respond rapidly to threats, leveraging threat intelligence and automated response mechanisms to mitigate risks effectively.

Another notable characteristic is improved compatibility with cloud environments. With the rise of hybrid cloud models, Cisco Systems 3.6 offers seamless integration capabilities that enable businesses to connect their on-premises networks with public and private cloud infrastructures. This ensures greater flexibility and enhanced performance for cloud-based applications.

Cisco also emphasizes software-defined networking (SDN) with its updated platform. This approach allows for greater agility, enabling network administrators to programmatically manage resources through a centralized interface. SDN facilitates rapid deployment of services and applications, optimizing the overall user experience.

Cisco Systems 3.6 also boasts enhanced collaboration tools, fostering improved communication across teams. Featuring advanced video conferencing and messaging capabilities, it enhances productivity and streamlines processes, regardless of employee location. These tools are designed to support remote work environments, which have become increasingly important in today's business landscape.

Furthermore, energy efficiency is a core aspect of Cisco Systems 3.6. The system is designed to optimize power consumption and reduce overall operating costs, aligning with global sustainability goals. The efficient design prioritizes environmentally friendly practices while still delivering high performance.

In conclusion, Cisco Systems 3.6 represents a comprehensive evolution in networking technology, focusing on automation, security, cloud integration, SDN, collaboration, and energy efficiency. These features position Cisco as a pivotal player in supporting organizations as they navigate the complexities of digital transformation and the future of networking.