Table Of Contents

Administering Campus Manager

Understanding Campus Manager Administration

Using Daemon Manager

Restarting Daemon Manager on Solaris

Restarting Daemon Manager on Windows

Viewing Campus Manager Home Page

Using Campus Manager Data Collection Administration

Viewing Summary of Data Collection Settings

Modifying SNMP Timeouts and Retries

Device Management

Mode and Policy Settings

Manually Including Devices to Data Collection

Manually Excluding Devices from Data Collection

FAQs on Device Management

Scheduling Data Collection

Device Poller

Understanding Groups

System Defined Groups

User Defined Groups

Overview of Subnet Based Groups

Rules Editor

Example of Rule

Using Groups

Creating Groups

Creating Group Properties

Creating Rules for Groups

Creating Memberships

Modifying Groups

Viewing Group Details

Deleting a Group

Recomputing Group Membership

Using Administration Reports

Analyzing ANI Server

Viewing Data Collection Metrics

Viewing Data Collection Details

Viewing List of Devices Supported

Using Other Admin Settings

Configuring Discrepancy Reporting and Syslog Message Generation

Purging Reports Jobs and Archived Reports

Setting RME Credentials

Setting Debugging Options

Setting up Debugging Options for Data Collection

Setting up Debugging Options for Configuration and Reports

Setting Debugging Options for Device Groups

Setting Debugging Options for Topology

Using Campus Manager Job Browser

Administration Command Line Interface

Configuration Settings for SNMPv3 Devices

Security

Frequently Asked Question

Administering Campus Manager

---

Network administrators can perform administrative tasks on Campus Manager applications using the Administration module. This chapter contains:

•Understanding Campus Manager Administration

•Viewing Campus Manager Home Page

•Using Campus Manager Data Collection Administration

•Understanding Groups

•Using Administration Reports

•Using Other Admin Settings

•Setting Debugging Options

•Using Campus Manager Job Browser

•Administration Command Line Interface

•Security

Understanding Campus Manager Administration

There are two main processes in Campus Manager:

•Data Collection

Fetches the device list from DCR and collects the following data from the network:

–Ports available in a device

–VLANs in the network or device

–Subnets in the network

–Discrepancies in the network

–Neighbor data for each device

–Details about STP running in the network

•User Tracking Major Acquisition

Collects information about the end hosts and IP phones in the network. For more details on User Tracking, see Understanding User Tracking.

The data collected by the above processes is used by Campus Manager to generate reports about the network.

---

Note The Device Discovery process that was available in the previous versions of Campus Manager is now moved to Common Services. For more details see, Removal of Device Discovery.

---

You can do the following settings from Campus Manager Administration:

•Data Collection Settings

– Specify the time period at which SNMP queries time out, and the number of retries that can be done by Campus Manager before it stops querying the device.

–Schedule the time intervals at which Data Collection runs.

–Include or exclude devices for Data Collection by setting appropriate filters.

For details, see Viewing Summary of Data Collection Settings.

•User Tracking Settings

Configure various options based on which data on end-hosts and IP phones in the network are collected. For details see, Using User Tracking Administration.

•Group Management

Create Device groups that can be shared by a set of users. These groups allow you to view a subset of the entire network.

For details, see Understanding Groups.

•Launch Administration Reports

Launch and view reports on:

–Analysis of the ANI Server

–Data Collection metrics

–List of devices supported

For details, see Using Administration Reports

•Other Admin Settings:

–Discrepancy Configuration

Customize the Discrepancies Report to display only those discrepancies that you want to be notified about.

Specify the discrepancies for which you need to generate Syslog messages

For details, see Understanding Discrepancies and Best Practices Deviations.

–RME Server Credentials

Enter the credentials of the RME Server that you need to access, to invoke CiscoWorks CLI commands from a remote client.

For details, see Setting RME Credentials.

–Set Purge Policies

Configure Purge settings for jobs or report archives For details, see Purging Reports Jobs and Archived Reports.

•Set Debugging options

Enable debugging for the various applications in Campus Manager. For details, see Setting Debugging Options

Using Daemon Manager

The daemon manager provides the following services:

•Maintains the startup dependencies among processes.

•Starts and stops processes based on their dependency relationships.

•Restarts processes if an abnormal termination is detected.

•Monitors the status of processes.

The daemon manager is useful if there are applications that have long-running processes that must be monitored and restarted. It is also used to start processes in a dependency sequence, and to start transient jobs.

Restarting Daemon Manager on Solaris

To restart daemon manager on Solaris:

---

Step 1 Log in as root.

Step 2 Enter the following to stop the daemon manager:

/etc/init.d/dmgtd stop

Step 3 Enter the following to start the daemon manager:

/etc/init.d/dmgtd start

---

Restarting Daemon Manager on Windows

To restart daemon manager on Windows:

---

Step 1 Go to the command prompt.

Step 2 Enter the following to stop the daemon manager:

net stop crmdmgtd

Step 3 Enter the following to start the daemon manager:

net start crmdmgtd

---

---

Note Do not start the daemon manager immediately after you stop it. The ports used by daemon manager will be in use for a while even after the daemon manager is stopped. Wait for sometime before you start the daemon manager.

---

If the system resources are less than the required resources to install the application, restarting daemon manager displays warning messages that are recorded in log file.

•Log file for Solaris is /var/adm/CSCOpx/log/dmgtd.log

•Log file for Windows is NMSROOT\log\syslog.log

Viewing Campus Manager Home Page

The Campus Manager Home Page is the first page that appears when you start Campus Manager.

From this homepage you can :

•View the status of the various processes running in Campus Manager

For details, see System Status

•View the count of Discrepancies and Best Practise Deviations available in the network and launch reports on them.

For details, see Discrepancies and Best Practices Deviations

•Access frequently used features in the application.

For details, see Campus Manager Tasks and Reports

•Launch various reports

For details, see Campus Manager Tasks and Reports

•Launch Recently Completed User Tracking Jobs

For details, see Recently Completed Jobs

You can use the Refresh icon to refresh the homepage manually and get a live status of the applications.

By default, the page refreshes every 45 seconds. Select the Auto Refresh check box to refresh the page automatically.

The information displayed on the homepage depends on the role assigned to you for the feature.

System Status

Table 5-1 describes the fields in the System Status table.

Table 5-1 Fields in System Status Table 

Field	Description
Operation	Campus Manager processes—Data Collection, User Tracking Acquisition
Last Completion Time	Date and time when the operation was last completed.
Result	Click on the respective hyperlinks to get reports on Data Collection, and User Tracking Reports.
Status	Status of the Operation—Running or Idle
Action	Click on the respective hyperlinks to start Data Collection, or User Tracking Acquisition. •Data Collection: Displays a confirmation message from where you can choose to run Data Collection only for new devices or for all devices. After selecting the required option, click OK to run Data Collection. •User Tracking Acquisition: Displays a confirmation message. Click OK to start User Tracking Acquisition.

Discrepancies and Best Practices Deviations

Campus Manager provides reports on discrepancies, such as network inconsistencies and anomalies or misconfiguration in the discovered network.

Best Practices Deviations are variations from the normal or recommended practices in a network.

The Campus Manager Home Page displays the total number of Discrepancies and Best Practise Deviations present in the network. When you click on the total number, the relevant report is launched. For more information, see Understanding Discrepancies and Best Practices Deviations.

Recently Completed Jobs

The Recently Completed Jobs table displays the following details of User Tracking jobs that were completed recently:

•Job ID

•Job Type

•Description

•Status

•Completed At

Each Job ID is displayed as a hyperlink. You can launch the report by clicking the hyperlink.

If there are more than eight jobs, a link named More is displayed at the bottom right of the table. Click More to launch the Report Jobs page.

Campus Manager Tasks and Reports

The Campus Manager homepage provides hyperlinks to the following tasks and reports:

Tasks	Description
Application Setup Tasks
Data Collection Settings	Displays the Data Collection Settings page. Here, you can configure various settings that define the scope of Data Collection in your network. For more information see Viewing Summary of Data Collection Settings.
User Tracking Acquisition Settings	Displays the Campus User Tracking Acquisition Settings page. Here you can configure various settings that define the scope of User Tracking Acquisition. For more information, see Using User Tracking Administration.
Discrepancy Settings	Displays the Network Discrepancies page from where you can customize the Network Discrepancies report. For more information, see Understanding Discrepancies and Best Practices Deviations.
Device Group Management	Displays the Group Management page from where you can manage groups. For more information, see Understanding Groups.
Device Trap Configuration	Displays the Device Trap Configuration page, from where you can configure Cisco switches for sending SNMPv1 MAC Notification Traps. For more information, see Enabling SNMP Traps on Switch Ports.
Trap Listener Configuration	Displays the Trap Listener Configuration page, from where you can configure either Campus Manager or DFM or HPOV to listen to SNMP traps sent by devices. For more information, see Configuring SNMP Trap Listener.
Trunk Configuration	Displays the Trunk Configuration page, from where you can configure trunk link between devices. For more information, see Creating Trunk.
Operational Tasks
Topology Services	Launches the Campus Manager Topology Services window.
VLAN Port Assignment	Launches the Campus Manager VLAN Port Assignment window.
Path Analysis	Launches the Campus Manager Path Analysis window.
Device Reports
Device Attributes Report	Displays the Report Generator from where you can generate and view Device Attributes Report. The report gives information about the devices in your network. For more information, see Displaying Device Attributes.
Port Attributes Report	Displays the Report Generator from where you can generate and view Port Attributes Report. The report gives complete information about the ports in the devices such as Port Name, type, Speed, Duplex mode etc. For more information, see Displaying Port Attributes.
VLAN Report	Displays the Report Generator from where you can generate and view VLAN Report. The report gives complete information about the VLANs existing in your network such as, VLAN ID, VLAN Type Status etc. For more information, see Displaying VLAN Reports.
User Tracking Reports
End Host/IP Phone Report	Displays the User Tracking Quick Reports page from where you can generate different types of End Host and IP Phones Report. For more information, see Viewing End Hosts Reports and Viewing IP Phones Reports.
Wireless Report	Displays the User Tracking Report Generator from where you can generate and view reports on the wireless devices connected to your network. For more information, see Viewing Reports on Wireless Clients.
End Host History Report	Displays the User Tracking Report Generator from where you can generate and view reports on end host history. This report gives information about the user logged in to the host, the date and time in which it was connected or disconnected to and from a port etc. For more information, see History Reports Based on Filters.
Network Reports
Best Practice Deviation Report	Displays the Report Generator from where you can generate and view reports on Best Practice Deviations in the network. You can view Acknowledged as well as Unacknowledged deviations. For more information, see Viewing Best Practices Deviations Reports.
Discrepancies Report	Displays the Report Generator from where you can generate and view reports on discrepancies present in the network. You can view Acknowledged as well as Unacknowledged discrepancies. For more information, see Viewing Discrepancy Reports.
Advanced Reports
Switch Port Capacity Report	Lists switches that crossed utilization threshold limits, along with the value of percentage port utilization. For details see, Understanding Switch Port Usage Reports.
Switch Port Summary Report	Gives the number of Connected, Free, and Free down ports in each switch. For details see, Understanding Switch Port Usage Reports.
Reclaim Unused Down Report	Lists administratively down ports, which are not connected to any end host. For details see, Understanding Switch Port Usage Reports.
Reclaim Unused Up Report	Lists administratively up ports, which are not connected to any end host. For details see, Understanding Switch Port Usage Reports.
Switch Port Utilization History Report	History Report for Switch Port Utilization helps you to view the log in and log out of end hosts for the selected devices. For details, see Understanding History Report.
Duplicate IP Report	Displays the Report Generator page from where you can generate Duplicate IP Report. For more information, see Viewing Duplicates Report
Duplicate MAC Report	Displays the Report Generator page from where you can generate the Duplicate MAC Report. For more information, see Viewing Duplicates Report
Duplicate MAC and VLAN Report	Displays the Report Generator page from where you can generate the Duplicate MAC and VLAN Report. For more information, see Viewing Duplicates Report
Ports with Multiple MAC Report	Displays the Report Generator page from where you can generate report for Ports with Multiple MAC. For more information, see Viewing Duplicates Report

Using Campus Manager Data Collection Administration

You must run Data Collection for Campus Manager to manage devices. Using the Administration module of Campus Manager, you can:

•View the summary of Data Collection settings. For details, see Viewing Summary of Data Collection Settings.

•Modify SNMP Timeouts and Retries. For details, see Modifying SNMP Timeouts and Retries.

•Schedule Data Collection. For details, see Scheduling Data Collection.

•Specify Data Collection filters. For details, see Device Management.

•Specify the Data Collection debugging options. For details, see Setting up Debugging Options for Data Collection.

•Configure Polling options. For more details see, Device Poller.

You can click the Go to Campus Administration hyperlink from any screen to go to the Campus Administration dashboard.

Viewing Summary of Data Collection Settings

You can view a summary of the Data Collection settings in this page.

To view summary:

---

Step 1 Select Campus Manager > Administration > Data Collection.

The summary of Data Collection Settings appears.

Table 5-2 describes the fields that appear in the Data Collection Settings dialog box.

Table 5-2 Data Collection Settings 

Field	Description
Type of Polling	Polling can be done for all devices or a critical set of devices. Clicking View Details for this option takes you to the Device Poller, where you set the type of polling. For more information, see Device Poller
Device Management Mode	Devices can be managed in the Auto mode or Manual mode. Clicking View Details for this option launches the Mode and Policy Settings page, where you can do the required settings. For more information, see Device Management.
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 checks whether the devices managed by Campus Manager are SNMP reachable, and if the interfaces in the devices are up or down. The default poll interval is 2 hours. You can change this value in Campus Manager > Administration > Data Collection > Device Poller page.
Data Collection Schedule	Data Collection fetches the device list from DCR and collects the following data from the network: •Ports available in a device •VLANs present in the network/ device •Subnets in the network •Discrepancies in the network •Neighbor data for each device •Details about STP running in the network 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 the SNMP timeouts and retries when Data Collection fails for a particular device with SNMP timeout exceptions.

To modify SNMP timeouts and retries:

---

Step 1 Select Campus Manager > Administration > Data Collection > SNMP Timeouts and Retries.

The SNMP Timeouts and Retries dialog box appears.

Step 2 Modify the SNMP settings as given in Table 5-3.

Table 5-3 Modify Data Collection SNMP Timeouts and Retries 

Field	Description
Target	IP address of the target device. For example, 10.*.*.*
Timeouts	Time period after which the query times out. This also indicates the time interval between the request and the first initial response from the device. The SNMP response may be slow for remote devices. If your network has remote devices connected over a slow link, configure a higher value for time-out. If Time out is increased, discovery time could also increase. Enter the value in seconds. The allowed range is 0-60. For every retry, the timeout value is doubled. For example, If the timeout is 10 seconds and retries 4: Campus Manager waits for 10 seconds for response for the first try, 20 seconds for the second retry, 40 seconds for the third retry and 80 seconds for the fourth retry. 150 seconds (10+20+40+80) is the total time lapse after which Campus Manager stops querying the device.
Retries	Number of attempts made to query the device. The allowed range is 0-8.

Step 3 Click Add to add SNMP settings.

Step 4 Select a row and either:

•Click Edit to edit the timeouts and retries values.

Or

•Click Delete to delete the timeouts and retries values.

Click OK to save the changes or click Cancel to exit.

Step 5 Click Apply.

---

Device Management

There are two modes of managing devices in Campus Manager namely Auto mode and Manual mode.

Auto Mode

This is the default option, where devices in DCR are automatically managed in Campus Manager Data Collection. You can specify the filter policies based on IP addresses to exclude or include devices in data collection. You can also manually add or delete devices.

For more details on mode and policy settings, see Mode and Policy Settings.

Manual Mode

In this mode policies are not applicable. You must manually add or delete devices and only those devices will be taken for Data Collection.

For more details on manual mode, see:

•Manually Including Devices to Data Collection.

•Manually Excluding Devices from Data Collection

Mode and Policy Settings

You can control the mode in which Data Collection runs as well as specify filter policies as follows:

Enable Auto Mode

This option is selected by default. This indicates that Campus Manager Data Collection happens in the Auto mode. When you deselect this, Campus switches to the Manual mode of Data Collection and all policies set in the Auto mode are dropped.

Specifying Filter Policies

In Auto mode you can specify filter policies to manage devices during Data Collection. These policies can either be a set of Include IP address ranges or Exclude IP address ranges. You cannot mix Include and Exclude policies.

Example for Include policy: Manage devices in the IP Address ranges 10.77.209.*, 10.77.210.*

If you want to have a combination of include and exclude filters, combine the Auto and Manual mode to achieve it. For example if you want to exclude a range of IP addresses say 10.77.210.* but want to include devices 10.77.210.1 and 10.77.210.2:

•Set Exclude Filter Policies in the Auto mode to exclude the IP address range 10.77.210.*

•Go to the page where you can manually include devices and select 10.77.210.1 and 10.77.210.2 from the device selector in that page.

To set up Data Collection filters:

---

Step 1 Select Campus Manager > Administration > Data Collection > Device Management > Mode And Policy Settings.

The Data Collection Filter Settings dialog box appears.

Step 2 Specify the Data Collection filters as described in Table 5-4.

Table 5-4 Data Collection Filters 

Field	Description	Usage Notes
IP Address Range	1. From the drop-down list box, select either 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 Campus Manager Server. 1. Click Add to add an IP Address Range. 2. Select an IP Address Range and click Delete to delete the IP Address Range. 3. Click Apply to save changes.

---

---

Note Filters come into effect only in the next Data collection cycle.

---

Manually Including Devices to Data Collection

The Device Selector in Include devices page displays the list of devices not managed by Campus Manager, but present in DCR. From this list you can select and add devices that need to be managed by Campus Manager.

This manual mode of including devices can work in complement with the Auto mode or can work independently. This implies:

•You can manually include devices even when you are in Auto management mode. Whereas if you are in Manual mode, Auto mode policies are not applicable.

•If you switch from Auto mode to Manual mode, the Auto mode policies will not be retained. However, the devices that are already managed will be included in future Data Collections.

•The list of devices included manually is given preference over the policies set through Auto mode.

For example, If you set a Data Collection filter to exclude the devices belonging to the address range 10.77.*.*, but manually add 10.77.2.1, this device will be included in the consecutive Data Collection cycle.

•The policies that you set in Auto and Manual mode will come into effect only during the next Data Collection cycle.

•Click Show Included Devices, to see the list of manually included devices in this cycle.

To manually include devices:

---

Step 1 Select Campus Manager >Administration >Data Collection >Device Management > Include Devices.

The Include Devices page is launched. The Device Selector in this page has two groups:

All devices and Device Type Groups. If you have configured User defined groups, it is displayed here.

Step 2 Select the list of devices from the groups.

The devices that are already being managed by Campus Manager will not be present in the Add list.

Step 3 Click Include.

These devices will be included in the next Data Collection process.

Step 4 Click the Selection tab to see the list of devices that you have added manually.

---

---

Note Any changes you make here will come into effect only in the next Data collection cycle.

---

Manually Included Devices Report

This report gives the details of devices that are manually included from Campus.

To view the report:

---

Step 1 Go to Campus Manager >Administration >Data Collection >Device Management >Include Devices

Step 2 Click Show Included Devices.

The report displays information as described in Table 5-5:

Table 5-5 Manually Included Devices Report

Field	Description
IP Address	IP Address of the device.
Device Name	Name of the device.
Management State	Indicates whether the device is currently managed in Campus.

To exclude a device from the Included list, select the device and click Exclude.

---

To get more clarity on Device Management, see FAQs on Device Management.

Manually Excluding Devices from Data Collection

You can manually exclude devices from the list of devices managed by Campus Manager. The Device Selector in the Exclude page will list the devices that are currently managed in Campus Manager and the manually included devices.

This manual mode of excluding devices can work with Auto mode or independently. This implies:

•You can manually exclude devices even when you are in Auto management mode. Whereas if you are in Manual Mode, Auto mode policies are not applicable

•If you switch from Auto mode to Manual mode, the Auto mode policies will not be retained. However, the devices that are already managed will be included in forthcoming Data Collections.

•The list of devices excluded manually are given preference over the policies set through Auto mode.

For example, If you set a Data Collection filter to include the devices belonging to the address range 10.77.*.*, but manually exclude 10.77.1.3, the device 10.77.1.3 will be excluded in the Data Collection process.

•The changes made in Auto and Manual mode will come into effect only during the next Data Collection cycle.

•Click Show Excluded Devices to see the list of manually excluded devices in this cycle.

To manually exclude devices:

---

Step 1 Select Campus Manager >Administration >Data Collection >Device Management > Exclude Devices.

The Exclude Devices page is displayed with the following groups:

– All Devices

–Device Type Groups

–User Defined Groups (If any)

Step 2 Select the devices from the list which you want to remove.

Step 3 Click Exclude.

These devices will be excluded from the list of devices managed by Campus Manager.

Step 4 Click the Selection tab to see the list of devices that you excluded manually.

---

---

Note Any changes you make here will come into effect only in the next Data collection cycle

---

Manually Excluded Devices Report

This report gives the details of devices that you manually excluded from Campus Manager.

To view the report:

---

Step 1 Select Campus Manager >Administration >Data Collection >Device Management > Exclude Devices.

The Exclude Devices page is launched.

Step 2 Click Show Excluded Devices.

The report displays information as given in Table 5-6:

Table 5-6 Manually Excluded Devices Report

Field	Description
IP Address	IP Address of the device.
Device Name	Name of the device.

---

To include a device from the Excluded list, choose the device and click Include.

For more information on Device Management, see FAQs on Device Management.

FAQs on Device Management

The following are the frequently asked questions about Device Management. The answers to these questions help you understand Device Management better:

Q. Some of the devices in DCR are not managed in campus, but that IP Address range is available in Auto mode policy filter. What could be the reason?

A. Check whether these devices are manually excluded from Campus Manager in the Manually Excluded Devices report. If the device you are looking for is available here, then it will not be managed in Campus unless it is manually included.

Q. When I exclude a device, will it get deleted immediately or during next Data Collection?

A. If you are manually excluding a device, it will be immediately deleted from Campus Manager and they will be prevented from getting managed in further Data Collections.

Q. What is the difference between manually excluding a device and deleting a device from Topology Services screen?

A. Manually Excluding a Device: If you manually exclude a device, it gets deleted from Campus. Even if you do Data Collection from the neighbor device, it does not get managed in Campus.

Deleting a device from Topology Services screen: If you delete a device from Topology services, and run Data Collection on its neighbor device, the device becomes managed in Campus Manager.

Q. I have manually included a device. How do I exclude it?

A. Select and exclude that device from the device selector in the Exclude Devices page. Alternatively, you can exclude that device from the Manually Included Devices report.

Q. I have manually excluded a device. How do I include it?

A. Select and include that device from the device selector in the Include Devices page. Alternatively, you can include that device from Manually Excluded Devices report.

Q. .When I manually include a device, will it be managed immediately in Campus Manager?

A. No. Unless you run Data collection, this will not get managed in Campus Manager.

Q. I have both Auto mode and Manual mode enabled. Which one will take higher priority?

A. Manual mode always gets higher priority.

Q. I have manually added some devices and started Data collection for all devices. For which devices will Data collection run?

A. Data collection will run for manually added devices and the devices that are already managed in Campus Manager.

Q. I have added n devices in DCR and in that I want to manage only subset of devices in Campus Manager. Is there any way to do this?

A. Either:

•Manually include those devices and run Data collection.

Or

•Select Auto Mode and specify the required IP Address range in the auto mode policy filter and run Data collection.

Q. Is VTP domain based filter available in Campus Manager?

A. No, it is removed in Campus Manager. You can only filter based on IP Address range.

Q. How to make Campus Manager identify the HSRP devices and perform data collection?

A. To make Campus Manager identify the HSRP devices and perform data collection, do the following:

---

Step 1 Add the virtual IP address of the HSRP router as the value for the property "HsrpVitrualIPAddress" in the ANIServer.properties file

Since there is no UI to specify the virtual IP address, you need to enter it in the ANIServer.properties file.

When you need to specify multiple virtual IP addresses, separate them with a colon.

For example:

HsrpVitrualIPAddress=10.77.210.20:10.77.211.21

Step 2 Restart the ANIServer for the changes to take effect.

---

Scheduling Data Collection

To schedule data collection:

---

Step 1 Select Campus Manager > Administration > Data Collection > Schedule Data Collection.

The Data Collection Schedule dialog box appears.

Step 2 Modify the data collection settings as described in Table 5-7.

Table 5-7 Data Collection Schedule Settings 

Field	Description	Usage Notes
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.

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

Step 3 Click OK to save the changes or click Cancel to exit.

---

Best Practices

Be cautious while scheduling Data Collection:

•Data Collection consumes significant resources on the network management system.

•Use the Polling option to see the device and link status without running data collection. For more details on polling see, Device Poller

Device Poller

Campus Manager polls the entire network for device and link status periodically.This feature allows you to:

•Configure the time interval at which the network is polled.

•Poll only a critical set of devices.

Use this option to see the device and link status without running Data Collection.

Since Data Collection consumes significant system resources, you can simply poll the network and view the device and link status in Topology maps.

Adding Critical Devices to the Device Poller

To add a device to the Critical Devices list from Topology Map:

---

Step 1 Launch a Topology map.

Step 2 Right click a device and select Add device to Critical Poller.

---

To add a device to the Critical Devices list from N-Hop View Portlet:

---

Step 1 Launch N-Hop View Portlet.

Step 2 Go to the configuration screen and select Poll devices.

For complete details on N-Hop view portlet, see N-Hop View Portlet.

---

---

Caution If the critical set of devices is more than 30, the amount of traffic generated as part of polling cycle will be occupying good amount of bandwidth.

---

To configure Device Poller:

---

Step 1 Go to Campus Manager > Administration > Data Collection > Device Poller.

The Device Poller screen is displayed.

Step 2 Configure the device poller options as specified in Table 5-8.

Table 5-8 Device Poller Options

Field	Description	Usage Notes
Polling Details
All Devices	Specifies that all devices in the network will be polled at the specified interval.	By default the whole network is polled every 2 hours.
Critical Devices	Specifies that only critical devices in the network will be polled at the specified interval.	You can configure this option when you need to poll a few devices in the network more frequently. By default the critical devices are polled every five minutes.
Time Interval	Time interval at which the specified devices are polled periodically. The time interval is added to the completion time of Data Collection. For example, you have configured the following: •Data Collection is scheduled to run at 07:00 hours •Time interval is set to 4 hours. If Data Collection completes at 08:00 hours, the next polling will happen at 12:00 hours (8 + 4).	Configure this option to change the interval from the default value.
Show Devices	For Critical Devices: Displays the list of critical devices in the network.	The following information about the Critical Devices is displayed: •IP Address •DeviceName You can choose any device and click Delete to remove it from the Critical Device poller list.
	For All Devices: Launches the Data Collection metrics report.	The following information about the devices in the network is displayed: •IP Address •DeviceName •DeviceType •Neighbors

Step 3 Click Apply to save the configuration.

---

Understanding Groups

A Group can be thought of as a convenience view that allows you to view a subset of the entire network based on the group rule defined while creating the view.

These views, which are subsets of the Layer 2 views, can be accessed by a user or a set of users. These custom views are generated using a Campus Manager feature called Grouping Services that helps to manage groups of devices.

Grouping Services determines the membership of a group by interpreting and applying the rule associated with the group.

Hence, Topology Groups allows you to:

•Identify and view a set of objects corresponding to a view.

•Create and manage views.

•Define convenience views which are a subset of the Layer 2 map.

Concept of a Group

A group is a named set of devices. The group is characterized by a set of properties such as a name, description, type, access permission, and so on. Most importantly, a group has an associated rule. The rule determines the membership of a group, which may change whenever the rule is evaluated.

Groups manage subgroups in a hierarchical organization. Two predefined top level Parent groups are available when you install Campus Manager:

•System Defined Groups

•User Defined Groups

Another group named Subnet Based Group is automatically created when devices are managed. For more details, see Overview of Subnet Based Groups.

These groups are provided to categorize devices at your site, and each of these contains a list of all the devices in the Campus Manager Database.

The groups under Administration > Groups and that under Topology Services > Topology Groups follow the same hierarchy.

After you create a group through Administration > Groups, you must reopen the Topology Services to view the changes.

By default, only the admin user has necessary privileges to create groups under System Defined Groups. However, the admin user can edit the group to provide write access to other users. Access permissions are maintained on a username basis, not a role basis.

If you have appropriate permissions, you can create subgroups under groups. Hence, each Child group is a subgroup of a Parent group.

Note the following:

•The membership of a Child group will be a subset of its immediate Parent group.

•Changes in the properties of a Parent group—Name, Rule, Evaluation Type, Access Permissions, impact all Child groups under it.

•When you remove a group, all Child groups under it are also removed.

•When a user is removed from the Campus Manager list of users, the groups created by the user are not removed.

System Defined Groups

System Defined Groups is a top-level container for standard groups that are accessible to and used by most Campus Manager users. By default, only the Campus admin user has necessary privilege to create groups under the System Defined Groups folder.

A user must have write permission to a group in order to create a Child group under it. Although by default, only the Campus Manager Admin user has write permission to System Defined Groups, the admin user can grant write privilege to other users by editing the access permission to System Defined Groups.

A system administrator will typically define and configure their own System Defined Groups based on the partitioning requirements of the network.

The Admin user may choose to partition views based on any of the attributes that can be grouped; however, IP address, device name, sysLocation, and subnet will be common selections.

User Defined Groups

User Defined Groups is a top-level container where individual Campus Manager users can create their own groups. Typically, the groups under User Defined Groups would be used and accessible to the user who created the group, and perhaps a small group of additional users, or these groups may be transient in nature.

For example, if Joe Smith wants to create a group that contains all devices where he is the System Contact, and he uses the following rule to form this group:

:Campus:OGS:Device.SystemContact equals "Joe Smith" OR

:Campus:OGS:Device.SystemContact equals "jsmith"

Dynamic Group

A dynamic group is a group for which the membership list is always up-to-date.

Whenever you view a dynamic group, it always displays the latest group membership list.

Static Group

A static group is a group for which the membership is refreshed only when you explicitly request it. Between re-evaluations, the Group Server stores the membership list and group definition of the static group.

Overview of Subnet Based Groups

Subnet based groups are automatically created when devices are managed. Subnet based groups help you work on smaller subsets of devices that are logically grouped. They are automatically deleted when all the devices in a subnet are deleted. This topic covers:

•Accessing Subnet Based Groups

•Understanding Subnet Based Groups

•Creating Groups Based on Subnet

Accessing Subnet Based Groups

To access Subnet based groups go to Campus Manager > Administration > Groups.

This displays the Group Management page. The Group Selector field displays two groups, System Defined Groups and User Defined Groups. The Subnet Based Groups are created under System Defined Groups.

Understanding Subnet Based Groups

The Subnet based groups use the following name format:

Subnet -- Subnet Mask.

The rule expression for Subnet Based Groups has the following components:

Class.attribute operator "value"

For example,

:Campus:OGS:Device.IP.Subnet equals "172.20.104.192" AND :Campus:OGS:Device.IP.SubnetMask 
equals "255.255.255.240"

The rule above will select all devices of subnet 172.20.104.192 and subnet mask 255.255.255.240.

Creating Groups Based on Subnet

For example, the following rules might be used to create two groups based on the IP address subnet:

:Campus:OGS:Device.IP.Subnet equals "172.29.252.32"

:Campus:OGS:Device.IP.Subnet equals "172.29.252.64"

The examples provided here are simple. However, the Grouping Service allows arbitrarily complex rules to be formed by combining rule expressions with AND, OR or the EXCLUDE operators. This gives the administrator the power and flexibility to create view partitions tailored to the needs of their site.

Rules Editor

Every group is defined by a set of rules. You may select an item from the drop down menus, enter a rule in the free-form Rule Text area, or use a combination of the two.

A rule set contains a Boolean combination of individual rule expressions. A rule expression is made of the following components:

Object Type

The type of devices which form the group. Rules are evaluated on the list of devices discovered. Campus Manager supports only one object type:

:Campus:OGS:Device

Variable

Any of the attributes of a device. Table 5-9 gives details on the available variables:

Table 5-9 Device Attribute Description 

Attributes	Description
DiscoveryStatus	Status of the Data Collection process.
Hostname	Name of the device.
ImageVersion	Software version running on the device.
IP.Subnet	IP address of the device with the subnet to which it belongs.
IP.SubnetMask	Subnet mask address of the device.
IPAddress	IP Address of the device.
SysName	Name of the device as configured by the Administrator.
SysObjectID	SysObjectID of the device as configured by the Administrator.
SystemContact	Contact for the device details as entered by the Administrator.
SystemLocation	Location of the device as entered by the Administrator.

Operator

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

–equals

–contains

•When the variable DiscoveryStatus is used, equals is the only operator is available.

•When the variable IPAddress is used, the following operators are available:

–equals

–contains

–startswith

–endswith

–range

Value

A free flow operand forming the last part of the rule.

When the variable DiscoveryStatus is used, only the following values are available:

•Never_Reachable

•Reachable

•Currently_Unreachable

Example of Rule

Let us consider a scenario where you need to define a rule for a set of devices in the State Street Campus. Campus Manager has devices at two locations: Bldg 1 Devices and Bldg 2 Devices.

In this scenario, we will create rules for the System Defined Groups and the User Defined Groups.

Rule for a System Defined Group

•To create a System Defined Group whose member devices are located in Bldg. 1 Devices, the group rule is:

:Campus:OGS:Device.SystemLocation equals "Bldg 1 Devices"

where

Variable is SystemLocation

Operator is equals

Value is Bldg 1 Devices

•Similarly, to create a System Defined Group whose member device IP addresses is 172.20.121.10, the group rule is:

:Campus:OGS:Device.IpAddress equals "172.20.121.10"

In addition you can use the contains operator to match a value anywhere in the attribute:

:Campus:OGS:Device.IpAddress contains "10"

The above rule, will match devices with IP address like 172.20.10.3, 172.25.3.101 etc.

Rule for a User Defined Group

To create an User Defined group whose member devices have a common system contact person, J Smith Devices, the group rule is:

:Campus:OGS:Device.SystemContact equals "J Smith Devices"

A Composite Rule

A Boolean set of such rules form a composite rule. In the example, to create a group whose member devices are labelled Lab Test Setup, have a common system contact person, J Smith Devices, the composite rule is:

:Campus:OGS:Device.DeviceLabel equals "Lab Test Setup" AND

:Campus:OGS:Device.SystemContact equals "J Smith Devices"

Using Groups

The main tasks that you can perform using groups are:

•Creating Groups

•Modifying Groups

•Viewing Group Details

•Recomputing Group Membership

•Deleting a Group

Creating Groups

You can create groups under System Defined Groups and User Defined Groups. To create Groups, you must select Campus Manager > Administration > Groups. Creating Groups involves:

•Creating Group Properties

•Creating Rules for Groups

•Creating Memberships

Creating Group Properties

Access to group creation is based on permission levels. You can create groups under User Defined Groups.

By default, only the CiscoWorks admin user can create groups under System Defined Groups. However, the admin user can modify the access permission to the System Defined Group to enable edit privilege (that is, create permission) to other Campus Manager user names.

To create Group Properties:

---

Step 1 Select Campus Manager > Administration > Groups.

The Group Management window appears.

Step 2 Click Create.

The Properties: Create window opens.

Step 3 Enter details as explained in Table 5-10:

Table 5-10 Creating Properties Field Description 

Field	Usage Notes
Group Name	The group name should be unique within the Parent group. However, it need not be so across groups. The same group name cannot be used in the same group hierarchy.
Copy Attributes from Group	1. Click Select Group to copy attributes from a previously selected defined group. The Replicate Attributes dialog box appears. 2. Select the devices from the Replicate Attributes dialog box. 3. Click OK to select the devices or click Cancel to exit.
Parent Group	1. Click Change Parent to change the Parent group under which you want to define the group. 2. Select the devices from the Select Parent window. 3. Click OK to select the devices or click Cancel to exit.
Description	You can enter a detailed description of the group identifying its characteristics in this field.
Membership Update	Select a membership update mode. •Automatic—The membership of the group is automatically recomputed each time the group is invoked. •Only upon user request—The membership of the group is recomputed only when an explicit request is made, using the Refresh option. If you select Automatic, the group will be a Dynamic group. If you select Only Upon User Request, the group will be a Static group.
Visibility Scope	Select the mode of visibility. •Private •Public

Step 4 Click Next.

The Rules window appears. To enter the details in the Rules: Create dialog box, see Creating Rules for Groups.

---

Creating Rules for Groups

After entering the details for creating properties for the Group, you must create rules for the Group. To create rules for the Group, either you must use the parameters specified, or manually enter the rule text.

To create rules using parameters:

---

Step 1 Enter details for Rule Expression, in the Rules Window.

Table 5-11 describes the fields in the Rule Expression area.

Table 5-11 Rules: Create Field Description 

Field	Description
—	Select the Boolean expression. •OR •AND •EXCLUDE
Object Type	The type of devices that form the group. Rules are evaluated on the list of devices discovered. Campus Manager supports only one object type::Campus:OGS:Device
Variable	Attribute of a device. The available variables are: •DiscoveryStatus •HostName •ImageVersion •IP Subnet •IP SubnetMask •IPAddress •SysName •SysObjectID •SystemContact •SystemLocation For more details, see Rules Editor.
Operator	Operator used in forming a rule. equals is the only operator available.
Value	Enter the desired value for the variable you have selected.

Step 2 Click Add Rule Expression.

The Rule Text field shows the rule you are creating.

You can also enter the rules directly in the Rule Text field.

Step 3 Click Check Syntax to validate the rules syntax entered.

Step 4 Click View Parent Rules to view rules defined for the Parent Groups.

Step 5 Click Next to create Memberships to specify the devices available to the group.

For entering details for creating Memberships, see Creating Memberships.

---

Creating Memberships

You can create memberships to specify the devices available to the group. The devices appear in Available Objects From Parent Group or Objects Matching Membership Criteria, based on the properties and rules you specified in the previous steps.

Available Objects From Parent Group is the set of objects in the Parent group not selected by the Child group's rule.

To add the selected devices from the Available Objects From Parent Group list to the Objects Matching Membership Criteria list:

---

Step 1 Select one or more IP addresses of the devices from the Available Objects From Parent Group list on the left pane.

Step 2 Click Add.

The devices appear in Objects Matching Membership Criteria list, based on the properties and rules you specified in the previous steps.

If you want to remove devices from the Objects Matching Membership Criteria list, select the device from the list of Objects Matching Membership Criteria, and click Remove.

Step 3 Click Next to view the summary of the details of the newly created group.

Table 5-12 describes the entries in the Summary: Create table.

Table 5-12 Create Group Summary Entry Description 

Entry	Description
Group Name	Name of the group.
Parent Group	Name of the Parent group.
Description	Description for the group.
Membership Update	Select a membership update mode. •Automatic—The membership of the group is automatically recomputed each time the group is invoked. •Only Upon User Request—The membership of the group is recomputed only when an explicit request is made, using the Refresh option. If you select Automatic, the group will be a Dynamic group. If you select Only Upon User Request, the group will be a Static group.
Rules	Rule you entered for the group.
Visibility Scope	Visibility scope that you selected.

Step 4 Click either:

•Finish to create the group,

or

•Cancel to exit the wizard and go back to the Group Management window.

---

Membership Update

The membership of a group is governed by the rule associated with a group. The changes in the membership is reflected in the Network Topology View of the group. To view a topology view, select Campus Manager > Topology Views.

Moreover, while groups with evaluation type Automatic have membership that is current, groups with evaluation type Only Upon User Request retain the membership at creation time or on subsequent re-evaluation.

Two modes of membership updates are available:

•Automatic

The membership of a group is recomputed automatically after every Data Collection.

If the node or view has been displayed, you must close all of Topology Services and re-open it to display the revised group membership.

•Only Upon User Request

The membership of the group is recomputed only when an explicit request is made, using the Refresh option. For more information on the Refresh option, see Recomputing Group Membership.

Modifying Groups

You can modify most attributes of a group in the Edit mode, except the Parent group.

To modify groups:

---

Step 1 Select a group, and click Edit.

You can modify the Group Name, Description, and Membership Update Type.

Step 2 Click Next.

•To modify group rule, edit the rule either using the Rule Expression fields or edit the rule in the Rule Text field and click Next.

•To add or remove devices from the Objects in Group, click Add or Remove, as appropriate and click Next.

•To modify access permissions, select the access levels in the Permission field and click Next.

Step 3 Click Finish to save the modified groups.

---

Viewing Group Details

To view the attributes of a group:

---

Step 1 Select Campus Manager > Administration > Groups.

Step 2 Select a group.

Group information is displayed in the right window.

•To view detailed attributes for the group, click Details.

•To view the rules attributes of the Parent group, click View Parent Rules.

•To view the list of devices in the group, click Membership Details.

---

Deleting a Group

You can delete a group and all Child groups under it.

To delete a group:

---

Step 1 Select Campus Manager > Administration > Groups.

The Group Management window appears.

Step 2 Select a group.

Step 3 Click Delete to remove the group.

Step 4 Click Yes to confirm.

The selected group is deleted.

---

Recomputing Group Membership

You can re-evaluate and re-apply the rules of a group to recompute the membership of groups.

To recompute group membership:

---

Step 1 Select Campus Manager > Administration > Groups.

Step 2 Select a group.

Step 3 Select Refresh to recompute the membership of the group.

Step 4 Click Yes to confirm.

The group membership is recomputed.

---

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

To analyze the ANI server:

---

Step 1 Go to Campus Manager > Administration > Reports.

The Reports dialog box appears with a list of reports that you can generate.

Step 2 Choose Analyze ANI Server and click Generate Report.

The ANI Server details appear.

---

Viewing Data Collection Metrics

Data Collection Metrics report gives you details about the duration of each Data Collection and the count of devices for which data was collected.

To view the Data Collection metrics:

---

Step 1 Go to Campus Manager > Administration > Reports.

The Reports dialog box appears with a list of reports that you can generate.

Step 2 Choose Data Collection Metrics.

Step 3 Enter the number of Data Collection cycles for which data is to be archived and click Apply.

The Data Collection cycles will be removed from the metrics report only after the next Data Collection.

It is not mandatory to set this property, whenever you launch the report.

Step 4 Click Generate Report.

The Data Collection metrics appear.

Table 5-13 describes the columns of the Data Collection Metrics report.

Table 5-13 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. When you click on the hyperlink, the Data Collection Detail page appears.
New Devices	Number of devices from which data was collected. When you click on the hyperlink, the Data Collection Detail page appears.
Devices Deleted	Number of devices that were deleted. When you click on the hyperlink, the Data Collection Details page appears.
Devices Per Hour	Number of devices in each hour for which data was collected.
Objects Per Hour	Number of objects in each hour for which data was collected.

---

Viewing Data Collection Details

You can launch this report from:

•Campus Manager Home page

See Table 5-14 for the description of this report.

•Data Collection Metrics Report

The Data Collection Metrics report displays the total number of Devices, the number of New Devices, and the number of Deleted Devices for which data was collected during the Data Collection cycle.

You can click on the hyperlink in the above mentioned fields to view the Data Collection Details page.

See Table 5-14 for the description of this report.

Table 5-14 Data Collection Detail

Field	Description
IPAddress	IP address of the device for which data is collected
HostName	DNS name of the device
DeviceName	DCR display name of the device
DeviceType	Type of the device for which data is collected - the device family it belongs to.
Neighbors	Host names of the neighboring devices

Viewing List of Devices Supported

You can view the icon, name and object ID of the supported devices using the Device Support option. This list does not indicate whether you have these devices in your network.

To view the devices supported:

---

Step 1 Go to Campus Manager > Administration > Reports.

The Reports dialog box appears with a list of reports that you can generate.

Step 2 Select Device Support and click Generate Report.

The details of supported devices appear.

Table 5-15 describes the columns of the Devices Supported report.

Table 5-15 Devices Supported Report 

Field	Description
Icon	Icon of the device.
Name	Name of the device.
OID	sysobject ID of the device.

---

Using Other Admin Settings

The following Administrative settings can be done from this page:

•Discrepancies

At the end of Data Collection, Campus Manager computes the Discrepancies & Best Practice Deviations present in the network. You can configure Campus Manager to:

–Receive Syslog messages for the required Discrepancies and Best Practice Deviations.

–Include only the required Discrepancies and Best Practice Deviations in reports, for which you need complete details.

For details, see Configuring Discrepancy Reporting and Syslog Message Generation.

•Purge Settings

You can configure purging interval for Campus Manager Report Jobs and Archives.

For details, see Purging Reports Jobs and Archived Reports.

•RME Server Credentials

Campus Manager uses the CLI framework (cwcli) of Resource Manager Essentials (RME) for the following functionalities:

–Fixing discrepancies and best practices deviations

–Enabling MAC notification traps

–Inter-VLAN Routing

To invoke the CWCLI commands from a remote client, you need to provide the credentials of the RME Server that you need to access.

For details, see Setting RME Credentials

Configuring Discrepancy Reporting and Syslog Message Generation

You can customize the Discrepancy Report to display only those discrepancies about which you want to be notified.

To customize the reports:

---

Step 1 Select Campus Manager > Administration > Discrepancies, from the LMS Portal.

Alternatively, if you are in Campus Manager Administration page, click Other Admin Settings and choose Discrepancies from the Table of Contents (TOC).

The discrepancies page appears. You can view the list of Network discrepancies, and Discrepancies configured to send Syslog messages by clicking the corresponding View Details link.

Step 2 Click Configure to do the required configuration.

The Configuring Network Discrepancies page appears.

•To include a discrepancy in the Discrepancy Reports, check the box next to it.

Checking all the boxes results in a report displaying all discrepancies in the network.

•To exclude a discrepancy from the Discrepancy Reports, uncheck the box.

Step 3 Select Configure Syslog to receive Syslog messages for the selected discrepancies.

Step 4 Click Next.

The list of selected discrepancies appears.

Step 5 Select Send Syslogs and enter the name of the server in the Syslog Server field.

Step 6 Click Next.

A summary of the selected discrepancies appears.

Step 7 Click Finish.

---

You can use the filters to display discrepancy reports for specific devices, link or network types. This makes it easy to find a particular discrepancy for a particular type.

You can use more than one filter at the same time, but results will vary.

•If you select more than one filter in the same top-level category, Boolean OR is used.

For example, if you select Duplex, Speed under Link, any link or port that fulfils at least one filter criteria will be displayed in the report.

•If you select more than one filter from different top-level categories, Boolean AND is used.

For example, if you select both a Link type and a Port type filter from the discrepancy filter, any link that fulfils both filter criteria will appear in the report.

Purging Reports Jobs and Archived Reports

You can purge jobs or report archives in Campus Manager. By default, purging is disabled.

To enable the Purge option for report jobs and archives:

---

Step 1 Select Campus Manager > Administration > Purge Settings.

Alternatively, if you are in Campus Manager Administration page, click Other Admin Settings tab and choose Purge Settings from the Table of Contents (TOC).

The Report Settings dialog box appears. You can specify the Purge Policy for archives or jobs here.

Step 2 Check the Purge Archives Older Than to specify the number of days, or weeks, or months to purge archives.

For instance, if you select 44 days, Campus Manager purges archives that are older than 44 days.

Step 3 Check the Purge Jobs Older Than to specify the number of days, or weeks, or months to purge jobs.

For instance, if you select 2 weeks, Campus Manager purges jobs that are older than 2 weeks.

Step 4 Click Save.

---

Setting RME Credentials

Campus Manager uses the CLI framework (cwcli) of Resource Manager Essentials (RME) for the following functionalities:

•Fixing discrepancies and best practices deviations

•Enabling MAC notification traps

•Inter-VLAN Routing

CLI framework (cwcli) is a Command-Line Interface (CLI). CLI framework (cwcli) offers remote access facilities that allow you to invoke cwcli commands from the client in the same way as they run on the RME server.

To invoke the CWCLI commands from a remote client, you must enter the credentials of the RME Server that you need to access.

For more details on CWCLI, see the section, cwcli Framework in the User Guide for Resource Manager Essentials 4.1.

CWCLI feature uses various protocols to configure devices. Details of this is available in the help page for RME > Admin> Config Mgmt > Transport Settings, and in the User Guide for Resource Manager Essentials 4.1.

To set RME credentials:

---

Step 1 Go to Campus Manager > Administration > RME Server Credentials.

Alternatively, if you are in Campus Manager Administration page, click Other Admin Settings tab and select RME Server Credentials from the Table of Contents (TOC).

The RME Credentials dialog box appears.

Step 2 Enter details in the RME Credentials dialog box.

Table 5-16 describes the fields in the RME Credentials dialog box.

Table 5-16 RME Credentials 

Field	Explanation
RME Server Name	DNS name or IP address of the RME server. local host or 127.0.0.1 should not be given.
RME Server Port	Port number of the RME server. For example, 1741. For https, the port number is 443.
RME Server Protocol	Protocol used by RME server. For example, http or https.
User Name	User name of the RME server.
User Password	Password of the RME server.
Verify User Password	Password of the RME server for confirmation.

If you have specified https as the server protocol, make sure that the Peer Server Certificate is properly imported. Peer Server Certificate is mandatory for communication between CiscoWorks servers in SSL mode.

To add Peer Server Certificate, go to Common Services > Server > Security> Peer Server Certificate Setup. Launch Help and follow the instructions to add the certificate.

Step 3 Click OK to apply the changes

or

Click Cancel to discard the values you have entered.

---

Possible Cause and Solution for Error Conditions

If you cannot connect to the RME server, it could be because of the following reasons:

•RME Server name or IP address is wrong.

Enter correct DNS name or IP address of the RME server. Do not enter local host or 127.0.0.1.

•RME Server Protocol is wrong.

Enter either http or https as the server protocol.

•RME Server Port is wrong.

Port number for http is 1741 and that for https is 443.

•RME Server is down.

Try connecting to the server after it is up.

•RME Server is not installed in the specified machine.

Either:

–Install RME in the specified machine and try again.

Or:

–Provide machine details where RME is installed.

•Peer Server Certificate is not imported properly

If you have specified https as the server protocol, make sure that the Peer Server Certificate is properly imported. Peer Server Certificate is mandatory for communication between CiscoWorks servers in SSL mode.

To add Peer Server Certificate, go to Common Services > Server > Security> Peer Server Certificate Setup. Launch Help and follow the instructions to add the certificate.

Setting Debugging Options

When you face issues in running Campus Manager, you can enable logging to debug the same. You can set debugging options for the following functions:

•Data Collection (see Setting up Debugging Options for Data Collection)

•Configuration and Reports (see Setting up Debugging Options for Configuration and Reports)

•Device Groups (see Setting Debugging Options for Device Groups)

•Topology (see Setting Debugging Options for Topology)

•User Tracking Server (see Debugging Options for User Tracking Server)

•Dynamic User Tracking (see Debugging Dynamic Updates)

•User Tracking Reports (see Debugging Options for User Tracking Reports)

•Dynamic User Tracking Console (see Dynamic User Tracking Console)

Setting up Debugging Options for Data Collection

You can set the trace, and debugging, for Campus Manager Data Collection as follows:

---

Step 1 Select Campus Manager > Administration >Debugging Options >Data Collection.

The Debugging Options dialog box appears.

Step 2 Modify the debugging options as specified in Table 5-17.

Table 5-17 Data Collection Debugging Options  for Data Collection

Field	Description	Usage Notes
Enable Debug	Select this option to enable logging for Data Collection.	You can select the modules for debugging only if 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 you want to enable debug. For details on Debug modules, see Selecting Data Collection Debug Modules
File Name	Name of the log file in which the trace messages are to be recorded.	The default log file is NMSROOT\log\ani.log
Maximum File Size (lines)	Maximum size of the log file in lines
Enable Device Level Debugging
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 3 Click Apply.

---

Selecting Data Collection Debug Modules

Table 5-18 describes the debug modules available for Data Collection in Campus Manager.

Table 5-18 Data Collection Debug Modules 

Module	Description
framework	•Constructs and maintains data in the memory. •Provides framework for Campus Manager features. Enable debugging for this module only when requested by TAC. This is because enabling debugging for this module creates huge logs.
topo	Provides network topology computation and layouts. Enable debugging for this module if you have problems with Topology computation of devices.
vlad	•Discovers VTP domains, VLANs, port-in-VLAN configurations •Performs VLAN configuration tasks •Determines Spanning Tree state Enable debugging for this module if you have problems with VTP, VLAN reports, and configuration.
ccm	Discovers Cisco CallManager (CCM). Enable debugging for this module if you encounter issues with data collected for CCM.
vmpsadmin	•Discovers end-user hosts on the network •Records end-user host information in the ANI database •Manages requests for scheduling user and host discoveries, ping sweeps, database queries, and updates to user and notes information •Provides subnet to VLAN mapping information to path service module Enable debugging for this module if you have problems with User Tracking.
lane	•Discovers individual LANE components (LECS, LES/BUS & LEC) for both Ethernet and Token Ring networks •Discovers LEC to VLAN index mapping (used for ATM-VLAN to VLAN mapping) •Determines logical ATM-VLANs from the discovered individual LANE components •Determines ATM-VLAN to Ethernet and Token Ring VLAN associations Enable debugging for this module if you have problems with LAN Emulation reports and configuration.
laneconfiguration	Performs LANE configuration tasks
dcrp	Provides computation of network discrepancies. Enable debugging for this module if you have problems in Discrepancy reports.
status	Enables status polling on previously discovered devices. Enable debugging for this module if you have problems with device and link status polling.
path	Determines the path between a pair of endpoints. Enable debugging for this module if you have problems in Path Tracing.
atm	Performs ATM-related configurations, such as: •SPVC provisioning •ATM RMON configuration and data polling •OamPing •ATM interface configuration Enable debugging for this module if you have problems with ATM reports.
apps	Discovers application hosts such as MCS. Enable debugging for this module if you encounter issues with data collected on application hosts.
stp	Discovers all STP related information from the network. Enable debugging for this module if you have problems with STP reports and configuration.
stpeng	•Performs STP configuration tasks •Provides basic STP analysis for migration from one STP type to another Enable debugging for this module if you have problems with STP reports and configuration.
devices	Provides specific information, if any, available for device categories. Enable debugging for this module if you have problems specific to a particular device type.

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

Setting up Debugging Options for Configuration and Reports

If you need information on Configuration and Reports in Campus Manager, you can enable debugging for the same. To do this:

---

Step 1 Select Campus Manager > Administration > Debugging Options >Configuration and Reports.

The debugging page appears.

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

•INFO

Only informational messages are recorded in the log file.

•DEBUG

All messages related to Configuration and Reports are recorded in the log file.

•FATAL

Messages related to fatal errors are recorded in the log file. This is the default option.

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

Step 3 Click Apply.

---

Setting Debugging Options for Device Groups

If there are errors related to System defined or User defined groups in Campus Manager, you can enable debugging for the same. Its done as follows:

---

Step 1 Select Campus Manager > Administration > Debugging Options >Device Groups.

The debugging page appears.

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

•INFO

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

•DEBUG

All client side messages are recorded in the log file.

•FATAL

Messages related to fatal errors 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\CampusDeviceSelector.log

Step 3 Click Apply.

---

Setting Debugging Options for Topology

You can enable debugging for Topology Services client side activities. The debugging information will be available in the Java Console.

To display Java Console:

---

Step 1 Select Start > Settings > Control Panel > Java.

Step 2 Select the Advanced tab.

The corresponding tree structure is displayed.

Step 3 Go to the tree and select Java Console > Show Console.

Step 4 Click Apply and then OK.

The Java console is displayed when you launch Topology Services.

---

Note In case you close the Java Console, to reopen it, close the Topology window and relaunch it.

---

---

To enable debugging:

---

Step 1 Select Campus Manager > Administration > Debugging Options >Topology.

The debugging page appears.

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

•TRACE

Only informational messages are displayed in the Java Console.

•DEBUG

All Topology Services client side messages are displayed in the Java Console.

•ERROR

Messages related to all errors are displayed in the Java Console. This is the default option.

Step 3 Click Apply.

---

To change log level settings:

---

Step 1 Close the Topology Services window.

Step 2 Change the settings in the Campus Manager Administration page.

Step 3 Re-launch Topology services.

---

Using Campus Manager Job Browser

The Campus Manager Job Browser enables you to view the status of all Campus Manager Jobs (User Tracking jobs, Path Analysis jobs, Campus Manager reports).

The job details that you can view here include the job ID, the job type, the job status, the job description, the job owner, the time the job is scheduled to run at, the time of job completion, and the schedule type.

To open the job browser, select Campus Manager > Job Management.

The Campus Manager Job Browser appears.

You can filter the jobs by any specified criteria using the Show Only drop-down list. Select your criteria. The jobs pertaining to that category are displayed.

Table 5-19 displays the fields in the Campus Manager Job Browser.

Table 5-19 Campus Manager Job Browser 

Column	Description
Job ID	Unique ID of the job. For example, 1007.0. Job IDs have N.x format, where x stands for the number of instances of that job. For example, 1007.4 indicates that the Job ID is 1007 and it is the fifth instance of that job.
Job Type	Type of job. The jobs include, User Tracking jobs, Path Analysis jobs, Campus Manager reports.
Description	Description of the job.
Owner	Username of the job creator.
Scheduled At	Date and time at which the job was scheduled.
Completed At	Date and time at which the job was completed.
Schedule Type	Type of job schedule—daily or periodic.
Status	Status of the job—Scheduled, Succeeded, Failed, Cancelled, Stopped, Running, Missed Start.

Click the Refresh icon to refresh the Campus Manager job browser.

Use the Stop and Delete buttons to stop or delete jobs:

•Stop button—Stops or cancels a running job. You will be prompted to confirm the cancellation of the job.

However, the job is stopped only after the devices currently being processed are successfully completed. This is to ensure that no device is left in an inconsistent state.

•Delete button—Deletes the selected job from the job browser. You can select more than one job to delete. You will be asked to confirm the deletion.

---

Note You cannot delete a running job.

---

Administration Command Line Interface

This section describes how to administer Campus Manager database from the command line. This is explained in the following topics:

•Replacing Corrupted Database

•Re-initializing the Database

•Deleting all Active Entries from User Tracking, and Restarting Servers

•Deleting all Inactive Entries from User Tracking, and Restarting Servers

•Deleting all History Entries from User Tracking, and Restarting Servers

•Deleting all User Tracking Entries, and Restarting Servers

•Restoring the Original Data in the Server

•Restoring Data from Another Server

•Performance Tuning Tool

•Configuration Settings for SNMPv3 Devices

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

The following message appears:

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.

Deleting all Active Entries from User Tracking, and Restarting Servers

From the command prompt or shell window, enter:

•On Solaris: NMSROOT/campus/bin/reinitdb.pl -ut

•On Windows: perl NMSROOT\campus\bin\reinitdb.pl -ut

where active entries are hosts that are currently logged in

Deleting all Inactive Entries from User Tracking, and Restarting Servers

From the command prompt or shell window, enter:

•On Solaris: NMSROOT/campus/bin/reinitdb.pl -ut -inactive

•On Windows: perl NMSROOT\campus\bin\reinitdb.pl -ut -inactive

where inactive entries are hosts that are currently not logged in

Deleting all History Entries from User Tracking, and Restarting Servers

From the command prompt or shell window, enter:

•On Solaris: NMSROOT/campus/bin/reinitdb.pl -ut -history

•On Windows: perl NMSROOT\campus\bin\reinitdb.pl -ut -history

where history entries are complete entries. That is, hosts that have a login and logout in the past.

Deleting all User Tracking Entries, and Restarting Servers

From the command prompt or shell window, enter:

•On Solaris: NMSROOT/campus/bin/reinitdb.pl -ut -all

•On Windows: perl NMSROOT\campus\bin\reinitdb.pl -ut -all

Restoring the Original Data in the Server

From the command prompt or shell window, enter:

•On Solaris: NMSROOT/campus/bin/reinitdb.pl -restore

•On Windows: perl NMSROOT\campus\bin\reinitdb.pl -restore

---

Note Before executing the -restore command, you should stop the daemon manager and start again manually. For details, see Using Daemon Manager.

---

Restoring Data from Another Server

When you take database backup for Campus Manager in one server and restore it in another server, the NMSROOT logfile location may not be the same in both servers.

In that case, Campus Manager will log messages to the log file stored in the default NMSROOT location in the restored machine.

where NMSROOT is the root directory where you installed CiscoWorks.

Performance Tuning Tool

When you get out of memory errors in Campus, the following command can be used to tune the performance:

NMSROOT/bin/perl NMSROOT/campus/bin/CMPTT.pl ProcessName HeapSize MaxPermSize

•ProcessName should be either one of the following:

–ANIServer

–UTMajorAcquisition

•Heap size should be multiples of 512 and should not exceed 1536 MB.

Ensure you have enough swap space in the server before tuning the heap size.

•MaxPermSize will set the JVM MaxPermSize option to 64m.

Configuration Settings for SNMPv3 Devices

Campus Manager supports the following Authentication protocols for SNMP v3:

•md5

•SHA

Campus Manager supports the following Privacy protocols for SNMP v3:

•des

•3des

•aes128

•aes192

•aes256.

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

For Catalyst devices, enter the following command:

set snmp view campusview 1.3.6.1 included nonvolatile

For IOS devices, enter the following command:

snmp-server view campusview oid-tree included

Configuring Access Groups

You must set the access rights for a group with a certain security model in different security levels.

For Catalyst devices, enter the following command:

set snmp access campusgroup security-model v3 authentication read campusview write campusview nonvolatile

For IOS devices, enter the following command:

snmp-server group campusgroup v3 auth read campusview write campusview access access-list

Configuring Device with Context Name

For Catalyst devices, enter the following commands:

set snmp access campusgroup security-model v3 authentication read campusview write campusview context vlan- prefix nonvolatile

Context exact is also supported. The following is an example:

set snmp access campusgroup security-model v3 authentication read campusview write campusview context vlan-1 exact nonvolatile

For IOS devices, enter the following command:

snmp-server group campusgroup v3 auth context vlan-1 read campusview write campusview

IOS image versions prior to12.4 support only exact context name.

IOS image versions 12.4 or higher, support both exact or prefix context names.

You need to configure the device with and without context name, since Data Collection manages the device without context name and User Tracking requires context name to contact the device.

Configuring a New User

For Catalyst devices, enter the following command:

set snmp user campususer authentication md5

For IOS devices, enter the following command:

snmp-server user campususer campusgroup v3 auth md5 password1

Configuring Password for a User

For Catalyst devices, enter the following command:

set snmp user campususer authentication md5 password1

For IOS devices, enter the following command:

snmp-server user campususer campusgroup v3 auth md5 password1

Relating a User to a Group

Using a specified security model you can relate a user to a group.

For Catalyst devices, enter the following command:

set snmpw group campusgroup user campususer security-model v3 nonvolatile

For IOS devices, enter the following command:

snmp-server user campususer campusgroup v3

Configuring Privacy Protocol

For Catalyst devices:

set snmp user campususer authentication md5 password1 privacy des password2

For IOS devices:

snmp-server user campususer campusgroup v3 auth md5 password1 priv des password2

Security

After a period of inactivity, the LMS Portal page times out and is no longer accessible. Close all browser instances and relaunch CiscoWorks.

Frequently Asked Question

Q. I have an office with 300 remote branches each with a Cisco router. The routers are connected to the head office over an SP infrastructure and IPSec is used to encrypt the traffic between the remote branches and the head office. How do I manage the devices in the remote network using Campus Manager?

A. If you want to discover and manage the devices in the remote network, add those as seed devices in Campus Manager.