cc/td/doc/product/rtrmgmt/ipmcw2k/ipm21
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Preparing to Install IPM

Preparing to Install IPM

This chapter provides information to help you plan your installation of IPM including a description of the available installation methods, the supported platforms, and the hardware and software requirement. It includes the following sections:

Licensing Information

A single license for IPM allows you to install the following number of components:

For information on configuring IPM collectors, see the Cisco Internetwork Performance Monitor User Guide.

Installation Methods

You can install the IPM server and client software on the same workstation or on different workstations. You can install the IPM server and client software locally or remotely using one of the following methods:

For more information about installing the IPM client software from the web interface see the "Installing the IPM Client on Solaris Using the Web Server" section or the "Installing the IPM Client on Windows from the Web Server" section.

Supported Platforms

IPM Release 2.1 supports the following operating system platforms:


Note IPM supports running the IPM client software on Windows 95, Windows 98, or Windows NT and connecting to the IPM server running on a Sun Solaris workstation.

Hardware and Software Requirements

This document is divided into chapters according to the platform on which you will install the IPM software. Each installation chapter includes the hardware and software requirements and installation instructions specific to that platform.

Cisco IOS Software Requirements

To be manageable by IPM, source routers must be running the Cisco IOS software Release 11.2(18) or later with the Cisco IOS SAA feature (available in the IP Plus, Desktop Plus, IBM, and Enterprise feature sets) according to the following requirements.

Minimum Cisco IOS Software Releases

To run IPM, you need to have at least one of the following Cisco IOS software releases on your router:

Recommended Cisco IOS Software Releases

The recommended Cisco IOS software releases are as follows:

See Table 2-1 to look up your Cisco IOS release number and feature set to determine if it supports the Cisco IOS SAA feature and IPM.


Table 2-1: Cisco IOS Release by Feature Set to Support IPM and SAA
Cisco IOS Release Cisco IOS Feature Set IPM/SAA Support Maximum Number of Collectors

11.2(18)-11.2(x)

(where x is greater than 18)

IP Plus
Desktop Plus
IBM
Enterprise

Yes

2001

IP only
IP/IPX
Desktop

No

---

11.3(6)-11.3(y)

(where y is greater than 6)

IP Plus
Desktop Plus
IBM
Enterprise

Yes

2001

IP only
IP/IPX
Desktop

No

---

12.0(5) and later

All

Yes

5001

12.0(5)T and later2

All

Yes

5001

12.1(1) and later

All

Yes

5001

1The maximum number of collectors supported by any given router might be less than 200. This number is dependent on several factors including the router configuration buffer size, the amount of DRAM installed in the router, and the type of collectors configured in IPM.
2IP Path Echo collectors are not supported on routers running Cisco IOS software release12.0(x)T and later. To create IP Path Echo collectors, you must upgrade the router s defined as source routers to Cisco IOS software release 12.1(1) or later.


Note To support measurement of SNA response times with IPM's NSPECHO program, install either the IBM or Enterprise feature set for your Cisco IOS software release.

Configuring Routers to Support SNMP and Send SAA-Related Traps

IPM uses the SNMP protocol to communicate with the SAA feature on Cisco routers. Therefore, you must configure SNMP in every Cisco router that you want to use as an IPM source router. Also, if you want to receive traps or alerts at your NMS when thresholds are exceeded in IPM, you must enable these routers to send SAA-related traps.


Note If you have already configured your routers to support SNMP, skip to Step 5.

To configure routers to support SNMP and send SAA-related traps:


Step 1 Log in to the router in privileged mode using the following command, and type the password when prompted:

> enable
 

Step 2 To modify the router configuration, type the following command at the privileged mode prompt:

# config terminal
 

Step 3 Set the SNMP read password by entering the following command at the router:

# snmp-server community string RO
 

Where:

string is the read community string (a password for access to SNMP, usually set to public) in the router.

RO specifies read-only access to SNMP in the router.

Step 4 Set the SNMP write password with the following command:

# snmp-server community string RW
 

Where:

string is the write community string (a password for access to SNMP, usually set to private) in the router.

RW specifies read-write access to SNMP in the router.


Note Remember the SNMP community names. You will need to enter them when you add each source router to IPM.

Step 5 If you want SAA-generated traps sent to a network management host, configure the Cisco IOS software in every SAA-enabled router using the following command:

# snmp-server host address string [rtr]
 

Where:

address is the IP address of the network management host, such as 123.45.178.90.

string is the read community string for access to SNMP in the network management host.

rtr limits the traps sent to address to SAA-related traps. If you omit this value, no traps are sent to the named network management host. Sending traps is optional---not required to use IPM.

Step 6 To exit configuration mode on the router, press Ctrl-C.

Step 7 To save the changes in NVRAM for permanent storage in the startup_config file of the router, use the following command:

# wr mem
 

Note Unless you permanently save the configuration changes, they only remain in the running memory of the router (in the running_config file) until the router is restarted.

Step 8 To verify that your changes appear in both temporary storage (in the running_config file of the router) and in NVRAM (in the startup_config file), run the following commands to display the contents of those files:

# show running
# show startup
 

Note When you configure an IPM collector, it uses an index number in SNMP that might be very large. If you have defined any IPM collectors prior to saving the SNMP configuration (using the wr mem command), then these index numbers are also saved when you issue the write memory command. When an index number is a large number, the router generates warning messages when it is reloaded because these numbers are not valid through the command-line interface of the router. These SAA warning messages about the index do not indicate a problem with IPM and you can ignore them. To avoid seeing warning messages for large index numbers when you reload the router, save your SNMP configuration before defining any IPM collectors.



hometocprevnextglossaryfeedbacksearchhelp
Posted: Sun Apr 16 12:25:20 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.