Table Of Contents
Cisco Active Network Abstraction 3.6.5
Release NotesNew Features in Cisco ANA 3.6.5
Enhanced Functionality for VNEs
Cisco ANA 3.6.0 Postinstallation Script
Solaris Services and Components
Installing the Cisco IOS XR Manageability Package
Missing Module Software Version Values
JDK DST Timezone Update Tool for Cisco ANA
Configuring Database Storage (Redo Logs)
Workflow Editor Template Naming Conventions
Workflow Editor and Floating User Licenses
Workflow Editor Attribute Types
Resolved Caveats - Cisco ANA 3.6.5
Obtaining Documentation and Submitting a Service Request
Cisco Active Network Abstraction 3.6.5
Release Notes
Revised: May 19, 2009, OL-18659-02These release notes support the release of Cisco Active Network Abstraction (Cisco ANA) 3.6.5.
Note
See Cisco.com for the most up-to-date version of the Release Notes for Cisco Active Network Abstraction 3.6.5.
Contents
This document includes the following topics:
•
•
•
•
Introduction
Cisco ANA 3.6 is a carrier-class, multiple-vendor network and service management platform providing the flexibility for carriers and service providers to efficiently respond to the constant market demand for new, reliable, and more sophisticated services.
Cisco ANA 3.6 identifies network characteristics and builds a real-time virtual model of the network, serving as a live information base for value-added tools and applications capable of seamless integration within a customer's existing Operations Support System (OSS) environment.
Cisco ANA 3.6 provides a unified solution for diverse network environments and applications. Implemented with a highly scalable and distributed architecture, Cisco ANA 3.6 offers:
•
•
•
•
These integrated applications enable correlated management of global-scale networks supporting millions of subscribers and customers.
Cisco ANA 3.6 is a unified, fully integrated solution that offers:
•
•
•
•
Cisco ANA 3.6 dynamically discovers and identifies basic network components, while obtaining end-to-end visibility of the network resources, connections, and dependencies, enabling Cisco ANA 3.6 to manage and analyze network behavior. Cisco ANA 3.6 builds its end-to-end understanding of the network structure and interoperability across vendors, technologies, and network layers into a customer-specific virtual network model for each installation.
The virtual network model within Cisco ANA 3.6 is an always maintained, up-to-date, enabling, and powerful device, network, and service management function, including:
•
•
•
•
•
New Features in Cisco ANA 3.6.5
The following new features were added in Cisco ANA 3.6.5:
•
•
•
•
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
•
•
•
–
–
–
•
•
•
•
–
–
•
Note
•
•
•
–
–
–
For more information about the documentation provided with this release, see Related Documentation.
New VNEs Introduced
Table 1 identifies the VNE device support introduced with Cisco ANA 3.6.5.
For details on the support provided for each VNE, see the Cisco Active Network Abstraction 3.6.5 VNE Reference Guide.
This release also includes support for additional modules and software versions for VNEs that are supported by previous Cisco ANA releases. For details, see the Cisco Active Network Abstraction 3.6.5 VNE Reference Guide.
Enhanced Functionality for VNEs
No functionality was enhanced for existing VNEs in Cisco ANA 3.6.5.
Service Alarms Added
Cisco ANA 3.6.5 has added standard service alarms for Cisco ASR 1000 series and 9000 series devices.
For more information about event and alarm configuration parameters, see the Cisco Active Network Abstraction 3.6.5 User Guide.
Trap Support Added
The following sections identify the trap support added in this release:
•
V2 Traps - Cisco IOS Software
V2 Traps - Cisco ASR Devices
Syslog Support Added
Table 4 identifies the syslog support added in this release. The new syslog support is for Cisco ASR devices.
Pluggable Transceiver Support
Cisco ANA now supports three-level hierarchical discovery and modeling of pluggable transceiver modules on Cisco equipment. The hierarchy looks like this:
|---The Container object|---The Module, such as an SFP container|---The Port, such as an SFP or GBIC portTable 5 identifies the Cisco network elements and pluggable transceivers supported in Cisco ANA 3.6.5.
Table 5 Supported Network Elements and Transceivers
Cisco Catalyst ME-C3750-24TE-M switch
GLC-LH-SM, SFP-GE-L (DOM)1
Cisco Metro Ethernet Access Switches ME-3400G-2CS-A, ME-3400G-12CS-D, and ME-3400G-12CS-A
GLC-LH-SM, SFP-GE-L (DOM)1
Cisco Catalyst 6509-NEB Switch
WS-G5486
Cisco Catalyst 6509-NEB-A Switch, Cisco 7609-S Router
GLC-LH-SM, SFP-GE-L (DOM), XFP-10GLR-OC192SR, XENPAK-10GB-LR
Cisco CRS-1 single-shelf system CRS-16/S
CRS-XENPAK10GB-LR
1 Transceivers GLC-LH-SM and SFP-GE-L (DOM) are displayed in Cisco ANA as 1000BaseLX SFP only. For more information, see CSCsv95130.
Cisco ANA uses objects from CISCO-ENTITY-VENDORTYPE-OID-MIB to physically discover and model the supported transceivers. For details on the MIB objects, contact Cisco Professional Services.
Cisco ANA provides the following property information for the supported pluggable modules:
•
•
•
•
Important Notes
This section includes the following topics:
•
•
•
Installation Notes
This section includes the following topics:
•
For installation procedures, see the Cisco Active Network Abstraction 3.6.5 Installation Guide.
Cisco ANA 3.6.5 is installed on top of a Cisco ANA 3.6 installation and includes all patches that were released since the Cisco ANA 3.6 release. Any patches or fix packs that were previously installed on top of Cisco ANA 3.6 are automatically uninstalled by the 3.6.5 installation script.
Cisco ANA 3.6.0 Postinstallation Script
Beginning with version 3.6.5, Cisco ANA provides a postinstallation script that fixes installation problems associated with Oracle 10G software and Cisco ANA schemas.
This script is to be used only if you are installing Cisco ANA 3.6.0 for the first time. For detailed instructions on using this script, see the gateway installation chapter in the Cisco Active Network Abstraction 3.6.5 Installation Guide.
Memory Consumption
If your network contains several routers that maintain 1000 or more BGP routing entries in their routing tables, and if the VNEs for these devices use the product scheme, memory consumption might increase with this release.
To determine if you are affected, see Enhanced Functionality for VNEs. If new modeling was added for VNEs used in your environment, we recommend that you check your AVM memory allocations. Contact the Cisco Project Manager or Cisco Account Team to perform the necessary calculations.
Generating SSH Keys
You must generate Secure Shell Protocol (SSH) keys to ensure synchronization between the gateway and units. SSH keys are generated on the gateway and propagated to all the units in the setup. For more information, see the Cisco Active Network Abstraction 3.6.5 Installation Guide.
Backward Compatibility
Note the following with regard to backward compatibility of Cisco ANA 3.6.5 with existing installations of Cisco ANA 3.6:
•
•
Solaris 10
Note
On Sun servers, the recommended operating system for Cisco ANA 3.6.5 is Solaris 10. Cisco ANA 3.6.5 is compatible with the latest patch release as published by Sun on January 18, 2008 (Cluster patch ID Generic_120011-14). Table 6 identifies the patches included in this patch release.
Note
Solaris Services and Components
Table 7 lists the Solaris services and components that Cisco ANA uses and that must not be removed.
Table 8 lists the product services that are installed with Cisco ANA.
Using Cisco CRS-1 VNEs
Installing the Cisco IOS XR Manageability Package
For Cisco CRS-1 VNEs, you must install the Cisco IOS XR Manageability Package on top of the Cisco IOS XR version. In addition, verify that the device configuration contains the following command:
xml agent ttyCreating the SNMP Community
When creating the SNMP community, configure a new SNMP community string that has SystemOwner privileges. To do this, log into the device and create a new community read string with SystemOwner privileges, and then direct the Cisco ANA VNE to use the new community. For example:
snmp-server community 1icpub RO SystemOwnersnmp-server community ate9riv RWMissing Module Software Version Values
The module software version does not appear for Cisco CRS-1 devices that use software earlier than Cisco IOS XR version 3.7. This issue was resolved in Cisco IOS XR version 3.7 but occurs in earlier versions. For more information, see CSCsk36398.
Supported Schemes
Cisco ANA supports two schemes:
•
•
Table 9 identifies the schemes used by device type.
JDK DST Timezone Update Tool for Cisco ANA
Cisco ANA comes with Java Development Kit (JDK) 1.4.2_13. It is possible that the daylight saving time (DST) at your location has changed since JDK 1.4.2_13 was released. If this is true for you, you can use the Sun JDK DST Timezone Update Tool to be current with the latest daylight saving time as published by Sun.
To use the Sun JDK DST Timezone Update Tool:
1.
http://java.sun.com/javase/downloads/index.jsp
2.
3.
a.
b.
c.
d.
java -jar tzupdater.jar -u -v4.
Configuring Database Storage (Redo Logs)
If you are already running Cisco ANA 3.6, change the Oracle installation to write the logs on a different disk. For more information, see the Cisco Active Network Abstraction 3.6.5 Installation Guide.
Online Help
The online help for Cisco ANA 3.6.5 has been tested using the following browsers:
•
•
•
Note
http://www.cisco.com/en/US/products/ps6776/tsd_products_support_series_home.html
Limitations and Restrictions
This section includes the following limitations and restrictions:
•
•
Cisco ANA NetworkVision
Cisco ANA NetworkVision, with a configured 512 MB of free nonvirtual memory per running instance, supports the following number of objects, links, and devices across all maps that are open:
•
•
•
One map in Cisco ANA NetworkVision supports:
•
•
•
The maximum number of maps that can be opened concurrently for Cisco ANA NetworkVision is five (the default) regardless of the number of devices, links, and tickets. The number of maps that can be opened concurrently can be modified as long as the overall number of links and devices per application does not exceed the maximum limits. For information about customizing the maximum number of maps, contact the Cisco Project Manager or Cisco Account Team.
Cisco ANA Fault Management
The maximum number of open tickets (other tickets can be correlated to them) for the system is 5000. Although this number is configurable in the registry, we do not recommend increasing it. For a definition of an open ticket, see the Cisco Active Network Abstraction 3.6.5 User Guide. To avoid exceeding the maximum number of open tickets, we recommend that you close the tickets on time.
Note
A tickets capacity overflow system alarm is generated when the maximum number of open tickets is exceeded. The alarm severity is defined as critical.
Cisco ANA Workflow Editor
The following sections provide important information for working with Cisco ANA Workflow Editor:
•
•
•
Workflow Editor Template Naming Conventions
Do not include the characters underscore ( _ ) or percent (%) in workflow template names when executing a workflow or referencing a subflow. In template names, these characters act as wildcards and represent the following:
•
•
If these characters are included in template names, the execution fails and the following message is displayed in the AVM 66 log:
"WARN [13 21:00:08,248] - dralasoft.workflow - Task aborted. Task: 245886, Workflow: 245885 java.lang.IllegalArgumentException: Template AA_BB.template is ambiguous, templates ids are: 245874 , 245873"The following examples illustrate how workflow template names with these characters can lead to ambiguity if they are deployed together:
•
•
The ambiguity occurs only when templates containing wildcard characters in their names are executed.
Workflow Editor and Floating User Licenses
Users cannot open multiple Cisco ANA workflow sessions from the same PC when they are using the Floating User License.
Workflow Editor Attribute Types
By default, all attributes in Workflow Editor are of the type String. To use another attribute type, such as Integer, set the flag use-workflow-string-param-casting to true in /export/home/sheer4/Main/registry/workflowavm.xml. In workflowavm.xml, the flag use-workflow-string-param-casting appears under the workflow key.
After you change this flag to true, you can use attribute types other than String.
OSPF
OSPF networks are presented in Cisco ANA logical inventory. The current implementation was developed to present nonoverlapping interfaces so that, when a device has multiple interfaces with the same IP address and these interfaces participate in different OSPF networks, only one interface is displayed. For example, a device might have multiple interfaces that use the same IP address if it is configured for multiple VRFs.
This situation can occur when multiple OSPF processes are running on the device.
OSPF processes (OSPFService) do not have IMO representation in Cisco ANA.
HSRP
For correlation to work, the path through which HSRP signaling passes must be modeled (must exist) in the system.
ATM Topology Discovery
ATM topology discovery is performed in two phases:
1.
2.
ATM topology discovery is supported on topologies where the ports at either end of the connection are both configured with VCs or VPs. Discovery is not supported on ATM topologies where VPs are configured at one end and VCs are configured at the other end.
Adaptive Polling
Adaptive polling is supported only for Cisco devices and the Juniper VNE.
BGP Neighbors
•
•
Open Caveats in Cisco ANA 3.x
Table 10 Open Caveats in Cisco ANA 3.x
MPBGP section in logical inventory shows only the local Cisco ASR 1841 router.
The Multiprotocol BGP (MPBGP) section in logical inventory shows only the local Cisco ASR device instead of showing the BGP peer details.
This situation occurs when a BGP peer is configured on the device.
None
3.6.5
FRU traps do not correlate to card down on Cisco GSR devices running Cisco IOS XR 3.7.1
When a card is removed from Cisco GSR devices running Cisco IOS XR 3.7.1 software, the following Field replaceable unit (FRU) traps are not correlated under the Card Out ticket:
•
•
None
3.6.5
Cisco 3750ME: Cisco GBICs SFP-GE-L and GLC-LH-SM are not displayed in Cisco ANA NetworkVision
If the following GBICs are inserted into a Gigabit Ethernet port on a Cisco 3750ME device, they are displayed in NetworkVision:
•
•
None
3.6.5
Cisco ASR 9000: Hardware Type shown as Unknown
For Cisco ASR 9010 devices, NetworkVision physical inventory displays A9K-RSP-HDD in the Hardware Type field instead of the correct value of A9K-RSP-4G.
None
3.6.5
Cisco ME3400 devices: Wrong VlanInterface Mode when Ethernet port is down
For Cisco ME3400 devices, if a Gigabit Ethernet port that is configured with dot1q tunneling goes down, NetworkVision displays Access instead of Dot1q-Tunnel for the VlanInterface mode.
Enter the following command:
show dot1q-tunnel3.6.5
MPLS 13 VPN vrfDown trap does not correlate to link down alarm
When a link is shut down on a port configured with MPLS 13 VPN VRF, a separate mpls 13 vrf Down Trap ticket is created instead of being correlated to the link down service alarm.
None
3.6.5
Cisco ASR1004 routers: A few SFP values appear as "yyyyyyyyyyyyyy"
For Cisco ASR 1004 routers, if the Part ID and Description fields for an SFP are empty, Cisco ANA displays yyyyyyyyyyyyyy for their value in NetworkVision.
None
3.6.5
Cisco ME3400 devices: Incorrect type shown for static route entry under routing table
For Cisco ME3400 devices, the static route entry in the logical inventory routing table displays Indirect instead of Static.
None
3.6.5
Some BGP links are missing in the Cisco ANA GUI
In an environment using MPLS, some BGP links are not displayed in the Cisco ANA GUI although all links are present on the VNE.
Restart AVM 11 by entering the following command:
mc.csh localhost 8099 bsm.restartAvm 11
3.6.5
Cisco GSR XR 3.6.2: Module XFP-10GLR-OC192SR is not displayed in Cisco ANA
For Cisco GSR XR devices running Cisco IOS XR 3.6.2 software, Cisco XFP-10GLR-OC192SR modules inserted into TenGigE0/2/1/0 slots are not displayed in NetworkVision.
None
3.6.5
EventVision froze after two weeks
The EventVision GUI froze after it was open continuously for two weeks.
Close and restart EventVision.
3.6.5
Cisco ASR 9010 routers: A few interfaces are missing from physical inventory
The following interfaces do not appear in Cisco ANA physical inventory in NetworkVision for Cisco ASR 9010 devices:
•
•
None
3.6.5
Cisco GSR-XR devices: Cisco ANA does not display the pseudowire container configured at device
For Cisco GSR XR devices running Cisco IOS XR 3.6.2 software, a configured pseudowire is not displayed in NetworkVision as a container.
None
3.6.5
Cisco GSR-XR devices: When a Gigabit Ethernet port is down, OSPF is shown as if it were up
For Cisco GSR XR devices running Cisco IOS XR 3.6.2 software, when a Gigabit Ethernet port is down, Open Shortest Path First (OSPF) Networks Traffic Descriptor Container Properties are the same as when the port is up.
None
3.6.5
Label switching protocol is not refreshed in LSE table
When changing the MPLS label switching protocol on an interface from Label Distribution Protocol (LDP) to Tag Distribution Protocol (TDP), the LSE table is not refreshed for protocol and state.
This situation occurs when running an LDP session with a neighbor.
Wait for the next polling period for the table to refresh.
3.6.5
Wrong hardware type value for POS modules in Cisco 12000 series device
For Packet-Over-SONET (POS) modules in Cisco 12000 series devices, NetworkVision physical inventory displays cevGsrE48Atm4oc3SmIrSc in the Hardware Type field instead of the correct value of cevModuleGsrType.155.
None
3.6.5
Power supply and fan are not modeled for Cisco 12000 series devices
NetworkVision physical inventory does not display power supply units or fans for Cisco 12000 series devices.
None
3.6.5
Chassis description and serial number are not populated for Cisco 3750ME Ichassis
NetworkVision physical inventory does not display a chassis description or serial number for Cisco 3750ME devices.
None
3.6.5
Power supply and fan are not modeled for Cisco ME3400 devices
NetworkVision physical inventory does not display power supply units or fans for Cisco ME3400 devices.
None
3.6.5
Wrong physical modeling for Cisco CRS-1 devices running Cisco IOS XR software version 3.8.0.29I
The physical modeling is incorrect for Cisco CRS-1 devices running Cisco IOS XR 3.8.0.23I software.
This situation occurs because the device response to the Entity MIB contains the module information before the chassis information.
None
3.6.5
Flash Device Size is 0 in ImanagedElement of Cisco 12000 series device
In NetworkVision, the Flash Device Size field displays a value of 0 (zero) for Cisco 12000 series devices.
None
3.6.5
DRAM Used and DRAM Free memory are not populated for Cisco 12000 series devices
NetworkVision does not display the fields for DRAM Used and DRAM Free memory for Cisco 12000 series devices.
None
3.6.5
Flash device size attribute is missing in ImanagedElement of Cisco 4948 device
For Cisco 4948 devices, the flash device size attribute is not displayed in ImanagedElement in NetworkVision.
None
3.6.5
Riverstone: A few entries are missing in the IP Interface table
The following information is incorrect in NetworkVision logical inventory for Riverstone devices:
•
•
None
3.6.5
Riverstone: VLAN ID should be displayed for bridges
NetworkVision logical inventory displays the bridge VLAN name but does not display the VLAN ID for Riverstone device.
None
3.6.5
Port containers are not modeled for Cisco Catalyst 4948 devices
If you add a VNE for a Cisco 6500 device, and then, in NetworkVision, select Physical Inventory > Chassis > Slot > Module > Port, the port containers do not appear.
None
3.6.5
For Cisco 6503 devices, the software version is a mismatch
If you update the software on a Cisco 6503 device, Cisco ANA inventory updates the product description in inventory, but not the software version.
The software version can take 30 minutes to be updated.
None
3.6.5
Power and fan modules are not modeled for Cisco Catalyst 4948 devices
If you add a VNE for a Cisco Catalyst 6500 device, and then, in NetworkVision, select Physical Inventory > Chassis > Slot > Module, the power and fan modules are not displayed.
None
3.6.5
Connector details are missing for Cisco Catalyst 4948 devices
If you add a VNE for a Cisco Catalyst 4948 device, and then, in NetworkVision, select Physical Inventory > Chassis > Slot > Module, the connector description and part ID are not displayed for port containers.
None
3.6.5
Hardware type of fixed module is inaccurate for Cisco Catalyst 4948 devices
If you add a VNE for a Cisco Catalyst 4948 device, and then, in NetworkVision, select Physical Inventory > Chassis > Slot > Module, the Hardware Type field contains incorrect information for the fixed module.
None
3.6.5
BGP peer state is populated incorrectly for Cisco 12000 series devices
In NetworkVision, the Peer State field in the BGP Neighbors Properties window displays Active instead of Established for Cisco 12000 series devices.
None
3.6.5
Juniper LDP Session Up/Down trap without correlation
The SNMP trap Juniper LDP Session Up/Down is generated when the value of jnxMplsLdpSesState leaves the operational(5) state.
This situation occurs for:
•
•
•
•
None
3.6.4
Cisco ANA does not present the interface when SONET interface changes
Cisco ANA does not present the interface when the SONET interface changes.
None
3.6.4
Cisco ANA presents Swact notification (Redundancy) as Generic trap for Cisco CRS-1 devices
Cisco ANA presents Swact notification (Redundancy) SNMP traps as Generic traps in EventVision.
The trap is ciscoRFSwactNotif.
To generate the ciscoRFSwactNotif trap, use the following MIB:
OID:.1.3.6.1.4.1.9.9.176.2.0.1
None
3.6.4
Path Tracer does not reach IP interface configured on L3 Link Agg on Cisco CRS-1 devices
If you use Path Tracer on an interface that is configured for Layer 3 link aggregation on a Cisco CRS-1 device, the path does not reach the IP interface of the remote device.
None
3.6.4
Standard access list entries are not shown for Cisco 3750ME devices
Standard access list entries configured on Cisco 3750ME devices are not displayed in the Cisco ANA interface.
To check access lists entries on the device, enter the following command on the device:
show access-lists3.6.4
On Cisco 3750ME devices, one of the TRUNK ports is modeled as ACCESS
This situation occurs when you:
1.
2.
The comparison reveals that the TRUNK port contains inconsistent information.
None
3.6.4
Missing DataLinkAggregation info
Some of the DataLinkAggregation information is missing for Cisco 3750ME and Cisco 2950 devices. This situation occurs when you:
1.
2.
The DataLinkAggregation information is missing.
None
3.6.4
Some of the Juniper VNEs appear under Product scheme
Some Juniper VNEs appear under the Product scheme even though they are supported by the ipcore scheme.
This situation occurs when you run the VEG tool. The results show the VNEs for some Juniper devices under the Product scheme instead of the ipcore scheme.
None
3.6.4
Information missing for system description and element type
For Cisco 7609-S devices, the following fields do not contain complete information in NetworkVision:
•
•
None
3.6.4
Cisco GSR 12016: Module unsupported
The Cisco GSR 12016 fan tray is unsupported.
None
3.6.4
No description and no access-list entry appear in IP interface for Cisco GSR and Cisco CRS devices
In NetworkVision, if you provide a description, configure an access list for a Cisco GSR or Cisco CRS-1 device, and then select Logical Inventory > Routing Entry > IP Interface, the interface description and the access-lists entries are not displayed.
None
3.6.4
LDP protocol type received in NetworkVision is not followed by expedite
The wrong Label Distribution Protocol (LDP) status appears in inventory.
This occurs if you complete the following steps:
1. Create a new VNE for the affected device and open a map in NetworkVision with this device.
2. Open MPLS interfaces under the LSE table and enter LDP in the Distribution Protocol field.
3. Change the distribution protocol type to TDP on the device and confirm the change in NetworkVision.
4. Change the distribution protocol type to LDP on the device.
None
3.6.4
Removing a card from a Cisco GSR device causes links to disappear
This situation occurs when the links between the Cisco GSR device and other devices are modeled and the card is removed.
None
3.6.4
MPBGP section in logical inventory shows only the local AS (R-1841)
The MPBGP section in logical inventory shows only the local Autonomous System (AS) (R-1841).
None
3.6.4
Missing location for SNMP link down trap
If a link goes down on a device running Cisco IOS XR 3.6.1[00] software, EventVision does not display the location for the SNMP link down trap.
None
3.6.4
Missing Card Down tickets for Cisco GSR routers running Cisco IOS XR 3.7.1
On a Cisco GSR router running Cisco IOS XR 3.7.1 software, if a card goes down, Link Down tickets are issued instead of a Card Down ticket and three Link Down tickets that are correlated to the card.
None
3.6.4
Missing FrameRelay traffic profiles in logical inventory (Cisco R1841 routers)
Logical inventory does not display FrameRelay traffic profiles for Cisco R1841 routers.
None
3.6.4
No topology due to wrong port encapsulation in Cisco CRS-1 devices (High-Level Data Link Control [HDLC] instead of PPP)
For Cisco CRS-1 devices, due to the wrong encapsulation for a POS interface, no topology is discovered for that port although CDP neighbors are properly discovered.
To work around this issue, create a static link.
3.6.4
VLANs above Link Aggregation (LAG) links in switches are incorrectly modeled
Elements of type IEEE802 are connected as sons of VlanInterface, thus creating a class cast exception in IEEEOidToPcTranslator.
None
3.6.4
Failed to model Cisco GSR devices running Cisco IOS XR inventory from recordings
Telnet output of recordings for Cisco GSR devices running Cisco IOS XR software appears to be corrupted due to appearance of unexpected characters. As a result, the recordings cannot be used for device modeling in Cisco ANA.
None
3.6.4
SPA-4XT3_E3 slot has wrong parameters on Cisco CRS-1 router
Cisco ANA displays the wrong parameters for SPA-4XT3_E3 slots in physical inventory.
Cisco ANA displays "missing pluggable port" even though the slot is a coaxial port and it is connected.
None
3.6.4
Power supply down trap appears as generic
If you disconnect the power cord for a Cisco 7613 device, the Power supply down trap in Cisco ANA appears as generic.
None
3.6.4
Wrong port type for Gigabit Ethernet on Cisco 7606 card WS-SUP720-3B
For Cisco 7606 devices running Cisco IOS 12.2(33) SRB3 software, the port type for Cisco WS-SUP720-3B cards is displayed as RJ45 instead of fiber optic.
None
3.6.4
VNE "Maintenance" status missing
The VNE Maintenance status is missing in the Cisco ANA Manage client.
This situation occurs for VNEs for Cisco 7206VXR router reflectors that are running BGP and Cisco IOS software version 12.4(15)T1 and that are modeled with the Product scheme.
None
3.6.4
Cisco 6500 Virtual Switching System (VSS) Shelf out and Card out alarms are generated when the redundancy force-switchover command is issued
When Cisco 6500 VSS systems are issued the redundancy force-switchover command, the force-switchover occurs and the active switch is moved to Stand-By state and vice versa.
In the Cisco ANA GUI, the Shelf out and Card out alarms are generated.
None
3.6.3
Cisco 6500 VSS Interface operational state is down in active switch
When Cisco 6500 VSS systems are issued the redundancy force-switchover command, the Interface operational state goes down in the active switch.
None
3.6.3
Cisco 6500 VSS Module status shown as OUT in active switch
When Cisco 6500 VSS systems are issued the redundancy force-switchover command, the Module status is shown as OUT in the active switch.
None
3.6.3
Ticket is created for each SFP after card has been removed from a Cisco CRS-1 device
When removing a card from a Cisco CRS-1 system containing a shared port adapter (SPA) with 5 SFPs, each of the l5 related SFP "cefc FRU removed" traps is presented as a ticket in NetworkVision.
None
3.6.3
Cisco 6509 device: Wrong information is shown for Generic Routing Encapsulation (GRE) tunnel
For Cisco 6509 devices, the wrong source is shown for a GRE tunnel.
None
3.6.3
For Cisco MC CRS-1 devices, management interfaces from the second chassis are not displayed in Cisco ANA
For Cisco CRS-1 devices with a multiple chassis configuration, NetworkVision physical inventory does not display the management ports MgmtEth1/RP0/CPU0/0 and MgmtEth1/RP0/CPU0/1.
None
3.6.3
Long Port description is truncated in ANA GUI
Long port descriptions that are configured for Fast Ethernet (FE) ports on Cisco 3750ME devices are truncated in the Cisco ANA GUI. Only 64 characters are displayed.
This situation occurs because the data type for ifAlias is defined as DisplayString (0...64) in the MIB.
Using a CLI, enter the following command on the device:
snmp ifmib ifalias long
This command allows a maximum of 256 characters to be displayed. For additional information, see the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hnm_c/ch10/hshowif.htm
3.6.3
Resolved Caveats - Cisco ANA 3.6.5
Related Documentation
User Guides
Cisco Active Network Abstraction 3.6.5 Documentation Guide
Cisco Active Network Abstraction 3.6.5 User Guide
Cisco Active Network Abstraction 3.6.5 Managing MPLS User Guide
Cisco Active Network Abstraction 3.6.5 Technology Support and Information Model Reference Manual
Cisco Active Network Abstraction 3.6.5 VNE Reference Guide
Administrator Guides
Cisco Active Network Abstraction 3.6.5 Installation Guide
Cisco Active Network Abstraction 3.6.5 Administrator User Guide
Developer Guide
Cisco Active Network Abstraction 3.6.5 Customization User Guide
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 1999-2009 Cisco Systems, Inc. All rights reserved.
Guest
