Table Of Contents
Working with LMS Application Views
Working with Resource Manager Essentials View
RME Job Approval
RME Device Status
RME Collector Status
Syslog Collectors Information
Syslog Alerts
Audit Trail Information
RME Hardware Summary
RME Software Summary
Change Audit
Resource Manager Essentials
Working with Campus Manager View
N-Hop View
CM Data Collection Summary
Discrepancies
Best Practices Deviation
Campus Manager
Working with Device Fault Manager View
High Severity Alerts
DFM Device Status
Device Fault Manager
Working with Internetwork Performance Monitor View
IPM Highest Latency
IPM Highest Jitter
IPM Lowest Availability
IPM Collector Information
IPM Device Categorization
Internetwork Performance Monitor
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 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 the minimal impact on the client browser application.
RME applications provide the network monitoring and fault information features 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 topics:
•RME Job Approval
•RME Device Status
•RME Collector Status
•Syslog Collectors Information
•Syslog Alerts
•Audit Trail Information
•RME Hardware Summary
•RME Software Summary
•Change Audit
•Resource Manager Essentials
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 Configuring Refresh Time.
•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 Jobs Pending Approval details page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.1.1
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 Configuring Refresh Time.
•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 device has 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.1.1.
RME Collector Status
In RME Collector Status portlet, you can view the status of the RME configurations and inventory collection status (Successfully collected, Partially Collected, Failed to Collect, and Out of Sync).
The configuration and inventory collection details of devices are added to RME and stored in the configuration archive.
The RME Collector Status portlet enables you to check the status of the last archival attempt.
•To configure RME Collector Status portlet, see Configuring Refresh Time.
•To customize the look and feel of RME Collector Status portlet, see Changing the Look of Your Portlets.
Table 11-3 lists RME Collector Status portlet details:
Table 11-3 RME Collector Status Details
Field
|
Description
|
Operation
|
Type and the status of operation such as Inventory Collection or Config Archive.
|
No.of Devices
|
Displays the 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.1.1.
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, analyser 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-4 lists the Syslog Collectors Information portlet details.
Table 11-4 Syslog Collectors Information Portlet Details
Field
|
Description
|
Name
|
Displays the host name or the IP address on which the collector is installed.
|
Status
|
Displays the status of the Remote Syslog Collector. For example, whether it is connected.
|
Received
|
Displays the number of packets received.
|
You can click the Syslog Collectors Information portlet to navigate to the Collector Status details page in the RME application.
For more information, see User Guide for Resource Manager Essentials 4.1.1.
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 Configuring Refresh Time
•To customize the look and feel of Syslog Alerts portlet, see Changing the Look of Your Portlets.
Table 11-5 lists the Syslog Alert portlet details.
Table 11-5 Syslog Alerts Details
Field
|
Description
|
Device Name
|
Displays the device name.
|
Emergency
|
Displays the number of emergency messages in the last 24 hours.
|
Alerts
|
Displays the alert state in the last 24 hours.
|
Criticals
|
Displays the 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.1.1.
Audit Trail Information
In the Audit Trail Information portlet, you can view the details of the changes made to the RME application by the user.
•To configure Audit Trail Information portlet, see Configuring Refresh Time.
•To customize the look and feel of Audit Trail Information portlet, see Changing the Look of Your Portlets
Table 11-6 lists Audit Trail Information portlet details.
Table 11-6 Audit Trail Information Details
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.1.1.
RME Hardware Summary
In the RME Hardware Summary portlet, you can view a pie graph with the distribution of all managed Cisco devices in the inventory.
•To configure RME Hardware Summary portlet, see Configuring Refresh Time.
•To customize the look and feel of RME Hardware Summary portlet, see Changing the Look of Your Portlets.
Table 11-7 lists RME Hardware Summary portlet details.
Table 11-7 RME Hardware Summary Details
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.1.1.
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 RME Software Summary portlet, see Configuring Refresh Time.
•To customize the look and feel of RME Software Summary portlet, see Changing the Look of Your Portlets.
Table 11-8 lists the RME Software Summary portlet details.
Table 11-8 RME Software Summary Details
Fields
|
Description
|
Device Categories
|
Categories of devices used in the application.
|
Software Version
|
Displays the software version of the device categories.
|
Count
|
Displays the 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.1.1.
Change Audit
In Change Audit portlet you can view the changes in the inventory and configuration information for all the devices after every Inventory or Configuration Collection.
The changes in the exception period are displayed in red.
•To configure Change Audit details, see Change Audit.
•To customize the look and feel of Change Audit portlet, see Changing the Look of Your Portlets.
Table 11-9 lists the Change Audit portlet details.
Table 11-9 Change Audit Details
Field
|
Description
|
Device Name
|
Displays the device name as entered in the Device and Credential Repository. Click the device name to launch the Device Name.
|
User Name
|
Displays the 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.1.1.
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 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.
You can select any application name from the drop-down list.
Step 4 Click Save to save the settings.
The new Application portlet appears.
Or
Click the Back arrow 
icon to return to the portlet.
Table 11-10 lists the Resource Manager Essentials portlet details.
Table 11-10 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 Systole 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.1.
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.
This application includes an operational and diagnostic tool that traces the Layer 2 and Layer 3 connectivity between two specified devices on the network.
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 sections:
•N-Hop View
•CM Data Collection Summary
•Discrepancies
•Best Practices Deviation
•Campus Manager
N-Hop View
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 N-Hop View:
•You can cross-launch the following CiscoWorks applications:
–CiscoView
–Device Center
–SWIM
To launch the applications, choose a device, right click and choose the required application.
•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 1.0.1
•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 in the map and select the required value. The selected information is displayed for all devices.
–To hide the displayed information, right click anywhere in the map and select Show/Hide Labels. Move the mouse over the label to display this relevant information as shown in the Figure 11-1.
Figure 11-1 N-Hop View
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-11.
Table 11-11 Device and Link Details of 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 N-Hop View to configure the portlet.
To configure the 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 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 N-Hop View portlet window.
Step 7 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 5 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 8 Click Save to save the settings.
The configured settings appears in the portlet.
Or
Click the Back arrow icon to return to the portlet.
Note You can also add this portlet to other application and view it.
For more information, see the User Guide for Campus Manager 5.0.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-12 lists the CM Data Collection Summary portlet details.
Table 11-12 CM Data Collection Summary Details
Field
|
Description
|
Operation
|
Displays the type of operation such as Device Discovery, Data Collection and User Tracking Acquisitions (End Hosts) and so on.
|
Last Completion Time
|
Displays the date and time when the operation was last completed.
|
Result
|
Displays the result of the operation.
Click the required link from the Result column to view the respective details page.
|
State
|
Displays the 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.0.2.
Discrepancies
In the 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 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 Discrepancies portlet, see Configuring Refresh Time.
•To customize the look and feel of the Discrepancies portlet, Changing the Look of Your Portlets.
Table 11-13 lists the Discrepancies portlet details.
Table 11-13 Discrepancy Details
Field
|
Description
|
Type
|
Type of the discrepancy such as network inconsistencies, anomalies or misconfigurations in the network.
|
Count
|
The number of deviations.
Click the number corresponding to the deviation to navigate to the Unacknowledged Discrepancy page 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.0.2.
Best Practices Deviation
In the Best Practices Deviation portlet, you can view the type and count of the deviations using the Best Practices Deviation portlet.
The 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 Best Practices Deviation portlet, see Configuring Refresh Time.
•To customize the look and feel of the Best Practices Deviation portlet, Changing the Look of Your Portlets
Table 11-14 lists Best Practices Deviation portlet details.
Table 11-14 Best Practices Deviation Details
Field
|
Description
|
Type
|
Brief description of the deviation from the Best Practice.
|
Count
|
The number of deviations.
Click the number corresponding to the deviation to navigate to the Unacknowledged Best Practices Deviation Reports page.
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.0.2.
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 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 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 save the settings.
The new Application portlet appears.
Or
Click the Back arrow icon to return to the portlet.
Table 11-15 lists the Campus Manager portlet details.
Table 11-15 Campus Manager Portlet Details
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.
|
Diagnostics
|
Allows you to view the path details such as the physical path that packets take between Cisco devices (including voice-enabled devices) and the shortcut connections where packets are IP-switched.
|
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.0.2.
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 chapter contains the following sections:
•High Severity Alerts
•DFM Device Status
•Device Fault Manager
High Severity Alerts
In 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-16 lists High Severity Alerts portlet details.
Table 11-16 High Severity Alerts Details
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.0.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 Configuring Refresh Time.
•To customize the look and feel of DFM Device Status, see Changing the Look of Your Portlets.
Table 11-17 lists DFM Device Status protect details.
Table 11-17 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.0.2.
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 save the settings.
The new Application portlet appears.
Or
Click the Back arrow icon to return to the portlet.
Table 11-18 lists the Device Fault Manager portlet details.
Table 11-18 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, and
•Adjusting logging levels.
|
For more information, see User Guide for Device Fault Manager 3.0.2.
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 topics:
•IPM Highest Latency
•IPM Highest Jitter
•IPM Lowest Availability
•IPM Collector Information
•IPM Device Categorization
•Internetwork Performance Monitor
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-19 lists the Highest Latency portlet details.
Table 11-19 Highest Latency Portlet Details
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.0.1.
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-20 lists the IPM Highest Jitter portlet details.
Table 11-20 IPM Highest Jitter Portlet Details
Field
|
Description
|
Collector Name
|
Name of the collector.
|
Operation Type
|
The 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.0.1.
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-21 lists the Lowest Availability portlet details.
Table 11-21 Lowest Availability Portlet Details
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.0.1
IPM Collector Information
In IPM Collector Information portlet, you can view the details about the state and the number of collectors.
A collector is defined as an entity that encompasses a source router, a target device, an operation, and the collector schedule details.
Collector Information is provided based on the collector status.
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-22 lists Collector Information portlet details.
Table 11-22 IPM Collector Information Portlet Details
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-23 lists the Collector Information status details
Table 11-23 Collector Information State Details
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.0.1.
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 it is to be noted that 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-24 lists Device Categorization portlet details.
Table 11-24 Device Categorization Details
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.0.1
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 Internetwork Performance Monitor portlet and click the Configuration icon.
Step 3 Select the application name from the Application drop-down list.
Step 4 You can select any application name from the drop-down list.
Step 5 Click Save to save the settings.
The new Application portlet appears.
Or
Click the Back arrow icon to return to the portlet.
Table 11-25 lists the Internetwork Performance Monitor portlet details.
Table 11-25 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.0.1.
