Cisco Active Network Abstraction Reference Guide, 3.7.1
Cisco VNE Introduction

Table Of Contents

Introduction

Introduction to VNEs

Understanding the Tables

Software Versions

ANA Versions

Expedite Legend


Introduction


This chapter introduces Virtual Network Elements (VNEs) and describes the types of information available in this Guide.

This chapter contains the following topics:

Introduction to VNEs

Understanding the Tables

Introduction to VNEs

VNEs (Virtual Network Elements) are independent software processes that run on the Cisco ANA Unit Servers. Each VNE is assigned to manage a single network element (NE) using the NE's management interfaces (for example, SNMP and/or Telnet). The VNEs maintain a live model, or abstraction, of each NE and the entire network.

As the VNE loads, it starts investigating the NE and automatically builds a live model of the NE, including its physical and logical inventory, its configuration and its status. After modeling the NE, the VNE begins negotiating with peer VNEs, which represent the peer NEs, in order to determine NE connectivity and topology at different layers. This model of the network topology, NE state, and NE inventory is constantly being updated by the VNEs, which track every change that occurs in the NEs and the network.

The VNEs communicate between themselves to analyze end-to-end flows, which provide information for root-cause and impact analysis, service path tracing, and more.

Understanding the Tables

This section describes key information that can be found in the VNE support information chapters in this Guide

This section contains the following topics:

Software Versions

ANA Versions

Expedite Legend

Software Versions

The Software Version column in the tables in this Guide identifies the NE software versions that are compatible with Cisco ANA and that can be running on the NEs that Cisco ANA supports. For example: The "Cisco 7600 Series—Supported Software Versions" table lists Cisco IOS software version 12.2(18)SXD. This means that Cisco ANA will work with any supported Cisco 7600-series router (such as the Cisco 7603) that is running IOS release 12.2(18)SXD.

Cisco ANA may support subsequent maintenance releases of NE software versions, but only if these later NE software versions do not require changes in Cisco ANA to maintain compatibility. Changes in any of the following NE software components can affect compatibility with Cisco ANA, and may require Cisco ANA software changes: XML interfaces, SNMP commands, MIBs, and CLI commands. In cases where a new NE software version remains compatible without requiring changes in Cisco ANA, support will include recognition of the new NE software version. However, it may not include support for additional software and features (such as new hardware modules) in the NE software version.

Also, for Cisco ANA to recognize a later NE software image, the name of the NE software rebuild should be similar to a software image in the train already supported in Cisco ANA. For example, Cisco ANA supports IOS 12.2(33)SRC4 for 7600 devices. If IOS 12.2(33)SRC5 is released, Cisco ANA will recognize IOS 12.2.(33)SRC5 with the same level of support as IOS 12.2(33)SRC4 on 7600 devices. However, Cisco ANA will not support any additional software or hardware features introduced in IOS 12.2(33)SRC5.

Cisco ANA will not recognize any other maintenance or special build whose version string does not match the indicated naming pattern. For example: IOS 12.2(33)SRC4xyz (or any other variation) will not be recognized.

When an NE software release is not recognized, Cisco ANA attempts to model the NE using the default version for that device series. The default version is a device-specific fallback set of commands and MIB instrumentation that allows Cisco ANA to discover and query for basic device properties, including:

Managed element information.

Basic physical inventory.

Logical Inventory (including the Routing Table, ARP, BGP and OSPF information). Modelling of other technologies is done on a best-effort basis.

The default version does not correspond to any specific supported NE software version. Building of the physical model and its containment structure depends on the instrumentation (MIB and CLI commands) used by the default version. The default version may show you different containment structures (modules and cards) from what you will see for an explicitly supported NE software version. You can discover whether the default version is being used for a particular VNE by looking in the AVM log located in install directory/main/logs (search for default version).

Cisco frequently qualifies new NE software versions for compatibility with Cisco ANA, and updates the online version of this Guide accordingly. If you are not sure whether the current version of Cisco ANA supports a recently released NE software version, check the online version of this Guide on Cisco.com for an update. The NE software version should appear in the updated version of this Guide if it has been qualified as compatible with this Cisco ANA release. If the online version of this Guide does not list the new software version, contact Cisco Professional Services or your Cisco Sales Representative.

ANA Versions

The ANA Version column found in the tables in this Guide lists the version of ANA during which a VNE supporting the specified NE module, software, topology, or other feature was first introduced. It is therefore the earliest Cisco ANA version that supports that NE. All later versions of ANA also support the NE. For example: If the Guide indicates that Cisco 7600 routers are supported on Cisco ANA 3.6.0, they are also supported on Cisco ANA 3.6.1, 3.6.2, and so on.

Expedite Legend

Table 1-1 describes the meaning of the Expedite column found in the service event (service alarm) tables in this Reference Guide.

Table 1-1 Expedite Legend in Service Event Tables 

Value
Descriptions

Y

The service event is expedited by a syslog or trap generated by the device. This means that the syslog or trap causes the VNE to poll the device without waiting for the usual polling cycle, thus enabling quicker detection of the event.

N

The service event is not expedited.This means that the VNE will poll this device during the next regularly scheduled polling cycle.