|
|
The Cisco IP Manager software consists of several servers (separate executable files) and a graphical user interface (GUI) application. You can install all of the servers on one machine or divide them among several machines.
You can install the GUI application on the server machine or on one or more client workstations. You can run the GUI application locally or you can log in remotely using the UNIX rlogin command.
Before you begin, you need to know the host name of the machine (or machines) on which your Name Server and Event Server are to be installed, and all server hosts should be capable of translating host names into IP addresses (using DNS---recommended---or some other means of host name resolution).
You must have an Oracle database installed and operational before you can successfully launch the Cisco IP Manager software.
You must install Oracle before you install the Cisco IP Manager software (or at least know your Oracle home directory, host machine, and Oracle Server ID), and your database must be running when you launch the Cisco IP Manager servers. See the section "Minimum System Requirements" in "Cisco IP Manager Overview," for a list of required Oracle components.
If you have already installed Oracle, you can perform the installation process a second time with a new ORACLE_SID value and select the Database Only installation option. This creates a new database without overwriting your existing database files and does not reinstall the Oracle binary files.
If you intend to use the same Oracle installation with more than one installation of the Cisco IP Manager servers, you must create a unique Oracle SID and Oracle tablespace for each Cisco IP Manager installation. (This requirement applies to multiple complete installations of the Cisco IP Manager software; it does not apply to multiple users of a single installation or multiple client installations that use the same servers.)
This file should already exist in the /dbs subdirectory of your Oracle installation. (The filename contains your database's SID in place of ORACLE_SID. For example, if you named your database CIPM, this file is named initCIPM.ora.)
If you are installing the Cisco IP Manager software on multiple machines, each remote server host machine must have a tnsnames.ora file in a directory called /var/opt/oracle or in the $ORACLE_HOME/network/admin directory. You must also install the Oracle component Net8 8.0.5.0.0 on each of these remote hosts.
The ORACLE_HOME environment variable on the remote host should be set to the directory in which you install this package.
For a database created with the ORACLE_SID of CIPM, located on a machine called host in the DNS domain cisco.com, the contents of the edited file should look like the following:
CIPM = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (Host = host.cisco.com) (Port = 1521) ) ) (CONNECT_DATA = (SID = CIPM) (GLOBAL_NAME = CIPM) ) )
You can create your own file, or edit the sample tnsnames.ora file from the following subdirectory of your Cisco IP Manager installation:
utility/sample_db_files
The first line is the service name, and (aside from any domain appendages, if any) it must match the GLOBAL_NAME entry. You should change the Host entry to be equal to the host name of the database server, and both the SID and GLOBAL_NAME entries to the value of your ORACLE_SID. Oracle uses the GLOBAL_NAME entry to resolve alternative names for the same database. The entry is required, even though the Cisco IP Manager software does not make use of this feature.
Protocol and Port are required and must be set to the values shown. Proper indentation is important. Keyword/value pairs should be indented beneath their parent keyword; if an entry must be wrapped, its second line must be indented by at least one space or it is misread as a new parameter.
If any of the Cisco IP Manager servers that communicate with the database are located on a machine other than the one on which Oracle is installed, a listener.ora file must be located on the Oracle host, in either a directory called /var/opt/oracle or in the $ORACLE_HOME/network/admin directory. (All of the Cisco IP Manager servers except TGServer and SGServer need to communicate with the database.) For more on the listener file, refer to "Verifying and Launching Oracle."
The listener.ora file provides the Oracle listener process with information about your Oracle installation. Edit the sample file located in the following subdirectory of your Cisco IP Manager installation:
utility/sample_db_files
For a database called CIPM installed on a machine called host, which is located in the DNS domain cisco.com, the contents of the listener.ora file would look like the following:
LISTENER =(ADDRESS_LIST =(ADDRESS =(PROTOCOL = IPC)(KEY = CIPM) ) (ADDRESS = (PROTOCOL = TCP) (Host = host.cisco.com)(Port = 1521)))STARTUP_WAIT_TIME_LISTENER=0CONNECT_TIMEOUT_LISTENER=10TRACE_LEVEL_LISTENER=OFFSID_LIST_LISTENER =(SID_LIST =(SID_DESC =(SID_NAME = CIPM)(ORACLE_HOME = /oracle/8.0.5)))
The KEY value should be set to your ORACLE_SID. The Host value should be set to the host name of the database server. The SID_NAME is your ORACLE_SID again. The ORACLE_HOME value should be the full path to your Oracle installation.
Protocol and Port values are required and must be listed as shown. Indentation should be the same as described for the tnsnames.ora file. This file is case sensitive. Enter data exactly as shown.
If your Oracle database was installed prior to your Cisco IP Manager installation, you can append this file to the listener.ora file that already exists. If you installed Oracle specifically for use with Cisco IP Manager software and are not already using the listener process, you can replace the existing listener.ora file with your edited version.
The oratab file should be located in the /var/opt/oracle directory on the machine on which the database is installed. It is used by Oracle's dbstart utility to identify your database.
The oratab file consists of a single line:
database_name:location_of_your_Oracle_executables:Y
If your Oracle home directory is /oracle/8.0.5 and your database SID is CIPM, the oratab entry would be as follows:
CIPM:/oracle/8.0.5:Y
A sample oratab file is located in the following subdirectory of your Cisco IP Manager installation:
utility/sample_db_files
To make this happen automatically following a reboot (after a power interruption, for example), execute the dbstart utility from a script in the /etc/init.d directory on the Oracle host machine. For more information, see the section "Restarting after a Reboot" elsewhere in this chapter.
Your Oracle database must be open before you can install or use the Cisco IP Manager software.
First, verify the Oracle processes, as described in the following. If the processes are running, you can skip the succeeding section. If they are not, perform the procedures described under "Launching Oracle and Opening Your Database."
Log in to the Oracle host machine and enter the following on the command line to see if the Oracle processes are running:
ps -ef | grep ora_
If there is no output displayed from the ps command, Oracle is not running.
If Oracle is running, you should see something similar to the following:
oracle 328 1 0 14:25:18 0:00 ora_pmon_CIPM oracle 328 1 0 14:25:18 0:00 ora_dbwr_CIPM oracle 328 1 0 14:25:18 0:00 ora_lgwr_CIPM oracle 328 1 0 14:25:18 0:00 ora_ckpt_CIPM oracle 328 1 0 14:25:18 0:00 ora_smon_CIPM oracle 328 1 0 14:25:18 0:00 ora_reco_CIPM oracle 328 1 0 14:25:18 0:00 ora_wmon_CIPM
These are the Oracle processes currently running (your output may not match this list exactly, depending on which Oracle components are installed).
If any Cisco IP Manager servers are installed on a remote host, you must have the Oracle Net8 8.0.5.0.0 listener process running on the Oracle host. Enter the following on the Oracle host's command line to see if the listener process is running:
ps -ef | grep tnslsnr
If there is no output on the screen, the listener process is not running.
If the listener process is running, you should see something similar to the following:
oracle 354 1 0 14:27:13 ? 0:00 /oracle/8.0.5/bin/tnslsnrLISTENER -inherit
Your Oracle database must be open before you can install or use the Cisco IP Manager software.
If Oracle is not currently running, you need to use the startup utilities located in the /bin subdirectory of your Oracle installation.
To open your database, you must be logged in to the Oracle host workstation under the Oracle administrator (DBA) user ID; you then locate your $ORACLE_HOME/bin subdirectory.
On the command line, enter the following:
dbstart
The dbstart script starts the database identified in the oratab file. If the database starts successfully, you should see several lines of output, including the following:
SVRMGR> Connected to an idle instance. SVRMGR> ORACLE instance started.
...and ending with the following:
Server Manager Complete. Database "CIPM" warm started.
If the Net8 8.0.5.0.0 listener process is not running, you need to start that process as well. On the command line, enter the following
lsnrctl start
You should see several lines of output as the process is invoked, then you should see output similar to the following:
Services Summary... CIPM has 1 Service handler(s) The command completed successfully
To configure your database to work with the Cisco IP Manager software, you need to create a tablespace and configure several files.
You must be logged in to the Oracle host using the user ID (such as oracle) created during the Oracle installation procedure.
To create the tablespace, Oracle must be running and your database must be open.
Log in to the Oracle host using the oracle user ID. Identify (or create) the directory where your Cisco IP Manager data should be stored, and grant write permission to the oracle user ID. Be sure your ORACLE_SID and ORACLE_HOME environment variables are set correctly, then launch the Oracle utility svrmgrl, which is located in the $ORACLE_HOME/bin directory.
At the SVRMGR prompt, enter the following on the command line:
connect internal; CREATE TABLESPACE CIPM_DAT DATAFILE '/your_data_directory/CIPM_DAT_01.dbf' size 200M autoextend on next 50M maxsize unlimited;
The data directory you specify must already exist. The TABLESPACE and DATAFILE names are arbitrary. You can use any names that help you keep track of what files are associated with what database. The only requirement is that the name given to the tablespace at the time of its creation (CIPM_DAT in the example) be the same as the default tablespace listed when you create the ipmgr user account.
The autoextend option allows ORACLE to automatically extend your data file. The maximum size of the data file will be limited only by the available space on the file's disk.
CREATE USER ipmgr IDENTIFIED BY password DEFAULT TABLESPACE CIPM_DAT; GRANT CONNECT TO ipmgr; GRANT RESOURCE TO ipmgr;
You should use this user and password when entering Oracle information in the script ipmgr.configure (as described in the section "User IDs" elsewhere in this chapter).
When you have configured your database and listener file, enter the following (for the Oracle user ipmgr and for the database named CIPM) on the command line:
svrmgrlconnect ipmgr/ipmgr@CIPM
The two instances of ipmgr are the database username and database password. A slash with no spaces separates the database user name and password, and there are no spaces around the @ symbol.
If your system is set up properly (and your Oracle database is running), you should see a message advising you that you are connected to Oracle. Enter quit on the command line to exit the database.
File read/write/execute permissions are inherited from the login of the person who installs the software. You, or your system administrator, should create an ipmgr user ID on each machine that hosts a Cisco IP Manager server. This user ID should be used both for installing the software and for launching any of the servers.
The default behavior is to allow the GUI application to be run by any person able to log into a workstation on which the GUI has been installed, regardless of UNIX-level permissions on the server machines.
Before installing the Cisco IP Manager software, you should be sure your Oracle database is set up and operational, as described in the section "Setting Up Your Oracle Files" elsewhere in this chapter. If you are still logged in to your UNIX workstation with the oracle user ID, log off and log back on using your ipmgr user ID.
The installation script installs those servers that you specify; you need to run the installation separately for each machine. You can install server packages in various combinations and on multiple machines as needed, with the caveats noted in "Installing on Multiple Machines."
You can distribute your Cisco IP Manager software on multiple machines as long as you observe the following restrictions.
The NS, ES, and ADMServer packages should be installed on only one machine each (may be the same machine, or different machines for each).
The NEMServer, SGServer, and TGServer packages can be installed on multiple machines. However, each NEMServer should use only the TGServer and SGServer processes running on the same machine as the NEMServer.
If the servers are distributed among multiple machines, run the ipmgr.configure script on each machine and specify the host for the Name Server and the Event Server. The script puts these names into the file install_dir/OrbixMT/2.3c03-01/cfg/Orbix.hosts.
If you install the NEMServer on a machine other than the one on which Oracle is installed, you must also install the Oracle Net8 8.0.5.0.0 package. When you run the script ipmgr.configure, specify the local Oracle installation directory.
TGServer.Properties under the tgs directory. You can then copy this file to override the version of TGServer.Properties installed during the upgrade or installation. Do this to preserve the TGServer's properties within Cisco IP Manager during the new version upgrade. You should also manually back up the file sgs.properties under the sgs/bin directory. You can then copy this file to override the version of sgs.properties installed during the upgrade or installation. Do this to preserve the SGServer's properties within Cisco IP Manager during the new version upgrade.
To install the Cisco IP Manager software, run the installation script found on the installation CD. The installation script does not run if you are logged in as root; otherwise, file permissions would be set incorrectly. Log in as the ipmgr user described in the section "User IDs" elsewhere in this chapter. The installation CD contains the installation script, a number of compressed files (*.Z), plus a number of ancillary files. Execute the ipmgr.install script as follows:
cd /cdrom/cdrom0./ipmgr.installsource_directory install_dir[package1] [package2] ... [packagen] | [all]
...where source_directory is the directory in which you are running the ipmgr.install script (usually this would be ./), install_dir is the full path to the location of your Cisco IP Manager installation, and package1..n is either a list of the packages you wish to install, or the string all. You would use all if you wish to install the entire product on one machine.
The package parameters can be given in any order. They correspond to the packages shown in Table 3-1 (presented in order of appearance), and described in detail in "Advanced Usage."
all, you must enter all package names in upper case only.
| Package | Description | Components |
|---|---|---|
Usual package for a distributed installation | ADM CTM ES LOG NS VCM | |
Name Event servers | OrbixWeb OrbixMT OrbixName jre OrbixNameclasses | |
GUI client | GUI OrbixMT OrbixWeb jre OrbixESclasses OrbixNameclasses swing vcafe | |
NEMServer | NEM OrbixMT | |
TGServer | TGS OrbixMT expect | |
SGServer | SGS jre OrbixWeb OrbixMT OrbixNameclasses |
For example, to install all packages into the directory ipmgr, enter the following on the command line:
./ipmgr.install ./ /ipmgr all
If you do not specify any parameters, the script prompts for them at the appropriate time.
Once invoked, the installer script prompts for certain information, as shown in the following list.
./), the installer requests this information. If you did specify this directory, the script prompts for confirmation; you can accept the value assumed by the script by pressing Return.
all. For considerations when installing a distributed system, see "Installing on Multiple Machines." If you did specify such a list, the script prompts for confirmation; you can accept the values assumed by the script by pressing Return.
ipmgr.configure). You can run this utility at a point in the future if your configuration changes (such as new server locations). The script is located in install_dir/scripts.
(a) Detailed
(b) Administrative
(c) Nonadministrative
| Option | Service |
|---|---|
SNMP options | SGServer |
Archive Manager options | VCMServer (Archive Manager) |
User Manager options | User Manager |
Permission Manager options | Permission Manager |
Log Viewer options | LOGServer |
all choice), the installer prompts you to enter the root password.
The installation concludes with instructions on how to add the Cisco IP Manager directory to your search path:
(a) Close the terminal window from which you performed the installation, and open a terminal, logging in as the same user that performed the installation.
(b) Change directory to install_dir/scripts.
(c) Source the file ipmgr.csh.
ipmgr.csh.
If you have installed the NEMServer on a machine other than the one on which Oracle is installed, you must also install the Oracle Net8 8.0.5.0.0 package. When you run the script ipmgr.configure, specify the local Oracle installation directory.
GUI client workstations do not need to be configured to work with Oracle, nor do they need to be configured for TFTP. However, you must run the ipmgr.configure script as described in the section "Installation and Configuration."
Whenever you run ipmgr.configure, you must close the current terminal, open a new one, and source ipmgr.csh first. The ipmgr.csh script is located in install_dir/scripts, but you can run it from anywhere, as long as you specify the full path name. Once you have sourced this file, you can execute Cisco IP Manager utilities and scripts from any directory, and you need not specify the path.
The Cisco IP Manager software is designed to use the Trivial File Transfer Protocol (TFTP) to upload and download network element data. Before you can use this protocol, however, you must configure a machine to be a TFTP server.
If possible, each machine on which you install NEMServer should act as its own TFTP server.
If you use a remote TFTP server, the /tftpboot directory must be mounted on the NEMServer host.
Log in as the superuser and edit the file /etc/inetd.conf. Locate the line that enables TFTP:
#tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
Remove the comment character (#) from the beginning of the line. Save your changes and exit the text editor.
ln -s /myTftp /tftpboot
To verify that your workstation is TFTP-enabled, enter the following on the UNIX command line:
ps -ef | grep -v grep | grep inetd
The output displays the process identification number for the inetd configuration:
root 106 1 0 Sep 21 ? 0:00 /usr/sbin/inetd -s
The first column shows the user ID of the user who owns the process (inetd is owned by root). The process ID is the number in the second column. In the example, the process ID is 106.
Issue a kill command with a -1 (the number one) or -HUP argument to force the inetd process to read the newly edited inetd.conf file:
kill -1 106
Verify that TFTP is enabled by entering the following:
netstat -a | grep tftp
Your machine is enabled as a TFTP server if you see the following:
*.tftp Idle
If there is no output from the netstat command, TFTP is not enabled. Check the /etc/inetd.conf file for errors and repeat the previous instructions. For more information about TFTP or the kill command, see the UNIX man pages for tftp, tftpd, and kill.
While logged in as the superuser, create the /tftpboot directory if it does not already exist, by entering the following on the command line:
mkdir /tftpboot
Modify the permissions for this directory to give all users read, write, and execute permissions, by entering the following command:
chmod 777 /tftpboot
If you intend to specify a subdirectory of /tftpboot for your Cisco IP Manager TFTP communications from within the GUI (Domain Properties dialog), you should create that at this time, as well, and set its permissions to the same value.
Your system is now enabled to act as a TFTP server.
If you install the DNEM package (NEMServer) on multiple machines, you must install Oracle Net8 8.0.5.0.0 on each and set up the Oracle listener process on the Oracle host to recognize each of the remote NEMServer hosts. When you run the ipmgr.configure utility during installation, specify the location of the Net8 8.0.5.0.0 files as the Oracle home variable on each remote host.
The SGServer must be installed on the remote host where the remote NEMServer and TGServer are installed. The SGServer is optional only on the host where the CENTER-LITE package is installed; it is mandatory on remote hosts.
Figure 1-1 shows a typical distributed installation.
The Cisco IP Manager software consists of several independent executable files (servers) installed onto one or more server machines, and an executable GUI program that provides the user interface on one or more client machines.
Before launching any of the servers, you must source the file ipmgr.csh, which is located in the scripts directory. You can do this manually, or you can add the following line to the .cshrc or .login file in the home directory of your ipmgr user ID:
source /install_dir/scripts/ipmgr.csh
...where install_dir is the full path to the location of your Cisco IP Manager installation. (Before you can source the ipmgr.csh file, you must have already run the ipmgr.configure utility.)
While you do not have to source the file ipmgr.csh on a workstation running only the Cisco IP Manager GUI application, you should source the file so that you can restart the GUI from anywhere (because sourcing the file sets the path to include /install_dir/scripts).
Before you can use the Cisco IP Manager software, you need to first register each of the server applications you intend to use with the Orbix Implementation Repository, and then launch them. Two utilities for doing these tasks---ipmgr.putit and ipmgr.launch---are located in the scripts subdirectory beneath your Cisco IP Manager installation directory.
Do not use the all parameter unless all servers are present on the same machine.
If certain Oracle files are writable, the NEMServer is unable to communicate with your network's devices. The ipmgr.launch script checks the status of these files. If there is a conflict, the script displays an error message and halts.
The ipmgr.putit script invokes the Orbix putit command to register the servers with the Orbix Implementation Repository.
Change to the directory scripts beneath the root installation directory and execute the utility ipmgr.putit for the server you plan to launch. Usage is as follows:
./ipmgr.putit server_name
...where server_name is one of the following (listed in the order in which they should be started):
ES NS LOGServer NEMServer SGServer TGServer VCMServer ADMServer CTMServer all // use only if all servers are on one machine
ipmgr.putit script at least once before running the ipmgr.launch script.
After using the ipmgr.putit script, you can launch one or more of the server applications by executing the launch utility in the scripts subdirectory, as follows:
./ipmgr.launch server_name
...where server_name is one of the following (listed in the order in which they should be started):
ES NS LOGServer NEMServer SGServer TGServer VCMServer ADMServer CTMServer all // use only if all servers are on one machine
To get a trace while running the ipmgr.launch utility, use the following syntax:
./ipmgr.launch -T trace_dir all
...where trace_dir is the directory into which to store the trace.
Other utility scripts are provided. The following are in the scripts subdirectory:
ipmgr.catit server_name
ipmgr.launch). Enter the following on the command line:
ipmgr.killit all
ipmgr.killit orbixd
ipmgr.launch, the ipmgr.killit command may miss them. After executing the ipmgr.killit utility, you should check to be sure all Cisco IP Manager processes were in fact halted before restarting any servers. To do so, enter the following on the command line:ps -ef | grep $IPMGR_SRVRS_HOME
ipmgr.killit command does not halt those processes. You can then kill any Orbix processes as described above.ipmgr.killit, issue the UNIX kill command directly:kill -9 PIDs
ipmgr.lsit
ipmgr.psit
ipmgr.rmit all
The following are in the utility subdirectory:
log_users trace option on and off. (For more information about this option, see the section "TGServer" in the appendix "Advanced Usage.")
########################### banner text ###########################
# and > are part of a Cisco IOS prompt. The Cisco IP Manager servers must determine when these reserved characters are being used as a banner graphic and when they designate a prompt. The test involves introducing a delay to all device operations. If you are downloading to a large number of devices, the aggregate delay can be significant. You should not use this check if you know your configurations do not contain banners that use the characters # and >. Several Orbix-related utilities from Iona Technologies PLC are available to you. (Launch them from any directory. Their location---install_dir/OrbixMT/2.3c03-01/bin---was included in your path when you sourced ipmgr.csh.) The ones used with the Cisco IP Manager servers are:
Marker Launch command shows the command used to launch the server, including the full path to the executable and the list of launch arguments and their values. (If you change a server's launch arguments---by running the ipmgr.configure script and sourcing ipmgr.csh again, for example---you must use the script ipmgr.putit to register the changes before they will show up in the catit output, and you must use the script ipmgr.launch again before the changes are actually implemented. In the preceding scenario, it is safest to open a new terminal session, and source ipmgr.csh there. The changes you make will take effect in this new terminal session.)
ipmgr.killit command instead, which invokes a UNIX kill -9 command.
ipmgr.putit invokes this utility for one or all of the specified Cisco IP Manager servers.
ipmgr.rmit invokes this utility for each Cisco IP Manager server currently running.
Environment variables are referenced in several scripts, and there are inter-script dependencies.You should not edit these scripts. To change your environment, rerun ipmgr.configure.
If you are executing the ipmgr.configure script again, existing server environment files are backed up. The allcommon.env, allserver.env, gui.env, and orbix.env files, all found in the envs directory under your CIPM installation directory, are backed up as filename.env.org (and any previous filename.env.org file is overwritten). New Orbix.hosts and Orbix.cfg files are also generated. The Orbix.hosts file is backed up as Orbix.hosts.bak (and any previous Orbix.hosts.bak file is overwritten). The Orbix.cfg file is backed up as Orbix.hosts.n (where n is an incremented number, starting with 0; no files are overwritten).
You must set a value for every variable each time you run ipmgr.configure. The default is to use the old value; if you enter nothing, the variable is set to that old value.
After executing ipmgr.configure while servers are running, you should run the utilities ipmgr.killit and ipmgr.rmit to unregister the servers, source the file ipmgr.csh again, and then reinvoke both ipmgr.putit and ipmgr.launch as described elsewhere in this chapter. These files are all located in the scripts subdirectory of your Cisco IP Manager installation.
For more about server launch flags, see "Advanced Usage."
If the system on which your servers are installed reboots, you must do the following:
ipmgr.csh again
ipmgr.putit and ipmgr.launch utilities as described in the section "Starting the Cisco IP Manager Software" elsewhere in this chapter.
If you choose to create a startup script to relaunch the Cisco IP Manager servers automatically upon reboot, copy your script into the directory /etc/init.d (you must be the root user). Link the script to aliases with the prefaces S99 and K99 in the /etc/rc2.d directory (the "K" link provides for an orderly database stop in the event of a manual reboot).
Here is the text of a sample Bourne shell script that restarts Oracle and the Cisco IP Manager servers when all are installed on a single host:
#!/bin/sh # # startup and shutdown script for IP Manager server, oracle & orbixd # Replace $ORACLE_HOME, $ORACLE_SID, and IPMGR_HOME with # your actual value # Replace $IPMGR_USER with the UNIX user id who can start the IP Manager # servers # case "$1" in 'start') echo "Cisco IP Manager starting..." # # restart Oracle # ORACLE_HOME=$ORACLE_HOME; export ORACLE_HOME ORACLE_SID=$ORACLE_SID; export ORACLE_SID su oracle -c "$ORACLE_HOME/bin/dbstart" su oracle -c "$ORACLE_HOME/bin/lsnrctl start" # # restart Cisco IP Manager servers # su $IPMGR_USER -c "source $IPMGR_HOME/scripts/ipmgr.csh;$IPMGR_HOME/scripts/ipmgr.launch all" ;; 'stop') echo "Cisco IP Manager stopping..." # # stop Cisco IP Manager servers # su $IPMGR_USER -c "source $IPMGR_HOME/scripts/ipmgr.csh;$IPMGR_HOME/scripts/ipmgr.killit all" # # stop Oracle # ORACLE_HOME=$ORACLE_HOME; export ORACLE_HOME ORACLE_SID=$ORACLE_SID; export ORACLE_SID su oracle -c "$ORACLE_HOME/bin/lsnrctl stop" su oracle -c "$ORACLE_HOME/bin/dbshut" ;; *) ;; esac
Save the script as ipm_start, then copy the script into the /etc/init.d directory:
cp ipm_start /etc/init.d chmod +x /etc/init.d/ipm_start
Change directories to the /etc/init.d directory and create links to the script, as follows:
cd /etc/init.d ln ipm_start /etc/rc2.d/S99ipm_start ln ipm_start /etc/rc2.d/K99ipm_start
For more information about executing scripts on reboot, see the UNIX init.d man page.
Reinstallation overwrites any old installations.
Cisco IP Manager comes preconfigured with certain system timeouts. You can change some of these.
Whenever the Cisco-supplied GUI application contacts a server, the GUI application will stop waiting for a response after 10 minutes (600 seconds). The length of the wait can be changed by entering a new TIMEOUT value in the PSSetup.properties file located in the java/cls/frontend subdirectory of your IP Manager installation. The value must be in the range of 60 to 1200 seconds, and must be greater than the telnet timeout value of any TGServer in the system. (TGServers have a default timeout value of 120 seconds and a minimum of 50.) The GUI application does not check to see if its timeout is larger than any TGServer's timeout value. Coordination of these values is the responsibility of the Cisco IP Manager administrator.
If the value is set below the acceptable minimum, it is increased to the minimum value. If set above the acceptable maximum, it is decreased to the maximum.
Table 3-3 presents a step-by-step checklist of all of the things you need to do to install and launch the Cisco IP Manager software.
If you are installing components on a machine on which CIPM components already exist, stop, using the ipmgr.killit script, all servers and the Orbix daemon. Then open a new terminal and start your installation. For information on using the ipmgr.killit script, see "Other Utilities."
| Item | Description | Reference |
|---|---|---|
Install and start Oracle | Your Oracle database must be running before you start the Cisco IP Manager software (though it is not necessary to have the database running during Cisco IP Manager installation). Depending on your specific installation deployment, you may have to edit some or all of the following: | |
Configure Oracle for Cisco IP Manager | Create an | |
Set up TFTP server | The Telnet Gateway Manager server (TGServer) is designed to exchange data with network devices via TFTP. You should configure at least one machine in your network as a TFTP server. | |
Create user ID | Create a user ID, such as | |
Install Cisco IP Manager components | Run the script | |
Set script environment variables | Execute the script | |
Set shell environment variables | Source the file | |
Register and launch the Cisco IP Manager servers | Use the Use the | |
Launch the GUI | Launch |
Posted: Mon Feb 14 14:10:57 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.