Table Of Contents
Working with LMS Application Views
Working with Resource Manager Essentials View
RME Job Approval
RME Device Status
RME CDA Error Summary
RME Config Protocol Summary
RME Collection Status
Syslog Collectors Information
Syslog Summary
Syslog Alerts
Syslog Message
Top N Syslog Sender Portlet
Technology portlet
RME Audit Trail Information
RME Hardware Summary
RME Software Summary
RME Change Audit
Resource Manager Essentials
RME Workflow Demos
Working with Campus Manager View
CM N-Hop View
CM Data Collection Summary
CM Discrepancies
CM Best Practices Deviation
CM User Tracking Summary
Campus Manager
CM Workflow Demo
Working with Device Fault Manager View
High Severity Alerts
DFM Device Status
DFM Events Summary
Device Fault Manager
DFM Workflow Demo
Working with Internetwork Performance Monitor View
IPM Highest Latency
IPM Highest Jitter
IPM Lowest Availability
IPM Collector Information
IPM Device Categorization
IPM Availability Dashboard
IPM Violation Summary
Internetwork Performance Monitor
IPM Workflow Demo
Working with Health and Utilization Monitor View
CPU Utilization Summary Chart
Custom Top /Bottom N Records
Device Availability
Histo-Graph It
HUM System Summary
HUM Live Graph-It
TOP-N Interface Discards
TOP-N Interface Errors
TOP-N Interface Utilization
TOP-N Memory Utilization
TOP-N-POE Utilization
TOP-N CPU Utilization
Threshold Information
Trend Watch Portlet
TOP-N Environmental Temperature
Health and Utilization Monitor Portlet
HUM Workflow Demo
Working with LMS Application Views
Working with LMS Application Views section gives a brief outline on all the LMS Applications Views and its portlets other than the Common Services.
This section has the following topics:
•
Working with Resource Manager Essentials View
•Working with Campus Manager View
•Working with Device Fault Manager View
•Working with Internetwork Performance Monitor View
•Working with Health and Utilization Monitor View
Working with Resource Manager Essentials View
The Resource Manager Essentials (RME) suite is part of the CiscoWorks family of products. RME is an enterprise solution to network management. RME is a powerful suite of web-based applications offering network management solutions for Cisco switches, access servers, and routers.
RME is based on a client/server architecture that connects multiple web-based clients to a server on the network. As the number of network devices increases, additional servers or collection points can be added to manage network growth with minimal impact on the client browser application.
RME applications provide the network monitoring and fault information features that you need for tracking devices that are critical to network uptime. RME also provides tools that you can use to rapidly and reliably deploy Cisco software images and view configurations of Cisco routers and switches.
RME applications, together with links to Cisco.com service and support, automate software maintenance to help you easily maintain and control your enterprise network.
Note The RME View and portlets are displayed in CiscoWorks LMS Portal only if RME application is installed.
This section contains the following portlets:
•RME Job Approval
•RME Device Status
•RME CDA Error Summary
•RME Config Protocol Summary
•RME Collection Status
•Syslog Collectors Information
•Syslog Summary
•Syslog Alerts
•Syslog Message
•Top N Syslog Sender Portlet
•Technology portlet
•RME Audit Trail Information
•RME Hardware Summary
•RME Software Summary
•RME Change Audit
•Resource Manager Essentials
•RME Workflow Demos
RME Job Approval
In RME Job Approval portlet, you can view the list of all jobs.
Note The RME Job Approval portlet is not added to RME View by default. However, the portlet is listed below the RME link and you can add it to any view.
•To configure RME Job Approval portlet, see RME Job Approval.
•To customize the look and feel of RME Job Approval portlet, see Changing the Look of Your Portlets.
Table 11-1 lists RME Job Approval portlet details.
Table 11-1 RME Job Approval Details
Field
|
Description
|
Job ID
|
ID of the job that has been given for approval.
The unique number assigned to the job. For periodic jobs such as Daily, Weekly, and so on, the job IDs are in the number x format. The x represents the number of instances of the job.
For example, 1001.3, indicates that this is the third instance of the job ID 1001.
Click the Job ID hyperlink to view the job details.
|
Job Description
|
Description of the job.
|
Job Schedule
|
Date and time for which the job has been scheduled.
|
The Job Approval portlet allows you to approve or reject a job for which you are an approver. A job will run only if it is approved. If the job is not approved by its scheduled runtime, or if an approver rejects it, the job is moved to its rejected state and will not run.
For periodic jobs, only one instance of the job needs to be approved. If one instance is approved, all other instances are also considered as approved.
You are notified by e-mail, when a job approved by you is created.
This portlet enforces the approval process by sending job requests through e-mail to people on the approved list.
You can click the portlet name in the title bar to navigate directly to the Jobs Pending Approval details page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3
RME Device Status
In RME Device Status portlet, you can view the number of devices along with its configurations and inventory collection status (Normal, Pending, Alias, Pre-deployed, Suspended, or Conflicting).
•To configure RME Device Status portlet, see RME Device Status.
•To customize the look and feel of RME Device Status portlet, see Changing the Look of Your Portlets.
Table 11-2 lists RME Device Status portlet details.
Table 11-2 RME Device Status Details
Field
|
Description
|
RME Device Status
|
The status of the RME device such as:
•Normal—The device has been successfully contacted by RME or the device has contacted RME at least once. This indicates that this is a real device in the network (at one point of time).
•Pending—No device will be in this state for any significant time as it is a transient state.
•Alias—When you add a new device to RME, this device may already exist in RME, but with a different host name or IP address.
•Predeployed—The devices are not in the network and are waiting to be deployed.
•Suspended—The devices have been suspended and cannot participate in RME Workflows.
However, RME continues to maintains the historical data of the device. You can resubmit the devices in this state to participate in RME Workflows.
•Conflicting—The sysObjID of the device as given in the device conflicts with the sysObjID of the device as given in the Credentials Repository.
|
Count
|
The number of devices.
For instance, you can click the number corresponding to Normal Devices, to view the Normal Devices details page in RME application.
|
You can click the portlet name in the title bar to navigate directly to the Device Management State Summary details page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
RME CDA Error Summary
The RME Check Device Attribute (CDA) Error Summary portlet displays information about the different type of errors in RME devices with credentials such as SNMP, Telnet, SSH and so on.
It will display the device count along with the type of error.
•To configure the RME CDA Error Summary portlet, see Configuring Refresh Time.
•To customize the look and feel of RME CDA Error Summary portlet, see Changing the Look of Your Portlets.
Table 11-3 lists the RME Check Device Attribute Error Summary details.
Table 11-3 RME CDA Error Summary Details
Field
|
Description
|
Credential
|
Credential details such as SNMP, Telnet, SSH and so on.
|
No.of Devices
|
Number of devices with errors.
|
RME Config Protocol Summary
In RME Config Protocol Summary portlet, you can view the configuration protocol usage details for successful configuration fetches.
To configure RME Config Protocol Summary portlet, see Configuring Refresh Time.
To customize the look and feel of RME Config Protocol Summary portlet, see Changing the Look of Your Portlets.
Table 11-4 lists the RME Config Protocol Summary details.
Table 11-4 RME Config Protocol Summary Details
Field
|
Description
|
Protocol
|
Protocols used by RME for configuration fetches.
|
Config Type
|
The Configuration types for the various protocols. The available types are:
•Running — Count of the successful running configuration fetches for each protocol
•Startup — Count of the successful startup configuration fetches for each protocol
•VLAN — Count of the successful VLAN configuration fetches for each protocol. This configuration fetch is supported by only Telnet and SSH protocols.
Click the Count link to view a detailed report for a protocol and corresponding Config Type. The detailed report shows the list of devices which are accessed using a particular protocol and for which successful Config Fetch has happened.
Example:
If you click on a Count link, 20, for Telnet protocol and Running config type, a detailed report is generated with the following fields:
–Device Name — Display name of each device.
–Accessed At — Date and time at which each device was accessed for Config Fetch purpose.
–Config Type — Configuration type for each device.
–File Type -— Configuration file type for each device.
–This detailed report shows only the devices for which Telnet has successfully fetched configurations.
You can use the export icon to export the list of devices from this detailed report to the device selector.
|
Config NeverCollected
|
The count of devices for which configuration fetch has never happened.
Click the Count link to launch the Configuration Never Collected Device page.
|
Edit Protocol Order
|
Click this button, if you want to change the transport protocol order.
|
RME Collection Status
In RME Collection Status portlet, you can view the status of the following:
–Inventory collection status (Inventory collected, Inventory Never Collected, and Recently Failed Devices)
–Config archive status (Successfully Collected, Failed to Collect, Partially Collected and Out of Sync)
The configuration and inventory collection details of devices are added to RME.
You can customize and configure the RME Collection Status portlet.
•To configure RME Collection Status portlet, see Configuring Refresh Time.
•To customize the look and feel of RME Collection Status portlet, see Changing the Look of Your Portlets.
Table 11-5 lists RME Collection Status portlet details:
Table 11-5 RME Collection Status
Field
|
Description
|
Operation
|
Type and the status of operation such as Inventory Collection or Config Archive.
|
No.of Devices
|
Number of devices.
The successful operations are highlighted in green and the failed operations are highlighted in red.
To view the details of the operation based on the status, click the number corresponding to the status.
For instance, to know the Successfully Collected status of Inventory Collection, click the number corresponding to the status.
|
You can click the portlet name in the title bar to navigate directly to the Inventory Collection Status details page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
Syslog Collectors Information
Syslog Collectors Information portlet displays the list of remote Syslog collectors subscribed to the RME servers.
It contains the syslog collector informations such as the name of the remote syslog, analyzer name, status and the number of packets received and so on.
Note This portlet will not be added to any view by default. However, it is listed under the RME link and you can add the portlet to any view.
Syslog Collector is a service to receive, filter and forward syslogs to one or more Syslog servers. In this way it reduces traffic on the network as well as for the processing load on the server.
By default you can only view the remote Syslog analyzer's name, status and the number of packets received. However, you can configure the portlet to view the other details in the portlet such as the number of packets that are filtered, invalid, dropped, or forwarded.
To configure the Syslog Collector Information portlet, see Syslog Collectors Information.
To customize the look and feel of Syslog Collector Information portlet, see Changing the Look of Your Portlets.
Table 11-6 lists the Syslog Collectors Information portlet details.
Table 11-6 Syslog Collectors Information Portlet
Field
|
Description
|
Name
|
Host name or the IP address on which the collector is installed.
|
Status
|
Status of the Remote Syslog Collector. For example, whether it is connected.
|
Received
|
Number of packets received.
|
You can click the Syslog Collectors Information portlet to navigate to the Collection Status details page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
Syslog Summary
The Syslog Summary portlet displays the 24-hour Syslog event distribution as a a pie chart. It also displays the total number of Syslog counts.
The portlet displays the top 10 syslog summary reports.
There is also a Show and Hide Graph option.To view or hide the graph you can click the Show/Hide Graph toggle button.
For more information, see User Guide for Resource Manager Essentials 4.3.
•To configure the Syslog Summary portlet, see Syslog Summary Portlet.
•To customize the look and feel of Syslog Summary portlet, see Changing the Look of Your Portlets.
Syslog Alerts
In the Syslog Alerts portlet you can view the error messages, or informational messages about events such as exceptions, and device configuration changes.
•To configure Syslog Alerts portlet, see Syslog Alerts.
•To customize the look and feel of Syslog Alerts portlet, see Changing the Look of Your Portlets.
Table 11-7 lists the Syslog Alert portlet details.
Table 11-7 Syslog Alerts
Field
|
Description
|
Device Name
|
Displays the device name.
|
Emergency
|
Number of emergency messages in the last 24 hours.
|
Alerts
|
Alert state in the last 24 hours.
|
Critical
|
Critical state in the last 24 hours.
|
You can click the portlet name in the title bar to navigate directly to the Report Generator page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
Syslog Message
The Syslog Message portlet displays the top N Syslog messages in the last 24 hours.
You can choose the custom reports type from the drop-down box. The portlet also displays the details such as device name, time stamp, severity.
•To configure Syslog Message portlet, see Syslog Message Portlet.
•To customize the look and feel of Syslog Message portlet, see Changing the Look of Your Portlets
Table 11-8 lists the Syslog Message details
Table 11-8 Syslog Message Configuration details
Field
|
Description
|
Auto Refresh
|
Select the Auto Refresh to refresh the details in the portlet at the set time.
|
Refresh Every
|
Select the hour and minute from the Refresh Every drop-down list.
|
Messages
|
Select the messages to be displayed in the portlet from the Message drop-down list.
|
No.of Rows to be displayed
|
Select the number of rows to be displayed in the portlet from the drop-down list.
|
Optional columns— You can select any of the checkboxes such as Mnemonic, Facility or Message
|
Select the optional checkbox such as Mnemonic, Facility or Message.
•If you select the Mnemonic checkbox, the mnemonic details such as CONFIG_1, RESTART and others will be displayed in the column.
•If you select the Facility checkbox, the facility details will be displayed in the column.
•If you select the Message checkbox, the syslog message will be displayed in the column
|
Severity
|
Check the severity from the severity checkbox
|
Top N Syslog Sender Portlet
The Top N Syslog Sender portlet displays the total number of Syslogs during the last 24 hours, based on the severity type that you onfigured.
•To configure Top N Syslog Sender portlet, see Top N Syslog Sender Portlet
•To customize the look and feel of Top N Syslog Sender portlet, see Changing the Look of Your Portlets
Table 11-9 Top N Syslog Sender
Field
|
Description
|
Device Name
|
Displays the device name.
|
Severity
|
Severity that has been configured on the portlet.
For example, if you have checked the Severity 1 and Severity 2 checkboxes, then only S1 and S2 will appear in the portlet.
|
Count
|
Total number of devices with their severity numbers.
For example, if Device A has the following number of severity:
Device A: S1=2
Device A: S2=3
Then total number of severity in Device A is 5.
You can click the number to view the severity details.
|
Technology portlet
In Technology portlet, we group all the RME technologies such as AutoSmart Port (ASP), Generic OnLine Diagnostics (GOLD), Smart Call Home (SCH) and Embedded Event Manager (EEM) related links.
You can configure the portlet to display ASP, GOLD, SCH, and EEM.
This is a multi-instance portlet and so you can add this portlet more than once in a view.
To customize the look and feel of Technology portlet, see Changing the Look of Your Portlets.
You can configure the Technology portlet, To do this:
Step 1 Go to CiscoWorks LMS Portal and click RME View.
The RME View portlets appear.
Step 2 Move the mouse over the title bar of the Technology portlet to view the icons.
Step 3 Click the Configuration icon.
The Select Any One drop-down list is displayed.
Step 4 You can select either ASP, GOLD, SCH, or EEM from the drop-down list.
Step 5 Click Save to view the configured portlet with the changed settings.
RME Audit Trail Information
In the RME Audit Trail Information portlet, you can view the details of the changes made to the RME application by the user.
•To configure RME Audit Trail Information portlet, see Audit Trail Information.
•To customize the look and feel of RME Audit Trail Information portlet, see Changing the Look of Your Portlets
Table 11-10 lists RME Audit Trail Information portlet details.
Table 11-10 RME Audit Trail Information
Field
|
Description
|
User Name
|
Name of the person who performed the change. This is the name entered when the person logged in.
It can be the name under which the RME application is running, or the name under which the Telnet connection is established.
|
Application Name
|
Name of the RME application involved in the network change. For example, Change Audit, Device Management, ICServer, NetConfig, and NetShow.
|
Creation Time
|
Date and the time at which the changes were performed on the RME server.
|
Description
|
Brief summary of the change that occurred on the RME server.
|
You can click the portlet name in the title bar to navigate directly to the Report Generator page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
RME Hardware Summary
In the RME Hardware Summary portlet, you can view a pie graph that displays the distribution of all managed Cisco devices in the inventory.
•To configure the RME Hardware Summary portlet, see Configuring Refresh Time.
•To customize the look and feel of the RME Hardware Summary portlet, see Changing the Look of Your Portlets.
Table 11-11 lists RME Hardware Summary portlet details.
Table 11-11 RME Hardware Summary
Fields
|
Description
|
Network Management
|
Percentage of network management used.
|
DSL and Long Reach Ethernet
|
Percentage of Ethernet used.
|
Security and VPN
|
Percentage of security and VPN used.
|
Switches and Hubs
|
Percentage of switches and hubs used.
|
Routers
|
Percentage of routers used.
|
Count
|
Count of the devices.
For instance, you can click the number corresponding to Switches and Hubs to navigate to the Hardware Report details page.
|
The graph plots the percentage count of devices, based on Cisco MetaData Framework (MDF) categorization of devices.
Each section represents the device category, the device count and percentage of total devices. The graph displays the device category and the percentage of distribution in the network.
You can click the portlet name in the title bar to navigate directly to the Report Generator page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
RME Software Summary
In the RME Software Summary portlet, you can view the software version information and count for selected devices such as Cisco Interfaces and Modules, Switches and Hubs, Universal Gateways and Access Servers, and Routers.
•To configure the RME Software Summary portlet, see RME Software Summary.
•To customize the look and feel of the RME Software Summary portlet, see Changing the Look of Your Portlets.
Table 11-12 lists the RME Software Summary portlet details.
Table 11-12 RME Software Summary
Fields
|
Description
|
Device Categories
|
Categories of devices used in the application.
|
Software Version
|
Software version of the device categories.
|
Count
|
Number of the device.
For instance, you can click on the number corresponding to Switches and Hubs to navigate to the Software Report details page.
|
You can click the portlet name in the title bar to navigate directly to the Report Generator page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
RME Change Audit
In the RME Change Audit portlet you can view the changes in the inventory and configuration information for all the devices after every Inventory or Configuration Collection.
However, the VLAN config change details will not be displayed.
The changes in the exception period are displayed in red.
•To configure the RME Change Audit details, see RME Change Audit.
•To customize the look and feel of the RME Change Audit portlet, see Changing the Look of Your Portlets.
Table 11-13 lists the RME Change Audit portlet details.
Table 11-13 RME Change Audit Details
Field
|
Description
|
Device Name
|
Device name as entered in the Device and Credential Repository. Click the device name to launch the Device Name.
|
User Name
|
Name of the user who performed the change. This is the name entered when the user logged in.
It can be the name under which the RME application is running, or the name using which the change was performed on the device.
The User Name field may not always reflect the user name.
The User Name is reflected only when:
•Config change was performed using RME
•Config change was performed outside RME, and the network has username based on AAA security model
where in authentication is performed by a AAA server (such as TACACS/RADIUS or local server)
|
Creation Time
|
Date and the time at which the application communicated the network change or when Change Audit saw the change record.
|
Message
|
Brief summary of the network change.
You can click the Message link to navigate to the 24 Hour Inventory Change Report details page.
|
You can click the portlet name in the title bar to navigate directly to the Report Generator page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.3.
Resource Manager Essentials
The Resource Manager Essentials (RME) suite is part of the CiscoWorks family of products. RME is an enterprise solution to network management.
RME is a powerful suite of web-based applications offering network management solutions for Cisco switches, access servers, and routers.
You can customize and configure the Resource Manager Essentials portlet.
To customize the look and feel of Resource Manager Essentials, see Changing the Look of Your Portlets
To configure Resource Manager Essentials portlets:
Step 1 Go to CiscoWorks LMS Portal and select the RME View.
A list of RME portlets appear.
Step 2 Go to Resource Manager Essentials portlet and click the Configuration icon.
Step 3 Select the application name from the Application drop-down list.
Step 4 Click Save to view the Application portlet with the configured settings.
Table 11-14 lists the Resource Manager Essentials portlet details.
Table 11-14 Resource Manager Essentials Portlet
Launch Points
|
Description
|
Home
|
The Home page is the first page that appears when you start Resource Manager Essentials.
From the Home page you can view the details such as:
•Device Management Status
•Collection Status
•Recently Completed Jobs
•24 Hour Syslog Severity Summary
•24 Hour Changes
•System Tasks
•Device Management Tasks
•Reports and Management Tasks.
|
Devices
|
Allows you to add devices to RME that you have added in Common Services.
You can also schedule addition periodic polling and periodic inventory collection of devices, edit the device attributes, and group the RME devices based on the user-defined criteria.
|
Config Management
|
Allows you to manage configurations of the devices on the network.
You can archive, view, edit, update, and track changes to device configurations in a central location
|
Software Management
|
Allows you to analyze software upgrades by generating the following:
•Upgrade Analysis reports
•Import images into the software library
•Distribute software images to groups of devices
•Schedule reliable image upgrade jobs.
It also reduces errors by recommending images that you can deploy in your devices.
It also allows you to select one of your devices as a remote stage to temporarily store a software image.
|
Job Management
|
Allows you to view the status of all RME jobs.
This feature also enables you to view all the jobs that are pending approval, and approve or reject them.
|
Reports
|
Allows you to generate various RME custom and standard reports.
You can also manage report jobs, create customized templates, and access archived reports.
|
Tools
|
Allows you to access the Change Audit, Syslog, Notches and Smart Case applications.
•Change Audit
Lets you track and report network changes.
You can define automated actions, such as sending an e-mail or trap, running an automated script after creating a Change Audit record, and defining exception periods if you do not expect any changes to occur to the devices.
•Syslog
Lets you centrally log and track system error messages from Cisco devices.
You can define automated actions such as sending an e-mail or launching a customized webbed (URL), running an automated script after receiving a specific Syslog message and filtering unwanted messages.
•Netshow
Lets you run show commands on your system.
You can run your own custom commands or run available system-defined command sets.
You can also define Commands sets by choosing show commands based on device type.
|
Admin
|
Allows you to perform maintenance and administrative tasks. For instance, you can perform the following tasks:
•Set up the backup and purge policies.
•Schedule the inventory collection and polling of the devices.
•Define job approval policies.
•Define the upgrade preference for the software image management.
•Set up the Configuration Management job policies and define the transport protocol order for Configuration Management applications.
•Enable device credentials verification when you add devices to RME.
|
Shortcuts
|
Allows you to access the following links directly without navigating through the various pages in the RME application.
For instance, Using Shortcuts you can click the following links to access information.
•Device Management Summary
•Inventory Collection Summary
•Config Archive Summary
•Check Device Credentials
•Out of Sync Report
•Detailed Device Report
•Hardware Report
•Software Report
•24 Hour Inventory Change Report
•24 Hour Systole Report
•24 Hour Change Audit Report
•Exception Period Change Report
|
For more information, see User Guide for Resource Manager Essentials 4.3.
RME Workflow Demos
The RME Workflow demo (audio and video) portlet displays the most frequently used workflows in RME applications.
They are as follows:
•Managing Device Configuration
•Using Baseline Templates
•Managing Software Images
•Managing Syslogs
•Generating RME Reports
Click the corresponding links to view the demo.
Note You must enable JavaScript in the browser window and install the latest version of the Flash Player to view the demo.
Working with Campus Manager View
Campus Manager (CM) is an integral component of the CiscoWorks family of products. As an enterprise solution to network management, Campus Manager provides a suite of web-based network management tools that enable administrators to obtain various types of graphical views of their network topology and to obtain end-user information.
It also reports network inconsistencies, anomalies, and configuration errors in the discovered network.
Campus Manager provides support for Spanning-Tree protocols, a graphical tool for managing complex ATM networks. It has a user-friendly interface for creating, modifying, or deleting VLANs, LANEs. It also allows you to assign switch ports to VLANs.
Campus Manager is based on a client-server architecture that connects multiple web-based clients to a server on the network.
Note The CM View and its portlets are displayed in CiscoWorks LMS Portal only if CM application is installed.
This section contains the following portlets:
•CM N-Hop View
•CM Data Collection Summary
•CM Discrepancies
•CM Best Practices Deviation
•CM User Tracking Summary
•Campus Manager
•CM Workflow Demo
CM N-Hop View
CM N-Hop View portlet is a HTML based light weight feature and is available as a part of CiscoWorks Portal. This is much faster than the regular Campus Manger Topology services.
This portlet displays a N-hop view from a specified device. It should be used to view a limited set of devices.
Using CM N-Hop View:
•You can cross-launch the following CiscoWorks applications:
–CiscoView
–Device Center
–RME
–CiscoWorks Assistant
–Health and Utilization Monitor
–Internetwork Performance Monitor
–Device Fault Manager
To launch the applications, choose a device, right click and choose the required application.
Note You must have RME, CiscoWorks Assistant, IPM, and HUM installed on your CiscoWorks server, to launch them from the CM N-Hop View portlet. You can launch DFM Alert reports, even if Campus Manager and Device Fault Manager are installed on different CiscoWorks servers.
•Launch CiscoWorks Assistant
Select any device, right-click and choose Troubleshoot.
The CiscoWorks Assistant > Device Troubleshooting Report is launched. This page gives various details about the device. In case of devices that are down, you can use these details to analyze why the device is unreachable.
For more details, see User Guide for CiscoWorks Assistant.
•Launch Health and Utilization Monitor
–Select any device from the map and right-click and choose Device Dashboard.
The Device dashboard report is launched. It displays performance details for the device.
•Select any link from the Topology map and right-click and choose Interface Report.
The Interface Report for that particular link is launched, displaying data for the last one hour.
For complete details on the reports, see User Guide for Health and Utilization Monitor.
•Launch Resource Manager Essentials
–Select any device, right-click and choose SWIM
It cross-launches to RME Software Distribution page that enables you to distribute the images in your network.
For more details, see User Guide for Resource Manager Essentials.
–Select any device, right-click and choose NetConfig
It cross-launches to RME NetConfig page that enables you to manage NetConfig jobs. The page allows you to apply a set of commands (a task) on selected devices. You can create your own custom tasks for running on multiple devices.
For more details, see User Guide for Resource Manager Essentials.
•Launch Internetwork Performance Monitor.
Select any IPSLA capable devices, right click and choose Show Collector or Create Collector.
The corresponding Collector Management page is launched. You can either create new collectors or view existing ones for Layer 3 devices. An error appears if you do this on a Layer 2 device. For more details, see User Guide for Internetwork Performance Monitor.
•Launch Device Fault Manager
From the CM N-Hop View portlet, by launching Device Fault Manger, you can view the following details:
–Fault History Report: Provides the history of DFM events and alerts.
–Show DFM Alerts: Launches the DFM report that gives the Alerts and events information associated with the device.
For more details, see User Guide for Device Fault Manager.
Note You can launch RME, DFM, IPM and HUM from Topology maps even if they are installed on different CiscoWorks servers, in a Master Slave setup.
•You can access a device using Telnet. To do so, choose a device, right click and choose Telnet.
•You can view the following information in the map:
IP Address
|
IP Address of the Device
|
device name
|
Name of the device
|
sysName
|
sysName
|
sysContact
|
Contact person for that device
|
sysLocation
|
Physical location of the device
|
sysOID
|
Value of the System Object Identifier MIB variable of the device
|
–To view information, right click anywhere on the map and select the required value. The selected information is displayed for all devices.
–To hide the displayed information, right click anywhere on the map and select Show/Hide Labels. Move the mouse over the label to display this relevant information.
You can drag the labels anywhere inside the map. To set it to its original position, right click in the map and choose Reset Draggables.
You can view the details about a single device or link.
–Click the link Show Properties at the top right corner. (It toggles between Show Properties and Hide Properties). You can also move the IP address of the devices using the cursor.
–Choose a device or link. Properties of the device or link are displayed as shown in Table 11-15.
Table 11-15 Device and Link Details of CM N-Hop Portlet
Device Details
|
Device name
|
Name of the device
|
IP Address
|
IP Address of the device
|
status
|
Indicates if the device is up or down
|
imageVer
|
Version details of the image installed in the device
|
sysLocation
|
Physical location of the device
|
sysName
|
sysName
|
sysContact
|
Contact person for that device
|
sysOID
|
Value of the System Object Identifier MIB variable of the device
|
Link Details
|
Link Status
|
Indicates if the link is up or down
|
Device IP
|
IP Address of the device. Shown for both devices between which the link is configured.
|
Interface
|
Interface in the device. Shown for both devices between which the link is configured.
|
You can click the Configuration icon in the CM N-Hop View to configure the portlet.
To configure the CM N-Hop View portlet:
Step 1 Go to CiscoWorks LMS Portal and click the Add Portlet icon at the top right corner of the page.
A popup window appears. To expand and collapse the sections, click the arrow next to the section title.
Each section in this window contains a list of portlets.
Step 2 Click CiscoWorks and select CM.
A list of CM portlets appear.
Step 3 Click Add against the CM N-Hop View portlet.
The configuration screen is displayed.
Step 4 Enter the IP address or the Device name of the root device in the Root Device field.
If the device you specify is not managed by Campus Manager, it will display an error message such as "The root device you specified is not managed by Campus Manager"
Step 5 Enter the number of hops in the Hop count field.
The Network Topology map is drawn for the specified number of hops.
Step 6 Add the device to the critical device poller by checking the Poll Devices check-box.
Campus Manager polls the network periodically. If you need to monitor the status of a certain device more frequently, add it to the critical device poller.
This device is removed from the critical poller list when you close the CM N-Hop View portlet window.
Step 7 Check the Show DFM Alerts checkbox to display the DFM Alerts.
–Check the Critical checkbox to display only the critical alerts.
–Check the Warning checkbox to display only the warning alerts.
–Check the Informational checkbox to display only the informational alerts.
You can also check the Critical, Warning, and Informational checkboxes to display all the critical, warning and informational alerts.
Step 8 Select the time interval from the Refresh Every drop-down list. The interval can be either in minutes or hours.
By default, the portlet refreshes the topology map every 2 minutes. If you set the time interval, it refreshes accordingly. For every refresh, the data is fetched from the last polling cycle of the critical device poller.
Step 9 Click Save to view the portlet withe the configured settings.
Note You can also add this portlet to other application and view it.
For more information, see the User Guide for Campus Manager 5.2.
CM Data Collection Summary
In the CM Data Collection Summary portlet you can view the details of the operations carried out. The details displayed are the date and time at which the operation was last completed, and the result of the operation.
You can view the type of the operation, the last completed date and time of the operation, and the result of the operation in Collection Data Summary.
•To configure CM Data Collection Summary portlet, see Configuring Refresh Time.
•To customize the look and feel of CM Data Collection Summary portlet, Changing the Look of Your Portlets.
Table 11-16 lists the CM Data Collection Summary portlet details.
Table 11-16 CM Data Collection Summary
Field
|
Description
|
Operation
|
Type of operation such as Data Collection and User Tracking Acquisitions (End Hosts) and so on.
|
Last Completion Time
|
Date and time when the operation was last completed.
|
Result
|
Result of the operation.
Click the required link from the Result column to view the Report.
|
State
|
State, whether it is idle or active.
|
You can click the portlet name in the title bar to navigate directly to the corresponding page in the application.
For more information, see User Guide for Campus Manager 5.2.
CM Discrepancies
In the CM Discrepancies portlet, you can view the type and count of discrepancies, such as network inconsistencies and anomalies or misconfigurations in the discovered network, using the Discrepancies portlet.
The CM Discrepancy portlet gives a description of the discrepancy, the impact it has on the network, and ways to resolve it.
Campus Manager provides reports on discrepancies in the discovered network, enabling identification of configuration errors such as link-speed mismatches on either end of a connection. Discrepancies are computed at the end of each data collection schedule.
•To configure the CM Discrepancies portlet, see Configuring Refresh Time.
•To customize the look and feel of the CM Discrepancies portlet, Changing the Look of Your Portlets.
Table 11-17 lists the CM Discrepancies portlet details.
Table 11-17 Discrepancy
Field
|
Description
|
Type
|
Type of the discrepancy such as network inconsistencies, anomalies or misconfigurations in the network.
|
Count
|
Number of deviations.
Click the number corresponding to the deviation to navigate to the Unacknowledged Discrepancy Report in the application.
|
You can click the portlet name in the title bar to navigate directly to the Campus Manger Report Generator page. Select Discrepancies from the Select a Report drop-down list to navigate to the Network Discrepancy page.
For more information, see User Guide for Campus Manager 5.2.
CM Best Practices Deviation
In the CM Best Practices Deviation portlet, you can view the type and count of the deviations using the CM Best Practices Deviation portlet.
The CM Best Practices Deviation portlet helps you to view deviations from normal or recommended practices in a network and provides information on each of the Best Practice deviations reported in Campus Manager. These deviations do not have a serious impact on the functioning of the network.
This portlet 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 the deviation.
•To configure the CM Best Practices Deviation portlet, see Configuring Refresh Time.
•To customize the look and feel of the CM Best Practices Deviation portlet, Changing the Look of Your Portlets
Table 11-18 lists CM Best Practices Deviation portlet details.
Table 11-18 CM Best Practices Deviation
Field
|
Description
|
Type
|
Brief description of the deviation from the Best Practice.
|
Count
|
Number of deviations.
Click the number corresponding to the deviation to navigate to the Unacknowledged Best Practices Deviation Reports.
This page displays details such as the type, summary, first found and remarks.
|
You can click the portlet name in the title bar to navigate directly to the Campus Manger Report Generator page. Select Best Practices Deviations from the Select a Report drop-down list to navigate to the Best Practices Deviations page
For more information, see User Guide for Campus Manager 5.2.
CM User Tracking Summary
The CM User Tracking Summary portlet displays the number of MACs. These are:
–Rogue MAC— MAC Addresses that are not authorized to exist in your network.MAC Addresses that are configured as Rogue in the User Tracking setting will be displayed here.
–New MAC— MACs Address that are newly added to your network.
–Dormant MAC— MAC Addresses that are inactive for the specified number of days.
This portlet also gives the summary about the last User Tracking information such as the number of end hosts and active end hosts.
End Hosts are hosts that are currently connected to the network. The regular end hosts report shows both active end hosts and end hosts that were previously connected to the network but are disconnected now.
Table 11-19 lists the CM User Tracking Summary portlet details.
Table 11-19 CM User Tracking Summary
Field
|
Description
|
Number of End hosts
|
Displays the number of end hosts.
You can click the number to navigate to the End Hosts Immediate Reports page.
|
Number of Active End hosts
|
Displays the number of active end hosts.
You can click the number link to navigate to the Active End Hosts Immediate Report page.
|
Number of Dormant hosts in last 7 days
|
Displays the number of hosts that are inactive for 7 days.
The number of days depends on the days configured in the configuration screen.
You can click the number link to navigate to the Dormant MAC Report page.
|
Number of New hosts in last 7 days
|
Displays the number of new hosts in the last 7 days.
The number of days depends on the days configured in the configuration screen.
You can click the number link to navigate to the New MAC Report page.
|
Number of Rogue hosts in last 7 days
|
Displays the number of rogue hosts in the last 7 days.
The number of days depends on the days configured in the configuration screen.
You can click the number link to navigate to the Rogue MAC Report page.
|
You can configure the CM User Tracking Summary portlet.
To configure the CM User Tracking Summary:
Step 1 See Configuring Refresh Time.
Step 2 Enter the number of days to view the list of Dormant, New and Rogue hosts in the corresponding text fields.
Step 3 Click Save to save all the settings.
Campus Manager
Campus Manager is an integral component of CiscoWorks LAN Management Solution. It provides a suite of web-based network management tools that enable administrators to obtain various types of graphical views of their network topology and end-user information.
It also reports network inconsistencies, anomalies, and configuration errors in the discovered network.
If the application is not installed, the corresponding entries will not be available in CM portlets.
You can customize and configure the Campus Manager portlet.
To customize the look and feel of the Campus Manager portlet, see Changing the Look of Your Portlets.
To configure Campus Manager portlets:
Step 1 Go to CiscoWorks LMS Portal and click CM View.
The CM View portlets appear.
Step 2 Go to the Campus Manager portlet and click the Configuration icon.
Step 3 Select the application name from the Application drop-down list.
You can select any application name from the drop-down list.
Step 4 Click Save to view the configured settings.
Table 11-20 lists the Campus Manager portlet details.
Table 11-20 Campus Manager Portlet
Launch Points
|
Description
|
Home
|
The Campus Manager Home page is the first page that appears when you start Campus Manager.
From the Home page you can view the status of Device Discovery, Data Collection, and User Tracking Acquisition.
|
User Tracking
|
Helps you to locate and track the end hosts in your network.
It provides you the information required to troubleshoot as well as to analyze any connectivity issues.
This application identifies all end users connected to the discovered Cisco access layer switches on the network, including printers, servers, IP phones and PCs.
|
Visualization
|
Allows you to create Topology services that enables you to view and monitor your network including the links and the ports of each link.
|
Configuration
|
Allows you to create new VLAN, PVLAN, create and modify a trunk, and create VLAN Port assignment for assigning VLANs to ports.
|
Reports
|
Allows you to view an analysis of the ANI Server, details of devices discovered, Data Collection metrics, and the lists of devices.
|
Job Management
|
Allows you to view the Campus Manager job details such as the job ID, job type, description, owner, jobs schedule and completed time, and the status.
|
Administration
|
Allows you to set up Device Discovery, Campus Manager Data Collection, and User Tracking acquisition using the Administration module of Campus Manager.
|
For more information, see User Guide for Campus Manager 5.2.
CM Workflow Demo
The Campus Manager Workflow Demo (audio and video) portlet displays the most frequently used workflows in Campus Manager application.
They are as follows:
•User Tracking
•VLAN Configuration
•Topology Services
•Discrepancies and Best Practices
•Virtual Network Manager
Click the corresponding links to view the demo.
Note You must enable JavaScript in the browser window and install the latest version of the Flash Player to view the demo.
Working with Device Fault Manager View
Device Fault Manager (DFM) is an integral component of the CiscoWorks family of products. DFM offers real-time assistance to network operations personnel by monitoring and displaying the operational health of the network.
DFM also analyzes events and determines when a probable fault occurs and notifies users of conditions through an online display and other notification services.
Note The DFM View and portlets are displayed in CiscoWorks LMS Portal only if DFM application is installed.
This section contains the following portlets:
•High Severity Alerts
•DFM Device Status
•DFM Events Summary
•Device Fault Manager
•DFM Workflow Demo
High Severity Alerts
In the High Severity Alerts portlet, you can view the severity alerts using the High Severity Alerts portlet.
The High Security Alerts portlet provides a consolidated real-time view of the operational status of your network. When a fault occurs in the network, DFM generates an event. All events occurring on the same device are rolled into a single alert.
You can also use Notification Services to change the standard event name to a more meaningful one.
Click the High Severity Alerts link portlet to view the alerts and activities of Device Fault Manager.
•To configuring High Severity Alerts, see High Severity Alerts.
•To customize the look and feel of the High Severity Alerts portlet, Changing the Look of Your Portlets.
Table 11-21 lists High Severity Alerts portlet details.
Table 11-21 High Severity Alerts
Field
|
Description
|
ICON
|
Alert icon.
|
Alert ID
|
Alert Identifier number.
You can click the Alert ID link to navigate to the Alerts and Activities Detail page.
|
Device Type
|
Type of device such as switches and hubs.
The actual device type is reflected when new events occur.
|
Duration
|
Time span since alert creation depending upon alert status.
|
Last Change
|
Date and time alert last occurred or was changed. Alerts are grouped by severity, and within severities, alerts with the latest changes are listed first.
|
Device Name
|
Device name or IP address.
You can click the Device Name link to navigate to the Detailed Device View page.
|
Event Updated
|
Category of the event with the most recent changes such as: Environment, Interface, Other, Reachability, System Hardware, Utilization.
|
Status
|
Lists the alert status such as:
•Active—Alert is active. All suspended devices remain active.
•Cleared—Cleared: Alert is no longer alive. When the alert has been in the Cleared state for 20 minutes, it expires and it is removed from the display.
•Acknowledged— Alert was manually acknowledged by a user from the Alerts and Activities Detail page.
|
You can click the protect name in the title bar to navigate directly to the Alerts and Activities page in the application.
For more information, see User Guide for Device Fault Manager 3.2.
DFM Device Status
In DFM Device Status protect you can view the status and the number of all the devices in the DFM inventory.
•To configure DFM Device Status, see DFM Device Status.
•To customize the look and feel of DFM Device Status, see Changing the Look of Your Portlets.
Table 11-22 lists DFM Device Status protect details.
Table 11-22 DFM Device Status
Field
|
Description
|
Status
|
Lists the device status such as:
•Known—The device has been successfully imported and is managed by DFM.
•Learning—DFM is discovering the device. This is the beginning state when the device is first added or is being rediscovered.
•Questioned— DFM cannot manage the device.
•Pending— The device is being deleted and DFM is waiting for confirmation from all of its data collectors before purging the device and its details.
•Unknown—The device is not supported by DFM.
|
Device Count
|
Number of devices.
|
You can click the portlet name in the title bar to navigate directly to the Device Summary details page in the application.
For more information, see User Guide for Device Fault Manager 3.2.
DFM Events Summary
The DFM Events Summary portlet displays the information about the events that were encountered on the devices such based on the severity such as critical or informational.
Table 11-23 DFM Events Summary Portlet
Field
|
Description
|
Events Name
|
Name of the event such as Operationally Down, OutofRange, HighErrorRate, Unresponsive and so on.
|
Severity
|
Type of severity of the device such as critical, or informational.
|
No. of devices
|
Total number of devices affected by the severity.
|
You can customize and configure the look and feel of the Device Fault Manager portlets.
To customize the look and feel of Device Fault Manager, see Changing the Look of Your Portlets.
To configure DFM Events Summary portlet.
Step 1 Go to CiscoWorks LMS Portal and click DFM View.
The DFM View portlets appear.
Step 2 Move the mouse over the title bar of the DFM Events Summary portlet to view the icons.
Step 3 Click the Configuration icon.
Step 4 Select the minute and hour from the Refresh Every drop-down list to change the Refresh time.
The items in the portlet get refreshed at the changed Refresh time.
Step 5 Expand the icon against the Critical Checkbox.
It displays the list of Critical events. You can select the checkbox against the respective critical events to display the events in the portlet.Expand the icon against the Informational Checkbox.
It displays the list of Informational events. You can select the checkbox against the respective informational events to display the events in the portlets.
Note You can only select a maximum of 20 events to be displayed in the portlet.
Step 6 Click Save to view the portlet with the configured settings such as the Events Name, Severity and the No.of Devices.
Click the device count link against the corresponding Events to navigate to the Alerts and Activities page.
Device Fault Manager
Device Fault Manager (DFM) is an integral component of the CiscoWorks family of products. DFM offers real-time assistance to network operations personnel by monitoring and displaying the operational health of the network.
If the application is not installed, the corresponding entries will not be available in the DFM portlets.
You can customize and configure the look and feel of the Device Fault Manager portlets.
To customize the look and feel of Device Fault Manager, see Changing the Look of Your Portlets.
To configure Device Fault Manager portlets:
Step 1 Go to CiscoWorks LMS Portal and select DFM View.
A list of DFM portlets appear.
Step 2 Go to Device Fault Manager portlet and click the Configuration icon.
Step 3 Select the application name from the Application drop-down list.
You can select any application name from the drop-down list.
Step 4 Click Save to view the portlet with the configured settings.
Table 11-24 lists the Device Fault Manager portlet details.
Table 11-24 Device Fault Manager Portlet
Launch Points
|
Description
|
Home
|
The Device Fault Manager Homepage is the first page that appears when you start Device Fault Manager.
From the home page, you can view the following details:
•Status of Alerts and Activity Display
•Fault History reports
•Details of managing devices in DFM inventory
•Configuring notifications
•Performing system configuration on DFM.
|
Alerts and Activities
|
Enables you to view the details about alerts that have occurred in your network, and the specific events that caused the alerts.
|
Device Management
|
Enables you to perform the device management tasks. They are as follows:
•Synchronizing and comparing the DFM inventory with the Device Credential Repository. (DCR).
•Adding and deleting devices, suspending and resuming the management of devices (or their sub components), checking device status, rediscovering devices, and configuring DFM SNMP settings.
|
Notification Services
|
Enables you to customize event names and manage DFM notification.
This lets you change system-defined event names to other names that are more meaningful to you.
DFM will then use the new names throughout its system, including in its notifications.
The other functions on this page allow you to configure DFM to send notifications when specific alerts or events occur on specific device groups.
You can send these notifications to e-mail recipients or to network management systems.
For systems that do not accept SNMP traps, use syslog notification.
|
Fault History
|
Enables you to view stored information on past alerts and events.
This information stored in a Fault History database, and searches can be customized according to what you are looking for, such as alerts and events that occurred on certain devices, in a certain period, or in a certain group.
|
Configuration
|
Enables you to perform DFM-specific configuration and administration tasks.
From Polling and Threshold administrative tasks are separated from basic system configuration tasks.
From Polling and Threshold configuration, you can change your polling parameters and threshold settings and specify priorities when a component belongs to multiple groups. The other configuration tasks are:
•Setting up SNMP trap for forwarding and receiving
•Creating views for the Alerts and Activities display
•Creating and editing device groups
•Setting up schedules for rediscovering the managed inventory
•Trimming the Fault History database, specifying an SMTP server for e-mail notifications
•Adjusting logging levels.
|
For more information, see User Guide for Device Fault Manager 3.2
DFM Workflow Demo
The Device Fault Manager (DFM) Workflow demo (audio and video) portlet displays the most frequently used workflows in the DFM application.
They are as follows:
•Notification handling
•Trap Forwarding
•DFM Reports
•Configuring Polling and Threshold Settings
Click the corresponding link to view the demo.
Note You must enable JavaScript in the browser window and install the latest version of the Flash Player to view the demo.
Working with Internetwork Performance Monitor View
Internetwork Performance Monitor (IPM) suite is a network management application that allows you to monitor the network performance by configuring collectors on IP SLA (IP Service Level Agreement) capable source devices (routers) and collects the performance-related statistics from these devices.
Note The IPM View and portlet is displayed in CiscoWorks LMS Portal only when IPM application is installed.
This section contains the following portlets:
•IPM Highest Latency
•IPM Highest Jitter
•IPM Lowest Availability
•IPM Collector Information
•IPM Device Categorization
•IPM Availability Dashboard
•IPM Violation Summary
•Internetwork Performance Monitor
•IPM Workflow Demo
IPM Highest Latency
In the IPM Highest Latency portlet you can view the time taken for an IP packet to travel from source to target and back.
Latency is defined as the time taken for an IP packet to travel from source to target and back.
The collectors (by default there are five collectors) with higher latency are listed first, followed by other collectors. This arrangement helps the administrator to closely monitor the collectors with highest latency.
•To configure IPM Highest Latency, see IPM Highest Latency.
•To customize the look and feel of IPM Highest Latency, see Changing the Look of Your Portlets.
Table 11-25 lists the Highest Latency portlet details.
Table 11-25 Highest Latency Portlet
Field
|
Description
|
Collector Name
|
Name of the collector.
|
Operation Type
|
Lists the type of IPSLA operations.
|
Latency
|
Time taken for an IP packet to arrive from the Source to Target and back.
|
Note You can click the value of latency to view the Real time Latency Graph details in the IPM application.
You can click the portlet name in the title bar to navigate directly to the corresponding page in the application.
For more information, see User Guide for Internetwork Performance Monitor 4.2.
IPM Highest Jitter
The inter-packet delay between any two consecutive data packets sent from the source to target to target router and back is referred to as Jitter.
The collectors with the highest jitter are listed first, followed by other collectors. This arrangement helps the Administrator to monitor closely the collectors with highest jitter.
•To configure IPM Highest Jitter, see IPM Highest Latency.
•To customize the look and feel of IPM Highest Jitter, see Changing the Look of Your Portlets.
Table 11-26 lists the IPM Highest Jitter portlet details.
Table 11-26 IPM Highest Jitter Portlet Details
Field
|
Description
|
Collector Name
|
Name of the collector.
|
Operation Type
|
Type of operation.
|
SD Jitter (Source Destination Jitter)
|
Source destination jitter count.
|
DS Jitter (Destination Source Jitter)
|
Destination source jitter count.
|
Note You can click the value of the count of the SD Jitter or DS Jitter to view Real time Latency Graph details in IPM application.
You can click the protect name in the title bar to navigate directly to the corresponding page in the application.
For more information, see User Guide for Internetwork Performance Monitor 4.2.
IPM Lowest Availability
Checks the reachability of the target device from the source router using the latency information. The availability is reported in percentage.
The Lowest Availability portlet measures the availability of services such as FTP, DHCP, HTTP, TCP Connect, RTP, DNS, ICMP, UDP, and DSLw on the target device.
The collectors are listed in ascending order of availability to help the administrator closely monitor the collectors with lowest availability.
•To configure IPM Lowest Availability, see IPM Lowest Availability.
•To customize the look and feel of IPM Lowest Availability, see Changing the Look of Your Portlets.
Table 11-27 lists the Lowest Availability portlet details.
Table 11-27 Lowest Availability Portlet
Field
|
Description
|
Collector Name
|
Name of the collector.
|
Operation Type
|
Lists the IP SLA operation such as ICMP Jitter and so on.
|
Availability Percentage
|
Availability of target or service in percentage.
|
You can click the portlet name in the title bar to navigate directly to the corresponding page in the application.
For more information, see User Guide for Internetwork Performance Monitor 4.2.
IPM Collector Information
A collector is defined as an entity that encompasses a source router, a target device, an operation, and the collector schedule details.
In the IPM Collector Information portlet, you can view the following details
•The state of the collector such as Running, Source Not Responding, Config Failed, and Deleting.
•The total number of collectors in the respective state.
•The total number of licensed collectors.
To configure IPM Collector Information, see Configuring Refresh Time.
To customize the look and feel of IPM Collector Information, see Changing the Look of Your Portlets.
Table 11-28 lists Collector Information portlet details.
Table 11-28 IPM Collector Information Portlet
Field
|
Description
|
State
|
Displays the state of the collector such as:
•Running
•Deleting
•Pending
•Scheduled
•Dormant
•Config Failed
•Source Not Responding
•Completed
•Running
•Stopped and Configuring.
|
Number of Collectors
|
Displays the number of collectors.
|
Note You can click the number link to navigate to the Collector Management page in the IPM application.
Table 11-29 lists the Collector Information status details
Table 11-29 Collector Information State
Collector Status
|
Description
|
Deleting
|
Collector is being deleted.
|
Scheduled
|
Collector is scheduled for a future date and time.
|
Dormant
|
Collector is in dormant state and will start polling at the next polling interval.
|
Config Failed
|
Configuration of the collector failed on the source router.
|
Source Not Responding
|
Source router is not responding to configuration or reconfiguration of the collector or for polling the statistics. This problem could occur because of invalid credentials or because the device is not reachable.
|
Completed
|
Collector has reached its End Time and IPM will not poll this collector again.
|
Running
|
Collector is configured at the source router and polling is in progress.
|
Stopped
|
Collector has been manually stopped and is not being polled by IPM.
|
Configuring
|
Configuration of the collector is in progress.
|
You can click the portlet name in the title bar to navigate to the Collector Management page in the IPM application.
For more information, see User Guide for Internetwork Performance Monitor 4.2.
IPM Device Categorization
The devices added from DCR are categorized based on the availability of IP SLA. IP SLA is a feature built into Cisco Internetworking Operating System (IOS) and is used by most Cisco routers and switches.
IPM source is a device from which you initiate operations for measuring network performance statistics. IPM targets are destination devices for which you want to gather network performance statistics. However, some target devices are Responder enabled.
•To configure IPM Device Categorization, see Configuring Refresh Time.
•To customize the look and feel of IPM Device Categorization, see Changing the Look of Your Portlets.
Table 11-30 lists Device Categorization portlet details.
Table 11-30 Device Categorization
Field
|
Description
|
IPSLA
|
IPSLA is a portfolio of technology embedded in most devices that run Cisco IOS software.
This allows you to analyze IP service levels for IP applications and services, to increase productivity, to lower operational costs, and to reduce the frequency of network outages.
IP SLA uses active traffic monitoring- the generation of traffic in a continuous, reliable and predictable manner-for measuring network performance.
|
Count
|
Lists the number of IP SLA enabled devices in IPM space.
Click the number to view the IPM Devices details in IPM application.
|
You can click the portlet name in the title bar to navigate to the IPM Device details page in the IPM application.
For more information, see User Guide for Internetwork Performance Monitor 4.2
IPM Availability Dashboard
The IPM Availability Dashboard will display the following details:
•Operation Types
•Number of Collectors
•Availability percentage ranges.
If you click the Availability percentage number, it displays the Availability Report.
The Availability Report page contains the following details:
•Collector Name — The name of the collector.
•Source Device — The name of the source device. However, the source device displays only the IP address and not the display name.
•Target Device — The name of the target device. However, the Target device displays only the IP address and not the display name.
•Operation — The name of the operation.
•Availability Percentage— The percentage of the availability details.
You can customize and configure the IPM Availability Dashboard portlet.
•To customize the look and feel, see Changing the Look of Your Portlets.
•To configure IPM Availability Dashboard portlet, see Configuring Refresh Time.
In the configuration screen, the portlet will display the operation type groups and user defined collector groups.
In the configuration screen, the Operation Types and User Defined Collector Groups are displayed.
•To view the Operation Types, expand the button.
•To select the Operation Types, check the check box adjacent to the Operation Types
Based on configuration this portlet will display both selected operation types groups and selected user defined collectors groups.
If no operation type groups and user defined collector groups are created, then the portlet will display the error message.
IPM Violation Summary
IPM Violation Summary portlet displays the Violation summary count of collectors.
This portlet displays seven Violation Summary details such as rfactor, MOS, ICPF, Errors, Latency, Jitter and others.
You can configure the refresh time and the violation summary details for rfactor, MOS, ICPF, Errors and so on.
To configure the Refresh time, see Configuring Refresh Time.
To configure violation summary details:
Step 1 Click the configuration icon in the IPM Violation Summary portlet.
The configuration page appears.
Step 2 Expand the group and select the checkbox against each variable.
Step 3 Click the Save button.
The selected variable appears in the portlet.
You can customize the look and feel of the IPM Violation Summary portlet.
To customize the look and feel of IPM Violation Summary portlet, see Changing the Look of Your Portlets.
Note In the IPM Violation Summary reports, the source device and the target device displays only the IP Address and not the Display Name.
Internetwork Performance Monitor
Internetwork Performance Monitor (IPM) suite is part of the CiscoWorks family of products. IPM is a network management application that allows you to monitor the performance of multi-protocol networks.
You can customize and configure the Internetwork Performance Monitor portlet.
To customize the look and feel of Internetwork Performance Monitor, see Changing the Look of Your Portlets.
To configure Internetwork Performance Monitor:
Step 1 Go to CiscoWorks LMS Portal and select IPM View.
A list of IPM portlets appear.
Step 2 Go to the Internetwork Performance Monitor portlet and click the Configuration icon.
Step 3 Select the application name from the Application drop-down list.
You can select any application name from the drop-down list.
Step 4 Click Save to view the portlet with the configured settings.
Table 11-31 lists the Internetwork Performance Monitor portlet details.
Table 11-31 Internetwork Performance Monitor Portlet
Launch Points
|
Description
|
Collector Management
|
Consists of the following components:
•Devices
Allows you to manage devices from DCR automatically/manually and add adhoc devices.
•Operations
Allows you to manage user defined operations.
•Collectors
Allows you to manage collectors.
•Group Administration
Allows you to group a set of collectors based on one or more rules.
|
Reports
|
Allows you to manage report archives, report jobs, audit reports, and system reports. The Report module consists of the following components.
•Report Archives
Allows you to manage the archived reports and create report jobs.
•Report Jobs
Allows you to manage report jobs.
•Audit Reports
Audit Trail tracks and reports all configuration changes on the IPM collectors and source devices by the IPM and administrator.
•System Reports
The system generates statistical reports for collectors based on the parameters.
These parameters are Availability, Latency, Jitter, HTTP, ICMP, PathEcho, and RTP.
The reports are generated on a daily, weekly, and monthly basis.
|
Administration
|
The Admin module allows you to set system-wide parameters for IPM such as:
•Log Level Settings
Allows you to set the log levels for IPM modules. You can either set the log levels for all IPM modules or at a modular level. By default the log level is INFO for all the modules after installation.
•Application Settings
Allows you to automatically update the Common Services' Device Credential Repository (DCR) devices in IPM, copy IP SLA (Internet Protocol Service Level Agreement) configuration to running-config, and set managed source interface.
•Purge Settings
Allows you to set the purge period for historical data and audit reports. You can also set the purge period from the LMS Setup Center.
|
For more information, see User Guide for Internetwork Performance Monitor 4.2.
IPM Workflow Demo
The IPM Workflow Demo (audio and video) portlet displays the most frequently used workflows in Internetwork Performance Monitor application.
They are as follows:
•Creating Collectors
•Creating Operations
•Creating IPM Reports
•Creating IPM Summarized Reports
Click the corresponding links to view the demo.
Note You must enable JavaScript in the browser window and install the latest version of the Flash Player to view the demo.
Working with Health and Utilization Monitor View
This section describes the portlets available in CiscoWorks LMS Portal for Health and Utilization Monitor (HUM).
Note The HUM View and portlets are displayed in CiscoWorks LMS Portal only if the HUM application is installed.
This section contains the following portlets:
•CPU Utilization Summary Chart
•Custom Top /Bottom N Records
•Device Availability
•Histo-Graph It
•HUM System Summary
•HUM Live Graph-It
•TOP-N Interface Discards
•TOP-N Interface Errors
•TOP-N Interface Utilization
•TOP-N Memory Utilization
•TOP-N-POE Utilization
•TOP-N CPU Utilization
•Threshold Information
•Trend Watch Portlet
•TOP-N Environmental Temperature
•Health and Utilization Monitor Portlet
•HUM Workflow Demo
CPU Utilization Summary Chart
The CPU Utilization Summary Chart portlet displays the CPU usage details of the devices monitored using HUM. The CPU Utilization data is summarized and displayed in a pie-chart for all the devices for a specific time interval.
You can click the pie-chart to navigate to the CPU Utilization report. The portlet also displays the total number of CPU instances for CPU utilization.
If there is no data in the CPU Utilization Summary Chart portlet, it displays the following message:
No data found. Click here to configure pollers. Please check HUMPortal.log for more details.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure pollers.
If there is data in the CPU Utilization Summary Chart portlet, it displays the following message along with the data.
Click here to configure more pollers.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure more Pollers.
Table 11-32 displays the color and CPU Utilization summary status of the device.
Table 11-32 Color and the Percentage of the CPU Utilization Summary Status
Color
|
CPU Utilization Summary Status in percentage
|
Green
|
CPU utilization from 0 to 10%
|
Yellow
|
CPU utilization from 10 to 30%
|
Orange
|
CPU utilization from 30 to 80%
|
Red
|
CPU utilization from 80 to 100%
|
You can set the time interval as 1 hour, 1 day, 7 days, 15 days, or 30 days. However by default the time interval is 1 hour.
You can customize and configure the CPU Utilization Summary Chart portlet.
To customize the look and feel of the CPU Utilization Summary Chart portlet, see Changing the Look of Your Portlets.
To configure the CPU Utilization Summary Chart portlet:
Step 1 Go to CiscoWorks LMS Portal and select HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the CPU Utilization Summary Chart portlets.
Step 3 Click the Configuration icon.
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time.
The items in the portlet get refreshed at the refresh time that you set.
•Select the time interval from the Time Interval drop-down list.
The CPU Utilization summary is shown for the selected time interval.
For example, if you select 7 Days, the details of the CPU utilization for the last seven days is displayed.
Step 4 Click Save to view the portlet with the configured settings.
Custom Top /Bottom N Records
You can create a portlet for custom template MIB variable. This portlet will enable you to view the highest as well as the lowest number of reports on user-defined templates for which pollers have been created.
This is a multi-instance portlet.
For example, if you monitor a device for the tcpMaxConn using the user-defined templates for 15 devices, you will see the highest number of records and the lowest number of records for this object.
This will be retrieved in the custom portlet where you can specify to show the top 10 records based on the tcpMaxConn values or bottom 10 records based on the tcpMinConn values.
Currently Top N/Bottom N Records reports are available only for all templates.
Table 11-33 displays the Custom Top/Bottom N Records details.
Table 11-33 Custom Top/Bottom N Records
Field/Button
|
Description
|
Auto Refresh
|
Check the Auto Refresh checkbox if you want to auto-refresh the configuration details.
|
Refresh Every
|
Select the hour and minute from the Refresh Every drop-down list.
|
Template Name
|
Select the template name from the template drop-down list. For example, Custom template.
|
Variable Name
|
Select the variable name from the Variable Name drop-down list.
For example, IfOutErrors, IfOutOctets and so on.
|
Number of rows to be displayed
|
Select the rows from the drop-down list.
For example, if you select 5, then five rows will be displayed in the portlet.
|
Sort Order
|
Select either Top N or Botton N radio buttons.
•If you select Top N, the details are sorted from the highest to the lowest order.
•If you select Botton N, then the details are sorted from the lowest to the highest order.
|
Time Interval
|
Select the time interval from the drop-down list.
If you select Time Interval, as 1 day, it will displaythe configured details for one day.
|
Field Display
|
Select either the Max or Min checkbox.
|
To configure Top /Bottom NRecords:
Step 1 Go to CiscoWorks LMS Portal and select HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Top/Bottom N Records portlets.
Step 3 Click the Configuration icon.
The Custom-Top/Bottom N Configuration page appears. You can do the following:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time.
The items in the portlet get refreshed at the Refresh time that you set.
•Check the Auto Refresh checkbox, if you want to auto- refresh the time that you set.
•Select the template name from the Template Name drop-down list.
Note The Template Name drop down list displays only those templates that have atleast one poller associated with it and not all the compiled mibs
•Select the variable name from the variable drop-down list.
•Select the rows to be displayed from the No.of rows to be displayed drop-down list.
•Select the Sort Order Top N radio button to sort the utilization in ascending order
Or
•Select the Bottom N radio button to sort the utilization in descending order.
•Select the time interval from the Time Interval drop-down list.
•Check the Display field either as Max or Min.
•Click Save to save all the changes.
Device Availability
The Device Availability portlet enables you to view the availability status of the devices in the network.
The following information is displayed as a pie chart in the Device Availability portlet.
•Availability of all managed devices in the last N number of hours.
Where N is period of time in hours. For example, 5 hours.
•Information about the last polled devices.
If all the devices are reachable, the following message appears in green:
All devices are available as per the last polled cycle
If some of the devices are unreachable, the following message appears in red.
Last Poll Status: For instance, 6 (7 %) devices of 81 are not available
You can click the pie-chart to navigate to the Device Availability report.
Table 11-34 displays the color and the percentage of the availability status of the device.
Table 11-34 Color and Percentage of Availability Status of the Device
Color
|
Availability Status of the Devices in Percentage
|
Green
|
Availability status of the device from 90 to 100%.
|
Yellow
|
Availability status of the device from 50 to 90%
|
Orange
|
Availability status of the device from 10 to 50%.
|
Red
|
Availability status of the device from 0 to 10%.
|
You can customize and configure the Device Availability portlet.
To customize the look and feel of the Device Availability portlet, see Changing the Look of Your Portlets
To configure Device Availability portlet:
Step 1 Go to CiscoWorks LMS Portal and select HUM View.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Device Availability portlets.
Step 3 Click the Configuration icon.
You can do any of the following:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time.
The items in the portlet get refreshed at changed refresh time.
•Select the time interval from the Time Interval drop-down list.
The Device Availability details are shown for the selected time interval.
For example, if you select 7 Days, the details of the device available for the last seven days will be displayed.
Step 4 Click Save to view the portlet with the configured settings.
Histo-Graph It
Histo-Graph It portlet enables you to query the information of a particular MIB variable in a device for a specified period of time and generate a graph.
You can select two MIB variables from the configuration field and generate an overlay graph through Histo-Graph It portlet.
Enter the details in the corresponding fields and click the SaveIt button to generate the graph. For more information on field details, seeTable 11-35.
After the graph appears, you can select the Export icon to export the data to either CSV or XML format.
The graph is displayed along with a link named Bookmark This Link. Right click and select Bookmark This Link to bookmark the graph.
You can also click the pop-out option to view the graph in a separate pop-up window.
The graph that appears in the separate pop-up window will not refresh automatically. Auto refresh option is applicable only to the graph that is part of the Graph It portlet.
To customize the look and feel of the Histo-Graph It portlet, see Changing the Look of Your Portlets
To generate Historical Graph:
Step 1 Go to the LMS Portal and select HUM View.
Step 2 Go to the Histo-Graph It portlet.
Table 11-35 describes the fields in the Histo-Graph It portlet.
Table 11-35 Histo-Graph It Portlet
Field /Button
|
Description
|
Device Name
|
Enter the device name. For instance, 3500XL.
|
Template Name
|
Enter the template name from the template drop-down list.
|
Available MIB
|
MIB variable polled for the device. For example, ciscoMemoryPoolFree.
|
Available Instances
|
MIB variable instances available in the device. For example, Processor.
|
Add Variable/ Remove Variable
|
The Add Variable/Remove Variable is a link.
•If you click Add Variable:
You can add more than one Device Name, MIB Variable and Available Instance for another device.
•If you click Remove Variable:
You can remove the Second Variable.
|
Interval
|
Displays the list of intervals as a drop-down list such as:
•Last 1 Hour
•Last 1 Day
•Last 1 Week
•Last 1 Quarter
•Last 1 Year
•Custom
You can select Custom to customize the time interval.
|
Start Date
|
Select the start date from the Date Time picker.
|
End Date
|
Select the end date from the Date Time picker.
|
Refresh Every
|
Select the Refresh hour and minute from the drop-down list.
|
Graph It
|
Click the Graph It button to generate a graph.
A pop-up window appears displaying a graph with the device details along with the selected MIB variable and its instances.
|
Step 3 Enter a device name in the Device Name field.
The Available MIB drop-down list populates the list of MIB variables polled for the device and select a template from the list.
Step 4 Select a MIB variable from the Available MIB drop-down list.
The Available Instances drop-down list populates the list of MIB variable instances in the device.
Step 5 Select a MIB variable instance from the Available Instances drop-down list.
Step 6 Either:
•Select an interval from the Interval drop-down list.
Or
•Select the start date and end date from the respective fields.
The DatePicker is enabled only when you select Custom for the Interval.
Note After modifying the time (hh:mm) click the data again on the pop-up calender to reflect the time change in the portlet.
Step 7 Click Graph It.
A line graph is generated displaying the historical data for the device.
Step 8 Select the Export icon at the top right corner to export the data to either CSV or XML formats.
HUM System Summary
The HUM System Summary portlet displays the summary of HUM application as follows:
•No. of Devices Managed
•No. of Objects Monitored
•No. of Failure Variables: Click the number to view the Poller Failure Report in the export.pdf file.
•Average Polled Variables per Minute
•Number of Pollers with Missed Polling Cycles
•License Status and Limit: Displays the license status and the total limit of the devices that can be managed by the application.
•Last Purge Time: Displays the date and time of the last purge
Next Purge Due: Displays the date and time for the next purge. You can click this link to navigate to the Data Purge Settings page.
You can customize and configure the HUM System Summary portlet.
To customize the look and feel of the HUM System Summary portlet, see Changing the Look of Your Portlets.
To configure HUM System Summary:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the HUM System Summary portlet to view the icons.
Step 3 Click the configuration icon.
You can select the minute and hour from the Refresh Every drop-down list to change the Refresh time.
The items in the portlet get refreshed at the changed Refresh time.
Step 4 Click Save to view the portlet with the configured settings.
HUM Live Graph-It
HUM Live Graph It portlet enables you to do real-time monitoring for any MIB variable that belongs to a device that is managed by DCR.
You need not create any poller for this device or MIB variable.
HUM Live Graph can be plotted for any devices that are managed in the DCR. After you enter the device name, template and variable name, instance querying will be done for that devices.
Table 11-36 lists the HUM Live Graph It portlet details.
Table 11-36 HUM Live Graph It portlet details
Field/Button
|
Description
|
Refresh Every
|
Select the Refresh time.
The refreshing time intervals will be the following:
•30seconds
•45seconds
•60 seconds
However, 30 seconds will be the minimum refreshing interval.
|
Device Name
|
Enter the device name.
|
Template Name
|
Enter the template name.
For example, CPU Utilization.
|
Variable Name
|
Enter the variable name.
For example, cpmCPUTotal5minRev
|
Available Instances
|
Enter the instance from the drop-down list such as CPU Processor, I/O and so on.
|
To configure HUM Live Graph It portlet:
Step 1 Go to CiscoWorks LMS Portal and select HUM View.
Step 2 Go to HUM Live Graph It portlet and click the Configuration icon.
The configuration screen appears.
Step 3 Select the time interval from Refresh Every drop-down list.
The refreshing intervals will be 30 sec, 45 sec and 60 sec. The minimum refreshing interval is 30 seconds.
Step 4 Enter the device name in the Device Name field.
Step 5 Select the template name from the Template Name drop-down list. For example, customtemp
Step 6 Select the variable name from the Variable Name drop-down list. For example, IfinDiscards.
Step 7 Select the number of instances from the Available Instances drop-down list.
Step 8 Click the Graph It button.
The monitoring graph will appear as a pop-up browser window.
The graph is displayed along with a link named Link to this page. Right click and select Bookmark This Link to bookmark the graph or you can Add to Favorites, if you are using IE.
TOP-N Interface Discards
The Interface Discards portlet displays the information about the number of packets discarded in an interface in the particular time interval.
These packets are prevented from being delivered to a high-layer protocol. Such packets are discarded to free up the buffer space.
The Interface IN Discards are the number of inbound packets discarded and the Interface Out Discards are the number of outbound packets that are discarded.
If there is no data in the TOP-N Interface Discard portlet, it displays the following message:
No data found. Click here to configure pollers. Please check HUMPortal.log for more details.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure pollers.
If there is data in the TOP-N Interface Discard portlet, it displays the following message along with the data:
Click here to configure more pollers.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure more pollers.
Table 11-37 displays the Interface Discards portlet details.
Table 11-37 TOP-N Interface Discards Portlet Details
Field
|
Description
|
Interface IN Discards
|
Device Name
|
Name of the device. For example, 3500XL.
You can click the Device Name link to launch the Device Center page.
|
Interface
|
Interfaces such as Gigabit Ethernet 1/1 (Gi3/3), Gigabit Ethernet 5/7 (Gi5/7) and so on.
You can click the Interface link to launch the Interface report page.
|
IFInDiscards (packets/sec)
|
Number of packets discarded per second.
|
Interface OUT Discards
|
Device Name
|
Name of the device. For example, 3500XL.
The display name is the name you enter in the Device Center page.
You can click the Device Name link to launch the Device Center page.
|
Interface
|
Interfaces such as Gigabit Ethernet 1/1 (Gi3/3), Gigabit Ethernet 5/7 (Gi5/7) and so on.
You can click the Interface link to launch the Interface report page.
|
IFOut Discards (pkts/sec)
|
Number of packets discarded each second.
|
You can customize and configure the Interface Discard portlet.
To customize the look and Feel of the Interface Discards portlet, see Changing the Look of Your Portlets.
To configure Interface Discards portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Interface Discards portlet to view the icons.
Step 3 Click the configuration icon.
You can:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 5, five rows will be displayed in the portlet.
•Select the time interval from the Time Interval drop-down list.
For example, if you select 7 Days, the details of the interface discards for the last seven days will be displayed.
Step 4 Click Save to view the portlet with the configured settings.
TOP-N Interface Errors
The Top-N Interface Errors portlet displays the information about the number of errors in an interface.
The Top-N Interface Errors display information on devices having highest interface errors as If ln Error and If Out Error.
The Interface IN Errors are the number of inbound packets with the errors and the Interface Out Errors are the number of out bound packets with errors.
If there is data in the TOP-N Interface Errors portlet, it displays the following message:
No data found. Click here to configure pollers. Please check HUMPortal.log for more details.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure pollers.
If there is data in the TOP-N Interface Errors portlet, it displays the following message along with the data:
Click here to configure more pollers.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure more pollers.
Table 11-38 displays the Interface Errors portlet details.
Table 11-38 TOP-N Interface Errors Portlet Details
Field
|
Description
|
Interface OUT Errors
|
Device Name
|
Name of the device. For example, 3500XL.
You can click the Device Name link to launch the Device Center page.
|
Interface
|
Displays the Interfaces such as Gigabit Ethernet 1/1 (Gi3/3), Gigabit Ethernet 5/7 (Gi5/7) and so on.
You can click the Interface link to launch the Interface report page
|
IFOutErrors (pkts/sec)
|
Packets in each second of the outgoing interface errors.
|
Interface IN Errors
|
Device Name
|
Name of the device. For example, 3500XL.
You can click the Device Name link to launch the Device Center page.
|
Interface
|
Interfaces such as Gigabit Ethernet 1/1 (Gi3/3), Gigabit Ethernet 5/7 (Gi5/7) and so on.
You can click the Interface link to launch the Interface report page
|
IFInErrors (pkts/sec)
|
Packets in each second of the incoming interface errors.
|
You can customize and configure the Interface Errors portlet.
To customize the look and feel of the Interface Errors portlet, see Changing the Look of Your Portlets.
To configure Interface Errors portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Interface Errors portlet to view the icons.
Step 3 Click the configuration icon.
You can:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time that you set.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 10, then ten rows will be displayed in the portlet.
•Select the time interval from the Time Interval drop-down list.
For example, if you select 7 Days, the Interface Errors for the last seven days will be displayed.
Step 4 Click Save to view the portlet with the configured settings.
TOP-N Interface Utilization
The Interface Utilization portlet displays information on the devices with the highest and lowest utilization based on the configuration.
If there are no data in the TOP-N Interface Utilization portlet, it displays the following message:
No data found. Click here to configure pollers. Please check HUMPortal.log for more details.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure pollers.
If there is data in the TOP-N Interface Utilization portlet, it displays the following message along with the data:
Click here to configure more pollers.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure more pollers.
Table 11-39 displays the Interface Utilization portlet details:
Table 11-39 TOP-N Interface Utilization Portlet Details
Field
|
Description
|
Device Name
|
Name of the device. For example, 3500XL.
You can click the Device Name link to launch the Device Center page.
|
Interface
|
Interfaces such as Gigabit Ethernet 1/1 (Gi3/3), Gigabit Ethernet 5/7 (Gi5/7) and so on.
You can click the Interface link to launch the Interface report page
|
Tx%
|
Percentage of transmitted utilization.
|
Rx%
|
Percentage of received utilization.
|
The Top N calculations and sorting will be done based on the sum of the percentage of the packets transmitted (Tx%) and the percentage of the packets received (Rx%).
Table 11-40 displays the color and the percentage of transmitted packets.
Table 11-40 Color and the Percentage of Packets Transmitted
Color
|
Percentage of Packets Transmitted (Tx%)
|
Green
|
Transmitted packets from 0 to 50%.
|
Yellow
|
Transmitted packets from 50 to 70%
|
Orange
|
Transmitted packets from 70 to 90%
|
Red
|
Transmitted packets from 90 to100%
|
Table 11-41 displays the color and the percentage of the received packets.
Table 11-41 Color and the Percentage of Packets Received
Color
|
Percentage of Packets Received (Rx%)
|
Green
|
Received packets from 0 to 50%
|
Yellow
|
Received packets from 50 to 70%
|
Orange
|
Received packets from 70 to 90%
|
Red
|
Received packets from 90 to 100%
|
You can configure and customize the Interface Utilization portlet.
To customize the look and feel of the Interface Utilization portlet, see Changing the Look of Your Portlets.
To configure Interface Utilization portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Interface Utilization portlet to view the icons.
Step 3 Click the configuration icon.
You can:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time that you set.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select five, then five rows will be displayed in the portlet.
•Select the Sort Order Top N radio button to sort the utilization in ascending order or Bottom N radio button to sort the utilization in descending order.
•Select the time interval from the Time Interval drop-down list.
For example, if you select 7 Days, the details of the Interface Utilization for the last seven days will be displayed.
Step 4 Click Save to view the portlet with the configured settings.
TOP-N Memory Utilization
The Memory Utilization portlet displays information about the memory usage of all devices.
It also displays the device name, instance name and the percentage of minimum, maximum and average memory utilized.
No data found. Click here to configure pollers. Please check HUMPortal.log for more details.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure pollers.
If there is data in the TOP-N Memory Utilization portlet, it displays the following message along with the data:
Click here to configure more pollers.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure more pollers.
Table 11-42 displays the color and the percentage of the memory utilization of the device.
Table 11-42 Color and Memory Utilization of the Device
Color
|
Memory Utilization of the Device in Percentage
|
Green
|
Memory utilization of the device from 0 to 50%
|
Yellow
|
Memory utilization of the device from 50 to 70%
|
Orange
|
Memory utilization of the device from 70 to 90%
|
Red
|
Memory utilization of the device from 90 to 100%
|
Note The Avg % is displayed by default in the portlet. However, the Max% and Min % have to be configured to view it in the portlet.
Table 11-43 displays the Memory Utilization portlets
Table 11-43 TOP-N Memory Utilization Portlet Details
Field
|
Description
|
Device Name
|
Name of the device. For example, 3500XL.
You can click the Device Name link to launch the Device Center page.
|
Instance Name
|
Instance name such as DRAM, FLASH, MALLOC, Processor and so on.
|
MIN (%)
|
Percentage of the minimum memory utilized by the device.
|
MAX%
|
Percentage of the maximum memory utilized by the device.
|
AVG %
|
Percentage of average memory utilized by the device.
|
You can configure and customize the Memory Utilization portlet.
To customize the look and feel of the Memory Utilization portlet, see Changing the Look of Your Portlets.
To configure Memory Utilization portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Memory Utilization portlet to view the icons.
Step 3 Click the configuration icon. You can:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time that you set.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 5, then five rows will be displayed in the portlet.
•Select the Max or Min checkbox to display both the maximum or minimum field in the portlet.
•Select the Time interval from the Time Interval drop-down list.
For example, if you select 1 Hour, then the memory utilization for the last one hour will be displayed.
Step 4 Click Save to view the portlet with the configured settings.
TOP-N-POE Utilization
The power utilization summary of network devices are displayed as PSE wise and port wise component in the TOP-N-POE Utilization portlet.
In this portlet you can configure components, such as PSE-wise summary and port-wise summary.
This portlet also displays the minimum, maximum and average power utilization of network devices in the HUM application.
Table 11-44 TOP-N-POE Utilization Portlet
Fields/Buttons
|
Description
|
Auto Refresh
|
Check the Auto Refresh checkbox for the data to be refreshed at the given interval.
|
Refresh Every
|
Select the hour and minute from the Refresh Every drop-down list.
|
Report
|
By default, the PSE reports appear. However, you can check Port to view the details.
|
No.of Reports to be displayed
|
Select the number of reports to be displayed in the portlet from the drop down list.
|
Sort Order
|
Select either Top N or Botton N radio button.
•Select Top N radio button to sort the utilization in ascending order.
•Select Bottom N radio button to sort the utilization in descending order.
|
Time Interval
|
Select the time interval from the time interval drop-down list.
|
Display Fields
|
Check Min or Min or both the checkboxes.
•If you check Min:
Only the minimum percentage of power utilization and power consumption appears in the portlet.
•If you check Max:
Only the maximum percentage of power utilization and power consumption appears in the portlet.
|
To configure TOP-N-CPU Utilization portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Go to TOP-N-POE Utilization portlet.
Step 3 Click the configuration icon.
The configuration screen appears.
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed Refresh time that you set.
•Select the Port checkbox to view the Port details also in the portlet.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 5, then five rows will be displayed in the portlet.
•Select the Sort Order Top N radio button to sort the utilization in ascending order or Bottom N radio button to sort the utilization in descending order.
•Select the Time interval from the Time Interval drop-down list.
For example, if you select 1 Hour, the memory utilization for the last one hour will be displayed.
•Select the Display field checkbox.
–If you check the Max checkbox, only the maximum power utilization or power consumption details will be displayed in the portlet.
–If you check the Min checkbox, only the minimum power utilization or power consumption details will be displayed in the portlet.
Step 4 Click Save to view the portlet with the configured settings.
TOP-N CPU Utilization
The TOP-N-CPU Utilization portlet displays information about the devices that have the highest CPU utilization percentage.
It also displays the device name, CPU instance and percentage of the minimum, maximum and the average CPU memory utilized by the device.
If there is no data in the TOP-N CPU Utilization portlet, it displays the following message:
No data found. Click here to configure pollers. Please check HUMPortal.log for more details.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure pollers.
If there is data in the TOP-N CPU Utilization portlet, it displays the following message along with the data:
Click here to configure more pollers.
You can click the here link to launch the Poller Management page. The Poller Management page allows you to configure more pollers.
Table 11-45 displays the color and the percentage of the CPU Utilization of the device.
Table 11-45 Color and Percentage of CPU Utilization of the Device
Color
|
CPU Utilization of the Device in Percentage
|
Green
|
CPU Utilization of the device from 0 to 10%
|
Yellow
|
CPU Utilization of the device from 10 to 30%.
|
Orange
|
CPU Utilization of the device from 30 to 80%.
|
Red
|
CPU Utilization of the device from 80 to 100%.
|
Table 11-46 lists the TOP-N CPU Utilization portlet details.
Table 11-46 TOP-N CPU Utilization Summary
Field
|
Description
|
Device Name
|
Name of the device.
Click the Device Name link to navigate to the Device Center page.
|
CPU Instance
|
Instance which occupies the CPU at the particular period of time.
|
MIN%
|
Minimum CPU utilization percentage value in a device.
|
MAX%
|
Maximum CPU utilization percentage value in a device.
|
AVG%
|
Average CPU utilization percentage value in a device.
|
Note The maximum and minimum fields appear in the portlet only if they are configured. The Average % field appears by default in the portlet.
You can customize and configure the TOP-N-CPU Utilization portlet.
To customize the look and feel of the TOP-N-CPU Utilization portlet, see Changing the Look of Your Portlets.
To configure TOP-N-CPU Utilization portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the TOP-N-CPU portlet to view the icons.
Step 3 Click the configuration icon. You can:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 5, then five rows will be displayed in the portlet.
•Select the Max or the Min checkbox to display either the maximum or minimum fields in the portlet.
•Select the Time interval from the Time Interval drop-down list.
For example, if you select 1 Hour, the CPU Utilization details for the last one hour will be displayed.
Step 4 Click Save to view the portlet with the configured settings.
Threshold Information
The Threshold Information portlet provides information about the threshold violation details such as threshold name, time when the violation took place, the violation value, and device name.
The Threshold Information portlet also displays the latest N number of violations.
If there is no data in the Threshold Information portlet, it displays the following message:
Currently Thresholds have not been configured. Click here to configure.
You can click the here link to launch the Threshold Setup page. The Threshold Setup page allows you to configure thresholds.
Table 11-47 displays the Threshold Information portlet details.
Table 11-47 Threshold Information Portlet Details
Field
|
Description
|
No. of Thresholds Configured
|
Displays the number of threshold configured.
You can click the number to navigate to the List of Thresholds information page.
|
No. of Violations in Last "N" time interval.
|
Displays the number of violations occurred in the configured Time Interval.
The violations are based on the severity level such low, medium and critical.
The Critical Violation is displayed by default in the portlet. However, the medium and low violations have to be configured to view it in the portlet.
•If the violation is low, it is displayed in green.
•If the violation is medium, it is displayed in orange.
•If the violation is critical, it is displayed in red.
|
Threshold Details
|
Threshold Name
|
Name of the threshold. For instance, CPU Threshold.
|
Device Name - Instance
|
Device name and the instance.
For example, the device name as 3500XL and the instance name as DRAM.
|
Time
|
Date and time when the threshold is violated.
For instance Tue, April 29 2008 18:07:08 IST
|
Violated Value
|
Displays the violated value.
|
You can customize and configure the Threshold Information portlet.
To customize the look and feel of the Threshold Information portlet, see Changing the Look of Your Portlets.
To configure the Threshold Information portlet:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
The HUM View portlets appear.
Step 2 Move the mouse over the title bar of the Threshold Information portlet to view the icons.
Step 3 Click the configuration icon. You can:
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time that you set.
•Select the severity field such as Low, Medium, or Critical from the Severity display field's drop-down list to set the severity levels.
For instance, select the Low checkbox it you want to display the low level threshold information in the Threshold Information portlet.
By default, Critical will be displayed in the Threshold Information portlet.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 5, five rows will be displayed in the portlet.
Step 4 Click Save to view the portlet with the configured settings.
Viewing Threshold Violation Report:
You can also view the Threshold Violation Reports based on the severity levels such as Low, Medium and Critical.
To view the Threshold Violation Report:
Step 1 Go to CiscoWorks LMS Portal and click HUM.
Step 2 The HUM View portlets appear.
Step 3 Go to Threshold Information portlet and click the count against the severity levels.
The Threshold Report page appears.
For instance, if you click the number against the severity level Low, the threshold report based on the lowest severity appears. The report is also based on the time interval you have selected such as 1 hour or 1 day.
Note The Threshold Report page displays the entire generated reports. However the portlet displays only a maximum of twenty generated reports.
Trend Watch Portlet
Trend Watch portlet will display a list of configured TrendWatch. Each Trend Watch name will have a link to launch the corresponding report.
There are two options available to sort the report based on the severity and the TrendWatch name.
Table 11-48 Trend Watch portlet details
Field
|
Description
|
No.of TrendWatch configured
|
Total number of Trend Watch that are configured.
|
No.of Violations in the last 15 days
|
Total number of violations that occurred during the last 15 days.
|
Trend Watch Details
|
TrendWatch Name
|
Name of the TrendWatch.
|
Count
|
The total number of the Trend Watch.
The count is displayed when you select the TrendWatch radio button.
|
Device Name
|
Name of the device.
The Device name is displayed only when you select the Severity level radio button.
|
Severity Levels
|
Displays the severtiy level.
For example, S1, S2 for severity levels 1, severity level 2, and so on.
The severity level is displayed only when you select the Severity level radio button.
|
Last Time Stamp
|
Last time stamp of the TrendWatch.
|
You can customize and configure the TrendWatch portlet.
To customize the look and feel of the TrendWatch portlet, see Changing the Look of Your Portlets.
To configure TrendWatch portlet
Step 1 Go to CiscoWorks LMS Portal and select HUMView.
The HUM View portlets appear.
Step 2 Move the mouse over the TrendWatch portlet and click the configure icon to:
•Select the Auto Refresh checkbox to refresh the portlet details at the set time interval.
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the Refresh time that you set.
•Select the Content Summary radio button to sort the content in summary order or Content Details radio button to sort the order of the content details.
•Select the Group Severity levels radio button to group the TrendWatch based on the severity or select the TrendWatch radio button to group according to the TrendWatch details.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
For example, if you select 5, five rows will be displayed in the portlet.
•Select the time interval from the Time Interval drop-down list. For example, one day, one week one month, and so on.
•Click Save to view the portlet with the configured settings.
TOP-N Environmental Temperature
The TOP N Environmental Temperature portlet enables you to monitor the temperature of the various devices.
The portlet displays the device name, instance name and the average temperature of each device.
You can customize and configure the TOP-N- Environmental Temperature portlet.
To customize the look and feel of TOP-N-Environmental Temperature portlet, see Changing the Look of Your Portlets.
To configure the TOP-N-Environmental Temperature portlet:
Step 1 Go to CiscoWorks LMS Portal and select HUMView.
The HUM View portlets appear.
Step 2 Move the mouse over the TrendWatch portlet and click the configure icon to:
•Select the Auto Refresh checkbox to refresh the portlet details at the set time interval.
•Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed refresh time that you set.
•Select the number of rows to be displayed in the portlet from the No. of rows to be displayed drop-down list.
•Select Celsius radio button, if you want to set the unit of measurement in Celsius.
Or
•Select the Farenhiet radio button, if you want to set the unit of measurement in Farenhiet.
•Select the Max checkbox, if you want to display the list of devices with maximum temperature
•Or
•Select Min checkbox, if you want to display the list of devices with minimum temperature.
•Select the time interval from the Time Interval drop-down list. For example, 1hour, 1day, 7 days, 15 days and 30 days.
Step 3 Click Save button to save all the configured details.
Health and Utilization Monitor Portlet
The Health and Utilization Monitor portlet provides you with launch points to the HUM application.
You can customize and configure the Health and Utilization Monitor portlet.
To customize the look and feel of Health and Utilization Monitor, see Changing the Look of Your Portlets.
To configure a HUM portlet from any Application portlet:
Step 1 Go to CiscoWorks LMS Portal and click the Add Portlets icon at the top right corner of the page.
A pop-up window appears.
To expand and collapse the sections, click the arrow next to the section title. Each section is a View contains a list of portlets.
Step 2 Click CiscoWorks and select Others.
A list of portlet names appears.
Step 3 Click Add next to the Application Menu portlet name.
The Application Menu portlet name is displayed in CiscoWorks LMS Portal
Step 4 Click Close to close the pop-up window.
Step 5 Move the mouse over the portlet to view the icons.
Step 6 Click the configuration icon.
Step 7 Select the Application name from the Application drop-down list.
For instance, if you want to add the Health and Utilization Monitor portlet, you can select the respective name from the drop-down list.
The Health and Utilization Monitor portlet is displayed. You can view the launch points for the HUM application from this portlet.
Step 8 Click Save to view the portlet with the configured settings.
HUM Workflow Demo
The Health and Utilization Monitor (HUM)Workflow Demo (audio and video) portlet displays the most frequently used workflows in HUM application:
They are as follows:
•Creating Pollers
•Creating Thresholds
•Creating User-defined Templates
•Importing New MIB files
•Generating HUM Reports
Click the corresponding links to view the demo.
Note You must enable JavaScript in the browser window and install the latest version of the Flash Player to view the demo.
