Guest

CiscoWorks Campus Manager

Release Notes for Campus Manager 5.2 (With LMS 3.2)

  • Viewing Options

  • PDF (620.4 KB)
  • Feedback
Release Notes for Campus Manager 5.2 (With LMS 3.2)

Table Of Contents

Release Notes for Campus Manager 5.2 (With LMS 3.2)

New Features

Product Documentation

Related Documentation

Additional Information Online

Support Information

Caveats

Known Problems

General Known Problems

Browser Known Problems

User Tracking Known Problems

Topology Services Known Problems

ANI Server Known Problems

VLAN Configuration Known Problems

Spanning Tree Protocol Known Problems

Virtual Network Manager Known Problems

Resolved Problems in Campus Manager 5.2

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Campus Manager 5.2 (With LMS 3.2)


Published: May 22, 2009

Revised: May 22, 2009, OL-19699-01

These release notes are for Campus Manager 5.2 on Windows and Solaris, part of the CiscoWorks family of products running on Windows and Solaris platforms.

These release notes provide:

New Features

Product Documentation

Related Documentation

Additional Information Online

Support Information

Caveats

Known Problems

Resolved Problems in Campus Manager 5.2

Obtaining Documentation, Obtaining Support, and Security Guidelines

New Features

The following are the new features and enhancements available in Campus Manager 5.2 on Windows and Solaris:

Virtual Network Manager

Support for IPv6

Port and Module Configuration

Reclaim Unused Up/Unused Down Report

Selective Backup and Restore

Rogue MAC Enhancement

Virtual Network Manager

Virtual Network Manager (VNM) is an application that works in conjunction with Campus Manager (CM), and Resource Manager Essentials (RME).

Virtual Network Manager generates VRF Readiness Report to provide information on the VRF readiness that help administrators identify the devices with hardware and software support available, in contrast to the required support to configure VRF. The VNM application also generates VRF Report to provide details of the number of devices participating in a VRF as well as the details of the VRFs span across Enterprise network.

Virtual Network Manager application is used to perform VRF configurations in an enterprise network. You can perform the VRF Configurations using the following configuration workflows: Create, Edit, Extend, and Delete VRF. You can assign multiple VLANs to a single VRF instance, using the Edge VLAN Configuration workflow.

The VNM application provides advanced capabilities to view the virtualization status of the links connecting devices, participating in a VRF. The link virtualization status is displayed in the Map view of Topology Services in Campus Manager. It also enables administrators to debug and troubleshoot an end-to-end connectivity of VRFs configured in an enterprise network.

Support for IPv6

IPv6 support in Campus Manager includes the following network scenarios:

Devices that may have IPv6 configured on their interfaces. These devices must have at least one IPv4 interface. Devices are managed using IPv4.

Hosts running IPv6 are supported in the User Tracking application.

Port and Module Configuration

The Port and Module Configuration is a feature provided by Resource Manager Essentials (RME). RME uses port data to provide the port and module configuration feature.

Campus Manager gets updated with the port configuration data while the Data Collection process is executed. In this release, the port configuration details collected by Campus Manager is forwarded to RME, which is stored in the database of RME.

Reclaim Unused Up/Unused Down Report

This report displays both Link and Access ports that are used at least once but have not been used for a specific number of days. This report is an enhancement of UT Reclaim reports of Campus Manager 5.1.

Campus Manager 5.2 uses the data from Data Collection to retrieve the free up/down Link and Access Ports to generate reports. While running the Data Collection process, the timestamp information specific to the Data Collection is added to the ports.

Selective Backup and Restore

You can selectively Backup and Restore the configuration files and specific tables in data bases.

You can also back up the schema, stored procedures, and tables that are specified in the configuration file of Campus Manager. Applications will ensure that the selected tables include all dependent tables for proper functioning as a part of Restore.

For all tables that are not specified in the configuration file of Campus Manager, blank tables are created so that Campus Manager can function properly. Selective backup and restore allows you to restore the settings that are similar to the settings provided by normal backup.

We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.

Rogue MAC Enhancement

As an enhancement, the Rogue MAC feature is enhanced with filters in the following reports: Quick Reports, End Host Reports, Active End Host Reports, IP Phone Reports and Custom Reports. The enhanced filters in the report operate on the column that you have selected and fetch records that contain the user input value.

The pattern field that allows you to search patterns for the MAC Address column, is enhanced to include the following separators: dot (.) or colon (:). You can also search the patterns for MAC Addresses without any separators.

Product Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 1 describes the product documentation that is available.

Table 1 Product Documentation 

Document Title
Available Formats

User Guide for Campus Manager 5.2

PDF on the LMS Documentation CD-ROM.

On Cisco.com at:
http://cisco.com/en/US/products/sw/cscowork/ps563/products_user_guide_list.html

Supported Devices Table for Campus Manager 5.2

On Cisco.com at this URL:
http://cisco.com/en/US/products/sw/cscowork/ps563/products_device_support_tables_list.html

Context-sensitive Online help

Select an option from the navigation tree, then click Help.

Click the Help button in the dialog box.


Related Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 2 describes the additional documentation that is available.

Table 2 Related Documentation 

Document Title
Available Formats

Release Notes for CiscoWorks Common Services 3.3

PDF on the LMS Documentation CD-ROM.

On Cisco.com at:
http://cisco.com/en/US/products/sw/cscowork/ps3996/prod_release_notes_list.html

Installing and Getting Started with CiscoWorks LAN Management Solution 3.2

Printed document that was included with the product.

PDF on the LMS Documentation CD-ROM.

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

User Guide for CiscoWorks Common Services 3.3

PDF on the LMS Documentation CD-ROM.

On Cisco.com at:
http://cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html

Data Migration Guide for CiscoWorks LAN Management Solution 3.2 (for Maintenance Customers)

PDF on the LMS Documentation CD-ROM.

On Cisco.com:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html


Additional Information Online

The following product specific information is available online:

Service Packs (SP) contain updated files necessary for the latest device support and fixes to known problems that are not available in Campus Manager 5.2. If you are a registered user, you can download SP for Campus Manager from:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus

Support Information

Campus Manager 5.2 supports only US-English and Japanese versions of Windows Operating Systems. It does not support any other language version. Set the default locale to US-English for US-English version and Japanese for Japanese version.

Caveats

Note the following:

Campus Manager requires a DNS server to function properly. Many commands operate erratically or not at all, if there is no DNS server on the network.

You cannot run Campus Manager from a browser invoked from an X-Window System since this is not supported. Install a browser on the client from which you wish to connect.

You can upgrade your operating system (OS) either before or after you upgrade Campus Manager. However, if you upgrade the OS after upgrading Campus Manager, you will not receive any OS-related patch warnings or service pack-related warnings.

Verify that the latest version of all required OS patches, service packs, and third-party device drivers are installed before proceeding with an OS upgrade.

Do not export an entire topology map to Visio. Instead, select and export particular devices or a segment of the network and export it.

Known Problems

This section describes the known problems in this release:

General Known Problems

Browser Known Problems

User Tracking Known Problems

Topology Services Known Problems

ANI Server Known Problems

VLAN Configuration Known Problems

Spanning Tree Protocol Known Problems

Virtual Network Manager Known Problems

General Known Problems

The table below lists the known problems that are not specific to any module in Campus Manager.

Table 3 General Known Problems 

Bug ID
Summary
Explanation

CSCsw39443

The Default Sort option for scheduled jobs is not supported.

The Default Sort option for scheduled jobs in Campus Manager reports, is not supported. However, the Default Sort option is provided in the immediate job reports.

Workaround:

None

CSCse39112

Rules created for Groups in Campus Manager do not work properly.

In the Campus Manager 5.2 Rules creation screen, DiscoveryStatus operator is changed from "=" to "equals".

If you have created a rule with "=" operator in the earlier versions of Campus Manager and upgrade it to Campus Manager 4.0.4 or above, the rule will not work.

Workaround:

1. Open the rule created in the older version of Campus.

2. Change "=" to "equals"

3. Save the rule.

CSCsi76700

Multiple Hostname Mismatch Java alert windows appear when you launch Topology services applications.

This is a bug in Java Webstart. It occurs when you:

1. Run the CiscoWorks Server in the Non SSL mode and work with Topology Services.

2. Change the mode to SSL.

3. Launch Topology services.

Workaround:

Clear jar cache from the Java plug-in and launch Topology services.

CSCsc24255

Improper error message while configuring IVR.

This problem occurs in the following scenario:

If you do not enter proper SNMP or Telnet credentials for a device in DCR, RME does not fetch Config details from that device.

When you try to configure IVR for that device in Campus Manager, the following error message appears:

Configuration failed. Archive does not 
exist.

Workaround:

Enter proper SNMP and Telnet credentials for the device in DCR.

Make sure that the device is managed by RME and Config archive details are available.

CSCsa22708

Campus Manager does not manage existing devices when you upgrade from higher device limit to lower device limit.

This problem occurs because Campus Manager performs a fresh discovery of the network to obtain the devices and does not import them from the earlier versions.

Workaround:

None.

CSCds88388

Cannot launch CiscoView on an IGX series device.

This occurs if you:

1. Launch Topology Services.

2. Open LAN Edge view.

3. Right-click on IGX series device and select CiscoView from the Context menu.

A dialog box appears.

4. Enter appropriate community strings, and CiscoView attempts to launch.

An error message appears.

Workaround:

Launch CiscoView on IGX series devices using Cisco WAN Manager.

CSCdm83204

Campus Manager applications do not work when you access CiscoWorks using http://localhost:1741

If you access CiscoWorks applications using http://localhost:1741 from a browser on the same machine that CiscoWorks server is installed on, Campus Manager suite of applications will not work.

Workaround:

Use full DNS name or IP address of server, even when accessing it locally.

CSCsy29024

If you Campus Manager uninstall process is not removing the log files and jobs

If you uninstall Campus Manager only from LMS, the log files and the scheduled jobs related to Campus must be removed from LMS.

The campus manager and VNM related log files must be removed from default location: NMSROOT/CSCOpx or var/adm/CSCOpx/log.

The scheduled CM and VNM jobs must be removed from the JRM table.

For VNM application, the velocity.log file is created in an improper location under NMSROOT and it is not getting deleted after uninstalling Campus Manager.


Browser Known Problems

The table below lists the browser related known problems existing in Campus Manager.

Table 4 Browser Known Problems 

Bug ID
Summary
Explanation

CSCsw51113

Issues in FireFox 3.0.

While using the User Tracking feature using Mozilla Firefox, the User Tracking application opens in a new tab.

Workaround:

None

CSCsi21974

Exporting port attributes report crashes the browser.

This occurs if you:

1. Launch port attributes report with more than 65,000 records.

2. Export the report in PDF format.

The browser crashes after three minutes.

Workaround:

None.


User Tracking Known Problems

Information displayed in a row might not reflect the most current network state. This is because User Tracking Discovery takes information from routers and switches.

Since these switches collect their information at different times, the information in a row reflects the state of the network or subnet at the time displayed in the Last Seen field.

The table below lists other User Tracking related known problems in Campus Manager.

Table 5 User Tracking Known Problems 

Bug ID
Summary
Explanation

CSCsu84974

UT Acquisition does support invalid UTF-8 character for Port Name and Device Name fields.

UT Acquisition does support invalid UTF-8 character for Port Name and Device Name fields.

Workaround:

Remove invalid character from Portsdata.xml file and restart Data Collection.

CSCsz15769

UT Custom report jobs are not shown if custom templates are deleted.

This problem occurs when you:

1. Create a Custom Report template for End Host or IP Phone job.

2. Schedule the End Host or IP Phone job with the custom report template.

In UT Report Jobs page, the job is displayed.

3. Delete the Custom report template from Custom Reports.

4. Re-launch the Report jobs page. The job is not shown.

The job is not displayed.

The job appears only if the Custom Report template exist in the custom reports.

Workaround:

None

CSCsa97284

UTLITE drops packets when data is sent at a higher rate.

UTLITE traps are processed by Campus Manager at the rate of 150 traps per second. If traps are sent at a higher rate, some packets get dropped.

Workaround:

Increase the buffer size to get a higher trap processing rate.

For details on configuring the buffer size, see User Guide for Campus Manager 5.2.

CSCse68687

DNS timeouts do not happen as per the timeout value set.

This bug occurs in the following scenario:

DNS entries are not present for some end hosts in the DNS Server.

In ut.properties file, set:

UT.nameResolution = both or wins

UT.nameResolution.dnsTimeout = 2000

Run UTMajor Acquisition with the above settings. Timeout for the end hosts not having entries in the DNS Server is more than two seconds. It takes approximately four seconds to timeout.

Workaround:

If your network does not have IP addresses configured in WINS Server, set UT.nameResolution = dns in ut.properties file.

This avoids unnecessary searching for name lookup in the WINS servers.

Set UT.nameResolution.threadThresholdPercentage=100 or more in the ut.properties file.

This ensures that the percentage failure for name lookup is not high.

CSCsh85533

Exporting User Tracking data through Data Extraction Engine results in an Out of Memory error.

When you export 250,000 User Tracking records through Data Extraction Engine, it displays an Out of Memory error. It is logged in NMSROOT/MDC/tomcat/logs/stdout.log.

Workaround:

None.

CSCsi54994

Launching printer friendly format of End host report takes a long time.

This occurs when you:

1. Launch Endhost report.

2. Click the Printer option.

3. Enter the range as 1-30000 in the printer dialog box.

To launch the printer friendly format for 30000 records, it takes around 15 minutes.

To launch the printer friendly format for History reports with 30000 records, it takes around 12 minutes.

Workaround:

None.

CSCse57193

Campus Manager does not resolve hostnames for endhosts added through SNMP traps in DHCP environment.

This occurs if you:

1. Configure an endhost as DHCP client to get IP Address from DHCP server.

2. Ensure that all IP Addresses in the DHCP Scope have DNS entries in DNS Server.

3. Enable DHCP Snooping on the switch to which the DHCP client is to be connected.

4. Connect DHCP client to the above mentioned Switch. This makes the switch send SNMP traps to Campus Manager

The SNMP trap is processed and IP Address of the end host is fetched from the DHCP Snooping MIB in the switch.

However the DNS name for the corresponding IP Address is not resolved. IP Address is displayed in the host name field.

Workaround:

None.

CSCsb17074

User Tracking does not discover hosts connected to devices with SNMPv3 credentials.

This occurs if:

You manage the following devices with SNMPv3 Credentials

Cisco Catalyst 2900XL

Cisco Catalyst 3500XL

Cisco Catalyst 3750

Cisco Catalyst 4000

And

If there are end hosts connected to these devices

Workaround:

Either manage the devices with SNMPv2 credentials

Or

Upgrade the Operating System in the devices to Cisco IOS 12.2(25)SEE.

CSCsa27118

User Tracking Report displays Port State as Static for dot1x authenticated ports.

User Tracking Report displays Port State as Static when an end host is connected to the switch port, that is configured for dot1x authentication.

This is because the device populates vmVlanType as Static for dot1x authenticated ports.

Workaround:

None

CSCsa20659

Purge Job is created although you delete it from User Tracking Report Jobs.

In User Tracking, Purge Job is created even if you try to delete it from the User Tracking Report Jobs and Common Services JRM pages.

It gets deleted and then re-created immediately afterwards. There is no functionality loss because of this.

Workaround:

None.

CSCsa14652

NAM and IDS Modules appear as end hosts in User Tracking.

Cisco Catalyst 6000 devices running native IOS service modules appear as end hosts in User Tracking.

This is caused by a problem on the device.

Workaround:

None.

CSCin00363

End host does not appear if obsolete device IP address is assigned.

If you connect a CDP device to the port and then add a new end host, this new end host is not learnt. This is because ANI is not aware of such a change.

Workaround:

1. Delete the specific device.

2. Perform Data Collection for the neighboring devices.

3. Perform User Tracking Discovery for that device.

CSCin00181

Last Seen field gets updated for disconnected IP phones.

The Last Seen field in Phone Tracking corresponds only to the Last Seen field on Cisco CallManager and not to the Last Seen field on Network.

Workaround:

None.

CSCdw04499

End hosts are not discovered with Catalyst 3550 running Cisco IOS Release 12.1(6)EA1 or earlier.

End hosts are not discovered with Catalyst 3550 XL running Cisco IOS Release 12.1(4)EA1 and Cisco IOS release 12.1(6)EA1.

Workaround:

This problem has been fixed in Cisco IOS release 12.1(6)EA1a. Upgrade to this version.

CSCdw04486

End hosts not discovered with Catalyst 2950 running a software release earlier than Cisco IOS Release 12.0(5)WC2.

End hosts not discovered with Catalyst 2950 running a software release earlier than Cisco IOS Release 12.0(5)WC2.

Workaround:

This problem has been fixed in Cisco IOS Release 12.0(5)WC2. Upgrade to this version.

CSCdt25525

User Tracking Main Table sometimes displays CDP-enabled devices that are outside the ANI discovery boundary.

During User Tracking discovery, User Tracking reads entries from the CAM table. These entries may include MAC addresses of devices that fall outside the ANI discovery boundary.

Workaround:

None.

CSCdt06183

User Tracking Main Table may not display all entries that are displayed in the phone table.

User Tracking entries shown in the Main Table are discovered from network. However, User Tracking entries shown in the phone table are read from Cisco CallManager.

If User Tracking cannot discover particular phones in the network, entries for such phones in the User Tracking phone table will not have device and port information.

Workaround:

Ensure that the switch to which the IP Phones are connected, is managed by Campus Manager.

CSCdr85384

Phone entries displayed by User Tracking differ from entries displayed by Cisco CallManager.

User Tracking phone entries acquired through SNMP for each Cisco CallManager may be different from entries in Cisco CallManager.

The Cisco CallManager database displays a historical record of all phones registered to Cisco CallManager.

The SNMP agent retains only records of phones registered since the agent was started. This accounts for any differences.

Workaround:

None.

CSCsd58215

DNS resolution for end user entries takes an inordinate amount of time.

DNS resolution, which occurs for end hosts discovered in user tracking, takes a long time to timeout if the DNS resolution for the corresponding IP address is not available in the DNS Server.

This is because Campus Manager waits for a response from the DNS Server before exiting.

Workaround:

Set the property Ani.resolve=false in ANIServer.properties.

CSCse79161

User Tracking does not discover endhosts using SNMPv3 if the endhosts are connected to some of the Catalyst IOS devices such as Catalyst 2900, Catalyst 4000 and Catalyst 6000.

This problem is caused by insufficient support for SNMPv3 - VLAN based context names in Catalyst IOS devices.

Workaround:

This problem has been fixed in recent Catalyst IOS image versions 12.2 and above for some devices. So ensure that the devices are running these versions of Catalyst IOS.

Also, check whether the image supports
SNMPv3 - VLAN based indexing for those device types.

If the device does not have support for
SNMPv3 - VLAN based context names in Catalyst IOS, remove SNMPv3 credentials from DCR and manage the device using SNMPv2.

CSCsq55637

In VSS mode, the User Tracking report does not display the endhosts connected to standby devices.

In standalone mode, if User Tracking is run for standby devices, the User Tracking report displays all the endhosts connected to the standby devices.

If you convert the mode to VSS, the interface to which the endhosts are connected becomes unreachable. These endhosts will not be displayed in the User Tracking report.

Workaround:

If you convert to VSS mode, the interface notation format will be changed to x/y/z format. Where x is switch ID and y/z are slot/port IDs

In an active VSS switch:

1. Change the notation to x/y/z format and assign them to an access VLAN.

2. Launch the User Tracking report

The endhosts connected to the standby devices will be displayed in the report.


Topology Services Known Problems

Table 6 lists the Topology Services related known problems in Campus Manager.

Table 6 Topology Services Known Problems 

Bug ID
Summary
Explanation

CSCsw90100

Automatic Refresh option of Topology Services at the client side, does not work as expected.

After the VNM Collection has completed, the Automatic Refresh option of Topology Services at the Client side, does not work as expected.

Workaround:

Close and re-open the Topology Services page manually.

CSCsw84667

The devices deleted in the ACS server are not reflected in the Topology Map View.

The devices deleted in the ACS Server are not displayed in the Topology Map View.

This occurs if you:

1. Integrate CisoWorks with ACS Server.

2. Go to Campus Manger > Admin > Topology > Restricted Topology View.

3. Enable Display only the Authorized Devices in Topology Maps and click Apply.

4. Launch Topology Services.

5. In Network View, choose Layer 2 View.

6. Right-click Layer 2 View and select Display View.

7. Delete a device in the ACS server.

Ideally, the deleted device should be reflected in the Topo Layer 2 view device count as well as in the Map View. The deleted device is not reflected in the Layer 2 and Map view.

8. In the ACS server, change the User setup to per Network Device Group Basis.

The changes in the User setup are not reflected in the Topo Maps as they should be.

9. Make some changes in a particular device, such as change the VTP Domain.

10. Run Data Collection for a particular device.

11. Close Topology Services and launch it again.

Errors are displayed in the Java Console.

Workaround:

None

CSCsz16391

You cannot cross-launch other applications from Topology Services.

If you install JRE1.6.0_13 or higher version of JRE at the client side and launch Topology Services, you cannot cross-launch any applications or features from Topology Services.

This happens because of a JRE problem.

Workaround:

None

CSCsh20449

RMON configuration fails on Cluster Member switches.

If you perform RMON configuration on a Cluster Member switch, it fails and displays a message SNMP credentials required.

This happens although the credentials are available in DCR.

Workaround:

None.

CSCsh41208

Topology Services does not support deleting 1000 devices at a time.

When you try to delete 1000 or more devices at a time from Topology maps, nothing happens.

No error message is displayed. No errors are recorded in the ANI log file.

Workaround:

Delete in batches of 500 devices.

If you are managing 1000 devices in Campus Manager and need to delete all of them, reinitialize the database instead of deleting the devices from Topology Services.

For details on reinitializing the database, see User Guide for Campus Manager 5.2.

CSCsi11610

Background image cannot be set if the image name has spaces in it.

In Topology views, background image cannot be set if the image name contains spaces.

If you drag the devices in that view, the device icons get cluttered.

Example: Hello World.jpg

Workaround:

Set a background image where the image name does not have spaces.

CSCse26688

Cannot launch Device Attributes report for more than 3000 devices.

This occurs if you:

1. Select 3000 devices or more from Layer 2 view in Topology Services.

2. Launch Device Attributes report.

Out of Memory error is displayed in the Java Console.

Workaround:

None.

CSCsh18809

Launching Topology Services after performing Single Device Data Collection, displays errors.

This occurs if you:

1. Make some changes in the device, such as changing the VTP Domain.

2. Run Data Collection for that device.

3. Close Topology Services and launch it again.

Errors are displayed in the Java Console. This issue does not occur consistently.

Workaround:

1. Log out of CiscoWorks and log in again.

2. Launch Topology Services.

It launches without any errors.

CSCsg67273

Changes are not reflected in Topology Services after doing Single Device Data Collection.

This occurs if you:

1. Launch Topology Services.

2. Select a domain which has only one device in it.

3. Use Telnet to connect to that device and change the VTP domain to any other name.

4. Perform single device data collection from Topology Services.

5. Collapse the tree view in the left pane of Topology Services window.

6. Select View > Reload from the menu.

7. Select View > Refresh Summary from the menu.

8. Open the VTP view in which the device was present.

The view still displays the old VTP domain name.

Workaround:

Close Topology Services and launch it again.

CSCsh71141

N-Hop View Portlet shows wrong device icon for MSFC Switch.

N-Hop View Portlet shows wrong device icon for switches with Multilayer Switch Feature Card (MSFC), if:

The device is on the edge of the network.

The device is on the edge of the topology map displayed in the N-Hop view portlet.

In this case, no options are displayed when you select the device. You cannot use Telnet to connect to the device or launch other applications.

Workaround:

None.

CSCsa27318

Topology Services displays an error, OutOfMemoryError, while working with 3000 devices.

When you save the layouts and re-start topology map after using Topology Map tools such as zoom and drag, Java console displays an error: java.lang.OutOfMemoryError.

Workaround:

1. Go to the Java Plugin Control panel and select the Advanced tab.

2. Add Xmx512m to the existing Java Runtime Parameters.

CSCsa25203

Campus Manager does not generate Time Domain Reflectometry (TDR) Report for Cisco 3750 and Cisco 4000 series switches.

Campus Manager displays a blank report when you run TDR test on Cisco 3750 and Cisco 4000 series switches.

This is because MIBs are not available to support TDR feature on these devices.

Workaround:

None.

CSCsa22699

Inter-VLAN Routing configuration user interface (UI) does not differentiate primary and secondary IP addresses.

Inter-VLAN Routing configuration user interface shows multiple entries for the same interface when you configure primary and secondary IP addresses for SVI or sub-interfaces.

The UI does not clearly differentiate the primary and secondary IP addresses.

Workaround:

This problem does not occur in Cisco IOS Release 12.1(20)E3 or later.

CSCsa18405

In PVLAN configuration, the secondary VLAN creation and association to Primary VLAN fail on Cisco Catalyst Operating System version 8.1.

In devices with Cisco Catalyst Operating System version 8.1, Secondary VLAN creation and association with Primary VLAN fail if the device is running on version VTP version 3.

Workaround:

Either:

Upgrade to Cisco Catalyst Operating System version 8.2.

Or

Change VTP version to 2 and VTP mode to transparent.

CSCsa12292

VLANs are not loaded for STP Offline Computation.

This problem occurs in Topology Services when you:

1. Launch STP Offline for PVST From the Topology Map.

2. Go to Reports > VLAN STP > Recommendations > STP Offline

3. Click Select Instance.

No VLANs are loaded.

Devices that do not support CISCO-STP-EXTENSIONS-MIB will not support any STP related functionality.

Workaround:

None

CSCsa11888

Channel or Trunk cannot be configured because of STP recalculation.

Campus Manager sets the channel mode to Desirable Non-silent on the selected devices to be channelled. However, STP state changes occur when any mode change happens.

So, if one of the two devices of the channel is an end-device and is only reachable through the to-be-channelled links, the device cannot be reached until the spanning-tree converges.

Workaround:

None.

CSCsa10216

Incorrect VTP version displayed in VTP reports.

This problem occurs in Topology Services:

The VTP Report displays the VTP version as 1 while the actual VTP version running on the device is VTP version 2.

This issue is seen only with some of the Cisco Catalyst platforms such as Catalyst 4506, Catalyst 3750G, Catalyst 2900.

Workaround:

None.

CSCsa04026

Link line or connection between two devices gets warped, if one device is moved.

This problem is seen in Topology services display map.

When there is a long line between devices and you drag a device to a different location on the map, a kink develops in the line. The link line connecting these two devices gets warped.

The line appears jagged, instead of being straight.

Workaround:

Keep the devices closer to one another.

CSCin68983

Cannot configure Trunk between Catalyst 2900XL and Catalyst 3500XL devices.

Trunk configuration fails between Catalyst 2900XL and Catalyst 3548XL series switches.

This is caused by lack of MIB support.

Workaround:

None.

CSCin48159

Cannot launch IDSM from Service Modules launch point for IDSM2 card of Cisco Catalyst 6000 device.

From Topology Services, you cannot start IDSM using the Service Module launch point. This is because of a defect in SNMP agent of the device.

Workaround:

None.

CSCin46641

Campus Manager does not calculate Trunk mode related discrepancies.

Topology Services does not report the following discrepancies for Cisco Catalyst 2900 series, 3500 series, and 4000 IOS devices, in Trunk mode.

AutoTrunk

NoTrunk

TrunkNegotiationEnabled

This is because of the lack of MIB support in the devices.

Workaround:

None.

CSCin46405

Campus Manager does not report Spanning Tree discrepancies for some devices.

Campus Manager does not report the following Spanning Tree discrepancies for some devices:

BackboneFastDisabled

UplinkFastDisabled

BPDUGuarDisabled

STPEnabledOnAccessPorts

This is because of lack of MIB support in the devices.

Workaround:

None.

CSCin46370

Trunk Negotiation Enabled Discrepancy Report does not show the Trunk mode details of the ports of some devices.

TrunkNegotiationEnabled Discrepancy Report does not show Trunk mode details of the ports on Cisco Catalyst 2950, Cisco Catalyst 3550, and Cisco Catalyst 4000 IOS devices.

This is because of a defect in the SNMP agent of the device.

Workaround:

None.

CSCin45496

Campus Manager does not report UDLD discrepancy for Cisco Catalyst 2900 series switches.

Discrepancy Reports does not display UDLD disabled discrepancy for Cisco Catalyst 2900 switches.

This is because of a defect in the SNMP agent of the device.

Workaround:

None.

CSCin45070

Launch points do not work if http/https ports have other than the default value.

In Topology Services, the launch points for Service Modules function only if the http/https port numbers are set to their default value.

Launch Points must function for any valid http/https port number configured on the service modules.

Workaround:

None.

CSCin43965

Spanning Tree reports more than one root for a switch cloud.

Spanning Tree reports more than one root for a switch cloud containing Cisco 2900XL, Cisco 3500XL, Cisco 2950, or Cisco 3550 devices, if the selected VLAN is not assigned to any of the ports in these devices.

This is because of a defect in SNMP agent of the devices.

Workaround:

None.

CSCin36950

Cannot view VCs in a tunnel from Topology Services main window.

This problem occurs in Topology Services when you:

1. Setup a tunnel between two ATM devices and let the devices see each other as Interim Local Management Interface (ILMI) neighbors on their tunnel interfaces (subinterfaces) only.

2. Select Fabric view.

3. Select a device and its associated VP tunnel link.

4. Select Tools > ATM Management > Display VCs > Per device.

The device or port chooser does not list subinterfaces.

Workaround:

None.

CSCin29281

Device Attribute of Cisco Catalyst 6000 devices does not display the IP address.

Device Attribute of Cisco Catalyst 6000 devices does not display the IP address of WS-X6624-FXS module.

Instead, Device Attribute displays the IP address of Supervisor engine.

This is because of a defect in the SNMP agent on the device. For more details, see CSCin33075.

Workaround:

None.

CSCin27895

Topology Services does not show VLANs as active, if the switch is in NULL folder under VTP Domain.

If you select Topology Services > VTP Domains > NULL folder, it shows VLANs in VTP server devices as inactive, if the VTP Domain name is not configured on the device.

Topology Services displays the VLANs as inactive although the state of the VLAN on the switch is active.

Workaround:

Either:

Configure VTP domain name in the device and rediscover.

Or

Configure VTP domain mode of the device as transparent and rediscover.

CSCin22459

Topology Groups membership update does not work as expected.

This problem occurs in Topology Services when you:

1. Launch Custom Views for a group by selecting Campus Manager > Topology Services.

2. With the Custom Views window open, delete a device group using Topology Group Administration.

Custom View does not update automatically.

Workaround:

Re-open the Custom View window.

CSCef67937

Campus Manager does not show port as trunking if the port is part of the Channel.

This problem occurs when Cisco Catalyst 3750 has a 12.1 EA software version.

When a port is part of channel and configured as trunk, Campus Manager does not display the port as trunking for Cisco Catalyst 3750 switches.

Workaround:

Upgrade Cisco Catalyst 3750 device to 12.2(18)SE1 or later.

CSCeb68819

Topology Services does not display dual links.

When two devices with dual links are aligned vertically on top of each other, the co-ordinates of the vertices of both links become the same.

If the devices are not vertical, Topology Map displays dual links.

Workaround:

Relayout the maps using hierarchical or symmetrical layout, so that the devices do not align vertically.

CSCea39271

Topology Services displays the devices connected to a UB Token-Ring Hub in the Unconnected Devices View.

CiscoWorks discovers Cisco Catalyst 4700 and Catalyst 4500 devices, but displays them under Unconnected Devices View, and not in Layer 2 View.

Campus Manager cannot draw the map for the devices, as the routers are connected through a UB hub.

Workaround:

None.

CSCdw49136

Campus Manager cannot establish connection between ATM ELAN and Ethernet VLAN when you remove LEC from Cisco Catalyst 2900XL devices.

Initially, VLAN and ELAN are connected in Topology Services. When you remove LEC from Cisco Catalyst 2900XL devices, the connection between VLAN and ELAN is broken for 2900XL devices.

This is because of a bug on 2900XL agent devices, where it does not support CISCO-LEC-EXT MIB.

Workaround:

None

CSCdv41860

Fetching LANE component details displays an error AniSQLException.

In Topology Services, if you create a LANE component in an ATM switch (LS1010) and launch its view, all the Profile and Diagnosis menu items related to this component display the following error:

Internal error

Workaround:

None.

CSCdt50619

Two devices, connected by multiple links, appear to be connected by only one link.

When two devices are connected by multiple links, and you rediscover either devices or links, all of the links are stacked on one another.

This causes the devices to appear as if they are connected by only one link.

Workaround:

Perform a re-layout.

CSCdt27824

Entire list of ports in a VTP domain appear when you select certain Transparent VTP domains from the VLAN Assignment dialog box.

When similar VLAN definitions exist on a VTP server and transparent devices, VLAN is added under the parent folder and all transparent devices.

Thus, VLAN ports are displayed under all transparent devices.

Workaround:

Run Find Ports query and enter only device name or address to view ports for a particular device.

CSCdt18293

Visio drawing does not import cleanly into Microsoft Visio.

If you export a Topology map as a Visio drawing, it is not imported cleanly into Microsoft Visio.

Links are drawn out of place, and some incorrect links appear to be drawn between devices.

Workaround:

Clean the Visio drawing manually after import.

CSCdr11577

Virtual Circuit (VC) error chart is blank.

A blank chart could mean either a continuous polling failure or a failure caused by other problems.

For example, a blank VC error chart might be caused by a continuous polling failure (of VC error related data).

It could also be because these statistics may not be supported on certain image versions of the ATM switch, being polled.

Workaround:

None.

CSCdp88318

Link attributes are not updated after a change is made.

If you change link attributes, ANI Server does not properly discover and display the change in reports.

Workaround:

To update link attributes, close and relaunch Topology Services.

CSCso87643

Topology services displays unauthorized devices

In a stacked device, if one of the devices is authorized and the other one is not authorized, although the Topo ACS property is enabled, the Topology window also displays the unauthorized device.

Workaround:

None.

CSCsm82212

An unknown error occurs while launching the Topology map from an earlier version of Campus Manager after launching Campus Manager 5.2 topology map.

This error occurs when you:

1. Go to Campus Manager and launch CM 5.1 topology.

2. CM 5.0.x topology in the same machine.

An error occurs although the same JRE plugin is used for both CM versions.

Workaround:

To use the same JRE plugin, you must delete the jacorb-sign-1-3.jar file located in JRE LOCATION \Java\jre version \lib\endorsed folder in the client machine.

Do this before launching the topology of an earlier version of CM.

Alternatively, you can use different JRE plugins for different versions of CM.

CSCsm25505

Device Attribute and VLAN report fails when more than 200 devices are selected.

This problem occurs when you:

1. Launch Topology services.

2. Select more than 200 devices from Layer 2 View/LAN Edge View.

3. Launch Device Attribute report.

The following error message is displayed in the status bar:
Error occurred while displaying attributes.

The same problem is noticed when the VLAN report is launched.

Workaround:

Launch the report with less than 150 devices selected.

CSCsz23980

In LAN Edge view, the application throws a NullPointer exception in Java console.

If you manage devices in Campus Manager in a way that the devices are present only in the Unconnected view. Now, if you click on LAN Edge view, the application throws a NullPointer Exception in Java console.

Workaround:

None

CSCtf85580

Unable to launch Topology Service from Windows Vista client.

This problem occurs when you launch Topology Service from Windows Vista client after installing Java Plug-in 1.6.0_11.

Workaround:

1. Disable UAC when you download the jar files for the first time.

2. Lauch the Topology Service. If you are unable to launch the Topology Service, then go to Step 3.

3. Manually copy the jacorb-sign-1-3.jar, avalon-framework-4.1.5-sign-1-3.jar and logkit-1.2-sign-1-3.jar files from the location NMSROOT/campus/www/classpath in LMS server to JRE installed directory \lib\endorsed.

4. Assign full control permission to jre/lib folder.


ANI Server Known Problems

The table below lists the ANI Server related known problems in Campus Manager.

Table 7 ANI Server Known Problems 

Bug ID
Summary
Explanation

CSCsf24921

Campus Manager does not load the DeviceDiscovery.properties file.

This occurs if you:

Repeatedly change Device Discovery settings

Upgrade from a previous version of Campus Manager

It corrupts the DeviceDiscovery.properties file. After this, you cannot start Device Discovery and it remains in an Idle state.

Workaround:

1. Delete the corrupted file.

2. Rename NMSROOT\campus\etc\cwsi\
DeviceDiscovery.properties.orig file

to

NMSROOT\campus\etc\cwsi\
DeviceDiscovery.properties

3. Use Campus Manager UI to re-enter the parameters.

CSCsi56555

PVLAN is not created after ANI server restart.

After restarting ANIServer, you cannot create PVLANs.

Workaround:

After restarting ANIServer, run Data Collection. After completion of Data Collection, configure PVLAN.

CSCsc43106

Device not discovered if SysUpTime is masked.

If the SysUpTime in masked in v1default view, Device Discovery does not discover the device.

Workaround:

Manually add the devices to DCR.

Or

Remove the mask in v1 default view.

CSCsa20827

Subnet based groups are not deleted from Campus Manager Topology Groups although you delete them from DCR.

In DCR, if you delete all devices or all devices in a subnet, the corresponding subnet based groups in Campus Manager are not deleted immediately.

Workaround:

If you want the subnet groups to be deleted earlier than 20 minutes, change the property from:

SubnetPollerConfigTime = 1200000 

to a lesser value in the properties file:

NMSROOT/MDC/tomcat/webapps/campus/WEB-INF/classes/CM_Implementation_Details.properties.

CSCsa19337

ANI goes into Unknown State when you delete all devices from DCR.

This problem occurs in ANI when you:

1. Discover some devices by specifying seed devices in Campus Manager.

The DCR is updated with those devices.

2. Run Data Collection on those devices.

3. Invoke Topology Services.

Devices appear in Views.

Deleting all devices from DCR will show ANI state and UT state as Unknown although you specify the seed devices in Device Discovery settings.

Workaround:

None.

CSCin74855

Devices are not managed in Campus Manager if management IP is not in ACS.

This problem is seen in ANI.

If a device has multiple IP addresses, Campus Manager automatically determines the management IP address of the device.

If the management IP address is not ACS (that is, the device is added in ACS with a different address), this device is not managed in Campus Manager. Data collection is not done for this device.

Workaround:

IP address in ACS and management IP address in DCR should be the same.

CSCin33112

Cannot delete devices on a remote system in SSL mode using the command line interface.

The Delete Device command fails if you use it on a remote server in the SSL mode.

Workaround:

None.

CSCdy31689

User Tracking Discovery stops responding when you refresh Discovery Metrics page.

In large networks, sometimes, when you refresh the Discovery Metrics page, ANI hangs after partially completing Device Discovery, and does not display any high CPU usage.

The is because of a known problem in JRE caching of DNS look ups.

Workaround:

1. Stop the Daemon Manager.

2. Edit the registry for:

HKEY_LOCAL_MACHINE\SOFTWARE\
Cisco\Resource Manager\CurrentVersion\
Daemons\ANIServer\Args

3. Modify the value of:

-cp:a C:\PROGRA~1\CSCOpx\lib\classpath\
servlet.jar -Dvbroker.orb.gcTimeout=90 -mx512m com.cisco.nm.ani.server.frontend.AniMain

to

-Xminf0.1 -Xmaxf0.1 -cp:a C:\PROGRA~1\CSCOpx\lib\classpath\
servlet.jar -Dvbroker.orb.gcTimeout=90 -Dsun.net.inetaddr.ttl=0 -mx1024m com.cisco.nm.ani.server.frontend.AniMain

4. Start Daemon Manager.

CSCdw67129

Topology Services cannot resolve the hostname of newly discovered devices.

If you add the DNS entry for the devices after initial Discovery, Topology Services cannot resolve the hostname of the newly discovered devices.

The subsequent Discoveries do not resolve the IP address to a hostname until the ANIServer reloads.

This occurs only in devices that do not have a DNS entry before Discovery. Devices that have a DNS entry before ANI discovers them, do not have this problem.

Workaround:

Do either of the following:

Restart CiscoWorks Server. ANI resolves the IP address to a hostname after restart.

Or

1. Display the sysName in Topology Services (does not require a restart).

2. Select Topology Services > Layer 2 View > View > Display Labels > Show Sysname

Alternatively, you can do any of the following:

Run Device Discovery again.

Stop and start the ANIServer.

If you require Campus Manager to ignore the cache and always look up the DNS server, add the following variable in the Java command line of the ANIServer:

Dnetworkaddress.cache.ttl=0

CSCdp76410

Campus Manager client cannot connect to server using proxies.

Campus Manager does not support proxies.

Workaround:

None

CSCdm58624

Campus Manager reports VTP Disconnected Domain discrepancy when VTP Domain is configured across a LANE Trunk.

Campus Manager reports Disconnected Domain discrepancy even when VTP domain is configured across ATM cloud and the default ATM-VLAN is configured to carry VTP advertisements across the cloud.

Workaround:

Ignore the discrepancy.

CSCsb52873

ANI Server fails to start

This problem occurs when you:

Start ANI Server, the server is up for sometime and shuts down with RC as -2 and Info as ANI Server failed to load from the database.

Workaround:

Stop the Daemon Manager. Re-initialize ANI database and start the daemons.

Enter the following command to reinitialize ANI database:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbRestoreOrig.pl dsn=ani dmprefix=ANI


VLAN Configuration Known Problems

The table below lists the VLAN Configuration related known problems in Campus Manager.

Table 8 VLAN Configuration Known Problems 

Bug ID
Summary
Explanation

CSCsi30755

Ports are not listed properly when shared VLANs are deleted.

This problem occurs in this condition:

Assume that a VLAN is present in the all transparent devices in the VTP domain (shared VLAN).

If you:

1. Go to the VLAN Configuration page

2. Select a shared VLAN from VTP server and delete it.

3. Navigate using Move Affected Ports to new VLAN page:

Along with the ports associated with the VTP server is shown, the ports associated with Client and the Transparent switches in the domain are also listed.

You can move the ports of the deleted shared VLAN only to other shared VLANs.

Workaround:

None.

CSCsi85533

Wrong error message displayed when you try to create VLANs in VTPv3 server.

VLAN creation on VTPv3 servers are not supported. When you try to do this, Campus Manager displays the following error message:

There has occurred some error during configuration. The device may be snmp unreacheable.Pls check the device.

NMSROOT\log\ani.log records the following error: SNMP illegal value is set.

Workaround:

None.

CSCsc24275

VLAN interfaces created through IVR are not shown in the existing interface list for that device.

If the corresponding VLAN on which the new VLAN interface is being created does not already exist in the device, the interface is not shown in the list.

Workaround:

Create a VLAN in the device before you create VLAN interfaces.

Or

Create interfaces for existing VLANs in the device.

CSCdw09818

Port Attribute in VLAN Port Assignment displays incorrect information.

This problem is observed only on inactive ports. The MIB values returned by the devices, latch onto the previous speed and duplex properties.

This is because of a defect in SNMP agent of the device.

Workaround:

None.


Spanning Tree Protocol Known Problems

The table below lists the Spanning Tree Protocol related known problems in Campus Manager.

Table 9 Spanning Tree Protocol Known Problems 

Bug ID
Summary
Explanation

CSCsg92439

Campus Manager does not compute the correct number of instances, when there are redundant links between switches.

This occurs if you:

1. Configure redundant links between switches.

2. Invoke MISTP or MST recommendations for a switch cloud that has redundant links.

3. Choose Max Instances for better link utilization and click Compute.

Campus Manager does not compute the correct number of instances for better link utilization.

However, the above computation works well when Ether channel is configured on switches with redundant links.

Workaround:

None.

CSCsa12292

VLANs not loaded for STP Offline Computation.

This problem occurs in STP when you:

1. Launch STP Offline for PVST From the Topology Map.

2. Go to Reports > VLAN STP Recommendations > STP Offline

3. Click Select Instance

No VLANs are loaded.

Devices that do not support CISCO-STP-EXTENSIONS-MIB will not support any STP related functionality.

Workaround:

None.

CSCsa09287

Cannot map VLANs to instance if the device runs MISTP.

In STP, if the device is running STP type as MIST, configuring the instance to VLAN mapping from STPConfiguationReport > InstanceTab is not applied on the device.

This is caused by an SNMP Agent problem.

Workaround:

None.

CSCin67279

Community suffix support is not available for MST on Cisco IOS switches.

In STP, community suffix support is not available for MST and MISTP on Cisco IOS switches.

Workaround:

None.

CSCed72194

MST device report does not report CIST root correctly.

In STP, MST device report may not report the CIST root properly.

This is because the dot1dStpDesignatedRootCost object corresponds to external root path cost. Hence the value of the object is 0 for all switches in the MST region that contains CIST root.

Workaround:

None.


Virtual Network Manager Known Problems

The table below lists the Virtual Network Manager related known problems in Campus Manager.

Table 10 Virtual Network Manager Known Problems 

Bug ID
Summary
Explanation

CSCsw30582

The Export option does not work in the VNM Readiness Report.

This problem occurs if you:

1. Launch VRF Readiness Report from Virtual Network Manager > Report Generator.

The Readiness Report is generated.

2. In the Readiness Report, click the Export icon.

The report is not exported in either CSV or PDF format.

Workaround:

None

CSCsw36595

The values you enter in the VLAN to VRF Mapping page are deleted if you click the Toggle icon.

The values that you enter in the VLAN to VRF Mapping page are not retained after you click the Toggle icon.

This happens because of the CUES issue in Virtual Network Manager (VNM).

Workaround:

None

CSCsw45726

The Device Center page does not display the reports generated by VNM.

The Device Center page does not display the reports generated by VNM.

Workaround:

None

CSCsw74869

You can launch VNM from the Layer 2 devices in Topology Services.

You can launch VNM from the Layer 2 devices displayed in the Topology Services should not launch VNM.

Currently, VNM does not support pure Layer 2 devices. Therefore, launching VNM from Layer 2 devices must be restricted.

Workaround:

None

CSCsw80285

In the Edge VLAN Configuraton workflow, if you assign a null VLAN to a VRF, the VLAN to VRF Mapping page does not list the virtual interfaces for the null VLAN.

This problem occurs when:

1. Select an interface (SI) virtualized with the selected VRF, in the Edge VLAN Configuration workflow.

2. Assign a null VLAN.

The VLAN to VRF Mapping page does not list the ports if the VLAN assigned is null.

This happens because the Edge VLAN Configuration workflow does not display virtual interfaces with null VLANIDs.

This is because VLAN communication does not occur on the particular virtual interface.

Workaround:

None.

CSCsw63053

The VNM Home page displays a VRF without an RD value with device count as zero. VRF without RD value, is an improper configuration.

The VNM Home page displays a VRF without an RD value with device count as zero.

A VRF without an RD value, is an improper configuration.

Workaround:

None

CSCsz55346

In VNM home page,page number validation is not happening in VRF LIST paging table.

Stop the JRM process and launch VNM. In the VNM home page, the VRF list does not get displayed. It is loaded with 0 pages.

Ideally, when you launch VNM, the VRF List must be loaded by default.

Workaround:

Enter a valid page number and press enter, the VRF List is loaded.

CSCsz63228

VRF Collection process does not run after the completion of Data Collection process.

If you stop and start the JRM process, VRF Collection process is not triggered after the completion of the Data Collection process.

In spite of starting the JRM process, the application throws an exception in the vnmserver.log stating that JRM down.

Workaround:

Manually trigger VRF Collection process.


Resolved Problems in Campus Manager 5.2

The following table lists the problems that have been fixed in Campus Manager 5.2.

Table 11 Resolved Problems in Campus Manager 5.2 

Bug ID
Summary
Additional Information

CSCdm48015

In VLAN-to-port association, all ATM ports on switches (except the ATM switches) configured to the VLAN appeared.

Campus Manager displayed an ATM trunk port as configured to a VLAN, even if no corresponding LANE client was associated with the VLAN.

This problem has been resolved.

CSCdp00593

SNMP report displayed wrong HwVersion and HwVersionMinor for Cisco LS1010 devices.

This was because the image had reached EOE.

This problem has been resolved.

CSCdm91634

In the Campus Manager Device report, the number of ports in a device's ATM module was incorrectly displayed as zero.

This problem occured in Catalyst 5000 devices running Catalyst operating system software release 4.3(1a). It was due to missing if Entry for device ATM module.

The ANI Server depends on if Entry to determine the number of ports in a particular module.

This problem has been resolved.


Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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.