Cisco Systems 3.6 specifications DC Model Correlation Cache, Using Weights, Correlating TCA

Page 24

Chapter 3 Cisco ANA Event Correlation and Suppression

Correlation Flows

This method is usually applicable for problems in the network layer and above (OSI network model) that might be caused due to a problem upstream or downstream. An example is an OSPF Neighbor Down event caused by a link-down problem in an upstream router. Another important distinction between Cisco ANA PathTracer and the correlation flow is that the correlation flow may run on an historical snapshot of the network.

DC Model Correlation Cache

The DC model correlation cache represents the network as it was before an event occurred or during a specific time frame by enabling the DC cache to be stored.

A flow of packets occurs on the virtual network, as part of correlation of all DCs, from one VNE to a destination VNE while simulating the virtual network state of a past moment in time, and these packets are forwarded via the message processing mechanism from one DC to another DC according to the rules of the flow. If there are active DCs, and if there is a change in the DC’s property value or if a DC was removed, all the DC properties that are marked as cache-based will be stored in the DC model cache for a configurable period of time as defined in the registry and these property values can be restored.

The DC model cache implements this so that the VNE holds cache information for each flow related to a DC (for example, routing entries or bridge entries) and for forwarding tables, so when a VNE needs to reflect its DC model, as it was at some point of time in the past, the VNE will be able to do so based on the cached information it keeps. The DC Property mechanism stores the related data of each property (when cache management is enabled) for a configurable period of time. The default is 10 minutes. The cache can be enabled or disabled in the registry (by default it is enabled).

The cached data (the data that is old according to the configured value in the registry) is periodically cleaned up, in order to maintain the latest valid VNE cache information. This includes old property values and also previously removed DCs, so that removed DCs are kept in a cache only for the defined amount of time. The Cache Manager Component of the DA repeatedly (the period of time is defined in the registry) sends itself a cleanup message in order to initiate a cleanup of the old property values, and all of the DCs that were removed outside of the defined period. So after 10 minutes all the DC properties with a timeout are automatically cleared.

Using Weights

In cases where there are multiple potential root causes along the same service path, Cisco ANA enables the user to define a priority scheme (weight) which can determine the actual root cause.

The correlation system will use the following information to identify more precisely the root-cause alarm:

•weight: >=0 The correlation flow will collect the alarm, but will not stop.

The correlation mechanism will choose the alarm with the highest weight as the root cause for the alarm that triggered the correlation by flow.

Correlating TCA

TCAs participate in the correlation mechanism, and can correlate or be correlated to other alarms.

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

3-4

OL-14284-01

 

 

Page 23 Page 25
Image 24
Page 23 Page 25
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 ANARoot-Cause Alarms Correlation FlowsCorrelation by Key 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 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 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

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.
Top Page Image Contents