Table Of Contents

Getting Started With Campus Manager

Logging Into CiscoWorks

Before Using Campus Manager

Starting Campus Manager Applications

Understanding the User Interface

Campus Manager Process and Dependent Processes

Viewing and Maintaining Log File Details

Error Messages

Getting Started With Campus Manager

---

This chapter tells you how to get started with Campus Manager. The sections in this chapter are:

•Logging Into CiscoWorks

•Before Using Campus Manager

•Starting Campus Manager Applications

•Understanding the User Interface

•Campus Manager Process and Dependent Processes

•Viewing and Maintaining Log File Details

•Error Messages

Logging Into CiscoWorks

You must log into CiscoWorks server to access Campus Manager. If you are logging into CiscoWorks server for the first time, you can use admin, which is the reserved username and password.

CiscoWorks UserModes

To prevent unauthenticated access to the CiscoWorks Server, CiscoWorks applications, and data, Common Services provides features for managing security. You can specify the user authentication mode using the AAA Mode Setup.

CiscoWorks Common Services supports two modes of user authentication and authorization:

•ACS mode—Access Control Server (ACS) provides authentication and authorization services in this mode. To use this mode, you must install Cisco Secure ACS on your network.

•Non ACS mode—CiscoWorks Server provides authentication and authorization services in this mode.

CiscoWorks Common Services, set to default, uses CiscoWorks Server authentication (Non ACS), to authenticate users and authorize them to access CiscoWorks Common Services applications.

The CiscoWorks Server authentication scheme has five roles. You cannot change these roles, or the privileges assigned to those roles. The following is the list of privileges, sorted from the least privileged to the most privileged:

•Help Desk

•Approver

•Network Operator

•Network Administrator

•System Administrator

You can also use Cisco Secure ACS to provide user authentication and authorization. Cisco Secure ACS allows you to create custom roles and privileges, so that you can customize Common Services client applications.

You can use Cisco Secure ACS to provide a more secure environment. Cisco Secure ACS allows you to define the roles for accessing a subset of devices.You can also decide on the applications that would function on the selected set of devices.

If you configure Common Services to use non ACS modes for authentication, CiscoWorks Server provides authorization services.

In ACS mode, the privileges you have depend on the ACS role assigned to you. See Campus Manager ACS Help for complete details on roles and privileges in Campus Manager.

Before Using Campus Manager

You must ensure that you have a valid license before you start using Campus Manager. For License information, see Installing and Getting Started with CiscoWorks LAN Management Solution 3.2.

Campus Manager determines the devices, which are to be managed, through Data Collection filters or the auto-manage function. The auto-manage function, automatically manages the devices, where all the devices in Device and Credential Repository are added into Campus Manager as managed devices.

You can also restrict the configuration to use a subset of the devices in DCR to be managed by Campus Manager, based on the devices in an IP address range or a VTP Domain.

Devices that have been deleted from DCR continue to be managed by Campus Manager if Data Collection or User Tracking Acquisition are in progress.

The licence is validated while launching different applications of Campus Manager like Topology services. If the license is expired or invalid, you are prompted to obtain a valid license.

Starting Campus Manager Applications

The Campus Manager applications are:

Application	Allows you to
User Tracking	Locate and display data about users and hosts in the network, including wireless users. Dynamic Updates provides details without any time delay. (To access User Tracking, select Campus Manager > User Tracking) For more details, see Chapter 7, "Tracking Users".
Topology Services	Manage, view, and monitor the physical and logical services on your network. (To access Topology Services, select Campus Manager > Visualization. The Topology Services page appears. Click Launch Topology Services) For more details, see, Chapter 9, "Using Topology Services".
Managing VLANs and VTP	Assign VLAN to ports, display VLAN ports, or configure trunk ports, Create PVLAN, Delete PVLAN, Configure Promiscuous Ports. (To access User Tracking, select Campus Manager > Configuration) For more details, see Chapter 10, "Managing VLANs and VTP".
Discrepancies and Best Practices Deviations Reporting	View the Discrepancies and Best Practices Deviations in your network. Fix some Discrepancies and Best Practice Deviations. (To access Reports, select Campus Manager > Reports) For more details, see Chapter 8, "Discrepancies and Best Practices Deviations".
Managing Campus Manager Jobs	View the status of all Campus Manager Jobs including User Tracking jobs and Campus Manager reports. (To access Campus Manager Jobs, select Campus Manager > Job Management) For more details, see Chapter 5, "Administering Campus Manager."
Configuring VLANs, PVLANs and Trunk	Configure and manage VLANs, PVLANs, Trunk, and also assign ports to VLANs. (To access Configuration, select Campus Manager > Configuration) For more details, see Chapter 10, "Managing VLANs and VTP."
Administrating Campus Manager	Administer Data Collection and User Tracking Major Acquisition processes. (To access Administration, select Campus Manager > Administration) For more details, see Chapter 5, "Administering Campus Manager."

Campus Manager with Java Web Start Technology

Campus Manager uses Java Web Start Technology to launch the user interface (UI) for Topology Services.

You are prompted to install Java Web Start, the first time you start these applications. You can download and install it on the client machine, using the installation screens that are displayed. The next time you start the application, it automatically uses this Java Web Start.

Understanding the User Interface

Campus Manager 5.2 provides a single User Interface (UI) for various applications such as Topology Services.

All pages in Campus Manager have a Toggle icon as explained in Table 3-1.

Table 3-1 Icon Description

Icon	Name	Description
	Toggle	To switch between the Full Screen view and the Normal view of the application page. •Full Screen view — Displays only the application configuration area. •Normal view — Displays the Table of Contents, Application tabs along with the Configuration area. By default, the Normal view is displayed.
	Configuration Icon	Used as a Configuration Icon in the Routing Protocol Configuration page in the Create, Edit and Extend VRF workflows. Used as an Edge Interface Configuration Icon in the VLAN to VRF Mapping page in the Edge VLAN Configuration workflow.
	Interface Status as UP	Displays the interface status as up in the VLAN to VRF Mapping page in the Edge VLAN Configuration workflow.
	Interface Status as DOWN	Displays the interface status as down in the VLAN to VRF Mapping page in the Edge VLAN Configuration workflow.
	Existing VLAN Icon	Icon is used to view the VLANs existing on the corresponding interface. You can use the icon in the VLAN to VRF Mapping page in the Edge VLAN Configuration workflow.

The applications are grouped in the UI as provided in Table 3-2.

Table 3-2 Grouping of Applications and Tasks in User Interface 

Tabs	Applications and Features
Home	Campus Manager Home
User Tracking
Reports	Report Jobs
	Report Generator
	Custom Reports
	Custom Layouts
	Archives
Acquisition	Actions
Visualization	Topology Services
	RMON Configuration
Configuration
VLAN Configuration
PVLAN Configuration	Create PVLAN
	Delete PVLAN
	Configure Promiscuous Port
VLAN Port Assignment
Trunk Configuration	Create Trunk
	Modify Trunk Attributes
Reports
Report Jobs
Report Generator	Campus Manager Reports
	Best Practices Deviations
	Device Attributes
	Discrepancies
	Port Attributes
	VLAN
Report Archives
Job Management	Campus Manager Job Browser
Administration
Dashboard
Data Collection	SNMP Timeouts and Retries
	Device Management
	Mode And Policy Settings
	Include Devices
	Exclude Devices
	Schedule Data Collection
	Device Poller
User Tracking	Acquisition
	Acquisition Settings
	Schedule Acquisition
	Ping Sweep
	Configure Subnet Acquisition
	Delete Interval
	Configure Trunk For End Hosts Discovery
	Reports
	User Tracking Purge Policy
	Domain Name Display
	End Host Table Import
	Dynamic Updates
	Device Trap Configuration
	Trap Listener Configuration
	Debugging Options
	Dynamic User Tracking
	Dynamic User Tracking Console
	User Tracking Reports
Groups
Other Admin Settings	Discrepancies
	Purge Settings
	RME Server Credentials
Reports
Debugging Options	Data Collection
	Configuration and Reports
	Device Groups
	Topology
	User Tracking Server
	User Tracking Reports
	Dynamic User Tracking

Campus Manager Process and Dependent Processes

The following table lists the Campus Manager processes and their dependency processes.

If you stop or restart any of these processes you must stop and restart their dependency processes. See for the list of dependent processes.

You can stop and restart the process using Common Services > Admin > Process

Table 3-3 List of Campus Manager and Dependent Processes 

Process Name	Dependency (Sequential)	Description	Log File
ANIDbEngine	None	System service: Database engine for Campus Manager	None
ANIServer	EDS ANIDbEngine	System service: Collects device information for Campus Manager	ani.log
CampusOGSServer	CmfDbMonitor EssMonitor DCRServer CMFOGSServer	System service: Provides Grouping services for Campus Manager	CampusOGSServer.log
MACUHIC	EssMonitor ANIDbEngine	System service: Receives and processes SNMP traps for Dynamic UT	macuhic.log
UTLITE	EssMonitor ANIDbEngine	System service: Receives and processes the UTLITE data	utlite.log
UTMajorAcquisition	ANIServer	UTMajor Acquisition is a transient process. System service: Collects end hosts information.	ut.log
UTManager	EssMonitor ANIDbEngine DCRServer	System service: Queries external system for Dynamic UT	utm.log
VNMServer	ANIDbEngine	System service: Handles VNM Services like configuration, VNM collector job scheduling	Vnmserver.log
WlseUHIC	ANIDbEngine	System service: Collects information from Wlse Device	wlseuhic.log

Viewing and Maintaining Log File Details

Each Campus Manager module writes log files within the NMSROOT/log folder. Table 3-4 lists the name of the log file, Campus Manager module for which log file is written, the location in Windows where log files is stored, the location in Solaris where log files is stored and the purpose of the log file.

Table 3-4 List of Campus Manager Log File Details 

Log File	Module	Location in Windows	Location in Solaris	Purpose
ani.log	Data Collection	NMSROOT/log/ani.log	/var/adm/CSCOpx/log/ani.log	Debugs Data Collection process.
AniServer.log	ANIServer	NMSROOT/log/ANIServer.log	/var/adm/CSCOpx/log/dmgtd.log	Debugs ANIServer process
Campus.log	Campus Manager Configuration and reports	NMSROOT/log/Campus.log	/var/adm/CSCOpx/log/Campus.log	Debugs Configuration and reports screen of Campus Manager
CampusOGSServer.log	Campus OGSServer	NMSROOT/log/CampusOGSServer.log	/var/adm/CSCOpx/log/CampusOGSServer.log	Debugs Campus OGSServer process
CampusOGSClient.log	Campus OGS client	NMSROOT/log/CampusOGSClient.log	/var/adm/CSCOpx/log/CampusOGSClient.log	Debugs OGSClient
campusportal.log	Campus Portal	NMSROOT/log/campusportla.log	/var/adm/CSCOpx/log/campusportal.log	Debugs the portlets like qtopo and CM portlets of Campus portal.
Cmapps.log	User Tracking UI	NMSROOT/log/Cmapps.log	/var/adm/CSCOpx/log/Cmpapps.log	Debugs all the UI pages for User Tracking
macuhic.log	MACUHIC	NMSROOT/log/macuhic.log	/var/adm/CSCOpx/log/macuhic.log	Debugs MACUHIC process for Dynamic UT
ut.log	User Tracking	NMSROOT/log/ut.log	/var/adm/CSCOpx/log/ut.log	Debugs the User Tracking module
utlite.log	UTLITE	NMSROOT/log/utlite.log	/var/adm/CSCOpx/log/utlite.log.log	Debugs UTLite Server.
UTMajorAcquisition.log	User Tracking	NMSROOT/log/ UTMajorAcquisition.log	/var/adm/CSCOpx/log/dmgtd.log	Debugs UTMajorAcquisition process.
utm.log	UTManager	NMSROOT/log/ Utm.log	/var/adm/CSCOpx/log/utm.log	Debugs UTManager process of Dynamic UT
Vnmclient.log	VNM UI	NMSROOT/log/ Vnmclient.log	/var/adm/CSCOpx/log/Vnmclient.log	Debugs VNM UI
Vnmcollector.log	VNM Collector	NMSROOT/log/VnmCollector.log	/var/adm/CSCOpx/log/Vnmcollector.log	Debugs VNMCollector process.
VNMDeviceSelector.log	VNM Device selector	NMSROOT/log/VnmDeviceSelector.log	/var/adm/CSCOpx/log/VNMDeviceSelector.log	Debugs the device selector provided by VNM.
Vnmserver.log	VNM Server	NMSROOT/log/Vnmerver.log	/var/adm/CSCOpx/log/Vnmserver.log	Debugs VNMServer process
Vnmutils.log	VNM UI and Server	NMSROOT/log/Vnmutils.log	/var/adm/CSCOpx/Vnmutils.log	Debugs utility classes used by VNM client and server.

Error Messages

Table 3-5 lists the error messages, with the probable cause due to which the error has occurred. The table also provides the possible action to be taken for the error message.

Table 3-5 Error Messages for Campus Manager

Error Message	Probable Cause	Possible Action
Assign Edge VLAN to VRF workflow
You have not selected any devices from the Device Selector page.	When no device is selected in the Device Selector.	Select one or more devices to perform Edge VLAN VRF Mapping.
You should make some changes to the VLAN to VRF Interface Mapping page before continuing.	When you click Next without making any changes in the Interface Mapping to VRF page in create VRF, edit VRF, and extend VRF workflow.	You should make some changes to the VLAN to VRF Interface Mapping page before continuing.
Cannot connect to the CSTM backend process.	The Application is not able to connect to CSTM backend process.	Check whether the daemons are up and running
You cannot configure the devices (display names) because they are being used by configuration workflows and locked.	If few devices that you have selected is locked or used by some other user.	Wait until they are free. Or Ensure that the devices are not used by configuration workflows and free the devices from the Resource Browser page. To access this, select CS > Admin > Resource Browser.
You cannot configure the devices (display names) because they are being used by other users and locked.	If all the devices that you have selected is locked or used by some other user.	Wait until they are free Or Ensure that the devices are not used by other users and free the devices from the Resource Browser page. To access this, select CS > Admin > Resource Browser.
You have entered an invalid IP Address. Enter a valid IP Address.	You have entered an invalid IP Address.	Enter a valid IP Address.
You have entered an invalid Subnet Mask. Enter a valid Subnet Mask.	You have entered an invalid Subnet Mask.	Enter a valid Subnet Mask.
You have entered an invalid VLAN ID. Enter a valid VLAN ID.	You have entered an invalid VLAN ID.	Enter a valid VLAN ID.
You have entered an invalid VLAN Name. Enter a valid VLAN Name.	You have entered an invalid VLAN Name	Enter a valid VLAN Name.
You have entered an invalid Route Distinguisher (RD).	You have entered an invalid Route Distinguisher.	Enter the RD value in the format A: B; where A takes numerical values (1 to 9999) or IP Address and B takes numerical values. RD value entered must be unique to a VRF.
An error occurred while creating a job because the following processes might be down: JRM, ConfigMgmtServer or CTMJrmServer.	When VNM is unable to create a job used to configure VRF on devices	Check the processes status in Common Services > Server > Admin > Processes. If the process is down, restart the daemon manager and try again.
Upon clicking Finish, the commands displayed in the Summary page, will be deployed to the selected devices.	The Summary page displays the commands that will be deployed to the devices for the following workflows: Create VRF, Edit VRF, Extend VRF, Delete VRF and Assign Edge VLAN.	You can edit the commands in the previous page by clicking Back Or You can exit out the workflow by clicking Cancel.
Cannot connect to the CTM backend process.	VNM is unable to connect to the CTM backend process.	Check the VNMServer status from Common Services > Server > Admin > Processes. If the process is down, restart the daemon manager and try again.
Job for configuration deployment is successfully created. Refer Job Id.	Appears after the completion of a configuration workflow.	Click the Job Id to view the status of the job.
Troubleshooting VRF - Server side
An error occurred while getting the source devices from the server because the ANIDbEngine might be down.	While fetching the list of source devices from the server, ANIDbEngine might be down.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
An error occurred while getting the source devices from the server because the ANIDbEngine might be down.	While fetching the list of destination devices from the server, ANIDbEngine might be down.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
An error occurred while getting the VRF from the server because the ANIDbEngine might be down.	While fetching the list of VRFs from the server, ANIDbEngine might be down.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
An error occurred while getting the source interfaces from the server because the ANIDbEngine might be down.	While fetching the list of source interfaces from the server, ANIDbEngine might be down.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
An error occurred while getting the destination interfaces from the server because the ANIDbEngine might be down.	While fetching the list of destination interfaces from the server, ANIDbEngine might be down.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
An error occurred while retrieving the commands from the server.	An error occurred while getting the list of commands from the server.	None
Unable to connect to the device since it is not supported in RME.	When the device is not supported in RME.	None
RME database has failed because the RMEDBEngine might be down. Cannot get the output for the Ping or Traceroute operation.	While executing the command, if the DB fails in RME.	Check the status of RMEDBEngine in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
Cannot get the output for the selected devices after connecting to them using Ping or Traceroute. This is because these devices are not managed by RME.	The selected device is not managed by RME.	None
Cannot use Ping or Traceroute to connect to the device because it is not supported by RME.	The selected device is not supported by RME.	None
An error occurred while running the command in RME because the RMEExtnService or RMEDBEngine processes might be down.	An error occurred while executing the command in RME.	Check the status of RMEDBEngine in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
Select the VRF to proceed with VRF troubleshooting.	If you click View Command or Ping without selecting a VRF.	Select the VRF and click View Command or Ping.
Select the source device to proceed with VRF troubleshooting.	If you click View Command or Ping without selecting the source device.	Select the source device and click View Command or Ping.
Select the destination device to proceed with VRF troubleshooting.	If you click View Command or Ping without selecting the destination device.	Select the destination device and click View Command or Ping.
Select the destination interface to proceed with VRF troubleshooting.	If you click View Command or Ping without selecting the source interface.	Select the destination device and click View Command or Ping.
Select the source interface to proceed with VRF troubleshooting.	If you click View Command or Ping without selecting the source interface.	Select the destination device and click View Command or Ping.
An error occurred while getting the command from the server.	An error occurred while getting the command from the server.	Try again.
An error occurred while getting the output for Ping or Traceroute from the server because the RMEExtnService or RMEDBEngine processes might be down.	An error occurred while getting the output from the server.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
The DCR ID of the device is negative.	DCR ID of the device entered is negative.	Enter the positive DCR ID
Troubleshooting VRF - Client side
An error occurred while getting the devices from the server.	While getting a list of source or destination devices from the server.	Try again.
An error occurred while getting the VRFs from the server.	While getting a list of VRFs from the server.	Try again.
An error occurred while getting the Source interfaces from the server.	While getting a list of source interfaces from the server.	Try again.
An error occurred while getting the Destination interfaces from the server.	While getting a list of destination interfaces from the server.	Try again.
Select a Source device before attempting to troubleshoot VRF.	If you click View Command or Ping without selecting the source device.	Select the source device and click View Command or Ping.
Select a VRF before attempting to troubleshoot VRF.	If you click View Command or Ping without selecting the VRF.	Select the VRF and click View Command or Ping.
Select a Destination device before attempting to troubleshoot VRF.	If you click View Command or Ping without selecting the destination device.	Select the destination device and click View Command or Ping.
Select the Source interface before attempting to troubleshoot VRF.	If you click View Command or Ping without selecting the source interface.	Select the source interface and click View Command or Ping.
Select the Destination interface before attempting to troubleshoot VRF.	If you click View Command or Ping without selecting the destination interface.	Select the destination interface and click View Command or Ping.
Select the Source interface before attempting to troubleshoot VRF	If you select the Bidirectional Ping option and click View Command or Ping without selecting the source interface.	Select the Source interface and click View Command or Ping.
An error occurred while retrieving the commands from the server.	An error occurred while retrieving the commands from the server.	Try again
An error occurred while getting the output for Ping or Traceroute from the server.	An error occurred while getting the output from the server.	Check the ANIDbEngine status in Common Services > Server > Admin > Processes. If the process is down, restart it and try again.
An internal error occurred. An error occurred while getting the output for Ping or Traceroute from the server.	A general error has occurred.	Try again.