HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

13.3 INSTALLING THE MANAGEMENT SERVER

The time it takes to install the OpenView software onto the management server will vary based upon your familiarity with the system hardware, network and operating system environments. Your experience with prior versions of the application will also prove beneficial with the installation of any new versions of the products. So, whether you are just starting or have the experience of prior installations, the first steps are listed here for reference:

http://ovweb.external.hp.com/lpe/doc_serv/.
• Read the release notes.

HP-UX operating system examples are used throughout this part of the book. Any significant installation differences for the Solaris are indicated when appropriate.

13.3.1 Hardware and Software Prerequisites

The hardware and software prerequisite verification is the first step in the installation process. Taking the time to perform this important task ensures that your installation completes in a timely manner and without error. One method to verify the HP server configuration is with the command

/opt/ignite/bin/print_manifest ; this produces a report that includes information in the following categories:

• System Information
  System type and build data

• System Hardware
  System model, memory, processors, OS, LAN, SWID, and Language

• Storage devices
  HW Path and Interface Name

• I/O Interfaces
  Class, HW Path, Driver, and Description

• Installed Software
  Product Name, Revision, and Description

• Logical Volume Manager (

  LVM ) File System Configuration

• JFS File System (JFS or VXFS) Configuration

• Disk layout
  LVM Disk, Device file, HW Address, size, and volume group

• File System layout
  LVM device file, mount point, size, and file system type

• Swap configuration
  Type, size, priority, and device/location

• Kernel Configuration
  Drivers and Parameters

• System Information
  Hostname, IP Address, Subnet mask, Gateway IP, and time zone

The

/opt/ignite/bin/print_manifest command is only available if Ignite/UX client or server is installed. Installing OVO uses HP Distributor and runs a pre-installation check for kernel parameters, disk space, hostname, and so on during the installation. The output of the check can be read form the software distributor logfile.

Produce a similar report on a SUN Solaris server with the commands

prtconf and

pkginfo . Refer to the man pages for syntax details and optional command line parameters.

The specification and final configuration for the disk, memory, and swap resources depends on a number of factors, including:

1. How many user sessions will operate in parallel?

2. How many operators will use Motif GUIs?

3. How many operators will use Java GUIs?

4. How many active messages?

5. How many acknowledged messages?

6. How large is the IP network?

The disk, memory and swap minimum requirements are summarized in Table 13-2. The information in the table is based on approximately 500 nodes, 3,000 active messages, and 1,000 objects in the Service Navigator tree. The required parameters may vary with different OV software versions. The best practice is to review the most current installation guide.

^[*] Although 700 MB is specified, it is recommended that you make available 1.5 GB.

Table 13-3 is a listing of the recommended kernel parameters.

13.3.2 Prerequisite Patches

Verify that you have installed all prerequisite patches. The required patches are listed within the installation materials. Check or download OpenView patches from http://support.openview.hp.com/patches/patch_index.jsp. Vendor updates on the latest patches are available via email if you sign up for the email notification service.

13.3.3 Installing Oracle and OVO Software

The Oracle for OpenView software and the OVO software products are delivered on two different CD sets. Oracle must be installed prior to running the OVO install command,

ovoinstall , which configures the database for use. The Oracle installation procedure is documented in the OVO Installation Guide. A standard version of Oracle is also compatible for use with OVO. After Oracle is installed, you can begin the OVO software installation. The script

ovoinstall (new with OVO 8 ) will initialize a terminal window and begin the installation process with a series of prompts that allow the user to verify the prerequisite software patches, configuration parameters, and default settings, such as directory paths and environment variables. The installation default parameters are found in the file ovoinstall.defaults. An example of the file is listed here:

#cat ovoinstall.defaults
# This file is parsed by ovoinstall. Values may be changed in this 
section
# Note: English text only.
BBCCLIENTS_PATH=/ovo_8/CD2/OV_DEPOT/HPOvOhttpsClients.depot
BBCCLIENT_PRODUCTS="OVO-CLT.OVO-UX11-CLT OVO-CLT.OVO-SOL
-CLT OVO-CLT.OVO-LIN-CLT OVO-CLT

.OVO-DLIN-CLT"RPCCLIENTS_PATH=/ovo_8/CD2/OV_DEPOT/
HPOvOrpcClients.depot RPCCLIENT_PRODUCTS="OVOPC-CLT.OVOPC-
NT-CLT OVOPC-CLT.OVOPC-SOL-CLT OVOPC-CLT.OVOPC-UX11-CLT"
CDROM_DEV=/dev/dsk/c0t0d0
CDROM_INSTALL=false
CDROM_MNT_PT=/SD_CDROM
DB_CHARACTER_SET=
DEFAULT_M10I_PATH=/ovo_8/CD1/OV_DEPOT/HPOvComponents.depot
DEFAULT_SERVER_PATH=/ovo_8/CD2/OV_DEPOT/HPOvOServer.depot
FORCED=false
LANGUAGE=C
M10I_PRODUCTS="HPOvLcore.HPOVXPL HPOvLcore.HPOVSECCO
HPOvLcore.HPOVBBC HPOvLcore.HPOVSECCC HPOvLcore.HPOVCTRL 
HPOvLcore.HPOVDEPL HPOvLcore.HPOVCONF HPOvLcore.
HPOVSECCC HPOvSext" M10I_PRODUCTS_INSTFLAGS="-x enforce_
dependencies=false -x autoselect_dependencies=false"
MINIMAL=false
ORACLE_HOME=/opt/oracle/product/9.2.0
ORACLE_DATA_DIR=/ora_db
PACKAGES_TO_ADD=
POLICY_DATA_TYPE=
REINSTALL=false
SERVER_PRODUCTS="OVOEnglish OVOSvcNavEng"
TAR_files=
this listing is truncated
HP-UXHP-UX
TAR_FILE_PATH=/ovo_8/CD2/OVOServer_patches
VERBOSE=true
TIMEOUT=5
INSTALL_DEVKIT=false
# NNM installation script options.
NNMINSTALL_SCRIPT_NAME=install
NNMDEPOT_PATH_CD1=/ovo_8/disk1
NNMDEPOT_PATH_CD2=/ovo_8/disk2
NNM_DISC_NETWORK=n
NNM_SHOW_UI=n
NNM_SNMPCOMMUNITY=s
NNM_BROWSER_PATH=s
NNM_VIEW_RELEASE_NOTES=n
NNM_INST_JAPANESE=n
# Values below here will not be read by ovoinstall when running in
 silent mode 
ORACLE_PW_OPC_OP=opc_op
ORACLE_PW_OPC_REPORT=opc_report
ORACLE_PW_SYSTEM=manager
ORACLE_USR_DBA=oracle
ORACLE_AUTODBSTART=y
ORACLE_SID=openview
ORACLE_USE_CURR_DB=y
ORACLE_NET=ov_net
ORACLE_BASE=/opt/oracle
ORACLE_DB_REINIT=y
ORACLE_IDX_DIR=/ora_db
#

The

ovoinstall installation program writes progress messages into the log file /var/opt/OV/log/OpC/mgmt_sv/install.log. The software installation process uses the

swinstall command, and you can monitor progress in the log file swagent.log with the command

tail f /var/adm/sw/swagent.log .