Table Of Contents
Release Notes for Campus Manager 5.1
on Windows and Solaris
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
Resolved Problems in Campus Manager 5.1
Obtaining Documentation, Obtaining Support, and Security Guidelines
Notices
OpenSSL/Open SSL Project
License Issues
Release Notes for Campus Manager 5.1
on Windows and Solaris
These release notes are for Campus Manager 5.1, 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.1
•Obtaining Documentation, Obtaining Support, and Security Guidelines
•Notices
New Features
The following are the new features and enhancements available in Campus Manager 5.1:
•Auto Allocation of Devices
•MAC Detection and Reporting
•Integration with IPM, HUM and DFM for Topology Maps
•Enhanced Discrepancy and Best Practices Deviation Report
•Enhanced Topology in ACS Environment
•User Tracking Summary Portlet
•VSS Support
Note ATM Management and Path Analysis that were supported in the previous releases of Campus Manager, have been removed in Campus Manager 5.1.
Auto Allocation of Devices
Devices can be added to Campus Manager in two modes:
•Auto
•Manual
In Auto Management mode, Campus Manager 5.1 allows you to manage devices in groups
There are two types of groups available:
•System-defined groups
System-defined groups are automatically created, based on the information in DCR.
•User-defined Groups
You can create User-defined groups based on your requirements.
For example, if you want to manage only devices that have IP addresses in the range 10.77.*.* in Campus Manager, create a group for those devices in Common Services and add it to Campus Manager in the Auto Mode Settings page. These devices will be managed in Campus Manager after you run Data Collection.
MAC Detection and Reporting
Campus Manager 5.1 detects New MACs, Rogue MACs and Dormant MACs that are in the network.
•Dormant MAC
MAC Addresses that are inactive for the specified number of days.
•New MAC
MAC Addresses that are newly added to your network.
•Rogue MAC
MAC Addresses that are not authorized to exist in your network.
This feature allows you to:
•Configure Campus Manager to send e-mails when New MACs are added to the network and Rogue MACs are detected in the network.
•Define the list of MAC addresses that are to be classified as unauthorized addresses in the network.
•Generate reports to get information on the New MACs, Rogue MACs and Dormant MACs in the network.
Integration with IPM, HUM and DFM for Topology Maps
From Topology Maps and N-Hop view Portlets, you can:
•View DFM information. If an alert is associated with a device, you can see icons displayed along with the devices. These icons indicate the severity of the alert.
•Launch the DFM report that displays information on the alerts and events that are associated with the device.
•Launch the Create Collectors page in IPM to create collectors on IPSLA capable devices.
•Launch the Collectors page in IPM to view details on collectors that have already been created.
•Launch the Device Dashboard page in HUM that provides performance details of the device.
•Launch the Interface Report in HUM that displays data for the past one hour for a link.
You can launch the application pages, if DFM, HUM, and IPM are installed on a local server or on a remote server with a Master-Slave setup.
Enhanced Discrepancy and Best Practices Deviation Report
You can fix the following Best Practises Deviation through Campus Manager 5.1:
•Channel port in Auto mode
•Trunk ports in Auto mode
•Non-channel port in Desirable mode
•Non-trunk ports in Desirable mode
The following discrepancies are removed from Campus Manager 5.1:
•DRIP Enabled VLAN
•ATM-VLANs that do not have an entry in Lane Config server
•ATM-VLANs with Lane Server that do not have an entry in Config server
•Partitioned ATM-VLAN
•More than one Config server in a single ATM-Fabric
Enhanced Topology in ACS Environment
Topology Maps normally display all the devices discovered by Campus Manager. When Campus Manager is integrated with the ACS server, you can set Topology Maps to display only the devices you are authorized to view.
User Tracking Summary Portlet
The User Tracking Summary Portlet displays the following data:
•Number of End hosts
You can click the number link to launch the End Hosts Immediate Reports page.
•Number of Active End hosts
End hosts that are currently connected to the network are called Active End hosts. You can click the number link to launch the Active End Hosts Immediate Report page.
•Number of Dormant hosts in the last 12 days
Displays the number of hosts that are inactive for 12 days. The number of days depends on the days configured in the Configuration screen.
•Number of New hosts in the last 12 days
Displays the number of new hosts in the last 12 days. The number of days depends on the days configured in the Configuration screen.
•Number of Rogue hosts in the last 21 days
Displays the number of Rogue hosts in the last 21 days. The number of days depends on the days configured in the Configuration screen.
For more details, see the User Guide for CiscoWorks LMS Portal 1.1.
VSS Support
The Virtual Switching technology is the process of combining two standalone distribution switches in the local distribution layer, into a single management point. The Virtual Switching System (VSS) functions and appears as a single switch to the wiring closet and the core layer.
See the User Guide for CiscoWorks Resource Manager Essentials 4.2, for more details on:
•VSS Support
•Prerequisites for conversion to VSS
•VSS Configuration Process
Note Only VSS-capable standalone Cisco Catalyst 6000 switches can be converted into a Virtual Switching System.
If the following devices are available in DCR, Campus Manager manages VSS as follows:
•Device A
–IP Address—10.77.240.1
–Display Name —Switch 1
•Device B
–IP Address—10.77.240.2
–Display Name —Switch 2
Campus Manager manages these devices as normal Catalyst 6000 devices.
You can configure the above devices as VSS through RME, with Device A as the Master and Device B as the Slave. After this configuration, RME adds another device in DCR with the following credentials:
•IP Address of the Master device—10.77.240.1
•sysOID of the VSS device—1.3.6.1.4.1.9.1.896
•Display name—VSS_10.77.240.1
Now DCR contains three devices instead of two:
•10.77.240.1— Switch 1
•10.77.240.2 — Switch 2
•10.77.240.1—VSS_10.77.240.1
When Data Collection runs, the following occurs:
•10.77.240.1 — Switch 1 will be deleted from Campus Manager
•10.77.240.2 — Switch 2 will be managed in Campus Manager as an unreachable device
•10.77.240.1—VSS_10.77.240.1 will be added to Campus Manager
With this VSS device, you can perform all Campus Manager operations that are applicable for normal Catalyst 6000 devices.
VSS re-configuration is not supported in RME. You have to manually reconfigure the devices to remove VSS. In that case, all of these three devices will be present in DCR. You must delete the VSS device from DCR before running Data Collection. Otherwise, the results will be unpredictable.
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.
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.
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.1. If you are a registered user, you can download SP for Campus Manager from:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus
Support Information
Campus Manager 5.1 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
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
|
CSCse39112
|
Rules created for Groups in Campus Manager do not work properly.
|
In the Campus Manager 4.0.4 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.
|
CSCsi44992
|
Switch Port Reports for Unused Up and Unused Down ports are migrated from LMS 2.6 to LMS 3.0.
|
Switch Port Reports for Unused Up and Unused Down ports are available in LMS 2.6 but not in LMS 3.0.
These reports are migrated, when you perform a Local or a Remote data migration from LMS 2.6 to LMS 3.0.
If you have scheduled jobs for these reports, they do not run in LMS 3.0.
Workaround:
After upgrading to LMS 3.0, delete the scheduled jobs for Switch Port Reports on Unused Up and Unused Down ports.
|
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.
|
CSCsb28190
|
Campus Manager applications do not start in ACS mode.
|
Topology Services, VLAN Port Assignment, and Discrepancy Report tasks do not start when you login to CiscoWorks in ACS mode.
This problem occurs if you select Assign a Ciscoworks on a per Network Device Group Basis in ACS server, but in the selected device group, you do not add the CiscoWorks server IP address.
Workaround:
When you assign a user to a specific group, ensure that you also add the device group that contains the Cisco Works server.
For example, assume that the user is added to group X and Cisco Works belongs to device group Y, add the device group Y, also to group X.
|
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.
|
CSCsa44629
|
Campus Manager does not restore Topology Map settings after you take a backup and restore the data on another machine, that has Campus Manager 4.0.
|
Campus Manager does not save the changes to the layout style and background colors of the Topology Map settings, if you had taken a backup on another machine.
This occurs when you:
1. Modify Topology Map settings on a machine with Campus Manager 3.3.
2. Back up and restore the files on another machine, that has Campus Manager 4.0.
3. Run Data Collection.
4. Start Topology Services.
Workaround:
1. Run NMSROOT/campus/conf/upgrade/cm/topo/
2cm31maplayout.pl on the machine with Campus Manager 3.3 to generate the map files.
2. Copy the map files to the location on the target system, where you have restored the data: NMSROOT/campus/etc/users/username/
3. Upgrade Topology Map by selecting File > Upgrade View Layouts from Topology Services.
|
CSCdu51651
|
You cannot select the first template from the drop-down box, when you create SPVC/SPVP/Advanced parameters.
|
Under ATM if you create SPVC/SPVP/Advanced parameters, you cannot select the first template from the drop-down box. This is because the traffic parameter fields are not populated.
Workarounds:
1. Go to Select/Edit and select the template.
2. Click OK.
Or
1. Select the second template
2. Select the first template.
|
CSCdt22462
|
Download of Java applets on Windows 2000 machines may take longer than expected if virus checker application is enabled.
|
On some Windows systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected (up to six minutes in some instances).
After the applet has been loaded and cached locally, the problem no longer occurs.
The delay is caused by client side filtering mechanisms such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers.
Scanning consumes a lot of memory and results in disk paging on most systems.
Owing to this, downloading is significantly slower than expected. (The effect is less on systems with large amounts of RAM and virtual memory.)
Workaround:
Disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension).
Exact instructions vary depending on the virus scanner installed on your system.
|
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.
|
CSCsl80838
|
Mismatch in Java Runtime version error is displayed when Topology Services window is launched.
|
Campus Manager uses the tested version of JRE version (1.6.0_05) for launching Topology Services even if the higher version of JRE (1.6.0_06 or later) is installed in the client machine.
The current behavior:
•If JRE 1.6.0_05 is selected from JNLP settings, then the Topology window launches properly.
•If JRE 1.6.0_06 is selected from JNLP settings, then Mismatch in Java Runtime version error is displayed and asking you to install JRE 1.6.0_05.
•If both JRE 1.6.0_05 and JRE 1.6.0_06 are selected from JNLP settings, then Mismatch in Java Runtime version error is thrown and asking you to install JRE 1.6.0_05.
Workaround:
Even if the client machine has higher version of JRE installed, you must select only the required JRE version (1.6.0_05) from the JRE settings.
|
CSCso62351
|
When upgrading CiscoWorks Server to LMS 3.1 the count on the number of devices managed in Campus Manager is reduced.
|
This problem occurs while migrating IP Address range filters into corresponding user-defined groups in LMS 3.1.
Check whether the ANIServer.properties file in NMSROOT/campus/etc/cwsi has:
1. A preceding `#' symbol for the filter value `DataCollection.AutoMgmtGroupids'
2. An empty property for `DataCollection.AutoMgmtGroupids'
These two conditions indicate that an error has occurred during the filter migration process.
Workaround:
1. Remove the empty property for `DataCollection.AutoMgmtGroupids'
2. Remove `#' symbol from the filter value `DataCollection.AutoMgmtGroupids'
3. Restart ANIServer process by entering pdterm ANIServer in the console of the server and then after few minutes enter pdexec ANIServer
These steps should migrate the IP Address range filters into corresponding user defined groups.
|
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
|
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.
|
CSCin39472
|
Problems with Campus Manager applications after logout.
|
When you logout from CiscoWorks, Campus Manager applications will continue to function. However, the following functions will not be available:
•Launching Help.
•Tasks in Campus Manager that require user action between applications.
For example, highlighting a device in Topology Services using Path Analysis.
Workaround:
1. Close all Campus Manager applications.
2. Login into CiscoWorks.
3. Launch Campus Manager applications.
|
CSCdp43999
|
Maps and configuration dialog boxes display offset menus and list boxes in Netscape on a Solaris client.
|
Sometimes, when you launch a map or a configuration dialog box, menus or list boxes are not displayed below the menu. This offset occurs in Navigator on a Solaris client.
Workaround:
Move or resize window.
|
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
|
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 than this, 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.1.
|
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 2 seconds. It takes approximately 4 seconds for 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.
|
CSCsc49155
|
User Tracking report generator displays error for some Custom queries.
|
If you run a Custom query on User Tracking reports after remote migration, an error message appears.
Campus Manager 3.x allows you to create some queries that are not supported by CM 4.0.x. Hence, an error is displayed when you run the queries.
Workaround:
Delete the old queries created in Campus Manager 3.x, and create new queries.
|
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
|
CSCsh20449
|
RMON configuration fails in cluster member switch.
|
When you try to do RMON configuration in 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.1.
|
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.
|
CSCsa80409
|
Campus Manager Telnet and SSH do not support Windows 2003 and XP clients
|
Telnet and SSH do not launch from the Campus Manager Topology Map.
This occurs on Windows 2003 and Windows XP clients.
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.
|
CSCin36988
|
Cannot calculate utilization of VCs in tunnel.
|
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 > Display VCs > Per device.
5. Click Get Info.
An error appears:
Failed to compute utilization for some
or all rows
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.
|
CSCin01977
|
Position of devices connected to switch cloud changed after upgrade.
|
Switch clouds and fabrics represent the collection of LAN switches and ATM switches, respectively.
These logical entities are very specific to the currently discovered network. That is, if a new switch is discovered, you cannot uniquely identify a switch cloud/fabric across ANI databases.
Workaround:
None.
|
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:
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 |
