Table Of Contents
Release Notes for Campus Manager 4.0 on Windows
New Features
Topology Services
Path Analysis
User Tracking
Discrepancy Reports
Administration
Product Documentation
Related Documentation
Additional Information Online
Support Information
Known Problems
General Notes and Known Problems
General Known Problems
Browser Known Problems
Path Analysis Known Problems
User Tracking Known Problems
Topology Services Known Problems
ANI Server Known Problems
Device/Agent Known Problems Impacting ANI Server
VLAN Port Assignment Known Problems
Spanning Tree Protocol Known Problems
Resolved Problems
Obtaining Documentation
Cisco.com
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Campus Manager 4.0 on Windows
These release notes are for use with the Campus Manager 4.0 (Campus), part of the CiscoWorks family of products running on a Windows platform.
These release notes provide:
•
New Features
•Product Documentation
•Related Documentation
•Additional Information Online
•Support Information
•Known Problems
•Resolved Problems
•Obtaining Documentation
•Documentation Feedback
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
New Features
Campus Manager 4.0 contains the following new features:
•Ability to work with devices managed using ACS (Access Control Server).
•Integration with CiscoWorks Homepage portal.
•Enhanced support for virtual LAN (VLAN) and private VLAN (PVLAN).
•Support for hosts running IPv6 and devices that may or may not have IPv6 configured on their interfaces.
•Support for certain SNMPv3 features.
•Support for Device and Credential Repository (DCR).
•Licensing using the Common Services licensing framework.
•Fixes to problems that existed in previous releases. For more information see "Spanning Tree Protocol Known Problems" section.
In addition, the following enhancements have been made to individual Campus applications.
Topology Services
The new features in Topology Services support:
•Creating PVLAN.
•Managing workgroups that use VLANs and segment your network logically.
•Creating trunk.
•Viewing port, device, and trunk attributes.
•Displaying reports about inconsistencies or misconfigurations in your physical or logical network setup.
•Viewing and finding port information in a VTP domain and configuring VLANs on a trunk.
•Creating EtherChannel.
Path Analysis
The new features in Path Analysis allow:
•Support for IPv6.
•Analyzing paths between two specified Layer 2 or Layer 3 devices. It enables you to use device hostnames or IP addresses, and show results in a network view, table, or textual trace display.
•Sorting Subnet-to-VLAN mapping table.
•Displaying managed domain, and display the Layer 2 path, wherever possible, between two specified end-user hosts known to User Tracking.
•Displaying information about interface properties such as Maximum Transmission Unit (MTU) size, speed, MAC address, and media type.
•Displaying information about device properties such as node name, device type, chassis type, up-time, and one alias.
•Tracing paths that Voice over IP (VoIP) can take on data networks.
•Saving and print path trace information.
•Running CiscoView from supported devices displayed in the Path Analysis view.
•Running Visual Switch Manager from Cisco 1900, 2900XL, and 3500XL devices displayed in the Path Analysis view.
•Support for Cisco CallManager login.
User Tracking
The new features in User Tracking allow:
•Discovering and displaying information about users, hosts, and IP phones in your network.
•Performing query for users, hosts, and IP phones.
•Modifying, adding, and deleting the username and notes in the main User Tracking table.
•Highlighting devices on the Layer 2 view in Topology Services.
•Viewing reports about duplicate IP addresses, and duplicate MAC addresses and VLAN names.
•New non-java based lightweight user Interface.
Discrepancy Reports
The new features in Discrepancy Reports allow:
•Support for enhanced discrepancy reporting.
•Reporting on network inconsistencies, anomalies or misconfiguration in the physical and logical layout in the discovered network.
Administration
The new features in Administration allow:
•Configuring the discrepancies and generate syslog messages.
•Administering Topology Groups, and schedule Path Analysis traces.
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.
Table 2 Related Documentation
Document Title
|
Description and Available Formats
|
User Guide for CiscoWorks Common Services 3.0
|
Describes CiscoWorks Common Service 3.0, gives an overview of the applications that make up Common Services 3.0 and provides conceptual information about network management.
This also describes common tasks you can accomplish with Common Services. This document is available in the following formats:
•PDF on the product CD-ROM.
•On Cisco.com at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/
cw2000/cw2000_d/comser30/index.htm
•Printed document available by order (part number DOC-78-16398-01).1
|
Additional Information Online
The following product specific information is available online:
•Incremental Device Update (IDU) contains updated files necessary for the latest device support and fixes to known problems that are not available in Campus Manager 4.0. If you are a registered user, you can download IDU for Campus Manager from:
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus
Support Information
Campus Manager 4.0 supports only US-English and Japanese versions of Solaris 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.
Known Problems
This section describes the known problems in this release:
•General Notes and Known Problems
•General Known Problems
•Browser Known Problems
•Path Analysis Known Problems
•User Tracking Known Problems
•Topology Services Known Problems
•ANI Server Known Problems
•Device/Agent Known Problems Impacting ANI Server
•VLAN Port Assignment Known Problems
•Spanning Tree Protocol Known Problems
Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)
General Notes and Known Problems
Note the following:
•Your browser must be properly configured. If it is not properly configured, Campus might not work correctly. See the Installation and Setup Guide for CiscoWorks Common Services 3.0 (Includes CiscoView) on Solaris for information on properly setting up client systems.
•Campus requires a DNS server to function properly. Many commands operate erratically or not at all, if there is no DNS server on the network.
•Running Campus from a browser invoked from an x-window connection is not supported. Install a browser on the client from which you wish to connect.
•Virus checker applications on Microsoft Windows systems might slow Campus response time.
•You can upgrade your operating system (OS) either before or after you upgrade Campus. However, if you upgrade the OS after upgrading Campus, 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.
•We recommended that any Windows 2000 server running Netscape Navigator should not also be used as a client.
•Visio Caveats:
–Do not export an entire topology map to Visio. Instead, select and export particular devices or a segment of the network.
–After selecting Export to Visio, you must enter a filename in the Export to Visio dialog box for the file Visio will generate.
–Before opening a topology map exported to Visio, you need to download the cm_cisco.vss file and place it in the Visio/Solutions directory.
Table 3 General Known Problems
Bug ID
|
Summary
|
Explanation
|
None
|
Cisco Catalyst 3500 series is supported in IP mode only.
|
Campus supports Cisco Catalyst 3500 series in IP mode only. Cluster mode is not supported. If your network has a Cisco Catalyst 3500 switch in cluster mode, the links display incorrectly.
Workaround:
None.
|
CSCsb28190
|
Campus Manager applications fail to start in ACS mode.
|
Toplogy Services, Path Analysis, VLAN Port Assignment, and Discrepancy Report tasks fail to start when you login to CiscoWorks in ACS mode.
This problem occurs when you assign a CiscoWorks user to a group and when CiscoWorks server is not present in that group.
Workaround:
When you assign a user to a specific group, ensure that the CiscoWorks Server IP address is added to that device group.
|
CSCsa80727
|
Launching of Campus Manager UIs fails.
|
Campus Manager UIs fail to open when the daemon manager is not restarted for a long period of time.
Workaround:
Stop and restart the daemon manager. Campus Manager UIs will now open properly.
|
CSCsa65685
|
Online Help for Data Extraction Engine has incorrect details.
|
Schema for User Tracking Data, Switch Data, and Subnet Data are incorrect in the Online Help.
The servlet for exporting user tracking data is incorrectly mentioned as CMExportServlet.
Workaround:
See Chapter Data Extraction Engine in the User Guide for Campus Manager 4.0 on Cisco.com for the correct information.
|
CSCsa65131
|
Campus Manager Data Extraction Engine servlet interface does not work.
|
The Campus Manager Data Extraction Engine servlet interface (CMExportServlet) displays an error when you try to export User Tracking Data.
The Online Help for Data Extraction Engine has incorrect details on the servlet to be used for exporting User Tracking Data.
Workaround:
Do not use the CMExportServlet to export User Tracking data. Use UTExportServlet to export User Tracking Data. See Chapter Data Extraction Engine in the User Guide for Campus Manager 4.0 on Cisco.com for more details.
|
CSCsa65130
|
Online Help for Data Extraction Engine refers to a non-existent logfile element.
|
In the schema for payload file, the Online Help refers to a logfile element which is non-existent. If this schema is used, an error is displayed.
Workaround:
Do not use the logfile element in the payload file. See Chapter Data Extraction Engine in the User Guide for Campus Manager 4.0 on Cisco.com for the correct schema for payload file.
|
CSCsa59569
|
Restoring Campus files fails when path of the backup.pl file is in lower case.
|
When path of the backup.pl file, is provided in lower case, Campus successfully backs up the files, but does not restore the files.
This is because during restore, NMSROOT verification of the tar file fails, which stops the Campus restore.
Workaround:
You must execute NMSROOT/objects/db/conf/configureApp.pl before backing up the files using backup.pl.
|
CSCsa47864
|
After uninstalling Campus, the application does not remove the links to Campus from CiscoWorks Homepage.
|
If you have enabled SSL on CiscoWorks server and if you uninstall Campus, the links to Campus Manager application are not unregistered from CiscoWorks Homepage.
Workaround:
None.
|
CSCsa44629
|
Campus does not restore Topology Map settings after taking back up and restore in another machine, which has Campus 4.0.
|
Campus does not save the changes to layout style and background colors in Topology Map settings, which were backed up in another machine.
This occurs when you do the following:
1. Modify Topology Map settings in a machine with Campus 3.3.
1. Back up and restore the files in another machine, which has Campus 4.0.
2. Run Data Collection.
3. Start Topology Services.
Workaround:
1. Run NMSROOT/campus/conf/upgrade/cm/topo/
2cm31maplayout.pl on the machine with Campus 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.
|
CSCsa29999
|
In Campus, User Defined group lists all the devices when you create the group in CiscoWorks Common Services.
|
When you create Common Services User Defined group in Device and Credential Repository (DCR) Device Management, the User Defined Group in Campus displays all the devices.
Workaround:
None.
|
CSCsa22708
|
Campus does not manage existing devices when upgrading from higher device limit to lower device limit.
|
This problem occurs because Campus performs a fresh discovery of the network to obtain the devices and does not import them from the earlier versions.
Workaround:
None.
|
CSCin58202
|
Unable to get XML data using user defined queries or layouts, until you restart User Tracking after creating the user defined queries or layouts.
|
The is because of an error in the applet where you create user defined query or layout.
The applet does not save the user defined query or layout in the ANI Server until you close User Tracking window.
Workaround:
None.
|
CSCin23883
|
Jobs created in Path Analysis or User Tracking appear in the Job Management page even after uninstalling Campus.
|
If you have scheduled Path Analysis or User Tracking jobs and then uninstall Campus, the jobs are not deleted from the CiscoWorks Job Management page.
Workaround;
Delete the Path Analysis or User Tracking jobs from the Job Management page.
|
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.
|
CSCdt55303
|
Starting Campus application with the Print dialog box open in another Campus application results in error.
|
This problem occurs if you:
1. Select Print from active Campus application.
2. Start another Campus application, with Print dialog box open.
The new application window does not respond to user input.
Workaround:
Close the Print dialog box and restart the application.
|
CSCdt42318
|
Cannot copy and paste IP addresses from Topology Services to Path Analysis when you use keyboard shortcuts.
|
This problem occurs if you:
•Enter Ctrl-C to copy address after selecting an IP address in Topology Services,
Or
•Enter Ctrl-V with the cursor active in the From field in Path Analysis.
•In both cases the following is pasted in instead of the IP address:
java.lang.nullPointerException
Ctrl-X, Ctrl-C, and Ctrl-V (keyboard shortcuts for cut, copy, and paste commands) are not supported by summary tables in the Topology Services main window or most tables displayed by Campus applications.
Also, in applications that support the copying of table cells by selecting Edit > Copy, a carriage return is added to the end of the last cell copied.
Workaround:
None.
|
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 via Cisco WAN Manager.
|
CSCdm88520
|
Minimized windows are not visible when you select them from a Window menu.
|
If a window is minimized, you cannot make it visible by selecting it from a Window menu.
Workaround:
•On Solaris, double-click the icon of the window on the desktop.
•On Windows, click the icon of the window in the task bar.
|
CSCdm83204
|
Campus 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 suite of applications will not work.
Workaround:
Use full DNS name or IP address of server, even when accessing it locally.
|
CSCdm77812
|
In Path Analysis, Tools > Path Trace displays an error,
null pointer exception on Microsoft Internet Explorer 5.0 with the URL of a local host.
|
If your system has a non-blank CLASSPATH environment variable, your browser might behave unpredictably.
Workaround:
Reset the CLASSPATH variable non-globally:
•Solaris— Reset the CLASSPATH variable from the terminal window from where you launch the browser.
•Windows—Reset the CLASSPATH variable in MS-DOS prompt window and launch the browser from the prompt.
|
General Known Problems
Browser Known Problems
Table 4 Browser Known Problems
Bug ID
|
Summary
|
Explanation
|
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, which require user action between applications. For example, highlighting a device in Topology Services using Path Analysis.
Workaround:
1. Close all Campus applications.
2. Login into CiscoWorks.
3. Launch Campus applications.
|
CSCdt11838
|
You are not prompted to install the Java plug-in when launching an application that utilizes the plug-in for the first time.
|
If RealJukebox Plug-in for Navigator is already installed on a Windows client before the first launch of application utilizing Java Plug-in, you will not be prompted to install Java Plug-in.
Workaround:
Uninstall RealJukebox Plug-in. Another option is to rename nprjplug.dll file in Navigator Plug-ins directory with new extension—for example, nprjplug.dll.bak.
After Java Plug-in is installed, you can reactivate RealJukebox Plug-in by changing the renamed file back to nprjplug.dll.
|
CSCdp43999
|
Maps and configuration dialogs 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.
|
Path Analysis Known Problems
Table 5 Path Analysis Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsa47939
|
You cannot start CiscoView from Path Analysis, on SSL server.
|
You cannot start CiscoView from Path Analysis because of an incorrect URL:
https://CiscoWorksServer:-1/CVng/
chassis.do?deviceip=10.77.209.53
Workaround:
Replace -1 with 443 in the URL, thus correcting the URL to:
https://CiscoWorksServer:443/CVng/
chassis.do?deviceip=10.77.209.53
|
CSCsa41902
|
Campus does not display proper error message when ACS is down.
|
When ACS is down, authentication succeeds but authorization to the server fails. Campus tasks display an error message, which does not specify that TACACS+ login has failed.
Campus must display an error message similar to the message in Common Services: Authentication with TACACS+ fails. You are in the fallback mode. Please go to Server > Security > Login Module > Non ACS to change the Login Module to CiscoWorks Local. You will need appropriate privileges to perform this operation.
Workaround:
None.
|
CSCin37960
|
VLAN-to-Subnet mapping information is not available for Phone Traces.
|
Path Analysis does not provide VLAN-to-Subnet mapping information, when you run Path Trace between two IP phones.
Workaround:
None.
|
CSCin37938
|
Interface Type displays Unknown for phones in Path Analysis Table.
|
This problem occurs when you run path traces between IP Phones or between a device and IP Phone.
Workaround:
None.
|
CSCin36082
|
Additional hop appears when you perform a trace using HSRP virtual IP address.
|
An additional hop appears if you perform a trace by providing an HSRP virtual IP address as the source or destination in the path trace.
Workaround:
None.
|
CSCin35773
|
Map displays self loop when routing loop occurs.
|
Occasionally, when the potential first hop learnt by Path Analysis is not discovered successfully by ANI, the map displays a self loop.
Workaround:
None.
|
CSCin30899
|
Path Analysis does not work when LSR Traceroute is disabled.
|
If you disable source route on routers, Path Analysis might not display the route occasionally.
Workaround:
None.
|
CSCin28223
|
CORBA related error message is logged into the log file during path trace.
|
Occasionally, during path trace, a CORBA related error message is logged into the ani.log file.
Workaround:
Close the client browser window and relaunch Path Analysis.
|
CSCin00624
|
Path trace involving HSRP router results in an empty If Index entry in the Path Analysis table.
|
The problem occurs when you run a Path trace which includes the IP address of an HSRP router in the From field of a path trace.
Workaround:
None.
|
CSCdw15555
|
Voice trace fails to get Cisco CallManager cluster information if Cisco CallManager HTTPD shuts down.
|
Path Analysis Voice Trace needs to query call managers known to ANI to see what the cluster membership is.
This is done through a HTTP query.
As a security precaution, you might disable the Web Server on all cluster members except one. This is because Cisco CallManagers use IIS, and can be badly damaged by viruses such as Code Red and NIMDA.
However, if cluster members have Web Server shut off, then Path Analysis cannot obtain information on cluster membership and cannot retrieve CDRs.
Workaround:
Turn the Web Server on the Cisco CallManager back on.
|
CSCdw03410
|
Path Voice Trace does not consider transcoding points.
|
Current Campus Path Analysis Voice Trace is valid only in the case where the two endpoints are IP Phones registered with the same Cisco CallManager cluster.
For other cases (involving transcoding), Path does not get correct path information.
Examples:
•Phone call from IP phone to POTS phone off H.323 gateway (e.g. 3640)
•Phone call from one Cisco CallManager cluster to another.
In such a case the path would be:
a. From phone 1 to Cisco CallManager 1
b. From Cisco CallManager 1 to Cisco CallManager 2 through H.323 inter-cluster trunk
c. From Cisco CallManager 2 to phone 2
•Phone call to gateway (PSTN, analog, etc.)
•Phone call to other servers (voice mail, conference, etc.)
This is a very complex issue, and most likely will require new instrumentation from telephony servers, etc.
Workaround:
None.
|
CSCdt42600
|
To and From fields may not function properly after selecting Print in Path Analysis.
|
This problem is caused by Java Virtual Machine bug. After you select Print in Path Analysis, the To and From fields may not accept mouse focus, or focus may appear in both fields, simultaneously.
Workaround:
Resize Java console window. If the problem persists, close Path Analysis window and open another window.
|
CSCdt42404
|
Trace tab displays GMT as time zone, although server is set to local time zone.
|
A number of Java bugs involve incorrect interpretation of time zones. Usually, the correct time zone appears if you set the local time zone to the appropriate three-letter abbreviation—for example, PST for Pacific Standard Time.
This problem is observed on Solaris clients with TZ environment variable set to American/Tijuana.
Workaround:
If the TZ environment variable is instead set to PST8PDT, then Java interprets local time zone correctly.
|
CSCdt23712
|
Path Analysis displays the Elvis module of Cisco Catalyst 6000 devices as unknown.
|
Since Path Analysis depends on ANI for its tracing capabilities, if a device-related discovery problem occurs in ANI, it results in an unsuccessful trace.
Workaround:
None.
|
CSCdt04978
|
Highlighted path trace in Topology Services map may be difficult to view.
|
It may be difficult to view highlighted path trace in Topology Services map, especially you select the Fit to Window view.
Workaround:
Zoom into Topology Services Map view by selecting
Select All Highlighted Objects > Zoom to Selected.
|
CSCds79693
|
Voice trace query results always appear using local time zone.
|
Local time zone always appears in voice trace query results, even if you select GMT time zone when specifying call start time.
Workaround:
None.
|
CSCds77461
|
Call Detail Records (CDR) query results are sometimes displayed after pressing Cancel.
|
Multiple threads are launched to query every Cisco CallManager for information specified in user's CDR query.
Since all query activities can take a second or two to cancel, query results sometimes continue to appear even after you press Cancel.
Workaround:
None.
|
CSCds77438
|
Path Analysis Map tab does not refresh properly.
|
This problem mainly occurs when running both the client and the server on the same machine. It occurs after running a large number of Path traces on client browser.
Workaround:
Close browser and relaunch Campus.
We recommend that you run the client and server on different machines. Doing so does not eliminate this problem. However, it reduces its occurrence because you need to run a large number of traces before problem manifests itself.
|
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.
Table 6 User Tracking Known Problems
Bug ID
|
Summary
|
Explanation
|
CSCsb17074
|
User Tracking does not discover hosts connected to devices with SNMPv3 credentials.
|
When you manage the devices Cisco Catalyst 3750 and Cisco Catalyst 4000 with SNMPv3 Credentials in Campus Manager, and if there are end hosts connected to these devices, the end hosts are not discovered and shown by User Tracking.
Workaround:
None.
|
None
|
User Tracking discovery could span more than desired subnet.
|
When you start subnet discovery of user nodes, devices in that subnet are marked for discovery.
Since switches support multiple VLANs, discovery could span more than the subnet that you selected. User Tracking could discover additional end host nodes that are not in the selected subnet.
Workaround:
Query only the required VLAN option in the subnet discovery window.
|
CSCsa30812
|
Job reports are not available after upgrading to Campus 4.0.
|
Reports for the jobs that are successfully completed in Campus 3.3 are not available after upgrading to Campus 4.0.
This is because of the change in format of the Reports in Campus 4.0. In earlier versions of Campus, job results were stored in plain text, whereas in Campus 4.0, the results are stored in serialized object.
Workaround:
None.
|
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, which is configured for dot1x authentication.
This is because the device populates vmVlanType as Static for dot1x authenticated ports.
Workaround:
None
|
CSCsa22740
|
ARP entries are not fetched for Cisco 3550-24 VLAN Interfaces.
|
ARP entries are not fetched for Cisco 3550-24 VLAN Interfaces. Hence, IP Address is not displayed in User Tracking End Host Reports.
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 recreated immediately. 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 are displayed as end hosts in User Tracking.
This is caused by a problem on the device.
Workaround:
None.
|
CSCin08287
|
User Tracking does not recognize change in IP address UTIPChange is set to 1 under DHCP.
|
In a network using DHCP, with the UTIPChange set to 1, User Tracking does not recognize changes in IP address when an end-host is moved across VLANs. In this case, IP address changes across subnets.
When you set UTIPChange to 0, User Tracking detects the change of IP address across VLANs.
Workaround:
None.
|
CSCin00365
|
A change of Cisco CallManager registration adds a new record in phone table.
|
Cisco CallManager entries themselves respond with two entries. Make the change in the Cisco CallManager and not in the User Tracking.
Workaround:
None
|
CSCin00363
|
End host does not appear if obsolete ANI 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:
Do the following:
1. Delete the specific device.
2. Perform device specific discovery.
3. Perform a User Tracking discovery.
|
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.
|
CSCec59408
|
Campus does not query CISCO-PORT-SECURITY-MIB to verify port security configuration.
|
In User Tracking, configuring port security for a port makes the CAM entry static. When port security is configured, Campus does not query CISCO-PORT-SECURITY-MIB.
This is because of a device specific MIB implementation problem.
Workaround:
Upgrade to Cisco IOS Release 12.2(18)EW1 or 12.2(20)EW.
|
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 network, entries for such phones in the User Tracking phone table will not have device and port information.
Workaround:
None.
|
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.
|
Topology Services Known Problems
Table 7 Topology Services Known Problems
Bug ID
|
Summary
|
Explanation
|
None
|
Multilayer Switch Module gigabit ports displayed as unknown-duplex.
|
Multilayer Switch Module does not have the MIB to support half and full-duplex on gigabit ports. Therefore, those ports are displayed as unknown-duplex.
Workaround:
None.
|
CSCsa78413
|
Hostname resolution does not work on Windows 2003.
|
Campus Manager does not display hostnames for devices or end hosts even when DNS support is configured, and working properly.
This occurs when CiscoWorks is running on Windows 2003.
Workaround:
None.
|
CSCsa80409
|
Campus Manager Telnet and SSH do not support Windows 2003 and XP clients
|
Telnet and SSH fail to launch from the Campus Manager Topology Map.
This occurs on Windows 2003 and Windows XP clients.
Workaround:
None.
|
CSCsa39618
|
Unable to close Topology Services and Path Analysis.
|
Java console hangs when you select File > Close option from Menu in Netscape 7.1 on Microsoft Windows.
Workaround:
Click the Close button (X) on the right hand corner of the window.
|
CSCsa37595
|
Unable to delete large number of devices from Topology Services.
|
An error message appears when you try to delete more than 100 devices from VTP Domain View in Topology Services.
Workaround:
We recommend that you restart the database without deleting large number of devices through the User Interface.
|
CSCsa36666
|
Internet Explorer client on Microsoft Windows 2003 displays wrong title for Topology Services
|
Internet Explorer on Microsoft Windows 2003 erases all the characters before the character @, and displays the rest of the title.
Workaround:
None. This does not cause any loss of data or affect the functionality.
|
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.
This is because of low memory in profiles directory, where the jar files are being downloaded.
Workaround:
Make sure that there is enough memory in the jar cache partition.
|
CSCsa25203
|
Campus does not generate Time Domain Reflectometry (TDR) Report for Cisco 3750 and Cisco 4500 series switches.
|
Campus displays an empty report when you run TDR test on Cisco 3750 and Cisco 4500 series switches.
This is because MIBs are not available to support TDR feature on these devices.
Workaround:
None.
|
CSCsa24985
|
Topology times out after a brief period of inactivity.
|
In Topology Services, after a brief period of inactivity, when you launch port attributes from the map, it displays an Authorization Error.
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.
|
CSCsa12448
|
Channel mode is set to desirable on one end, and auto on the other.
|
This can be seen in switches running Cisco IOS. Channel mode is set as desirable on one end, and to auto on the other end.
Though this combination is valid and the link gets converted to a channel, it has to be set to desirable on both sides.
Workaround:
None.
|
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 not supporting CISCO-STP-EXTENSIONS-MIB will not support any STP related functionality.
Workaround:
None
|
CSCsa11888
|
Channel or Trunk cannot be configured due to 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 is moved.
|
This problem is seen in Topology services display map. When there is a long line between devices and one of the device is dragged to a different location on the map, a kink in the line develops with the link line connecting these two devices getting warped.
The line appears jagged, instead of being straight.
Workaround:
To avoid this behavior, have devices closer to each other.
|
CSCin68983
|
Cannot configure Trunk between Cisco 2900XL and Cisco 3500XL devices.
|
Trunk configuration fails between Cisco 2900XL and Cisco 3548XL series switches.
This is due to lack of MIB support.
Workaround:
None.
|
CSCin68382
|
Tasks related to Network Administrator role are not properly reflected in ACS.
|
This problem is found when a user in ACS server is associated with Network Administration role.
When a comparison is made between tasks defined for Network Administrator role in CiscoWorks LMS and that in ACS shared profile components, some authorized tasks are found deselected for ACS shared profile components.
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 does not calculate Trunk mode related discrepancies.
|
Topology Services does not flag 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 does not report Spanning Tree discrepancies for some devices.
|
Campus 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 SNMP agent of the device.
Workaround:
None.
|
CSCin45496
|
Campus 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 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 is displayed:
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.
|
CSCin30389
|
On Netscape Navigator, for System Defined Groups, the Create, Edit, and Delete buttons appear enabled for all users.
|
When you click Create, Edit, or Delete buttons even without permissions, the Admin client displays a message saying that you do not have access rights.
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.
|
Topology Services > VTP Domains > NULL folder 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:
Reopen 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 there is a new switch discovered, it can affect either of them to a very large extent.
This means that you cannot uniquely identify a switch cloud/fabric across ANI databases.
Workaround:
None.
|
CSCin01451
|
Cannot launch Customer Response Application (CRA) URLs from Service Attributes window.
|
This problem occurs when you launch Service Attributes from Topology Services. The sysApplInstallPkgLocation MIB returns /AppAdmin/.
The server http://ip-address/AppAdmin does not start the application.
This is because the application Web Server was running in a different port 6293.
Workaround:
Use CRA version 3.0(0.25) or later.
|
CSCin00665
|
Voice Port information not shown for Catalyst 4224 running a Cisco IOS release earlier than release 12.1(5)YE3.
|
This is caused by a bug in the agent on the device (Bug ID CSCdu08256).
Workaround:
This problem has been fixed in the Cisco IOS release 12.1(5)YE3. Upgrade to this version.
|
CSCef67937
|
Campus does not show port as trunking if the port is part of the Channel.
|
This problem occurs when Cisco Catalyst 3750 |
