Table Of Contents

Integrating Campus Manager With CiscoWorks Common Services

CiscoWorks LMS Portal Integration

Understanding Common Services ACS Integration

Understanding DCR Integration

Data Collection and DCR

Handling DCR Events

Understanding Object Grouping Services Integration

Understanding Device Center Integration

Understanding Software Center Integration

Understanding License Integration

Integrating Campus Manager With CiscoWorks Common Services

---

This chapter details the various CiscoWorks Common Services features that are integrated with Campus Manager. The features given in this chapter are:

•CiscoWorks LMS Portal Integration

•Understanding Common Services ACS Integration

•Understanding DCR Integration

•Understanding Object Grouping Services Integration

•Understanding Device Center Integration

•Understanding Software Center Integration

•Understanding License Integration

CiscoWorks LMS Portal Integration

CiscoWorks LMS Portal is the first page that appears when you log into CiscoWorks Server. The user interface, that is the LMS Portal, allows you to launch the LMS applications and it provides top-level navigation for the frequently used functions in these applications. You can launch Campus Manager from CiscoWorks LMS Portal.

CiscoWorks LMS Portal uses portlets to provide important statistics and details of Campus Manager. Portlets are the basic user interface components that are managed and displayed in the CM View.

For more information, see the User Guide for CiscoWorks LMS Portal 1.2.

Table 4-1 describes the CM Portlets in CiscoWorks LMS Portal.

Table 4-1 CM Portlets in CiscoWorks LMS Portal

Portlet	Description
Campus Manager	Provides navigation path to individual CM modules
CM N-Hop View	HTML-based feature. It displays the N-Hop view from a specified device. You can use it to view a limited set of devices.
CM Discrepancies	Displays the type and count of discrepancies, such as network inconsistencies, anomalies, and misconfigurations in the discovered network. It also gives a description of the discrepancy, the impact it has on the network, and ways to resolve it.
CM User Tracking Summary	Displays the count of the following MAC Addresses: Rogue MAC, New MAC, and Dormant MAC. It also gives a summary of the last User Tracking information such as the number of end hosts and active end hosts.
CM Best Practices Deviation	Displays the deviations from normal or recommended practices in a network. It also provides information on each of the Best Practice Deviations reported in Campus Manager. It also gives a description of the Best Practice Deviation. It includes the impact, if any, that the deviation has on the network, and ways to resolve this deviation.
CM Data Collection Summary	Displays the details of the operations performed. The details displayed are the date and time at which the operation was last completed, and the result of the operation. It also displays the type of the operation, the last completed date and time of the operation, and the result of the operation in Collection Data Summary.
CM Workflow Demo	Displays the demos of the most frequently used workflows in Campus Manager application.

The data in the portlets are shown as tables or graphs, based on the type of data. The data available in the portlet gets refreshed according to the CiscoWorks LMS Portal application configuration.

For more information on CM portlets, see User Guide for CiscoWorks LMS Portal 1.2.

Understanding Common Services ACS Integration

Common Services 3.3 (CS) Access Control Server (ACS) model provides six standard roles:

•Help Desk

•Approver

•Network Operator

•Network Administrator

•System Administrator

•Super Admin

Campus Manager application features are mapped to CS User Roles. Campus Manager integrates CS 3.3 ACS model to provide granular role definitions.

Campus Manager application features are defined as a set of tasks. For a list of Campus Manager tasks, see Common Services Permission Report. (Common Services > Server > Reports > Permission Report)

In the CS mode, you can perform any operation on the device view as well as perform any operation on all the devices, if authorized for the corresponding tasks.

In the ACS mode, you can view the devices. However, you are not allowed to perform a task for which you have no authorization. If you try to perform the task, Campus Manager displays an error message.

For example, in the ACS mode, when you launch Topology Services window, you can view all the devices. All the devices includes devices whose groups you have not mapped to in the ACS server.

However, if you select a task that is related to configuration or IP change management on a device that you are not authorized to work on, an error message appears.

The following case applies when you select Per Network Device Group as the mode of authorization in the ACS server.

Suppose you (with Network Admin role in Common Services) are authorized to perform the following tasks in the ACS mode. Let us assume that the same tasks are applicable to a user with Network Admin Role in Common Services.

•View_topo

•View_vpa

•View_ut

•View_Reports

•View_AniAnalysis

•Config_Vlan

•Config_VlanPort

•Config_UT

•Config_MgmtIP

•Discover_TopoDevices

•Discover_UTEndHosts

•Export_data

In ACS, assume that you are assigned to a device group with devices ip1, ip2, and ip3. You are not assigned to another device group that contains the devices ip4, ip5, and ip6.

If you launch Topology Services, you can view all the devices in the Topology Map window.

If you right-click and select Change Management IP Address, and the Change Management IP Address dialog box is launched since you are authorized for the task Config_MgmtIP. You can perform the task.

If you right-click and select Delete Device, an authorization error appears because you are not authorized for the task, Delete_device.

Understanding DCR Integration

Device and Credential Repository (DCR) is a set of tables that stores device information and their credentials. DCRServer, a Common Services component, is a process.

Managing devices and end hosts in Campus Manager is a two-step process:

•Data Collection

Data Collection runs as a daemon. It fetches data from devices and computes topology and network discrepancies.

•User Tracking Major Acquisition

User Tracking Major Acquisition is a transient process initiated by the Campus Manager Server. It discovers end hosts and IP phones in the network.

This section contains:

•Data Collection and DCR

•Handling DCR Events

Data Collection and DCR

After fetching device details from DCR, Campus Manager needs to perform Data Collection to manage devices. Campus Manager Server does Data Collection, at scheduled intervals.

For Data Collection, the server:

1. Gets the list of devices and their credentials from DCR.

2. Polls these devices.

3. Fetches information that is required for topology computation, reporting network discrepancies, and for various reports and device configurations.

Earlier, Data Collection process supported the collection for ports less than or equal to 150K in a network. In this release, Campus Manager supports the collection of ports up to 250K.

Note the following about Data Collection:

•If the credentials in DCR are incorrect, the devices are reported as unreachable in Campus Manager. For Data Collection, the credentials are not fetched from discoverysnmp.conf.

•It is not mandatory that Data Collection be done for all devices in DCR. You can choose or restrict the devices to be managed by Campus Manager, using the IP Address.

•Devices in DCR can be managed by Campus Manager in Auto mode or Manual mode.

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

•Manual mode policies are not applicable. You have to manually add or delete devices and only those devices will be taken for Data Collection.

For complete details on Device Management, see Device Management.

•Campus Manager places the port data collected by Data Collection into the database of Resource Manager Essentials (RME). The data placed in the database is used by Port and Module Configuration feature of RME.

For more information on how the data is used by Port and Module Configuration, see User Guide for Resource Manager Essentials 4.3

Handling DCR Events

Data Collection Server gets the list of devices and credentials from DCR during every Data Collection. It is possible that other applications also, add new devices or update attributes of devices in DCR.

DCRServer provides an event mechanism to inform the applications about these changes. For Campus Manager to be in synchronization with DCR, Data Collection Server listens to update and delete events from DCR.

When Data Collection Server receives an update event for a device or a set of devices, it synchronizes the credential information for them.

When Data Collection Server receives a Delete event for a set of devices, it deletes the devices from Campus Manager database. All Campus Manager views reflect this change immediately.

Whenever there is a change in Management IP address in Campus Manager, the Data Collection Server sends an event to DCRServer. DCRServer updates the Management IP address attribute accordingly.

Understanding Object Grouping Services Integration

The Groups feature in Common Services helps you to group devices managed by CiscoWorks applications. It helps in creating, managing, and sharing groups of devices. The groups created using this feature, are shared across applications. You can also view the groups created in applications from Common Services.

Understanding Device Center Integration

Device Center provides a one-stop place where you can see a summary for a device as well as the various tools, reports, and tasks that you can perform on a selected device. Device Center helps you access device-centric features and information from a single location.

After launching Device Center, you can invoke many tools on the selected device from a single location. The various features in Device Center come from the CiscoWorks applications installed on the server.

The device details related to Campus Manager that are available in the various sections are:

•Summary

–Device IP Address

–Device Type

–CDP Neighbors

•Reports

–Device Attributes Report

–Port Attributes Report

–Switch Port Report — Recently Down

–Switch Port Report — Reclaim Unused Up Ports

–Switch Port Report — Reclaim Unused Down Ports

–Switch Port Report — Switch Port Capacity

–Switch Port Report — Switch Port Summary

–UT End Host Report

–VLAN Report

Understanding Software Center Integration

Campus Manager releases Service Packs (SP) every three months and these updates are available through Cisco.com. Campus Manager integrates with Software Center, also known as Package Support Updater (PSU), and uses its download service.

You can check the latest SP available for Campus Manager and download it, if required, using Software Center.

Understanding License Integration

Campus Manager uses the Common Services licensing framework for licensing. Licensing is based on the number of devices. Devices managed by Campus Manager are determined during Data Collection.

The license is validated while you are launching different applications of Campus Manager such as Topology Services. If the license has expired or is invalid, you are prompted to obtain a valid license.

The following are the Use Case scenarios for Campus Manager based on the Common Services licensing framework:

•Behavior Before License Expiration (Nagging)

•Behavior When License Period Expires

•Impact of Licensing Device Limit.

Behavior Before License Expiration (Nagging)

This behavior applies to all users:

•A Nag message appears 10 days before a license expires.

•A message appears before expiration of license and when the device limit is crossed.

•When you add devices, you are warned if the device count is close to the configured limit (±10% of limit or 100 whichever is lower).

•A message appears if the device limit is crossed. However, it allows you to add a further 10% of the license limit or 100 devices, whichever is lower.

Behavior When License Period Expires

This behavior applies to all users:

•Campus Manager displays the License Expired page after the license expires.

•User Tracking CLI and Data Extraction Engine (DEE) checks expiry and stops after displaying the License Expired message.

•User Tracking does not allow any scheduled jobs in the system.

•Backup and Restore processes backup and restore the license file. The behavior is consistent with the bundle-level behavior.

Impact of Licensing Device Limit.

A network might have more devices than what is allowed by the product specific license. In such cases, Campus Manager manages only the number of devices allowed by the license.

For example, consider a network that has 1000 devices. Assume that the license is only for 300 devices.

In this case, Common Services discovers all 1000 devices and stores the credentials in Device and Credential Repository. Campus Manager manages only the first 330 devices (± 10% of the allowed license limit) in DCR. However, you are prompted to upgrade the license.

Since Data Collection is done on a partial set of devices, it is possible that some of the devices are placed under Topology Services Unconnected Views.

In this case, you have to either upgrade to the unrestricted version of the license or apply the IP Address filters in order to manage only the devices within the current license limit.

You can apply filters to manage devices in Auto mode of Device Management. You can also manually exclude devices from Campus Manager. For complete details, see Device Management.