User Guide for Campus Manager 4.0.6 (With LMS 2.6)
Chapter 5 Tracking Users
Downloads: This chapterpdf (PDF - 660.0KB) The complete bookPDF (PDF - 13.54MB) | Feedback

Tracking Users

Table Of Contents

Tracking Users

Understanding User Tracking

Using User Tracking

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 Purge Policy

Specifying Domain Name Display

Modifying Ping Sweep Options

Configuring Subnet Acquisition

Modifying Delete Interval

Importing Information on End Host Users

Understanding User Tracking Reports

Using User Tracking Reports

Viewing Quick Reports

Operator Values for Last Seen Column

Viewing Report Jobs List

Viewing Job Details

Stopping Jobs

Deleting Jobs

Using Report Generator

Viewing Duplicates Report

Interpreting Duplicate Reports

Viewing End Hosts Reports

Interpreting End Host Reports

Viewing IP Phones Reports

Interpreting IP Phones Reports

Understanding Switch Port Usage Reports

Report on Unused Down Ports

Report on Unused Up Ports

Report on Recently Down Ports

Using Advanced Search

Viewing Reports on Switch Port Usage

Interpreting Switch Port Usage Reports

Using Custom Reports

Viewing List of Custom Reports

Creating Custom Reports

Editing Custom Reports

Copying Custom Reports

Deleting Custom Reports

Exporting Reports

Printing Reports

Using Custom Layouts

Viewing List of Custom Layouts

Creating Custom Layouts

Editing Custom Layouts

Copying Custom Layouts

Deleting Custom Layouts

Using Archived Reports

Viewing Archived Reports List

Viewing Reports

Deleting Archived Reports

User Tracking Command Line Interface

Importing User Tracking Data

Understanding UTLite

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

User Tracking Utility

Understanding UTU 1.1.1

Definitions

Hardware and Software Requirements for UTU 1.1.1

Using User Tracking Utility

Downloading UTU 1.1.1

Installing UTU 1.1.1

Accessing UTU 1.1.1

Configuring UTU 1.1.1

Searching for Users or Hosts

Uninstalling UTU 1.1.1

Upgrading to UTU 1.1.1

User Tracking Debugger Utility

Understanding Debugger Utility

Using Debugger Utility

Troubleshooting User Tracking

User Tracking FAQs


Tracking Users


User Tracking application of Campus Manager allows you to track end stations. This chapter contains the following sections:

Understanding User Tracking

Understanding User Tracking Reports

Using User Tracking Reports

User Tracking Command Line Interface

Understanding UTLite

User Tracking Utility

User Tracking Debugger Utility

Troubleshooting User Tracking

User Tracking FAQs

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:

A new device is added to the network.

A port changes state. That is if it comes up or goes down.

A new VLAN is added to the network.

There is a change in the existing VLAN.

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:

Display information about the connectivity between the devices, users, and hosts in your network. For example, you might want to identify all users connected to a particular subnet, or all hosts on a particular switch.

Display information about the IP phones registered with discovered Media Convergence Servers.

Use simple queries to limit the amount of information User Tracking displays.

Configure or limit the User Tracking acquisition by subnets.

Create and save simple and advanced queries.

Modify, add, and delete username and notes.

You can use UTLite or configure User Tracking to collect usernames through ANI Server and update UT table during UT major acquisition.

Customize User Tracking table layouts.

For example, you can design a layout that displays only the MAC addresses of hosts on your network.

View User Tracking reports that identify Switch Port Usage, duplicate IP addresses, duplicate MAC addresses, duplicate MAC and VLAN names, and ports with multiple MAC addresses. You can set the schedule for generating the reports, and also generate the reports for a subset of devices.

Launch Device Center, host center, phone center.

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. Set up your network devices so that they can be discovered. This includes enabling Cisco Discovery Protocol (CDP) and Integrated Local Management Interface (ILMI), enabling SNMP, and configuring VLAN Trunk Protocol.

2. Set up the Data Collection Server so that it can successfully collect data for devices in the network. This includes providing SNMP community strings and selecting a seed device.

3. Run device discovery and data collection processes.

Using User Tracking Administration

You can perform the following administrative tasks using User Tracking Administration:

Modify Acquisition settings. For more details, see Modifying Acquisition Settings.

Schedule Acquisition. For more details, see Modifying Acquisition Schedule.

Specify Purge Policy. For more details, see Specifying Purge Policy.

Specify Domain Name display. For more details, see Specifying Domain Name Display.

Configure Ping Sweep options for Acquisition. For more details, see Modifying Ping Sweep Options.

Configure subnet Acquisition. For more details, see Configuring Subnet Acquisition.

Configure end host and IP phone data delete interval. For more details, see Modifying Delete Interval.

Import information on end hosts. For more details, see Importing Information on End Host Users.

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 Select Campus Manager > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Click Acquisition.

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Click Acquisition > Actions.

The Acquisition Actions dialog box appears.

Step 3 Configure Acquisition Actions as specified in Table 5-1.

Table 5-1 Acquisition Actions 

Field
Description
Usage Notes

Select a type

You can select the type of acquisition. Type of acquisition can be:

Devices

Subnets

IP Phones

When you select a type of acquisition the appropriate fields appear.

Devices

Scope Selection

Select the All hosts and users check box to acquire information about all hosts and users in your network.

If you do not select the All hosts and users check box, the device selection field is enabled and you can enter the name or IP address of the device about which data is to be acquired.

Device Selection

Device Name or IP Address

Enter the name or IP address of the device about which data is to be acquired.

Click Select to select the device from the list of available devices.

Subnets

Type Selection

You can choose to get data about a particular subnet or all the configured subnets.

If you choose to acquire data about a particular subnet, the subnet selection fields are enabled.

Subnet Selection

Subnet ID

Enter the ID/IDs of the subnet/subnets on which you need to get data.

This field is enabled only if you select the Subnet option in the Type Selection area.

Click Select to select the subnet ID from the list of available subnets.

You can select multiple subnets by selecting the check boxes. The selected subnets will be listed in the text area in the format subnet/subnet mask.

Acquire Only VLAN Specific to Subnet

Select this check box to get data only about the VLANs specific to the subnet.

If you select this checkbox, Campus gets the list of devices associated with the selected subnets and acquires end hosts only on VLANs that are specific to those subnets.

If you do not select this checkbox, Campus gets the list of devices associated with the selected subnets and acquires end hosts on all the VLANs in those devices.


You do not have to specify any details for the IP Phones option.

Step 4 Click Start Acquisition.


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

Modifying Acquisition Schedule

Specifying Purge Policy

Specifying Domain Name Display

Modifying Ping Sweep Options

Configuring Subnet Acquisition

Modifying Delete Interval

Importing Information on End Host Users

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Click Admin > Acquisition > Acquisition Settings.

The Acquisition Settings dialog box appears.

Step 3 Modify the acquisition settings as specified in Table 5-2.

Table 5-2 Acquisition Settings 

Field
Description
Usage Notes

Enable User Tracking for DHCP Environment

Enables User Tracking for DHCP Environment.

If you enable this option, when the end hosts are in DHCP environment, you can detect the IP address information of end hosts correctly.

The IP address of the end hosts change frequently, in this DHCP environment.

Use DNS to resolve host names

Resolves host names using DNS.

None.

Get User Names from UNIX hosts

Allows acquisition of active user names on the UNIX network.

UNIX user names are updated at the end of major acquisitions.

Collects information only for users who are currently logged into the network.

Get User Names from hosts in NT and NDS

Allows the acquisition of active user names on the Windows or Novell Directory Service (NDS) servers.

Windows and NDS user names are updated at the end of subsequent major acquisition.

This option helps you to:

Collect information only for users who are currently logged into the network.

Collect information from NDS hosts. You must use NDS 5.0 or later.

You must install UTLite script, since it is a prerequisite.

User Port Number

Specify the UDP port number from where logon and logoff messages are received from hosts in Windows and NDS.

You must use the default port number unless it is already in use. This port number must match the port indicated in the login script.

Log File Name

Name of the log file.

User Tracking major acquisition errors are logged in this file.


Step 4 Click Apply.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Click Admin > Acquisition > Schedule Acquisition.

The Acquisition Schedule dialog box appears.

Step 3 Modify the acquisition schedule as specified in Table 5-3.

Table 5-3 Acquisition Schedule

Field
Description
Usage Notes

Minor Acquisition

Specify the periodicity in minutes at which a minor acquisition should take place.

None.

Major Acquisition

Specify the days on which, the time at which a major acquisition is to take place.

You can also specify the days of the week on which a major acquisition is to be scheduled.

None.

Days, Hour, Min

Days on which and the time at which a major acquisition is to be carried out.

You can add new schedules and edit or delete existing schedules.

Recurrence Pattern

Select the days of the week on which a major acquisition is to be scheduled.

This field is available only when you are adding or editing a schedule.


Step 4 Select the schedule, and do any one of the following:

Click Edit to edit the schedule.

Click Delete to delete the schedule.

Click Add to add a new schedule.

Step 5 Click OK to save the changes or Cancel to cancel the changes.

Step 6 Click Apply after adding or editing a schedule.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Admin > Reports > Purge Policy.

The Report Settings dialog box appears.

Step 3 Specify the purge details for report archives and jobs.

Step 4 Click Save.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Admin > Reports > Domain Names.

The Report Settings dialog box appears.

Step 3 Choose the way in which domain names are to be displayed.

You can:

Display the full domain name suffix

Display part of the domain name suffix

Hide the specified domain name suffix

Enter the domain name suffix in the field, if you choose to hide the specified domain name suffix.

Step 4 Click Save.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Click Admin > Acquisition > Ping Sweep.

The Ping Sweep dialog box appears.

Step 3 Specify if you want to enable Ping Sweep.

Specify the Wait Interval, if Ping Sweep is enabled.

Step 4 Specify the subnets, if you want to exclude any subnet from Ping Sweep.

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 Click Apply.


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:

Configure a higher value for the ARP cache time-out on the routers. To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.

Use any external software, which will enable you to ping the host IP addresses. This will ensure that when you run User Tracking Acquisition the ARP cache of the router contains the IP addresses.

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Click Admin > Acquisition > Configure Subnet Acquisition.

The Configure Subnet Acquisition dialog box appears.

Step 3 Select either of the following options:

Perform acquisition on all subnets

All the subnets are included for User Tracking Major Acquisition. If you select this option do not perform steps 4 and 5.

Or

Perform subnet based acquisition

The action depends on the Filter value.

Step 4 Select either of the following Filter values:

Perform major acquisition on selected subnet(s)

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

Do not perform major acquisition on selected subnet(s)

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 Select subnets from the list of Available Subnets and add them to the list of Selected Subnets.

Step 6 Click Apply.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Admin > Acquisition > Delete Interval.

The Delete Interval dialog box appears.

Step 3 Specify delete intervals for end host and IP phone tables.

Step 4 Select the Delete After Every Major Acquisition check box, if required or click Delete now to delete the entries immediately.

Step 5 Click Apply.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Admin > End Host Table Import.

The End Host Table Import dialog box appears.

Step 3 Specify the name of the file from which you are importing the end host table data.

Step 4 Click Apply.


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

Viewing Report Jobs List

Viewing Job Details

Stopping Jobs

Deleting Jobs

Using Report Generator

Viewing Duplicates Report

Viewing End Hosts Reports

Viewing IP Phones Reports

Viewing Reports on Switch Port Usage

Using Custom Reports

Using Custom Layouts

Using Archived Reports

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports.

The Quick Report dialog box appears.

Step 3 Enter the required information as given in Table 5-4.

Table 5-4 Viewing Quick Reports 

Field
Description
Usage Notes

Select a type

Select the type of report that you wish to view.

The two types of reports that are available are:

End Hosts

IP Phones

QueryExpression

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 Click Submit.

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.

Table 5-5 Operators Available and their Values 

Operator
Pattern

Contains

Does not contain

Begins with

Does not begins with

Ends with

Does not end with

yyyy/mm/dd

yyyy/mm/dd hh:mm:ss

dd mmm yyyy, hh:mm:ss GMT

dd mmm yyyy hh:mm:ss GMT

dd mmm yyyy, hh:mm:ss

dd mmm yyyy hh:mm:ss

dd mmm yyyy

hh:mm:ss GMT

hh:mm:ss

Matches

Does not match

yyyy/mm/dd hh:mm:ss

dd mmm yyyy, hh:mm:ss GMT

dd mmm yyyy hh:mm:ss GMT

dd mmm yyyy, hh:mm:ss

dd mmm yyyy hh:mm:ss

Less than

Greater than

yyyy/mm/dd hh:mm:ss

dd mmm yyyy, hh:mm:ss GMT

dd mmm yyyy hh:mm:ss GMT

dd mmm yyyy, hh:mm:ss

dd mmm yyyy hh:mm:ss

dd mmm yyyy

Is between

Is not between

yyyy/mm/dd hh:mm:ss,yyyy/mm/dd hh:mm:ss

dd mmm yyyy, hh:mm:ss GMT,dd mmm yyyy, hh:mm:ss GMT

dd mmm yyyy hh:mm:ss GMT,dd mmm yyyy hh:mm:ss GMT

dd mmm yyyy, hh:mm:ss ,dd mmm yyyy, hh:mm:ss

dd mmm yyyy hh:mm:ss ,dd mmm yyyy hh:mm:ss

dd mmm yyyy ,dd mmm yyyy

Is in

Is not in

yyyy/mm/dd hh:mm:ss,yyyy/mm/dd hh:mm:ss

dd mmm yyyy, hh:mm:ss GMT,dd mmm yyyy, hh:mm:ss GMT

dd mmm yyyy, hh:mm:ss GMT,dd mmm yyyy, hh:mm:ss GMT

dd mmm yyyy, hh:mm:ss ,dd mmm yyyy, hh:mm:ss

dd mmm yyyy hh:mm:ss ,dd mmm yyyy hh:mm:ss


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Jobs.

The Report Jobs dialog box appears.

Table 5-6 Report Jobs Column Description 

Column
Description

Job ID

Unique ID of the job. Job IDs have N.x format, where x stands for the number of instances of that job.

For example, 1007.4 indicates that it is the fifth instance of the Job with ID 1007.

Job Type

Type of job. The jobs include:

Duplicate IP

Duplicate MAC

Duplicate MAC and VLAN

Ports with Multiple MAC

End Hosts - All Host entries

IP Phone - All IP Phone entries

Switch Port Usage - Recently Down

Switch Port Usage - Unused Up

Switch Port Usage - Unused Down

Description

Description of the job.

Owner

Username of the job creator.

Scheduled At

Date and time at which the job was scheduled.

Completed At

Date and time at which the job was completed.

Schedule Type

Type of job schedule—Daily or Periodic.

Status

Status of the job—Scheduled, Successful, Failed, Cancelled, Stopped, Running, Missed Start.



Viewing Job Details

To view the details of a selected job:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Jobs.

The Report Jobs dialog box appears.

Step 3 Check the check box against the job whose details you want to view.

Step 4 Click View.


Stopping Jobs

To stop a scheduled job:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Jobs.

The Report Jobs dialog box appears.

Step 3 Check the check box against the job that you want to stop.

Step 4 Click Stop.


Deleting Jobs

To delete a job:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Jobs.

The Report Jobs dialog box appears.

Step 3 Check the check box against the job that you want to delete.

Step 4 Click Delete.


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:

Select an Application
Select a Report

Duplicates

Duplicate IP, Duplicate MAC, Duplicate MAC and VLAN, and Ports with multiple MAC.

End Hosts

All Host Entries.

IP Phones

All IP Phone Entries

Switch Port Usage

Recently Down, Unused Down, Unused Up.


To use the report generator:


Step 1 Select Campus Manager > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Reports > Report Generator.

The Report Generator dialog box appears.

Step 3 Select the Application for which you want to view reports.

Step 4 Select the Report that you want to view.

Step 5 Schedule the report by selecting the report type and the date on which you want the report to be generated.

Step 6 Enter Job Description and E-mail address, if any.

Step 7 Set system preferences for receiving mail.

Step 8 Click Submit to generate the report.

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.

Duplicate IP addresses

Duplicate MAC addresses

Duplicate MAC and VLANs

Ports with multiple MAC addresses

To view reports on duplicates:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Generator.

The Report Generator dialog box appears.

Step 3 Select Duplicates from the Select Application list.

Step 4 Select the Report for the application that you want to view.

Step 5 Schedule the report by selecting the report type and the date on which you want the report to be generated.

Step 6 Enter Job Description and E-mail address, if any.

Step 7 Click Submit to generate the report.

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-7 Standard Layout for Duplicates Reports

Column
Description

UserName

Discovered username or the username that you have entered. You can edit this field.

You can configure the Campus Manager Server to collect user names.

MACAddress

Media Access Control (MAC) address of network interface card in end-user node.

For Ethernet topology the MAC address appears in the format, xx-xx-xx-xx-xx-xx.

For Token Ring topology the MAC address appears in the format, xx:xx:xx:xx:xx:xx.

HostName

Name of host.

IPAddress

IP address of host.

Subnet

Subnet of IP address, which appears in the format String xxx.xxx.xxx.xxx.

DeviceName

Name corresponding to IP address of device.

Port

Port in device to which a host is connected.

VLAN

VLAN name associated with port.

LastSeen

Date and time when User Tracking last found an entry for this user or host in a switch. Last Seen appears in the format dd mon yyyy hh:mm:ss.

Notes

Notes on this entry, that you enter.


Table 5-8 provides details of the columns in All Columns Layout.

Table 5-8 All Columns Layout for Duplicates Reports 

Field
Description

UserName

Discovered username or the username that you have entered. You can edit this field.

You can configure the Campus Manager Server to collect user names.

MACAddress

Media Access Control (MAC) address of network interface card in end-user node.

For Ethernet topology the MAC address appears in the format, xx-xx-xx-xx-xx-xx.

For Token Ring topology the MAC address appears in the format, xx:xx:xx:xx:xx:xx.

HostName

Name of host.

IPAddress

IP address of host.

Subnet

Subnet of IP address.

IPv6 Address

IPv6 address of the host, if any.

Prefix Length

Length of the IPv6 address prefix.

Prefix

IPv6 address prefix.

DeviceName

Name corresponding to IP address of device.

Device

IP address of device to which end user node is attached.

Port

Port/Interface in device to which a host is connected.

Port Name

User assigned port name (port label).

Port State

Configured port mode.

Port Duplex

Operational duplex.

Port Speed

Operational speed.

VLAN

VLAN name associated with port.

VLAN ID

VLAN identifier associated with the MAC address or port.

VLAN Type

Ethernet, Token Ring, FDDI, unassigned, or unknown.

Parent VLAN

Token Ring VLAN of the host.

Secondary VLAN

Secondary VLAN of the host.

Ring

Ringnumber for Token Ring VLANs.

Bridge

BRF bridge number.

LastSeen

Date and time when User Tracking last found an entry for this user or host in a switch. Last Seen appears in the format
dd mon yyyy hh:mm:ss.

Notes

Notes on this entry, that you enter.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Generator.

The Report Generator dialog box appears.

Step 3 Select End Hosts from the Select Application list.

Step 4 Select All Host Entries from the Select a Report list.

Step 5 Schedule the report by selecting the report type and the date on which you want the report to be generated.

Step 6 Enter a description in the Job Description field of the Job Information area.

Step 7 Enter a valid E-mail ID in the Email field, of the Job Information area, to receive the report through mail.

Step 8 Click Submit to generate the report.

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-9 End Hosts Report—Standard Layout Columns 

Column
Description

UserName

Discovered username or the username that you have entered. You can edit this field.

You can configure the Campus Manager Server to collect user names.

MACAddress

Media Access Control (MAC) address of network interface card in end-user node.

For Ethernet topology the MAC address appears in the format, xx-xx-xx-xx-xx-xx.

For Token Ring topology the MAC address appears in the format, xx:xx:xx:xx:xx:xx.

HostName

Name of host.

IPAddress

IP address of host.

Subnet

Subnet of IP address, which appears in the format String xxx.xxx.xxx.xxx.

DeviceName

Name corresponding to IP address of device.

Port

Port in device to which a host is connected.

VLAN

VLAN name associated with port.

LastSeen

Date and time when User Tracking last found an entry for this user or host in a switch. Last Seen appears in the format dd mon yyyy hh:mm:ss.

Notes

Notes on this entry, that you enter.


Table 5-10 provides details of the columns in End Hosts Report—All Columns Layout

Table 5-10 End Hosts Report—All Columns Layout 

Field
Description

UserName

Discovered username or the username that you have entered. You can edit this field.

You can configure the Campus Manager Server to collect user names.

MACAddress

Media Access Control (MAC) address of network interface card in end-user node.

For Ethernet topology the MAC address appears in the format, xx-xx-xx-xx-xx-xx.

For Token Ring topology the MAC address appears in the format, xx:xx:xx:xx:xx:xx.

HostName

Name of host.

IPAddress

IP address of host.

Subnet

Subnet of IP address.

IPv6 Address

IPv6 address of the host, if any.

Prefix Length

Length of the IPv6 address prefix.

Prefix

IPv6 address prefix

DeviceName

Name corresponding to IP address of device.

Device

IP address of device to which end user node is attached.

Port

Port name in device to which a host is connected.

Port Name

User assigned port name (port label).

Port State

Configured port mode.

Port Duplex

Operational duplex.

Port Speed

Operational speed.

VTP Domain

VTP Domain the port is associated with.

VLAN

VLAN name associated with port.

VLAN ID

VLAN identifier associated with the MAC address or port.

VLAN Type

Ethernet, Token Ring, FDDI, unassigned, or unknown.

Parent VLAN

Private VLAN of the host.

Secondary VLAN

Secondary VLAN of the host.

Ring

Ringnumber for Token Ring VLANs.

Bridge

BRF bridge number.

LastSeen

Date and time when User Tracking last found an entry for this user or host in a switch. Last Seen appears in the format
dd mon yyyy hh:mm:ss.

Notes

Notes on this entry, that you enter.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Generator.

The Report Generator dialog box appears.

Step 3 Select IP Phones from the Select Application list.

Step 4 Select the Report, from the Select Report list.

Step 5 Schedule the report by selecting the report type and the date on which you want the report to be generated.

Step 6 Enter Job Description and E-mail address, if any.

Step 7 Click Submit.

The report is generated.


Interpreting IP Phones Reports

Table 5-11 gives details of the columns in IP Phones Report—Standard Layout.

Table 5-11 IP Phones Report—Standard Layout Columns 

Field
Description

PhoneNumber

Phone number.

MACAddress

Media Access Control (MAC) address of network interface card on the phone.

For Ethernet topology the MAC address appears in the format, xx-xx-xx-xx-xx-xx.

For Token Ring topology the MAC address appears in the format, xx:xx:xx:xx:xx:xx.

IPAddress

IP address of phone.

CCM Address

Cisco CallManager IP address.

Status

Status of the phone, as known to Cisco Call Manager.

PhoneType

Type of the Phone. Example: SP30, SP30+, 12S, 12SP, 12SPplus, 30SPplus, 30VIP

PhoneDescr

Description of the phone.

DeviceName

Name corresponding to IP address of device.

Device

IP address of device to which IP phone is attached.

LastSeen

Date and time when User Tracking last found an entry. Last Seen appears in the format dd mon yyyy hh:mm:ss.


Table 5-12 gives details of the columns in the IP Phones Report—All Columns Layout.

Table 5-12 IP Phones Report—All Columns Layout 

Field
Description

PhoneNumber

Phone number.

MACAddress

Media Access Control (MAC) address of network interface card on the phone.

For Ethernet topology the MAC address appears in the format, xx-xx-xx-xx-xx-xx.

For Token Ring topology the MAC address appears in the format, xx:xx:xx:xx:xx:xx.

IPAddress

IP address of phone, which appears in the format String, xxx.xxx.xxx.xxx.

CCM Address

Cisco CallManager IP address.

Status

Status of the phone, as known to Cisco Call Manager

PhoneType

Can be SP30, SP30+, 12S, 12SP, 12SPplus, 30SPplus, 30VIP, SoftPhone, or unknown.

PhoneDescr

Description of the phone.

DeviceName

Name corresponding to IP address of device.

Device

IP address of device to which IP phone is attached in the format String, xxx.xxx.xxx.xxx.

Port

Port name in device to which IP Phone is connected

Port Name

User assigned Port Name(Port Label)

LastSeen

Date and time when User Tracking last found an entry. Last Seen appears in the format dd mon yyyy hh:mm:ss.


Understanding Switch Port Usage Reports

You can generate three types of reports using Campus Manager, based on the status of the switch ports.

Report on Unused Down Ports

Report on Unused Up Ports

Report on Recently Down 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.

Table 5-13 Device Attribute Description 

Attributes
Description

DiscoveryStatus

Status of the device after data collection has been completed.

Host name

Name of the device.

ImageVersion

Software version running on the device.

IPSubnet

Subnet address of the device's IP address.

IPSubnetMask

Subnet mask address of the device.

SingleIpAddress

Single IP Address—Not a range of addresses.

SysName

Name of the device as configured by the Administrator.

SysObjectID

SysObjectID of the device.

SystemContact

Contact for the device details as entered by the Administrator.

SystemLocation

Location of the device as entered by the Administrator.


Operator

The operator used in forming a rule. The following operators are available:

equals

contains

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:

Never_Reachable

Reachable

Currently_Unreachable

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Report Generator.

The Report Generator page appears.

Step 3 Select Switch Port Usage from the Select Application list.

Step 4 Select the Report, from the Select Report list.

The Device Selector appears.

Step 5 Select the device(s) for which you want to view the Switch Port usage.

Step 6 Schedule the report by selecting the report type and the date on which you want the report to be generated.

Step 7 Enter Job Description and E-mail address, if any.

Step 8 Click Submit.

The report is generated.


Interpreting Switch Port Usage Reports

Table 5-14 describes the columns of a Switch Port Usage report.

Table 5-14 Switch Port Usage Report 

Field
Description

Port

Port or interface of the device.

Port Name

User assigned port name (port label)

Operating Status

Operating status of the port

Admin Status

Admin status of the port


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

Creating Custom Reports

Editing Custom Reports

Copying Custom Reports

Deleting Custom Reports

Exporting Reports

Printing Reports

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Reports.

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Reports.

The Custom Reports dialog box appears with the list of Available Reports.

Step 3 Click Create.

You can use the Custom Reports wizard to customize and create reports. The Type selection page appears.

Step 4 Select the type of devices for which you need the report, from:

End Host—Contains all the devices managed by Campus Manager, including IP phones.

IP Phones—Contains only the IP phones managed by Campus Manager.

Step 5 Click Next.

The Group Selection page appears.

Step 6 Select the devices from the Group Selection box.

Step 7 Click Next.

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 

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

Simple

Advanced

Select the type of query.

Simple

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:

Column—Select a query expression based on which you want to generate the report.

Operator—Select a logical operator for the query expression.

Pattern—Enter a pattern for the selected query expression.

For a detailed list of operator values for the Last Seen column, see Table 5-5.

Advanced

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 Click Next.

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Reports.

The Custom Reports dialog box appears with the list of Available Reports.

Step 3 Select a report and click Edit.

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Reports.

The Custom Reports dialog box appears with the list of Available Reports.

Step 3 Select a report and click Copy.

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Reports.

The Custom Reports dialog box appears with the list of Available Reports.

Step 3 Select a report, and click Delete.


Exporting Reports

To export a report:


Step 1 Click the export icon on the right top of the screen.

The Exporting Report dialog box appears.

Step 2 Select the format in which the report is to be exported.

Step 3 Enter the range of rows or the row numbers that you want to export. Separate the rows and numbers by commas.

Step 4 Click OK.

The report is exported.


Printing Reports

To print a report:


Step 1 Click the print icon in the top right of the screen.

The Printing Report dialog box appears.

Step 2 Enter the number of rows that need to be printed.

Step 3 Click OK.

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

Creating Custom Layouts

Editing Custom Layouts

Copying Custom Layouts

Deleting Custom Layouts

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Layouts.

The Custom Layouts dialog box appears with the list of Available Layouts.



Note Standard layouts are available after a fresh install. You can edit the standard layouts. However, you cannot delete them.


Creating Custom Layouts

You can create Custom layouts by clicking Create in the Available Custom Layouts dialog box.

To create Custom layouts:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Layouts.

The Custom Layouts dialog box appears with the list of Available Layouts.

Step 3 Click Create.

Step 4 Select the type of report for which you want to create the layout.

Step 5 Select the columns that you want displayed in the report from the Available Sources list.

Step 6 Use the Up and Down arrow keys to arrange the columns in the order in which you want them displayed.

Step 7 Click Add to add the selected columns to the Selected Sources list.

Step 8 Specify the Name and Description of the customized layout.

Step 9 Click OK.


Editing Custom Layouts

You can edit Custom layouts by clicking Edit in the Available Custom Layouts dialog box.

To edit Custom reports:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Layouts.

The Custom Layouts dialog box appears with the list of Available Layouts.

Step 3 Click Edit.

Step 4 Select the columns that you want displayed in the report from the Available Sources list.

Step 5 Click Add to add the selected columns to the Selected Sources list.

Step 6 Select the columns that you want removed from the Selected Sources list.

Step 7 Click Remove to remove these fields from the customized layout.

Step 8 Specify the Description of the customized layout.

Step 9 Click OK.



Note Editing Standard Layout columns is seen only in Device Center and external applications. They are not seen in UT jobs.


Copying Custom Layouts

You can copy Custom layouts by clicking Copy in the Available Custom Layouts dialog box.

To copy Custom layouts:


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Layouts.

The Custom Layouts dialog box appears with the list of Available Layouts.

Step 3 Click Copy.

Step 4 Select the columns that you want displayed in the report from the Available Sources list.

Step 5 Click Add to add the selected columns to the Selected Sources list.

Step 6 Select the columns that you want removed from the Selected Sources list.

Step 7 Click Remove to remove these fields from the customized layout.

Step 8 Specify the Name and Description of the customized layout.

Step 9 Click OK.


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Custom Layouts.

The Custom Layouts dialog box appears with the list of Available Layouts.

Step 3 Select the layout that you want to delete and click Delete.


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

Viewing Reports

Deleting Archived Reports

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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Archives.

The Archives dialog box appears with the list of archived reports.


Viewing Reports

You can view a report using:

The Report Jobs option in the Reports tab of Campus User Tracking window (See Using the Report Jobs Option)

The Report Generator option in the Reports tab of Campus User Tracking window (See Using the Report Generator Option)

The Archives option in the Reports tab of Campus User Tracking window (See Using the Archives Option)

The Device Center feature of CiscoWorks and selecting a report pertaining to the device (See Using the Device Center)

Using the Report Jobs Option

This section explains how you can view reports of the scheduled jobs


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Reports Jobs.

The Report Jobs dialog box appears with the list of scheduled jobs.

Step 3 Select the job for which you want to view the report and click View.


Using the Report Generator Option

This section explains how you can generate a report using Report Generator.


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Report > Report Generator.

The Report Generator dialog box appears.

Step 3 Select the an application and a relevant report that you want to view

Step 4 Click Submit.

The report is generated.


Using the Archives Option

This section explains how you can view a report from the archives.


Step 1 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Report > Archives.

The Archives dialog box appears.

Step 3 Select the report that you want to view and click View.


Using the Device Center

This section explains how you can view reports for a specified device.


Step 1 From the CiscoWorks Homepage select Device Troubleshooting > Device Center. The Device Center window appears.

Step 2 In the Device Selector field either:

Enter the IP address or name of the device you want to select and click Go.

Or

Select a device from the device groups.

The Campus Manager reports available for the selected device appears under the Reports column in the Functions Available area.

Step 3 Click the report that you want to view


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 Select Campus Manager > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Reports > Archives.

The Archives dialog box appears with the list of archived reports.

Step 3 Select the report that you want to delete and click Delete.


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.

Use the -prompt command if you do not want to enter your password from the command line. Using -prompt prevents other users from running ps and seeing your password.

The host option is required if the User Tracking and the Campus Manager Server are running on different subnets.

All options are available in CLI mode. Only the -debug, -host, and -port options are available in both CLI and GUI modes.

Table 5-16 User Tracking CLI Commands 

Option
Arguments
Function

-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:

Configure a higher value for the ARP cache time-out on the routers.

To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.

Use any external software, which will enable you to ping the host IP addresses.

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 Place the exported files under the directory:

NMSROOT/campus/

where NMSROOT is the directory where you have installed CiscoWorks.

Step 2 Run the Command:

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 Support for importing data, from the User Interface (UI) exported file is not provided in this release.


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

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

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 Copy the required files to the Active Directory server:

a. Log into the Active Directory server as Administrator.

b. Obtain the UTLite files from the Server Configuration:

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. Copy the UTLiteNT.bat and UTLite33.exe files into the NETLOGON folder.

NETLOGON is located at:
%SystemRoot%\sysvol\sysvol\domain DNS name\scripts

where %SystemRoot% is usually c:\winnt and domain DNS name is the DNS name of the domain

Step 2 Edit the UTLiteNT.bat file:

Step 3 Open the UTLiteNT.bat file.

Step 4 Locate the following line and replace domain and ipaddress with the domain name of the Windows domain controller and IP address of the computer running the Campus Manager Server:

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 Edit the logon script files to run the UTLiteNT.bat file when users log into the network by adding this line:

UTLiteNT.bat

Step 6 Update the domain controller's logon script for each Windows domain that you add.

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 Copy the required files to the primary Windows domain controller:

a. Log into the Windows primary domain controller as Administrator.

b. Obtain the UTLite files from the Server Configuration:

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. Copy the UTLiteNT.bat and UTLite33.exe files into the NETLOGON folder.

NETLOGON is located at
%SYSTEMROOT%\system32\Repl\Import\Scripts,

where, SYSTEMROOT% is the root directory for the Windows operating system files.

Step 2 Edit UTLiteNT.bat file.

a. Open the UTLiteNT.bat file.

b. Locate the following line and replace domain and ipaddress with the domain name of the Windows domain controller and IP address of the computer running the Campus Manager Server:

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 Edit the logon scripts. Edit users' logon script files to run the UTLiteNT.bat file when users log into the network by adding this line:

UTLiteNT.bat

Step 4 Update the domain controller's logon script for each Windows domain that you add.

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 Copy the required files to the Novell Server.

Step 2 Log into the Novell Server as Administrator.

Step 3 Obtain the UTLite files from the CiscoWorks Server:

C:\Program Files\CSCOpx\campus\bin\UTLite33.exe

C:\Program Files\CSCOpx\campus\bin\UTLiteNDS.bat

where C:\Program Files\ is the directory in which you installed CiscoWorks.

Step 4 Create a folder in \\Novell Server Name\SYS\public and copy UTLiteNDS.bat and UTlite33.exe to the folder.

Step 5 Edit the UTLiteNDS.bat file:

Step 6 Open the UTLiteNDS.bat file.

Step 7 Locate the following line and replace domain and ipaddress with the domain name of the Windows domain controller and IP address of the computer running the Campus Manager server:

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 Edit the logon scripts.

Step 9 Enter \\Novell_Server_Name\SYS\public\NaL.exe at the command prompt.

Step 10 Click NWAdmin32 to run the Novell Netware Administrator program.

Step 11 Right-click on the users or organizational units whose logon scripts you want to modify and select Details.

Step 12 Click Login Script and enter:

@\\%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 Remove UTLiteNT.bat and UTLite33.exe files from each primary domain controller.

Step 2 Remove the call to run UTliteNT.bat from users' logon scripts.

Step 3 Delete UTLite33.exe from the WINDIR directory of all Windows clients.

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 Remove UTLiteNT.bat and UTLite33.exe files from each Active Directory server.

Step 2 Remove the call to run UTliteNT.bat from users' logon scripts.

Step 3 Delete UTLite33.exe from the WINDIR directory of all Windows clients.

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 Remove UTLiteNDS.bat and UTLite33.exe files from the Novell Server.

Step 2 Remove the line added to the login scripts for all users and organizational units.

Step 3 Delete UTLite33.exe from the WINDIR directory of all clients.

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

Hardware and Software Requirements for UTU 1.1.1

Downloading UTU 1.1.1

Installing UTU 1.1.1

Accessing UTU 1.1.1

Configuring UTU 1.1.1

Searching for Users or Hosts

Uninstalling UTU 1.1.1

Upgrading to UTU 1.1.1

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:

Support for silent installation mode for easy deployment.

Support for communication with Campus Manager server in
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.

Table 5-17 Definitions 

Term
Definition
Host

Any UNIX or Windows system discovered by User Tracking.

Host Name

Name of the discovered host.

Campus Manager Server

Host name or IP address of CiscoWorks server on which you have installed Campus Manager.

Port

Port number to which the host is connected.

Port number on which Campus Manager is running on the CiscoWorks server.

Subnet

Subnet to which the host belongs.

User Name

Name of the user who has logged into the host.


Hardware and Software Requirements for UTU 1.1.1

Table 5-18 lists the minimum system requirements for UTU.

Table 5-18 System Requirements 

Requirement Type
Minimum Requirements

System Hardware

IBM PC-compatible computer with Intel Pentium processor.

System software

Windows 2000 (Professional or Server) with Service Pack 4 or higher.

Memory (RAM)

128 MB

Additional required software

Campus Manager 4.0.3

Network Connectivity

Campus Manager 4.0 must be in operation, and accessible through the network.


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

Installing UTU 1.1.1

Accessing UTU 1.1.1

Configuring UTU 1.1.1

Searching for Users or Hosts

Uninstalling UTU 1.1.1

Downloading UTU 1.1.1

UTU requires CiscoWorksUserTrackingUtility1.1.1.exe file to be downloaded and installed.


Step 1 Locate the file CiscoWorksUserTrackingUtility1.1.1.exe at:

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus-crypto

Step 2 Save the file to a temporary directory on your system.


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 Log into the system with local system administrator privileges.

Step 2 Navigate to the directory that contains CiscoWorksUserTrackingUtility1.1.1.exe.

Step 3 Double-click CiscoWorksUserTrackingUtility1.1.1.exe to begin installation.

The User Tracking Utility Welcome screen appears.

Step 4 Click Next.

The Choose Destination Location dialog box appears. By default, UTU is installed in the directory C:\Program Files\CSCOutu.

Step 5 Click Next to install UTU in the default directory.

Or

a. Click Browse to choose a different directory and click OK.

b. Click Next to continue with the installation.

The Configure CiscoWorks Campus Manager Server Details dialog box appears.

Step 6 Enter the name or IP address of the server on which Campus Manager is installed.

Step 7 Enter the port number of the Campus Manager server. The default port number is 1741.

Step 8 Click Next.

The following message appears:

Is CiscoWorks LMS Server SSL Enabled?

Step 9 Click Yes if the Campus Manager server is SSL enabled, otherwise, click No.

The Configure LMS Server Authentication dialog box appears. You can also configure these server details after installation.

Step 10 Enter a valid CiscoWorks Campus Manager Server user name and password.

This is used to verify the validity of the user when searching for users or hosts.

Step 11 Confirm the password and click Next.

The Setup Complete dialog box appears.

Step 12 Click Finish to complete the installation.

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

exe-location is the directory where you have CiscoWorksUserTrackingUtility1.1.1.exe

file-location is the directory where you have the setup.iss file.

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= hostname
szEdit2= server-port
Result=1
[AskYesNo-0]
Result=1           <1- SSL Enabled, 0 - SSL Disabled>
[SdShowDlgEdit3-0]
szEdit1=username
szEdit2=password
szEdit3=password

You 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 Right-click the taskbar of the machine on which you installed UTU.

Step 2 Select Toolbars > User Search Band, as shown in Figure 5-1.

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 Right-click the User Information search area on the taskbar of the machine on which you installed UTU.

A popup menu appears.

Step 2 Select Configure.

The Campus Manager Server Configuration dialog box appears.

Step 3 Modify the settings as required.

Step 4 Click Enable SSL for communicating with an SSL enabled server.

The port number changes to 443, which is the default port for SSL. See Figure 5-2.

Figure 5-2 Enabling SSL

Step 5 Click OK to configure or Cancel to quit.


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 Enter host name or IP address in the User Information field on the taskbar of the machine.

The default search criterion is host name or IP address of the host. To customize this search criterion:

a. Right-click the Users Information search area.

A popup menu appears with the default search criterion Host/IP selected.

b. Select User, Host/IP, or MAC Address from this popup menu.

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 

Search Criterion
Description

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 Enter any value related to user name, host name, IP address, or the MAC address in the User Information field.

For example, you can enter 10.77.208* in the User Information field.

Step 3 Press Enter.

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 Click Details to view the certificate details.

You can verify the authenticity and correctness of the SSL server here. See Figure 5-4.

Figure 5-4 Certificate Details

Step 5 Click Yes in the Certificate Viewer dialog box to accept and store the certificate.

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 Select an entry in the Select Entry popup box.

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 Select Copy All to Clipboard in the Select Entry popup to copy the complete search result.

Another popup box appears with the details for that particular entry, as described in Table 5-20.

Table 5-20 Details for Each Entry in Select Entry Box 

Entry
Description

User Name

User name of the user logged in to the host.

Host Name

Name of the host discovered by User Tracking.

MAC Address

MAC address of the host.

IP Address

IP address of the host.

Subnet

Subnet to which the host belongs.

Switch

Device name or IP address of the switch.

Port

Port number to which the host is connected.

Port State

State of the port: Static or Dynamic.

VLAN

VLAN to which the port of the switch belongs.

Port Speed

Bandwidth of the port of the switch.

Port Duplex

Port Duplex configuration details on the device.

Last Seen

Last time User Tracking discovered this host.

Copy to Clipboard

Copies the entries and the details to clipboard.


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,

Cisco it displays users or hosts, where the user name or host name matches Cisco.

Cisco* it displays users or hosts that begin with the word Cisco.

10.77.208* it displays host IP addresses that begin with 10.77.208.

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 From the Windows taskbar, select Start > Settings > Control Panel > Add/Remove Programs.

The Add/Remove Programs dialog box appears.

Step 2 Select CiscoWorks User Tracking Utility.

Step 3 Click Change/Remove.

The system prompts you to confirm uninstallation.

Step 4 Click Yes.

The Remove Programs From Your Computer dialog box appears.

Step 5 Either:

a. Click Yes

The shared DLL, and UTBand.dll files, are removed.

b. Click OK.

Or

a. Click No.

The uninstallation proceeds, but it does not completely uninstall UTU. To complete the uninstallation process, you must:

b. Go to the command prompt and access the directory where you have installed UTU.

The default directory is C:\Program Files\CSCOutu.

Step 6 Enter regsvr32 /u UTBand.dll

The following message appears:

DLLUnregisterServer in UTBand.dll failed

Step 7 Click OK.

Step 8 Enter del UTBand.dll

This removes the UTU installation completely from the machine.

Step 9 Restart your system.


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/No

Click 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

Using Debugger Utility

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. Checks the switch ports in a sequential order.

2. Reports violation of basic rules for each of the missing ports such as, link ports and trunk ports.

3. Checks for SNMP retrieval of data, if the ports pass the validity check.

4. Generates an Action Report suggesting possible remedial actions to retrieve the valid missing ports.

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/12
utdebug -switch 10.29.100.10 -port Fa0/10
utdebug -switch 10.29.6.14 -port Gi6

Troubleshooting User Tracking

Use the information in Table 5-21 to troubleshoot the User Tracking application.

Table 5-21 Troubleshooting User Tracking 

Symptom
Probable Cause
Possible Solution

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. Check the CiscoWorks topology for the missing devices

2. Ensure that CDP and SNMP are enabled on the devices, rediscover these devices,

3. Verify that they appear on the topology view.

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. Check the CiscoWorks topology for the missing MCS that runs the instance of Cisco CallManager to which the phones are registered.

2. Ensure that Cisco CallManager is shown as a service running on the MCS shown in the topology view if it is discovered by the Campus Manager Server.

3. Rediscover all IP phones.

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:

Configure a higher value for the ARP cache time-out on the routers.

To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.

Or

Use any external software, which will enable you to ping the host IP addresses.

This will ensure that when you run User Tracking Acquisition the ARP cache of the router contains the IP addresses.

You have:

Made changes to the network

Run User Tracking discover.

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. Run device discovery.

2. Try running a complete Data collection.

3. Generate a new report after data collection is complete to see the changes.


User Tracking FAQs

Use the information in these sections to answer some of your common questions:

Why are outdated entries showing up in my User Tracking table?

Why doesn't the IP phone display act like the User Tracking table?

How does User Tracking acquisition process differ from that of the Campus Manager Server?

How does User Tracking user and host acquisition process work?

Why is User Tracking not performing Ping Sweeps on some subnets?

How long does User Tracking maintain data?

Does User Tracking discover users and hosts connected to non-Cisco Discovery Protocol (CDP) discovered or managed devices?

How does User Tracking log errors?

Q. Why are outdated entries showing up in my User Tracking table?

A. Outdated entries result when:

A user or host is assigned to 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:

Manually delete selected entries.

Or

Schedule User Tracking to remove old entries.

Q. Why doesn't the IP phone display act like the User Tracking table?

A. The IP phone table and the main User Tracking table display different kinds of information. See the User Tracking table and the User Tracking table for IP Phone data to see what kinds of information each table displays.

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. How does User Tracking acquisition process differ from that of the Campus Manager Server?

A. User Tracking is a Campus Manager client application. The 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 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. How does User Tracking user and host acquisition process work?

A. Before collecting user and host information, Campus Manager must complete a global discovery. During global discovery, the Campus Manager generates a device list to determine which switches and routers it should look at to obtain MAC and IP addresses.

With these device lists in place, the User Tracking service performs steps described in Table 5-22.

Table 5-22 User Tracking User and Host Acquisition Process 

Process
Description

Performs Ping Sweeps

Pings all IP addresses on all known subnets, if you have Ping Sweeps enabled (the default).

This process updates the switch and router tables before User Tracking reads those tables. This ensures that User Tracking displays the most recent information about users and hosts.

Obtains MAC addresses from switches

Reads the switch's bridge forwarding table.

The bridge forwarding table provides the MAC addresses of end stations, and maps these MAC addresses to the switch port on which each workstation resides.

Obtains IP and MAC addresses from routers

Reads the Address Resolution Protocol (ARP) table in routers to obtain the IP and corresponding MAC addresses.

Obtains hostnames

Performs a Domain Name Service (DNS) lookup to obtain the hostname for every IP address.

Obtains usernames

Attempts to locate the users currently logged in to the hosts and tries to obtain their username or login ID.

Records discovered information

Records the discovered information in the Campus Manager database.


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 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. How long does User Tracking maintain data?

A. Indefinitely, until you delete the information.

Q. Does User Tracking discover users and hosts connected to non-Cisco Discovery Protocol (CDP) discovered or managed devices?

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 the 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.