Table Of Contents
Prerequisites
Product Overview
Preparing to Install RME
RME Installation, Upgrade and Migration Paths
RME Installation
Upgrade Paths
Migration Paths
Server Requirements and Recommendations
Minimum Server Requirements
Server Recommendations
Client Requirements
Additional Client Requirements
RME Port Usage
Supported Devices
Prerequisites
This chapter describes the prerequisites for installing Resource Manager Essentials 4.0.3 on a Windows system. It consists of:
•
Product Overview
•
Preparing to Install RME
Product Overview
Resource Manager Essentials (RME), one of the major components of CiscoWorks, enables the deployment, configuration, and monitoring of devices across your network. RME is a suite of web-based network management tools integrated into a network desktop that includes web-based tools, and web-browser capability.
This product is based on a client/server network architecture that connects multiple web-based clients to a network server.
The RME CD-ROM contains the Resource Manager Essentials 4.0.3 installable package.
Preparing to Install RME
This section describes prerequisites and other factors you should consider before installing RME. This consists of:
•
RME Installation, Upgrade and Migration Paths
•
Server Requirements and Recommendations
•
Client Requirements
•
Supported Devices
•
RME Port Usage
RME Installation, Upgrade and Migration Paths
This section outlines the steps for installing, upgrading, and migrating to RME 4.0.3.
RME Installation
You must install RME 4.0.3 on a system with CiscoWorks Common Services 3.0.3. You can install RME 4.0.3 on a system with:
•
CiscoWorks Common Services only.
•
Common Services and any of the other CiscoWorks applications that are included in the LAN Management Solution 2.5.1 product.
If you are installing RME with contents of the LAN Management Solution, check the installation order as described in the quick start guide (see Related Documentation).
For RME 4.0.3 fresh installation instructions, see "Installing RME".
Upgrade Paths
This involves overwriting the existing RME version with the new RME version. The data may be migrated to the newer version based on the installed LMS application. To see the data that gets migrated, see "Upgrading and Migrating RME".
You can upgrade to RME 4.0.3 from any one of these versions:
•
RME 4.0.x to RME 4.0.3
•
RME 3.5.x to RME 4.0.3
•
RME 3.4.x to RME 4.0.3
For more information, see "Upgrading and Migrating RME".
Migration Paths
If you have any one of the following versions of RME, to be in RME 4.0.3 you must migrate your RME data:
•
RME 3.5.x to RME 4.0.3
•
RME 3.4.x to RME 4.0.3
For more information, see "Upgrading and Migrating RME".
Server Requirements and Recommendations
This section describes the server requirements and recommendations for CiscoWorks Common Services 3.0.3 (Common Services) and RME 4.0.3.
See Installation Guides for CiscoWorks Common Services 3.0.3 for list of Solaris and Windows patches that have to be installed on CiscoWorks server and client:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/
cw2000_d/cs303/index.htm
Minimum Server Requirements
The minimum system requirements for a CiscoWorks Server running the Common Services 3.0.3 and Resource Manager Essentials 4.0.3 software are shown in Table 1-1.
Table 1-1 Server System Minimum Requirements
Requirement Type
|
Minimum Requirements
|
System hardware
|
• 1 GHz Pentium IV processor for Restricted license.
• Dual 2.8 GHz Pentium IV processor for Unrestricted license
|
System software
|
One of the following:
• Windows 2000 Professional, Server, Advanced Server with terminal services (in remote admin mode) or Server with Service Pack 4.
• Windows 2003 Standard and Enterprise Edition with terminal services (in remote admin mode) with Service Pack 1.
RME supports only US-English and Japanese versions of Windows Operating System. It does not support any other language version.
Set the default locale to US-English for US-English version of RME and Japanese for Japanese version of RME.
ODBC Driver Manager1 3.5.10.
|
Memory (RAM)
|
• 1GB for Restricted license
• 2 GB for Unrestricted license.
|
Available drive space2
|
• 4 GB for Restricted license
• 8 GB for Unrestricted license.
• Enough space for storing device software image files3 .
• Paging space equal to double the amount of memory (RAM). For example, if your system has 512 MB of RAM, you need 1024 MB of paging space.
• NTFS file system required for secure operation.
• 16 MB in the Windows temporary directory (%TEMP%).
|
Additional required software
|
Common Services 3.0.3 must be installed before installing RME. For instructions, see Installation and Setup Guide for Common Services 3.0.3 (Includes Ciscoview) on Windows.
|
Additional optional software
|
One of these browsers:
• Microsoft Internet Explorer 6.0 (version 6.0.3790.0) with SP1.
• Netscape Navigator 7.1 and 7.2
• Mozilla 1.7.1 and 1.7.5
|
Server Recommendations
To select or configure a server system that best meets your needs, you must consider the number of managed devices expected in Inventory, Configuration Management, and Software Management applications.
These factors affect server performance and response time.
Table 1-2 shows the recommendations for a server running Common Services and RME. These recommendations produce optimal response time while running user reports.
Table 1-2 Server System Recommendations
Minimum System Configuration
|
Inventory
|
Configuration Management
|
Software Management
|
Pentium III, 500 MHz
Memory: 1 GB MB Virtual memory: 2 GB Available disk space: 40 GB
|
0-300 devices
|
0-300 devices
|
0-300 devices
|
Dual Processor Pentium III, 1.26 GHz
Memory: 2 GB Virtual memory: 4 GB Available disk space: 80 GB
|
Up to 3000 devices
|
Up to 2000 devices
|
Up to 1700 devices
|
Client Requirements
The recommended client system requirements for Common Services and RME are shown in Table 1-3.
Before you access RME from a client system, you must configure the system. For more information about client system requirements and configuring clients, see Installation and Setup Guide for Common Services 3.0.3 (Includes Ciscoview) on Windows.
Table 1-3 Client System Requirements Summary
Requirement Type
|
Minimum Requirement
|
System Software and Hardware
|
One of the following:
• IBM PC-compatible system with at least a 300 MHz Pentium processor running,
– Windows 2000 (Professional, Server, and Advanced Server) with Service Pack 4
– Windows Server 2003 (Standard and Enterprise Edition) with Service Pack 1
– Windows XP with Service Pack 2
RME supports only US-English and Japanese versions of Windows OS. Set the default locale to US-English for US-English version of RME and Japanese for Japanese version of RME.
• Solaris 8 (Solaris 2.8) or Solaris 9 (Solaris 2.9).
|
Memory (RAM)
|
512 MB
|
Browser
|
One of these browsers:
• On Windows 2000, Windows 2003, and Windows XP clients:
– Microsoft Internet Explorer 6.0 Service Pack 1 on Windows 2000 and Windows 2003
– Microsoft Internet Explorer 6.0.2900.2180 on Windows XP.
– Netscape Navigator 7.1 and 7.2
– Mozilla 1.7.1 and 1.7.5
• On Solaris clients:
– Netscape Navigator 7.0 1 for Solaris 8 (Solaris 2.8) and Solaris 9 (Solaris 2.9)
– Mozilla 1.7 and 1.7.5 for Solaris 8 (Solaris 2.8) and Solaris 9 (Solaris 2.9)
|
Additional Client Requirements
The Table 1-3 lists minimum client requirements for RME. Some memory and processor intensive operations might require higher client requirements. For example, scheduling or viewing NetConfig jobs containing more than 500 devices, we recommend the following additional client requirements:
Requirement Type
|
Minimum Requirement
|
System Hardware
|
IBM PC-compatible computer with at least 450 MHz Pentium processor running Windows 2000 (Professional or Server), or Windows XP.
|
Memory (RAM)
|
384 MB.
|
Virtual Memory
|
1024 MB.
|
RME Port Usage
Table 1-4 lists the ports used by RME.
Table 1-4 RME Port Usage
Protocol
|
Port Number
|
Service Name
|
Direction (of Establishment) of Connection
|
ICMP
|
7
|
Ping
|
Server to Device
|
TCP
|
22
|
Secure Shell (SSH)
|
Server to Device
|
TCP
|
23
|
Telnet
|
Server to Device
|
TCP
|
25
|
Simple Mail Transfer Protocol (SMTP)
|
Server Internal
|
TCP
|
514
|
rsh Daemon
|
Server to Device
|
TCP
|
1742
|
SSL (HTTPS)
For SSL, by default, the port is 443.
|
Client to Server
|
TCP
|
3333
|
Syslog Collector Service and Syslog Analyzer Service
|
Server Internal
|
TCP
|
43455
|
RME Database
|
Server Internal
|
TCP
|
4444
|
Syslog Collector Service and Syslog Analyzer Service
|
Server Internal
|
TCP
|
47000 - 47020
|
RME CSTM (Common Services Transport Mechanism) Server.
Used for internal application communication.
|
Server Internal
|
UDP
|
69
|
Trivial File Transfer Protocol (TFTP)
|
Server to Device
Device to Server
|
UDP
|
161
|
Simple Network Management Protocol (SNMP)
|
Server to Device
Device to Server
|
UDP
|
162
|
SNMP Traps (Standard Port)
|
Device to Server only (nGenius Real-Time Monitor);
Server to Device Device to Server (all others)
|
UDP
|
514
|
Syslog
|
Device to Server
|
UDP
|
42342
|
OSAGENT
|
Server Internal (Common Services); RSAC to Server via OSAGENT (RME)
|
Supported Devices
Device packages for all supported devices are installed when you install RME. Information about these devices is at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
e_4_x/4_0_3/sdt/index.htm
To see the list of installed RME device packages, select Software Center > Resource Manager Essentials on the CiscoWorks homepage.
As additional device packages become available, you can download the Service Packs (formerly called IDUs) that contain them, by logging into Cisco.com at:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme