|
|
This chapter describes the steps to install and configure Cisco Info Center in a Single System Architecture.
This chapter contains the following sections:
The CD-ROM should mount automatically when running the Solaris Volume daemon (vold) as /cdrom/infocenter. When this daemon is not running, mount the CD-ROM with the following command:
where </dev/dsk/device> is the CD-ROM drive device entry.
When the CD-ROM is mounted, change directory to that location. For example, when you mounted the CD-ROM in the /cdrom/infocenter directory, specify the following command:
To run the install program, specify:
The following text is displayed:
Cisco Info Center Version 1.0 InstallationThis program installs the Cisco Info Center Version 1.0 software for Unix onto your system from the distribution CD.Please enter the path to where the CD-ROM is mounted.[/cdrom/infocenter]Hit Enter to accept the path to the CD-ROM or enter a new path.
Specify the pathname of the mount point of the CD-ROM or press Return to select the default (/cdrom/infocenter).
The following Platform selection menu is displayed:
Cisco Info Center Version 1.0 InstallationPlatform selection:1. Solaris 2.x on SPARCI. Install selected modulesC. Change install directory /opt/OmnibusH. HelpQ. Quit the installOption:
Specify option 1 to select Solaris 2.x on SPARC.
The installation program displays the available platform. To the right is an installation status indicator. When the message SELECTED is displayed, all components for that platform are selected for installation. When PARTIAL is displayed, only some of the components for that platform are selected for installation. By default, no selections are made.
Upon selecting 1 for Solaris 2.x on SPARC from the Platform selection menu (previous screen), the following text is displayed:
Cisco Info Center Version 1.0 Installation1 - Info Admin Desktop2 - Info Gateway3 - Licensing4 - Process Control5 - Info Mediators6 - Info Server7 - Java supportQ - Quit the installS - Select AllU - Unselect AllM - Return to Main MenuH - HelpOption:
Specify option S to select all of the components, then press Return.
When the selections are made, the screen displays the following text:
Cisco Info Center Version 1.0 Installation1 - Info Admin DesktopSELECTED2 - Info GatewaySELECTED3 - LicensingSELECTED4 - Process ControlSELECTED5 - Info MediatorsSELECTED6 - Info ServerSELECTED7 - Java supportSELECTEDS - Select AllU - Unselect AllM - Return to Main MenuH - HelpQ - Quit the installOption:
After the required components are selected, specify option M to return to the Platform selection menu.
The following text is displayed:
Cisco Info Center Version 1.0 InstallationPlatform selection:1. Solaris 2.x on SPARCSELECTEDI. Install selected modulesC. Change install directory/opt/OmnibusH. HelpQ. Quit the installOption:
When you want to change the installation directory, specify option C in the Platform selection menu. Otherwise, go to Section, "Single System - Starting the Installation Process".
When the Change Directory command (C) is specified, the following text is displayed:
Cisco Info Center Version 1.0 InstallationEnter the new installation directory.[/opt/Omnibus]/export/home/infocenter
Specify the new installation directory, when desired. When the new destination directory does not exist, the following text is displayed:
Cisco Info Center Version 1.0 Installation/export/home/infocenter does not exist. Create it [Y]?
Press Return to accept and create the new installation directory or N to repeat the above process.
The following text is displayed:
Cisco Info Center Version 1.0 InstallationPlatform selection:1. Solaris 2.x on SPARCSELECTEDI. Install selected modulesC. Change install directory/export/home/infocenterH. HelpQ. Quit the installOption:
To display online Help, specify option H. To exit the install program, specify option Q.
After the desired directory is set and the required components are selected, specify
option I in the Platform selection menu to start the installation process.
Before the installation process continues, the selected platform and components are displayed for your verification. The following text is displayed:
Cisco Info Center Version 1.0 InstallationYou have selected:Solaris 2.x on SPARC:Info Admin Desktop, Info Gateway, Licensing, Process Control, Info ServerIs this correct [Y]?
Press Return to accept the defaults.
When the destination directory already exists, the following text is displayed:
Cisco Info Center Version 1.0 Installation/opt/Omnibus is not empty.Are you SURE you want to overwrite files in this directory [N]?
When you do not want to overwrite the files in the selected installation directory, specify N or press Return. You are then returned to the Platform selection menu.
Specify Y and press Return to overwrite this directory and continue the installation process.
Installation begins when:
When you confirm the list, the install program checks whether the /opt/Omnibus install directory exists and that enough disk space is available for the installation of the selected components. When the install program is unable to check the disk space, for example, with NFS mounted file systems or similar network mounted file systems, it displays the message: "Unable to determine disk space. Do you want to try and install anyway?". Specify Y to install the required components without checking disk space.
When insufficient disk space exists, an error message is displayed along with the option to return to the Platform selection menu. When enough disk space exists, the installation starts.
The following text is displayed during the installation process as each component is installed:
Cisco Info Center Version 1.0 InstallationStarting installation ...Installing common files ... done.Installing OEM files ... done.Installing Solaris 2.x on SPARC common files ... done.Installing Solaris 2.x on SPARC OEM files ... done.Installing Info Admin Desktop for Solaris 2.x on SPARC ... doneInstalling Info Gateway for Solaris 2.x on SPARC ... doneInstalling Licensing for Solaris 2.x on SPARC ... doneInstalling Process Control for Solaris 2.x on SPARC ... doneInstalling Info Mediator for Solaris 2.x on SPARC ... doneInstalling Info Server for Solaris 2.x on SPARC ... doneInstalling Java Support for Solaris 2.x on SPARC ... doneInstalling Info Server common files ... doneInstalling Info Server OEM files ... doneInstalling Info Admin Desktop common files ... doneInstalling Info Admin Desktop OEM files ... doneInstalling Info Mediators common files ... doneInstalling Info Mediators OEM files ... doneInstalling Info Gateway common files ... doneInstalling Info Gateway OEM files ... doneInstalling Java support common files ... doneInstallation complete
After installation, the following Configuration main menu is displayed.
Cisco Info Center Version 1.0 Configuration Menu1. Configure Info Server2. Configure SV+ Mediators3 Configure Info Admin Desktop4. Configure All5. Help6. QuitSelect one of the above options:
Select option 4 from the Configuration menu.
The script displays the selected option and prompts you for confirmation:
Cisco Info Center Version 1.0 Configuration MenuYou have Selected the following Info Center Components to be configuredInfo Server, Info Admin Desktop, SV+ MediatorsDo you want to continue (y/n)? [y]:
Press Return to continue or N to go back to the previous menu.
When you continue with the configuration process, and when the current installation directory is not /opt/Omnibus, the script automatically links the Cisco Info Center install directory to /opt/Omnibus.
However, when /opt/Omnibus is not the current installation directory and /opt/Omnibus already exists either as a directory, file, or a link on the system, the following error message is displayed:
........ ......*** Info Center Requires Installation in /opt/Omnibus****** /opt/Omnibus already exists, ****** Create a link to /opt/Omnibus from the <install directory> ****** at the end of this configuration script ***
The following text is displayed to configure the Cisco Info Server properties as discussed in next section.
The script configures the Cisco Info Server by prompting you for name of the Cisco Info Server and the port to run on.
........ .........o Server must be alphanumeric beginning ****** With a letter and up to 11 characters long ***Name for the Info Server [INFOSERVER]
Press Return to accept the default name, INFOSERVER or specify any alphanumeric string up to eleven characters, beginning with a letter. The script converts all characters specified in the string to upper case and informs you of the converted Cisco Info Server name. When the Cisco Info Server name is valid, the following text is displayed:
Enter the Port Number for the Info Server [4100]:
Press Return to accept the default port or specify an unused port number.
The script validates the availability of the port and informs you when the specified port number is already in use or is a reserved port. This process may take a few seconds. When the port number is in use or reserved, the following message is displayed:
Checking Port Availability Please Wait...Port Number [4100] is already in use...Checking Port Number 4101Enter the Port Number for the Info Server [4101]
The script automatically increments the port number and checks for port availability. It continues to do so until a free port is available and prompts you to accept this new port number.
Press Return to accept the unused port number.
The following text is displayed to configure the Process Control Agent name, as described in the next section:
*** Name for the Process Agent must be alphanumeric beginning with ****** a letter, must NOT exceed 11 characters and must end with _PA ***Name for the Info Server Process Agent [NCO_PA]
Press Return to accept the default name, NCO_PA or specify any alphanumeric string up to eleven characters, beginning with a letter and ending with _PA. The script validates the Process Control name and prompts you to specify the port number for Process Control.
The following text is displayed:
*** Port Number for the Process Agent must not be ****** the same as the Info Server Port Number [4100] ***Enter the Port Number for the Info Server Process Agent [4200]:
Press Return to accept the default port or specify an unused port number. The script validates the availability of the port number and also ensures the port number specified is not the same as the port number selected for the Cisco Info Server. This process may take a few seconds. When the port number is in use or reserved, the following text is displayed:
Checking Port Availability Please Wait...Port Number [4200] is already in use...Checking Port Number 4200Enter the Port Number for the Info Server Process Agent [4201]
The script automatically increments the port number and checks for port availability. It continues to do so until a free port is available and prompts you to accept this new port number.
Press Return to accept the unused port number. The following text is displayed:
Creating the new Info Server INFOSERVERAdding its entry to omni.dat... doneCreating the new Process Agent NCO_PAAdding its entry to omni.dat... doneRunning nco_igen... doneUpdating ./etc/services . Please wait...Generating the database files... Info Server INFOSERVER created*** Configuring the Cisco Trap Receiver to register with StrataView+ ***IP address of the SV+ machine [<IP Address of local machine>]
The Trapd Mediator registers with the Cisco SV+ Service Agent. The registration process requires the IP address of the Cisco SV+ workstation and the port number for the Trapd Mediator to receive the traps.
Press Return to accept the local IP address or specify the IP address of the Cisco SV+ workstation (that is, the workstation you are currently on).
The following text is displayed:
Port Number to run the Info Center Trap Receiver [4000]:
Press Return to accept the default port or specify an unused port number. The script validates the availability of the port number. This process may take a few seconds. When the port number is in use or reserved, the following message is displayed:
The following text is displayed:
Checking Port Availability Please Wait...Port Number [4000] is already in use...Checking Port Number 4001Enter the Port Number for the Info Center Trap Receiver[4001]
The script automatically increments the port number and checks for port availability. It continues to do so until a free port is available and then prompts you to accept this new port number.
Press Return to accept the unused port number. The script completes the configuration as follows:
Configuring SV+ Mediators...Configuring nnm4 mediator...Configuring trapd mediator...Generating Lookup Files for the SV+ MediatorsGenerating Node to IP Address Lookup File...Lookup file /opt/Omnibus/probes/solaris2/node_ip_addr.lookup generatedGenerating Node to Platform Lookup File...Lookup file $OMNIHOME/probes/solaris2/node_platform.lookup generatedGenerating the NCO_PA config file ... done Configuring Tools... done
When Cisco SV+ is not actually installed on the specified host, error messages are displayed instead of the line that reads: Lookup file....generated.
At the end of the configuration process, the following text is displayed:
This script copies a startup script...Do you wish to continue (y/n)? [y]
Press Return to configure automatic start-up scripts or N to finish configuration.
When automatic startup scripts are selected for configuration, the following text is displayed:
Scripts installed
When the configuration process is successful, the Cisco SV+ Mediators are configured in the configuration topology, as shown in Figure 4-1.
This section describes the installation and configuration of components used to enhance the installed and configured multi or single system, or to install Cisco Info Center and manually configure the components.
Cisco Info Center uses client/server technology, therefore, all of the components can be installed either on one workstation or on separate workstations and platforms, communicating over a TCP/IP network.
Components installed on different workstations use the Cisco Info Center communications protocol to communicate with the Cisco Info Center software. This relationship is configured in the interfaces file.
This section describes how to install the Cisco Info Center system on a Solaris 2.x platform. The following assumptions are made:
When the installer does not have root access (or at least write access to /opt), other users can run the Cisco Info Admin Desktop. (When only the Cisco Info Admin Desktop is being installed, root access is not necessary.)
The installation procedure covers the following steps:
1. Mount the CD-ROM.
2. Start the installation.
3. Select the target directory.
4. Select the components for the system.
5. Set the environment variables.
6. Install licensing.
This section describes how to mount the CD-ROM on a Solaris 2.x platform.
Before you begin, you must have write access to /opt installation directory.
The CD-ROM should mount automatically when running the Solaris Volume daemon (vold) as /cdrom/infocenter. When this daemon is not running, mount the CD-ROM with the following command:
where </dev/dsk/device> is the CD-ROM drive device entry.
When the CD-ROM is mounted, change directory to that location. For example, when the CD-ROM is mounted in the /cdrom/omnibus directory, specify the following command:
To run the install program, specify:
The installation program prompts you for the source directory. Press Return to select the default directory for the current platform. The default directory for Cisco Info Center is /opt/Omnibus.
To install in a different directory, specify another directory name.
When Cisco Info Center is not installed in the default directory, you must set the LD_LIBRARY_PATH environment variable so the dynamic loader can find the required shared library. See Section, "Manual Installation - Shared Libraries", for more information about this environment variable.
The install program now prompts for the required components.
The installation program displays the available platforms. To the right is an installation status indicator. When the message SELECTED is displayed, all components for that platform are selected for installation. When PARTIAL is displayed, only some of the components for that platform are selected for installation. By default, no selections are made.
The Platform selection menu is displayed:
Cisco Info Center Version 1.0 InstallationPlatform selection:1. Solaris 2.x on SPARCI. Install selected modulesC. Change install directory/opt/OmnibusH. HelpQ. Quit the installOption:
Select 1 for Solaris 2.x on SPARC.
Cisco Info Center Version 1.0 Installation1 - Info Admin Desktop2 - Info Gateway3 - Licensing4 - Process Control5 - Info Mediators6 - Info Server7 - Java supportQ - Quit the installS - Select AllU - Unselect AllM - Return to Main MenuH - HelpOption:
When any component on the platform is selected for installation, SELECTED is displayed to the right of the component.
To select a single component, specify the number displayed to the left of the component. You may repeat this process to select the components required for the installation.
When you want to select all components for the platform, specify option S (Select All). When you want to clear all the current selections, specify option U (Unselect All).
When you have selected the required components, specify option M to return to the Platform selection menu.
When you want to change the installation directory, specify option C in the Platform selection menu.
To display online Help, specify option H. To exit the install program, specify option Q.
When you have selected all the required components on all the required platforms, specify option I in the Platform selection menu to start the installation process.
Before the installation process continues, the selected platforms and components are displayed. When you want to change any of the platforms and components, specify N. Specify Y to confirm and the installation continues.
When you confirm the list, the install program checks that there is enough disk space available for the installation of the selected components. When the install program is unable to check the disk space, for example, with NFS mounted file systems or similar, it displays the message: "Unable to determine disk space. Do you want to try and install anyway?". Specify Y to install the required components without checking disk space.
When there is insufficient disk space, an error message is displayed along with the option to return to the Platform selection menu. When there is enough disk space, the installation starts.
At the end of the installation, depending upon the components picked in the component selection process, a Configuration menu is displayed.
Select option Q to quit the configuration process and proceed with the manual configuration as described below.
From this point on in the installation, the OMNIHOME environment variable must be set. This variable should point to the directory (/opt/Omnibus) in which you installed Cisco Info Center.
For C-shell users, specify the following command in the $HOME/.login file for each user:
For Korn and Bourne shell users, specify the following command in the $HOME/.profile file for each user:
The PATH environment variable must be defined as follows:
The Cisco Info Center directory layout uses shared libraries, which contain rationalized common executables providing smaller executables and a smaller total distribution.
The run-time dynamic loader module automatically looks for shared libraries within the default /lib and /usr/lib directories. The libraries are installed in the default location specific to the platform. For example, the installation default location of the shared libraries for Solaris 2 is /opt/Omnibus/platform/solaris2/lib. When Cisco Info Center is started, the run-time dynamic loader searches this directory for the shared libraries, due to the default path being encoded within the header of the program.
When Cisco Info Center is not installed in the default directory, you must set a system environment variable in order for the dynamic loader to find the required shared library.
The environment variable is platform specific:
For ksh and sh users, specify the following command:
You must set the NCO_ELMHOST environment variable to the host where the license daemon is located. For example, when the licenses are installed on the host muppet, using csh, specify:
When you are using sh or ksh, specify the following command:
This command ensures that components search for licenses on the host muppet before issuing a network broadcast. To search for licenses on multiple sources, prefix the host name with a @. For example, the following command (csh) ensures that components search for licenses on muppet, then on boomerang, before doing a network broadcast:
When you are using sh or ksh, the command is as follows:
When you do not set the NCO_ELMHOST environment variable, components search for licenses by network broadcast only.
The Cisco Info Center system is licensed on a component basis. Before you can bring up the system, you must supply license keys, on the NCO_ELMHOST workstation. These licenses are installed in the Cisco Info Center license manager. To start the license manager, specify:
Accept all the default options and you are then supplied with a server code, which is generated from unique host information. Send the server code to support@MicroMuse.com (800-637-2665) to obtain your license keys.
When you receive your license keys, run the license manager again and specify the keys when prompted to do so, or press Return to skip a key. The nco_license command automatically starts the license daemon. To run it manually, specify the command:
This section describes how to configure the Cisco Info Center system.
The configuration procedure covers the following steps:
1. Create the interfaces file for Cisco Info Center communications.
2. Run a Cisco Info Server using the nco_objserv command. For details, see Chapter 1, "Cisco Info Server" in the Cisco Info Center Administrator Reference guide.
3. Configure the system to run under process control. For details, see Chapter 2, "Process Control" in the Cisco Info Center Administrator Reference guide.
4. Define users and groups (for Cisco Info Center, not UNIX).
The interfaces file contains information about:
When Cisco Info Center components are started, they search for the $OMNIHOME/etc/interfaces.solaris2 file.
You can also use the nco_igen command's -java parameter to generate the interfaces file used specifically for Java support.
Without an appropriate interfaces file, the software looks for a file named $OMNIHOME/etc/interfaces and uses that as the interfaces file.
When that file does not exist, the programs are unable to contact any Cisco Info Servers and fail to run.
.
To create the interfaces file, use the Server Editor window, shown in Figure 4-2. To open the Server Editor window, specify:
The Server Editor window may display an empty list or display the list of Cisco Info Servers, Info Gateways, or Process Control that may have been configured, along with the host name and the TCP port to which they are allocated. The list of servers is stored in the $OMNIHOME/etc/omni.dat file and any changes you make in the Server Editor window are saved in this file.
Note, although it is possible to edit the $OMNIHOME/etc/omni.dat file directly, it is recommended you use the Server Editor window to edit the list of servers. However, there may be occasions when you want to edit the connections data file. For more information about how to edit this file, see Section, "Editing the Connections Data File", in
Appendix B, in the Cisco Info Center Administrator Reference guide.
To change the host name:
1. Click on the server name to select it.
2. Specify the name of the host machine in the Host field.
3. Click on the Update button. The server is displayed in the list of servers.
4. Click on the Apply button. The interfaces file for the local platform is generated. A separate interfaces file for Java support is also generated automatically.
Cisco Info Center allows you to specify back up hosts for each server defined. This ensures that when a server, for example, NCOMS, fails on the first host, Cisco Info Center attempts to connect to NCOMS on the backup host.
For example, to specify a backup host for NCOMS:
1. Click on the CISCO server in the main list.
2. Specify a different host name in the Host field.
3. Click on the Add button.
In Figure 4-3, the NCOMS server shows two backup hosts: muppet and darkstar.

To change the priority of the server in the list:
1. Click on the server name to select it.
2. Click on either the Raise or Lower buttons to move the server up or down the list, respectively.
To add a new server to the interfaces file:
1. Specify the name of the server into the Name field.
2. Specify the name of the host machine in the Host field.
3. Specify the port number into the Port field.
4. Click on the Add button to add the new server.
5. Click on the Apply button to apply the changes.
To change a primary server:
1. Click on the server name to select it, or specify the server name in the Name field.
2. Edit the Name, Host, or Port fields, as required.
3. Click on the Update button.
4. Click on the Apply button to apply the changes.
To delete a primary server:
1. Click on the server name to select it.
2. Click on the Remove button.
3. Click on the Apply button to apply the changes.
To test the server, click the Test button. A window is displayed providing the results of the test command.
By default, the Server Editor window generates the interfaces file for use on Solaris 2.
You can then copy this interfaces file to the $OMNIHOME/etc directory on each of the participating Cisco Info Center machines.
This section describes how to install the startup scripts and configure the login procedure.
The Multisystem and Single System installation processes automatically add the automatic start-up procedures to the /etc/init.d/nco file.
To manually start the installed Cisco Info Center components, execute the following command:
To manually shut down the running Cisco Info Center components, execute the following command:
Each Cisco Info Center user must have the OMNIHOME environment variable set and the $OMNIHOME/bin directory added to the PATH environment variable. For more information, see Section, "Manual Installation - Defining Environment Variables".
When you start the Event List, the default Event List configuration is displayed. The Event List displays one Monitor box.
You can, however, create a new Event List configuration and save it as default.elc. You should then copy this file to the /opt/Omnibus/desktop directory. (You must be logged in as root to write to this directory.)
The Login window is displayed when you start the Desktop tools. To modify the Server button on the Login window, use a skip filter file. This filter is an external file that comprises regular expression statements to define the servers that will not appear in the Login window.
To use this skip file, create a file called:
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Mar 18 11:19:05 PST 1999
Copyright 1989-1999©Cisco Systems Inc.