|
|
The Cisco IP Manager software is part of the Cisco Service Management (CSM) System of provisioning and management tools for service providers and operators of large enterprise networks. The Cisco IP Manager program interacts with other tools in the suite to provide a fully scalable element-level management system for high-quality, rapid network services.
The Cisco IP Manager software meets business requirements for scalable, reliable Layer 3, Cisco IOS-based element management in very large networks by:
Operators can use the software either to configure new devices before they are brought on line, or to change existing configurations in live elements to support new services. Import and export features allow you to write current device configurations to files prior to provisioning the network with new data and restore the saved configurations if you need to perform a rollback.
The Cisco IP Manager software provides automated, push-button services for network-element configuration. Its features include:
Operators can propagate multiple configuration files across a large network from a single template, allowing use of standardized configuration variables such as host names, IP addresses, and subnet masks.
The template-building interface provides a mechanism for defining variables in a template file and their values in a companion data file. Configuration files can then be generated as a group, similar to a word processing application's mail-merge operation.
The software can manage multiple discrete customer networks that use the same unregistered IP address ranges. System administration allows user-based authentication. Managers can organize elements into domains and sub-domains and assign permissions to each, based on user group. Operators must enter a password to obtain access to permitted domains.
The Cisco IP Manager software also partitions and controls data access in the following ways:
A fully installed Cisco IP Manager system consists of the following elements:
If your machine has sufficient resources, you can install all of these components on the same host, or you can deploy various elements to different hosts. (Servers are described more fully in "Advanced Usage"; the installation process is described in the chapter "Installation and Configuration.")
The installation scripts supplied by Cisco can be used to install the GUI application and NEMServer, TGServer, and SGServer on any number of machines, and the central servers ADMServer, CTMServer, ES, LOGServer, and NS on another machine.
If you choose to install without using the Cisco-supplied script, any combination of servers and hosts is possible, with the following restrictions:
As shown in Figure 1-2, the GUI can be displayed on remote X displays.
Cisco IP Manager contains two new server managers:
The element manager system consists of three servers, two of which are new to Cisco IP Manager:
All three servers must be located on the same machine.
The NEMServer is the gateway master controller device. It stores and retrieves element information, which is kept in the Oracle database. For device operations, the NEMServer forwards either to the SNMP Gateway Server (SGServer) or Telnet Gateway Server (TGServer), depending on the connect type for the element.
The Telnet Gateway Server (TGServer) and SNMP Gateway Server (SGServer) are closely tied with the NEMServer. Both Gateway modules are registered with the Name Server (NS).
Any element can use either Telnet or SNMP, whichever the element supports; the element connect type attribute must be set through the GUI.
The SGServer monitors router configuration changes by listening for SNMP traps that you can specify. The SGServer listens for SNMP traps on the standard SNMP trap port 162. To listen for SNMP traps, the SGServer needs to be run as root and listens on UDP port 162. Therefore, no other process on the same machine can listen on that port.
The TGServer is transparent to the user. A properties file stores telnet attributes such as the tftp server IP address, timeout value, and so on, in such a way that TGS can be relaunched without losing its attribute data.
This history is useful for performing change analysis and rollback later. The Archive Manager allows you to store and view different versions of configuration files. The system compares the current configuration file with a previous version of the configuration file and returns results of the comparison. The Archive Manager also provides version control for other text files, such as the template body, as described in "Managing Templates."
The following sections describe the equipment that can be provisioned by the Cisco IP Manager software and the equipment required to run it.
For a list of products and Cisco IOS releases currently certified, see the release notes.
Your system must have the following software installed:
The Cisco IP Manager GUI uses the Java 1.2 run-time environment. Table 1-1 shows the required and recommended patches for JDK 1.2 on Solaris 2.6.
| Patch | Comment |
|---|---|
105633-10 or later | required |
106040-10 or later | required |
105568-02 or later | recommended |
Specific hardware requirements can vary greatly depending on configuration of the software and client/server distribution. For information about installation options, you should consult with your Cisco customer service engineer. Also, see "Installation and Configuration."
A Sun Ultra 60 with 512 MB of RAM and a 2 GB hard drive is the minimum recommended machine for running the CENTER-LITE server packages. If packages are installed separately, each host should meet these specifications. The DNEM package can be run on a Sun Ultra 10 with at least 256 MB of RAM.
These estimates assume an average of six interfaces per router, moderate use of access lists, and typical WAN connectivity. You may need additional resources if your network has a larger number of interfaces per router, makes extensive use of access lists, or is heavily meshed.
Memory and swap space requirements vary considerably, depending on your installation configuration and the size of your network. A general rule for swap space is twice RAM.
The following table shows the disk space required to install the various packages:
| Package | Description | Size |
|---|---|---|
CENTER-LITE | All center servers | 298 MB |
SNES | Name-Event Servers | 229 MB |
GUI-LITE | GUI client | 223 MB |
DNEM | NEM server | 174 MB |
DTGS | Telnet Gateway server | 164 MB |
DSGS | SNMP Gateway server | 198 MB |
ALL | Complete package | 420 MB |
In addition to the space requirements listed in the table, during installation your system should have available about twice the indicated storage as temporary storage space used during decompression of the modules.
Posted: Mon Feb 14 14:13:29 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.