CiscoWorks Campus Manager

CiscoWorks Campus Manager 5.0

  • Viewing Options

  • PDF (131.1 KB)
  • Feedback

Device Management

Q. Some of the devices in the Device Credential Repository (DCR) are not managed in CiscoWorks Campus Manager, but the IP address range of the devices is available in the automode policy filter. What could be the reason?
A. Check whether these devices are manually excluded from CiscoWorks Campus Manager in the Manually Excluded Devices report. If the device you are looking for appears in the report, it will not be managed in CiscoWorks Campus Manager unless you manually include it.
Q. When I exclude a device, will it get deleted immediately or during the next data collection?
A. If you manually exclude a device, it is immediately deleted from CiscoWorks Campus Manager, and the excluded device will be prevented from being managed in further data collections.
Q. What is the difference between manually excluding a device and deleting a device from the Topology Services screen?
A. Manually excluding a device: If you manually exclude a device, it gets deleted from CiscoWorks Campus Manager. Even if you do data collection from a neighboring device, an excluded device does not get managed in CiscoWorks Campus Manager. Deleting a device from the Topology Services screen: If you delete a device from the Topology Services screen, rediscovery of its neighboring device by CiscoWorks Campus Manager will cause CiscoWorks Campus Manager to manage the deleted device.
Q. I have manually included a device. How do I exclude it?
A. Select and exclude that device from the device selector in the Exclude Devices page. Alternatively, you can exclude that device by including it in the Manually Included Devices report.
Q. I have manually excluded a device. How do I include it?
A. Select and include that device from the device selector in the Include Devices page. Alternatively, you can include that device by deleting it from the Manually Excluded Devices report.
Q. When I manually include a device, will it be managed immediately in CiscoWorks Campus Manager?
A. No. CiscoWorks Campus Manager does not manage the included device unless you run data collection.
Q. I have both automode and manual mode enabled. Which one will take higher priority?
A. Manual mode always gets higher priority.
Q. I have manually added some devices and started data collection for all devices. For which devices will data collection run?
A. Data collection will run for manually added devices and the devices that are already managed in CiscoWorks Campus Manager.
Q. I have added n devices in DCR, and I want CiscoWorks Campus Manager to manage only a subset of the added devices. Is there any way to do this?
A. Either manually include those devices and run data collection, or select automode and specify the required IP address range in the automode policy filter and run data collection.
Q. Is the VLAN Trunking Protocol (VTP) domain-based filter available in CiscoWorks Campus Manager?
A. No, it is removed in CiscoWorks Campus Manager 5.0. You can filter based only on the IP address range.

User Tracking (UT)

Q. Why are outdated entries showing up in my user tracking table?
A. Outdated entries result when:

• A user or host is assigned to a new VLAN/port/VTP domain

• A power failure occurred

• A workstation has been switched off or removed from the network

User tracking does not automatically delete outdated end-user host entries. To delete these entries, either manually delete selected entries or schedule user tracking to remove old entries.
Q. How does the user tracking acquisition process differ from that of the CiscoWorks Campus Manager server?
A. User tracking is a CiscoWorks Campus Manager client application. The CiscoWorks Campus Manager server provides several types of global discoveries, including:

• Device and physical topology acquisition, resulting in baseline network information such as device identity, module and port information, and physical topology. This type of acquisition is required for logical, user, and path acquisition.

• User acquisition, resulting in information about users and hosts on the network.

The CiscoWorks Campus Manager server stores this information in the database. User tracking discovers the host and user information in the CiscoWorks Campus Manager server database, correlates this information, and displays it in the user tracking reports.
Q. How does the user tracking user and host acquisition process work?
A. Before collecting user and host information, CiscoWorks Campus Manager must complete global discovery. During global discovery, CiscoWorks Campus Manager generates a device list to determine which switches and routers it should look at to obtain MAC and IP addresses.
Q. Why is user tracking not performing ping sweeps on some subnets?
A. The criterion for whether or not user tracking performs ping sweeps on a subnet is the number of hosts in the subnet: You must check whether you have excluded the subnets from ping sweep. If a subnet has 256 or fewer hosts, user tracking performs ping sweeps on that subnet. User tracking does not perform ping sweeps on subnets that have more than 256 hosts. If ping sweeps are not performed, user tracking still obtains information from the router and switch mapping tables during a discovery.
Q. How long does user tracking maintain data?
A. Indefinitely; until you delete the information.
Q. Does user tracking discover users and hosts connected to devices discovered or managed other than through Cisco ® Discovery Protocol?
A. User tracking discovers all users and hosts in the network from the list of devices defined using data collection filters. The subset of devices in DCR that is defined after data collection might not be the same as the set of devices discovered based on the data collection filters.
Q. How does user tracking log errors?
A. User tracking major acquisition errors are logged in the user tracking error log. Device discovery and data collection errors are logged in the respective log files.

Data Extraction Engine (DEE)

Q. Where does DEE collect the discrepancy information from?
A. DEE collects the running discrepancy data from the latest configuration in the CiscoWorks Campus Manager server.
Q. What is an XSD file?
A. An XSD file is an XML-based alternative to Document Type Definition (DTD). It is based on an XML schema, which describes the structure of an XML document. An XML schema defines the valid building blocks of an XML document, similar to a DTD.
An XML schema:

• Defines elements that can appear in a document

• Defines attributes that can appear in a document

• Defines which elements are child elements

• Defines the order of child elements

• Defines the number of child elements

• Defines whether an element is empty or can include text

• Defines data types for elements and attributes

• Defines default and fixed values for elements and attributes

For more information, please refer to the CiscoWorks Campus Manager User Guide at
Q. How can I make use of the servlet interface?
A. You must write customized scripts that can connect to the servlet. The arguments and options have to be specified in XML format.
Q. Can I get user tracking and Layer 2 topology data for a particular set of switches or subnets managed by separate CiscoWorks Campus Manager servers?
A. No. This feature is not supported.
Q. I do not want to provide the password in the command line as it is insecure. Is there a way to provide it in a secure way?
A. Yes. You can create an environment variable CMEXPORTFILE, which points to a text file that contains the user ID and password list separated by a blank space.
Q. Where will the XML output file be stored?
A. The default locations for storing the XML output files are:

• PX_DATADIR/cmexport/ut/timestamput.xml

• PX_DATADIR/cmexport/l2topology/timestampL2Topology.xml

• PX_DATADIR/cmexport/Discrepancy/timestampDiscrepancy.xml

You can use the -f option to specify an alternative location.

For More Information

For more information about the CiscoWorks Campus Manager application and CiscoWorks LAN Management Solution, visit, contact your local Cisco account representative, or send an e-mail to the product marketing group at