-
User Guide for Campus Manager 5.2 (with LMS 3.2)
-
Notices
-
Preface
-
Chapter 1 About Campus Manager
-
Chapter 2 Whats New in Campus Manager
-
Chapter 3 Getting Started with Campus Manager
-
Chapter 4 Integrating Campus Manager With CiscoWorks
-
Chapter 5 Administering Campus Manager
-
Chapter 6 Generating Reports
-
Chapter 7 Tracking Users
-
Chapter 8 Discrepancies and Best Practices Deviations
-
Chapter 9 Using Topology Services
-
Chapter 10 Managing VLANs and VTP
-
Chapter 11 Managing Network Spanning Trees
-
Chapter 12 Support for IPv6
-
Chapter 13 Data Extraction Engine
-
Chapter 14 Virtual Network Manager
-
Chapter 15 Troubleshooting and FAQs
-
Index
-
Table Of Contents
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
Configuring Subnet Acquisition
Configuring Trunk for End Host Discovery
Specifying Domain Name Display
Importing Information on End Host Users
Viewing Dynamic Updates Process Status
Enabling SNMP Traps on Switch Ports
SNMP MAC Notification Listener
Configuring SNMP Trap Listener
Configuring Dynamic User Tracking
Debugging Options for User Tracking Server
Debugging Options for User Tracking Reports
Understanding User Tracking Reports
Operator Values and Date Formats for Last Seen Column
Exporting and Printing Reports
Interpreting Duplicate Reports
Interpreting Active End Hosts Report
Interpreting IP Phones Reports
Understanding Switch Port Usage Reports
Interpreting Switch Port Capacity Report
Interpreting Switch Port Usage Reports
Interpreting Summary Report for Switch Ports
Viewing History Reports for Switch Port Utilization
Interpreting History Reports for Switch Ports
History Reports Based on Filters
Interpreting End Host History Reports
Viewing List of Custom Reports
Viewing List of Custom Layouts
Viewing Reports on Wireless Clients
Interpreting Reports on Wireless Clients
User Tracking Command Line Interface
Exporting Switch Port Usage Report
Installing UTLite Script on Active Directory
Installing UTLite Script on Windows
Installing UTLite Script on NDS
Uninstalling UTLite Scripts From Windows
Uninstalling UTLite Scripts From Active Directory
Uninstalling UTLite Scripts From NDS
Hardware and Software Requirements for UTU 1.1.1
User Tracking Debugger Utility
Understanding Debugger Utility
Tracking Users
User Tracking application of Campus Manager allows you to track end stations. This chapter contains the following sections:
•
Using User Tracking Administration
•
•
•
•
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 and 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 such as 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:
•
•
•
•
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.
This topic covers:
•
Using User Tracking
You can use User Tracking to:
•
•
•
•
•
•
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.
•
For example, you can design a layout that displays only the MAC addresses of hosts on your network.
•
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.
•
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
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.2.
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:
•
•
•
•
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
This includes enabling Cisco Discovery Protocol (CDP), Integrated Local Management Interface (ILMI) and SNMP.
Step 2
For more details on Data Collection, see Viewing Summary of Data Collection Settings.
Using User Tracking Administration
You can perform the following administrative tasks using User Tracking Administration:
•
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
•
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
•
You can configure Campus Manager to perform Ping Sweep on selected subnets, during Acquisition.
For more details, see Modifying Ping Sweep Options
•
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
•
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
•
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
•
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
•
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
•
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
•
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
•
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
The Campus Manager User Tracking window appears.
Step 2
The acquisition information appears.
Interpreting Acquisition Information
Acquisition Information window displays the fields described in Table 7-1.
Configuring User Tracking Acquisition Actions
You can trigger the following acquisitions from this page:
•
•
•
To configure the required acquisition:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Acquisition Actions dialog box appears.
Step 3
You do not have to specify any details for the IP Phones option.
Step 4
Using User and Host Acquisition
You can modify the Acquisition settings and Acquisition schedule using the User and Host Acquisition option in the Administration tab of the Campus User Tracking window.
This section contains:
•
•
•
•
•
Modifying Acquisition Settings
You can modify User Tracking Acquisition settings using the Acquisition Settings option of the Administration tab in Campus User Tracking window.
This section contains:
•
•
•
•
Modifying Acquisition Settings from UI
To modify acquisition settings:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Acquisition Settings dialog box appears.
Step 3
Table 7-3 Acquisition Settings Field Description
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.
Enable User Tracking on Access Points
Enables User Tracking on Access Points
This is enabled by default which allows UT Major Acquisition process to collect Access point information. However, WlseUHIC cannot collect Wlse related end host information.
If disabled, it precludes Access point acquisition. However, WlseUHIC collects Wlse related end host information.
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:
•
•
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:
•
Number of parallel threads allowed for name resolution. The default value is 1. Maximum number of threads allowed is 12.
•
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.
Rogue MAC Detection
Enable notification when Rogue MACs are detected in the network.
Campus Manager sends e-mails to the specified addresses, when unauthorized end hosts are detected in the network.
Specify the E-mail IDs to be notified when Rogue MACs are detected in the network.
You can enter multiple E-mail IDs separated by commas. This field is enabled only when you check the Rogue MAC Detection field.
Define Rogue MACs
Specify the list of Rogue MACs in the screen that is launched.
For details, see Configuring Rogue MAC List.
New MAC Detection
Enable notification when new MACs are detected in the network.
Campus Manager sends e-mails to the specified addresses, when new end hosts are detected in the network.
Specify the E-mail IDs to be notified when new end hosts are detected in the network.
You can enter multiple E-mail IDs separated by commas. This field is enabled only when you check the New MAC Detection field.
Step 4
Step 5
UT Behaviour in DHCP Environment for Missing IP address
Selecting the 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 if it is excluded from DCR. 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:
•
•
•
•
•
Note
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
For the above list of properties:
•
•
•
•
The usage scenario for the above lists is as follows:
•
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.
•
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.
•
a.
b.
c.
d.
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
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:
•
•
•
•
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:
•
•
•
•
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
Configuring Rogue MAC List
MAC Addresses that are not authorized to exist in your network are termed as Rogue MAC addresses.
When you enable the Rogue MAC notification feature, you need to define the list of MAC addresses that are to be classified as unauthorized addresses in the network.
You can also import MAC addresses to Acceptable OUI either from a file or directly from UT.
If you import the MAC Addresses from a file or directly from UT, the MAC addresses in the file are converted to OUIs before you add them to the Acceptable OUI list.
To do so:
Step 1
The User Tracking Acquisition settings window appears.
Step 2
The Rogue MAC Configuration window appears. The lists displayed in the window are:
–
–
Step 3
The Add MAC/OUI window appears.
The Organizationally Unique Identifier (OUI) is a 24-bit number. It is used as an identifier to uniquely identify the vendor, manufacturer, or other worldwide organization.
An OUI reserves a block of each type of derivative identifier, such as MAC addresses, group addresses, Subnetwork Access Protocol protocol identifiers, and so on. It is used to identify an network interface controller (NIC), network protocol, or MAC addresses for Ethernet.
In case of MAC addresses, OUI is combined with a 24-bit number to form the address. The first three octets of the address are the OUI.
The Add MAC/OUI page is as explained in Table 7-7:
Table 7-7 Populating the MAC/OUI list
Select Mode
Provides the following options to add MAC addresses to MAC/OUI List:
•
•
•
Add MAC/OUI
Enter the MAC Address or OUI in the text box provided.
The values should be separated by spaces, tabs, or commas. You can also enter values on separate lines.
The address can have only hexa decimal numbers separated by hyphen.
Example:
00-c0-1d-99-06-b6
OUI List
Displays predefined values in Campus Manager. You can select values from the list, to add to the Rogue OUI or Acceptable OUI list.
To add more values to the list, add them to the Property file:
NMSROOT/campus/etc/cwsi/OUI.properties
where NMSROOT is the directory where you installed CiscoWorks.
To get the latest OUIs listed by IEEE, see http://standards.ieee.org/regauth/oui/index.shtml
Step 4
•
a.
b.
The MAC or OUIs that you enter in the ADD MAC or in the OUI textbox will be added to the list that you selected.
•
a.
b.
The MACs are converted to OUIs before you add them to the Acceptable MAC/OUI list.
•
Click the Import to Acceptable OUI list. The MACs are converted to OUIs prior to adding them to the Acceptable MAC/OUI List.
It is mandatory that the file that is imported to Acceptable MAC/OUI list must include the header - MAC Address followed by MAC Address entries.
For example: In the example, the file to be imported includes a MAC Address column with MAC Address entries.
MAC Address
MAC 1
MAC 2
MAC 3
The newly added values are reflected in the Rogue MAC Configuration screen.
Step 5
When you check this, Campus Manager treats any new MAC address coming into the network as Rogue MAC. This is if it is not defined in the Acceptable MAC list.
Step 6
•
Saves the settings to the server. They come into effect in the next UT Major Acquisition cycle.
–
–
•
Deletes entries
•
Cancels changes and closes the window.
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
The Campus Manager User Tracking window appears.
Step 2
The Acquisition Schedule dialog box appears.
Step 3
Step 4
•
•
•
Step 5
Step 6
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.
Before collecting information from a device, the subnets connected to the device are pinged. This serves as a connectivity check, as well as loads the ARP table of the layer 3 device with the latest information. After pinging, acquisition process starts collecting end host information from the device.
You can modify Ping Sweep option from the Admin tab in Campus User Tracking window.
To modify Ping Sweep options:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Ping Sweep dialog box appears.
Step 3
•
•
•
When you choose Exclude subnets from Ping Sweep, select the subnets that you want to exclude 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
Wait Interval is the time duration between pinging subnets. The interval ensures that the network is not flooded with ping packets.
For example, assume that you have included 4 subnets for pinging, and set the wait interval to 10 seconds.
If Subnets 1 and 2 are connected to Device 1, and Subnets 3 and 4 are connected to Device 2, then 10 seconds lapse between pinging Subnets 1 and 2. After pinging both the subnets, acquisition starts on Device 1. Same happens with Device 2.
Step 5
User Tracking does not perform Ping Sweep on large subnets.
For more details, see Notes on Ping Sweep Option.
Notes on 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:
•
•
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
The Campus User Tracking window appears.
Step 2
The Configure Subnet Acquisition dialog box appears.
Step 3
•
All the subnets are included for User Tracking Major Acquisition. If you select this option do not perform steps 4 and 5.
Or
•
The action depends on the Filter value.
Step 4
•
All subnets added to the Selected Subnets list are included for User Tracking acquisition.
Or
•
All subnets added to the Selected Subnets list are excluded for User Tracking acquisition.
Step 5
Step 6
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
The Campus Manager User Tracking window appears.
Step 2
The Delete Interval dialog box appears.
Step 3
Step 4
•
If you select this step do not perform Step 5.
Or
•
If you select this option, Campus Manager will delete records older than the specified interval, after every UT Major Acquisition.
Step 5
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:
•
•
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.
To configure trunk ports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The corresponding page appears.
Step 3
–
–
–
Step 4
Step 5
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
Step 7
The selected ports are displayed under the Selected Trunks list.
Step 8
•
Or
•
Step 9
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
The Campus Manager User Tracking window appears.
Step 2
The Report Settings dialog box appears.
Step 3
•
•
You must specify the period in days, or weeks, or months for which you want to retain the report archives or jobs.
Step 4
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
The Campus Manager User Tracking window appears.
Step 2
The Report Settings dialog box appears.
Step 3
•
•
•
If you want to hide the specified domain name suffix, enter the domain name suffix in the field.
Step 4
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
The Campus Manager User Tracking window appears.
Step 2
The End Host Table Import dialog box appears.
Step 3
Step 4
Note
For example:
MAC1 Peter Finance department
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 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:
•
Contains information from UT Major Acquisition and the recently added end-hosts.
•
Contains information from UT Major Acquisition and the recently disconnected end-hosts/end-hosts that have moved between ports or VLANs.
•
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.
See Figure 7-1for an overview of Dynamic Updates.
Figure 7-1 Overview of Dynamic Updates
To enable the Dynamic Updates feature:
•
•
•
•
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/en/US/docs/ios/12_2/ip/configuration/guide/1cfdhcp.html
•
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
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:
•
•
If the traps are from valid sources:
•
•
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 i n Dynamic Updates
When an end-host is connected to your network, the following happens in the background. See Figure 7-2 for details:
1.
2.
3.
4.
5.
–
–
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
The Campus Manager User Tracking window appears.
Step 2
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
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
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.
Even if the device is managed with SNMPv3, Campus Manager processes only SNMPv1/SNMPv2 traps.
You can configure the ports Through Campus Manager Interface or Through Command Line Interface (CLI).
Note
Through Campus Manager Interface
Prerequisites to enable MAC Notification on switches through Campus Manger interface:
•
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.
•
Note
To enable MAC notification in switches:
Step 1
Step 2
The Configure Trap on Devices dialog box appears.
Step 3
Step 4
Step 5
The Configure MAC-Notification Trap on Ports dialog box appears. Table 7-9 describes the entries in the Configure MAC-Notification Trap on Ports dialog box.
Table 7-9 Configure MAC-Notification Trap on Ports Field Description
Add Campus Manager Server as Trap Receiver
Check the check box to configure devices, to send SNMP traps to Campus Manager.
To configure Campus Manager to listen to traps sent from devices, see Configuring SNMP Trap Listener.
Trap Community
Set a community string for the SNMP traps sent by devices. This property is enabled only when Campus Manager is the Primary receiver for SNMP traps. This string is added to the list of valid strings in the Dynamic User Tracking Configuration screen.
Set as Dynamic User Tracking Default
Check the check box to make this community string as the default for future configurations, if Campus Manager is the Primary Trap receiver.
Filter
Allows you to 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
Step 7
An Information window appears.
Step 8
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-10 lists the commands that need to be run on each device.
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.
•
•
Note
To select the MAC notification listener, see the following sections:
•
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
Step 2
The Trap Listener Configuration dialog box appears.
Step 3
This makes Campus Manager as the primary listener for receiving SNMP traps from devices.
OR
Check Listen traps from DFM/HPOV to receive the traps through these applications.
In this case, DFM or HPOV act as the primary listener for SNMP traps from devices. They forward it to Campus Manager which acts as the secondary listener for traps.
If both options are enabled, Campus Manager can receive traps directly from devices, from HPOV and from DFM.
Step 4
The default trap listener port number of the Campus Manager server is 1431.
Step 5
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 :
•
•
The supported versions of HPOV are HPOV 7.50, HPOV 7.51 and HPOV 7.53.
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 DVD in the CiscoWorks LAN Management Solution 3.2.
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.7, for more details on the integration utility.
Note
Install Trap Adapter for HPOV
Campus supports Trap Adapter for OpenView on Windows and Solaris operating systems.
To install the adapter on Windows:
Step 1
Step 2
Step 3
Step 4
The Trap Adapter gets attached to OpenView process and starts sending traps to the Campus Manager server.
To install the adapter on Solaris:
Step 1
Step 2
Step 3
Step 4
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:
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
Step 1
The Configurations page appears.
Step 2
The Notification Services page appears.
Step 3
Step 4
The trapd.conf file is modified and the DFMServer process is restarted.
Note
From the DFM Server
Step 1
Step 2
Step 3
Step 4
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
Configuring Dynamic User Tracking
You can configure certain properties in Dynamic User Tracking to enhance the security of the system. These properties make the server receive traps only from specified devices and with specified community strings.
To configure properties for filtering SNMP Traps:
Step 1
Step 2
The Dynamic User Tracking Configuration page appears.
Step 3
Campus Manager validates the community string in SNMP traps, with the values you have set. You can add community strings only after checking this check-box.
•
•
Step 4
You can add the community strings one at a time. You can use the Delete button to remove the extra or erroneous strings.
The default Trap community string that you might have added in the Device Trap configuration screen is also listed here.
Step 5
Campus Manager validates the source IP Address of the trap. You can add the list of IP Addresses only after checking this check-box.
Step 6
You can use the Delete button to delete extra or erroneous entries.
Step 7
To revert to the default values, click Reset.
You can use any one of the options to filter SNMP traps.
For example:
If you set
Validate SNMP Community = true (by checking the check-box)Community String = private, testValidate Trap Source =falsethen traps from all sources with community string private or test will be processed by Campus Manager.
If you set
Validate SNMP Community =trueCommunity String = private, testValidate Trap Source =trueValid IP Addresses = 10.77.210.211, 10.77.210.212then traps from the listed IP addresses, with the community string private or test will be processed by Campus Manager. In this case, Campus Manager first validates the community string and if it matches, validates the source address.
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:
•
You can debug events related to all User Tracking server side processes. For details on this, see Debugging Options for User Tracking Server.
•
You can set the debugging options required for Dynamic Updates. For details on this, see Debugging Dynamic Updates.
•
You can debug events related to User Tracking client side activities. For details on this, see Debugging Options for User Tracking Reports.
•
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:
Debugging Options for User Tracking Server
To debug events related to all User Tracking server side processes:
Step 1
The debugging page appears. See Table 7-12 for a description of the fields:
Table 7-12 User Tracking Server Side Debugging Options
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
Device IP(s)
IP addresses of devices for which you need to log debugging messages.
You can enter multiple IP addresses, separated by commas.
This field is enabled only when the Device Level Debugging option is enabled.
Step 2
Selecting User Tracking Server Side Debug Modules
Table 7-13 describes the debug modules available for User Tracking Server in Campus Manager.
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
Or
Go to Campus Manager > Administration > User Tracking > Administration > Debugging Options > Dynamic User Tracking.
The debugging page appears.
Step 2
Step 3
The framework modules appear in the Module Name column. The framework modules depend on the service that you select.
Step 4
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
•
•
•
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
Dynamic User Tracking modules available for debugging are explained in Table 7-14:
Note
Debugging Options for User Tracking Reports
You can debug events related to User Tracking client side activities as follows:
Step 1
Step 2
•
Only informational messages are recorded in the log file. This is the default option.
•
Messages related to fatal errors are recorded in the log file.
•
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
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:
•
•
•
Each process monitors 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
The debugging page appears.
Step 2
•
•
•
The error conditions related to that process is listed under the Error Details section.
Step 3
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
•
•
•
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.x, 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
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
The Quick Report dialog box appears.
Step 2
Table 7-15 Viewing Quick Reports
Select a type
Select the type of report that you wish to view.
The two types of reports that are available are:
•
•
Column
Select a query expression based on which you want to generate the report.
To view a list of valid query expressions, click the drop-down arrow.
The information on the other query expressions are available in the corresponding report.
Operator
Logical operator for the query expression.
To view a list of valid operators click the drop-down arrow.
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.
In the pattern field to search the pattern for MAC Address Column, you can use the following separators: dot (.) or colon (:). You can also search the pattern for MAC Address without any separator.
For example: String for pattern FF:FF:FF:FF:FF:FF can be replaced with continuous string FFFFFFFFFFFF.
For details on date formats and operator values, see Operator Values and Date Formats for Last Seen Column.
Step 3
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.
Exporting and Printing Reports
Campus Manager allows you to export and print reports. For details see,
Exporting Reports
To export a report:
Step 1
The Exporting Report dialog box appears.
Step 2
End Host Report and End Host History Reports can be exported only to CSV format.
Step 3
Step 4
The report is exported.
Printing Reports
To print a report:
Step 1
The Printing Report dialog box appears.
Step 2
Step 3
The report is printed.
Restrictions on Printing Reports
•
•
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
The Campus Manager User Tracking window appears.
Step 2
The Report Jobs dialog box appears. See Table 7-17
Note for Custom Reports
Custom reports are generated by evaluating a query on a group of devices.
They do not launch, if the group has been deleted or if the underlying query does not return any device.
Viewing Job Details
To view the details of a selected job:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
Step 4
The report is launched. You can also launch the report by clicking on the Job ID.
Stopping Jobs
To stop a scheduled job:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
Step 4
Deleting Jobs
To delete a job:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
Step 4
Using Report Generator
The Report Generator in User Tracking allows you to view System-defined reports and Custom reports. You can also schedule to generate these reports immediately, once, daily, weekly, monthly or quarterly.
You can generate the following reports using Report Generator:
To use the report generator:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
The report is generated.
To modify the settings, click Reset.
Viewing Duplicates Report
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,
•
•
You need to take appropriate action 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.
•
•
•
•
Note
To view reports on duplicates:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
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.
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
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
The report is generated.
To modify the settings, click Reset.
Interpreting End Host Reports
This section contains the following topics:
•
•
•
•
•
Launching CiscoWorks Assistant from End Host Report
To launch CiscoWorks Assistant from End Host Reports:
Step 1
The Host center page is launched for that endhost.
Step 2
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:
•
•
•
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:
•
•
•
•
•
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:
•
•
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.
In the pattern field to search the pattern for MAC Address Column, you can use the following separators: dot (.) or colon (:). You can also search the pattern for MAC Address without any separators.
For example: String for pattern FF:FF:FF:FF:FF:FF can be replaced with continuous string FFFFFFFFFFFF.
Table 7-19 displays details of the columns in End Hosts Report—Standard Layout.
Table 7-20 displays details of the columns in End Hosts Report—All Columns Layout.
Interpreting Active End Hosts Report
The End hosts that are currently connected to the network are termed as Active End Hosts.
Active end hosts reports can be launched from the User Tracking Summary portlet in the Campus Manager view. For more details on Campus View and the portlets in it, see User Guide for LMS Portal 1.2.
Filters in Active End Hosts Reports
Filters in the report operate on the selected column and fetch records containing the user input value.
The pattern field to search pattern for MAC Address Column is enhanced to include the following separators: dot (.) or colon (:). You can also search the pattern for MAC Address without any separators.
For example: String for pattern FF:FF:FF:FF:FF:FF can be replaced with continuous string FFFFFFFFFFFF.
Active End Hosts report can be displayed in two formats:
•
•
Table 7-21 displays details of the columns in End Hosts Report—Standard Layout.
Table 7-22 displays details of the columns in End Hosts Report—All Columns Layout.
•
Viewing IP Phones Reports
You can view a report on all IP phones in the network using the IP Phones option of the Report Generator dialog box.
To view a report on IP phones:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
The report is generated.
Interpreting IP Phones Reports
Filters in IP Phone Reports
Filters in the report operate on the selected column and fetch records containing the user input value.
The pattern field to search pattern for MAC Address Column is enhanced to include the following separators: dot (.) or colon (:). You can also search the pattern for MAC Address without any separators.
For example: String for pattern FF:FF:FF:FF:FF:FF can be replaced with continuous string FFFFFFFFFFFF.
Table 7-23 gives details of the columns in IP Phones Report—Standard Layout.
Table 7-24 gives details of the columns in the IP Phones Report—All Columns Layout.
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.
Viewing MAC Reports
You can generate reports to get information on new end-hosts, unauthorized endhosts, and idle end hosts in the network. To do that:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
•
MAC Addresses that are inactive for the specified number of days.
•
MAC Addresses that are newly added to your network.
•
MAC Addresses that are not authorized to exist in your network.
Step 5
•
The Days drop-down list is editable. It allows you to specify a value, other than the ones listed. The maximum number of days that can be specified is 999.
Or
•
For example, select 30 from the Date Since drop down list, to generate reports for the new, dormant, or rogue MACs found in the network for the past 30 days.
Note
If the purge policy is set to 20 days, and you generate the report for 30 days, the Dormant MAC report will not contain any data.Step 6
•
•
•
•
•
•
If you have selected Immediate report, go to Step 10.
Step 7
Step 8
Step 9
Step 10
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.
Click Reset, to bring back the default settings.
Interpreting MAC Reports
The columns in New MAC, Dormant MAC and Rogue MAC reports are explained in Table 7-25.
New MAC Report
To mark a MAC as a Rogue MAC
Step 1
Step 2
After the selected MAC is marked as Rogue, you cannot make any changes to the MAC selection as the checkbox used to select the MAC is disabled.
Rogue MAC Report
To mark a MAC as a Acceptable MAC
Step 1
Step 2
After the selected MAC is marked as Non-Rogue, the MAC is deleted from the Rogue MAC Report page.
Understanding Switch Port Usage Reports
You can generate the following switch port reports using Campus Manager , based on the status of the switch ports.
•
•
•
You can use the Advanced Search feature to select the devices for which you want to generate reports. For more details on performing advanced search, see Using Advanced Search.
For a detailed description of the features in Device Selector, see User Guide for Common Services 3.3
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:
•
•
Report on Recently Down Ports
Campus Manager generates report for recently down ports as follows:
•
•
If the ports are still in an Unconnected state when the next UT Major Acquisition cycle runs, they are classified as Unused Up or Unused Down ports. These ports are further moved to the Reclaim Unused Up Ports report or Reclaim Unused Down Ports report.
Reclaim Unused Down Ports Report
Campus Manager queries both link and access ports to generate the Unused Down report. It uses ports:
•
and
•
You can generate reports on ports which have been in Unused Down state for a specified interval of time.
Reclaim Unused Up Ports Report
Campus Manager queries both link and access ports to generate the Unused Up report. It uses ports:
•
and
•
You can generate reports on ports that have been in Unused Up state for a specified interval of time.
The data provided by the reports will be lost if you reinitialize the database. For information on reinitializing the database, see Re-initializing the Database.
Note
Switch Port Summary Report
Switch Port Summary report gives the number of Connected, Free, and Free down ports in each switch.
•
•
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 Capacity Report
The Switch Port Capacity 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
•
•
•
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.
2.
3.
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
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
•
•
•
•
•
The Report Generator page appears.
•
•
•
Step 5
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.
Step 6
•
Or
•
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 7
Step 8
•
•
•
•
•
•
Step 9
Step 10
Step 11
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-26 describes the device attributes available for defining rules.
Operator
The operator used in forming a rule. The following operators are available:
•
•
In addition to the above, the following operators are also available for the variable IPAddress:
•
•
•
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:
•
•
•
Interpreting Switch Port Capacity Report
Table 7-27 describes the columns of Switch Port Capacity Report:
For more details on this, see Switch Port Capacity Report
Interpreting Switch Port Usage Reports
The following reports have information as described in Table 7-28:
•
•
•
•
Switch Port Capacity Report
This report has three sections:
•
The ports that are administratively UP and are connected to a device will be listed here.
•
The Ports that are administratively UP but are not connected to a device will be listed here.
•
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-29.
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
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
Step 2
Step 3
Step 4
Step 5
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
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
Step 8
Step 9
Step 10
Interpreting History Reports for Switch Ports
The Report lists each switch with its ports and the usage time in hours.
Table 7-30 describes the entries in the History Report for switch ports.
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
To generate the reports on the log in and log out:
Step 1
Step 2
Step 3
Step 4
The filter can be any one of the following:
•
•
•
•
Step 5
Step 6
Apart from specific values, blank space and * can also be given.
Step 7
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
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 12.
Step 9
Step 10
Step 11
Step 12
Interpreting End Host History Reports
Table 7-31 describes the entries in the History Report.
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
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
The Campus Manager User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Creating Custom Reports
You can create Custom reports by clicking Create in the Available Custom Reports dialog box.
To create Custom reports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
You can use the Custom Reports wizard to customize and create reports. The Type selection page appears.
Step 4
•
•
Step 5
The Group Selection page appears.
Step 6
Step 7
The Properties and Query Expression page appears. See Table 7-32.
Table 7-32 Properties and Query Pane Field Description
Name
Enter a name for the query you are going to create.
Description
Enter a description for the query you are going to create.
Select a type
•
•
Select the type of query.
•
In the Query Expression area, select the radio button to search using any of the options or all the options that you select.
Select the options for the query, from:
–
–
–
For example: String for pattern FF:FF:FF:FF:FF:FF can be replaced with continuous string FFFFFFFFFFFF.
•
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
Step 9
The Summary page appears. The Custom Report Summary pane displays a summary of the values and options you have selected for the query to generate the report.
Editing Custom Reports
You can edit custom reports by clicking Edit in the Available Custom Reports dialog box.
To edit Custom reports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
You can use the Custom Reports wizard to modify group, report properties, and query expressions.
Copying Custom Reports
You can copy Custom reports by clicking Copy in the Available Custom Reports dialog box.
To copy Custom reports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
You can use the Custom Reports wizard to modify the Name of the report, group, report properties, and query expressions.
Deleting Custom Reports
You can delete Custom reports by selecting a report from the Available Custom Reports dialog box and clicking Delete.
To delete Custom reports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Reports dialog box appears with the list of Available Reports.
Step 3
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
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
The Campus Manager User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Note
Creating Custom Layouts
You can create Custom layouts by clicking Create in the Available Custom Layouts dialog box.
To create Custom layouts:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Editing Custom Layouts
You can edit Custom layouts by clicking Edit in the Available Custom Layouts dialog box.
To edit Custom reports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Note
Copying Custom Layouts
You can copy Custom layouts by clicking Copy in the Available Custom Layouts dialog box.
To copy Custom layouts:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Deleting Custom Layouts
You can delete Custom layouts by selecting a layout from the Available Custom Layouts dialog box and clicking Delete. To delete Custom layouts:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Custom Layouts dialog box appears with the list of Available Layouts.
Step 3
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
You can view a list of archived reports using the Reports Archive option. To view a list of archived reports:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Archives dialog box appears with the list of archived reports.
Viewing Reports
Campus Manager generates various reports. You can view them using:
•
•
•
•
Using the Report Generator Option
You can schedule jobs for generating reports. To do so:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
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
The Campus Manager User Tracking window appears.
Step 2
The Report Jobs dialog box appears.
Step 3
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
The Campus Manager User Tracking window appears.
Step 2
The Archives dialog box appears.
Step 3
Using the Device Center
You can view a report pertaining to a specific device. To do so:
Step 1
The Device Center window appears.
Step 2
•
Or
•
The Campus Manager reports available for the selected device are displayed under the Reports column in the Functions Available area.
Step 3
Details of Individual Reports
•
•
•
•
•
Deleting Archived Reports
You can delete an archived report by selecting the report from the list of archived reports and clicking Delete.
To delete an archived report:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Archives dialog box appears with the list of archived reports.
Step 3
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 User Tracking Wireless report for the devices managed by Campus with WLSE integrated. The report is viewed using the Wireless End Hosts option in the Reports Generator dialog box.
To view report on wireless end hosts:
Step 1
The Campus Manager User Tracking window appears.
Step 2
The Report Generator dialog box appears.
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
If you click Submit, the Wireless LAN Report window appears.
Interpreting Reports on Wireless Clients
Table 7-33 displays details of the columns in Wireless LAN Report.
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-34.
•
•
Table 7-34 User Tracking CLI Commands
-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:
•
To configure the value, you must use the
arp time-out interface configuration command on devices running Cisco IOS.•
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.
-importMACToAcceptableOUI
filename
Imports MACs and converts them to OUI and adds the MACs to the Acceptable OUI List.
For example:
cd NMSROOT/bin ut -cli -importMACToAcceptableOUI filename -u username -p password
-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.
-wireless
No keywords or arguments.
Displays detailed information on Wireless clients connected to the network.
If you enter this option along with the export option, data can be exported to a text file.
For example:
NMSROOT/campus/bin ut -cli -wireless -export c:/sample -u username -p password
-switchPortCapacity
For complete details on this, see Exporting Switch Port Usage Report.
-switchPortreclaimreport
For complete details on this, see Exporting Switch Port Usage Report
-switchPortSummary
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 Capacity report lists switches whose utilization percentage falls in the specified range.
Switch Port Reclaim reports lists:
•
and
•
Switch port usage reports can be generated from the command prompt as given in Table 7-35:
where NMSROOT is the directory where you installed CiscoWorks.
Note
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
NMSROOT/campus/ etc/cwsi
where NMSROOT is the directory where you have installed CiscoWorks.
Step 2
NMSROOT/campus/bin/utupgrade.pl import_filename
The data is imported.
Note
Using Lookup Analyzer Utility
Lookup Analyzer is an utility used to analyze the performance of DNS servers and provide the following information:
•
•
•
•
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: FAILUREHost IP: 172.20.123.74, DNS Server: WINS, Time taken: 22, Status: FAILUREHost IP: 10.77.209.254, DNS Server: 64.104.128.248, Time taken: 18, Status: FAILURE....DNS Server : 64.104.128.248Success Count: 12Failure Count: 76Failure % : 86 %Total Time : 1 secs 561 msMin Time : 0 msMax Time : 52 msAvg Time : 17 msServer Efficiency(successCount/totalTime): 7.0--------------------------------DNS Server : 64.104.76.247Success Count: 0Failure Count: 76Failure % : 100 %Total Time : 2 secs 729 msMin Time : 0 msMax Time : 61 msAvg Time : 35 msServer Efficiency(successCount/totalTime): 0.0--------------------------------DNS Server : WINSSuccess Count: 0Failure Count: 76Failure % : 100 %Total Time : 750 msMin Time : 0 msMax Time : 23 msAvg Time : 9 msServer Efficiency(successCount/totalTime): 0.0--------------------------------Overall Summary-----------------Success Count: 12Failure Count: 76Failure % : 86 %-----------------Current Namelookup Related Settings---------------------------------UTMajorUseDNSSeperateThread: falseUT.nameResolution: bothUT.nameResolution.threadCount: 1UT.nameResolution.winsTimeout: 2000UT.nameResolution.threadThresholdPercentage: 10UT.nameResolution.dnsTimeout: 2000UTMajorUseDNSCache: falsenameserver.usednsForUT: trueDB.dsn: ani---------------------------------ISSUES/RECOMMENDATIONS-----------------------Issue #1: Failure Percent is greater than 20%Recommendation: Check all DNS/WINS entries and ensure proper hostnames are configuredIssue #2: DNS reverse lookup is NOT done as separate processRecommendation: Enable UTMajorUseDNSSeperateThread=true in ut.propertiesIssue #3: Name Resolution DNS server order is not optimalRecommendation: 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=48The 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
Step 2
Step 3
Step 4
Caution
To receive UTLITE events:
Step 1
Step 2
Or
You can change the property of URTlite state by launching Campus Manager. Select the Acquisition Settings option from User Tracking > Administration > Acquisition. The Acquisition Settings page appears. In the Acquisition Settings page, check the Get user names from hosts in NT and NDS domains and click Apply.
The UTLite script is supported on these platforms:
•
•
•
•
•
•
The UTLite script is not supported on these UNIX hosts:
•
•
•
This section contains:
•
•
•
•
•
•
Installing UTLite Script on Active Directory
You must install the UTLite script on the Active Directory server and update the server's logon script to get user logon information from Active Directory hosts.
You must have Administrator privileges on the Active Directory server to install the UTLite logon script. To install the script:
Step 1
a.
b.
NMSROOT\campus\bin\UTLite33.exe
NMSROOT\campus\bin\UTLiteNT.bat
where NMSROOT is the directory in which you installed CiscoWorks.
c.
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
a.
b.
start %WINDIR%\UTLite33 -domain domain -host ipaddress -port 16236
If port 16236 is already in use, enter a different number. This port number must match the number that you entered in the Use Port Number field, in the User Tracking > Administration > Acquisition > Acquisition Settings page.
For more details, see Modifying Acquisition Settings.
Step 3
UTLiteNT.bat
Step 4
The first time users log into the network after you edit this script, UTLite33.exe is copied to the local WINDIR directory on their Windows client system.
Installing UTLite Script on 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
a.
b.
C:\Program Files\CSCOpx\campus\bin\UTLite33.exe
C:\Program Files\CSCOpx\campus\bin\UTLiteNT.bat
where C:\Program Files\ is the directory in which you installed CiscoWorks.
c.
NETLOGON is located at
%SYSTEMROOT%\system32\Repl\Import\Scripts,where, SYSTEMROOT% is the root directory for the Windows operating system files.
Step 2
a.
b.
start %WINDIR%\UTLite33 -domain domain -host ipaddress -port 16236
If port 16236 is already in use, enter a different number. This port number must match the number that you entered in the Use Port Number field, in the User Tracking > Administration > Acquisition > Acquisition Settings page.
For more details, see Modifying Acquisition Settings.
Step 3
UTLiteNT.bat
Step 4
The first time users log into the network after you edit this script, UTLite33.exe is copied to the local WINDIR directory on their Windows client system.
Installing UTLite Script on NDS
You must install the UTLite script on the Novell Server and update the domain controller's logon script, to get user logon information from Windows hosts. You only need to do this once for each domain.
You must have ZenWorks installed and running on the Novell Server, and you must be using NDS 5.0 or later.
To install the script:
Step 1
Step 2
Step 3
•
•
