Table Of Contents
Cisco Active Network Abstraction 3.6.6
Release NotesNew Features in Cisco ANA 3.6.6
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
Resolved Caveats - Cisco ANA 3.6.6
Obtaining Documentation and Submitting a Service Request
Cisco Active Network Abstraction 3.6.6
Release Notes
Revised: June 26, 2009, OL-19193-01
These release notes support the release of Cisco Active Network Abstraction (Cisco ANA) 3.6.6.
Note
See Cisco.com for the most up-to-date version of the Cisco Active Network Abstraction 3.6.6 Release Notes.
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.6
The following new features were added in Cisco ANA 3.6.6:
•
Using Cisco ANA NetworkVision or Cisco ANA Manage, you can move links to maintenance mode to suppress link alarms. This allows you to suppress these alarms while you perform configuration and provisioning in the network. If you still want to see the alarms, you can set Cisco ANA EventVision to display them.
In addition, you can view all links in maintenance mode and remove links from maintenance mode.
For details, see the Cisco Active Network Abstraction 3.6.6 User Guide and Cisco Active Network Abstraction 3.6.6 Administrator Guide.
•
Cisco ANA NetworkVision displays IPv6 addresses when they are configured on provider edge (PE) and customer edge (CE) routers in the Cisco ANA NetworkVision IP interface table. For details, see the Cisco Active Network Abstraction 3.6.6 MPLS User Guide.
•
•
•
•
•
–
•
–
–
•
•
–
–
•
–
•
–
•
–
•
–
•
•
•
XFP-10GLR-OC192SR
A9K-4T-E
A9K-8T/4-B
A9K-8T/4-E
SFP-GE-L
SFP-GE-Z
XFP-10GZR-OC192LR
XFP-10GER-192IR+
A9K-RSP-4G
ASR-9006-FAN
A9K-1.5KW-DC
A9K-2KW-DC
Note
•
•
–
–
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.6 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.
Note
Cisco ANA 3.6.0 Postinstallation Script
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.6 Installation Guide.
Upgrade to Cisco ANA 3.6.6
Upgrading to Cisco ANA 3.6.6 from an earlier version of Cisco ANA could take a long time on the Cisco ANA servers that have a large number of alarms in the database. For example: On an enterprise-level server with 2 million alarms in the database, the upgrade may take approximately 90 minutes. This also affects downgrading from Cisco ANA 3.6.6 to earlier versions of Cisco ANA. See CSCta10859 for more details.
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.
If new modeling was added for VNEs used in your environment, we recommend that you check your AVM memory allocations. Contact the Cisco ANA 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.6 Installation Guide.
Backward Compatibility
Note the following with regard to backward compatibility of Cisco ANA 3.6.6 with existing installations of Cisco ANA 3.6:
•
•
Solaris 10
Note
On Sun servers, the recommended operating system for Cisco ANA 3.6.6 is Solaris 10. Cisco ANA 3.6.6 is compatible with the latest patch release as published by Sun on January 18, 2008 (cluster patch ID Generic_120011-14). For more information, see the Cisco Active Network Abstraction 3.6.6 Installation Guide.
Solaris Services and Components
Cisco ANA uses the Solaris services and components. You must not remove them. For more information, see the Cisco Active Network Abstraction 3.6.6 Installation Guide.
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:
•
•
For supported device type and schemes table, see Cisco Active Network Abstraction 3.6.6 Administrator Guide.
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.6 Installation Guide.
Online Help
The online help for Cisco ANA 3.6.6 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.
Links in Maintenance Mode
When a link is placed in maintenance mode, the severity property of the physical layer link remains in the same state as it was before the link was placed in maintenance mode. The link property changes for other layers except for physical layer. You can view the link state in the maps displayed in Cisco ANA NetworkVision.
For example: When a fault occurs on a link that is not on maintenance mode. The link turns red. If the operator adds this link to maintenance mode to suppress further alarms. The link continues to remain in red as long as the link is in maintenance mode even though the fault in the physical link is rectified.
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.6 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.
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 and the Juniper devices.
BGP Neighbors
•
•
Open Caveats in Cisco ANA 3.x
The open caveats in Cisco ANA 3.x are:
Table 1 Open Caveats in Cisco ANA 3.x
Layer 3 ports causes MAC-based topology to create the wrong links
If you have Layer 3 Cisco 6500 or Cisco 7600 devices in the network and they do not have unique MAC addresses for each port, the physical topology is discovered incorrectly and ports are erroneously connected in Cisco ANA.
Disable MAC-based topology discovery in Cisco ANA using the following steps:
1.
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 "site/agentdefaults/da/amsi/topology/common/waitForSpecificSignature" true2.
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 "site/agentdefaults/da/amsi/topology/ethernet/enabled" false3.
3.6.6
Cisco MWR 2941: Pluggable type not shown for inserted SFP
If you add a VNE with SFP in a Gig0/0 SFP container, and then, in Cisco ANA NetworkVision, select Physical Inventory > Chassis > Slot, the Pluggable type of SFP is not displayed in the Ports table and Location Information of Port container.
None
3.6.6
Cisco MWR 2941: Serial number for motherboard is missing
If you add a VNE for a Cisco MWR 2941 running Cisco IOS 12.4(19)MR02, and then, in Cisco ANA NetworkVision, select Physical Inventory > Chassis > Slot, the serial number for the motherboard is not displayed.
None
3.6.6
The 6500 IOS ATM interface type is misleading
Cisco ANA displays the ATM interface as "Unknown" for devices, such as the Cisco 6500 or Cisco 7600 that contain the ATM interface.
None
3.6.6
Physical port is not modeled for Cat4503-E
The physical port FastEthernet1 is not modeled for Cisco Catalyst 4503-E.
None
3.6.6
Incorrect modeling of Mgmt 0/RP0/* interface
For Cisco CRS-1 with Cisco IOS XR 3.7.0, GigabitEthernet port is displayed under RP card instead of Mgmt ports.
None
3.6.6
Cisco ANA is not setting transceiver-related property for affected cards
Cisco ANA does not set the transceivers-related property for the cards affected by the new CNEM recommendation post SRD1.
None
3.6.6
No ports under SPA-4XOC48POS/RPR are displayed
If a single Cisco CRS chassis is configured as a parent router and LR router, the ports under the modules associated to the LR router are not shown in Cisco ANA NetworkVision.
None
3.6.6
No ports under CRS-FCC-SC-22GE are displayed.
For Cisco CRS with Cisco IOS XR 3.8.0, no ports under CRS-FCC-SC-22GE are displayed in Cisco ANA NetworkVision.
None
3.6.6
GSR-XR inserted module not reflected in GUI
Cisco XR 12000 shared port adapter (SPA-2XCT3) is not visible in the Cisco ANA user interface.
This issue occurs when you:
1.
2.
3.
None
3.6.6
Command Builder Update should be confirmed to the user
No confirmation message is displayed when the existing command script is updated. This issue occurs when you:
1.
2.
3.
4.
5.
6.
None
3.6.6
Dynamic VLAN type is shown as static VLAN
For Cisco Catalyst 4503, the dynamic VLAN setup is displayed as static VLAN in the Cisco ANA NetworkVision user interface.
None
3.6.6
Port is not displayed in link aggregation if it is configured with on mode
In Cisco ASR 900 devices, ethernet link aggregation port is not displayed if it is configured with bundle id 73 mode on.
None
3.6.6
RP Mgmt port modeled as GigabitEthernet for CRS_3.4.3
For Cisco IOS XR 3.7.0, RP Mgmt port is modeled as GigabitEthernet port.
This issue occurs when the entAliasMappingIdentifier entry gets corrupted. This entry get corrupted when mgmtethernet interfaces or controlethernet interfaces are present on the device.
None
3.6.6
BFD link state does not change
The BFD link remains in major state (in orange color) even after the BFD session is in up state. This issue occurs because the ticket is not closed even after the device is polled
None
3.6.6
Incomplete Part ID and Pluggable Type for Cisco GE SX modules on a Cisco CRS device.
Cisco ANA displays incomplete Part ID and Pluggable Type for Cisco GE SX modules on a Cisco CRS device.
None
3.6.6
The trap cefc module oper statusTraps is not properly associated
The traps cefc module oper status are not properly associated in Cisco ANA NetworkVision (Physical Inventory > Chassis > Slot). This issue occurs when you add a VNE and then pull out the module and push it back in.
None
3.6.6
Ticket, Card Down is not cleared
The ticket, Card Down is not cleared when the card is inserted in the device. This issue occurs when you:
1.
2.
3.
4.
5.
None
3.6.6
Cisco 12406 GSR: Wrong card description is displayed
Cisco ANA displays the incorrect card description for the Cisco 12406 GSR.
The issue is due to the EEPROM configuration on the module.
None
3.6.6
CSCsz56260
For DWDM modules, laser status is not modeled and G.709 status is incorrect
Cisco ANA does not model the laser status, and G.709 status is modeled with a set of signals instead of "enable/disable."
None
3.6.6
Client memory got to 99% after it stayed open for the weekend
The memory consumption reached 99% when Cisco ANA NetworkVision application ran continuously for a few days.
Relaunch Cisco ANA NetworkVision.
3.6.6
VNEs are stuck in the Initializing state
When you load the VNEs using the vne_creation_script.pl script, the VNEs remain in the Initializing state.
Either restart the units or load a few VNEs at a time.
3.6.6
IPV6 VRF interface is displayed in the interface table
For Cisco ASR 1000 devices, the IPV6 VRF interface is displayed in the interface table instead of VRF.
None
3.6.6
Empty lines are displayed for non-Administrator users
For user with the Viewer role, a few extra entries are seen between the physical interface and VRFs in the Links view.
This issue occurs when you:
1.
2.
3.
4.
5.
None
3.6.6
Java crash in AVM11
This issue is seen when Cisco ANA is managing 15K VNEs. After running Cisco ANA for a few hours, AVM11 crashes with the following error:
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (434F4E43555252454E542D41524B335745455027454E45524154494F4E0E4350501177 01), pid=25992, tid=6
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_13-b06 mixed mode)
# An error report file with more information is saved as hs_err_pid25992.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Restart Cisco ANA gateway by entering the command:
./mvm.cshFor details, see Cisco Active Network Abstraction 3.6.6 Administrator User Guide.
3.6.6
Attributes such as, clocking, framing, loopback, scrambling are not populated
Cisco ANA does not display loopback, scrambling, clocking, and framing details for Cisco 7200 with SRD1 image.
None
3.6.6
An alarm is not generated when a VNE is switched back to the regular polling rate.
When a VNE is switched back to the regular polling rate, the service alarm is not generated if the CPU level goes below the lower threshold of 70%.
None
3.6.6
Missing MPLSTEProperties for sub-interfaces in Cisco CRS devices.
MPLSTEProperties for sub-interfaces are not populated in Cisco ANA. Null pointer exception is displayed while fetching the admin weight attribute.
None
3.6.6
Missing BGPNeighbors under BGP Table for Cisco devices running Cisco IOS XR software image.
If you are having IPv4 and IPv6 addresses in your network, the Cisco ANA does not fetch the BGP neighbor information for IPv6 address. Also, while fetching the information for IPv4 address, if IPv6 device is found, Cisco ANA stops populating the information for the remaining BGP neighbors even though if the devices contains IPv4 address.
None
3.6.6
LDP Neighbor Peers are not populated in Cisco CRS devices due to Network Processing Engine.
Null Pointer exception occurs in LDPneighbor parser. The LDP Neighbor information is not modeled for Cisco CRS devices in Cisco ANA.
None
3.6.6
Cisco ANA 3.6.6 installation and uninstallation takes a longer time
While using the script, update.pl. Cisco ANA 3.6.6 installation and uninstallation takes a longer time with the following message:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
This issue occurs because the update.pl script updates the database and it may take a longer time if the size for the following database tables are large:
•
•
•
•
•
•
You do not have to perform any action. The installation process continues after the database tables are updated.
None
3.6.6
Correlation issue between Interface Status and Link Down tickets
There is no correlation when the events, Interface Status Down and Link Down Events Due to Admin Down occur.
This issue occurs because syslog is not sent to Cisco ANA AVM100.
Ensure that both the devices are configured to send the syslog messages to Cisco ANA AVM100.
If one of the devices is not sending Syslogs the correlation is effected.
3.6.6
No exception is displayed when you readd an existing link in maintenance mode using BQL query.
No exception is displayed when you perform the following steps:
1.
2.
None
3.6.6
Redundancy for RP is shown none in Cisco 12000 series devices.
For Cisco 12000 series devices running software version Cisco IOS XR 3.7.1, the Redundancy State and Configured fields for active RP is displayed as none instead of Active in Physical Inventory.
None
3.6.6
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 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, Cisco ANA NetworkVision displays Access instead of Dot1q-Tunnel for the VlanInterface mode.
Enter the following command:
show dot1q-tunnel3.6.5
Cisco ANA EventVision froze after two weeks
The Cisco ANA EventVision GUI froze after it was open continuously for two weeks.
Close and restart Cisco ANA EventVision.
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 Cisco ANA NetworkVision as a container.
To check the pseudowire configuration on the device, enter the following command:
show l2vpn x-connect type ac-pw detail
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
Issue with memory distribution on a unit server
If you are running Cisco ANA for several days, the memory consumption on the Cisco ANA unit server grows to 16 GB. Because of this, the link may disappear in the maps.
Option 1:
Move some AVMs from the Cisco ANA unit server to the Cisco ANA gateway server.
Option 2:
1.
2.
3.
4.
3.6.5
Memory leak when removing a VNE from the gateway
Memory leak occurs on the Cisco ANA gateway server when a VNE is removed.
None
3.6.5
redirect.pl cannot handle 735 syslogs per second
Some of the syslogs that are sent are not received in AVM100. This issue is seen on the Sun SPARC Enterprise T5220 server.
1.
2.
3.
Where PID#1 is the PID of the first redirectUdp.pl process.4.
Where PID#2 is the PID of the second redirectUdp.pl process.5.
scripts/
redirectUdp162.sh.6.
scripts/
redirectUdp514.shNote
3.6.5
Wrong options displayed on the map link filter.
The IP and Unknown links are displayed in the Cisco ANA NetworkVision view.
The IP and Unknown links are not supported in Cisco ANA.
You can filter the links based on a predefined set of link types or by manually configuring a customized set of link types. See Cisco Active Network Abstraction 3.6.6 User Guide for more details.
3.6.5
Clear all ticket does not put the VNE into the green state.
The VNE state remains unchanged (in the orange state) even after the ticket is cleared and removed.
None
3.6.5
Port name shown only for pseudowire sides in the down state
When the link is in the down state, the port name is shown only for a pseudowire.
None
3.6.5
PathTracer displays the wrong path
PathTracer does not display the correct path for packets. The final destination is not reached. However, the path is displayed correctly for the neighboring devices.
None
3.6.5
External Launcher menu does not pop up if using String match expression
The External Launcher menu is not displayed if only a parameter and String matching expression is used in the BQL set command.
You must use the parameter "com.sheer.imo.IManagedElement:IP" (management IP address of the network element) in BQL command for adding External Launcher menu.
3.6.5
BQL adapter does not raise an error when the BQL command contain invalid data
If the IMO property name is wrongly entered while creating a BQL command, the BQL disregards this property without giving an error.
None
3.6.5
Module shown with unsupported event for Cisco 12000 series devices with Cisco IOS XR.
SPA-IPSEC-2G-2 module is displayed with unsupported event.
None.
3.6.6
Error in Registry editor
Error in Registry editor.
None
3.6.5
Generic VNE inventory incorrectly displays 10G interface speed
Cisco ANA incorrectly displays the 10 G interface speed as 4294 Gbps for Generic VNE.
None
3.6.5
Subinterface not discovered
The subinterface is not populated in Cisco ANA.
This issue occurs because the subinterfaces are populated based on the technologies that are supported in Cisco ANA.
See Cisco Active Network Abstraction 3.6.6 VNE Reference Guide for details on the supported technologies.
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 PathTracer does not reach an IP interface configured on L3 Link Agg on Cisco CRS-1 devices
If you use Cisco ANA PathTracer 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
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
No description and no access-list entry appear in IP interface for Cisco GSR and Cisco CRS devices
In Cisco ANA 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 Cisco ANA 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 Cisco ANA 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 Cisco ANA NetworkVision.
4. Change the distribution protocol type to LDP on the device.
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
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
No expedite on local switching Card Out on Cisco CRS device
On Cisco CRS devices, the event Local Switching Entry Down is not correlated to a Card Out alarm.
None
3.6.4
Cisco ANA Path Tracer does not work properly
If you attempt to use Cisco ANA Path Tracer with a VRF configured for MPLS, Cisco ANA Path Tracer does not display the end-to-end results.
Verify that the VRF configuration is correct.
3.6.4
Tunnel reroute traps are not correlated to any ticket
The tunnel reroute trap generates Informational tickets and these tickets are not correlated.
None
3.6.4
Cisco Catalyst 6509 cannot connect to the cloud VNE
Cisco Catalyst 6509 cannot connect to the cloud VNE even though the configuration is similar to Cisco Catalyst 3560.
None
3.6.4
Cisco ANA is not polling information for fans and power supplies for Cisco XR 12000 devices.
Cisco ANA is not polling information for fans and power supplies for the devices that are running Cisco IOS XR software.
None
3.6.4
Cannot restrict maps on a user basis
Cannot assign maps to the user using Cisco ANA Manage.
You can assign maps to the user by updating a registry file. Changes to the registry should be performed only with the support of Cisco. For details please contact the Cisco ANA Project Manager or Cisco Account Team.
3.6.4
Repetitive commands are sent to the device
While discovering the network, VNE sends repetitive commands to the devices. This is causing delay in the discovery of the network.
None
3.6.4
Cisco ANA is raising MPLS black hole events for destination devices with VRFLite
Cisco ANA generates incorrect MPLS black hole events on the PE when the destination device is a VRFlite CE.
Disable MPLS black hole checking.
3.6.4
Tickets are not cleared
Tickets are not cleared even after the issue on the device or network has been resolved. The Correlation tab shows that the root alarm is cleared, but some of alarms that are correlated to it are not cleared and this is propagated to the overall ticket severity.
None
3.6.4
Cisco ANA alert processing is slow
When handling 12 events per second, Cisco ANA alert processing becomes extremely slow, resulting in delays from 1 to 2 hours.
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
New VNEs added after disaster recovery failover are in the Unreachable state.
In the High Availability Cisco ANA setup, after disaster recovery, the newly added VNE goes into the Unreachable state.
Restart the AVMs to remodel the VNEs. For details, see Cisco Active Network Abstraction 3.6.6 Administrator User Guide.
3.6.3
Occam: Stability problem in the device due to repeated polling
Occam devices exhibit issues related to stability and memory usage due to repeated polling of the device with the same set of commands.
Configure site.xml with a longer polling interval.
3.6.3
ECI Hi-FOCuS devices are not modeled
ECI Hi-FOCuS devices are not modeled.
None
3.6.2
Juniper routers Cross VRF information is wrong
Cisco ANA displays incorrect Cross VRF information for Juniper routers.
None
3.6.2
Improper modeling of Power and Fan modules of 6500VSS
If you add a VNE for a Cisco 6500 device, and then, in Cisco ANA NetworkVision, select Physical Inventor > Chassis > Shelf > Module, the Power and Fan modules for Chassis 1 are not displayed. However, they are displayed for Chassis 2
None
3.5.2
Resolved Caveats - Cisco ANA 3.6.6
The resolved caveats in Cisco ANA 3.6.6 are:
Related Documentation
User Guides
Cisco Active Network Abstraction 3.6.6 Documentation Guide
Cisco Active Network Abstraction 3.6.6 User Guide
Cisco Active Network Abstraction 3.6.6 MPLS User Guide
Cisco Active Network Abstraction 3.6.6 Technology Support and Information Model Reference Manual
Cisco Active Network Abstraction 3.6.6 VNE Reference Guide
Administrator Guides
Cisco Active Network Abstraction 3.6.6 Installation Guide
Cisco Active Network Abstraction 3.6.6 Administrator User Guide
Developer Guide
Cisco Active Network Abstraction 3.6.6 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
