Customized output from:
Document Release Date: August 2016
Software Release Date: August 2016 |
|
The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HPE required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2015-2016 Hewlett Packard Enterprise Development LP
Adobe® is a trademark of Adobe Systems Incorporated.
AMD is a trademark of Advanced Micro Devices, Inc.
© 2012 Google Inc. All rights reserved. Google™ is a trademark of Google Inc.
Intel®, Intel® Itanium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.
SAP®, SAP® BusinessObjects™, and SAP® BusinessObjects™ Web Intelligence® are the trademarks or registered trademarks of SAP SE in Germany and in several other countries.
UNIX® is a registered trademark of The Open Group.
Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
For the full Oracle license text, see the open_source_third_party_license_agreements.pdf
file in the license-agreements
directory in the SOM product download file.
Read the following documents before installing HPE Storage Operations Manager (SOM):
HPE Storage Operations Manager Deployment Guide
File name = deployment_guide.pdf
Product media = Root directory\Documentation
For information about supported SOM environments, see "Planning an SOM Deployment."
The PDF document is also available at https://softwaresupport.hp.com/
SOM Support Matrix for the supported hardware and operating systems versions as well as the operating system prerequisites.
File name = support_matrix.pdf
Product media = Root directory\Documentation
HPE Storage Operations Manager Release Notes for the list of known issues.
File name = release_notes.pdf
Product media = Root directory\Documentation
SOM Device Support Matrix for the list of supported devices and device features.
File name = device_support_matrix.pdf
Product media = Root directory\Documentation
Note: The Storage Operations Manager documents are updated when new information is available. Before you deploy SOM, check for the most recent Storage Operations Manager documentation for your version of the software at https://softwaresupport.hp.com/.
You must have an HP Passport ID to access this web site.
You can view your customized document on the screen, or print it.
Documents that are customized according to your selections. PDF print drivers are available from several open source and third-party providers.
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
Read the following documents before installing HPE Storage Operations Manager (SOM):
HPE Storage Operations Manager Deployment Guide
File name = deployment_guide.pdf
Product media = Root directory\Documentation
For information about supported SOM environments, see "Planning an SOM Deployment."
The PDF document is also available at https://softwaresupport.hp.com/
SOM Support Matrix for the supported hardware and operating systems versions as well as the operating system prerequisites.
File name = support_matrix.pdf
Product media = Root directory\Documentation
HPE Storage Operations Manager Release Notes for the list of known issues.
File name = release_notes.pdf
Product media = Root directory\Documentation
SOM Device Support Matrix for the list of supported devices and device features.
File name = device_support_matrix.pdf
Product media = Root directory\Documentation
Note: The Storage Operations Manager documents are updated when new information is available. Before you deploy SOM, check for the most recent Storage Operations Manager documentation for your version of the software at https://softwaresupport.hp.com/.
You must have an HP Passport ID to access this web site.
You can install the Storage Operations Manager (SOM) only in the GUI and silent mode. Console (command) mode is not supported.
To install SOM using an XServer, set the $DISPLAY variable appropriately.
You must import the HPE public key into the Linux RPM database before installation. To do this, point your browser to the following location for instructions: https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning
If a dialog box appears during installation stating that the code signing key cannot be found, do the following:
If the installation shows an unable to open DISPLAY error message, install the specified RPM Package Manager (RPM) library versions specified in the HPE Storage Operations Manager Support Matrix. SOM requires both 32-bit and 64-bit versions of these shared libraries and this error message occurs if one or both library versions are missing.
Complete the following action before you begin the installation:
For more information about the FQDN of the SOM management server, see Obtaining or Setting the Official FQDN.
Check for the SNMP service; if installed, the SNMP trap service needs to be disabled on this server.
If you plan to install SOM from an XServer, run the xclock command to verify that you have the XDisplay variable configured correctly. If the clock does not appear, complete the following steps:
Note: Dynamic Host Configuration Protocol (DHCP) users make sure that the SOM management server is consistently assigned the same IP address.
Turn off any anti-virus software on the system. See Disabling Anti-Virus Software for more information.
SOM uses several TCP ports to communicate with other systems. See Enabling Communication Ports to confirm that these ports are available before installing SOM. Make sure that the firewall and other anti-virus applications on the SOM management server do not block the ports.
If you plan to upgrade SOM from an XServer, run the xclock command to verify that you have the XDisplay variable configured correctly. If the clock does not appear, complete the following steps:
An Oracle database administrator creates the SOM Oracle database. To install an Oracle database instance for SOM, follow this checklist:
CREATE USER <user_name> IDENTIFIED BY <password> DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp QUOTA UNLIMITED ON users;
grant Create sequence, Create session, Create table, Create view, UNLIMITED TABLESPACE to <user_name> WITH ADMIN OPTION;
grant drop any table, drop any view, DELETE ANY TABLE, INSERT ANY TABLE, UPDATE ANY TABLE to <user_name> WITH ADMIN OPTION;
grant DBA to <user_name> WITH ADMIN OPTION;
grant CONNECT to <user_name> WITH ADMIN OPTION;
The <password> must be Hps0m1.
The Oracle user name and password are required during the SOM installation.
SOM uses the Domain Name System (DNS) to determine relationships between hostnames and IP addresses. This can result in a large number of name service queries when SOM discovers storage elements.
Make sure that your DNS servers are well configured to prevent long delays when resolving name service queries. This means that the DNS server responding to the SOM name service queries has these characteristics:
On the SOM management server, make sure that the following is configured correctly for your environment:
In this instance,
<IP_Address> is the IP address of the SOM management server.
<SOM_server_name> is the FQDN of the SOM management server set during installation.
In the configuration file, resolv.conf, make sure that all identified DNS servers provide consistent hostname-to-IP address mappings and IP address-to-hostname mappings.
Before logging on to SOM, make sure to configure the web browser to interact with the SOM console. The following must be enabled in the web browser:
To complete the following procedures, you need to know the FQDN of the SOM management server.
If the SOM management server has more than one domain name, SOM chooses one during the installation process. To determine the FQDN that the SOM is using, click Help > System Information > Server tab.
To enable pop-ups, follow these steps:
To enable cookies, follow these steps:
On the Privacy tab Settings area, select one of the following options:
Accept All Cookies
Medium High
Note: This setting affects the Internet zone only. If you are connecting to the SOM management server over an Intranet, this setting has no effect.
To install SOM, log on to the server with administrator privileges.
Coexistence with HPE Operations Agent
If Operations Agent is already installed on the server where SOM is to be installed, export the certificates by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_agent
It is recommended to log on with the same user credentials that were used for the SOM installation.
To install upgrade SOM, follow these steps:
Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.
Run setup.exe from the local folder to start the installation process manually.
For example, [drive:]\local folder\Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>\setup.exe.
The HPE Software Installer wizard opens and the Introduction page appears.
The installer verifies that the system meets the software requirements. If your system does not meet the requirements, the Application Requirement Check Errors window displays a failure message. For more details about the failure message, see %TEMP%\som_preInstall.txt
.
Click Next.
The License Agreement page appears.
The Product Customization page appears.
The Product Requirements page appears. The installer performs the pre-installation checks.
The Server Configuration page appears.
The Product Requirements page appears. The installer performs the pre-installation checks.
The Pre-Install Summary page appears with the version number, list of components to be installed, and locations of the application and data folders.
The Pre-Install Summary page appears with the version number, list of components to be upgraded or newly installed and locations of the applications and data folders.
If you suspect that you do not have enough available disk space to complete the installation, see Problem: The installation requires more disk space than is available on the host system.
Click Install Upgrade to begin the installation.
The Installing page displays the Summary and Details tabs.
After the components are installed, the Post Installation dialog box appears and then several post-installation tasks are executed.
After the components are installed, the System Account Password dialog box appears.
The password must adhere to the following rules:
The HPE Storage Operations Manager Web Server Port dialog box appears.
You can specify a different port if required.
The HPE Storage Operations Manager Https Web Server Port dialog box appears.
You can specify a different port if required.
The Official Fully Qualified Domain Name (FQDN) dialog box appears.
You can specify a different FQDN if required.
The installer configures the system.
Coexistence with HPE Operations Agent
If SOM is installed on a server with Operations Agent, follow these steps:
Import the certificates that were exported before the SOM installation, by running the following command:
ovcert -importtrusted -file /tmp/backupcert_agent
Re-export the certificates, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_final
Backup the certificates on the OM server, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_OM
/tmp/backupcert_final
file to any location on the OM serverImport the certificates that are copied in step 4, by running the following command:
ovcert -importtrusted -file <l>/backupcert_final
Verify the communication between the SOM server and the OM server, by running the following command:
bbcutil
Log on with administrator privileges to the server where you plan to install SOM.
Coexistence with HPE Operations Agent
If Operations Agent is already installed on the server where SOM is to be installed, export the certificates by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_agent
To install SOM, follow these steps:
Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.
Run setup.exe from the local folder to start the installation process manually.
For example, [drive:]\local folder\Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>\setup.exe
The HPE Software Installer wizard opens and the Introduction page appears.
The installer verifies that the system meets the software requirements. If your system does not meet the requirements, the Application Requirement Check Errors window displays a failure message. For more details about the failure message, see %TEMP%\som_preInstall.txt
.
Click Next.
The License Agreement page appears.
Select I accept the terms of the License Agreement and click Next.
The Product Customization page appears.
The Server Configuration page appears.
Click Next.
Note: For an Oracle RAC, type the Scan IP or the host name (that is the cluster host name or IP).
The Instance is the Oracle RAC service name.
Click Next.
The Product Requirements page appears. The installer performs the pre-installation checks.
The Pre-Install Summary page appears with the version number, list of components to be installed, and locations of the application and data folders.
Click Install to begin the installation.
The Installing page displays the Summary and Details tabs.
After the components are installed, the System Account Password dialog box appears.
The password must adhere to the following rules:
The HPE Storage Operations Manager Web Server Port dialog box appears.
You can specify a different port if required.
The HPE Storage Operations Manager Https Web Server Port dialog box appears.
You can specify a different port if required.
The Official Fully Qualified Domain Name (FQDN) dialog box appears.
You can specify a different FQDN if required.
The installer configures the system.
If an Oracle RAC is used, follow these steps to overcome the error message and launch the SOM Console:
ovstop
Open the nnm-server.properties
file from the following location:
Windows:
%OvDataDir%\shared\nnm\conf\props\nnm-server.properties
Linux:
/var/opt/OV/shared/nnm/conf/props/nnm-server.properties
Comment the com.hp.ov.nms.oracle.sid
property
com.hp.ov.nms.oracle.serviceName
property and set its value to the service name.com.hp.ov.nms.oracle.connection.standalone.url
property.com.hp.ov.nms.oracle.connection.url
property.com.hp.ov.nms.oracle.connection.cluster.url=(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=${com.hp.ov.nms.oracle.host})(PORT=${com.hp.ov.nms.oracle.port}))(CONNECT_DATA=(service_name=${com.hp.ov.nms.oracle.serviceName})))
com.hp.ov.nms.oracle.connection.url=${com.hp.ov.nms.oracle.connection.cluster.url}
Restart the services by running the following command: ovstart
Note: Ensure that you let the command execution complete.
Coexistence with HPE Operations Agent
If SOM is installed on a server with Operations Agent, follow these steps:
Import the certificates that were exported before the SOM installation, by running the following command:
ovcert -importtrusted -file /tmp/backupcert_agent
Re-export the certificates, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_final
Backup the certificates on the OM server, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_OM
/tmp/backupcert_final
file to any location on the OM serverImport the certificates that are copied in step 4, by running the following command:
ovcert -importtrusted -file <l>/backupcert_final
Verify the communication between the SOM server and the OM server, by running the following command:
bbcutil
Access the Linux host by doing one of the following:
Use the graphics console on the localhost
Run the following command at the command prompt:
# /usr/X11R6/bin/xhost +
Access from a remote Linux client
Make sure that the X Windows server on the remote client can accept TCP connections, by following these steps:
Verify that the line for the screen number 0 (the line containing :0 local) does not contain the -nolisten TCP option. Remove the -nolisten TCP option if present. The line should appear as follows:
:0 local /usr/X11R6/bin/X
Enable TCP connections on the X Windows server of the remote client:
SUSE – Edit /etc/sysconfig/displaymanager and set the following options to 'yes':
DISPLAYMANAGER_REMOTE_ACCESS
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN
For example:
DISPLAYMANAGER_REMOTE_ACCESS="yes"
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="yes"
RHEL (for gnome) – Edit /etc/X11/gdm/gdm.conf and set the DisallowTCP option to false (uncomment if commented).
For example:
DisallowTCP=false
Run the following command at the command prompt:
# /usr/X11R6/bin/xhost +
SOM supports the use of RealVNC Viewer Free Edition version 4.1 or later to access the Linux host from a remote client. For information about how to configure the RealVNC server and how to use it to access the Linux host, see the RealVNC documentation. After you have configured the RealVNC server, follow the instructions in the Use the graphics console on the localhost section.
Before running X Window server from a client, make sure that X Windows server is running on the SOM management server.
Note: ReflectionX Manager from Attachmate corporation is the tested X Windows server to install the product. You cannot install the product using Xming as the X Windows server.
Start up a local X Windows server, connect through xterm to the remote system, and then set your $DISPLAY environment variable appropriately by using the following commands:
# DISPLAY=<ip-address>:displaynumber.screennumber
In this instance, <ip-address> is the address of the client from which the installer program is launched.
# export DISPLAY
For example:
# DISPLAY=172.168.10.15:0.0
# export DISPLAY
Log on with root privileges to the system where you plan to install SOM.
Coexistence with HPE Operations Agent
If Operations Agent is already installed on the server where SOM is to be installed, export the certificates by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_agent
It is recommended to log on with the same user credentials that were used to install the earlier version of SOM.
To install upgrade SOM, follow these steps:
Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.
For more information, see Accessing the Linux Host.
The HPE Software Installer wizard opens and the Introduction page appears.
The installer verifies that the system meets the software requirements. If your system does not meet the requirements, the Application Requirement Check Errors window displays a failure message. For more details about the failure message, see the /tmp/som_preInstall.txt
file.
The Server Configuration page appears.
The following are the default paths:
The Product Requirements page appears. The installer performs the pre-installation checks.
The Product Requirements page appears. The installer performs the pre-installation checks.
The Pre-Install Summary page appears with the version number, list of components to be installed, and locations of the application and data directories.
The Pre-Install Summary page appears with the version number, list of components to be upgraded or newly installed, and locations of the application and data directories.
If you suspect that you do not have enough available disk space to complete the installation, see Problem: The installation requires more disk space than is available on the host system.
Click Install Upgrade to begin the installation.
The Installing page displays the Summary and Details tabs.
After the components are installed, the Post Installation dialog box appears and then several post-installation tasks are executed.
After the components are installed, the System Account Password dialog box appears.
The password must adhere to the following rules:
Type a password for the system account and click OK.
You can specify a different port if required.
The HPE Storage Operations Manager Https Web Server Port dialog box appears.
You can specify a different port if required.
The Official Fully Qualified Domain Name (FQDN) dialog box appears.
You can specify a different domain name if required.
The installer configures the system.
A Gnu Privacy Guard (GPG) signature file is included with the Installer. HPE recommends that you verify the authenticity of the installer before installation.
To verify the file, follow the instructions for "Verification using GPG" at : https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning
The file verification process is valid for all operating system platforms supported by GPG. The verification process might vary depending on the GPG version and the operating system platform. For more information, see the documentation for your version of GPG.
Coexistence with HPE Operations Agent
If SOM is installed on a server with Operations Agent, follow these steps:
Import the certificates that were exported before the SOM installation, by running the following command:
ovcert -importtrusted -file /tmp/backupcert_agent
Re-export the certificates, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_final
Backup the certificates on the OM server, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_OM
/tmp/backupcert_final
file to any location on the OM serverImport the certificates that are copied in step 4, by running the following command:
ovcert -importtrusted -file <l>/backupcert_final
Verify the communication between the SOM server and the OM server, by running the following command:
bbcutil
Log on with root privileges to the system where you plan to install SOM.
Coexistence with HPE Operations Agent
If Operations Agent is already installed on the server where SOM is to be installed, export the certificates by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_agent
To install SOM, follow these steps:
Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.
For more information, see Accessing the Linux Host.
The HPE Software Installer wizard opens and the Introduction page appears.
The installer verifies that the system meets the software requirements. If your system does not meet the requirements, the Application Requirement Check Errors window displays a failure message. For more details about the failure message, see the /tmp/som_preInstall.txt
file.
The Server Configuration page appears.
The following are the default paths:
Type the name of the Oracle Host, Port, and Instance.
Note: For an Oracle RAC, type the Scan IP or the host name (that is the cluster host name or IP).
The Instance is the Oracle RAC service name.
The Product Requirements page appears. The installer performs the pre-installation checks.
The Pre-Install Summary page appears with the version number, list of components to be installed, and locations of the application and data folders.
Click Install to begin the installation.
The Installing page displays the Summary and Details tabs.
After the components are installed, the System Account Password dialog box appears.
The password must adhere to the following rules:
Type a password for the system account and click OK.
You can specify a different port if required.
The HPE Storage Operations Manager https Web Server Port dialog box appears.
You can specify a different port if required.
The Official Fully Qualified Domain Name (FQDN) dialog box appears.
You can specify a different FQDN if required.
The installer configures the system.
If an Oracle RAC is used, follow these steps to overcome the error message and launch the SOM Console:
ovstop
Open the nnm-server.properties
file from the following location:
Windows:
%OvDataDir%\shared\nnm\conf\props\nnm-server.properties
Linux:
/var/opt/OV/shared/nnm/conf/props/nnm-server.properties
Comment the com.hp.ov.nms.oracle.sid
property
com.hp.ov.nms.oracle.serviceName
property and set its value to the service name.com.hp.ov.nms.oracle.connection.standalone.url
property.com.hp.ov.nms.oracle.connection.url
property.com.hp.ov.nms.oracle.connection.cluster.url=(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=${com.hp.ov.nms.oracle.host})(PORT=${com.hp.ov.nms.oracle.port}))(CONNECT_DATA=(service_name=${com.hp.ov.nms.oracle.serviceName})))
com.hp.ov.nms.oracle.connection.url=${com.hp.ov.nms.oracle.connection.cluster.url}
Restart the services by running the following command: ovstart
Note: Ensure that you let the command execution complete.
Coexistence with HPE Operations Agent
If SOM is installed on a server with Operations Agent, follow these steps:
Import the certificates that were exported before the SOM installation, by running the following command:
ovcert -importtrusted -file /tmp/backupcert_agent
Re-export the certificates, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_final
Backup the certificates on the OM server, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_OM
/tmp/backupcert_final
file to any location on the OM serverImport the certificates that are copied in step 4, by running the following command:
ovcert -importtrusted -file <l>/backupcert_final
Verify the communication between the SOM server and the OM server, by running the following command:
bbcutil
Log on with root privileges to the system where you plan to install SOM.
Coexistence with HPE Operations Agent
If Operations Agent is already installed on the server where SOM is to be installed, export the certificates by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_agent
To install SOM, follow these steps:
Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.
Rename the file, <media>/ovinstallparams_embedded.ini to <media>/ovinstallparams.ini
The installer verifies that the system meets the software requirements. For details about the requirements check failure, see /tmp/som_preInstall.txt
.
After the installation is complete, use the following credentials to log on to the SOM Console:
User Name : system
Password : hpsom
The log files generated during the installation are available in the $Data_Dir/log/som folder.
A Gnu Privacy Guard (GPG) signature file is included with the Installer. HPE recommends that you verify the authenticity of the installer before installation.
To verify the file, follow the instructions for "Verification using GPG" at : https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning
The file verification process is valid for all operating system platforms supported by GPG. The verification process might vary depending on the GPG version and the operating system platform. For more information, see the documentation for your version of GPG.
Coexistence with HPE Operations Agent
If SOM is installed on a server with Operations Agent, follow these steps:
Import the certificates that were exported before the SOM installation, by running the following command:
ovcert -importtrusted -file /tmp/backupcert_agent
Re-export the certificates, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_final
Backup the certificates on the OM server, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_OM
/tmp/backupcert_final
file to any location on the OM serverImport the certificates that are copied in step 4, by running the following command:
ovcert -importtrusted -file <l>/backupcert_final
Verify the communication between the SOM server and the OM server, by running the following command:
bbcutil
Log on with root privileges to the system where you plan to install SOM.
Coexistence with HPE Operations Agent
If Operations Agent is already installed on the server where SOM is to be installed, export the certificates by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_agent
To install SOM, follow these steps:
Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.
Rename the file, <media>/ovinstallparams_oracle.ini to <media>/ovinstallparams.ini.
Modify the file <media>/ovinstallparams.ini to provide values only for the following parameters:
db.host=<host_name/IP_Address>
db.instance=<SID_name>
db.port=<port_number>
db.user.loginname=<user_name>
Note: For an Oracle RAC, type the Scan IP or the host name (that is the cluster host name or IP).
The Instance is the Oracle RAC service name.
Run the following command:
./setup.bin -i silent
The Installer verifies that the system meets the software requirements. For details about the requirements check failure, see /tmp/som_preInstall.txt
.
If an Oracle RAC is used, follow these steps to overcome the error message and launch the SOM Console:
ovstop
Open the nnm-server.properties
file from the following location:
Windows:
%OvDataDir%\shared\nnm\conf\props\nnm-server.properties
Linux:
/var/opt/OV/shared/nnm/conf/props/nnm-server.properties
Comment the com.hp.ov.nms.oracle.sid
property
com.hp.ov.nms.oracle.serviceName
property and set its value to the service name.com.hp.ov.nms.oracle.connection.standalone.url
property.com.hp.ov.nms.oracle.connection.url
property.com.hp.ov.nms.oracle.connection.cluster.url=(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=${com.hp.ov.nms.oracle.host})(PORT=${com.hp.ov.nms.oracle.port}))(CONNECT_DATA=(service_name=${com.hp.ov.nms.oracle.serviceName})))
com.hp.ov.nms.oracle.connection.url=${com.hp.ov.nms.oracle.connection.cluster.url}
Restart the services by running the following command: ovstart
Note: Ensure that you let the command execution complete.
After the installation is complete, use the following credentials to log on to the SOM Console:
User Name : system
Password : hpsom
The log files generated during the installation are available in the $Data_Dir/log/som folder.
A Gnu Privacy Guard (GPG) signature file is included with the Installer. HPE recommends that you verify the authenticity of the installer before installation.
To verify the file, follow the instructions for "Verification using GPG" at : https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning
The file verification process is valid for all operating system platforms supported by GPG. The verification process might vary depending on the GPG version and the operating system platform. For more information, see the documentation for your version of GPG.
Coexistence with HPE Operations Agent
If SOM is installed on a server with Operations Agent, follow these steps:
Import the certificates that were exported before the SOM installation, by running the following command:
ovcert -importtrusted -file /tmp/backupcert_agent
Re-export the certificates, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_final
Backup the certificates on the OM server, by running the following command:
ovcert -exporttrusted -file /tmp/backupcert_OM
/tmp/backupcert_final
file to any location on the OM serverImport the certificates that are copied in step 4, by running the following command:
ovcert -importtrusted -file <l>/backupcert_final
Verify the communication between the SOM server and the OM server, by running the following command:
bbcutil
When you install SOM, a temporary Instant-On license is automatically installed and remains valid for 60 days.
To view the license information, click Help > System Information > View Licensing Information.
The Instant-On license enables you to use all the features of SOM. You should obtain and install a permanent license key as soon as possible.
For more information about obtaining and installing a permanent license, see the SOM Deployment Guide.
Now that you have installed SOM, you can configure SOM to discover and manage the storage elements in your environment.
Use the SOM console to configure SOM.
To access the SOM console, follow these steps:
If the SOM management server has more than one domain name, SOM chooses one during the installation process. To determine the FQDN that the SOM is using, click Help > System Information > Server tab.
During installation, SOM creates a system account to access the SOM console.
For everyday use, the SOM administrator sets up an account for each user (or group of users) and assigns a pre-configured access privileges to each account. User accounts and roles determine who has access to the SOM console, as well as which workspaces and actions are available to each user.
Before configuring SOM sign-in access for your team, determine which pre-defined SOM role is appropriate for each team member. The roles are hierarchical, meaning the higher level roles include all privileges of the lower roles in the hierarchy (Administrator is highest, Guest is lowest).
User accounts and groups are configured in the SOM console (Configuration > Security). For more information, see Configure User Groups in the SOM online help.
The SOM online help describes the SOM console and how to use SOM to discover and manage your environment.
To access the online help, from the SOM console menu bar, click Help > HPE Storage Operations Manager Documentation Library.
This opens the Welcome page of the HPE Storage Operations Manager Help. The Welcome page contains links to resources to facilitate effortless use of SOM to accomplish the different tasks required to manage your storage environment.
For more information about the SOM console, see Using the SOM Interface in the online help.
The following sections contain information about startup problems during installing and troubleshooting SOM. Other sections in this guide reference these sections as appropriate.
SOM users access SOM using the official FQDN.
To determine the official FQDN of the SOM management server, use one of the following methods:
If you need to change the FQDN that was set during installation, use the somsetofficialfqdn.ovpl command.
To improve installation performance, turn off the anti-virus software on the target system by following these steps:
During SOM installation, you set the system account password. If you forget the system account password, you can change it by using the somchangesyspw.ovpl script.
To change the password, follow these steps:
A number of TCP ports are used to communicate between a source server (SOM, OBR, SMI Agent) and other systems (devices/clients/integrations). These ports must be enabled and kept open for communication.
To enable the ports on a Windows server, follow the steps:
The Windows server might have anti-virus protection enabled. Configure anti-virus protection to make sure the Windows server allows access to the required ports.
Port | Name | Purpose | Configuration File |
---|---|---|---|
80 | nmsas.server.port.web.http |
Default HTTP port - used for Web UI & Web Services. After this port is open, it becomes bi-directional. |
nms-local.properties You can also change this during installation. |
443 | nmsas.server.port.web.https | Default secure HTTPS port (SSL) - used for Web UI & Web Services. | nms-local.properties |
1098 | nmsas.server.port.naming.rmi |
Used by SOM command line tools to communicate with a variety of services used by SOM. HPE recommends configuring the system firewall to restrict access of these ports to localhost only. |
nms-local.properties |
1099 | nmsas.server.port.naming.port |
Used by SOM command line tools to communicate with a variety of services used by SOM. HPE recommends configuring the system firewall to restrict access of these ports to localhost only. |
nms-local.properties |
3873 | nmsas.server.port.remoting.ejb3 |
Used by SOM command line tools to communicate with a variety of services used by SOM. HPE recommends configuring the system firewall to restrict access of these ports to localhost only. |
nms-local.properties |
4444 | nmsas.server.port.jmx.jrmp |
Used by SOM command line tools to communicate with a variety of services used by SOM. HPE recommends configuring the system firewall to restrict access of these ports to localhost only. |
nms-local.properties |
4445 | nmsas.server.port.jmx.rmi |
Used by SOM command line tools to communicate with a variety of services used by SOM. HPE recommends configuring the system firewall to restrict access of these ports to localhost only. |
nms-local.properties |
4446 | nmsas.server.port.invoker.unified |
Used by SOM command line tools to communicate with a variety of services used by SOM. HPE recommends configuring the system firewall to restrict access of these ports to localhost only. |
nms-local.properties |
4712 | nmsas.server.port.ts.recovery | Internal transaction service port. | nms-local.properties |
4713 | nmsas.server.port.ts.status | Internal transaction service port. | nms-local.properties |
4714 | nmsas.server.port.ts.id
|
Internal transaction service port. | nms-local.properties |
5432 | com.hp.ov.nms.postgres.port | The embedded PostgreSQL database uses this port. | nms-local.properties |
8886 | OVsPMD_MGMT | SOM ovspmd (process manager) management port. | /etc/services |
8887 | OVsPMD_REQ | SOM ovsmpd (process manager) request port. | /etc/services |
8989 | com.hp.ov.nms. events.action.server.port | Enables the action server port to be configurable. | nnmaction.properties |
Port | Purpose | Client, Server |
---|---|---|
80 | TCP default HTTP port; used for Web UI and Web services. | Server |
80 | TCP default HTTP port to connect to other applications. The actual client port depends on the configuration in SOM management server. | Client |
389 | TCP default LDAP port. | Client |
443 |
TCP default secure HTTPS port to connect to other applications; the actual port depends on the configuration on SOM management server. Default HTTPS port for HPE Operations Manager on Windows client. |
Client |
443 | TCP default secure HTTPS port; used for Web UI and Web services. | Server |
636 | TCP default secure LDAP port (SSL). | Client |
135 | TCP psexec port, Windows agentless on SOM management server. | Server |
445 | TCP psexec port, Windows agentless on SOM management server. | Server |
139 | TCP winexe port, Windows agentless on SOM management server. | Server |
383 | LCore communication port on SOM management server used for communication with the reporting server. | Server, Client |
Device | Device Interface |
Port (SOM Outbound/Device Inbound) |
---|---|---|
Storage | ||
HPE 3PAR* | SMI-S | 22, 5989 |
HP EVA | SMI-S | 5989 |
HPE StoreEasy Storage | WMI | 135, 445 |
HPE XP | RMI-API | 1099, 51099, 51100 |
NetApp 7 Mode, NetApp Cluster Mode | ONTAP API | 443 |
Hitachi AMS, Hitachi Unified Storage, Hitachi VSP | XML | 1099, 2001, 51099, 51100 |
IBM SAN Volume Controller*, IBM Storwize V7000*, IBM XIV | SMI-S | 5989 |
EMC CLARiiON*, EMC VNX Block*, EMC Symmetrix* | SMI-S | 5989 |
EMC VNX Filer* | XML API | 443 |
EMC VPLEX | REST API | 443 |
EMC Isilon | SSH | 22 |
Switches | ||
Brocade Switch* | SMI-S | 5989 |
Cisco Switch* | SNMP v2, v3 | 161 |
Hosts | ||
HP-UX | SSH (Agentless) | 22 |
CIM Extension | 4673 | |
IBM AIX | SSH (Agentless) | 22 |
CIM Extension | 4673 | |
IBM HMC | SSH (Agentless) | 22 |
Red Hat Enterprise Linux (RHEL) | SSH (Agentless) | 22 |
CIM Extension | 4673 | |
Solaris host | SSH (Agentless) | 22 |
CIM Extension | 4673 | |
SuSE Linux | SSH (Agentless) | 22 |
CIM Extension | 4673 | |
Windows Agentless (for Windows Management Server) | WMI (Agentless) | 135, 445 |
Windows Agentless (for Linux Management Server) | WMI (Agentless) | 139 |
Windows Host | CIM Extension | 4673 |
Note: * Incidents supported for these devices.
Note: For devices with Incident support, the device inbound port is 161 and SOM inbound port is 162.
To uninstall SOM, follow these steps:
The HPE Software Installer wizard opens and the Initialization page appears.
The Pre-Uninstall Summary page appears.
The Uninstalling page displays the Summary and Details tabs.
The Uninstall Complete page appears.
For details, view the following the log file, after removing SOM:
%temp%\HPStorageOperationsManager_<version>_HPOvInstaller.txt.
To uninstall SOM, follow these steps:
Run the following command:
./setup.bin
The HPE Software Installer wizard opens and the Initialization page appears.
The Pre-Uninstall Summary page displays the list of installed components and the locations of the application and data directories.
The Uninstalling page displays the Summary and Details tabs.
The Uninstall Complete page appears.
If you suspect problems after removing SOM, view the following log file: /tmp/HPStorageOperationsManager_<version>_HPOvInstaller.txt
Before you install OBR, read the Requirements for the SOM Reporting Server section of the SOM Support Matrix.
OBR must be installed on a separate server from the SOM management server.
To enable SOM reports, follow this sequence:
Install OBR using the instructions in the OBR Interactive Installation Guide.
The Installation Guide is available as a ZIP file, OBR_10.00_Interactive_Installation.zip, in the Documentation/en_US directory, after you extract the OBR TAR installer file.
To view the Installation Guide, open the OBR_Interactive_Installation.htm file after extracting the OBR_10.00_Interactive_Installation.zip file.
Post installation, complete the tasks in the section, Post Installation Configuration of HPE Operations Bridge Reporter (OBR) (Chapter 2: Tasks 1-8) of the Reports Guide to configure OBR for SOM.
The Reports Guide is available at the following location of the extracted SOM installer: Root directory\Documentation
Install and deploy the necessary SOM content packs.
Configure the connection between the two servers (the SOM management server and the OBR server) to transfer files.
For more information about establishing a connection between the two servers, follow the instructions in the Configuring Connections Between SOM Management Server and SOM Reporting Server section of the Reports Guide.
In scenarios where OBR is already installed, do the following to enable SOM reports:
Install and deploy the SOM content packs if required.
If a scenario has one OBR server configured to report on multiple SOM servers, in a consolidated reporting mode, you might not need to install all the SOM content packs. Only install and deploy the new packs.
If a scenario uses the OBR server as a cross-product reporting solution, you might need to install and deploy the SOM content packs as they may not exist on the OBR server.
Configure the connection between the SOM management server and the OBR server to transfer files between the two servers.
Follow the instructions in the section, Configuring Connections Between SOM Management Server and SOM Reporting Server of the Reports Guide to configure the connection.
The following information discusses some possible installation problems and solutions:
When you install the SOM on Linux, you cannot choose the locations for the binaries ($Install_Dir), and the data files ($Data_Dir). These locations are as follows:
If you want to install the SOM on a non-default directory, use the symbolic links for the /opt/OV and /var/opt/OV folders.
The syntax to create the symbolic links is as follows:
ln -s <large disk> /opt/OV
ln -s <large disk> /var/opt/OV
Install SOM.
By default, the jboss application server uses several ports for communication with SOM. These ports are commonly used by Oracle and other applications. If the SOM installer determines that the jboss application server ports are already being used by other applications, such as the Oracle database server, the installer displays an error message regarding the port contention.
To determine if port contention is a problem for SOM, check the following log file:
<Data_Dir>\conf\nnm\props\nms-local.properties
$Data_Dir/conf/nnm/props/nms-local.properties
The command displays the following status:
Service | PID | State | Last Message(s) |
---|---|---|---|
OVsPMD | 1552 | RUNNING | - |
somtrapreceivermd | 244 | RUNNING | Initialization Complete. Trap Receiver is STOPPED. |
somdbmgr | 1324 | RUNNING | Database available. |
somjboss | 1360 | RUNNING | Initialization complete. |
somaction | 6132 | RUNNING | Initialization complete. |
Service | PID | State | Last Message(s) |
---|---|---|---|
OVsPMD | 1552 | RUNNING | - |
somtrapreceivermd | 244 | RUNNING | Initialization Complete. Trap Receiver is STOPPED. |
somjboss | 1360 | RUNNING | Initialization complete. |
somaction | 6132 | RUNNING | Initialization complete. |
Stop or start SOM services as needed. At the command prompt, type the appropriate command:
ovstop -c <service>
ovstart -c <service>
Ports | Protocol |
---|---|
161 | udp |
162 | udp |
nmsas.server.port.web.http | tcp |
Problem: During installation, a message indication that the preinstall step (phase II) failed and check the /tmp/som_preinstall_phaseII.log file for details appears.
Solution: The SOM installation script attempts to automatically create two groups (nmsgrp and nmsdb), two users (nmsproc and nmsdbmgr), and their corresponding $HOME folders. These operations could fail for the following reasons:
If the SOM installer fails to create these groups, users, or folders, the installation stops. In this case, you can create the users manually and restart the installation:
You can create the groups, users, and the $HOME folder before starting the installer if you know these operations might fail or you need to control user ID, group ID, or the $HOME location.
Remove all unwanted and unused paths that exists in the PATH environment variable, and then continue the installation.
Rediscover the 3PAR arrays after the SOM in place upgrade.
cannot execute binary file
error message. The following are the details of the error message:[root@srmesx10-vm2 sombase]# ./setup.bin Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
Launching installer...
./setup.bin: line 3419: /tmp/install.dir.3089/Linux/resource/jre/bin/java: cannot execute binary file
./setup.bin: line 3419: /tmp/install.dir.3089/Linux/resource/jre/bin/java: Success
This error message is displayed when you install the SOM on unsupported Linux platform. For all supported Linux platform, see the HPE Storage Operations Manager Support Matrix.
If you have provided any incorrect input to the Oracle database, this warning message appears. This does not impact the installation process.
If the X11 component is not installed on your system, the installer uses the console mode by default. To resolve this issue, do any of the following:
© Copyright 2015-2016 Hewlett Packard Enterprise Development LP