-
User Guide for Campus Manager 4.0.6 (With LMS 2.6)
-
Notices
-
Preface
-
Chapter 1 About Campus Manager
-
Chapter 2 Getting Started With Campus Manager
-
Chapter 3 Administering Campus Manager
-
Chapter 4 Integrating Campus Manager With CiscoWorks Common Services
-
Chapter 5 Tracking Users
-
Chapter 6 Discrepancy Reporting
-
Chapter 7 Using Topology Services
-
Chapter 8 Managing VLANs and VTP
-
Chapter 9 Managing Network Spanning Trees
-
Chapter 10 Support for IPv6
-
Chapter 11 Managing ATMs
-
Chapter 12 Path Analysis
-
Chapter 13 Data Extraction Engine
-
Index
-
Table Of Contents
Understanding Network and Campus Manager Dependencies
Using User Tracking Administration
Viewing Acquisition Information
Configuring User Tracking Acquisition Actions
Using User and Host Acquisition
Modifying Acquisition Settings
Modifying Acquisition Schedule
Specifying Domain Name Display
Configuring Subnet Acquisition
Importing Information on End Host Users
Understanding User Tracking Reports
Operator Values for Last Seen Column
Interpreting Duplicate Reports
Interpreting IP Phones Reports
Understanding Switch Port Usage Reports
Viewing Reports on Switch Port Usage
Interpreting Switch Port Usage Reports
Viewing List of Custom Reports
Viewing List of Custom Layouts
User Tracking Command Line Interface
Installing UTLite Script on Active Directory
Installing UTLite Script on Windows
Installing UTLite Script on NDS
Uninstalling UTLite Scripts From Windows
Uninstalling UTLite Scripts From Active Directory
Uninstalling UTLite Scripts From NDS
Hardware and Software Requirements for UTU 1.1.1
User Tracking Debugger Utility
Understanding Debugger Utility
Tracking Users
User Tracking application of Campus Manager allows you to track end stations. This chapter contains the following sections:
•
Understanding User Tracking Reports
•
•
•
Understanding User Tracking
User Tracking helps you to locate and track the end hosts in your network. This helps you to troubleshoot and analyze any connectivity issues. User Tracking identifies all end users connected to the discovered Cisco access layer switches on the network, including printers, servers, IP phones and PCs.
You can sort and query the User Tracking table that contains details, such as VLAN memberships, port assignments, end host specifications, switch ports, and switch to which the end users are connected.
Predefined reports, such as the reports on duplicate IP addresses or MAC addresses, multiple MAC addresses enable you to locate the mobile end users or any violation in port policies.
You can also configure User Tracking to collect usernames of the end hosts from UNIX hosts, Domain Name System (DNS), Primary Domain Controller (PDC), or Novell Directory Services (NDS). This makes it easier for you to locate and track specific users on your network.
Various Acquisitions in User Tracking
This section expalins the various acquisitions that can be done using Campus Manager, to get information about the end users.
User Tracking Major Acquisition
Discovers all the end hosts that are connected to the devices managed by Campu Manager.
User Tracking Minor Acquisition
Minor acquisition occurs on a device if any of the following changes take place:
•
•
•
•
Minor acquisition updates the Campus database, only with the changes that have happened in the network. It is triggered at regular intervals. The default for these intervals is 60 minutes. You can configure the interval at which the acquisition takes place. For details on modifying the acquisition interval, see Modifying Acquisition Schedule
User Tracking IP Phone Acquisition
Discovers all phones registered in Cisco Call Managers (CCM), that are managed by Campus Manager.
Subnet based User Tracking Major Acquisition
User tracking acquisition would run only on those subnets that are configured in Campus Manager . This would discover end hosts on all the vlans available in the configured subnets. For details on configuring subnets, see Configuring Subnet Acquisition
Single device on-demand User Tracking
This is a device based acquisition. It discovers the end hosts on all the vlans available in the selected device.
For details on initiating an Acquisition, see Configuring User Tracking Acquisition Actions
User Tracking Acquisition can also be initiated from the CLI prompt. To do so, enter the following command:
NMSROOT/campus/bin/ut -cli performMajorAcquisition -u userid -p password
where NMSROOT is the directory where you have installed CiscoWorks.
Using User Tracking
You can use User Tracking to:
•
•
•
•
•
•
You can use UTLite or configure User Tracking to collect usernames through ANI Server and update UT table during UT major acquisition.
•
For example, you can design a layout that displays only the MAC addresses of hosts on your network.
•
•
Understanding Network and Campus Manager Dependencies
For User Tracking to display user and host data, Campus Manager must perform Data Collection before User Tracking discovers end hosts and collects user data. Data Collection is done for active and properly configured devices in your network.
Therefore, before using User Tracking, you must:
1.
2.
3.
Using User Tracking Administration
You can perform the following administrative tasks using User Tracking Administration:
•
•
•
•
•
•
•
•
Viewing Acquisition Information
You can view acquisition information using the Acquisition tab of the Campus Manager User Tracking window.
To view acquisition information:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The acquisition information appears.
Configuring User Tracking Acquisition Actions
You can configure User Tracking acquisition actions using the Actions option in the Acquisition tab of the Campus User Tracking window.
To configure acquisition actions:
Step 1
The Campus User Tracking window appears.
Step 2
The Acquisition Actions dialog box appears.
Step 3
You do not have to specify any details for the IP Phones option.
Step 4
Using User and Host Acquisition
You can modify the Acquisition settings and Acquisition schedule using the User and Host Acquisition option in the Acquisition tab of the Campus User Tracking window.
This section contains:
•
•
•
•
•
Modifying Acquisition Settings
You can modify User Tracking Acquisition settings using the Acquisition Settings option of the Acquisition tab in Campus User Tracking window.
To modify acquisition settings:
Step 1
The Campus User Tracking window appears.
Step 2
The Acquisition Settings dialog box appears.
Step 3
Step 4
Modifying Acquisition Schedule
You can modify UT acquisition schedule using the Acquisition Schedule option of the Acquisition tab in Campus User Tracking window.
To modify acquisition schedule:
Step 1
The Campus User Tracking window appears.
Step 2
The Acquisition Schedule dialog box appears.
Step 3
Step 4
•
•
•
Step 5
Step 6
Specifying Purge Policy
You can specify the intervals at which old reports and jobs are to be purged, using the Purge Policy option of Reports in Campus User Tracking window. You can save the Purge Policy as a job or execute it immediately.
To specify the Purge Policy:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Settings dialog box appears.
Step 3
Step 4
Specifying Domain Name Display
You can specify the way in which domain names are to be displayed, using the Domain Names option of Reports in Campus User Tracking window.
To specify the Domain Name display:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Settings dialog box appears.
Step 3
You can:
•
•
•
Enter the domain name suffix in the field, if you choose to hide the specified domain name suffix.
Step 4
Modifying Ping Sweep Options
When Ping Sweep is enabled, the UTPing program in $NMSROOT/campus/bin will be invoked during acquisition to send out a sweep of pings for each subnet.
You can modify Ping Sweep option using the Ping Sweep option from the Admin tab in Campus User Tracking window.
To modify Ping Sweep options:
Step 1
The Campus User Tracking window appears.
Step 2
The Ping Sweep dialog box appears.
Step 3
Specify the Wait Interval, if Ping Sweep is enabled.
Step 4
You can select subnets from the list of available subnets and add to the list of subnets to be excluded. User Tracking does not perform Ping Sweep on large subnets.
For more details, see Note for Ping Sweep Option.
Step 5
Note for Ping Sweep Option
User Tracking does not perform Ping Sweep on large subnets. For example, subnets containing Class A and B addresses. Hence, ARP cache might not have some IP addresses and the User Tracking may not display the IP addresses.
In larger subnets, the Ping process leads to numerous ping responses that might increase the traffic on your network and result in extensive use of network resources.
To perform Ping Sweep on larger subnets, you can:
•
•
Configuring Subnet Acquisition
You can configure the subnets for User Tracking Acquisition. These configurations are used for User Tracking Major Acquisition and Configured Subnets based acquisition. You can choose to include or exclude specified subnets to perform User Tracking major acquisition.
To configure subnet acquisition:
Step 1
The Campus User Tracking window appears.
Step 2
The Configure Subnet Acquisition dialog box appears.
Step 3
•
All the subnets are included for User Tracking Major Acquisition. If you select this option do not perform steps 4 and 5.
Or
•
The action depends on the Filter value.
Step 4
•
All subnets added to the Selected Subnets list are included for User Tracking acquisition. If none of the subnets are added to the Selected Subnets list, User Tracking Acquisition runs on all subnets.
Or
•
All subnets added to the Selected Subnets list are excluded for User Tracking acquisition. If none of the subnets are added to the Selected Subnets list, all the subnets available in the Available Subnets list are included for acquisition.
Step 5
Step 6
Modifying Delete Interval
You can modify the interval for deleting entries from the end host table or the IP table using the Delete Interval option of the Admin tab in Campus User Tracking window.
To modify the Delete Interval:
Step 1
The Campus User Tracking window appears.
Step 2
The Delete Interval dialog box appears.
Step 3
Step 4
Step 5
Importing Information on End Host Users
You can import from a file, user names and notes for end hosts already discovered, using the End Host Table Import option of the Admin tab in the Campus User Tracking window.
To import information in end host users:
Step 1
The Campus User Tracking window appears.
Step 2
The End Host Table Import dialog box appears.
Step 3
Step 4
Understanding User Tracking Reports
User Tracking automatically locates servers and end-user workstations, and Cisco voice over IP (VoIP) telephone handsets and their connections to Layer 2 Cisco switches. During this acquisition process, it also tabulates specific connection information about the end station.
The Reports section provides various options to view, create and schedule various reports that User Tracking provides.
Using User Tracking Reports
The Reports section provides various options to view, create and schedule various reports that User Tracking provides. This section contains:
•
Viewing Quick Reports
You can view the reports on end hosts or IP phones, based on the credential for which you want to generate the report, using the Quick Report generator in Campus Manager User Tracking application.
To view the reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Quick Report dialog box appears.
Step 3
Table 5-4 Viewing Quick Reports
Select a type
Select the type of report that you wish to view.
The two types of reports that are available are:
•
•
Column
Select a query expression based on which you want to generate the report.
To view a list of valid query expressions, click the drop-down arrow.
The information on the other query expressions are available in the corresponding report.
Operator
Logical operator for the query expression.
To view a list of valid operators click the drop-down arrow.
For a list of possible values for Last Seen column, see Operator Values for Last Seen Column.
Pattern
Pattern for the selected query expression.
Enter the pattern for the selected query expression.
The Pattern field is mandatory for all other Operator options except for is null and is not null.
Step 4
The selected type of report appears in the standard layout. The data displayed depends on the query expression specified. For details on the report, see Interpreting End Host Reports.
You can also view all end hosts or IP phones in your network using User Tracking. For more details, see Viewing End Hosts Reports and Viewing IP Phones Reports.
Operator Values for Last Seen Column
Table 5-5 lists the operators available for the Last Seen column and their corresponding values for Pattern field.
Viewing Report Jobs List
You can view a list of scheduled jobs and their current status using the Report Jobs option of Campus User Tracking window.
To view Report Jobs:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Viewing Job Details
To view the details of a selected job:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
Step 4
Stopping Jobs
To stop a scheduled job:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
Step 4
Deleting Jobs
To delete a job:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
Step 4
Using Report Generator
The Report Generator in User Tracking allows you to view System-defined reports and Custom reports. You can also schedule to generate these reports immediately, once, daily, weekly, monthly, or quarterly.
You can generate the following reports using Report Generator:
To use the report generator:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
The report is generated.
To modify the settings, click Reset.
Viewing Duplicates Report
You can generate the following reports to get the details of all duplicate IP addresses, duplicate MAC addresses, duplicate VLANs, or ports with multiple MAC addresses.
•
•
•
•
To view reports on duplicates:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
The report is generated.
To modify the fields, click Reset.
Interpreting Duplicate Reports
Table 5-7 provides details of the columns in Standard Layout.
Table 5-8 provides details of the columns in All Columns Layout.
Viewing End Hosts Reports
You can view a report on all end host entries using the End Hosts option in the Reports Generator dialog box.
To view report on end hosts:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
The report is generated.
To modify the settings, click Reset.
Interpreting End Host Reports
Filters in the report operate on the selected column and fetch records containing the user input value.
For example, If there are 10 records with device name XYZ , then a filter for Device Name field with value YZ will fetch these 10 records.
Table 5-9 provides details of the columns in End Hosts Report—Standard Layout
Table 5-10 provides details of the columns in End Hosts Report—All Columns Layout
Viewing IP Phones Reports
You can view a report on all IP phones in the network using the IP Phones option of the Report Generator dialog box.
To view report in IP phones:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
The report is generated.
Interpreting IP Phones Reports
Table 5-11 gives details of the columns in IP Phones Report—Standard Layout.
Table 5-12 gives details of the columns in the IP Phones Report—All Columns Layout.
Understanding Switch Port Usage Reports
You can generate three types of reports using Campus Manager, based on the status of the switch ports.
•
You can use the Advanced Search feature to select the devices for which you want to generate reports. For more details on performing advanced search, see Using Advanced Search.
For a detailed description of the features in Device Selector, see User Guide for Common Services 3.0.5
Report on Unused Down Ports
Campus Manager generates report for administratively down ports, which are not connected to any device or end host after the last User Tracking Acquisition..
Report on Unused Up Ports
Campus Manager generates report for administratively up ports, which are not connected to any device or end host after the last User Tracking Acquisition.
Report on Recently Down Ports
Campus Manager generates report for the ports, which were earlier connected to a device or end host, but are not connected when the last User Tracking Acquisition was completed.
Using Advanced Search
The Advanced search feature in Device Selector helps you search for devices based on a set of search criteria which you specify in the Advanced Search window. You can either select the search criteria from the drop-down menu or enter custom search criteria in the Rule Text area, or use a combination of both. When you enter the search criteria manually, you can use the Check Syntax button to verify whether the Rule Expression you have entered is correct.
You can define single or multiple search criteria based on which you can search for devices. Table 5-13 describes the device attributes available for defining rules.
Operator
The operator used in forming a rule. The following operators are available:
•
•
When the variable DiscoveryStatus is used, only one operator is available, which is equals.
Value
A free flow operand forming the last part of the rule.
When the variable DiscoveryStatus is used, only the following values are available:
•
•
•
Viewing Reports on Switch Port Usage
You can view reports on Switch port usage using the Switch Port Usage option of the Report Generator dialog box. You can view reports on switch ports that have been recently down, unused and down, and unused and up.
To view report on switch port usage:
Step 1
The Campus User Tracking window appears.
Step 2
The Report Generator page appears.
Step 3
Step 4
The Device Selector appears.
Step 5
Step 6
Step 7
Step 8
The report is generated.
Interpreting Switch Port Usage Reports
Table 5-14 describes the columns of a Switch Port Usage report.
Using Custom Reports
You can create, view, edit, copy, and delete user-defined reports for end hosts and IP phones using the Custom Reports option in the Reports tab of Campus User Tracking window. This section contains:
•
Viewing List of Custom Reports
You can view the list of Custom reports using the Custom Reports option in the Reports tab of the Campus User Tracking window.
To view the list of Custom reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Creating Custom Reports
You can create Custom reports by clicking Create in the Available Custom Reports dialog box.
To create Custom reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
You can use the Custom Reports wizard to customize and create reports. The Type selection page appears.
Step 4
•
•
Step 5
The Group Selection page appears.
Step 6
Step 7
The Properties and Query Expression page appears.
Table 5-15 explains the fields in Properties and Query pane.
Table 5-15 Properties and Query Pane Field Description
Name
Enter a name for the query you are going to create.
Description
Enter a description for the query you are going to create.
Select a type
•
•
Select the type of query.
•
In the Query Expression area, select the radio button to search using any of the options or all the options that you select.
Select the options for the query, from:
–
–
–
For a detailed list of operator values for the Last Seen column, see Table 5-5.
•
You can enter the query string in the Query Text area. Click Check Syntax to validate the query string.
Select the options to create the query string, from the Query Expression area.
You can choose the sort criteria and add the string for them.
Step 8
The Summary page appears. The Custom Report Summary pane displays a summary of the values and options you have selected for the query to generate the report.
Editing Custom Reports
You can edit Custom reports by clicking Edit in the Available Custom Reports dialog box.
To edit Custom reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
You can use the Custom Reports wizard to modify group, report properties, and query expressions.
Copying Custom Reports
You can copy Custom reports by clicking Copy in the Available Custom Reports dialog box.
To copy Custom reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
You can use the Custom Reports wizard to modify the Name of the report, group, report properties, and query expressions.
Deleting Custom Reports
You can delete Custom reports by selecting a report from the Available Custom Reports dialog box and clicking Delete.
To delete Custom reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
Exporting Reports
To export a report:
Step 1
The Exporting Report dialog box appears.
Step 2
Step 3
Step 4
The report is exported.
Printing Reports
To print a report:
Step 1
The Printing Report dialog box appears.
Step 2
Step 3
The report is printed.
Using Custom Layouts
You can create or customize the columns displayed in Custom Report using Custom Layouts option in the Reports tab of Campus User Tracking window.
This section contains:
•
Viewing List of Custom Layouts
You can view the list of Custom layouts using the Custom Layouts option in the Reports tab of the Campus User Tracking window.
To view the list of Custom layouts:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Note
Creating Custom Layouts
You can create Custom layouts by clicking Create in the Available Custom Layouts dialog box.
To create Custom layouts:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Editing Custom Layouts
You can edit Custom layouts by clicking Edit in the Available Custom Layouts dialog box.
To edit Custom reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Note
Copying Custom Layouts
You can copy Custom layouts by clicking Copy in the Available Custom Layouts dialog box.
To copy Custom layouts:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Deleting Custom Layouts
You can delete Custom layouts by selecting a layout from the Available Custom Layouts dialog box and clicking Delete.
To delete Custom layouts:
Step 1
The Campus User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Using Archived Reports
You can create, view, edit, copy, and delete archived reports using the Archives option in the Reports tab of Campus User Tracking window. This section contains:
•
Viewing Archived Reports List
You can view a list of scheduled reports using the Reports Archive option.
To view a list of archived reports:
Step 1
The Campus User Tracking window appears.
Step 2
The Archives dialog box appears with the list of archived reports.
Viewing Reports
You can view a report using:
•
•
•
•
Using the Report Jobs Option
This section explains how you can view reports of the scheduled jobs
Step 1
The Campus User Tracking window appears.
Step 2
The Report Jobs dialog box appears with the list of scheduled jobs.
Step 3
Using the Report Generator Option
This section explains how you can generate a report using Report Generator.
Step 1
The Campus User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
The report is generated.
Using the Archives Option
This section explains how you can view a report from the archives.
Step 1
The Campus User Tracking window appears.
Step 2
The Archives dialog box appears.
Step 3
Using the Device Center
This section explains how you can view reports for a specified device.
Step 1
Step 2
•
Or
•
The Campus Manager reports available for the selected device appears under the Reports column in the Functions Available area.
Step 3
Table 5-9 gives details of the columns in End Hosts Report - Standard Layout
Table 5-11 gives details of the columns in IP Phones Report - Standard Layout
Table 5-10 gives details of the columns in End Hosts Report - All Columns Layout
Table 5-12 gives details of the columns in the IP Phones Report - All Columns Layout.
Table 5-14 gives details of the columns in Switch Port Usage Report.
Deleting Archived Reports
You can delete an archived report by selecting the report from the list of archived reports and clicking Delete.
To delete an archived report:
Step 1
The Campus User Tracking window appears.
Step 2
The Archives dialog box appears with the list of archived reports.
Step 3
User Tracking Command Line Interface
You can execute User Tracking commands from the command line in Solaris and Windows 2000.
Enter ut options -u username -p password.
The options can be one or more of those shown in Table 5-16.
•
•
•
Table 5-16 User Tracking CLI Commands
-cli
No keywords or arguments.
Runs User Tracking in command-line mode.
-prompt
No keywords or arguments.
This command is required if you do not enter your password from the command line.
If -prompt is specified, User Tracking asks you to type in your password.
-help
No keywords or arguments.
Prints the command line usage.
-ping
{enable | disable}
Enables the Ping Sweep option so that the Campus Manager Server pings every IP address on known subnets before discovery. The default is the last setting used.
For more details, see Modifying Ping Sweep Options.
User Tracking does not perform Ping Sweep on large subnets, for example, subnets containing Class A and B addresses.
Hence, ARP cache might not have some IP addresses and the User Tracking may not display the IP addresses.
In larger subnets, the ping process leads to numerous ping responses that might increase the traffic on your network and result in extensive use of network resources.
To perform Ping Sweep on larger subnets, you can:
•
To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.
•
This will ensure that when you run User Tracking Acquisition, the ARP cache of the router contains the IP addresses.
-performMajorAcquisition
No keywords or arguments.
Acquires data about all users and hosts on the network and updates the Campus Manager database.
This option starts an acquisition but does not wait for its completion.
-query
This option takes one of the following arguments:
Queries the Campus Manager database and updates the User Tracking table.
all
Gets all User Tracking entries. Similar to "All Host Entries"/simple query in the GUI.
name
Runs the named advanced/simple query, created earlier in the GUI.
dupMAC
Finds duplicate MAC addresses.
dupIP
Finds duplicate IP addresses.
hub
Finds ports with multiple MAC addresses (hubs).
-queryPhone
all
Gets all IP Phone entries.
name
Runs the named advanced query, created earlier in the GUI.
-layout
layout_name
Uses the specified main table layout while performing a query to fetch User Tracking display entries.
-layoutPhone
layout_name
Uses the specified IP phone table layout while performing a query to fetch IP phone display entries.
-host
Campus Manager Server device name or IP Address
Specifies the host name or IP address of the machine running the Campus Manager Server.
This argument is mandatory if the User Tracking client and the Campus Manager Server are running on different subnets.
-port
Campus Manager Server web port number
Specifies the web server port number of the Campus Manager Server. The default is 1741.
-export
filename
Exports data to a text file.
You must first specify the -query option to fetch the data that you want to export.
-import
filename
Imports lost or deleted UserName and Notes fields from the last exported file.
-stat
No keywords or arguments.
Displays statistical information, such as time of last acquisition, acquisition status, number of records in the User Tracking database, and so on.
-debug
No keywords or arguments.
Enables trace and debug messages for the User Tracking client application.
Importing User Tracking Data
You can import User Tracking data from previous releases like Campus Manager 3.3 and Campus Manager 4.0 into the current database.
The data from the old database, has to be exported into files as Comma Separated or Tab Separated values, through the Command Line Interface (CLI). It is mandatory to have the field MAC Address in the exported file.
To import data:
Step 1
NMSROOT/campus/
where NMSROOT is the directory where you have installed CiscoWorks.
Step 2
NMSROOT/bin/perl/opt/CSCOpx/campus/bin/utupgrade.pl -f import_filename
-f forces all the entries to the database.
The data is imported.
Note
Understanding UTLite
UTLite is a utility that allows you to collect user names from Primary Domain Controllers, Active Directory, and Novell servers.
To do this you need to install UTLite in the Windows Primary Domain Controllers and in the Novell servers. You can also install UTLite in an Active Directory server.
This section contains:
•
•
•
•
•
•
Installing UTLite Script on Active Directory
You must install the UTLite script on the Active Directory server and update the server's logon script to get user logon information from Active Directory hosts.
You must have Administrator privileges on the Active Directory server to install the UTLite logon script.
To install the script:
Step 1
a.
b.
C:\Program Files\CSCOpx\campus\bin\UTLite33.exe
C:\Program Files\CSCOpx\campus\bin\UTLiteNT.bat
where C:\Program Files\ is the directory in which you installed CiscoWorks.
c.
NETLOGON is located at:
%SystemRoot%\sysvol\sysvol\domain DNS name\scriptswhere %SystemRoot% is usually c:\winnt and domain DNS name is the DNS name of the domain
Step 2
Step 3
Step 4
start %WINDIR%\UTLite33 -domain domain -host ipaddress -port 16236
If port 16236 is already in use, enter a different number. This port number must match the number that you entered in the Use Port Number field, in the User Tracking > Admin > Acquisition > Acquisition Settings page.
For more details, see Modifying Ping Sweep Options.
Step 5
UTLiteNT.bat
Step 6
The first time users log into the network after you edit this script, UTLite33.exe is copied to the local WINDIR directory on their Windows client system.
Installing UTLite Script on Windows
You must install the UTLite script on the primary domain controller and update the domain controller's logon script to get user logon information from Windows hosts. Do this once for each domain.
You must have Administrator privileges on the primary domain controller to install the UTLite logon script.
Step 1
a.
b.
C:\Program Files\CSCOpx\campus\bin\UTLite33.exe
C:\Program Files\CSCOpx\campus\bin\UTLiteNT.bat
where C:\Program Files\ is the directory in which you installed CiscoWorks.
c.
NETLOGON is located at
%SYSTEMROOT%\system32\Repl\Import\Scripts,where, SYSTEMROOT% is the root directory for the Windows operating system files.
Step 2
a.
b.
start %WINDIR%\UTLite33 -domain domain -host ipaddress -port 16236
If port 16236 is already in use, enter a different number. This port number must match the number that you entered in the Use Port Number field, in User Tracking > Admin > Acquisition > Acquisition Settings page.
For more details, see Modifying Acquisition Settings.
Step 3
UTLiteNT.bat
Step 4
The first time users log into the network after you edit this script, UTLite33.exe is copied to the local WINDIR directory on their Windows client system.
Installing UTLite Script on NDS
You must install the UTLite script on the Novell Server and update the domain controller's logon script, to get user logon information from Windows hosts. You only need to do this once for each domain.
You must have ZenWorks installed and running on the Novell Server, and you must be using NDS 5.0 or later.
Step 1
Step 2
Step 3
•
•
where C:\Program Files\ is the directory in which you installed CiscoWorks.
Step 4
Step 5
Step 6
Step 7
start %WINDIR%\UTLite33 -domain domain -host ipaddress -port 16236
If port 16236 is already in use, enter a different number. This port number must match the number that you entered in the Use Port Number field, in User Tracking > Admin > Acquisition > Acquisition Settings page.
For more details, see Modifying Ping Sweep Options.
Step 8
Step 9
Step 10
Step 11
Step 12
@\\%FILE_SERVER%\sys\public\your_folder_name\UTLiteNDS.bat where your_folder_name is the name of the folder you created in Step 1.
Uninstalling UTLite Scripts From Windows
If you choose not to have Campus Manager server automatically collect user names, follow these instructions to properly remove the UTLite scripts.
Step 1
Step 2
Step 3
To quickly locate the WINDIR directory, enter set windir from a command prompt window on each client.
Uninstalling UTLite Scripts From Active Directory
If you choose not to have Campus Manager server automatically collect user names, follow these instructions to properly remove the UTLite scripts.
Step 1
Step 2
Step 3
To quickly locate the WINDIR directory, enter set windir from a command prompt window on each client.
Uninstalling UTLite Scripts From NDS
If you choose not to have Campus Manager server automatically collect user names, you must perform these steps to properly remove the UTLite scripts:
Step 1
Step 2
Step 3
To quickly locate the WINDIR directory, enter set windir from a command prompt window on each client.
User Tracking Utility
CiscoWorks User Tracking Utility 1.1.1 is a Windows desktop utility that provides quick access to useful information about users or hosts discovered by Campus Manager User Tracking application. This section contains:
•
Understanding UTU 1.1.1
User Tracking Utility 1.1.1 (UTU 1.1.1) allows users with Help Desk access to search for users or hosts discovered by Campus Manager User Tracking application. UTU comprises a server-side component and a client utility.To use UTU, Campus Manager must be installed and functioning on your machine, and accessible through the network.
UTU 1.1.1 has the following additional features:
•
•
Secure Sockets Layer (SSL) mode, as well as Non SSL mode.Definitions
Table 5-17 explains certain terms and definitions used in User Tracking Utility.
Hardware and Software Requirements for UTU 1.1.1
Table 5-18 lists the minimum system requirements for UTU.
Using User Tracking Utility
You can use the UTU search band to search for the Users/Hosts in your network. You can search using user name, host name or IP address, or MAC address. Searching by Host is the default search criteria. This section describes:
Downloading UTU 1.1.1
UTU requires CiscoWorksUserTrackingUtility1.1.1.exe file to be downloaded and installed.
Step 1
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus-crypto
Step 2
Installing UTU 1.1.1
UTU 1.1.1 supports installation in normal installation mode and silent installation mode.
To install UTU 1.1.1 in normal installation mode:
Step 1
Step 2
Step 3
The User Tracking Utility Welcome screen appears.
Step 4
The Choose Destination Location dialog box appears. By default, UTU is installed in the directory C:\Program Files\CSCOutu.
Step 5
Or
a.
b.
The Configure CiscoWorks Campus Manager Server Details dialog box appears.
Step 6
Step 7
Step 8
The following message appears:
Is CiscoWorks LMS Server SSL Enabled?
Step 9
The Configure LMS Server Authentication dialog box appears. You can also configure these server details after installation.
Step 10
This is used to verify the validity of the user when searching for users or hosts.
Step 11
The Setup Complete dialog box appears.
Step 12
User Tracking Utility 1.1.1 is installed at the destination location you specified in Step 5 above.
However, it does not create a program group under Start > Programs. To access the utility, see Accessing UTU 1.1.1.
To install UTU in silent mode:
At the command prompt, enter:
exe-location\CiscoWorksUserTrackingUtility1.1.1.exe -a -s -f1file-location\setup.iss
where
•
•
Do not use space after the -f1 option. Use the complete path for file-location.
For example:
If the install directory for UTU is C:\utu, enter the following at the command prompt:
c:\utu\CiscoWorksUserTrackingUtility1.1.1.exe -a -s -f1c:\utu\setup.iss
To configure the server information, modify the setup.iss file before running the silent install. Edit the following fields:
[SdShowDlgEdit2-0]szEdit1= hostnameszEdit2= server-portResult=1[AskYesNo-0]Result=1 <1- SSL Enabled, 0 - SSL Disabled>[SdShowDlgEdit3-0]szEdit1=usernameszEdit2=passwordszEdit3=passwordYou cannot re-install UTU on a system that already has this application installed on it. You must check for existing installations of UTU before beginning a fresh installation.
To confirm UTU installation on your system, right-click the taskbar and select Toolbars of your machine. You can find User Search Band option in the popup menu.
Accessing UTU 1.1.1
To display the UTU desktop band on the taskbar:
Step 1
Step 2
Figure 5-1 Selecting the Toolbar
The UTU desktop band appears on the taskbar with the title User Information.
Configuring UTU 1.1.1
You must configure UTU only if you want to change the Campus Manager server configurations that you entered while installing UTU.
To configure UTU:
Step 1
A popup menu appears.
Step 2
The Campus Manager Server Configuration dialog box appears.
Step 3
Step 4
The port number changes to 443, which is the default port for SSL. See Figure 5-2.
Figure 5-2 Enabling SSL
Step 5
Searching for Users or Hosts
You can use UTU search band to search for the users or hosts in your network. You can search using user name, host name or IP address, or MAC address. The default search criterion is host name or IP address of the host.
To search for users or hosts:
Step 1
The default search criterion is host name or IP address of the host. To customize this search criterion:
a.
A popup menu appears with the default search criterion Host/IP selected.
b.
The selected criterion is set for future searches until you change the criterion.
Table 5-19 describes the search criteria in UTU 1.1.1.
Table 5-19 Search Criteria in UTU
User
User name of the hosts in the network.
Host/IP
Host name or IP address.
MAC Address
MAC address of the hosts in the network.
Step 2
For example, you can enter 10.77.208* in the User Information field.
Step 3
If your server is not SSL enabled, go to Step 6.
When you query for data from an SSL enabled server, the Certificate Viewer dialog box appears. See Figure 5-3.
Figure 5-3 Certificate Viewer
Step 4
You can verify the authenticity and correctness of the SSL server here. See Figure 5-4.
Figure 5-4 Certificate Details
Step 5
SSL connection is established with the server.
If you click No, the certificate is not stored and no connection is established with the server.
The Certificate Viewer dialog box appears only for the first time configuration. If you had clicked Yes the first time, you are not prompted to store the certificate during subsequent sessions.
Step 6
UTU displays the search results,. This is a list of user names, host names, IP addresses, or MAC addresses, in a Select Entry popup menu.
Step 7
Another popup box appears with the details for that particular entry, as described in Table 5-20.
The search results for the value you enter in the User Information field depends on the default search criterion.
Using Search Patterns
UTU searches for the user or hosts, which match the user name, host name or IP address, or MAC address. You can search for users or hosts by entering a pattern. For example, if you enter,
•
•
•
Uninstalling UTU 1.1.1
Before you uninstall UTU 1.1.1, you must hide the UTU desktop band.
To do that, right-click the taskbar of the machine on which you installed UTU, and deselect User Search Band in the Toolbars popup menu.
To uninstall UTU 1.1.1:
Step 1
The Add/Remove Programs dialog box appears.
Step 2
Step 3
The system prompts you to confirm uninstallation.
Step 4
The Remove Programs From Your Computer dialog box appears.
Step 5
a.
The shared DLL, and UTBand.dll files, are removed.
b.
Or
a.
The uninstallation proceeds, but it does not completely uninstall UTU. To complete the uninstallation process, you must:
b.
The default directory is C:\Program Files\CSCOutu.
Step 6
The following message appears:
DLLUnregisterServer in UTBand.dll failed
Step 7
Step 8
This removes the UTU installation completely from the machine.
Step 9
Upgrading to UTU 1.1.1
You can upgrade User Tracking Utility from UTU 1.1 to UTU 1.1.1.
When you install UTU 1.1.1 above UTU 1.1, UTU prompts you to uninstall the previous version. A message appears:
WARNING: The setup program has detected a previous version of CiscoWorks User Tracking Utility. To install CiscoWorks User Tracking Utility 1.1.1, previous version of the product must be uninstalled. Do you want to uninstall CiscoWorks User Tracking Utility 1.1 now?Yes/NoClick either Yes to upgrade, or No to quit.
User Tracking Debugger Utility
The User Tracking Debugger Utility is a command line tool to help debug common problems with User Tracking. This section contains:
•
Understanding Debugger Utility
The utility provides a report on the reasons why User Tracking failed to discover end hosts on specific ports.
In many cases, User Tracking may fail to perform as expected due to unexpected behavior by other applications like Campus Manager Server (for example, devices not discovered by Campus Manager server) and Topology Services (for example, inadequate VLAN discovery).
You can run the utility to troubleshoot problems, or provide the report, and log generated by the utility when you contact TAC for help in diagnosing problems.
The debugger utility uses the data collected by Campus Manager Server and reports the reasons for the missing ports in User Tracking.
This tool also has an SNMP component embedded which runs a SNMP query for the table as a part of verification for SNMP failure. For example, SNMP bugs in Catalyst operating system because of which User Tracking may fail to discover devices.
This generates an Action Report for which may be used for analyzing the data.
The Debugger Utility:
1.
2.
3.
4.
Using Debugger Utility
The Debugger Utility is available at $NMSROOT/campus/bin/ (where $NMSROOT is the directory where you have installed CiscoWorks).
To run the Debugger Utility, run the command:
utdebug -switch switch-ip -port port1[,port2 ...] [-export filename]
where,
switch is the switch to which the end hosts are connected.
ports are the ports on the switch which have missing end hosts User Tracking.
-export filename specifies that the debug messages be stored in the file specified. If this option is not used, the messages are displayed on the console.
For example:
utdebug -switch 10.29.6.12 -port 5/12utdebug -switch 10.29.100.10 -port Fa0/10utdebug -switch 10.29.6.14 -port Gi6Troubleshooting User Tracking
Use the information in Table 5-21 to troubleshoot the User Tracking application.
Table 5-21 Troubleshooting User Tracking
User Tracking cannot discover any users or hosts
or
User Tracking cannot display any IP phones.
There may be no information in the Campus Manager database.
The device might not be part of DCR and you must run Device Discovery and Data Collection.
For more details, see Understanding Campus Manager Administration.
User Tracking cannot discover certain users or hosts.
The Campus Manager Server might not have discovered one or more devices to which users and hosts are connected.
1.
2.
3.
User Tracking cannot discover certain IP phones.
The Campus Manager Server might not have discovered the specific Media Convergence Server (MCS) that runs the instance of Cisco CallManager to which the IP phones are registered.
1.
2.
3.
User Tracking table does not contain device name, IP address, and subnet information for some hosts.
User Tracking cannot find the most recent network information.
Network changes are not currently reflected in ARP information (routers) or bridge tables (switches).
User Tracking does not perform Ping Sweep on large subnets; for example, subnets containing Class A and B addresses.
Hence, ARP cache might not have some IP addresses and the User Tracking may not display the IP addresses.
In larger subnets, the ping process leads to numerous ping responses that might increase the traffic on your network and result in extensive use of network resources.
Enable Ping Sweeps when User Tracking performs discovery. Ping Sweeps are enabled by default.
To perform Ping Sweep on larger subnets, you can either:
•
To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.
Or
•
This will ensure that when you run User Tracking Acquisition the ARP cache of the router contains the IP addresses.
You have:
•
•
The changes do not appear in the User Tracking display.
A complete device discovery process has not run since you added your changes.
User Tracking discovery is not a full network discovery. The process discovers only the user and host data in your network.
Changes that you make to your network might not appear after a User Tracking discovery.
1.
2.
3.
User Tracking FAQs
Use the information in these sections to answer some of your common questions:
•
•
•
•
•
•
•
Q.
A.
–
–
–
User Tracking does not automatically delete outdated end-user host entries. To delete these entries:
–
Or
–
Q.
A.
The IP phone table appears in a separate window from the window that displays the main User Tracking table. You cannot run any commands from this window. You can only run commands from the main User Tracking table. See the User Tracking command reference for more information.
Q.
A.
–
–
The Campus Manager Server stores this information in the database. User Tracking discovers the host and user information in the Campus Manager server database, correlates this information, and displays it in the User Tracking Reports.
For more information about the device discovery process, see Using Device Discovery Administration.
Q.
A.
With these device lists in place, the User Tracking service performs steps described in Table 5-22.
Q.
A.
You must check if 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 the subnets, which 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. For more details on Ping Sweep, see Note for Ping Sweep Option.
Q.
A.
Q.
A.
Q.
A.
