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

Table of Contents

Preparing to Install IPM

Preparing to Install IPM

This chapter provides the following information to help you plan the installation of IPM software release 2.0:

IPM software release 2.0 provides flexibility for the installation of the client and server software. This flexibility comes in the IPM support of multiple system platforms, including support of a mixed operating environment where the client operating system can be different from the server operating system, and in alternate methods for installing the IPM client software.

Licensing Information

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

To support more than 100 collectors, additional licenses can be purchased. For more information about setting up IPM collectors, see the Internetwork Performance Monitor User Guide.

Description of Installation Methods

The IPM server and client software can be installed on the same workstation, or they can be installed to run on separate 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 client software using the web interface see the "Installing the IPM Client Software Using the Web Server" chapter.

Supported Platforms

IPM software release 2.0 supports the following operating system platforms:

Solaris version 2.5.1 is equivalent to SunOS version 5.5.1 and Solaris version 2.6 is equivalent to SunOS version 5.6.

Note IPM supports Windows NT clients running IPM with a Sun Solaris server.

This book is divided into chapters according to the system platform on which you will install the IPM software. Each installation chapter includes the requirements specific to that platform and provides complete instructions for that environment.

Hardware and Software Requirements

This section describes the hardware and software requirements for all platforms, including the workstation requirements and Cisco IOS software requirements for IPM.

Workstation Requirements

This section describes the following hardware and operating system software requirements to run IPM on a UNIX or Windows NT workstation:

UNIX Workstation Requirements

All UNIX platforms require the following hardware and software to run IPM:

Sun Solaris Patch Requirements

The Solaris patches listed by version in this section are also required to install IPM. These patches are installed separately or as a jumbo patch from Sun Microsystems, Inc. To verify the patches installed on your Solaris system, run the showrev -p command.

To obtain the patches, contact your Sun Microsystems representative or download them from the Sun web site.

Solaris 2.5.1 Patches

The following minimum patch levels are required to run IPM on Solaris version 2.5.1:

Solaris 2.6 Patches

The following minimum patch levels are required to run IPM on Solaris version 2.6:

Windows NT Client Workstation Requirements

Windows NT client platforms require the following hardware and software:

Cisco IOS Software Requirements

To be manageable by IPM applications, source routers must be running the Cisco IOS software releases according to the following requirements.


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 release.

Cisco IOS Release 11.2 Software Requirements

If you are running Cisco IOS release 11.2 on the router, then the following release levels are required:

If you want to run IPM collectors for longer than 24 days, and you are running Cisco IOS release 11.2 on your router, then you need the following version of the Cisco IOS 11.2 software release:

Cisco IOS Release 11.3 Software Requirements

If you are running Cisco IOS release 11.3 on the router then the following release level is required:


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


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

11.2(8) and earlier

All

No1

---

---

11.2(8)-11.2(15)

  • IP Plus

  • Desktop Plus

  • IBM

  • Enterprise

Yes

23 days

2002

  • IP only

  • IP/IPX

  • Desktop

No1

---

---

11.2(16)-11.2(x)

(where x is greater than 16)

&&Center&&

  • IP Plus

  • Desktop Plus

  • IBM

  • Enterprise

Yes

Forever

2002

  • IP only

  • IP/IPX

  • Desktop

No1

---

---

11.3(0)-11.3(5)

All

No1

---

---

11.3(6)-11.3(y)

(where y is greater than 6)

&&Center&&

  • IP Plus

  • Desktop Plus

  • IBM

  • Enterprise

Yes

Forever

2002

  • IP only

  • IP/IPX

  • Desktop

No1

---

---

12.0 and later

All

Yes

Forever

5002

1. RTR is not supported on this router platform, which means that IPM cannot use this router as a source router. However, like all devices with IP addresses, IPM can use the following series of routers as monitored targets: Cisco 12000 series gigabit switch router (GSR), Cisco 1000 series router, Cisco 700 series router, and Cisco 90 series router.
2. The maximum number of collectors supported by any given router may 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.

Configuring Your Routers to Support SNMP and Send RTR-Related Traps

IPM uses the SNMP protocol to communicate with the RTR option on a router. If you have not already configured the routers in your network to support SNMP and send RTR-related traps, follow these steps to configure the Cisco IOS software in every source router.

If you have already configured your routers to support SNMP and send RTR traps, skip to Step 5.

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 this command at your router:

    # snmp-server community string RO
     
    

Where:

string is the read community string (a password for access to SNMP, typically public is used) in this router.

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

Step 4 Set the SNMP write password with this command:

    # snmp-server community string RW
     
    

Where:

string is the write community string (a password for access to SNMP, typically private is used) in this router.

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

Step 5 If you want RTR-generated traps to be sent to a network management host, configure the Cisco IOS software in every RTR-enabled router using this 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 RTR-related traps. If you omit this value, no traps are sent to the named network management host.

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, run the write memory command as follows:

    # wr mem
    

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 the write memory command is run. 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 RTR warning messages about the index do not indicate a problem with IPM and they can be ignored. To avoid seeing these warning messages for large index numbers when you reload the router, save your SNMP configuration before you define any IPM collectors.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Mar 12 11:22:31 PST 1999
Copyright 1989-1999©Cisco Systems Inc.