Cisco Systems 3.6 specifications Vne

Page 18

Chapter 2 Fault Detection and Isolation

Unreachable Network Elements

Table 2-1

 

Unreachable Network Elements (continued)

 

 

 

 

 

 

VNE Type

Checks reachability using

When the NE fails to respond

When the NE is reachable

 

 

 

 

 

Generic

•

SNMP only (default).

General polling is suspended, and a VNE

• General polling is restarted.

VNE

 

During the SNMP test the

Unreachable alarm is sent to the

• The first time the VNE is

 

 

unit’s “SNMP get” the

Cisco ANA Gateway. Only the

 

 

 

started, all the commands are

 

 

sysoid of the NE and

reachability tests are executed thereafter to

 

 

 

 

submitted to the queue, and the

 

 

expects to receive a

detect when the device is reachable again.

 

 

 

 

collector initiates an

 

 

response

 

 

 

 

If more than one protocol is used, it is

 

immediate session with the

 

 

 

 

 

 

or

enough for one of them to become

 

NE. The commands are sent to

 

•

SNMP only (default),

unreachable in order to generate the alarm.

 

the NE in a serial fashion.

 

The alarm is generic to all the protocols.

 

 

 

 

and adding an ICMP test.

•

The alarm is cleared.

 

 

 

 

 

Full VNE

•

SNMP only (default).

General polling is suspended, and a VNE

• The first time the VNE is

 

 

During the SNMP

Unreachable alarm is sent to the

 

started, all the commands are

 

 

reachability test, the

Cisco ANA Gateway. Only the

 

submitted to the queue and the

 

 

VNE polls the device’s

reachability tests are executed thereafter to

 

collector initiates an

 

 

SysOID MIB using a

detect when the device is reachable again.

 

immediate session with the

 

 

standard “SNMP Get”

If more than one protocol is used, it is

 

NE. The commands are sent to

 

 

command, and expects to

 

the NE in a serial fashion.

 

 

enough for one of them to become

 

 

 

receive a response

unreachable in order to generate the alarm.

•

The alarm is cleared.

 

 

 

 

 

or

The alarm is generic to all the protocols.

 

 

 

•

SNMP only (default),

 

 

 

 

 

and adding ICMP and

 

 

 

 

 

Telnet. During the Telnet

 

 

 

 

 

test the unit sends

 

 

 

 

 

"Enter" via the open

 

 

 

 

 

session and expects to get

 

 

 

 

 

a prompt back.

 

 

 

 

 

 

 

 

 

Each of these scenarios have two possible settings in the registry, namely:

•track reachability (true/false). The default is true.

When this parameter is true reachabilty is tracked according to the specific protocol, for example, ICMP, SNMP, Telnet, and so on.

When this parameter is false then the test is not performed.

•lazy reachability (true/false). The default is false. This parameters determines whether there is a dedicated reachability command ‘in-charge’ of tracking reachability or whether reachability is determined by the regular polled commands.

When this parameter is true reachability is based on polling, and a dedicated command not activated.

When this parameter is false a dedicated SNMP command is activated, and this test verifies the response from a specific SNMP oid (sysoid is the default that can be changed).

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

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

2-2

OL-14284-01

 

 

Page 17 Page 19
Image 18
Page 17 Page 19
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 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