User Guide for Campus Manager 5.0 (With LMS 3.0)
Chapter 7 Tracking Users
Downloads: This chapterpdf (PDF - 1.2MB) The complete bookPDF (PDF - 15.34MB) | Feedback

Tracking Users

Table Of Contents

Tracking Users

Understanding User Tracking

Understanding Network and Campus Manager Dependencies

Using User Tracking Administration

Viewing Acquisition Information

Interpreting Acquisition Information

Configuring User Tracking Acquisition Actions

Using User and Host Acquisition

Modifying Acquisition Settings

Modifying Acquisition Schedule

Modifying Ping Sweep Options

Configuring Subnet Acquisition

Modifying Delete Interval

Configuring Trunk for End Host Discovery

Specifying Purge Policy

Specifying Domain Name Display

Importing Information on End Host Users

Understanding Dynamic Updates

Viewing Dynamic Updates Process Status

Enabling SNMP Traps on Switch Ports

SNMP MAC Notification Listener

Configuring SNMP Trap Listener

HPOV as Primary Listener

DFM as Primary Listener

Debugging Options

Debugging Options for User Tracking Server

Debugging Dynamic Updates

Debugging Options for User Tracking Reports

Dynamic User Tracking Console

Understanding User Tracking Reports

Using User Tracking Reports

Viewing Quick Reports

Operator Values and Date Formats for Last Seen Column

Exporting and Printing Reports

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

Interpreting Switch Port Utilization Report

Interpreting Switch Port Usage Reports

Interpreting Summary Report for Switch Ports

Understanding History Report

Viewing History Reports for Switch Port Utilization

Interpreting History Reports for Switch Ports

History Reports Based on Filters

Interpreting End Host History Reports

Using Custom Reports

Viewing List of Custom Reports

Creating Custom Reports

Editing Custom Reports

Copying Custom Reports

Deleting Custom 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

Integrating CiscoWorks WLSE

Viewing Reports on Wireless Clients

Interpreting Reports on Wireless Clients

User Tracking Command Line Interface

Exporting Switch Port Usage Report

Importing User Tracking Data

Using Lookup Analyzer Utility

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

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

Using Search Patterns

Uninstalling UTU 1.1.1

Upgrading to UTU 1.1.1

Re-installing UTU

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

Using User Tracking Administration

Understanding Dynamic Updates 

Debugging Options

Understanding User Tracking Reports

Using User Tracking Reports

Integrating CiscoWorks WLSE

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. In this way, you get the information required to troubleshoot as well as to analyze any connectivity issues. The application identifies all end users connected to the discovered Cisco access layer switches on the network, including printers, servers, IP phones PCs and wireless hosts.

User Tracking collects the details of the end users and the layer 2 connections, and updates User Tracking table in the Campus Manager database. This is done through automated polling of the network, by User Tracking (UT) Major Acquisition process.

In addition to polling the network, Dynamic UT process receives details from the end users and update the database dynamically. User Tracking also computes subnet related data and updates the database with complete host information. Thus you get latest information about the changes in connections on your network.

You can also configure User Tracking to collect usernames of the end hosts connected in the network. The user names are collected from the UTLite process installed in UNIX hosts, Primary Domain Controller (PDC), or Novell Directory Services (NDS). This makes it easier for you to locate and track specific users on your network.

You can sort and query the User Tracking table that contains details like VLANs, switches and switch ports 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 accurately locate the end users.

Switch Port reports give you information on:

Recently down ports

Ports which are in unused condition for the specified interval

Connected ports and Free ports

Percentage utilization of ports per device

These reports give a clear picture of the switch port utilization in the network and help you in doing capacity planning for the network. For complete details on switch port reports, see Understanding Switch Port Usage Reports.

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 configure User Tracking Acquisition settings to collect usernames during UT Major Acquisition and update UT table. The user names are collected from the UTLite process.

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 also view History Reports for Switch port utilization, and the connection and disconnection of endhosts and users from your network.

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.

Accessing UT Data

The following are the ways to access User Tracking data:

Quick Reports

You can generate End hosts or IP Phones report based on the given filter criteria

For example, you can generate reports on end hosts which belong to a specific VLAN.

For more details, see Viewing Quick Reports

Scheduled Reports

You can schedule reports that run at the specified date and time. You can generate immediate reports or schedule them to run once or at repititive intervals.

For more details, see Using Report Generator

Custom Reports

You can customize the layout and columns displayed in the reports to suit your needs.

For more details, see Using Custom Reports

Command Line Interface

You can generate various User Tracking reports from the Command Line Interface also.

For more details, see User Tracking Command Line Interface

Data Extraction Engine

Data Extraction Engine is a Campus Manager UTility that allows you to generate User Tracking data in XML format.

For more details, see Overview of Data Extraction Engine, page 15-1

Object Finder

You can search for Device details, the Job details, the End host details using the Object Finder

For more details, see the User Guide for LMS Portal 1.0.

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.

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.

For more details, see User Tracking Utility

Various Acquisitions in User Tracking

This section explains 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 Campus Manager.

For details on the various options that can be set before starting an acquisition, see Modifying Acquisition Settings.

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. For more details, see User Tracking Command Line Interface.

User Tracking Minor Acquisition

Minor acquisition occurs on a device if any of the following changes take place:

A new endhost or IP phone is added to the network.

Port state changes (when the port 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 subnet based acquisition would run only on those subnets that are configured in Campus Manager. Campus Manager discovers end hosts on all the VLANs available in the configured subnets.

Do subnet based acquisition, when you need details about the end hosts connected to a particular subnet or a select set of subnets. The acquisition completes faster, since it is not run on all devices managed by Campus Manager.

For details on running subnet based acquisition, see Configuring Subnet Acquisition

Single device on-demand User Tracking Acquisition

This discovers the end hosts on all the VLANs available in the selected device. Hence this acquisition is useful for collecting information only on end hosts connected to the specified device.

For details on initiating this type of acquisition, see Configuring User Tracking Acquisition Actions

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:


Step 1 Set up your network devices so that they can be discovered.

This includes enabling Cisco Discovery Protocol (CDP), Integrated Local Management Interface (ILMI) and SNMP.

Step 2 Run Device Discovery.

For more details on Device Discovery, see Viewing Summary of Device Discovery Settings, page 5-9.

Step 3 Run Data Collection.

For more details on Data Collection, see Viewing Summary of Data Collection Settings, page 5-17.


Using User Tracking Administration

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

Modify Acquisition settings.

Before you start collecting information about the hosts in your network, you can set various options that control the way in which Acquisition happens.

For example, you can set Campus Manager to perform DNS lookup, while resolving the IP address of a host.

For complete details, see Modifying Acquisition Settings

Schedule Acquisition.

You can set the day and time of the week when you want to run Major Acquisition. The time interval at which Minor Acquisition happens in the network can also be set.

For more details, see Modifying Acquisition Schedule

Configure Ping Sweep options for Acquisition.

You can configure Campus Manager to perform Ping Sweep on selected subnets, during Acquisition.

For more details, see Modifying Ping Sweep Options

Configure Subnet Acquisition.

You can trigger acquisition on a single subnet or a select set of subnets. Subnet based acquisition collects details about the end hosts that are connected to a particular subnet or a select set of subnets. This Acquisition completes faster, since it is not run on all devices managed by Campus Manager.

For more details, see Configuring Subnet Acquisition

Configure end host and IP phone data delete interval.

You can modify the time interval for deleting entries from the End Host Table, IP Phone Table, or the History Table from the database.

For more details, see Modifying Delete Interval

Configure UT Acquisition to discover end hosts connected to non-link trunk ports.

Normally UT Acquisition only discovers end hosts that are connected to access ports. If you enable this feature, UT Acquisition also discovers end hosts that are connected to non-link trunk ports.

For more details, see Configuring Trunk for End Host Discovery

Specify Purge Policy.

You can specify the intervals when you want old reports and jobs to be purged. You can save the Purge Policy, so that the older jobs and archives are purged at the specified interval.

For more details, see Specifying Purge Policy

Specify Domain Name display.

You can specify the way in which domain names are to be displayed in User Tracking Reports.

For more details, see Specifying Domain Name Display

Import information on end hosts.

You can import user names and notes for end hosts that are already discovered by User Tracking, from a file.

For more details, see Importing Information on End Host Users

Enable Dynamic User Tracking.

Dynamic Updates are asynchronous updates that are based on SNMP MAC notifications traps. Campus Manager tracks changes about the end hosts and users on the network to provide real-time updates, based on these traps.

For more details, see Understanding Dynamic Updates

Enable Debugging options.

When you face issues in running User Tracking, logging can be enabled for debugging purposes.

For more details, see Debugging Options

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.


Interpreting Acquisition Information

Acquisition Information window displays the fields described in Table 7-1.

Table 7-1 Acquisition Information Field Description 

Field
Description

Acquisition status

Status of the User Tracking Major Acquisition process. It can be either Idle or Running.

Last acquisition type

Type of User Tracking acquisition that you had performed last time. Types of acquisition are:

Major—User Tracking Major Acquisition

Devices—User Tracking Acquisition for a device

Subnets—User Tracking Acquisition for subnets

IP Phones—User Tracking Acquisition for IP phones

Acquisition start time

Date and time when User Tracking started the Acquisition process. This is displayed in the format dd mon yyyy hh:mm:ss.

Acquisition end time

Date and time when User Tracking stopped the Acquisition process. This is displayed in the format dd mon yyyy, hh:mm:ss time zone.

Number of major acquisitions

Number of major acquisitions that has been performed.

Number of host entries

Number of hosts found after User Tracking acquisition.

Number of duplicate MAC

Number of MAC addresses that have duplicate entries in the list of hosts found.

Number of duplicate IP

Number of IP addresses that have duplicate entries in the list of end hosts found.

Number of CCM hosts

Number of Cisco CallManagers in the list of devices found after Data Collection.

Number of IP phone entries

Number of IP phones available in the Campus Manager managed network.

Last Campus data collection completed at

Date and time of the previous Campus Manager Data Collection process. This is displayed in the following format: dd mon yyyy hh:mm:ss time zone.

Campus data collection status

Status of the Campus Manager Data Collection process. It can be either Idle or Running.


Configuring User Tracking Acquisition Actions

You can trigger the following acquisitions from this page:

Device based Acquisition

Subnet based Acquisition

IP Phone Acquisition

To configure the required acquisition:


Step 1 Select Campus Manager > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Acquisition >Actions.

The Acquisition Actions dialog box appears.

Step 3 Configure Acquisition Actions as specified in Table 7-2.

Table 7-2 Acquisition Actions 

Field
Description
Usage Notes

Select a type

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

Device

Subnet

IP Phones

When you select a type of acquisition the appropriate fields are displayed.

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 for which you require data.

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

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

Subnet Mask

Enter the subnet mask.

If you select the subnet ID, the subnet mask is automatically entered.

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 check box, only the work stations associated to the VLANs that are mapped to the selected subnets will be acquired.

If you do not select this check box, work stations associated to all the available VLANs in the selected subnets will be acquired.


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 Administration 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 Administration tab in Campus User Tracking window.

This section contains:

Modifying Acquisition Settings from UI

UT Behaviour in DHCP Environment for Missing IP address

Configuring Properties That Support Duplicate MAC Address

Configuring User Tracking Properties from the Backend

Modifying Acquisition Settings from UI

To modify acquisition settings:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Acquisition > Acquisition Settings.

The Acquisition Settings dialog box appears.

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

Table 7-3 Acquisition Settings Field Description 

Field
Description
Usage Notes

Enable User Tracking for DHCP Environment

Enables User Tracking for DHCP Environment.

If you enable this property, it allows you to control inclusion and exclusion of Duplicate MAC addresses in the Acquisition.

To understand the behavior of User Tracking in case of missing IP address, see UT Behaviour in DHCP Environment for Missing IP address.

For details on properties that support Duplicate MAC address, see Configuring Properties That Support Duplicate MAC Address.

Get user names from UNIX hosts

Select this option to allow Acquisition to collect the active usernames of UNIX hosts.

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

Collects information only for users, who are logged into the console port of the UNIX hosts.

Get user names from hosts in NT and NDS

Allows Campus Manager to collect active user names on the Windows or Novell Directory Service (NDS) servers.

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.

Use DNS to resolve host names

Resolves host names using DNS.

User Tracking performs DNS Lookup for a host to resolve its IP address.

When you choose this option the Advanced button is enabled. Click on this to launch the Advanced UT Acquisition Settings window.

The following options are available:

DNS threads

Number of parallel threads allowed for name resolution. The default value is 1. Maximum number of threads allowed is 12.

DNS Timeout

Time duration for which UT waits for response from the DNS server, for name resolution. The value should be entered in milli seconds. The default value is 2000 milliseconds (2 seconds).

Enter values and click OK to save changes.

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.


Step 4 Click Apply to save the modifications in the settings.

Step 5 Click Start Acquisition to start User Tracking Acquisition with the modified settings.


UT Behaviour in DHCP Environment for Missing IP address

Enabling Enable User Tracking for DHCP Environment property allows you to control inclusion and exclusion of Duplicate MAC addresses in UT Acquisition.

Campus Manager will not get the IP address of end hosts, if the Router is not reachable or excluded from Campus Manager Device Discovery process. In such cases, behaviour of User Tracking after enabling Enable User Tracking for DHCP Environment property, is as explained in Table 7-4.

The conventions used in Table 7-4 are:

MACx — MAC address of the endhost

IPx — IP address of the endhost

Device x — Device to which the end host is connected.

Time in xx:xx format — Time entries in the Last seen column

NA — Not Available.


Note The explanation given for scenarios 1 and 2 hold good, irrespective of the value set for Enable User Tracking for DHCP Environment property.


Table 7-4 UT Behaviour in DHCP Environment for Missing IP address

Scenario
Explanation
What gets updated in Database

Scenario1: Missing IP Address

         

MAC1

NA

Device 1

6:35

For an endhost, if the IP address is not available in the first UT acquisition, but is available in the next, the IP address field in the database is updated with the value that is currently discovered.

MAC1

IP1

Device 1

6:40

MAC1

IP1

Device 1

6:40

       

Scenario 2: Missing IP Address

         

MAC1

IP1

Device 1

6:45

For an endhost, if the IP address is available in the first UT acquisition, but is not available in the next, the older value for IP address is retained in the database.

MAC1

IP1

Device 1

6:50

MAC1

NA

Device 1

6:50

       

Scenario 3: Single MAC, Multiple IP Addresses

         

MAC1

IP1

Device 1

6:55

For an endhost with Single MAC address but multiple IP addresses, if UT does not get the IP address in the current acquisition, it retains the older values in the database.

MAC1

IP1

Device 1

7:00

MAC1

IP2

Device 1

6:55

MAC1

IP2

Device 1

7:00

MAC1

IP3

Device 1

6:55

MAC1

IP3

Device 1

7:00

MAC1

NA

Device 1

7:00

       

Scenario 4: Dynamic change in IP Address

         

MAC1

IP1

Device 1

4:00

For an endhost with different IP addresses at different points of time, if UT does not get the IP address in the current acquisition, it retains the value that was last discovered.

MAC1

IP1

Device 1

4:00

MAC1

IP2

Device 1

5:00

MAC1

IP2

Device 1

5:00

MAC1

IP3

Device 1

6:00

MAC1

IP3

Device 1

7:00

MAC1

NA

Device 1

7:00

       

Scenario 5: Endhost moving between devices

         

MAC1

IP1

Device 1

4:00

When an end host moves between devices, if UT does not find the IP address in the current acquisition, it retains the IP address value that was last discovered for that device.

MAC1

IP1

Device 1

6:00

MAC1

IP1

Device 2

5:00

       

MAC 1

NA

Device 1

6:00

       

Configuring Properties That Support Duplicate MAC Address

The following properties can be configured in the ut.properties file stored in

NMSROOT/campus/etc/cwsi/

where NMSROOT is the root directory where you installed CiscoWorks.

Table 7-5 lists the properties that support Duplicate MAC Address

Table 7-5 Properties Supporting Duplicate MAC Address

Property
Description

UT.DuplicateMac.Include_SwitchPorts

List of switchports connected to endhosts, for which duplicate MAC entries need to be included in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Exclude_SwitchPorts

List of switchports connected to endhosts, for which duplicate MAC entries need to be excluded in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Include_Switches

List of switches connected to end hosts, for which duplicate MAC entries need to be included in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Exclude_Switches

List of switches connected to end hosts, for which duplicate MAC entries need to be excluded in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Include_Vlans

List of VLANs associated with endhosts, for which duplicate MAC entries need to be included in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Exclude_Vlans

List of VLANs associated with endhosts, for which duplicate MAC entries need to be excluded in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Include_Subnets

List of subnets associated with endhosts, for which duplicate MAC entries need to be included in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.

UT.DuplicateMac.Exclude_Subnets

List of subnets associated with endhosts, for which duplicate MAC entries need to be excluded in UT Major, UT Minor, UT device based, and UT subnet based Acquisition.


For the above list of properties:

Values should be separated by commas.

IP addresses of the devices should be given.

Port numbers should be given along with the device's IP address as deviceip:port.

The Exclude list takes precedence over the Include list.

The usage scenario for the above lists is as follows:

If you use the Include list OR the Exclude list alone, the duplicate MAC addresses will be included or excluded as specified.

For example, if you set the Include list as,

UT.DuplicateMac.Include_Switches=X,Y

Duplicate MAC addresses will be allowed only for endhosts connected to Switches X and Y. Duplicate addresses will not be allowed for any other endhost.

If you set both Include and Exclude list as,

UT.DuplicateMac.Include_Switches=X,Y

UT.DuplicateMac.Exclude_Switches=A,B

Duplicate MAC addresses will not be allowed for endhosts connected only to Switches A and B. Duplicate addresses will be allowed for all other end hosts, even for those connected to switches not specified in the Include list. Thus when an Exclude list is set, the Include list is ignored.

The above examples hold good for the Include/Exclude lists of Switchports, Subnets and VLANs.

The order of priority for the property list is as follows:

a. SwitchPorts

b. Switches

c. VLANs

d. Subnets

The SwitchPorts list has the highest priority, followed by Switches, VLANs and Subnets list.

For example, if you set

UT.DuplicateMac.Include_SwitchPorts=10.77.211.33:3/2

UT.DuplicateMac.Exclude_Switches=10.77.211.33

Although the switch 10.77.211.33 is in the Exclude list, a switchport belonging to that switch is also present in the Include list. So Duplicate MAC addresses will be allowed for that port on the switch. Thus the SwitchPorts list has higher priority over the Switches list.

Configuring User Tracking Properties from the Backend

This section explains the new user configurable properties that have been added to UT.

You can configure properties that control DNS name resolution and history reports, by editing them in the file ut.properties, stored in

NMSROOT/campus/etc/cwsi/

where NMSROOT is the root directory where you installed CiscoWorks.

Table 7-6 lists the new properties added to UT:

Table 7-6 Configuring User Tracking Properties

Property
Default value
Description

HistoryHostPurgeTime

10 days

Purges history entries which are older than the specified time. The value should be provided in minutes.

For example,

If you want to purge entries older than 10 days, set

HistoryHostPurgeTime=14400

UT.nameResolution

both

Name resolution for end hosts using Java APIs JNDI and InetAddres.This property can have the following values:

wins (Use only InetAddress)

dns(Use only JNDI)

wins,dns(First InetAddress then JNDI)

both (JNDI first and InetAddress next)

UT.nameResolution.dnsTimeout

2000

Time duration for which UT waits for response from the DNS server , for name resolution. The value should be entered in milliseconds.

UT.nameResolution.winsTimeout

2000

Time duration for which UT waits for response from the DNS server , for name resolution.The value should be entered in milliseconds.

This property must be enabled only for windows server.

UTMajorUseDNSCache

false

Uses cache memory for name resolution in subsequent User Tracking discoveries.

User Tracking performs DNS Lookup for a host only if the IP address of the host is being resolved for the first time.It does not perform DNS Lookup for every Major Acquisition.

This helps the application to reduce the number of queries during User Tracking Acquisition. This in turn reduces the time taken for Acquisition process.

UT.RunLookupAnalyzer

OFF

To analyze the performance of DNS servers and provide the following information in the NMSROOT\log\ut.log file:

DNS Server Efficiency for each DNS Server

Overall Summary of DNS Servers

Namelookup related settings in ut.properties file

Issues found and recommendations to overcome them

Set the value to ON to turn on the feature.

You need not enable debugging for UT to get the LookupAnalyzer data in the ut.log file.

For details on running Lookup Analyzer utility from the command prompt and example output of the utility, see Using Lookup Analyzer Utility


Modifying Acquisition Schedule

You can modify UT acquisition schedule using the Acquisition Schedule option of the Administration tab in Campus User Tracking window.

To modify acquisition schedule:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Acquisition > Schedule Acquisition.

The Acquisition Schedule dialog box appears.

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

Table 7-7 Acquisition Schedule Field Description 

Field
Description
Usage Notes

Minor Acquisition

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

None.

Major Acquisition

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

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


Modifying Ping Sweep Options

A ping sweep (also known as an ICMP sweep) is a basic network scanning technique used to determine which range of IP addresses map to live end hosts (computers). You can use a single ping to find out whether a specific end host exists on the network.

A Ping Sweep consists of ICMP (Internet Control Message Protocol) ECHO requests sent to multiple hosts. If a given address is live, it will return an ICMP ECHO reply. Ping sweeps are among the older and slower methods used to scan a network.

When Ping Sweep is enabled in Campus Manager, 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 from the Admin tab in Campus User Tracking window.

To modify Ping Sweep options:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Acquisition > Ping Sweep.

The Ping Sweep dialog box appears.

Step 3 Choose any of the following:

Disable Ping Sweep

Perform Ping Sweep on all subnets

Exclude subnets from Ping Sweep

When you choose Exclude subnets from Ping Sweep option, select the subnets which are to be excluded from Ping Sweep.

You can select subnets from the list of available subnets and add to the list of subnets to be excluded.

Step 4 Specify the Wait Interval, if Ping Sweep is enabled.

This is the time interval for which Campus Manager waits for response.

Step 5 Click Apply.

User Tracking does not perform Ping Sweep on large subnets.

For more details, see Note for Ping Sweep Option.


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.

You can increase the value of the wait interval. Wait interval helps the ping response traffic to settle, which may appear as Denial Of Service (DOS) or may affect the functioning of router by high CPU usage.

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, that 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 Campus Manager to perform User Tracking Acquisition on selected subnets. 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  > Administration > User Tracking.

The Campus User Tracking window appears.

Step 2 Select Administration > 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 subnets

All subnets added to the Selected Subnets list are included for User Tracking acquisition.

Or

Do not perform major acquisition on selected subnets

All subnets added to the Selected Subnets list are excluded for User Tracking 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

Using this option, you can modify the time interval for deleting entries from the End Host Table, IP Phone Table or the History Table from the database.

To modify the Delete Interval:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Acquisition > Delete Interval.

The Delete Interval dialog box appears.

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

Step 4 Either:

Click Delete now to delete the entries immediately.

If you select this step do not perform Step 5.

Or

Select the Delete After Every Major Acquisition check box.

If you select this option, Campus Manager will delete records older than the specified interval, after every UT Major Acquisition.

Step 5 Click Apply.


Configuring Trunk for End Host Discovery

Normally UT Acquisition discovers end hosts connected only to access ports. If you enable this feature UT Acquisition discovers end hosts connected to non-link trunk ports also.

Campus Manager classifies trunk ports as follows:

Link ports — Trunk ports connected to Cisco devices (Switch or Router).

Non-link ports— Trunk ports connected to end hosts or IP phones.

Scenarios where a Trunk port is connected to an end host:

In a switched network, many clients from different VLANs might access an enterprise resource, such as a database server.

If the server has only a standard EthernetNIC, it can belong to only one VLAN. Clients that belong to a different VLAN would have to send their traffic to a router. The router forwards the frames to the database server. The problem with this approach is the latency introduced by the router.

To overcome this, a trunk-capable NIC card can be placed in the server that understands multiple VLAN information. With this arrangement, an end station need not send its frame to the router. Instead it can directly access the file server. This makes the access much faster.

Another scenario, where servers with trunk-capable NICs are connected to Gigabit ethernet links can be understood using the figure given in http://www.cisco.com/en/US/products/hw/switches/ps679/products_configuration_guide_chapter09186a008007e7c3.html#xtocid89874.

To configure trunk ports:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Acquisition > Configure Trunk for End Host Discovery.

The corresponding page appears.

Step 3 You can:

Select Enable End Host Discovery on all Trunks to include all non-link trunk ports to UT Major Acquisition. After choosing this option, go to Step 9.

Select Enable End Host Discovery on selected Trunk(s) to include only the required set of non-link trunk ports to UT Major Acquisition. After choosing this option, go to Step 4.

Select Disable End Host Discovery on Trunk(s) to disable this feature. For this option, only the end hosts connected to access ports will be discovered by UT Major Acquisition. After choosing this option, go to Step 9.

Step 4 Select the list of switches where end hosts are connected to trunk ports, from the device selector.

Step 5 Click Show Trunks.

This displays the list of non-link trunk ports from the selected switches. Non-link trunk ports in down state are also listed here.

If you have selected devices that do not have non-link trunk ports, a message is displayed indicating the same. Change your selection to devices that have non-link trunk ports and click Show Trunks, to display the ports. Link ports are not listed here.

Step 6 Select the list of trunk ports where end hosts are connected from the Available Trunks list.

Step 7 Click Add.

The selected ports are displayed under the Selected Trunks list.

Step 8 Select either

Discover End Hosts on Trunks to include the selected ports in UT Major Acquisition.

Or

Do not Discover End Hosts on Trunks to exclude the selected ports from UT Major Acquisition.

Step 9 Click Apply.

This saves the configuration on the server.

After saving the configuration, run Data Collection. End hosts connected to trunk ports will be discovered in the successive UT Major Acquisition.

For Dynamic User Tracking to track end hosts connected to trunk ports, enable SNMP traps in these ports. For details on Enabling SNMP traps, see Enabling SNMP Traps on Switch Ports.


Specifying Purge Policy

You can specify the intervals at which old reports and jobs are to be purged, using the Purge Policy option. You can save the Purge Policy, so that the older jobs and archives are purged at the specified interval.

To specify the Purge Policy:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Reports > User Tracking Purge Policy.

The Report Settings dialog box appears.

Step 3 Check the relevant check box:

Purge Archives Older than

Purge Jobs Older than

You must specify the period in days, or weeks, or months for which you want to retain the report archives or jobs.

Step 4 Click Save.


Specifying Domain Name Display

You can specify the way in which domain names are to be displayed in User Tracking Reports, using the Domain Name Display option.

To specify the Domain Name display:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration  > Reports > Domain Name Display.

The Report Settings dialog box appears.

Step 3 Select the format for displaying the domain names in User Tracking Reports. You can:

Show full domain name suffix

Hide full domain name suffix

Hide specified domain name suffix

If you want to hide the specified domain name suffix, enter the domain name suffix in the field.

Step 4 Click Save.


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 Administration tab in the Campus Manager User Tracking window.

To import information in end host users:


Step 1 Select Campus Manager  > Administration >User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > 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 Dynamic Updates

User Tracking generates reports on various functions and attributes of the end hosts and devices connected to your network that are managed by Campus Manager . These reports are generated by polling the network at intervals set by the network administrator.

In addition to polling the network at regular intervals, Campus Manager 5.0 tracks changes about the end hosts and users on the network to provide real-time updates.

Dynamic Updates are asynchronous updates that are based on SNMP MAC notifications traps.

When an endhost is connected to a switch managed by Campus Manager, an SNMP MAC notification trap is sent immediately from the switch to the Campus Manager Server, indicating an ADD event. This trap contains the MAC address of the end host connected to the switch.

Similarly if an end host is disconnected from a switchport, an SNMP MAC notification trap is sent from the switch to the Campus Manager indicating a DELETE event. Thus Campus Manager provides real time data about end hosts coming into and moving out of the network.

The difference between UTMajor Acquisition and Dynamic UT process is :

Campus Manager collects data from the network at regular intervals for UTMajor Acquisition.

In Dynamic UT, the devices send traps to Campus Manager as and when changes happen in the network.

This implies that you need not wait till next UTMajor Acquisition cycle to see the changes that have happened in your network. This is an improvement over the earlier versions, where updates on endhost information happened based on the polling cycle.

As a result of Dynamic updates, the following reports contain up-to-date information:

End-Host Report

Contains information from UT Major Acquisition and the recently added end-hosts.

History Report

Contains information from UT Major Acquisition and the recently disconnected end-hosts/end-hosts that have moved between ports or VLANs.

Switch Port reports

Contains information about the utilization of switch ports.

SNMP Traps are generated when a host is connected to the network, disconnected from the network or when it moves between VLANs or ports in the network.

Figure 7-1 Overview of Dynamic Updates

To enable Dynamic Updates feature:

Switches must be managed by Campus Manager .

Configure Campus Manager as a primary or secondary receiver of the MAC notifications. For details, see SNMP MAC Notification Listener.

Configure all devices to send traps to the Trap Listener port of the Campus Manager server (This is the port number that you would have configured on Campus Manager Administration screen). For more details, see Enabling SNMP Traps on Switch Ports.

Configure DHCP snooping on the switches

Dynamic Host Configuration Protocol (DHCP) snooping is a security feature that filters untrusted DHCP message received from outside the network or Firewall, and builds and maintains a DHCP snooping binding table.

Campus Manager queries the CISCO-DHCP-SNOOPING-MIB to get the IP address of the end-host connected.

For details on configuring DHCP, see http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c/ipcprt1/1cddhcp.htm

User Tracking collects username and IP address through UTLite for Windows environment. For more details, see Understanding UTLite.

In a Windows environment you can either install UTLite or configure DHCP snooping to get IP address of the end host. They can also co-exist.

If you have neither installed UTLite nor enabled DHCP snooping, the IP address of the end-host connected will be updated only in the next UT Major Acquisition cycle. The ARP cache of the device should be populated with the IP address, for UT Major Acquisition to discover it.

The User Tracking Dynamic Updates process includes:

MAC User-Host Information Collector (MACUHIC) Process

User Tracking Manager (UTManager) Process

UTLite

MAC User-Host Information Collector (MACUHIC) Process

MAC User-Host Information Collector tracks wired end users dynamically. It receives MAC notifications from the switches either directly or through DFM or HPOV.

After receiving the MAC notifications, MACUHIC validates the traps as follows:

Checks whether the traps are generated from a switch managed by Campus Manager .

Checks whether the source is an access port.

If the traps are from valid sources:

Updates Campus Manager database.

Informs UTManager if the trap is received for an ADD event.

User Tracking Manager (UTManager) Process

UTManager receives the information from MACUHIC about the ADD MAC notification trap that is received. This information is not complete and can be completed using updates from DHCP or UTLite or from both.

In the UTLite process, UTLite receives details of changes in username, and the time at which the host has logged in or logged out of the network.

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.

For complete information, see Understanding UTLite.

Figure 7-2 Processes Involved in Dynamic Updates

When an end-host is connected to your network, the following happens in the background:

1. The switch to which it is connected sends a MAC notification.

2. The MACUHIC process in Campus Manager receives the MAC notification either directly from the switch or through other applications like DFM or HPOV.

3. After processing this MAC notification, MACUHIC informs the UTManager.

4. Campus Manager updates the database with the username and IP Address received from the UTLite. Database does not contain the complete information about the end host.

5. UTManager finds the following details:

Subnet, VTP domain, VLAN, Port duplex, and port speed from XML files generated after Data Collection.

Hostname from DNS Server

Campus Manager updates the database with the complete User Tracking information for the host.

The User Tracking end host history reports, end host reports, reports on switch ports, wireless clients, duplicate MAC addresses, duplicate IP addresses, and so on use this updated information while generating reports.

Viewing Dynamic Updates Process Status

You can check whether the Dynamic Updates processes are running or not.

To check the status:


Step 1 Select Campus Manager  > Administration > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Administration > Dynamic Updates.

The Dynamic Updates Process Status window appears.

If you have started the process already, the status window shows Dynamic Updates Processes are RUNNING.

Step 3 Click Stop to stop the Dynamic Updates processes.

The Stop button then toggles to Start, and the status window shows Dynamic Updates Processes are STOPPED. When you stop these processes, Campus Manager stops processing traps sent by devices.

Step 4 Click Start to restart the Dynamic Updates processes.

The Start button again toggles to Stop.


Enabling SNMP Traps on Switch Ports

You must configure the Cisco switches for sending SNMPv1/SNMPv2 MAC Notification Traps when a host is connected to or disconnected from that port. You can configure the ports Through Campus Manager Interface or Through Command Line Interface (CLI).


Note Campus Manager supports only those switches which contain the Management Information Base (MIB) named MAC Notification, for enabling the SNMP traps.


Through Campus Manager Interface

Prerequisites to enable MAC Notification on switches through Campus Manger interface:

The switches must be managed by RME.

If the devices are managed in SNMP version 2 (SNMPv2), you need to configure the Read as well as the Write community strings to enable MAC Notification in the switches.

Configure the RME server credentials in Campus Manager . For more details, see Setting RME Credentials, page 5-42.

To enable MAC notification in switches:


Step 1 Select Campus Manager  > Administration > User Tracking, from LMS Portal.

Step 2 Select Administration > Dynamic Updates > Device Trap Configuration.

The Configure Trap on Devices dialog box appears.

Step 3 Select the switches for which you want to enable the traps, from the Device Selector.

Step 4 Click Selection to see the devices that you have selected.

Step 5 Click Configure to configure MAC notification on the ports in the devices.

The Configure MAC-Notification Trap on Ports dialog box appears. Table 7-8 describes the entries in the Configure MAC-Notification Trap on Ports dialog box.

Table 7-8 Configure MAC-Notification Trap on Ports Field Description 

Field
Description

Add Campus Manager Server as Trap Receiver

Check the check box to allow Campus Manager as the Primary Receiver for traps.

Filter

You can filter the ports listed, based on port name, device name and the device address (IP address of the device).

Trap Receiver Port

Port number that you entered for receiving traps.

The default trap receiver port number of the Campus Manager server is 1431.

Port

Name of the port.

Access ports as well as Non-link Trunk ports are listed.

Device Name

Name corresponding to IP address of the switch.

Device Address

IP address of the switch.

Rows per page

Select to view 10 to 50 rows on a page.


Step 6 Check the check boxes to select the ports that you want to enable SNMP traps.

Step 7 Click Configure to enable the SNMP traps.

An Information window appears.

Step 8 Click OK.


Through Command Line Interface

If you do not have RME installed on your CiscoWorks server, you must configure the switches manually, for the switches to send MAC Notifications to the Campus Manager server.

Table 7-9 lists the commands that need to be run on each device.

Table 7-9 Commands to Enable SNMP Traps in Devices

OS Type
Commands

Cisco IOS Software

Global:

mac-address-table notification

mac-address-table notification interval 15

snmp-server enable traps MAC-Notification

snmp-server host HOST version 1 default udp-port PORT mac-notification

Interface:

snmp trap mac-notification added

snmp trap mac-notification removed

Cisco Catalyst Operating System

For Cisco Catalyst 4000 series devices:

set cam notification enable

set snmp trap enable macnotification

set snmp trap HOST default port PORT

set cam notification added enable INTERFACE

set cam notification removed enable INTERFACE

For Cisco Catalyst 6000 series devices:

set cam notification enable

set snmp trap enable macnotification

set snmp trap HOST public version 1 port PORT

set cam notification added enable INTERFACE

set cam notification removed enable INTERFACE


For complete list of devices supported by Campus Manager, see http://www.cisco.com/en/US/products/sw/cscowork/ps563/products_device_support_tables_list.html

SNMP MAC Notification Listener

You must enable the switches to send SNMP MAC notifications to the listener, to avail the Dynamic Updates feature. After you enable the switches, you can choose either Campus Manager , CiscoWorks Device Fault Manager (DFM), or HP OpenView (HPOV) as the primary listener for MAC notifications.

If you select Campus Manager as the Primary listener, the MAC notifications reach the application directly from the switches.

If you select Campus Manager as the Secondary listener, (HPOV or DFM as the primary listener), MAC notifications reach Campus Manager through HPOV or DFM.


Note Campus Manager configures SNMP MAC Notification version 1 as the default version on switches for Dynamic Updates.


To select the MAC notification listener:

Configuring SNMP Trap Listener

HPOV as Primary Listener

DFM as Primary Listener

Configuring SNMP Trap Listener

Campus Manager receives SNMP traps directly from the switches, unless you configure the port to direct the traps through HP Open View (HPOV) or CiscoWorks Device Fault Manager (DFM) applications.

To configure the trap listener:


Step 1 Select Campus Manager  > Administration > User Tracking, from LMS Portal.

Step 2 Select Administration > Dynamic Updates > Trap Listener Configuration.

The Trap Listener Configuration dialog box appears.

Step 3 Check Listen traps from Device to configure the trap reception directly from the devices

or

Check Listen traps from DFM/HPOV to receive the traps through these applications.

Step 4 Enter the port number of the port through which you want to receive the traps, in the Trap Listener Port field.

The default trap listener port number of the Campus Manager server is 1431.

Step 5 Click Apply to save the details.


Configuring Properties to Enhance Security

You can configure certain properties in the Campus Manager server to enhance the security of the system. By setting these properties, you can configure the server to receive traps only from specified devices and with specified community strings.

The name and path of the properties file is:

NMSROOT/campus/lib/classpath/com/cisco/nm/cm/ut/uhic/mac/properties/macuhic.properties

where NMSROOT is the directory where you have installed CiscoWorks and macuhic.properties is the filename.

Table 7-10 lists the properties that can be configured.

Table 7-10 Properties to Enhance Security

Property
Description

security.iplist

This is the list of IP addresses of valid sources from which Campus Manager server will accept traps.

Example:

security.iplist=10.77.210.210:10.77.210.211

security.chkIP

You have to set this property to true, for the property security.iplist to come into effect. The default value is false.

security.communitylist

These are the community strings that Campus Manager server will use to validate traps received from a device.

Example: security.communitylist=public:private:test

For more information on Configuring SNMP traps, see the corresponding device-side documentation.

security.chkCommunity

You have to set this property to true, for the property security.communitylist to come into effect. The default value is false.


While setting the values for security.iplist and security.communitylist properties, the following rules need to be followed:

The values must be separated by colon.

The list must not end with a colon.

There must be no spaces between the colon and the values.

You must enter IP addresses in valid dotted-decimal format, for security.iplist property. Campus Manager does not validate them.

HPOV as Primary Listener

If you select HPOV as the primary listener, you must perform the following to receive the Dynamic Updates through Campus Manager :

Install CiscoWorks Integration Utility

Install Trap Adaptor for HPOV

The supported versions of HPOV are HPOV 6.x and HPOV 7.0.

Install CiscoWorks Integration Utility

You must have CiscoWorks Integration Utility (Integration Utility) installed on your system. Integration Utility is a utility that integrates CiscoWorks applications with third-party Network Management Systems (NMS).

This utility is available as part of the CD-ROM that contains CiscoWorks Common Services 3.1 and CiscoView 6.1, in the CiscoWorks LAN Management Solution 2.5, or download the utility from http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-utility.

This integration utility adds Cisco device icons to topology maps, allows Cisco MIB browsing from NMS, and sets up menu items on the NMS to launch remotely installed CiscoWorks applications.

See User Guide for CiscoWorks Integration Utility 1.6, for more details on the integration utility.


Note You must install the Integration Utility on the same machine on which you have installed HPOV.


Install Trap Adaptor for HPOV

Campus supports Trap Adapter for OpenView on Windows, Solaris and HP-UX operating systems.

To install the adaptor on Windows:


Step 1 Locate the TrapListener.conf file in the NMSROOT/campus/hpovadapter/win/ directory.

Step 2 Modify the Trap Receiver address and the port number to the Campus Manager values, in the file.

Step 3 Set the LIB environment variable to HP OpenView lib directory.

Step 4 Run the fwdTrap.exe program located in the same directory.

The Trap Adapter gets attached to OpenView process and starts sending traps to the Campus Manager server.


To install the adaptor on Solaris and HP UX:


Step 1 Locate the TrapListener.conf file in the /opt/CSCOpx/campus/hpovadapter/SOL directory.

Step 2 Modify the Trap Receiver address and the port number to the Campus Manager values, in the file.

Step 3 Set the LD_LIBRARY_PATH environment variable to HP OpenView lib directory.

Step 4 Run the fwdTrap program located in the same directory.

The Trap Adapter gets attached to OpenView process and starts sending traps to the Campus Manager server.


Supported Platforms (Operating Systems)

The supported platforms for the HP NNM and HPOV adapters are:

Solaris 2.8 and 2.9

HP-UX 11.0

Windows 2000 Professional with SP3 or SP4

Windows 2000 Server with SP3 or SP4

Windows 2000 Advanced Server with SP3 and SP4

Windows 2003 Server Standard Edition

Windows 2003 Server Enterprise Edition

DFM as Primary Listener

If you select DFM as the primary listener, you must perform the following to receive MAC Notifications from the switches, thus availing the Dynamic Updates feature in Campus Manager .

The default port number of DFM Server for receiving Traps from the switches is 9000. You must configure or verify this port number on the device, for the device to forward the Traps to DFM. The trapd.conf file has the details regarding the port number that receives the Traps at the DFM server.

To enable DFM to forward the MAC Notifications, you must modify the trapd.conf file in the DFM server, at NMSROOT/object/smarts/conf/trapd directory. You can modify the file through the command line interface or through the application interface.

You can configure the application to forward the MAC Notifications to Campus Manager Server in two ways:

From LMS Portal

From the DFM Server

From LMS Portal


Step 1 Select Device Fault Manager > Configuration.

The Configurations page appears.

Step 2 Select Other Configurations > SNMP Trap Forwarding.

The Notification Services page appears.

Step 3 Enter the Hostname and the port number of the Campus Manager server to which you want to forward the MAC Notifications.

Step 4 Click Apply to configure.

The trapd.conf file is modified and the DFMServer process is restarted.



Note If you configure through CiscoWorks, Campus Manager server receives all Traps including MAC Notification.


From the DFM Server


Step 1 Access the DFM server using Telnet.

Step 2 Enter pdterm DfmServer at the command line to stop the DFM server.

Step 3 Navigate to NMSROOT/object/smarts/conf/trapd directory.

Step 4 Edit the trapd.conf file in the directory to reflect the following changes.

Enter:

FORWARD: address OID generic type specific type \ host [:port] | [:port:community] [host [:port] | [:port:community] ...], where the explanation for each variable is provided in the trapd.conf file.

Step 5 Enter pdexec DfmServer at the command line to restart the DFM server.


Debugging Options

When you face issues in running User Tracking, logging can be enabled for debugging purposes. Debug settings related to all User tracking functionality can be done here.

You can enable debugging for:

User Tracking Server side processes

You can debug events related to all User Tracking server side processes. For details on this, see Debugging Options for User Tracking Server.

Dynamic User Tracking

You can set the debugging options required for Dynamic Updates. For details on this, see Debugging Dynamic Updates.

User Tracking Client side activities

You can debug events related to User Tracking client side activities. For details on this, see Debugging Options for User Tracking Reports.

Dynamic User Tracking Console

This feature helps you to troubleshoot the three major processes involved in Dynamic User Tracking updates. For details on this, see Dynamic User Tracking Console

Table 7-11 explains the difference between Debugging dynamic updates and Dynamic User Tracking:

Table 7-11 Difference between the debugging methods 

Debugging Method
Explanation
Advantages
Limitations

Debugging Dynamic Updates

Allows you to enable debugging for the various processes, which results in immediate logging.

Complete information about trap processing starting from receiving traps, processing them, and information about various stages in MACUHIC, UTLite and UTManager.

Interferes with the trap processing capability of Campus Manager.

We recommend that you enable debugging for this module only when requested by TAC.

Dynamic UT Console

Error conditions that occurred while processing Dynamic Updates are stored in circular buffers, in the Campus Manager Server.

If you need to see these conditions, you can download the errors in a file format.

Does not interfere with the trap processing capability of the Campus Server

Can be used to get only error conditions

Circular buffers hold only the last 10 error conditions


Debugging Options for User Tracking Server

You can debug events related to all User Tracking server side processes as follows:


Step 1 Go to Campus Manager > Administration > Debugging Options >User Tracking Server.

The debugging page appears.

Table 7-12 User Tracking Server Side Debugging Options 

Field
Description
Usage Notes

Enable Debug

Check this option to enable logging for User Tracking Server side activities.

You can select the modules for debugging only after you select this option.

Modules

Specify the modules on which you need to enable debugging.

Click Select to view the available modules and select the modules in which debug is to be enabled. Table 7-13 lists the debug modules available for User Tracking Server.

File Name

Name of the log file in which the trace messages are to be recorded.

The default log file is NMSROOT\log\ut.log

Maximum File Size (lines)

Maximum size of the file in lines

 
Enable Device Level Debugging

Device IP(s)

IP addresses of devices for which you need to log debugging messages.

This field is enabled only when the Device Level Debugging option is enabled.


Step 2 Click Apply.


Selecting User Tracking Server Side Debug Modules

Table 7-13 describes the debug modules available for User Tracking Server in Campus Manager.

Table 7-13 User Tracking Debug Modules 

Module
Description

user tracking

Provides user tracking functionality. Enable debugging for this if user tracking fails to discover end hosts as expected.

framework

Constructs and maintains data in the memory.

Provides framework for Campus Manager features.

Enable debugging for this module only when requested by TAC. This is because enabling debugging for this module creates huge logs.

devices

Provides specific information, if any, available for device categories.

Enable debugging for this module if you encounter issues specific to a particular device type.


Click OK to save the selected modules or click Cancel to exit.

Debugging Dynamic Updates

You can set the debugging options required for Dynamic Updates. Enabling debugging, records all the required information to the log files. To know the difference between Dynamic User Tracking Console and debugging Dynamic Updates, see Table 7-11.

To enable debugging Dynamic Updates:


Step 1 Go to Campus Manager > Administration > Debugging Options > Dynamic User Tracking.

Or

Go to Campus Manager > Administration > User Tracking > Administration > Debugging Options > Dynamic User Tracking.

The debugging page appears.

Step 2 Check Enable Debug to set the options.

Step 3 Select the Service Name from the drop down list in the Service Name field.

The framework modules appear in the Module Name column. The framework modules depend on the service that you select.

Step 4 Select the debug level for each module.

The debug level options are INFO, DEBUG, and TRACE.

INFO logs minimum information required for debugging and is the default option. DEBUG is the next level of debugging. TRACE provides complete debugging information and creates huge logs.

Step 5 Enter the filename for the log file in the Log Filename field.

The default log file for UT LITE is NMSROOT\log\utlite.log

The default log file for MACUHIC is NMSROOT\log\macuhic.log

The default log file for UTManager is NMSROOT\log\utm.log

The default value for Log file size is 1,000,000 lines. You can give values between 1 and 2,147,483,647. Giving zero or negative values or alphabets results in errors.

Step 6 Click Apply to save the settings.


Dynamic User Tracking modules available for debugging are explained in Table 7-14:


Note Enabling debugging for these modules creates huge logs which interferes with the Trap processing capability of Campus Manager. We recommend that you enable debugging for this module only when requested by TAC.


Table 7-14 Dynamic User Tracking Debug Modules 

Module
Description

UT Lite

control plane

Handles configuration events related to:

Log level Settings

Log file

Port number

For example:

If you changed the log file from X to Y, but logging still happens in X , enable debugging for this module.

listener

Listens to data sent by the UTLite script installed in the Windows/Novell server.

Checks for the integrity of the data received.

execution framework

Handles code level execution of the data received.

Enable debugging for this module to debug Java related errors.

execution

Processes and validates the data received.

UTLite receives MACAddress, IPAddress and User logged in for the end host. This information is updated to the database only if the endhost has been discovered in last UT Major Acquisition cycle or through Dynamic User Tracking.

MACUHIC

control plane

Handles configuration events related to:

Log level Settings

Log file

Port number

listener

Listens to SNMP traps sent by devices.

Checks for the integrity of the data received.

execution framework

Handles code level execution of data received by MACUHIC.

Enable debugging for this module to debug Java related errors.

decoder

Validates the traps sent by devices by checking whether:

The trap is sent by a device managed by Campus Manager.

The SNMP version is correct

execution

Checks whether:

The data received is duplicate data

If the data is sent by a Link port or Access port.

Dynamic UT does not process traps sent from link ports.

Updates the database with information received and forwards it to UTManager for further processing.

UTManager

 

control plane

Handles configuration events related to:

Log level Settings

Log file

Port number

listener

Listens to data sent by UTLite and MACUHIC.

Checks for the integrity of the data received.

execution framework

Handles code level execution of data received by UTManager.

Enable debugging for this module to debug Java related errors.

decoder

Validates the data received from UTLite, MACUHIC, SNMP data from DHCP Snooping MIB and the other data sent by external systems.

execution

Processes the data received and updates the database.

es framework

Handles queries sent to External Systems.

es.snmp

Handles SNMP queries sent to External Systems.

es.subnet

Performs subnet calculation based on the information sent by External Systems.

es.db

Handles database operations.


Debugging Options for User Tracking Reports

You can debug events related to User Tracking client side activities as follows:


Step 1 Go to Campus Manager > Administration > Debugging Options >User Tracking Reports.

Or

Go to Campus Manager > Administration > User Tracking > Administration > Debugging Options > User Tracking Reports.

The debugging page appears.

Step 2 Select the level of debugging. It can be any one of the following:

INFO

Only informational messages are recorded in the log file. This is the default option.

FATAL

Messages related to fatal errors are recorded in the log file.

DEBUG

All User Tracking client side messages are recorded in the log file.

The Log File Name field specifies the location and name of the log file. The default log file is NMSROOT\log\Cmapps.log

Step 3 Click Apply.

Debugging is enabled for UT client side activities and the messages are recorded in the corresponding log file.


Dynamic User Tracking Console

This feature helps you to troubleshoot Dynamic User Tracking updates in a detailed way. Dynamic UT consists of three major processes:

UTLite

UTManager

MACUHIC

Each process will keep track of different error conditions using circular buffers in the memory. For each error condition, the buffer will have the count of error occurrences and the conditions under which the error occurred.

You can write this information from the memory to a file if you need to, and troubleshoot based on that. To know the difference between Dynamic User Tracking Console and debugging Dynamic Updates, see Table 7-11.

To enable Dynamic User Tracking Console:


Step 1 Select Campus Manager > Administration > User Tracking > Administration > Debugging Options > Dynamic User Tracking Console.

The debugging page appears.

Step 2 Select the Service name from one of the following:

UTLite

UTM

MACUHIC

The error conditions related to that process is listed under the Error Details section.

Step 3 Select the error condition for which you need details and click Generate.

A new file is generated with all the error details and stored in the Campus Manager server. Its also listed under the File list pane.

Step 4 Select a file and:

Click View to see the file contents.

Click Download to save the file in your local machine.

Click Delete to delete the file from the server. You can delete multiple files at the same time.


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 Cisco switches. During this acquisition process it also tabulates specific connection information about the end station.

The Reports section displays various options to view, create and schedule various reports that User Tracking provides.

User Tracking Data Migration

When you upgrade from older versions of Campus Manager to Campus Manager 5.0, complete details about end hosts and IP phones are migrated. This helps you retain data from the earlier database.

For complete details on Data Migration, see Data Migration Guide for LAN Management Solution 3.0

Using User Tracking Reports

The Reports section displays various options to view, create and schedule various reports that User Tracking provides. This section contains:

Viewing Quick Reports

Exporting and Printing Reports

Viewing Report Jobs List

Viewing Job Details

Using Report Generator

Viewing Duplicates Report

Viewing End Hosts Reports

Viewing IP Phones Reports

Viewing Reports on Wireless Clients

Understanding Switch Port Usage Reports

Understanding History Report

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 filter criteria for which you want to generate the report.

To view the reports:


Step 1 Select Campus Manager  > User Tracking > Reports.

The Quick Report dialog box appears.

Step 2 Enter the required information as given in Table 7-15.

Table 7-15 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.

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.

For details on date formats and operator values, see Operator Values and Date Formats for Last Seen Column.


Step 3 Click Submit.

The selected type of report is 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 and Date Formats for Last Seen Column

Table 7-16 lists the operators available for the Last Seen column and their corresponding values for Pattern field.

Table 7-16 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


Exporting and Printing Reports

Campus Manager allows you to export and print reports. For details see,

Exporting Reports

Printing Reports

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 Enter the format in which the report needs to be exported. You can export reports to CSV or PDF format.


Note End Host Report and End Host History Reports can be exported only to CSV format.


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.


Restrictions on Printing Reports

For End hosts report, End hosts history report and IP Phones report, you can print only 30,000 records at a time. If you want to print more than 30,000 records, do it in batches of 30,000.

For End hosts report and End hosts history report, comma separated values are not accepted in the print range.

For example, specifying the range as 10-40, 70-80 will not work.

Specify the range as 10-40 to print from the 10th record to the 40th record.

Repeat it for 70-80 range.

Viewing Report Jobs List

You can view a list of scheduled jobs and their current status using the Report Jobs option of Campus Manager User Tracking window.

To view Report Jobs:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Reports > Report Jobs.

The Report Jobs dialog box appears.

Table 7-17 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. It includes:

Duplicate IP

Duplicate MAC

Duplicate MAC and VLAN

Ports with Multiple MAC

End Hosts — All Host entries

History — End Host History

History — Switch Port Utilization

IP Phone — All IP Phone entries

Switch Port Usage — Switch Port Utilization

Switch Port Usage — Switch Port Summary

Switch Port Usage — Recently Down

Switch Port Usage — Reclaim Unused Up

Switch Port Usage — Reclaim Unused Down

Wireless Report — Wireless End Hosts

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

The report is launched. Clicking on the Job ID also launches the report.


Stopping Jobs

To stop a scheduled job:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager 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 Manager 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.

History

End Host History, Switch Port Utilization.

IP Phones

All IP Phone Entries

Switch Port Usage

Recently Down, Switch Port Summary, Switch Port Utilization, Reclaim Unused Down, Reclaim Unused Up.

Wireless Report

Wireless End Hosts


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

Duplicate report helps you to identify possible network discrepancies related to MAC Address or IP Address of the end hosts. Network Administrators can either correct them or ignore them, if they feel that these discrepancies will not affect the network.

For example,

Single MAC address may be detected in more than one port

Single IP address assigned to more than one end host

Suitable action needs to be taken based on the network condition.

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.


Note Running Immediate Report on a large amount of data will take a long time to complete. We recommend that you run it as a Scheduled Job.


To view reports on duplicates:


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 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 7-18 displays details of the columns in the duplicates report.

Table 7-18 Duplicate Reports Column Description 

Field
Description

UserName

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

You can configure the Asynchronous Network Interface (ANI) Server to collect user names. See the ANI Server online help for further information.

MACAddress

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

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

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

Clicking on the value launches the Host Center page for that endhost.

HostName

Name of host. Clicking on the value launches the Host Center page for that endhost.

IPAddress

IP address of host. Clicking on the value launches the Host Center page for that endhost.

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. Clicking on the value launches the Device Center page for that device.

Device

IP address of device to which end user node is attached. Clicking on the value launches the Device Center page for that device.

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

Parent VLAN of the host.

Secondary VLAN

Secondary VLAN of the host.

Ring

Ring number for Token Ring VLANs

Bridge

BRF bridge number

Last Seen

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

Notes

Notes on this entry, that you enter.

dot1xEnabled

Status of Dot 1x authentication on the device. Two status are:

True—When authentication is enabled on the device.

False—When authentication is disabled on the device.

Associated Routers

IP addresses of the routers associated with the host.

Discrepancies Found

Number of discrepancies found associated with the port.

Best Practice Deviations Found

Number of best practice deviations found associated with the port.


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.

End hosts report also displays all active wireless clients, which are connected to your network.

To view report on end hosts:


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 End Hosts from the Select Application list.

Step 4 Select All Host Entries, 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 a description in the Job Description field of the Job Info area.

Step 7 Enter a valid E-mail ID in the Email field, of the Job Info 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

This section contains the following topics:

Launching CiscoWorks Assistant from End Host Report

Duplicate MAC Entries in End Host Reports

Handling Disconnected End Host entries in the Report

Printing End Host Reports

Filters in End Host Reports

End Hosts Report—Standard Layout Columns

End Hosts Report—All Columns Layout

Launching CiscoWorks Assistant from End Host Report

To launch CiscoWorks Assistant from End Host Reports:


Step 1 Click on MAC Address or Host name or IP address in the report.

The Host center page is launched for that endhost.

Step 2 Click Troubleshoot at the bottom of the page.

CiscoWorks Assistant > End Host/ IP Phone Down page is launched. Launch the report based on the instructions provided in Help. This report displays the information that you need to troubleshoot and analyze the connectivity issues.


Duplicate MAC Entries in End Host Reports

Campus Manager lists endhosts, whose MAC address is seen in any of the managed devices at the time of running User Tracking Major Acquisition.

It merges CAM table and ARP table entries from multiple switches and routers to gather information on end hosts.

An endhost creates multiple ARP/CAM entries in different devices if the endhost:

Is in DHCP environment and the IP Address changes often

Moves from one port to another

Moves from one VLAN to another

The entries are removed from the device if ARP timeout/CAM timeout happens.

Campus Manager treats the end host as a distinct entity, if any of the following information about the end host does not match:

IP Address

VLAN

Port

Device Name

MAC Address

For example, end hosts with same MAC Address but two different IP address are listed as two different entities in the end hosts report.

Handling Disconnected End Host entries in the Report

Campus Manager lists end hosts that are discovered during User Tracking Acquisition in the end hosts report. If any of these end hosts are found disconnected during subsequent acquisitions, their data is moved from End Host reports to History reports. This is the case with User Tracking Major Acquisition with no subnets configured.

In case of all other Acquisitions, data about disconnected end hosts are moved from end host reports to history reports only if the device is reachable through SNMP, at the time of acquisition.

For example,

Assume there are five end hosts connected to device X, which have been discovered previously and data is available in End host reports. You start a device based UT Acquisition for that device X.

At the time of UT Acquisition assume that:

Three end hosts are disconnected

The device is unreachable through SNMP

In this case, since the CAM table of that device is not read at the time of acquisition, data about the disconnected end hosts will remain in the End Host reports. They are not moved to History reports.

Printing End Host Reports

You can print only 30,000 records at a time. If you want to print more than 30,000 records, do it in batches of 30,000.

Comma separated values are not accepted in the print range. For example, specifying the range as 10-40, 70-80 will not work. Specify the range as 10-40 to print from the 10th record to the 40th record. Repeat it for the 70-80 range.

Filters in 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 7-19 displays details of the columns in End Hosts Report—Standard Layout.

Table 7-19 End Hosts Report—Standard Layout Columns 

Column
Description

User Name

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

MAC Address

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

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

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

If you click on the value it launches, the Host Center page for that endhost.

Host Name

Name of host. If you click on the value it launches, the Host Center page for that endhost.

IP Address

IP address of host. If you click on the value it launches, the Host Center page for that endhost.

Subnet

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

Device Name

Name corresponding to IP address of device. If you click on the value it launches, the Device Center page for that 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 is displayed in the format dd mon yyyy hh:mm:ss.

Notes

Notes on this entry, that you enter.


Table 7-20 displays details of the columns in End Hosts Report—All Columns Layout.

Table 7-20 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 Asynchronous Network Interface (ANI) Server to collect user names. See the ANI Server online help for further information.

MACAddress

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

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

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

Clicking on the value launches the Host Center page for that endhost.

HostName

Name of host. Clicking on the value launches the Host Center page for that endhost.

IPAddress

IP address of host. If you click on the value it launches, the Host Center page for that endhost.

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. If you click on the value it launches, the Device Center page for that device.

Device

IP address of device to which end user node is attached. If you click on the value it launches, the Device Center page for that device.

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

Parent VLAN of the host.

Secondary VLAN

Secondary VLAN of the host.

Ring

Ring number for Token Ring VLANs

Bridge

BRF bridge number

Last Seen

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

Notes

Notes on this entry, that you enter.

dot1xEnabled

Status of Dot 1x authentication on the device. Two status are:

True—When authentication is enabled on the device.

False—When authentication is disabled on the device.

Associated Routers

IP addresses of the routers associated with the host.

Discrepancies Found

Number of discrepancies found associated with the port. If you click on the number it launches, the Discrepancies report.

Best Practice Deviations Found

Number of best practice deviations found associated with the port. If you click on the value it launches, the Best Practice Deviations report.


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 a report on IP phones:


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 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 7-21 gives details of the columns in IP Phones Report—Standard Layout.

Table 7-21 IP Phones Report—Standard Layout Columns 

Column
Description

PhoneNumber

Phone number.

MACAddress

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

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

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

Clicking on the value launches the Host Center page for that endhost.

IPAddress

IP address of phone.

CCM Address

IP address of the Cisco CallManager.

Status

Status of the phone, as known to Cisco Call Manager

PhoneType

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

PhoneDesc

Description of the phone.

DeviceName

Name corresponding to IP address of device.

LastSeen

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


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

Table 7-22 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 is displayed in the format, xx-xx-xx-xx-xx-xx.

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

Clicking on the value launches the Host Center page for that endhost.

IPAddress

IP address of phone, which is 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.


Printing IP Phones Reports

You can print only 30,000 records at a time. If you want to print more than 30,000 records, do it in batches of 30,000.

Understanding Switch Port Usage Reports

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

Report on Recently Down Ports

Reclaim Unused Down Report

Reclaim Unused Up Report

Switch Port Summary Report

Switch Port Utilization Report

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

Group Selector can be used to create reports based on device groups. For details, see Using Group Selector.

Campus Manager classifies trunk ports as follows:

Link ports — Trunk ports connected to Cisco devices (Switch or Router).

Non-link ports— Trunk ports connected to end hosts or IP phones.

Report on Recently Down Ports

Campus Manager generates report for recently down ports as follows:

Link ports that were connected to a device in the previous Data collection, but found unconnected in the current Data Collection

Access ports that were connected to an endhost in the last UT Major Acquisition cycle, but found unconnected in the current Data Collection

If the access ports are still in unconnected state when the next UT Major Acquisition cycle runs, they are classified as Unused Up or Unused Down ports and are moved to the Reclaim Unused Up or Reclaim Unused Down reports.

Reclaim Unused Down Report

Campus Manager queries Access ports to generate the Unused Up report. It uses Access ports:

That are administratively down

AND

That were previously connected to an endhost but are unconnected atleast for a period of one day.

You can generate reports on ports which have been in Unused Down state for a specified interval of time.

Reclaim Unused Up Report

Campus Manager queries Access ports to generate the Unused Up report. It uses Access ports:

That are administratively up

AND

That were previously connected to an endhost but are unconnected atleast a day

You can generate reports on ports that have been in Unused Up state for a specified interval of time.


Note Reclaim Unused Up and Reclaim Unused Down reports are used to generate reports on ports that were previously connected to an endhost, but are unconnected atleast for a day.


Switch Port Summary Report

Switch Port Summary report gives the number of Connected, Free, and Free down ports in each switch.

Ports which are administratively up but are not connected to a device or endhost are Free Ports.

Ports which are administratively down and are not connected to a device or endhost are Free Down ports.

This report also displays the sum total of Connected, Free and Free Down ports in each switch. This report lists all the Down ports in a switch, regardless of whether they were previously connected to an endhost or not.

The number for Connected, Free and Free Down ports are given as links. Clicking on them launches a detailed report giving the Port, Port name, Administrative and Operational status of the ports for the selected device.

For details on generating and viewing these reports, see Generating Switch Port Reports.

Switch Port Utilization Report

The Switch Port Utilization report lists switches that have crossed utilization threshold limits, along with the value of percentage port utilization. This report enables you to do capacity planning for network growth.

Port Utilization for each switch is calculated as follows:

% Port Utilization (per switch) = (Number of Connected ports/ Total number of ports) * 100

Greater than option lists the switches whose port utilization is greater than the specified threshold.

Less than option lists the switches whose port utilization is less than the specified threshold.

Between option lists the switches whose port utilization falls between the specified threshold limits.

You can configure these reports as jobs, to get the list of switches that have crossed the threshold limits, at regular intervals. For details on Configuring reports as jobs, see Generating Switch Port Reports.

Using Group Selector

Group Selector allows you to create report jobs based on device groups.The Group Selector displays only the device groups that exist in the network and not the individual devices that form the group.

When a report job is created based on a device group, Campus Manager evaluates that group at the time of running the job, and devices corresponding to that group are used in the report generation.

In case of devices being included or deleted from the group after scheduling the report job, the report will reflect these changes, since Campus Manager dynamically evaluates the group information at the time of running the report job.

For example, if you have

1. Created a User Defined Group, with devices ranging from 10.77.210.1 to 10.77.210.15.

2. Scheduled a Switch Port Summary report for this group.

3. Deleted Device 10.77.210.13 from the group.

When the report job runs at the scheduled time, the resultant report will not contain information on 10.77.210.13.

Group Selector is available for all Switch Port Reports and Switch Port Utilization History Report.

Generating Switch Port Reports

To view a report on Switch Port usage:


Step 1 Select Campus Manager  > User Tracking > Reports.

The Campus Manager User Tracking window appears.

Step 2 Select Reports > Report Generator.

The Report Generator dialog box appears.

Step 3 Select Switch Port Usage from the drop down list.

Step 4 Select one of the following from the sub-list:

Recently Down

Reclaim Unused Down

Reclaim Unused Up

Switch Port Summary

Switch Port Utilization

The Report Generator page appears.

If you select the report for Switch Port Utilization, go to .

If you select the report for Unused Up or Unused Down ports, go to .

If you select either Recently Down or Switch Port Summary, go to Step 5.

For Switch Port Utilization report, specify the percentage value of utilization and the condition indicator.

For example, select greater than and 90 from the drop down lists to generate a report on devices, where port utilization exceeds 90%. The utilization percentage drop-down list is editable. It allows you to specify a value, other than the ones listed.

For Report on Unused Up or Unused Down ports, either:

Specify the number of days. The maximum number of days that can be specified is 999.

Or

Specify the date from which you want to generate the report.

For example, select 30 from the Unused for drop down list, to generate report for ports that are in unused state for the past 30 days.

The Unused for drop-down list is editable. It allows you to specify a value, other than the ones listed.

Step 5 Select the device(s) from the Device Selector or Group Selector, for which you want to view the Port information.

Step 6 Select the Run Type. It represents the periodic interval at which the report is generated. It can be one of the following:

Immediate

Once

Daily

Weekly

Monthly

Quarterly

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

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

Step 9 Click Submit.

If the Run Type is Immediate, the report is generated.

For other Run Types the report job number is displayed. You can view the list of jobs in the Report Jobs page. For more details on this, see Viewing Report Jobs List


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 7-23 describes the device attributes available for defining rules.

Table 7-23 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.

IPAddress

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

In addition to the above, the following operators are also available for the variable IPAddress:

startswith

endswith

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

Interpreting Switch Port Utilization Report

Table 7-24 describes the columns of Switch Port Utilization Report:

Table 7-24 Switch Port Usage Report  

Field
Description

Device Name

Name of the device.

IP Address

IP Address of the device.

Usage (%)

Percentage usage of ports in the device. This is the ratio between the Connected ports to the Total number of ports.

Connected Ports/Total Ports

Actual number of Connected Ports/ Actual number of Total Ports in the device.


The Name and IP address of the device are links. Clicking on them takes you to the Device Center, where you have detailed information about the device.

The Usage percentage of a device is also displayed as a link. Clicking on it takes you to a detailed report of all ports in the device. For more details on this, see Switch Port Utilization Report

Interpreting Switch Port Usage Reports

The following reports have information as described in Table 7-25:

Reclaim Unused Up

Reclaim Unused Down

Recently Down ports

Detailed Report on Connected Ports, Free ports and Free Down Ports

Table 7-25 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

Administrative status of the port

Last Used (For Reports on Unused Up & Unused Down Ports)

Date and time when the port was last used.


Switch Port Utilization Report

This report has three sections:

Connected Ports

The ports that are administratively UP and are connected to a device will be listed here.

Free Ports

The Ports that are administratively UP but are not connected to a device will be listed here.

Free Down Ports

The ports that are administratively down will be listed here.

Interpreting Summary Report for Switch Ports

The Switch Port Summary Report displays the details given in Table 7-26.

Table 7-26 Summary Report Field/Column Description 

Field/Column
Description

Device Name

Name of the device displayed as link. Clicking on it launches CiscoWorks Device Center from where you can perform device-centric activities.

IP Address

IP Address of the device displayed as link. Clicking on it launches CiscoWorks Device Center from where you can perform device-centric activities.

Connected Ports

Number of ports that are connected to a device/endhost.

Click the number to view the details on the ports.

Free Ports

Number of ports that are administratively up but are not connected to any device/endhost.

Click the number to view the details on the ports.

Free Down Ports

Number of ports that are administratively down and are not connected to any device/endhost.

Click the number to view the details on the ports.

Total Ports

Total number of ports in that device (Sum of Connected, Free and Free Down ports).


Understanding History Report

History reports help you to track the log in and log out information about the end hosts and the users in your network.

They provide information about the end hosts that were connected to and disconnected from each switch port. History Reports can also track the various users who logged in and out of the end hosts.

You can generate History reports to understand the utilization of switch ports. These reports help you to estimate the usage of ports and devices. You can also generate the reports based on the username of the host, MAC address, IP address, and device name. History reports also display all active wireless clients, which are connected to your network.

This section contains:

Viewing History Reports for Switch Port Utilization

Interpreting History Reports for Switch Ports

History Reports Based on Filters

Interpreting End Host History Reports

Viewing History Reports for Switch Port Utilization

History Report for Switch Port Utilization helps you to view the log in and log out of end hosts for a set of selected devices.

To view the User Tracking history report for switch port utilization:


Step 1 Select Campus Manager  > User Tracking > Reports > Report Generator.

Step 2 Select History from the Select an Application drop down menu on the left, in the Report Generator window.

Step 3 Select Switch Port Utilization from the Select a Report drop down menu on the right, in the Report Generator window.

Step 4 Select the devices from Device Selector or the device groups from the Group Selector. For details on Group Selector, see Using Group Selector.

Step 5 Specify the period for which you need the report in the Period area.

You must specify the start and end dates, which defines the period for which User Tracking must generate the report.

If you enter the same value for start and end dates, the application displays an error message.

Step 6 Select a Run type from the drop down menu, in the Scheduling area to schedule the report generator according to your requirement.

You can schedule it for generating the report immediately, once, daily, weekly, monthly or quarterly. If you choose to generate the report immediately, go to Step 10.

Step 7 Set the date and time for generating the report, in the Scheduling area.

Step 8 Enter a description to identify this job in the Job Description field.

Step 9 Enter a valid e-mail ID in the Email field, of the Job Info area, to receive the report through mail.

Step 10 Click Submit to generate the report or click Reset to modify the values that you have entered.


Interpreting History Reports for Switch Ports

The Report lists each switch with its ports and the usage time in hours.

Table 7-27 describes the entries in the History Report for switch ports.

Table 7-27 Switch Port Utilization Report Field Description 

Field
Description

Port

Lists the names of the ports in the switch.

Usage Time (Hrs, Mins & Sec)

Duration of time for which the port is connected to a host or utilized.


Click the usage time value for a port. The History Report for that port appears.

History Reports Based on Filters

You can view the log in and log out information of the end hosts, by querying the database. To do this use username, MAC address, IP address, or device name. Report Generator in User Tracking helps you to view a report on the history of the end hosts.


Note Running Immediate Report on a large amount of data will take a long time to complete. We recommend that you run it as a Scheduled Job.


To generate the reports on the log in and log out:


Step 1 Select Campus Manager  > User Tracking > Reports > Report Generator.

Step 2 Select History from the Select an Application drop down menu on the left, in the Report Generator window.

Step 3 Select End Host History from the Select a Report drop down menu on the right, in the Report Generator window.

Step 4 Select the filter value from the Column drop down.

The filter can be any one of the following:

Username

MAC Address

IP Address

Device Name

Step 5 Select the variable option from the Operator drop down menu, to link the device credential with the value you want to enter.

Step 6 Enter the filter value in the Value text box field, for which you want to generate the report.

Apart from specific values, blank space and * can also be given.

Step 7 Specify the period for which you need the report in the Selection Criteria area.

You must specify the start date, start time and end date, end time. These dates define the period for which User Tracking must generate the report.

Step 8 Select Run Type from the drop down menu, in the Scheduling area to schedule the report generator according to your requirement.

You can schedule it for generating the report immediately, once, daily, weekly, monthly or quarterly. If you choose to generate the report immediately, go to Step 10.

Step 9 Set the date and time for generating the report, in the Scheduling area.

Step 10 Enter a description to identify this job, in the Job Description field, of the Job Info area.

Step 11 Enter a valid e-mail ID in the Email field, of the Job Info area.

Step 12 Click Submit to generate the report or click Reset to modify the values that you have entered.


Interpreting End Host History Reports

Table 7-28 describes the entries in the History Report.

Table 7-28 End Host History Report Field Description 

Column
Description

User Name

Discovered username or the username that you have entered.

MAC Address

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

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

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

IP Address

IP address of the host.

Device

IP address of the device to which the host was connected.

Port

Port name in device to which the host was connected.

VLAN

VLAN name associated to the port

Port Connect

Date and time when the host or user was connected to the port. Port Connect is displayed in the format dd mon yyyy hh:mm:ss.

Port Disconnect

Date and time when the host or user was disconnected from the port. Port Disconnect is displayed in the format dd mon yyyy hh:mm:ss.


Printing End Host History Reports

You can print only 30,000 records at a time. If you want to print more than 30,000 records, do it in batches of 30,000.

Comma separated values are not accepted in the print range. For example, specifying the range as 10-40, 70-80 will not work. Specify the range as 10-40 to print from the 10th record to the 40th record. Repeat it for the 70-80 range.

Using Custom Reports

You can customize the layout and columns displayed in the reports to suit your needs.

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

You can create, view, edit, copy, and delete user-defined reports for end hosts and IP phones using the Custom Reports option.

This section contains:

Viewing List of Custom Reports

Creating Custom Reports

Editing Custom Reports

Copying Custom Reports

Deleting Custom 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 Manager User Tracking window.

To view the list of Custom reports:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager 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 Manager 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 7-29 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.

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.

To query using the Last Seen option, you must enter the date in the format yyyy/mm/dd hh:mm:ss. For more details on operator values and date formats, see Operator Values and Date Formats for Last Seen Column.


Step 8 Click View to launch the report and view details.

Step 9 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 Manager 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 Manager 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 Manager 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.


Using Custom Layouts

You can create or customize the columns displayed in Custom Reports using Custom Layouts option in the Reports tab of Campus Manager 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 Manager User Tracking window.

To view the list of Custom layouts:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager 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 Manager 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 Manager 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 Manager 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 Manager 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

Reports are archived after the completion of a Job. You can view and delete archived reports using the Archives option in the Reports tab of Campus Manager 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 archived reports using the Reports Archive option.

To view a list of archived reports:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Reports > Archives.

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


Viewing Reports

Campus Manager generates various reports. You can view them using:

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

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

The Archives options in the Reports tab of Campus Manager 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 Generator Option

You can schedule jobs for generating reports. To do so:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Report > Report Generator.

The Report Generator dialog box appears.

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

Step 4 Click Submit.

The report is generated.


Using the Report Jobs Option

You can view reports for the jobs that you have scheduled. To do so:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Reports > Reports Jobs.

The Report Jobs dialog box appears.

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


Using the Archives Option

Reports are archived after the completion of a Job. You can view a list of archived reports. To do so:


Step 1 Select Campus Manager  > User Tracking.

The Campus Manager User Tracking window appears.

Step 2 Select Reports >Archives.

The Archives dialog box appears.

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


Using the Device Center

You can view a report pertaining to a specific device. To do so:


Step 1 Go to the LMS Portal and select Device Troubleshooting > Device Center.

The Device Center window appears.

Step 2 Go to the Device Selector field and 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 are displayed under the Reports column in the Functions Available area.

Step 3 Click the report that you would like to view


Details of Individual Reports

Table 7-19 gives details of the columns in End Hosts Report - Standard Layout

Table 7-21 gives details of the columns in IP Phones Report - Standard Layout

Table 7-20 gives details of the columns in End Hosts Report - All Columns Layout

Table 7-22 gives details of the columns in the IP Phones Report - All Columns Layout.

Table 7-25 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 Manager 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.


Integrating CiscoWorks WLSE

The CiscoWorks Wireless LAN Solution Engine (WLSE) is a management component of Cisco Structured Wireless-Aware Network solution (SWAN) that provides a centralized, systems-level solution for managing the entire Cisco Aironet WLAN infrastructure.

Integrating WLSE with Campus Manager , provides you a single integrated view and support for wireless end hosts, in addition to the wired end hosts and Voice over IP (VoIP) phones that are already supported in User Tracking.

Viewing Reports on Wireless Clients

You can view the report on all wireless host entries using the Wireless End Hosts option in the Reports Generator dialog box.

To view report on wireless end hosts:


Step 1 Select Campus Manager  > User Tracking > Reports.

The Campus Manager User Tracking window appears.

Step 2 Select Report Generator.

The Report Generator dialog box appears.

Step 3 Select Wireless End Hosts from the Select Application list.

Step 4 Select All Wireless Entries, from the Select Report list.

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

Step 6 Enter a description to identify this job, in the Job Description field, of the Job Info area.

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

Step 8 Click Submit to generate the report or Reset to modify the values that you have entered.

If you click Submit, the Wireless LAN Report window appears.


Interpreting Reports on Wireless Clients

Table 7-30 displays details of the columns in Wireless LAN Report.

Table 7-30 Wireless LAN Report Field Description 

Column
Description

User Name

Discovered username or the username that you have entered.

Host Name

Name of end host.

MAC Address

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

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

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

Host Address

IP address of the end host.

AP Name

Name of the access point.

AP Address

IP address of the access point.

VLAN

VLAN to which the end host belongs.

SSID

Service Set Identifiers (SSIDs) on the access point

Client Role

Type of the role of a wireless client.

Client station, repeater access point, access point, bridge host, bridge, root bridge, and ethernet client are the different types of roles.

Dot1x Authenticated

State of the 802.1x authentication. Shows whether the device is 802.1x authenticated or not.

802.11 Associated

State of the 802.11 association. Shows whether the device is 802.1x associated or not.

Last Seen

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


User Tracking Command Line Interface

You can run User Tracking commands from the command line in Solaris and Windows 2000.

Enter ut -cli options -u username -p password.

The options can be one or more of those shown in Table 7-31.

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 when you run the cli command on a remote Campus Manager Server.

Table 7-31 User Tracking CLI Commands 

Option
Arguments
Function

-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 prompts you to enter your password.

-help

No keywords or arguments.

Prints the command line usage.

-ping

{enable | disable}

Enables the Ping Sweep option so that the ANI 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 ensures 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 it to complete.

-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

ANI Server device name or IP Address

Specifies the host name or IP address of the Campus Manager Server.

Use this argument when you need to run the cli command on a remote Campus Manager Server.

-port

ANI Server web port number

Specifies the web server port number of the ANI 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.

-switchportutilization

For complete details on this, see Exporting Switch Port Usage Report.

-switchPortreclaimreport

For complete details on this, see Exporting Switch Port Usage Report


For details on Importing User Tracking Data through CLI, see Importing User Tracking Data

For details on Lookup Analyzer Script, see Using Lookup Analyzer Utility

Exporting Switch Port Usage Report

Switch Port Utilization report lists switches whose utilization percentage falls in the specified range.

Switch Port Reclaim reports lists:

Access ports that are administratively up/down

AND

Access ports that were previously connected to an endhost but are unconnected atleast for a period of one day.

Switch port usage reports can be generated from the command prompt as follows:

Table 7-32 Switch Port Reports from the Command Prompt

Purpose
Command

Switch Port Utilization Report

To generate reports where the utilization is less than the specified percentage (for all devices managed by Campus)

NMSROOT/campus/bin ut -cli -switchportutilization lessthan 60 -devices all -export c:/sample -u username -p password

To generate reports where the utilization is less than the specified percentage (for specific devices)

NMSROOT/campus/bin ut -cli -switchportutilization lessthan 60 -devices 10.77.2.1,10.77.3.4,10.77.5.6 -export c:/sample -u username -p password

To generate reports where the utilization is greater than the specified percentage (for all devices managed by Campus)

NMSROOT/campus/bin ut -cli -switchportutilization greaterthan 60 -devices all -export c:/sample -u username -p password

To generate reports where the utilization is greater than the specified percentage (for specific devices)

NMSROOT/campus/bin ut -cli -switchportutilization greaterthan 60 -devices 10.77.2.1,10.77.3.4,10.77.5.6 -export c:/sample -u username -p password

To generate reports where the utilization falls between the specified range (for all devices managed by Campus)

NMSROOT/campus/bin ut -cli -switchportutilization between 10 60 -devices all -export c:/sample -u username -p password

To generate reports where the utilization falls between the specified range (for specific devices)

NMSROOT/campus/bin ut -cli -switchportutilization between 10 60 -devices 10.77.2.1,10.77.3.4,10.77.5.6 -export c:/sample -u username -p password

Switch Port Reclaim report

Generates reports for unused ports that are in up or down state.

To generate Switch Port Reclaim Unused Up report (for all devices managed by Campus)

NMSROOT/campus/bin ut -cli -switchPortReclaimReport type up days 2 -devices all -export c:/sample -u username -p password

To generate Switch Port Reclaim Unused Up report (for specific devices)

NMSROOT/campus/bin ut -cli -switchPortReclaimReport type up days 2 -devices 10.77.1.2,10.77.3.4 -export c:/sample -u username -p password

To generate Switch Port Reclaim Unused Down report (for all devices managed by Campus)

NMSROOT/campus/bin ut -cli -switchPortReclaimReport type down days 2 -devices all -export c:/sample -u username -p password

To generate Switch Port Reclaim Unused Down report (for specific devices)

NMSROOT/campus/bin ut -cli -switchPortReclaimReport type down days 2 -devices 10.77.1.2,10.77.3.4 -export c:/sample -u username -p password


where NMSROOT is the directory where you installed CiscoWorks.


Note The above commands can be run in a Solaris machine. To run the same commands in Windows, replace all forward slash (/) with reverse slash (\).


The report generated by the above options is saved as a file in the CSV format, at the specified location.

For more details on Switch Port Usage reports, see Understanding Switch Port Usage Reports

Importing User Tracking Data

You can import User Tracking data from previous releases of Campus Manager 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/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.


Using Lookup Analyzer Utility

Lookup Analyzer is an utility used to analyze the performance of DNS servers and provide the following information:

DNS Server Efficiency for each DNS Server

Overall Summary of DNS Servers

Namelookup related settings in ut.properties file

Issues found and recommendations to overcome them

For Solaris:

The utility file is NMSROOT/campus/bin/LookupAnalyzer.sh

If dir is the directory where the file is present, run the following command to run the utility:

dir# ./LookupAnalyzer

For Windows:

The utility file is NMSROOT\campus\bin\LookupAnalyzer.bat

If dir is the directory where the file is present, run the following command to run the utility:

dir> LookupAnalyzer

Example output of the Lookup Analyzer script:

Host IP: 172.20.123.74, DNS Server: 64.104.76.247, Time taken: 35, Status: FAILURE
Host IP: 172.20.123.74, DNS Server: WINS, Time taken: 22, Status: FAILURE
Host IP: 10.77.209.254, DNS Server: 64.104.128.248, Time taken: 18, Status: FAILURE
..
..
DNS Server   : 64.104.128.248
Success Count: 12
Failure Count: 76
Failure %    : 86 %
Total Time   : 1 secs 561 ms
Min Time     : 0 ms
Max Time     : 52 ms
Avg Time     : 17 ms
Server Efficiency(successCount/totalTime): 7.0
--------------------------------
DNS Server   : 64.104.76.247
Success Count: 0
Failure Count: 76
Failure %    : 100 %
Total Time   : 2 secs 729 ms
Min Time     : 0 ms
Max Time     : 61 ms
Avg Time     : 35 ms
Server Efficiency(successCount/totalTime): 0.0
--------------------------------
DNS Server   : WINS
Success Count: 0
Failure Count: 76
Failure %    : 100 %
Total Time   : 750 ms
Min Time     : 0 ms
Max Time     : 23 ms
Avg Time     : 9 ms
Server Efficiency(successCount/totalTime): 0.0
--------------------------------
Overall Summary
-----------------
Success Count: 12
Failure Count: 76
Failure %    : 86 %
-----------------
Current Namelookup Related Settings
---------------------------------
UTMajorUseDNSSeperateThread: false
UT.nameResolution: both
UT.nameResolution.threadCount: 1
UT.nameResolution.winsTimeout: 2000
UT.nameResolution.threadThresholdPercentage: 10
UT.nameResolution.dnsTimeout: 2000
UTMajorUseDNSCache: false
nameserver.usednsForUT: true
DB.dsn: ani
---------------------------------
ISSUES/RECOMMENDATIONS
-----------------------
Issue #1: Failure Percent is greater than 20%
Recommendation: Check all DNS/WINS entries and ensure proper hostnames are configured

Issue #2: DNS reverse lookup is NOT done as separate process
Recommendation: Enable UTMajorUseDNSSeperateThread=true in ut.properties

Issue #3: Name Resolution DNS server order is not optimal
Recommendation: Change dns server order as 64.104.128.248=7.0, 64.104.76.247=0.0, 
WINS=0.0, 

Other Recommendations:
* If hostnames in your network are less likely to change often, set 
UTMajorUseDNSCache=true
* If reverse lookup failure % is more, try increasing UT.nameResolution.winsTimeout, 
UT.nameResolution.dnsTimeout and UT.nameResolution.threadThresholdPercentage
* Optimal timeout values are: UT.nameResolution.winsTimeout=0, 
UT.nameResolution.dnsTimeout=48

The script can also be run by setting properties in the ut.properties file. For details, see Configuring User Tracking Properties from the Backend

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.

UTLite sends traps to Campus Manager whenever a user logs in or logs out. UTLite traps are processed by Campus Manager at the rate of 150 traps per second, with a default buffer size of 76800.

If you need a higher trap processing rate, say 300 traps per second, increase the buffer size to 102400.

To increase the buffer size:


Step 1 Enter pdterm UTLITE at the command line to stop the UTLite process.

Step 2 Open utliteuhic.properties located at NMSROOT\campus\lib\classpath\com\cisco\nm\cm\ut\uhic\utlite\properties\

Step 3 Set Socket.portbuffersize=102400

Step 4 Enter pdexec UTLITE at the command line to start the UTLite process.



Caution Increasing the buffer size beyond 102400 results in performance degradation of UTLite.

The UTLite script is supported on these platforms:

Windows NT

Windows 2000

Windows XP

Windows 2003

Novell Directory Services (NDS)

The UTLite script is not supported on these UNIX hosts:

Solaris

HP-UX

AIX

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:

NMSROOT\campus\bin\UTLite33.exe

NMSROOT\campus\bin\UTLiteNT.bat

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

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 the User Tracking > Administration > Acquisition > Acquisition Settings page.

For more details, see Modifying Acquisition Settings.

Step 3 Edit the 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 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. To install the 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 the User Tracking > Administration > 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. To install the script:


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 > Administration > Acquisition > Acquisition Settings page.

For more details, see Modifying Acquisition Settings.

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. To uninstall the script:


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. To uninstall the script:


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. To uninstall the script:


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

Using Search Patterns

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.

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. The default search criteria is Searching by Host.

Definitions

Table 7-33 explains certain terms and definitions used in User Tracking Utility.

Table 7-33 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 7-34 lists the minimum system requirements for UTU.

Table 7-34 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 5.0

Network Connectivity

Campus Manager 5.0 must be running and accessible through the network


Downloading UTU 1.1.1

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

To download UTU:


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 HTTP 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 7-3.

Figure 7-3 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 CiscoWorks 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 7-4.

Figure 7-4 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 as 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 7-35 describes the search criteria in UTU 1.1.1.

Table 7-35 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 7-5.

Figure 7-5 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 7-6.

Figure 7-6 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 7-36.

Table 7-36 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 Go to the Windows taskbar and 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.

Re-installing UTU

You must not 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 check for an existing installation of UTU:


Step 1 Right-click the taskbar of the machine.

Step 2 Select Toolbars.

If the User Search Band option is displayed, UTU is already installed on the system.

You must first uninstall the current installation of UTU, and then start the new installation


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 displays a report on the reasons why User Tracking failed to discover end hosts on specific ports.

In many cases, User Tracking may not perform as expected. This may be because of problems in other Campus Manager applications. For instance Campus Manager Server may have devices that are not discovered or inadequate VLAN discovery in Topology Services.

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 that you can use to analyze 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 7-37 to troubleshoot the User Tracking application.

Table 7-37 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, page 5-1.

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 Major Acquisition.

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 Major Acquisition 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 Major Acquisition.

1. Run device discovery.

2. Run 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, page 5-9.

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

Table 7-38 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.