Table Of Contents
Administering Campus Manager
Understanding Campus Manager Administration
Using Campus Manager Administration
Viewing Campus Administration Dashboard
Using Device Discovery Administration
Viewing Summary of Device Discovery Settings
Specifying Seed Device
Modifying Discovery Schedule
Setting Debugging Options for Device Discovery
Using ANI Data Collection Administration
Viewing Summary of Data Collection Settings
Modifying SNMP Timeouts and Retries
Scheduling Data Collection
Setting up Data Collection Filters
Setting up Debugging Options for ANI Data Collection
Using Administration Reports
Analyzing ANI Server
Viewing Details of Discovered Devices
Viewing ANI Data Collection Metrics
Viewing List of Devices Supported
Using User Tracking Administration
Viewing Acquisition Information
Configuring User Tracking Acquisition Actions
Using User and Host Acquisition
Modifying Acquisition Settings
Modifying Acquisition Schedule
Specifying Purge Policy
Specifying Domain Name Display
Modifying Ping Sweep Options
Configuring Subnet Acquisition
Modifying Delete Interval
Importing Information on End Host Users
Using SNMP Version 3
Setting SNMP Credentials
Configuration Settings for SNMPv3 Devices
Administration Command Line Interface
Deleting Devices
Security
FAQs for Administering Campus Manager
Administering Campus Manager
Network administrators can perform administrative tasks on Campus Manager applications using the Administration module. This chapter contains:
•
Understanding Campus Manager Administration
•Using Campus Manager Administration
•Using SNMP Version 3
•Administration Command Line Interface
•Security
•FAQs for Administering Campus Manager
Understanding Campus Manager Administration
You can set up device discovery, ANI data collection, and User Tracking acquisition using the Administration module of Campus Manager.
The Administration module also allows you to:
•Configure discrepancy reporting for the discrepancies.
•Specify any discrepancies for which you need to generate syslog messages.
•Administer Topology Groups.
•Schedule Path Analysis traces.
Using Campus Manager Administration
Use the administrative functions of Campus to:
•View the Admin Dashboard. For more details, see Viewing Campus Administration Dashboard.
•Setup Device Discovery
–View the summary of Device Discovery Settings. For more details, see Viewing Summary of Device Discovery Settings.
–Specify the seed device and the IP address range, For more details, see Specifying Seed Device.
–Modify the Discovery Schedule. For more details, see Modifying Discovery Schedule.
–Specify the debugging options. For more details, see Setting Debugging Options for Device Discovery
–Modify SNMP settings. For more details, see Setting SNMP Credentials.
•Setup ANI data collection
–View a summary of data collection settings. For more details, see Viewing Summary of Data Collection Settings
–Modify data collection schedule. For more details, see Scheduling Data Collection.
–Specify data collection filters. For more details, see Setting up Data Collection Filters
–Set data collection debugging options. For more details, see Setting up Debugging Options for ANI Data Collection
•Administer User Tracking.
•Manage Topology Groups.
•View Network Discrepancies.
•Schedule Path Analysis traces.
•View reports on ANI server analysis, device discovery, data collection, and device support.
This section contains:
•Viewing Campus Administration Dashboard
•Using Device Discovery Administration
•Using ANI Data Collection Administration
•Using Administration Reports
•Using User Tracking Administration
•Using User and Host Acquisition
Viewing Campus Administration Dashboard
You can view the status of Device Discovery, Data Collection, and User Tracking Acquisition using the Campus Administration page of the Campus Manager Administration window.
Using this page you can also view a brief description of the steps involved in configuring Campus Manager.
To view the Campus Administration dashboard, start Campus Manager > Administration. The Campus Administration page appears.
The Current Status table displays the last completion time, result and status of Device Discovery, Data Collection, and User Tracking Acquisition.
The Configure Campus Manager table gives a brief description of the steps required for configuring Campus Manager.
Using Device Discovery Administration
The Device Discovery option of the Admin tab in the Campus Administration window allows you to:
•View a summary of Device Discovery settings. For more details, see Viewing Summary of Device Discovery Settings.
•Specify the seed device and IP address range. For more details, see Specifying Seed Device.
•Modify Device Discovery schedule. For more details, see Modifying Discovery Schedule.
•Specify the Device Discovery debugging options. For more details, see Setting Debugging Options for Device Discovery.
•Modify SNMP settings. For more details, see Setting SNMP Credentials.
Viewing Summary of Device Discovery Settings
You can view a summary of the device discovery settings using the Device Discovery option in the Admin tab of Campus Administration window.
To view a summary of device discovery settings:
Step 1 Start Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Device Discovery.
The Device Discovery Settings Summary page appears.
Table 4-1 describes the fields that appear in the Device Discovery Settings Summary page.
Table 4-1 Discovery Settings Summary
Field
|
Description
|
SNMP
|
Click View Details to view the SNMP settings. You can add new SNMP community strings, and edit or delete existing strings.
|
Use LoopBack Address
|
If true, name resolution using loopback address is enabled.
|
ResolveByName
|
If true, name resolution using device name is enabled
|
ResolveBySysName
|
If true, name resolution using sysname is enabled
|
Jump Router Boundaries
|
If true, discovery beyond router boundaries is enabled.
|
Reverse DNS Lookup
|
If true, name resolution using reverse DNS lookup is enabled.
|
Seed Device
|
Click View Details to view the Device Discovery Settings page. You can use this page to configure the seed device(s).
|
IP Address Range
|
The IP address range specified for discovery.
|
Discovery Schedule
|
Click View Details to view the discovery schedule. You can add a new schedule, and edit or delete existing schedules.
|
Specifying Seed Device
You can specify the seed device using the Device Discovery > Seed Device option in the Admin tab of Campus Administration window.
To specify seed device:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Device Discovery > Discovery Settings.
The Seed Device dialog box appears.
Step 3 Specify the seed device and the IP address range as described in Table 4-2.
Table 4-2 Device Discovery Settings
Field
|
Description
|
Usage Notes
|
Use Reverse DNS Lookup
|
Select this option to use DNS in your network.
|
Device Discovery uses Domain Name Services (DNS), if available, to perform device name lookups. If Device Discovery has problems resolving DNS names, discovery might take longer.
Therefore, if you do not use DNS in your network, or if you are experiencing problems with DNS or degraded performance from ANI, consider disabling the reverse DNS lookup.
|
Use LoopBack Address
|
Select this option to resolve name server by loopback address.
|
The preferred management address is obtained by searching for the address assigned to the Loopback interface.
|
Resolve By Sysname
|
Select this option to resolve name using sysname.
|
The preferred management address is obtained by resolving the name using the Sysname.
|
Resolve By Name
|
Select this option to resolve name using the name.
|
The preferred management address is obtained by resolving the name using the device name.
|
Jump Router Boundaries
|
Select this option to extend discovery beyond the boundaries set by routers on your network.
|
Be cautious about enabling discovery to occur beyond router boundaries.
Discovery could take much longer if you do not selectively choose the boundaries by excluding specific IP addresses.
|
Seed Device
|
Seed Device
|
Seed devices are devices used to initiate network discovery. Click Configure to enter the IP address or host name of the seed devices.
|
Click Browse to enter seed devices in a file.
The seed devices stored in the file have to be separated by a carriage return; only one seed device can be stored per line in the file.
For example, the seed devices in the file can be entered as:
Click Add to add new rows, enter seed device.
If you limit discovery by IP addresses, and these address are separated by addresses that are not in the included list, you must add a seed device for each set of addresses.
If you enter a seed device that matches the exclude criteria for IP address, the seed device is in the Discovery Report page.
The seed device is a special case and when discovering it, device discovery ignores the exclude criteria.
|
IP Address Range
|
IP Address Range
|
You can limit discovery by IP addresses in your network:
Click Configure to enter the IP Address ranges.
1. From the drop-down list box, select either of these options:
–Discover in IP address range.
–Do not discover IP address range.
2. Enter an IP address or a range of IP addresses to limit discovery.
Use standard IP addressing format (4 octets separated by periods) where any octet is:
–IP address—Number between 0 and 255
172.20.4.9
–Wild card—Asterisk (*) denoting all numbers from 0-255, inclusive
172.*.4.9
–Range—[begin-end], where begin and end are numbers between 0-255; begin is less than end.
172.[4-55].4.9
|
Establishing IP address boundaries prevents discovery from occurring outside of these boundaries. You can enter multiple IP Address ranges.
You can only exclude or include IP addresses or ranges; you cannot do both.
For example, you cannot enter IP addresses A and B to be discovered and IP address C to not be discovered. You can either include IP addresses A and B, or exclude IP address C.
|
Step 4 Click OK to start Device Discovery or click Cancel to apply these changes.
Modifying Discovery Schedule
You can modify the day, time, and frequency of discovery using
Device Discovery > Schedule Discovery of the Admin option in Campus Administration.
To modify the discovery schedule:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Device Discovery > Schedule Discovery.
The Schedule Discovery dialog box appears.
Step 3 Modify the discovery schedule settings as described in Table 4-3.
Table 4-3 Discovery Schedule
Field
|
Description
|
Usage Notes
|
Days, Hour, Min
|
Days on which and the time at which discovery is scheduled.
|
Optimum discovery schedule depends on the size of network and frequency of network changes.
The default discovery schedule is every 4 hours, on the 4-hour mark, daily: 3.00, 7.00 11.00, 15.00, 19.00, 23.00. Time is in the 24-hour format.
You can add new schedules and edit or delete existing schedules.
•Select a schedule and click Edit to edit the schedule.
•Select a schedule and click Delete to delete the schedule.
•Click Add to add a new schedule
Click Apply after adding or editing a schedule to save changes.
|
|
|
|
Recurrence Pattern
|
Select the days of the week on which discovery is to be scheduled.
|
This field is available only when you add or edit a schedule.
|
Step 4 Click Apply to apply these changes.
Discovery must occur frequently enough to capture changes to the network within a reasonable amount of time. This frequency is dependent on the frequency of changes to your network.
Setting Debugging Options for Device Discovery
You can specify the trace, debugging and logging options for device discovery using the Discovery > Discovery Debugging Options option in the Admin tab of Campus Administration window.
To set the options:
Step 1 Start Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Device Discovery > Debugging Option.
The Discovery Debugging Options dialog box appears.
Step 3 Modify the debugging options as specified in Table 4-4.
Table 4-4 Debugging Options Field Description
Field
|
Description
|
Usage Notes
|
Enable Debug
|
Modules
|
Specify the modules on which debug is to be enabled.
|
Click Select to view the available modules and select the modules in which debug is to be enabled.
Select is enabled only if Debug is enabled.
|
File Name
|
Name of the log file in which the trace messages are to be recorded.
|
This field is enabled only when the Record Trace Messages in Log File option is enabled.
|
Maximum File Size (lines)
|
Maximum size of the file in lines
|
This field is enabled only when the Record Trace Messages in Log File option is enabled.
|
Enable Device Level Debugging
|
Device IP(s)
|
IP addresses of devices for which discovery debugging messages are to be logged.
|
This field is enabled only when the device level debugging option is enabled.
You can enter multiple IP addresses, separated by commas.
|
Step 4 Click Apply.
Using ANI Data Collection Administration
You must run Data Collection for Campus Manager to manage devices. Using the Administration module of Campus you can:
•View the summary of data collection settings. For more details, see Viewing Summary of Data Collection Settings.
•Schedule data collection. For more details, see Scheduling Data Collection.
•Specify data collection filters. For more details, see Setting up Data Collection Filters.
•Specify the data collection debugging options. For more details, see Setting up Debugging Options for ANI Data Collection
Viewing Summary of Data Collection Settings
You can view a summary of the data collection settings using the Campus Data Collection option in the Admin tab of Campus Administration window.
To view a summary of data collection settings:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Campus Data Collection.
The Data Collection Settings Summary dialog box appears.
Table 4-5 describes the fields that appear in the Data Collection Settings dialog box.
Table 4-5 Data Collection Settings Summary
Field
|
Description
|
VTP Domains
|
VTP domains that are to be used as the filtering criteria for data collection.
|
IP Address Range
|
IP address range that is to be used as the filtering criteria for data collection.
|
Poll Interval
|
Periodicity for polling the network.
|
Data Collection Schedule
|
Click View Details to view the Data Collection Schedule details. You can add a new schedule and edit or delete existing schedules.
|
Modifying SNMP Timeouts and Retries
You can modify SNMP timeouts and retries using the Campus Data Collection > SNMP Timeouts & Retries option of the Admin tab in Campus Administration window.
To modify SNMP timeouts and retries:
Step 1 Choose Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Select Admin > Campus Data Collection > SNMP Timeouts & Retries.
The SNMP Timeouts & Retries dialog box appears.
Modify the SNMP settings as given in Table 4-6.
Table 4-6 Modify Data Collection SNMP Timeouts and Retries
Field
|
Description
|
Usage Notes
|
Target
|
Target device.
|
None.
|
Time Outs
|
Time period after which the query times out.
|
If time out is increased, discovery time could also increase.
|
Retries
|
Number of attempts.
|
None
|
Step 3 Click Add to add SNMP settings.
Step 4 Select a row and click Edit to edit the timeouts and retries values.
Or
Select a row and click Delete to delete the timeouts and retries values.
Step 5 Click Apply.
Scheduling Data Collection
You can schedule the day, time, and frequency of data collection and status polling using the Campus Data Collection > Schedule Data Collection option of the Admin tab in Campus Administration window.
To schedule data collection:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Campus Data Collection > Schedule Data Collection.
The Schedule Data Collection dialog box appears.
Step 3 Modify the data collection settings as described in Table 4-7.
Table 4-7 Data Collection Schedule Settings
Field
|
Description
|
Usage Notes
|
Poll Interval
|
Poll Interval
|
Periodicity for polling the network. Polling Interval is in the format HH:MM:SS, where HH is the hour; MM is the minutes; SS is the seconds.
|
Polling is done to see updated devices and link information without running data collection.
Polling is enabled by default. The default poll interval is 2 hours.
|
Schedule
|
Days, Hour, Min
|
Days on which and the time at which data collection is scheduled.
|
The optimum data collection schedule depends on the size of the network and the frequency of network changes.
The default data collection schedule is every 4 hours, on the 4-hour mark, daily: 04.00, 08.00, 12.00, 16.00, 20.00, 24.00 Note that time is in the 24-hour format.
|
|
|
|
Recurrence Pattern
|
Select the days of the week on which data collection is to be scheduled.
|
This field is available only when you are adding or editing a schedule.
|
Step 4 Select a schedule and click Edit to edit the schedule.
Step 5 Select a schedule and click Delete to delete the schedule.
Step 6 Click Add to add a new schedule.
Step 7 Click Apply after adding or editing a schedule.
Best Practices
Be cautious while scheduling data collection:
•Data collection consumes significant resources on the network management system.
•Use the Polling option to see updated device and link status without running data collection.
Peer Server Account (PSA) is used to get devices from DCR for running Data Collection. In ACS, for Authorization mode based on device groups, PSA plays a major role because Campus will run Data Collection for only those devices which are assigned to PSA.
For more details, see "Integrating Campus Manager With CiscoWorks Common Services."
Setting up Data Collection Filters
You can specify VTP Domains and IP Address ranges for data collection using the Campus Data Collection > Data Collection Filters option in the Admin tab of Campus Administration window.
To set up data collection filters:
Step 1 Click Campus Manager > Administration.
The Campus Manager Administration window appears.
Step 2 Click Admin > Campus Data Collection > Data Collection Filters.
The Data Collection FiltersSettings dialog box appears.
Step 3 Click Configure to activate the filter.
Corresponding filter window appears.
Step 4 Specify the Data Collection filters as described in Table 4-8.
Table 4-8 Data Collection Filters
Field
|
Description
|
Usage Notes
|
Filter Options
|
VTP Domain
|
Choose this radio button and click Configure to limit data collection using VTP domains:
1. From the drop-down list box, select one of these options:
–Manage devices in specified VTP domains.
–Do not manage devices in specified VTP domains.
2. Enter the VTP domains that are to be used to limit data collection.
|
Specifying VLAN Trunk Protocol (VTP) boundaries prevents data collection from occurring outside of these boundaries. You can enter multiple VTP domains.
You can only exclude or include domains; you cannot do both.
For example, you cannot enter domains A and B to be included for data collection and domain C to be excluded. You can either include domains A and B, or exclude domain C.
1. Click Add to add a VTP domain.
2. Select a VTP domain and click Delete to delete the VTP domain.
3. Click Apply to save changes.
|
IP Addresses
|
Choose this radio button and click Configure to limit data collection using IP addresses:
1. From the drop-down list box, select one of these options:
–Manage devices in specified IP address range.
–Do not manage devices in specified IP address range.
2. Enter an IP address or a range of IP addresses to limit data collection.
Use standard IP addressing format (4 octets separated by periods) in which any octet can be:
–IP address—Number between 0 and 255
172.20.4.9
–Wild card—Asterisk (*) denoting all numbers from 0-255, inclusive
172.*.4.9
–Range—[begin-end], where begin and end are numbers between 0-255 and begin is less than end
172.[4-55].4.9
|
Specifying IP address boundaries prevents data collection from occurring outside of these boundaries. The filter you set is applicable to the existing devices in ANI.
You can only exclude or include IP addresses or ranges; you cannot do both.
For example, you cannot enter IP addresses A and B to be included for data collection and IP address C to be excluded. You can either include IP addresses A and B, or exclude IP address C.
1. Click Add to add a VTP domain.
2. Select a VTP domain and click Delete to delete the VTP domain.
3. Click Apply to save changes.
|
Step 5 Click OK to start Data Collection or click Cancel to apply the changes and quit.
Setting up Debugging Options for ANI Data Collection
You can set the trace, and debugging, for ANI data collection using the Campus Data Collection > Debugging Options option in the Admin tab of Campus Administration window.
To set the debugging options:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Admin > Campus Data Collection > Debugging Options.
The Data Collection Debugging Options dialog box appears.
Modify the debugging options as specified in Table 4-9.
Table 4-9 Data Collection Debugging Options
Field
|
Description
|
Usage Notes
|
Enable Debug
|
Modules
|
Specify the modules on which debug is to be enabled.
|
Click Select to view the available modules and select the modules in which debug is to be enabled.
Select is enabled only if Debug is enabled.
|
File Name
|
Name of the log file in which the trace messages are to be recorded.
|
This field is enabled only when the Record Trace Messages in Log File option is enabled.
|
Maximum File Size (lines)
|
Maximum size of the file in lines
|
This field is enabled only when the Record Trace Messages in Log File option is enabled.
|
Enable Device Level Debugging
|
Device IP(s)
|
IP addresses of devices for which debugging messages are to be logged.
|
This field is enabled only when the device level debugging option is enabled.
|
Step 3 Click Apply.
Using Administration Reports
You can view an analysis of the ANI Server, details of devices discovered, data collection metrics, and list of devices supported using the Reports tab of Campus Administration window.
Analyzing ANI Server
You can analyze the ANI server for its performance using the Analyze ANI Server option in the Reports tab of Campus Administration window.
To analyze the ANI server:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Reports.
The Reports dialog box appears.
Step 3 Choose ANI Server and click Generate Report.
The ANI Server details appear.
Viewing Details of Discovered Devices
You can view details of devices discovered using the Discovery Report option in the Reports tab of Campus Administration window.
To view the details of devices discovered:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Reports.
The Reports dialog box appears.
Step 3 Choose Discovery Report.
Step 4 Select All Devices, Reachable Devices, or Unreachable Devices from the Report Type list.
Step 5 Click Generate Report.
The details of the discovered devices appear.
Table 4-10 describes the columns of the Device Discovery Report.
Table 4-10 Device Discovery Report
Field
|
Description
|
Type
|
Type of the discovered device.
|
OID
|
sys Object ID of the device.
|
IP Address
|
IP address of the discovered device.
|
Host Name
|
Host name of the discovered device.
|
Neighbors
|
IP address of the neighbors of the discovered device.
|
Status
|
Status of the discovered device.
|
Viewing ANI Data Collection Metrics
You can view the ANI data collection metrics using the Data Collection Metrics option in the Reports tab of Campus Administration window.
To view the data collection metrics:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Reports.
The Reports dialog box appears.
Step 3 Choose Data Collection Metrics.
Step 4 Enter the number of data collection cycles for which data is to be archived and click Apply.
Step 5 Click Generate Report.
The data collection metrics appear.
Table 4-11 describes the columns of the Data Collection Metrics report.
Table 4-11 Data Collection Metrics
Field
|
Description
|
Start Time
|
Time at which data collection was started.
|
Percent Complete
|
Percentage of data collection that has been completed.
|
End Time
|
Time at which data collection was completed.
|
Total Time
|
Total time taken for data collection.
|
Total Devices
|
Total number of devices from which data was collected.
|
New Devices
|
Number of devices from which data was collected.
|
Devices Deleted
|
Number of devices that were deleted.
|
Devices Per Hour
|
Number of devices per hour for which data was collected.
|
Objects Per Hour
|
Number of objects per hour for which data was collected.
|
Viewing List of Devices Supported
You can view the icon, name and object ID of the ANI supported devices using the Device Support option in the Reports tab of Campus Administration window.
To view the ANI supported devices supported:
Step 1 Click Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Click Reports.
The Reports dialog box appears.
Step 3 Choose Device Support and click Generate Report.
The details of supported devices appear.
Table 4-12 describes the columns of the Devices Supported report.
Table 4-12 Devices Supported Report
Field
|
Description
|
Icon
|
Icon of the device.
|
Name
|
Name of the device.
|
OID
|
sys Object ID of the device.
|
Using User Tracking Administration
You can perform the following administrative tasks using User Tracking Administration:
•Modify Acquisition settings. For more details, see Modifying Acquisition Settings.
•Schedule Acquisition. For more details, see Modifying Acquisition Schedule.
•Specify Purge Policy. For more details, see Specifying Purge Policy.
•Specify Domain Name display. For more details, see Specifying Domain Name Display.
•Configure Ping Sweep options for Acquisition. For more details, see Modifying Ping Sweep Options.
•Configure subnet Acquisition. For more details, see Configuring Subnet Acquisition.
•Configure end host and IP phone data delete interval. For more details, see Modifying Delete Interval.
•Import information on end hosts. For more details, see Importing Information on End Host Users.
Viewing Acquisition Information
You can view acquisition information using the Acquisition tab of the Campus User Tracking window.
To view acquisition information:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Acquisition.
The acquisition information appears.
Configuring User Tracking Acquisition Actions
You can configure User Tracking acquisition actions using the Actions option in the Acquisition tab of the Campus User Tracking window.
To configure acquisition actions:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Acquisition > Actions.
The Acquisition Actions dialog box appears.
Step 3 Configure Acquisition Actions as specified in Table 4-13.
Table 4-13 Acquisition Actions
Field
|
Description
|
Usage Notes
|
Select a type
|
You can select the type of acquisition. Type of acquisition can be:
•Devices
•Subnets
•IP Phones
|
When you select a type of acquisition the appropriate fields are displayed.
|
Devices
|
Scope Selection
|
Select the All hosts and users check box to acquire information about all hosts and users in your network.
|
If you do not select the All hosts and users check box, the device selection field is enabled and you can enter the name or IP address of the device about which data is to be acquired.
|
Device Selection
|
Device Name or IP Address
|
Enter the name or IP address of the device about which data is to be acquired.
|
Click Select to select the device from the list of available devices.
|
Subnets
|
Type Selection
|
You can choose to acquire data about a particular subnet or all the configured subnets.
|
If you choose to acquire data about a particular subnet, the subnet selection fields are enabled.
|
Subnet Selection
|
Subnet ID
|
Enter the ID of the subnet about which data is to be acquired.
|
This field is enabled only if you select the Subnet option in the Type Selection area.
Click Select to select the subnet ID from the list of available subnets.
|
Subnet Mask
|
Enter the subnet mask.
|
If you select the subnet ID then the subnet mask is automatically entered.
|
Discover only VLAN specific to subnet
|
Select this check box to acquire data only about the VLANs specific to the subnet.
|
None.
|
You do not have to specify any details for the IP Phones option.
Step 4 Click Start Acquisition.
Using User and Host Acquisition
You can modify the Acquisition settings and Acquisition schedule using the User and Host Acquisition option in the Acquisition tab of the Campus User Tracking window.
This section contains:
•Modifying Acquisition Settings
•Modifying Acquisition Schedule
•Specifying Purge Policy
•Specifying Domain Name Display
•Modifying Ping Sweep Options
•Configuring Subnet Acquisition
•Modifying Delete Interval
•Importing Information on End Host Users
Modifying Acquisition Settings
You can modify User Tracking Acquisition settings using the User and Host Acquisition > Acquisition Settings option of the Acquisition tab in Campus User Tracking window.
To modify acquisition settings:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Admin > Acquisition > Acquisition Settings.
The Acquisition Settings dialog box appears.
Step 3 Modify the acquisition settings as specified in Table 4-14.
Table 4-14 Acquisition Settings
Field
|
Description
|
Usage Notes
|
Enable User Tracking for DHCP Environment
|
Select this option to enable User Tracking for DHCP Environment.
|
If you enable this option, when the end hosts are in DHCP environment, the option helps you to detect the IP address information of end hosts correctly.
The IP address of the end hosts change rapidly,in this DHCP environment.
|
Use DNS to resolve host names
|
Select this option to resolve host names using DNS.
|
None.
|
Discover IP Phones on dot1q trunks for IOS Switches
|
Select this option to enable support of IP phones on IOS switches.
|
If you enable this option, the IP phones connected to the trunk links (voice VLANs) of IOS switches will be discovered.
Enabling this option causes User Tracking acquisition to take considerably longer to complete.
|
Get User Names from UNIX hosts
|
Select this option to allow acquisition of active user names on the UNIX network.
UNIX user names are updated at the end of major acquisitions.
|
Collects information only for users who are currently logged into the network.
|
Get User Names from hosts in NT and NDS
|
Select this option to allow the acquisition of active user names on the Windows or Novell Directory Service (NDS) servers.
Windows and NDS user names are updated at the end of subsequent major acquisition.
|
This option helps you to:
•Collect information only for users who are currently logged into the network.
•Collect information from NDS hosts. You must use NDS 5.0 or later.
You must install UTLite script, as it is a prerequisite.
|
User Port Number
|
Specify the UDP port number from where logon and logoff messages are received from hosts in Windows and NDS.
|
You must use the default port number unless it is already in use. This port number must match the port indicated in the login script.
|
Log File Name
|
Name of the log file.
|
User Tracking major acquisition errors are logged in this file.
|
Step 4 Click Apply.
Modifying Acquisition Schedule
You can modify UT acquisition schedule using the User and Host Acquisition > Acquisition Schedule option of the Acquisition tab in Campus User Tracking window.
To modify acquisition schedule:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Admin > Acquisition > Schedule Acquisition.
The Acquisition Schedule dialog box appears.
Step 3 Modify the acquisition schedule as specified in Table 4-15.
Table 4-15 Acquisition Schedule
Field
|
Description
|
Usage Notes
|
Minor Acquisition
|
Specify the periodicity in minutes at which a minor acquisition should take place.
|
None.
|
Major Acquisition
|
You can specify the days on which, the time at which a major acquisition is to take place.
You can also specify the days of the week on which a major acquisition is to be scheduled.
|
None.
|
Days, Hour, Min
|
Days on which and the time at which a major acquisition is to be carried out.
|
You can add new schedules and edit or delete existing schedules.
|
|
|
Recurrence Pattern
|
Select the days of the week on which a major acquisition is to be scheduled.
|
This field is available only when you are adding or editing a schedule.
|
Step 4 Select the schedule, and do one of the following:
•Click Edit to edit the schedule.
•Click Delete to delete the schedule.
•Click Add to add a new schedule.
Step 5 Click Apply after adding or editing a schedule.
Specifying Purge Policy
You can specify the intervals at which old reports and jobs are to be purged, using the Purge Policy option of Admin > Reports in Campus User Tracking window. You can save the purge policy as a job or execute it immediately.
To specify the purge policy:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Select Admin > Reports > Purge Policy.
The Report Settings dialog box appears.
Step 3 Specify the purge details for report archives and jobs.
Step 4 Click Save.
Specifying Domain Name Display
You can specify the way in which domain names are to be displayed, using the Domain Names option of Admin > Reports in Campus User Tracking window.
To specify the domain name display:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Select Admin > Reports > Domain Names.
The Report Settings dialog box appears.
Step 3 Choose the way in which domain names are to be displayed.
You can choose to show:
•Full domain name suffix
•Hide the full domain name suffix
•Hide the specified domain name suffix
Enter the domain name suffix in the field, if you choose to hide the specified domain name suffix.
Step 4 Click Save.
Modifying Ping Sweep Options
When Ping Sweep is enabled, the UTPing program in $NMSROOT/campus/bin will be invoked during acquisition to send out a sweep of pings for each subnet.
You can modify Ping Sweep option using the Acquisition > Ping Sweep option from the Admin tab in Campus User Tracking window.
To modify Ping Sweep options:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Admin > Acquisition > Ping Sweep.
The Ping Sweep dialog box appears.
Step 3 Specify if you want to enable Ping Sweep.
Specify the wait interval, if Ping Sweep is enabled.
Step 4 Specify the subnets, if you want to exclude any subnet from Ping Sweep.
You can select subnets from the list of available subnets and add to the list of subnets to be excluded. User Tracking does not perform Ping Sweep on large subnets. For more details, see Note for Ping Sweep Option.
Step 5 Click Apply.
Note for Ping Sweep Option
User Tracking does not perform Ping Sweep on large subnets, for example, subnets containing Class A and B addresses. Hence, ARP cache might not have some IP addresses and the User Tracking may not display the IP addresses. In larger subnets, the ping process leads to numerous ping responses that might increase the traffic on your network and result in extensive use of network resources.
To perform Ping Sweep on larger subnets, you can:
•Configure a higher value for the ARP cache time-out on the routers. To configure the value, you must use the arp time-out interface configuration command on devices running Cisco IOS.
•Use any external software, which will enable you to ping the host IP addresses. This will ensure that when you run User Tracking Acquisition the ARP cache of the router contains the IP addresses.
Configuring Subnet Acquisition
You can configure subnet acquisition using the Acquisition > Subnet Acquisition option of the Admin tab in Campus User Tracking window.
To configure subnet acquisition:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Admin > Acquisition > Configure Subnet Acquisition.
The Configure Subnet Acquisition dialog box appears.
Step 3 Specify the subnets that are to be discovered.
You can select subnets from the list of available subnets and add to the list of subnets to be discovered.
Step 4 Check Major acquisition on these subnets only check box, if required.
Step 5 Click Apply.
Modifying Delete Interval
You can modify the interval for deleting entries from the end host table or the IP table using the Acquisition > Delete Interval option of the Admin tab in Campus User Tracking window.
To modify the Delete Interval:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Admin > Acquisition > Delete Interval.
The Delete Interval dialog box appears.
Step 3 Specify delete intervals for end host and IP phone tables.
Step 4 Select Delete after every major acquisition check box, if required.
Click Delete now to delete the entries immediately.
Step 5 Click Apply.
Importing Information on End Host Users
You can import from a file, user names and notes for end hosts already discovered, using the End Host Table Import option of the Admin tab in the Campus User Tracking window.
To import information in end host users:
Step 1 Select Campus Manager > User Tracking.
The Campus User Tracking window appears.
Step 2 Click Admin > End Host Table Import.
The End Host Table Import dialog box appears.
Step 3 Specify the name of the file from which you are importing the end host table data.
Step 4 Click Apply.
Using SNMP Version 3
This section provides details of SNMP v3 support provided in Campus Manager 4.0. This section contains:
•Setting SNMP Credentials
•Configuration Settings for SNMPv3 Devices
Setting SNMP Credentials
You can modify SNMPv2 and SNMPv3 credentials using the Discovery > SNMP Settings option from the Admin tab in Campus Administration window.
Note You need to set the write community before you start using the configuration features in Campus Manager. To set the write community, select Common Services > Device and Credentials > Device Management from the CiscoWorks homepage.
To modify SNMP settings:
Step 1 Choose Campus Manager > Administration.
The Campus Administration window appears.
Step 2 Select Admin > Device Discovery > SNMP Settings.
The SNMP Setting window appears.
Modify the SNMP settings as given in Table 4-16.
Table 4-16 Modify SNMP Settings
Fields
|
Description
|
Usage Notes
|
SNMPV2, SNMPV3
|
Select the appropriate radio button for the version of the Simple Network Management Protocol for which you want to modify the settings.
|
Selecting the radio button displays the fields appropriate to the SNMP version selected.
|
|
SNMPV2
|
Enable Multiple Community Strings
|
Select this to enable multiple community strings.
|
You can provide multiple community strings for the same IP address range. Each string is tried for reachability until the correct string is found.
For example, 10.*.*.* public1 private1 and 10.*.*.* public2 private2
|
Encrypt Community Strings
|
Select this to enable encryption of community strings
|
Community strings are stored in the system in the encrypted format.
|
Target
|
Target device.
|
None.
|
Read Community
|
Read community string.
|
None.
|
Time Outs
|
Time period after which the query times out.
|
If time out is increased, discovery time could also increase.
|
Retries
|
Number of attempts.
|
None.
|
Comments
|
Remarks, if any.
|
None.
|
SNMPV3
|
Encrypt UserName and Password
|
If true, user name and password are encrypted.
|
None.
|
Target
|
Target device.
|
None.
|
UserName
|
Name of the user who has access to views configured on the device.
|
None.
|
Password
|
Password of the user.
|
None.
|
Time Outs
|
Time period after which the query times out.
|
If time out is increased, discovery time could also increase.
|
Retries
|
Number of attempts.
|
None.
|
Authentication
|
Method of authentication.
|
The method of authentication is SHA-1 or MD5.
|
Comments
|
Remarks, if any.
|
None.
|
Step 3 Do one of the following:
•Click Add to add community strings.
•Select a row and click Edit to edit the community strings.
•Select a row and click Delete to delete the community string.
Step 4 Click Apply.
Configuration Settings for SNMPv3 Devices
For using various Campus Manager features in devices running SNMPv3, you must make specific configurations on the devices. The commands that need to be configured are:
Configuring MIB views
set snmp view [-hex] {viewname} {subtree} [mask] [included | excluded]
[volatile | nonvolatile
For example:
set snmp view campusview 1.3.6.1 included nonvolatile
Setting access rights
You must set the access rights for a group with a certain security model in different security levels.
set snmp access [-hex] {groupname} {security-model v3}
{noauthentication | authentication | privacy} [read [-hex] {readview}]
[write [-hex] {writeview}] [notify [-hex] {notifyview}] [context
[-hex] {contextname} [exact | prefix]] [volatile | nonvolatile]
For example:
set snmp access campusgroup security-model v3 authentication read
campusview write campusview nonvolatile
Configuring a new user
set snmp user [-hex] {username} [remote {engineid}] [{authentication
[md5 | sha] {authpassword}] [privacy {privpassword}] [volatile |
nonvolatile]
For example:
set snmp user campususer authentication md5
Configuring password for a user
set snmp user [-hex] {username} [remote {engineid}] [{authentication
[md5 | sha] {authpassword}] [privacy {privpassword}] [volatile |
nonvolatile]
For example:
set snmp user campususer authentication md5 password1
Relating a user to a group
Using a specified security model you can relate a user to a group.
set snmp group [-hex] {groupname} user [-hex] {username}
{security-model v1 | v2 | v3} [volatile | nonvolatile]
For example:
set snmpw group campusgroup user campususer security-model v3
nonvolatile
Administration Command Line Interface
Replacing Corrupted Database
If you have a corrupted database, you can use the database administration tools to restore the database from a previous backup. However, if you do not have a previous backup, you must re-initialize the database.
When you run this command, if data collection is running, it is automatically stopped and then restarted when the database initialization is complete.
Caution If you re-initialize the database, information from discovered devices will be lost. However, user and host information is retained. Replace the database only if recommended by a Cisco technical representative.
Note Your login determines whether you can use this option.
Re-initializing the database
From the command prompt or shell window, enter:
•On Solaris: $NMSROOT/campus/bin/reinitdb.pl
•On Windows: perl %NMSROOT%\campus\bin\reinitdb.pl
This will erase all data from the database. Are you sure [y/n] ?
If you enter y, it erases all data (database tables Wbu*...) from the server.
Erasing data for user tracking and phone tracking, and restarting the server
•On Solaris: $NMSROOT/campus/bin/reinitdb.pl -ut
•On Windows: perl %NMSROOT%\campus\bin\reinitdb.pl -ut
Restoring the Original data in the server
•On Solaris: $NMSROOT/campus/bin/reinitdb.pl -restore
•On Windows: perl %NMSROOT%\campus\bin\reinitdb.pl -restore
where $NMSROOT is the root directory where you installed CiscoWorks.
Note Before executing the -restore command, you should stop the daemon manager and start again manually.
Deleting Devices
The Delete Device command is used to delete a device managed by Campus from ANI server.
Usage
DeleteDevice [-host hostname] [-port portnumber] [-secure] [-log
logfile] -device devices| -file filename | -u (unreachable devices)
-user username -password password
Security
After a period of inactivity, the CiscoWorks Homepage times out and is no longer accessible. Close all browser instances and relaunch CiscoWorks.
FAQs for Administering Campus Manager
These are the frequently asked questions for User Tracking application:
•How does the User Tracking acquisition process differ from that of the ANI Server?
•How does User Tracking user and host acquisition process work?
•Why is User Tracking not performing ping sweeps on some subnets?
Q. How does the User Tracking acquisition process differ from that of the ANI Server?
A. User Tracking is an ANI client application. The ANI Server provides several types of global discoveries, including:
–Device and physical topology acquisition, resulting in baseline network information such as device identity, module and port information, and physical topology. This type of acquisition is required for logical, user, and path acquisition.
–User acquisition, resulting in information about users and hosts on the network.
The ANI Server stores this information in the ANI database. User Tracking discovers the host and user information in the ANI database, correlates this information, and displays it in the User Tracking table.
For more information about the device discovery process, see Online help for Campus Manager Administration.
Q. How does User Tracking user and host acquisition process work?
A. Before collecting user and host information, Campus must complete a global discovery. During global discovery, the Campus generates a device list to determine which switches and routers it should look at to obtain MAC and IP addresses.
With these device lists in place, the User Tracking service performs steps described in Table 4-17.
Table 4-17 User Tracking User and Host Acquisition Process
Process
|
Description
|
Performs Ping Sweeps
|
Pings every IP address on all known subnets, as long as you have ping sweeps enabled (the default).
This process updates the switch and router tables before User Tracking reads those tables, ensuring that User Tracking displays the most recent information about users and hosts.
|
Obtains MAC addresses from switches
|
Reads the switch's bridge forwarding table. The bridge forwarding table provides the MAC addresses of end stations, and maps these MAC addresses to the switch port on which each workstation resides.
|
Obtains IP and MAC addresses from routers
|
Reads the Address Resolution Protocol (ARP) table in routers to obtain the IP and corresponding MAC addresses.
|
Obtains hostnames
|
Performs a Domain Name Service (DNS) lookup to obtain the hostname for every IP address.
|
Obtains usernames
|
Attempts to locate the users currently logged in to the hosts and tries to obtain their username or login ID.
|
Records discovered information
|
Records the discovered information in the ANI database.
|
For further information about device discovery process, see Online help for Campus Manager Administration.
Q. Why is User Tracking not performing ping sweeps on some subnets?
A. The criterion for whether or not User Tracking performs ping sweeps on a subnet is the number of hosts in the subnet:
–Check if you have excluded the subnets from ping sweep
–If a subnet has 256 or fewer hosts, User Tracking performs ping sweeps on that subnet.
–If a subnet has more than 256 hosts, User Tracking does not perform ping sweeps on that subnet.
If ping sweeps are not performed, User Tracking still obtains information from the router and switch mapping tables during a discovery. For more details on ping sweep, see Note for Ping Sweep Option.
Feedback
