Administration of Cisco Prime LAN Management Solution 4.1
Chapter 9: Monitoring and Troubleshooting Settings
Download this chapter
Chapter 9: Monitoring and Troubleshooting SettingsChapter 9: Monitoring and Troubleshooting Settings
Download the complete book
admin41ug.pdfadmin41ug.pdf (PDF - 7 MB)
 Feedback

Table Of Contents

Monitoring and Troubleshooting Settings

Configuring Fault Poller Settings For Topology

Loading MIB Files

Configuring NAM

Configuring RMON

Modifying the Parameters

Enabling RMON on All Ports in Selected Devices

Enabling RMON on Selected Ports in Selected Devices

Disabling RMON

Configuring Topology Settings

Viewing Restricted Topology


Monitoring and Troubleshooting Settings

Monitoring and Troubleshooting Settings in the Admin menu groups all the administrative tasks that you need to perform to monitor and troubleshoot your network using LMS.

This section contains:

•Configuring Fault Poller Settings For Topology

•Loading MIB Files

•Configuring NAM

•Configuring RMON

•Configuring Topology Settings

Configuring Fault Poller Settings For Topology

To display Fault Poller information in Topology Maps and N-Hop view portlet, you have to enable polling as follows:

Step 1 Select Admin > Network > Monitor / Troubleshoot > Fault Poller settings for topology.

The Fault Monitor Poller Settings page appears.

Step 2 Select the Poll Fault Monitor Server for alerts check box.

If you try to apply the settings when Fault Monitor module is not installed on a local or remote server, you will get an error message indicating the same.

If Fault Monitor module is enabled, the list of LMS servers detected is displayed above this check box.

You can enable this option, only if:

–Fault Monitor module is installed in the local LMS Server or on a remote LMS Server in the master slave mode.

AND

–LMS has detected the Fault Monitor server.

If Fault Monitor module is installed after running Data Collection, either run Data Collection or restart ANI Server before enabling the above setting.

Step 3 Set the time interval at which the polling should occur.

Fault Monitor updates the latest event information every 6 minutes. So the time interval can be a value between six minutes and fifty nine minutes, fifty nine seconds.

Step 4 Click Apply. The settings are saved to the server and polling starts within six minutes of the configuration.

In addition to this, you can restrict the type of LMS event displayed in your machine. For example you can choose to display only critical events in Topology maps.

The event information fetched from Fault Monitorserver can be launched from Topology Maps and N-Hop view portlet, by right clicking on the required device.

Loading MIB Files

You can load a new MIB file into LMS using the Load MIB option. The new MIB file is compiled and stored in LMS. You can use the new MIB file to create new templates by grouping MIB variables, to do this select Monitor > Performance Settings > Setup > Templates. For more information, see Creating a Template in Monitoring and Troubleshooting Online Help.

You can load MIB files with the file extension .my.

To load a MIB file:

Step 1 Select Admin > Network > Monitor / Troubleshoot > Load MIB.

The Load MIB dialog box appears.

Table 9-1 describes the field in the Load MIB dialog box.

Table 9-1 Load MIB Fields

Field
Description

MIB file

Use the Browse button to load a MIB file from a directory location.

For example, RFC1213-MIB.my

You are allowed to load a MIB file only from the following directory path:

•In Windows, $NMSROOT\hum\mibmanager\mibcompiler\mibs

•In Solaris/Soft Appliance, $NMSROOT/hum/mibmanager/mibcompiler/mibs

$NMSROOT is the default Cisco Prime LMS installation directory.


Step 2 Click Browse to select the MIB file from a directory location.

The Server Side File Browser dialog box appears.

Step 3 Double-click the MIB file from the directory location.

Step 4 Click Apply to load the MIB file into LMS or Cancel to cancel the operation.

You will be able to load and compile a new MIB file into LMS only when its dependent MIB files are available in the directory location.

For example,

To load and compile RFC1213-MIB, the dependent MIB files for RFC1213-MIB (RFC1155-SMI and RFC-1212) must also be available at the same directory location. If the dependent MIB files are not available, an appropriate error message is displayed and RFC1213-MIB does not compile.

The dependent MIB files are case sensitive, the names of these dependent MIB files should be the same as the MIB files names present in the definition files. Load only version2 MIB.

The following is the list of basic dependent MIBs that will be required for loading other MIBs in LMS:

•RMON2-MIB.my

•BRIDGE-MIB.my

•RFC-1215.my

•INET-ADDRESS-MIB.my

•P-BRIDGE-MIB.my

•Q-BRIDGE-MIB.my

•CISCO-NETFLOW-MIB.my

•CISCO-STACK-MIB.my

•TOKEN-RING-RMON-MIB.my

•RFC-1212.my

•RMOM-MIB.my

•RFC1155-SMI.my

•RFC1213-MIB.my

•SNMP-FRAMEWORK-MIB.my

•CISCO-SMI.my

•ENTITY-MIB.my

•FDDI-SMT73-MIB.my

•CISCO-VTP-MIB.my

•SNMPv2-TC.my

•SNMPv2-SMI.my

•SNMPv2-MIB.my

•SNMPv2-CONF.my

•IF-MIB.my

•IANAifType-MIB.my

To view the list of more dependent MIBs go to: http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2 The compiled MIB file appears in the Show MIB drop-down list in Select MIB Variables page.

Configuring NAM

NAM refers to Cisco Network Analysis Module Traffic Analyzer. The NAM offers flow-based traffic analysis of applications, hosts, and conversations, performance-based measurements on application, server, and network latency, quality of experience metrics for network-based services such as voice over IP (VoIP) and video. Only NAM 4.1 is supported in LMS 4.1.

To add, edit, or delete the NAM configuration details:

Step 1 Select Admin > Network > Monitor / Troubleshoot > NAM Configuration. The NAM Configuration page appears.

Step 2 You can do the following:

•Add

–Click Add. The Add NAM Configuration page appears.

–Enter the IP Address in the NAM IP field.

–Enter the user name and password in the corresponding fields.

–Enter the SNMP read community.

–Select either HTTP or HTTPS as the protocol.

–Enter the port number.

–Click Add to add the new NAM configuration details or Cancel to return to the NAM Configuration page.

•Edit

–Select a configuration detail that has to be edited.

–Click Edit. The Edit NAM Configuration page appears.

–Enter the IP Address in the NAM IP field.

–Enter the user name and password in the corresponding fields.

–Enter the SNMP read community.

–Select either HTTP or HTTPS as the protocol.

–Enter the port number.

–Click Edit to save the changes or Cancel to return to the NAM Configuration page.

•Delete

–Select a configuration detail that has to be deleted.

–Click Delete. A confirmation dialog box appears.

–Click OK to confirm or Cancel to return to the NAM Configuration page.

Configuring RMON

You can enable RMON to measure Bandwidth Utilization for Topology.

Bandwidth Utilization is the measure of traffic flowing across a link. LMS highlights bandwidth utilization across links, in the Topology maps. It computes the bandwidth utilization by taking the best estimate of the mean physical layer network utilization on the links, during the sampling time interval.

In Topology Map, LMS can differentiate the links using colors, based on the bandwidth utilized by them. You can customize the filters to display bandwidth utilization.

For more details, see Customizing Bandwidth Utilization Filters in Monitoring and Troubleshooting Online Help.

This section contains:

•Modifying the Parameters

•Enabling RMON on All Ports in Selected Devices

•Enabling RMON on Selected Ports in Selected Devices

•Disabling RMON

Note LMS computes bandwidth utilization only on ethernet links, and not on any other type of link.

To compute bandwidth utilization in LMS, you must enable Remote Monitoring (RMON). Enabling RMON depends on two parameters.

Parameters to Compute Bandwidth Utilization

Enabling RMON depends on the following parameters:

•Bucket Size—Number of samples (incoming and outgoing packets) that will be examined for a given point of time.

•Interval—Duration for which samples are to be collected.

The default values for Bucket Size and Interval are 10 and 300 respectively. Though you cannot edit the values through the user interface of LMS, you can reconfigure these values through command line interface. For more details see Modifying the Parameters.

LMS computes bandwidth utilization only for those devices that have the same parametric values as configured and displayed in the RMON Settings page. This application allows you to configure only the same parametric values on all link ports. This is to avoid conflicts in computation.

Enabling RMON on Ports

LMS allows you to enable RMON on:

•All Ports in selected devices. For details, see Enabling RMON on All Ports in Selected Devices

•Selected Ports in selected devices, see Enabling RMON on Selected Ports in Selected Devices

LMS highlights links in the Topology Map even if the devices are managed by other applications such as HPOV, or CiscoView.

Modifying the Parameters

The default Bucket Size is 10 and the Interval is 300 seconds. LMS does not compute bandwidth utilization for the links whose ports have different Interval values.

You can configure new values for the parameters in the ANIServer.properties file. To reconfigure the values, you must restart the ANI server so that the file takes the new value.

For computing bandwidth utilization, LMS takes only the latest values in the ANIServer.properties file. You must reconfigure the link ports according to the values set in the properties file for Topology Map to highlight the links.

You must reconfigure the parametric values before you enable RMON on ports.

Note You must configure the same value for Interval across the devices.

To reconfigure the values:

Step 1 Enter pdterm ANIServer at the command line to stop the ANI server.

Step 2 Go to NMSROOT/campus/etc/cwsi/ANIServer.properties.

Step 3 Modify the values of the properties, RMON.interval for Interval and RMON.bucketSize for the Bucket Size.

The maximum value that you can enter for RMON.interval is 3600 seconds (One hour).

Step 4 Enter pdexec ANIServer at the command line to start the ANI server.

After modifying the bucket size and interval, enable RMON in devices as explained in Enabling RMON on All Ports in Selected Devices or Enabling RMON on Selected Ports in Selected Devices.

You can use RMON.percentageTolerance property in the ANIServer.properties file to provide a value for the Interval in a range. This is a hidden property that creates a range for the Interval value.

The property adds a value to the current interval that forms the upper limit and subtracts a value from the current interval that forms the lower limit of the range. The default hidden value is 10 percent of the interval.

For example, if the value provided in the ANIServer.properties file is 300, the range will be 270-330. Thus, the samples are collected for the range of 270 to 330 seconds.

If you want to change this default value, you must:

Step 1 Stop the ANI server.

Step 2 Enter pdterm ANIServer at the command line to stop the ANI server.

Step 3 Go to NMSROOT/campus/etc/cwsi/ANIServer.properties.

Step 4 Enter RMON.percentageTolerance=value.

Step 5 Start the ANI server.

Step 6 Enter pdexec ANIServer at the command line to start the ANI server.

Enabling RMON on All Ports in Selected Devices

To enable RMON on all ports in selected devices:

Step 1 Select Admin > Network > Monitor / Troubleshoot > RMON Configuration.

The Enable RMON dialog box appears. The Device Selector pane displays a list of all devices.

Step 2 Select the check box corresponding to the devices for which you want to enable RMON.

The RMON Settings area displays the default Bucket Size required as 10; and the Interval in seconds as 300.

For a Bucket Size of 10, and interval of 300 seconds, LMS collects 10 samples of bandwidth utilization across links over a period of 50 minutes, with an interval of 5 minutes (300 seconds).

To modify the Bucket Size and Interval, see Modifying the Parameters. If you modify the parameters, repeat all the steps listed in this section, for enabling RMON with the new parameters.

Step 3 Check the Configure on all links check box to configure all the ports of the selected devices in the Device Selector.

Step 4 Click Configure to enable RMON on all the ports in the selected devices.

The following command is configured on the selected ports:

rmon collection history integer owner ownername buckets bucket-number interval seconds

Example:

rmon collection history 4 owner campusmanager buckets 10 interval 300

Enabling RMON on Selected Ports in Selected Devices

To enable RMON on selected ports in selected devices:

Step 1 Select Admin > Network > Monitor / Troubleshoot > RMON Configuration.

The Enable RMON dialog box appears. The Device Selector pane displays the list of devices.

Step 2 Select the check box corresponding to the devices for which you want to enable RMON.

The RMON Settings area displays the default Bucket Size required as 10; and the Interval in seconds as 300.

For a Bucket Size of 10, and interval of 300 seconds, LMS collects 10 samples of bandwidth utilization across links over a period of 50 minutes, with an interval of 300 seconds (5 minutes).

To modify the Bucket Size and Interval, see Modifying the Parameters. If you modify the parameters, repeat all the steps listed in this section, for enabling RMON with the new parameters.

Step 3 Uncheck the Configure on all Links check box since it is checked by default.

Step 4 Click Select links to select the ports for which you want to enable RMON.

It displays the list of ports in the selected devices. For details on the list displayed, see Table 9-2.

The Select Links check box is enabled only when you uncheck the Configure on all links check box.

Table 9-2 Select Links for RMON Configuration Column Description 

Column
Description

Port

Name of the port.

Device Name

Name of the device where the port is connected.

Device Address

The IP address of the device.

isLink

True is displayed for link ports and False for a non-link port.


Step 5 Select check boxes corresponding to the ports for which you want to enable RMON.

Step 6 Click Configure to enable RMON on the selected ports.

The following command is configured on the selected ports:

rmon collection history integer owner ownername buckets bucket-number interval seconds

Example:

rmon collection history 4 owner campusmanager buckets 10 interval 300

Disabling RMON

After you have enabled RMON on a device through LMS, you can disable it using Command Line Interface (CLI) only.

Commands to Disable RMON

For a device running Cisco IOS, enter the following command at the CLI prompt:

no rmon

For a device running Catalyst operating system, enter the following command at the CLI prompt

set snmp rmon disable

Configuring Topology Settings

You can configure the following Topology Settings:

•Restrict Topology Maps to display only authorized devices.

For details, see Viewing Restricted Topology.

•Configure LMS to fetch event information from Fault Monitor, and display it in Topology Maps.

For details, see Configuring Fault Poller Settings For Topology.

Viewing Restricted Topology

Topology Maps display all the devices discovered by LMS.

To view the Restricted Topology:

Step 1 Select Admin > Network > Monitor / Troubleshoot > Restricted Topology View.

The configuration screen is displayed.

Step 2 Select Display Only the Authorized devices in Topology Maps.

Step 3 Click Apply.

Topology Maps display only the devices you are authorized to view. If Topology Services is already launched, close it and relaunch for the change to take effect.

Important Notes

If you change the management IP address of an authorized device:

•It becomes an unauthorized device.

•The device is not shown in Topology maps in the consecutive relaunches.

•When the changed IP address is given as root in N-hop view portlet, it results in an error.