-
User Guide for Campus Manager 5.2 (with LMS 3.2)
-
Notices
-
Preface
-
Chapter 1 About Campus Manager
-
Chapter 2 Whats New in Campus Manager
-
Chapter 3 Getting Started with Campus Manager
-
Chapter 4 Integrating Campus Manager With CiscoWorks
-
Chapter 5 Administering Campus Manager
-
Chapter 6 Generating Reports
-
Chapter 7 Tracking Users
-
Chapter 8 Discrepancies and Best Practices Deviations
-
Chapter 9 Using Topology Services
-
Chapter 10 Managing VLANs and VTP
-
Chapter 11 Managing Network Spanning Trees
-
Chapter 12 Support for IPv6
-
Chapter 13 Data Extraction Engine
-
Chapter 14 Virtual Network Manager
-
Chapter 15 Troubleshooting and FAQs
-
Index
-
Table Of Contents
Understanding Campus Manager Administration
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
Manually Including Devices to Data Collection
Manually Excluding Devices from Data Collection
Using Advanced Search in CM Device Selector
Overview of Subnet Based Groups
Viewing Data Collection Metrics
Viewing Data Collection Details
Viewing List of Devices Supported
Configuring Discrepancy Reporting and Syslog Message Generation
Purging Reports Jobs and Archived Reports
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
Starting Campus Manager Applications
Administering Campus Manager
Network administrators can perform administrative tasks on Campus Manager applications using the Administration module. This chapter contains:
•
Understanding Campus Manager Administration
•
•
•
•
•
Understanding Campus Manager Administration
There are two main processes in Campus Manager:
•
Fetches the device list from DCR and collects the following data from the network:
–
–
–
–
–
–
•
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.
This section explains:
Note
You can do the following settings from Campus Manager Administration:
•
–
–
–
For details, see Viewing Summary of Data Collection Settings.
•
–
–
For details, see Configuring Topology 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.
•
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 and view reports on:
–
–
–
For details, see Using Administration Reports
•
–
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.
–
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.
–
Configure Purge settings for jobs or report archives For details, see Purging Reports Jobs and Archived Reports.
•
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:
•
•
•
•
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.
This section explains:
•
•
Restarting Daemon Manager on Solaris
To restart daemon manager on Solaris:
Step 1
Step 2
/etc/init.d/dmgtd stop
Step 3
/etc/init.d/dmgtd start
Restarting Daemon Manager on Windows
To restart daemon manager on Windows:
Step 1
Step 2
net stop crmdmgtd
Step 3
net start crmdmgtd
Note
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.
•
•
Selective Backup and Restore
You can selectively back up files from the LMS 3.2 Server and restore them only on this LMS 3.2 Server. You can also selectively back up and restore the configuration files and specific tables in databases.
You can also backup the schema, stored procedures, and select tables specified in the configuration file of Campus Manager. The selected tables include all dependent table for proper functioning, as a part of Restore.
For tables that are not specified in the configuration file of Campus Manager, blank tables are created so that Campus Manager can function properly.
You can restore the settings similar to a normal backup with no data or little data. You can restore the settings, using the CLI function on Windows and Solaris. Only configurable files and data from the database will be backed up as part of a selective backup.
This section contains:
Files used for backup
For selective backup, the following two files are used:
•
–
–
where, NMSROOT— CiscoWorks installed directory
•
–
–
where, NMSROOT— CiscoWorks installed directory
•
–
–
–
–
Backing up Using CLI
To back up data, using only CLI on Windows and Solaris:
On Windows, run:
NMSROOT\bin\perl NMSROOT\bin\backup.pl -dest=BackupDirectory [-system]
[-log=LogFile] [-email=E-mail][-gen=Num_Generations]
On Solaris, run:
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/backup.pl -dest=BackupDirectory [-system]
[-log=LogFile] [-email=E-mail] [-gen=Num_Generations]
where,
•
•
•
•
•
Backing up View
If you backup a view, it cannot be restored. To get the latest view details, you need to freshly install a view by invoking:
NMSROOT/bin/perl NMSROOT/bin/dbaccess.pl install
As a prerequisite to installing a view, you must run Data Collection and User Tracking.
Normal Backup
In case of normal backup, to backup a view, you need to freshly install a view by invoking:
NMSROOT/bin/perl NMSROOT/bin/dbaccess.pl install.
As a prerequisite to installing a view, you must run Data Collection and User Tracking.
If you modify various Network Topology View features and take a backup of Topo Map Preferences. The topo map views that are backed up cannot be restored because the map views are dynamically generated.
The following data is backed up when you run a backup from the user interface or from CLI without
entering the -system option:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Selective Backup
When you run a backup from CLI with -system option, all the above-mentioned data gets backed up except:
•
•
•
Discovery Settings will be migrated for LMS 3.0 or lower versions.
After the completion of selective backup and restore, you must run Data collection before executing VNM workflows.
Note
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 :
•
For details, see System Status
•
For details, see Discrepancies and Best Practices Deviations
•
For details, see Recently Completed Jobs
•
For details, see Campus Manager Tasks and Reports
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.
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 jobs that were completed recently:
•
•
•
•
•
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 Campus Manager Job Browser page.
Campus Manager Tasks and Reports
The Campus Manager homepage provides hyperlinks to the following tasks and reports:
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/SNMPv2 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.
Topology Services
Launches the Campus Manager Topology Services window.
VLAN Port Assignment
Launches the Campus Manager VLAN Port Assignment window.
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.
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.
MAC Reports
Displays the User Tracking Report Generator from you can generate reports on new MACs, Rogue MACs and dormant MACs in the network.
For more information, see Viewing MAC 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.
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 Ports Report
Lists administratively down ports, which are not connected to any end host or device.
For details see, Understanding Switch Port Usage Reports.
Reclaim Unused Up Ports Report
Lists administratively up ports, which are not connected to any end host or device. 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:
•
•
•
•
•
•
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
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
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:
•
•
•
•
•
•
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.
The SNMP fallback methodology applicable for Data Collection, UT Acquisition, and Dynamic UT is as follows:
•
•
To modify SNMP timeouts and retries:
Step 1
The SNMP Timeouts and Retries dialog box appears.
Step 2
Step 3
Step 4
•
Or
•
Click OK to save the changes or click Cancel to exit.
Step 5
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 device groups to include devices in data collection. In addition to these, 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:
•
•
Mode and Policy Settings
You can control the mode in which Data Collection runs as well as specify filters as follows:
•
Enable Auto Mode
This option is selected by default. This indicates that Campus Manager Data Collection happens in the Auto mode. This mode works in tandem with the Manual mode policies. When you deselect this, Campus switches to the Manual mode of Data Collection and all filters set in the Auto mode are dropped.
Specifying Auto Allocation Rules
In Auto mode you can either manage all devices or manage devices in groups.
There are two types of groups available:
•
System defined groups are automatically created, based on the information in DCR.
•
You can create User Defined groups based on your requirement. For example, if you want to manage only devices with the IP address 10.77.*.* in Campus Manager:
–
–
–
Now the devices with the IP address 10.77.*.* will be managed in Campus Manager.
For more details on Group Creation, see the User Guide for Common Services 3.3.
To combine Auto mode policies with Manual mode, see:
•
•
To set Auto Allocation rules:
Step 1
The Auto Allocation Settings dialog box appears.
Step 2
–
This setting indicates that all devices in DCR will be managed by Campus Manager (as per the license limit). If you select this, skip Step 3.
–
This setting indicates that only the devices belonging to the selected groups will be managed by Campus Manager.
Step 3
Step 4
If you selected Manage All Devices, the settings will be applied. All devices will be managed in Campus Manager in the next Data Collection. Skip Step 5.
If you selected Manage by Groups, the Auto Allocation Summary window appears with the information, as explained inTable 5-4:
.
Table 5-4 Data Collection Filters
Number of devices currently managed
Number of devices currently managed in Campus Manager.
Number of new devices after this rule change
Number of devices that will be added to Campus Manager, after the settings are applied. Clicking on the number launches the device list.
For the Manage by Groups setting:
If a device has different display names, the same IP address, and belongs to two different groups, it is listed twice in the report.
Number of devices that will be deleted after this rule change
Number of devices that will be deleted from Campus Manager, after the settings are applied. If you click on the number, it launches the list of devices marked for deletion.
For the Manage by Groups setting:
If a device has different display names, the same IP address, and belongs to two different groups, it is listed twice in the report.
Total number of devices after this rule change
Total number of device that will be managed in Campus Manager after the settings are applied.
This is the sum/difference of already managed devices and the devices added/deleted from the rule change.
Current license limit
Maximum number of devices that you can manage as per the LMS license you have purchased. For more details on this, see Installing and Getting Started guide published at http://cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html
Run Data Collection Immediately after applying the settings
Runs Data Collection immediately after applying the settings.
Step 5
The rules set come into effect only in the next Data collection cycle.
Example
Consider the following scenario:
The following devices are managed in Campus Manager:
•
•
•
To understand the device count in the Auto Allocation Summary window, assume the following:
•
•
•
–
–
–
–
–
•
•
Now the details of Auto Allocation Summary are:
–
–
–
–
–
Points to be noted:
•
•
•
This group will be selected automatically as an Auto mode setting. This conversion will happen immediately after migration, during ANIServer startup.
If the filter migration fails due to any issues, the filter value will be saved as comment (preceded with # symbol) in the ANIServer.properties file.
•
–
–
All Auto and Manual mode policies will be deleted. Data Collection will be triggered on Manual mode and will delete all previously managed devices from the Campus Manager database. You have to set new policies and run Data Collection again to manage devices in Campus Manager.
•
–
–
–
–
Auto Allocation mode is preserved.
•
But in the mode and policy settings page, when you click on "Number of new Devices after the rule change link" in the summary page, both authorized and unauthorized devices are listed— if you have included unauthorized devices for managing in Campus.
After you run Data collection, only the authorized devices are shown in Campus Manager.
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 along with the Auto mode or can work independently. This implies:
•
•
•
For example, If you set a Data Collection filter to exclude the devices belonging to the address range 10.77.*.* or 10.77.[0-255].[0-255], but manually add 10.77.2.1, this device will be included in the consecutive Data Collection cycle.
•
•
To manually include devices:
Step 1
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
The devices that are already being managed by Campus Manager will not be present in the Add list.
Step 3
These devices will be included in the next Data Collection process.
Note
Manually Included Devices Report
This report gives the details of devices that are manually included from Campus.
To view the report:
Step 1
Step 2
The report displays information as described in Table 5-5:
To exclude a device from the Included list, select the device and click Exclude.
To get more clarity on Device Management, see FAQs.
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:
•
•
•
For example, If you set a Data Collection filter to include the devices belonging to the address range 10.77.*.* or 10.77.[0-255].[0-255], but manually exclude 10.77.1.3, the device 10.77.1.3 will be excluded in the Data Collection process.
•
•
To manually exclude devices:
Step 1
The Exclude Devices page is displayed with the following groups:
–
–
–
Step 2
Step 3
These devices will be excluded from the list of devices managed by Campus Manager.
Note
Manually Excluded Devices Report
This report gives the details of devices that you manually excluded from Campus Manager.
To view the report:
Step 1
The Exclude Devices page is launched.
Step 2
The report displays information as given in Table 5-6:
Table 5-6 Manually Excluded Devices Report
IP Address
IP Address (IPv4 or IPv6 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.
Using Advanced Search in CM Device Selector
You can use the Advanced Search icon to specify a set of rules for advanced search. Advanced search is based on the Grouping Services attributes of Grouping Services Server of Campus Manager. In the Advanced Search dialog box, you can create rules to search for devices.Figure shows the Advanced Search dialog box.
The dialog box contains the following fields and buttons as mentioned in Table 5-7
Table 5-7 CM Advanced Search Dialog Box
Device Name
Name of the device.
Object Type
Type of object (device) that is used to form a group.
Variable
Device attributes based on which you can define the group. See Rules Editor.
Operator
Operator to be used in the rule. The list of possible operators changes based on the Variable selected.
Value
The value of the rule expression. The possible values depend upon the variable and operator selected. Depending on the operator selected, the value may be free-form text or list of values.
The wildcard characters are not supported.
Add Rule Expression
Used to add the rule expression to the group rules.
Rule Text
Displays the rule.
Check Syntax
Verifies that the rule syntax is correct. Use this button if you have entered the rules manually.
Search
Used to search for devices based on the defined rule.
Usage Notes
The following are the usage notes for Advanced Search:
•
•
Each rule expression contains the following:
object type.variable operator value
Object Type—The type of object (device) that is used to form a group.
Variable—Device attributes, based on which you can define the group. See the Rules Editor.
Operator—Operator to be used in the rule. The list of possible operators changes based on the Variable selected.
Value—Value of the rule expression. The possible values depend upon the variable and operator selected. Depending on the operator selected, the value may be free-form text or a list of values.
•
object type.variable operator value
•
You must use Check Syntax button only when you add a rule manually or when you modify a rule expressions in the Rule Text.
•
•
•
For information on the rules used to perform advanced search, refer Rules Editor.
Scheduling Data Collection
To schedule data collection:
Step 1
The Data Collection Schedule dialog box appears.
Step 2
•
•
•
Step 3
Best Practices
Be cautious while scheduling Data Collection:
•
•
Device Poller
Campus Manager polls the entire network for device and link status periodically.This feature allows you to:
•
•
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
Step 2
To add a device to the Critical Devices list from N-Hop View Portlet:
Step 1
Step 2
For complete details on N-Hop view portlet, see N-Hop View Portlet.
Caution
To configure Device Poller:
Step 1
The Device Poller screen is displayed.
Step 2
Step 3
Configuring Topology Settings
You can configure the following Topology Settings:
•
•
Restricted Topology View
Topology Maps display all the devices discovered by Campus Manager. When Campus Manager is integrated with the ACS server, you can set Topology Maps to display only the devices you are authorized to view. To do that:
Step 1
The configuration screen is displayed.
Step 2
This option is enabled only when Campus Manager is integrated with the ACS server.
Step 3
Topology Maps display only the devices you are authorized to view. If Topology Services is already launched, close it and relaunch for the change to take effect.
Points to be Noted
If you change the management IP address of an authorized device:
•
•
•
To avoid the above mentioned issues, you must maintain the same management IP address for the device in Topology Services and in the ACS server.
Configuring DFM Polling
To display DFM information in Topology Maps and N-Hop view portlet, you have to enable polling as follows:
Step 1
The configuration screen is displayed.
Step 2
If you try to apply the settings when DFM is not installed on a local or remote server, you will get an error message indicating the same.
If DFM is installed, the list of DFM servers detected is displayed above this check-box.
You can enable this option, only if:
–
AND
–
If DFM is installed after running Data Collection, either run Data Collection or restart ANI Server before enabling the above setting.
Step 3
DFM updates the latest alert information every 6 minutes. So the time interval can be a value between six minutes and fifty nine minutes, fifty nine seconds.
Step 4
The settings are saved to the server and polling starts within six minutes of the configuration.
In addition to this, you can restrict the type of DFM alert displayed in your machine. For example you can choose to display only critical alerts in Topology maps. To do that, see Modifying DFM Alert Settings.
To restrict the type of alerts displayed in N-hop view Portlet, see Configuring the Portlet.
The alert information fetched from DFM can be launched from Topology Maps and N-Hop view portlet, by right clicking on the required device. For details, see Starting CiscoWorks Applications From Topology Views.
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:
•
•
•
This section explains:
•
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:
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.
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:
•
•
•
•
System Defined Groups
A System Defined Group is a top-level container for standard groups that are accessible to and used by most Campus Manager users. These groups are pre-defined by Campus Manager.
The predefined sub-groups under System Defined Groups are:
•
•
These subnet folders are of the form: subnet — subnet mask
eg: 10.77.209.48 — 255.255.255.240
You cannot:
•
•
Based on your requirements, you can create customized groups under User Defined Groups.
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:
Device.SystemContact equals "Joe Smith" ORDevice.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. These are a part of System defined groups. You cannot create, edit or delete them.
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
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,
Device.IP.Subnet equals "172.20.104.192" AND 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
When you need to create subnet based groups as per network requirements, you can do it under User defined groups.
For example, the following rules might be used to create two groups based on the IP address subnet:
Device.IP.Subnet equals "172.29.252.32"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:
DeviceVariable
Any of the attributes of a device. Table 5-10 gives details on the available variables:
Operator
The operator used in forming a rule. The following operators are available:
–
–
•
•
–
–
–
–
•
–
–
–
–
–
IP Address Range Operator
The range operator enables you to group the devices of the specified range of IP Addresses. You can select the range operator only for the IPAddress variable. You should enter the range of IP Addresses in the Value field, to create a group rule based on IP Address ranges.
When you enter the IP Address range in the text field, you should:
•
•
•
•
For example, you can enter 10.10.10.[0-255] or 10.10.[0-255].[0-255] in the Value field.
You should not:
•
•
•
Value
A free flow operand forming the last part of the rule.
When the variable DiscoveryStatus is used, only the following values are available:
•
•
•
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.
This section contains:
•
•
Rule for a System Defined Group
•
Device.SystemLocation equals "Bldg 1 Devices"where
Variable is SystemLocation
Operator is equals
Value is Bldg 1 Devices
•
Device.IpAddress equals "172.20.121.10"In addition you can use the contains operator to match a value anywhere in the attribute:
Device.IPddress contains "10"The above rule, will match devices with IP address like 172.20.10.3, 172.25.3.101 etc.
To group all devices whose IP Addresses are within the range 10.10.0.0 to 10.10.50.255, the group rule is:
Device.IPAddress range "10.10.[0-50].[0-255]"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:
Device.SystemContact equals "J Smith Devices"Composite Rule
Composite rule contain more than one rule expression separated by a Boolean operator.
The Boolean Operators OR, AND, or EXCLUDE appear in the Rules:Create dialog box only when you have entered at least one rule expression.
When the composite rule has more than two simple rule expressions, you can adjust priorities among the expressions using opening and closing parenthesis.
In the above 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:
Device.DeviceLabel equals "Lab Test Setup" ANDDevice.SystemContact equals "J Smith Devices"Rule for Include Devices
Simple Rule for Include Devices contains a common parameter: CMF:DCR:Device. The Device Management filters the devices based on the rule you have specified in the Defined Advanced Search Rules dialog box.
For example, the rule type:
:CMF:DCR:Device.DisplayName equals "joe"will select the device with the DisplayName joe.
Rule for Exclude Devices
Simple Rule for Exclude Devices contains a common parameter: Device.The Device Management filters the devices based on the rule you have specified in the Defined Advanced Search Rules dialog box.
For example, the rule type:
Device.HostName equals "Saturn"will filter the Devices with common host name, Saturn.
For more information on creating groups, refer Creating Rules for Groups.
Using Groups
The main tasks that you can perform using groups are:
All actions begin from the Topology Groups administration page, unless otherwise specified.
Access control to groups is controlled on a username basis.
By default, read permission is granted to System Defined Groups, and read write and evaluate permissions are granted to User Defined Groups.
The User Defined Groups folder is meant to hold a users private group and/or groups that are more transient in nature.
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
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
The Group Management window appears.
Step 2
The Properties: Create window opens.
Step 3
Step 4
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
Table 5-12 describes the fields in the Rule Expression area.
Table 5-12 Rules: Create Field Description
—
Select the Boolean expression.
•
•
•
The Boolean Operators OR, AND, or EXCLUDE appear in the Rules:Create dialog box only when you have entered at least one rule expression.
For an example of Composite rule using boolean operatots, see Composite Rule.
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:Device
Variable
Attribute of a device. The available variables are:
•
•
•
•
•
•
•
•
•
•
•
•
For more details, see Rules Editor.
Operator
Operator used in forming a rule.
For a variable equal to DiscoveryStatus, the only available Operator variables is equals.
For all the variables, the available Operator variables are:
•
•
•
•
Apart from the operator variables listed above, for variable equal to IPAddress or IP.SubnetMask or IPv6.Subnet or IPv6.SubnetMask, an extra Operator variables range is added.
For more details, see Operator.
Value
Enter the desired value for the variable you have selected.
Step 2
The Rule Text field shows the rule you are creating.
You can also enter the rules directly in the Rule Text field.
To see an example of a rule, see Example of Rule.
Step 3
Step 4
Step 5
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
Step 2
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
Table 5-13 describes the entries in the Summary: Create table.
Step 4
•
or
•
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:
•
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.
•
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
You can modify the Group Name, Description, and Membership Update Type.
Step 2
•
•
•
Step 3
Viewing Group Details
To view the attributes of a group:
Step 1
Step 2
Group information is displayed in the right window.
•
•
•
Deleting a Group
You can delete a group and all Child groups under it.
To delete a group:
Step 1
The Group Management window appears.
Step 2
Step 3
Step 4
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
Step 2
Step 3
Step 4
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
The Reports dialog box appears with a list of reports that you can generate.
Step 2
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
The Reports dialog box appears with a list of reports that you can generate.
Step 2
Step 3
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
The Data Collection metrics appear.
Table 5-14 describes the columns of the Data Collection Metrics report.
Viewing Data Collection Details
You can launch this report from:
•
See Table 5-15 for the description of this 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-15 for the description of this report.
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
The Reports dialog box appears with a list of reports that you can generate.
Step 2
The details of supported devices appear.
Table 5-16 describes the columns of the Devices Supported report.
Table 5-16 Devices Supported Report
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:
•
At the end of Data Collection, Campus Manager computes the Discrepancies & Best Practice Deviations present in the network. You can configure Campus Manager to:
–
–
For details, see Configuring Discrepancy Reporting and Syslog Message Generation.
•
You can configure purging interval for Campus Manager Report Jobs and Archives.
For details, see Purging Reports Jobs and Archived Reports.
•
Campus Manager uses the CLI framework (cwcli) of Resource Manager Essentials (RME) for the following functionalities:
–
–
–
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 and the Best Practice Deviation Report to display only those discrepancies about which you want to be notified.
To customize the reports:
Step 1
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
The Configuring Network Discrepancies page appears.
•
Checking all the boxes results in a report displaying all Discrepancies/Best Practice Deviations in the network.
•
Step 3
Step 4
The list of selected Discrepancies and Best Practice Deviations appears.
Step 5
Step 6
A summary of the selected Discrepancies and Best Practice Deviations appears.
Step 7
You can use the filters to display Discrepancy/Best Practice Deviation reports for specific devices, link or network types. This makes it easy to find a particular Discrepancy/Best Practice Deviation for a particular type.
You can use more than one filter at the same time, but results will vary.
•
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.
•
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
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
For instance, if you select 44 days, Campus Manager purges archives that are older than 44 days.
Step 3
For instance, if you select 2 weeks, Campus Manager purges jobs that are older than 2 weeks.
Step 4
Setting RME Credentials
Campus Manager uses the CLI framework (cwcli) of Resource Manager Essentials (RME) for the following functionalities:
•
•
•
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.3.
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.3.
To set RME credentials:
Step 1
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
Table 5-17 describes the fields in the RME Credentials dialog box.
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
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:
•
Enter correct DNS name or IP address of the RME server. Do not enter local host or 127.0.0.1.
•
Enter either http or https as the server protocol.
•
Port number for http is 1741 and that for https is 443.
•
Try connecting to the server after it is up.
•
Either:
–
Or:
–
•
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
If you face issues while running Campus Manager, you can enable logging to debug the same. You can set debugging options for the following functions:
•
•
•
•
•
•
•
•
Setting up Debugging Options for Data Collection
You can set the trace, and debugging, for Campus Manager Data Collection as follows:
Step 1
The Debugging Options dialog box appears.
Step 2
Table 5-18 Data Collection Debugging Options for Data Collection
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
None
Enable Device Level Debugging
Device IP(s)
IP Addresses (IPv4 or IPv6 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
Selecting Data Collection Debug Modules
Table 5-19 describes the debug modules available for Data Collection in Campus Manager.
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
The debugging page appears.
Step 2
•
Only informational messages are recorded in the log file.
•
All messages related to Configuration and Reports are recorded in the log file.
•
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
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
The debugging page appears.
Step 2
•
Only informational messages are recorded in the log file. This is the default option.
•
All client side messages are recorded in the log file.
•
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
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
Step 2
The corresponding tree structure is displayed.
Step 3
Step 4
The Java console is displayed when you launch Topology Services.
Note
To enable debugging:
Step 1
The debugging page appears.
Step 2
•
Only informational messages are displayed in the Java Console.
•
All Topology Services client side messages are displayed in the Java Console.
•
Messages related to all errors are displayed in the Java Console. This is the default option.
Step 3
To change log level settings:
Step 1
Step 2
Step 3
Using Campus Manager Job Browser
The Campus Manager Job Browser enables you to view the status of all Campus Manager Jobs (User Tracking 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-20 displays the fields in the Campus Manager Job Browser.
Click the Refresh icon to refresh the Campus Manager job browser.
Use the Stop and Delete buttons to stop or delete jobs:
•
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.
•
Note
Administration Command Line Interface
This section describes how to administer Campus Manager database from the command line. This is explained in the following topics:
•
•
•
•
•
•
This section also explains 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
Note
Re-initializing the Database
From the command prompt or shell window, enter:
•
•
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:
•
•
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:
•
•
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:
•
•
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:
•
•
Restoring the Original Data in the Server
From the command prompt or shell window, enter:
•
•
Note
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
•
–
–
•
Ensure you have enough swap space in the server before tuning the heap size.
•
Configuration Settings for SNMPv3 Devices
Campus Manager supports the following Authentication protocols for SNMP v3:
•
•
Campus Manager supports the following Privacy protocols for SNMP v3:
•
•
•
•
•
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 password1privacy des password2
For IOS devices:
snmp-server user campususer campusgroup v3 auth md5 password1 priv des password2
Starting Campus Manager Applications
The Campus Manager Applications are:
•
•
•
•
You can select these applications from:
•
•
•
•
Security
After a period of inactivity, the LMS Portal page times out and is no longer accessible. Close all browser instances and relaunch CiscoWorks.
