Table Of Contents

Integration With Other Applications

CiscoWorks LMS Portal Integration

CiscoWorks Common Services Integration

SNMP Support

Backup and Restore

CiscoWorks ACS Integration

Cross-launching HUM Reports from LMS Applications

Launching HUM Reports from Campus Manager 5.1

Launching HUM Reports from CiscoView 6.1.8

Launching HUM Reports from Device Center

Launching HUM Reports from LMS Portal

Integration With Other Applications

---

This chapter explains how CiscoWorks HUM is integrated with other applications. The chapter contains the following topics:

•CiscoWorks LMS Portal Integration

•CiscoWorks Common Services Integration

•CiscoWorks ACS Integration

•Cross-launching HUM Reports from LMS Applications

CiscoWorks LMS Portal Integration

CiscoWorks LMS Portal is the first page that appears when you log into CiscoWorks Server. LMS Portal user interface allows you to launch the LMS applications and provide top-level navigation for the frequently used functions in these applications. You can launch the HUM application from CiscoWorks LMS Portal.

CiscoWorks LMS Portal uses portlets to provide important statistics and details of the HUM application. Portlets are the basic user interface components that are managed and displayed in the HUM View. For more information, see the User Guide for CiscoWorks LMS Portal 1.1.

Table 8-1 describes the HUM Portlets in CiscoWorks LMS Portal.

Table 8-1 HUM Portlets in CiscoWorks LMS Portal 

Portlet	Description
Health and Utilization Monitor	Provides navigation path to individual HUM modules.
TOP-N CPU Utilization	Displays the top N devices that have the highest CPU utilization value, where N is the number of devices configured to show in the portlet.
CPU Utilization Summary	CPU utilization is displayed as a pie chart for devices monitored using HUM.
TOP-N Memory Utilization	Displays the top N devices that have the highest and lowest memory utilization value, where N is the number of devices configured to show in the portlet.
Device Availability	Device availability status displayed as a pie chart. The pie chart presents Device availability information for all devices during the last N hour.
TOP-N Interface Utilization	Displays the top N devices that have the highest and lowest interface utilization value, where N is the number of devices configured to show in the portlet.
TOP-N Interface Errors	Displays the top N devices that have the highest interface errors (IfInError and IfOutError), where N is the number of devices configured to show in the portlet.
TOP-N Interface Discards	Displays the top N devices that have the highest interface discards (IfInDiscards, IfOutDiscards), where N is the number of devices configured to show in the portlet.
Threshold Information	Threshold configuration and violation information.
HUM System Summary	Provides information on the number of devices managed, number of MIB variables polled, license status and purge schedule.
Histo - Graph It	Provides MIB variable instance data for the specified period of time as a line graph.

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 HUM portlets, see User Guide for CiscoWorks LMS Portal 1.1.

CiscoWorks Common Services Integration

CiscoWorks HUM works on the framework of CiscoWorks Common Services 3.2. CiscoWorks Common Services 3.2 represents a common set of management services that are shared by multiple applications.

CiscoWorks Common Services 3.2 provides a standard user experience for all management functions. It also shares a common model for data storage, user-role definitions, security protocols, and navigation.

Device and Credential Repository (DCR), provided as part of CiscoWorks Common Services 3.2, is a common repository of devices, their attributes, and credentials that are meant to be used by various network management applications.

DCR helps multiple applications share device lists and credentials using a client-server mechanism, with secure storage and communications. For more information, see the User Guide for CiscoWorks Common Services 3.2.

CiscoWorks HUM uses DCR to select devices. To do this, HUM uses the Device Selector feature of CiscoWorks Common Services. SNMP support of CiscoWorks HUM depends on the SNMP credentials configured in the DCR. For more information, see SNMP Support.

CiscoWorks HUM only supports polling of Cisco devices. If you add any other devices to the DCR, you can add these devices to Pollers, as well. However, the application behavior may not be as intended.

CiscoWorks HUM uses the CiscoWorks Common Services 3.2 framework for backup and restore functionalities. For more information on backup and restore, see Backup and Restore.

SNMP Support

CiscoWorks HUM supports SNMP v1, SNMP v2c and SNMP v3 (authPriv, authNoPriv and noAuthNoPriv modes). This support depends on the SNMP credentials configured in the DCR.

---

Note The support of SNMP v3 authPriv mode is available from CiscoWorks Common Services 3.1.1.
To verify CiscoWorks Common Services version, go to Common Services > Software Center > Software Update and check the Products Installed table.

---

For instance, if DCR is configured with SNMP v3 credentials, CiscoWorks HUM communicates with the devices using SNMP v3. If DCR is configured with SNMP v2 credentials, then CiscoWorks HUM communicates with the devices using either SNMP v2c or v1.

If DCR is configured with both SNMP v2 and SNMP v3 credentials, CiscoWorks HUM gives preference to SNMP v3 version. Similarly, if DCR is configured with SNMP v2 credentials, then SNMP v2 will be given preference over SNMP v1.

The choice of using SNMP v3/v2/v1 is decided during instance query. If SNMP v3 credentials are configured then only SNMP v3 will be used, although wrong credentials are configured. If SNMP v2 credentials are configured, CiscoWorks HUM will first try with SNMP v2 and if SNMP v2 credentials are not working, then fallback is made to SNMP v1. For security reasons, fallback from SNMP v3 to SNMP v2 or SNMP v1 is not allowed.

The following scenarios are possible during instance querying:

•SNMP v1 credentials are automatically detected by CiscoWorks HUM during instance query.

If you add a Poller with Device Availability or any other scalar templates, the device is added to the database with SNMP v2 version. If you add a Poller with any other templates, the database is not be updated and results in polling failures.

•A Poller is created by adding a device with SNMP v3 credentials. Later if you delete the SNMP v3 credentials in the device and update with SNMP v2 credentials, the polling engine will not do any fallback detection from v3 to v2. CiscoWorks HUM will update SNMP v2 as the credential in the database.

•On instance querying, HUM detects that the device supports SNMP v1. If the credentials in DCR are changed, CiscoWorks HUM will still consider the credentials as SNMP v1 and not as SNMP v2.

To workaround this problem, you must remove the devices from the Pollers and then add them again. If you are not managing the devices in any of the other LMS applications, then remove the devices from DCR and then add it again.

Backup and Restore

CiscoWorks Common Services 3.2 provides Backup and Restore operations for all the installed applications.

CiscoWorks Common Services 3.2 backs up the following HUM data:

•Configuration Data

•Threshold Violation Scripts

•Reports

•Database. Poller Configuration, Threshold Configuration, Admin Settings, Polled data, Threshold Violation data, Summarization data and Job information.

We recommend that you should back up the data regularly. You can schedule immediate, daily, weekly, or monthly automatic data backups by selecting LMS Portal > Common Services > Server > Admin > Backup. You should have necessary privileges to use this option.

In all Backup-Restore scenarios, a backup taken from a machine A, can be restored on the same machine A, or on a different machine B.

For more information on backup and restore, see the User Guide for CiscoWorks Common Services 3.2.

CiscoWorks ACS Integration

CiscoWorks HUM integrates with Access Control Server (ACS) through CiscoWorks Common Services 3.1. CiscoWorks Common Services supports two modes of user authentication and authorization:

•ACS mode—Access Control Server (ACS) provides authentication and authorization services in this mode. To use this mode, you must install Cisco Secure ACS on your network.

•Non ACS mode—CiscoWorks server provides authentication and authorization services in this mode.

The CiscoWorks server authentication scheme has five roles. You cannot change these roles, or the privileges assigned to those roles. The following are the list of privileges, sorted from the least privileged to the most privileged:

•Help Desk—Can access network status information only. Can access persisted data on the system and cannot perform any action on a device or schedule a job that will reach the network.

•Network Operator—Can perform all Help Desk tasks. Can perform tasks related to network data collection. Cannot perform any task that requires write access on the network.

•Network Administrator—Can perform all Network Operators tasks. Can perform tasks that result in a network configuration change.

•System Administrator—Can perform all CiscoWorks system administration tasks.

•Super Admin—Can perform all CiscoWorks operations including the administration and approval tasks. By default, this role has full privileges and is available only in ACS mode.

If you configure CiscoWorks Common Services to use non ACS modes for authentication, HUM uses CiscoWorks Local authorization services.

In the ACS mode, CiscoWorks Common Services allows HUM to have only task-level authorization and not device-level authorization. Therefore, you will be able to access all the devices provided by DCR.

In the ACS mode the privileges you have, depend on the ACS role assigned to you. See the HUM ACS Help for complete details on roles and privileges in HUM.

Cross-launching HUM Reports from LMS Applications

This section explains how to launch HUM reports from the LMS application page. You can launch HUM reports from the following LMS applications:

•Campus Manager 5.1 (See Launching HUM Reports from Campus Manager 5.1)

•CiscoView 6.1.8 (See Launching HUM Reports from CiscoView 6.1.8)

•Device Center (See Launching HUM Reports from Device Center)

•LMS Portal (See Launching HUM Reports from LMS Portal)

Launching HUM Reports from Campus Manager 5.1

You can launch the HUM Device Dashboard and Interface reports from Campus Manager 5.1.

You must have devices managed in Campus Manager and HUM before launching these reports. See the User Guide for Campus Manager 5.1 on how to manage devices.

Table 8-2 provides the launch points for HUM reports.

Table 8-2 Launch Points for HUM Reports from Campus Manager 5.1 

Reports	Navigation
Device Dashboard Report	You can launch the Device Dashboard report for a device in Campus Manager 5.1 from: •Topology Services (see To launch Device Dashboard Report from Topology Services) •N-Hop View Portlet (see To launch Device Dashboard Report from N-Hop View Portlet) To launch Device Dashboard Report from Topology Services 1. Go to LMS Portal and select Campus Manager > Visualization > Topology Services. The Topology Services page appears. 2. Click Launch Topology Services. The Topology Services Main Window appears. 3. Go to the Topology Tree View. 4. Right-click items that you want to display. The context menu appears. 5. Select Display View. The Network Topology window opens, displaying the specified network or domain view. 6. Go to the Topology Map area. 7. Right-click the device or its components. The context menu appears. 8. Select Device Dashboard. The Device Dashboard Report page appears.
Device Dashboard Report	To launch Device Dashboard Report from N-Hop View Portlet 1. Go to LMS Portal and select CM. The Campus Manager portlets page appears. 2. Go to N-Hop View portlet. 3. Go to the Topology Map area. 4. Right-click the device or its components. The context menu appears. 5. Select Device Dashboard. The Device Dashboard Report page appears.
Interface Report	To launch the Interface Report from Campus Manager: 1. Go to LMS Portal and select Campus Manager > Visualization > Topology Services. The Topology Services page appears. 2. Click Launch Topology Services. The Topology Services Main Window appears. 3. Go to the Topology Tree View. 4. Right-click items that you want to display. The context menu appears. 5. Select Display View. The Network Topology window opens, displaying the specified network or domain view. 6. Go to the Topology Map area. 7. Select a link that connects between two devices. 8. Right-click the link. The context menu appears. 9. Select Interface Report. The Interface Report page appears displaying the last one hour data.

Launching HUM Reports from CiscoView 6.1.8

You can launch the HUM Device Dashboard and Interface Report from CiscoView. You must have devices managed in CiscoView before launching the report.

Table 8-3 provides the launch points for HUM reports.

Table 8-3 Launch Points for HUM Reports from CiscoView 6.1.8

Report	Navigation
Device Dashboard Report	You can launch Device Dashboard report for a device from CiscoView. To do this: 1. Go to CiscoView 6.1.8. 2. Select a device from the Device Selector. A graphical representation of the device chassis appears. 3. Right-click the device or its components. The context menu appears. 4. Select HUM. The Device Dashboard Report page appears.
Interface Report	You can launch Interface Report for a device from CiscoView. To do this: 1. Go to CiscoView 6.1.8. 2. Select a device from the Device Selector. A graphical representation of the device chassis appears. 3. Select one or more port interfaces on the device chassis by keeping the Ctrl key pressed down. 4. Press the Ctrl key and right-click to display the Context menu. 5. Select HUM Interface Report. The Interface Report page appears displaying the data for the last one hour.

Launching HUM Reports from Device Center

You can launch the HUM Device Dashboard report from Device Center.

You must have devices managed in Device Center and HUM before launching the report.

Table 8-4 provides the launch points for HUM reports.

Table 8-4 Launch Points for HUM Reports from Device Center

Report

Navigation

Device Dashboard Report

You can launch Device Dashboard report for a device from Device Center. To do this: 1. Go to Device Diagnostic Tools. 2. Select Device Center. 3. Select a device from the Device Selector. The Device Summary page appears, displaying the device details. 4. Go to the Functions Available panel. 5. Go to the Reports section and select Launch Device Dashboard. The Device Dashboard Report page appears with the device performance details.

Launching HUM Reports from LMS Portal

You can launch Device Dashboard and Interface Reports from HUM portlets in the LMS Portal application page.

Table 8-5 provides the launch points for HUM reports.

Table 8-5 Launch Points for HUM Reports from LMS Portal

Report	Navigation
Device Dashboard Report	You can launch Device Dashboard report for a device from the HUM portlet page. To do this: 1. Go to HUM portlets page in LMS Portal. 2. Click the device name link from any of the portlets. The Device Dashboard Report page appears.
Interface Report	You can launch Interface Report for a device from the HUM portlet page. To do this: 1. Go to HUM portlets page in LMS Portal. 2. Click the interface name link from any of the portlets. The Interface Report page appears displaying the data for the last one hour.