Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

Perform the following tasks before launching the BMC ProactiveNet installation program.

  • Clean your temporary directories. Start with the temporary folder in your home folder. You may not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with ProactiveNet.
  • Ensure that the nobody user account exists on the target computer.
  • Disable X Windows access control by using the xhost command.
  • If the init file is not copied to the /etc/rc3.d directory, then the BMC ProactiveNet Integration Service corresponding to the init file is not listed as installed (in the list of existing BMC ProactiveNet Integration Service installations) during installation of other integration services. This is valid only for non-root users.

Checking the pre-installation requirements for Solaris

When you start the BMC ProactiveNet Server installation, the installer checks to ensure that the target computer is configured based on the recommended settings. The installer checks the environment and reports a status of OK or Not OK for each configuration variable that it checks.

For Solaris, the following pre-installation checks are run:

Check

Description

Operating system

Checks if operating system is SunOS.

Zone on the System

The BMC ProactiveNet Server does not support installation on the global zone when there are subzones present. Installation is only supported on non-global full zones.
Zones are supported from Solaris 10 and above, so the check for presence of zones is from Solaris 10 onwards.

Root [ / ] partition

Ensures that the root partition is not 100% full. The installation may fail if there is insufficient space available in the root partition.

BEM Components

Checks if BMC Impact Solutions components are present. If they are present, they must be uninstalled.

User nobody exists in the system

Checks if the nobody user and nobody group exist in the system.

Operating System/
Processor Type

Checks if the processor is 64-bit SPARC processor. Installation is not supported on 32-bit SPARC processor.

Operating System/
Version

Checks if SunOS version is supported.

IP address

Verifies the IP address.

Host names resolved IP against IP

Checks if the resolved IP for the host name matches the IP address.

Loghost matching with host name

Checks if loghost matches the host name

DNS configuration

Checks whether DNS is configured on system. This is required for DHCP support for the BMC ProactiveNet Server.

Permissions on /tmp

Checks if /tmp directory has read, write and execute permission for owner, group and others.

gzip

Checks if the gzip compression utility is present in the /usr/bin/gzip or /bin/gzip or
/usr/local/bin/gzip path. Gzip is no longer shipped with BMC ProactiveNet Server and is required for successful installation.

Default router

Checks if the default gateway is configured.

Available swap space

Checks if the computer has the minimum amount of swap space available.

File mode creation mask

Checks if /usr/bin/umask value is 022.

Total memory

Checks if the computer has the minimum memory available.

Motif Runtime kit

Checks whether Motif Runtime kit (SUNWmfrun), ICE components package (SUNWxwice) and X11 platform software (SUNWxwplt) installation components are installed.

Patch level on the system

Check if all the required patches needed for the JRE on the particular OS are present.

If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any failed checks, review the prerequisites in this section to ensure that you have implemented all of them. If all the prerequisites have been implemented and the pre-installation check still fails for some checks, see the [BMC ProactiveNet Troubleshooting Guide|PN90:PDFs^ProactiveNet_Troubleshooting_9.0.pdf].

If the required patches are not installed, you will get the following message.
Solaris Patch Needed

If your system requires a new patch, the text will be similar to the following:
Checking patch level of the system...System does NOT have required level of patch.

To run the ProactiveNet Server successfully on Solaris, install the required patches from the SunSolve website and reboot the system before installing the BMC ProactiveNet Server.

Checking the pre-installation requirements for Linux

When you start the BMC ProactiveNet Server installation, the installer checks to ensure that the target computer is configured based on the recommended settings. The installer checks the environment and reports a status of OK or Not OK for each configuration variable that it checks.

For Linux, the following pre-installation checks are run

Check

Description

Operating system

Checks if operating system is RedHat Enterprise Linux 6 64 bit. Other Linux operating systems are not supported for Server installation.

Kernel version

Checks if the kernel version is 2.6.32.

Root [ / ] partition

Ensures that the root partition is not 100% full. The installation may fail if there is insufficient space available in the root partition.

BEM Components

Checks if BMC Impact Solutions components are present. If they are present, they must be uninstalled.

IP address

Verifies the IP address.

Host names resolved IP against IP

Checks if the resolved IP for the host name matches the IP address.

DNS configuration

Checks whether DNS is configured on system. This is required for DHCP support for the BMC ProactiveNet Server.

Permissions on /tmp

Checks if /tmp directory has read, write and execute permission for owner, group and others.

gzip

Checks if the gzip compression utility is present in the /usr/bin/gzip or /bin/gzip or /usr/local/bin/gzip path. Gzip is no longer shipped with BMC ProactiveNet Server and is required for successful installation.

gunzip

Checks if the gunzip compression utility is present in the /usr/bin/gunzip or /bin/gunzip or /usr/local/bin/gunzip path.

Default router

Checks if the default gateway is configured.

Port availability

Checks if following ports are available: 80, 443, 1099, 1100, 1827, 1828, 1851, 2638, 3084, 3115, 3182, 3183, 8005, 8008, 8009, 8093, 9149, 12123, 12124, 12126, 12134, 12141, 15000, 45000

Available swap space

Checks if the computer has a minimum of 3 gigabytes of swap space available.

File mode creation mask

Checks if umask value is 022.

Total memory

Checks if the computer has a minimum of 4 gigabytes of memory available.

Mail configuration

Checks for mail configuration.

Required libraries

Checks for required libraries. For information on the required libraries, see System requirements and product compatibility.

If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any failed checks, review the prerequisites in this section to ensure that you have implemented all of them. If all the prerequisites have been implemented and the pre-installation check still fails for some checks, see the [BMC ProactiveNet Troubleshooting Guide|PDFs^ProactiveNet_Troubleshooting_9.0.pdf].

.

  • No labels