HPE Storage Operations Manager

For the Windows® and Linux® operating systems

Software Version: 10.20

Customized output from:

Interactive Installation Guide

Document Release Date: August 2016

Software Release Date: August 2016

 
   
   
   
   
   
   

Legal Notices

Warranty

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.

Restricted Rights Legend

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 Notice

© Copyright 2015-2016 Hewlett Packard Enterprise Development LP

Trademark Notices

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.

Oracle Technology — Notice of Restricted Rights

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.

 
 
 
 

Interactive Installation Guide

Before You Install

Read the following documents before installing HPE Storage Operations Manager (SOM):

  1. 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/

  2. 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

  3. HPE Storage Operations Manager Release Notes for the list of known issues.

    File name = release_notes.pdf

    Product media = Root directory\Documentation

  4. 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.

Choose a Task

Install
Silent Install
Upgrade
Uninstall

Choose an Operating System

Linux
Windows

Choose a Database Type

Embedded Database
Oracle Database

Choose a Reporting Option

Install a new OBR instance
Use an existing OBR instance
Do not use SOM reporting

View or Print

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.

Check your selections

The following steps are customized according to your selections. Check that your selections are correct.

 

If any selections are not correct, click Change.

Read before Installation

Read the following documents before installing HPE Storage Operations Manager (SOM):

  1. 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/

  2. 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

  3. HPE Storage Operations Manager Release Notes for the list of known issues.

    File name = release_notes.pdf

    Product media = Root directory\Documentation

  4. 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.

Planning for Installation

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:

  1. Leave the dialog box open and complete step 2.
  2. Follow the instructions available at https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCodeSigning
  3. Click No in the dialog box to resume installation.

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:

  • Determine the fully qualified domain name (FQDN) of the SOM management server. The FQDN must meet the following requirements:
    • It must be DNS resolvable to the SOM management server.
    • It must be available so that the SOM management server can be accessed from other computers on your network.

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:

  1. Export the $DISPLAY environment variable to an appropriate value.
  2. Run the xhost command to enable a connection from the system running the installation process to the system displaying the installation process.
  3. Run the xclock command to verify the configuration.
    The clock should appear on the X Server.

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 need to change the locale, configure the SOM management server to support the locale you require (For example, Japanese). For more information about supported locales, see the SOM Support Matrix.

Planning for Upgrade

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:

  1. Export the $DISPLAY environment variable to an appropriate value.
  2. Run the xhost command to enable a connection from the system running the installation process to the system displaying the installation process.
  3. Run the xclock command to verify the configuration.
    The clock should appear on the X Server.

Understanding Oracle Requirements

An Oracle database administrator creates the SOM Oracle database. To install an Oracle database instance for SOM, follow this checklist:

  • Work with your Oracle database administrator and install the Oracle database according to the instructions provided by Oracle.
  • Create a database instance for SOM.
    Make sure that you know the host name of the Oracle server and the database instance name.
  • Create a tablespace to be used only by an SOM user that accesses the database.
  • Assign a tablespace size depending on the number of storage elements (hosts, storage systems, switches) in the environment.
    Note: The database requirement grows as SOM discovers additional elements.
    It is important to assign a large enough tablespace quota to a user. If the tablespace is not large enough, SOM may not create the required tables. This causes problems after installation. To prevent this, set the quota to unlimited.
  • Create an Oracle user with the following commands and grant the user access to the newly created tablespace:

    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 user name and password can be of your choice.
    Notes:
    The <user_name> can be of your choice.

    The <password> must be Hps0m1.

    The Oracle user name and password are required during the SOM installation.

Checking for a Well-Configured DNS

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:

  • The DNS server is an authoritative server and does not forward DNS requests.
  • The DNS server has consistent hostname-to-IP address mappings and IP address-to-hostname mappings.
  • If the network uses multiple DNS servers, all of them must respond consistently to all name service queries.

On the SOM management server, make sure that the following is configured correctly for your environment:

  • The host file %SystemRoot%\system32\drivers\etc\hosts must have a minimum of two entries:
    127.0.0.1 (loopback loghost)
    <SOM management server IP Address> <SOM management server name>
  • The host file %SystemRoot%\system32\drivers\etc\hosts takes precedence when the nslookup command is not successful.

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.

Configuring a Web Browser to Access the SOM Console

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:

  • JavaScript
  • Pop-up windows from the SOM management server
  • Cookies from the SOM management server

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.

Mozilla Firefox

Tip: Mozilla Firefox enables the use of JavaScript by default. Disabling JavaScript requires a privacy extension. If SOM generates an error indicating that JavaScript is disabled, check the Extensions option of the Firefox Add-ons Manager to determine whether a privacy extension is in use.

To enable pop-ups, follow these steps:

  1. In Mozilla Firefox, click Tools > Options.
  2. Click Content.
  3. Enable the Block pop-up windows check box.
  4. Next to the Block pop-up windows check box, click Exceptions.
  5. Add the FQDN of the SOM management server to the list of allowed sites.
  6. Click OK.

To enable cookies, follow these steps:

  1. In Mozilla Firefox, click Tools > Options.
  2. Click Privacy.
  3. Navigate to History and select Remember History.
  4. Click OK.
  5. Restart the web browser.

Microsoft Internet Explorer

  1. In Internet Explorer, click Tools> Internet Option.
  2. On the Security tab, select the zone that includes the SOM management server, and then click Custom level.
  3. Under Scripting, select the Enable option for Active scripting.
  4. 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.

  5. On the Privacy tab, select the Turn on Pop-up Blocker check box, and then click Settings.
  6. Add the FQDN of the SOM management server to the list of allowed sites.
  7. Restart the web browser.

Installing Upgrading SOM on a Windows System with the Embedded Database

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:

  1. Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.

  2. Copy the Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.zip file, and then extract the installation files to the local host server.
  3. 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.

  4. Click Next.
    The License Agreement page appears.

  5. Select I accept the terms of the License Agreement, and then click Next.

    The Product Customization page appears.

    The Product Requirements page appears. The installer performs the pre-installation checks.

  6. On the Product Customization page, do one of the following:
    • Click Next to continue with the default SOM folder locations.
    • Click Browse if you want to select different locations for the application and data folders.
    • Click Reset to revert to the default folder locations.
    Note: The selected application and data folders are referred to as <Install_Dir> and <Data_Dir> respectively in this Guide.
    The following are the default paths:
    <Install_Dir> - [drive:]\Program Files(x86)\HP\HP BTO Software\
    <Data_Dir> - [drive:]\ProgramData\HP\HP BTO Software\
    If you change a folder, keep the length of the path relatively short. Long paths cause the installation to fail.

    The Server Configuration page appears.

  7. Select HPE Software Embedded Database, and then click Next.

    The Product Requirements page appears. The installer performs the pre-installation checks.

  8. Click Next.

    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.

  9. Click Install Upgrade to begin the installation.

    The Installing page displays the Summary and Details tabs.

    • Summary tab - The progress of installation.
    • Details tab - The status of the installation of each SOM management server component.

    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:

    • Contain at least eight characters.
    • Be a combination of the following: upper case, lower case, and numbers.
    • Not contain the user id 'system'.
    • Not start with a numeric.
    • Not contain any spaces.
  10. Type a password for the system account and click OK.
    Note: The system account is used to sign in to the SOM console. For more information about changing the password of the system account, see Resetting the System Account Password.

    The HPE Storage Operations Manager Web Server Port dialog box appears.

  11. Click OK to confirm the use of the default port 80 for SOM web server HTTP communication.

    You can specify a different port if required.
    The HPE Storage Operations Manager Https Web Server Port dialog box appears.

  12. Click OK to confirm the use of the default port 443 for SOM web server HTTPS communication.

    You can specify a different port if required.
    The Official Fully Qualified Domain Name (FQDN) dialog box appears.

  13. Click OK to confirm the default FQDN of the SOM management server.

    You can specify a different FQDN if required.
    The installer configures the system.

  14. Click Finish.
    This completes the installation.
    The Launch HPE Storage Operations ManagerWeb UI page appears.
  15. Click Yes to launch the SOM console.
    You may use the system account and password created during the installation to sign in.
    The Installation Complete dialog box appears with the list of installed components in the Details tab.
  16. Click Done.
    You may want to see the log files generated during installation to check output messages. The log files are available in the <Data_Dir>\log\som folder.

Coexistence with HPE Operations Agent

If SOM is installed on a server with Operations Agent, follow these steps:

  1. Import the certificates that were exported before the SOM installation, by running the following command:

    ovcert -importtrusted -file /tmp/backupcert_agent

  2. Re-export the certificates, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_final

  3. Backup the certificates on the OM server, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_OM

  4. Copy the /tmp/backupcert_final file to any location on the OM server
  5. Import the certificates that are copied in step 4, by running the following command:

    ovcert -importtrusted -file <l>/backupcert_final

  6. Verify the communication between the SOM server and the OM server, by running the following command:

    bbcutil

Installing SOM on a Windows System with an Oracle Database

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:

  1. Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.

  2. Copy the zip file Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.zip and extract the installation files to the local host server.
  3. 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.

  4. Click Next.
    The License Agreement page appears.

  5. Select I accept the terms of the License Agreement and click Next.
    The Product Customization page appears.

  6. On the Product Customization page, do one of the following:
    • Click Next to continue with the default SOM folder locations.
    • Click Browse if you want to select different locations for the application and data folders.
    • Click Reset to revert to the default folder locations.
    Note: The selected application and data folders are referred to as <Install_Dir> and <Data_Dir> respectively in this Guide.
    The following are the default paths:
    <Install_Dir> - [drive:]\Program Files(x86)\HP\HP BTO Software\
    <Data_Dir> - [drive:]\ProgramData\HP\HP BTO Software\
    If you change a folder, keep the length of the path relatively short. Long paths cause the installation to fail.

    The Server Configuration page appears.

  7. Select Oracle and click Next.
  8. Select Primary Server Installation to initialize an Oracle database using previously defined database accounts.
    Note: Presently, SOM does not support the Secondary Server Installation mode.

    Click Next.

  9. Type the name of the Oracle Host, Port, and Instance.
    Note: If the Oracle instance is not configured for the default port 1521, type the port number configured for the Oracle 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.

    Click Next.

  10. Type the Username and Password to connect to the Oracle database.

    The Product Requirements page appears. The installer performs the pre-installation checks.

  11. Click Next.

    The Pre-Install Summary page appears with the version number, list of components to be installed, and locations of the application and data folders.

  12. Click Install to begin the installation.

    The Installing page displays the Summary and Details tabs.

    • Summary tab - The progress of installation.
    • Details tab - The status of the installation of each SOM management server component.

    After the components are installed, the System Account Password dialog box appears.

    The password must adhere to the following rules:

    • Contain at least eight characters.
    • Be a combination of the following: upper case, lower case, and numbers.
    • Not contain the user id 'system'.
    • Not start with a numeric.
    • Not contain any spaces.
  13. Type a password for the system account, and then click OK.
    Note: The system account is used to Sign In to the SOM console. For more information about changing the password of the system account, see Resetting the System Account Password.

    The HPE Storage Operations Manager Web Server Port dialog box appears.

  14. Click OK to confirm the use of the default port 80 for SOM web server HTTP communication.

    You can specify a different port if required.
    The HPE Storage Operations Manager Https Web Server Port dialog box appears.

  15. Click OK to confirm the use of the default port 443 for SOM web server HTTPS communication.

    You can specify a different port if required.
    The Official Fully Qualified Domain Name (FQDN) dialog box appears.

  16. Click OK to confirm the default FQDN of the SOM management server.

    You can specify a different FQDN if required.
    The installer configures the system.

  17. Click Finish.
    This completes the installation.
    The Launch HPE Storage Operations Manager Web UI page appears.
  18. Click Yes to launch the SOM console.
    You may use the system account and password created during the SOM installation to Sign In.
    The Installation Complete dialog box appears with the list of installed components in the Details tab.
  19. Click Done.
    You may want to see the log files generated during installation to check output messages. The log files are available in the <Data_Dir>\log\som folder.
  20. If an Oracle RAC is used, follow these steps to overcome the error message and launch the SOM Console:

    1. Stop the services by running the following command: ovstop
    2. 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

    3. Comment the com.hp.ov.nms.oracle.sid property

    4. Uncomment the com.hp.ov.nms.oracle.serviceName property and set its value to the service name.
    5. Comment the com.hp.ov.nms.oracle.connection.standalone.url property.
    6. Comment the com.hp.ov.nms.oracle.connection.url property.
    7. Add the following two properties:
      1. 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})))

      2. com.hp.ov.nms.oracle.connection.url=${com.hp.ov.nms.oracle.connection.cluster.url}

    8. Save and close the file.
    9. 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:

  1. Import the certificates that were exported before the SOM installation, by running the following command:

    ovcert -importtrusted -file /tmp/backupcert_agent

  2. Re-export the certificates, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_final

  3. Backup the certificates on the OM server, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_OM

  4. Copy the /tmp/backupcert_final file to any location on the OM server
  5. Import the certificates that are copied in step 4, by running the following command:

    ovcert -importtrusted -file <l>/backupcert_final

  6. Verify the communication between the SOM server and the OM server, by running the following command:

    bbcutil

Accessing the Linux Host

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:

    1. Open /etc/X11/xdm/Xservers.
    2. 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

    3. 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

    4. If you have made any changes in the configuration files during the previous steps, reboot the system for the changes to take effect.
    5. Run the following command at the command prompt:

      # /usr/X11R6/bin/xhost +

    6. Set the display to your client. For more information, refer to the Linux shell documentation.
  • Accessing the Linux Host from a Remote Client Using RealVNC

    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.

  • Accessing the Linux Host from a Remote Windows Client

    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

Installing Upgrading SOM on a Linux Operating System with the Embedded Database

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:

  1. Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.

  2. Copy the Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz tar file to the local host server.
    Extract the contents of the file by running the following command:
    tar -xvf Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz
  3. Make sure that the $DISPLAY environment variable is configured.

    For more information, see Accessing the Linux Host.

  4. Run ./setup.bin command

    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.

  5. Click Next.
    The License Agreement page appears.
  6. Select I accept the terms of the License Agreement, and then click Next.

    The Server Configuration page appears.

    Note: The default application and data paths are referred to as $Install_Dir and $Data_Dir respectively in this Guide.

    The following are the default paths:

    • $Install_Dir=/opt/OV
    • $Data_Dir=/var/opt/OV

    The Product Requirements page appears. The installer performs the pre-installation checks.

  7. Select HPE Software Embedded Database, and then click Next.

    The Product Requirements page appears. The installer performs the pre-installation checks.

  8. Select HPE Software Embedded Database, and then and click Next.The Product Requirements page appears. The installer performs the pre-installation checks.
  9. Click Next.

    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.

  10. Click Install Upgrade to begin the installation.

    The Installing page displays the Summary and Details tabs.

    • Summary tab - The progress of installation.
    • Details tab - The status of the installation of each SOM management server component.

    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:

    • Contains at least eight characters.
    • Be a combination of the following: upper case, lower case, and numbers.
    • Not contain the user id 'system'.
    • Not start with a number/numerical character.
    • Not contain any spaces.
  11. Type a password for the system account and click OK.

    Note: The system account is used to Sign In to the SOM console. For more information about changing the password of the system account, see Resetting the System Account Password.

    The HPE Storage Operations Manager Web Server Port dialog box appears.

  12. Click OK to confirm the use of the default port 80 for SOM web server HTTP communication.

    You can specify a different port if required.
    The HPE Storage Operations Manager Https Web Server Port dialog box appears.

  13. Click OK to confirm the use of the default port 443 for SOM web server HTTPS communication.

    You can specify a different port if required.
    The Official Fully Qualified Domain Name (FQDN) dialog box appears.

  14. Click OK to confirm the default FQDN of the SOM management server.

    You can specify a different domain name if required.
    The installer configures the system.

  15. Click Finish.
    This completes the installation.
    The Launch HPE Storage Operations Manager Web UI page appears.
  16. Click OK to launch the SOM console.
    You may use the system account and password created during the SOM installation to sign in.
    The Installation Complete dialog box appears with the list of installed components in the Details tab.
  17. Click Done.
    You may want to see the log files generated during installation to check output messages. The log files are available in the $Data_Dir/log/som directory.

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:

  1. Import the certificates that were exported before the SOM installation, by running the following command:

    ovcert -importtrusted -file /tmp/backupcert_agent

  2. Re-export the certificates, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_final

  3. Backup the certificates on the OM server, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_OM

  4. Copy the /tmp/backupcert_final file to any location on the OM server
  5. Import the certificates that are copied in step 4, by running the following command:

    ovcert -importtrusted -file <l>/backupcert_final

  6. Verify the communication between the SOM server and the OM server, by running the following command:

    bbcutil

Installing SOM on a Linux System with an Oracle Database

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:

  1. Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.

  2. Copy the tar file Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz to the local host server.
    Extract the contents of the file by running the following command:
    tar -xvf Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz
  3. Make sure that the $DISPLAY environment variable is configured.

    For more information, see Accessing the Linux Host.

  4. Run the following command: ./setup.bin

    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.

  5. Click Next.
    The License Agreement page appears.
  6. Select I accept the terms of the License Agreement, and then click Next.

    The Server Configuration page appears.

    Note: The default application and data paths are referred to as $Install_Dir and $Data_Dir respectively in this Guide.

    The following are the default paths:

    • $Install_Dir=/opt/OV
    • $Data_Dir=/var/opt/OV
  7. Select Oracle, and then click Next.
  8. Select Primary Server Installation to initialize an Oracle database using previously defined database accounts.
    Note: Presently, SOM does not support the Secondary Server Installation mode.
  9. Click Next.
  10. Type the name of the Oracle Host, Port, and Instance.

    Note: If the Oracle instance is not configured for the default port 1521, type the port number configured for the Oracle 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.

  11. Click Next.
  12. Type the Username and Password to connect to the Oracle database.

    The Product Requirements page appears. The installer performs the pre-installation checks.

  13. Click Next.

    The Pre-Install Summary page appears with the version number, list of components to be installed, and locations of the application and data folders.

  14. Click Install to begin the installation.

    The Installing page displays the Summary and Details tabs.

    • Summary tab - The progress of installation.
    • Details tab - The status of the installation of each SOM management server component.

    After the components are installed, the System Account Password dialog box appears.

    The password must adhere to the following rules:

    • Contain at least eight characters.
    • Be a combination of the following: upper case, lower case, and numbers.
    • Not contain the user id 'system'.
    • Not start with a numeric.
    • Not contain any spaces.
  15. Type a password for the system account and click OK.

    Note: The system account is used to Sign In to the SOM console. For more information about changing the password of the system account, see Resetting the System Account Password.

    The HPE Storage Operations Manager Web Server Port dialog box appears.

  16. Click OK to confirm the use of the default port 80 for SOM web server HTTP communication.

    You can specify a different port if required.
    The HPE Storage Operations Manager https Web Server Port dialog box appears.

  17. Click OK to confirm the use of the default port 443 for SOM web server HTTPS communication.

    You can specify a different port if required.
    The Official Fully Qualified Domain Name (FQDN) dialog box appears.

  18. Click OK to confirm the default FQDN of the SOM management server.

    You can specify a different FQDN if required.
    The installer configures the system.

  19. Click Finish.
    This completes the installation.
    The Launch HPE Storage Operations Manager Web UI page appears.
  20. Click Yes to launch the SOM console.
    You may use the system account and password created during the installation to Sign In.
    The Installation Complete dialog box appears with the list of installed components in the Details tab.
  21. Click Done.
    You may want to see the log files generated during installation to check output messages. The log files are available in the $Data_Dir/log/som folder.
  22. If an Oracle RAC is used, follow these steps to overcome the error message and launch the SOM Console:

    1. Stop the services by running the following command: ovstop
    2. 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

    3. Comment the com.hp.ov.nms.oracle.sid property

    4. Uncomment the com.hp.ov.nms.oracle.serviceName property and set its value to the service name.
    5. Comment the com.hp.ov.nms.oracle.connection.standalone.url property.
    6. Comment the com.hp.ov.nms.oracle.connection.url property.
    7. Add the following two properties:
      1. 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})))

      2. com.hp.ov.nms.oracle.connection.url=${com.hp.ov.nms.oracle.connection.cluster.url}

    8. Save and close the file.
    9. 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:

  1. Import the certificates that were exported before the SOM installation, by running the following command:

    ovcert -importtrusted -file /tmp/backupcert_agent

  2. Re-export the certificates, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_final

  3. Backup the certificates on the OM server, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_OM

  4. Copy the /tmp/backupcert_final file to any location on the OM server
  5. Import the certificates that are copied in step 4, by running the following command:

    ovcert -importtrusted -file <l>/backupcert_final

  6. Verify the communication between the SOM server and the OM server, by running the following command:

    bbcutil

Silent Install on a Linux System with the Embedded Database

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:

  1. Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.

  2. Copy the TAR file Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz to the local host server.
    Extract the contents of the file by running the following command:
    tar –xvf Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz
  3. Copy the ovinstallparams_embedded.ini file from the directory, <media>/support to its parent directory. That is the folder where the setup.bin file is located.
  4. Rename the file, <media>/ovinstallparams_embedded.ini to <media>/ovinstallparams.ini

  5. Run the following command: ./setup.bin -i silent
Note: You must watch for the completion of the command because the silent install does not launch the installer wizard.

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:

  1. Import the certificates that were exported before the SOM installation, by running the following command:

    ovcert -importtrusted -file /tmp/backupcert_agent

  2. Re-export the certificates, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_final

  3. Backup the certificates on the OM server, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_OM

  4. Copy the /tmp/backupcert_final file to any location on the OM server
  5. Import the certificates that are copied in step 4, by running the following command:

    ovcert -importtrusted -file <l>/backupcert_final

  6. Verify the communication between the SOM server and the OM server, by running the following command:

    bbcutil

Silent Install on a Linux System with an Oracle Database

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:

  1. Ensure that the target server meets the prerequisites described in "Requirements for the SOM Management Server" in the SOM Support Matrix.

  2. Copy the TAR file Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz to the local host server.
    Extract the contents of the file by running the following command:
    tar –xvf Software_HPE_Storage_Operations_Manager_<version_number>_<SKU_number>.tar.gz
  3. Copy the ovinstallparams_oracle.ini file from the <media>/support directory, to its parent directory. That is the folder where the setup.bin file is located.
  4. Rename the file, <media>/ovinstallparams_oracle.ini to <media>/ovinstallparams.ini.

  5. 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.

  6. Set the password of the Oracle database user name to Hps0m1.
  7. Run the following command:

    ./setup.bin -i silent

    Note: You must watch for the completion of the command since the silent install does not launch the installer wizard.

    The Installer verifies that the system meets the software requirements. For details about the requirements check failure, see /tmp/som_preInstall.txt.

  8. If an Oracle RAC is used, follow these steps to overcome the error message and launch the SOM Console:

    1. Stop the services by running the following command: ovstop
    2. 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

    3. Comment the com.hp.ov.nms.oracle.sid property

    4. Uncomment the com.hp.ov.nms.oracle.serviceName property and set its value to the service name.
    5. Comment the com.hp.ov.nms.oracle.connection.standalone.url property.
    6. Comment the com.hp.ov.nms.oracle.connection.url property.
    7. Add the following two properties:
      1. 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})))

      2. com.hp.ov.nms.oracle.connection.url=${com.hp.ov.nms.oracle.connection.cluster.url}

    8. Save and close the file.
    9. 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:

  1. Import the certificates that were exported before the SOM installation, by running the following command:

    ovcert -importtrusted -file /tmp/backupcert_agent

  2. Re-export the certificates, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_final

  3. Backup the certificates on the OM server, by running the following command:

    ovcert -exporttrusted -file /tmp/backupcert_OM

  4. Copy the /tmp/backupcert_final file to any location on the OM server
  5. Import the certificates that are copied in step 4, by running the following command:

    ovcert -importtrusted -file <l>/backupcert_final

  6. Verify the communication between the SOM server and the OM server, by running the following command:

    bbcutil

Licensing SOM

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.

Getting Started with SOM

Now that you have installed SOM, you can configure SOM to discover and manage the storage elements in your environment.

Accessing the SOM Console

Use the SOM console to configure SOM.

To access the SOM console, follow these steps:

  1. Make sure that you are using a supported web browser. To view the list of supported browser, see the HPE SOM Support Matrix.
  2. From the SOMmanagement server, enable the web browser for JavaScript, pop-up windows and to accept cookies.
  3. Type the following URL into a web browser window: https://<fully_qualified_domain_name>:<port>/som
    where <fully_qualified_domain_name> represents the FQDN of the SOM management server, and <port> is the port that the jboss application server uses for communicating with the SOM console.
  4. 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.

  5. In the SOM sign-in window, type system as the user account name and the password created during installation. Click Sign In.
If you cannot start the SOM console when pointing your browser to the SOM management server that is installed on a Linux operating system, you might have a Linux firewall on the SOM management server that is blocking the HTTP port. See Problem: You cannot start the SOM console when accessing a Linux SOM management server.
If you cannot start the SOM console when pointing your browser to the SOM management server that is installed on a Windows operating system, you might have a Windows firewall on the SOM management server that is blocking the HTTP port. See Problem: You cannot start the SOM console when accessing a Windows SOM management server

User Accounts and Roles

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.

Using the SOM 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.

Additional Information

The following sections contain information about startup problems during installing and troubleshooting SOM. Other sections in this guide reference these sections as appropriate.

Obtaining or Setting the Official FQDN

SOM users access SOM using the official FQDN.

To determine the official FQDN of the SOM management server, use one of the following methods:

    • Use the somofficialfqdn.ovpl command to display the value of the FQDN set during installation.
    • In the SOM console, click Help > System Information > Server tab. Find the value for the FQDN.

If you need to change the FQDN that was set during installation, use the somsetofficialfqdn.ovpl command.

Disabling Anti-Virus Software

To improve installation performance, turn off the anti-virus software on the target system by following these steps:

  1. On a Windows desktop, click Start > Settings > Control Panel.
  2. Double-click Administrative Tools.
  3. Double-click Component Services.
  4. Select Services.
  5. Review the status of the anti-virus services. For example, review the anti-virus services provided by companies such as Symantec or McAffee.
  6. For each anti-virus service, right-click the service and click Stop.
    After you complete the SOM installation, restart each anti-virus service.

Resetting the System Account Password

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:

  1. Stop the SOM processes using the ovstop -c command.
  2. As the administrator, run the somchangesyspw.ovpl script to set the system password.
  3. As root, run the somchangesyspw.ovpl script to set the system password.
  4. Start the SOM processes using the ovstart -c command.

Enabling Communication Ports

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:

  1. Open the Windows Firewall with Advanced Security console (Start > Administrative Tools > Windows Firewall with Advanced Security).
  2. Create an inbound rule and enable it for each port that SOM requires.

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.

Ports Used by SOM
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

 

Ports Used by SOM and Other Systems
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 Specific Ports used by SOM
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.

Uninstalling SOM on Windows

To uninstall SOM, follow these steps:

  1. Log on with administrator privileges to the server where SOM is installed.
  2. Turn off any anti-virus software on the system.
    1. From the Control Panel > Administrative Tools > Component Services, select Services.
    2. Review the status of installed anti-virus services such as Symantec, McAfee, and so on. Right-click the service, and then click Stop. For example, anti-virus services such as, Symantec, McAffee, and so on.
      Note: Restart the anti-virus service, after you remove SOM.
  3. Use one of the following options:
    • At the command prompt, type the following command:
      <Install_Dir>\Uninstall\HPStorageOperationsManager\setup.exe
    • Click Start > Programs > HP > Storage Operations Manager > Uninstall HP SOM.
    • Click Start > Control Panel > Programs and Features > Storage Operations Manager > Uninstall/Change.

    The HPE Software Installer wizard opens and the Initialization page appears.

  4. Select Uninstall, and then click Next.
    Note: SOM does not support the Repair option.

    The Pre-Uninstall Summary page appears.

  5. Click Uninstall.

    The Uninstalling page displays the Summary and Details tabs.

    • Summary tab - The progress of the uninstallation.
    • Details tab - The status of the uninstallation of each SOM management server component.

    The Uninstall Complete page appears.

  6. Click Done.
  7. Click Yes to reboot the server.

For details, view the following the log file, after removing SOM:

%temp%\HPStorageOperationsManager_<version>_HPOvInstaller.txt.

Uninstalling SOM on Linux

To uninstall SOM, follow these steps:

  1. Log on with root privileges to the server where SOM is installed.
  2. Use the cd command to change to the <Install_Dir>/Uninstall/HPStorageOperationsManager directory.
  3. Run the following command:

    ./setup.bin

    The HPE Software Installer wizard opens and the Initialization page appears.

  4. Select Uninstall.
    Note: SOM does not support the Repair option.

    The Pre-Uninstall Summary page displays the list of installed components and the locations of the application and data directories.

  5. Click Uninstall.

    The Uninstalling page displays the Summary and Details tabs.

    • Summary tab - The progress of the uninstallation.
    • Details tab - The status of the uninstallation of each SOM management server component.

    The Uninstall Complete page appears.

  6. Click Done.
  7. Click Yes to reboot the server.

If you suspect problems after removing SOM, view the following log file: /tmp/HPStorageOperationsManager_<version>_HPOvInstaller.txt

Install a New OBR Instance

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:

  1. 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.

  2. 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

    Caution: Do not perform the post-installation configuration tasks in the OBR Configuration Guide (Part 1: Configuring OBR, Chapter 4: Primary Configuration). They are not applicable for SOM.
  3. Install and deploy the necessary SOM content packs.

  4. 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.

Use an Existing OBR Instance

In scenarios where OBR is already installed, do the following to enable SOM reports:

  1. 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.

  2. 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.

Installation Problems and Solutions

The following information discusses some possible installation problems and solutions:

Problem: The SOM installation process does not accept the Oracle user name and password.
Solution:
  1. Check and make sure to use the correct Oracle user name and password.
  2. If step 1 does not solve the problem, obtain the correct port number for the given Oracle instance and also verify the instance name from your Oracle database administrator. Continue the installation.
Problem: User cannot install the SOM on non-default directory on Linux platform.
Solution:

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:

  • $Install_Dir=/opt/OV
  • $Data_Dir=/var/opt/OV

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.

Problem: Installation stops due to jboss port conflict.
Solution:

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>\log\som\boot.log
$Data_Dir/log/som/boot.log

To resolve any port contentions, follow these steps:
  1. As a user with administrator privileges, open the following file in a text editor:

    <Data_Dir>\conf\nnm\props\nms-local.properties

  2. As a user with root privileges, open the following file in a text editor:

    $Data_Dir/conf/nnm/props/nms-local.properties

  3. Modify existing entries and replace conflicting port numbers with available port numbers.
  4. Save the file, and then restart the SOM services by completing these steps:
    1. ovstop -c
    2. ovstart -c
    The ovstop and ovstart commands are also available from the Start menu.
Problem: Some SOM program components do not work correctly.
Solution:
Verify that all SOM services have been installed and started:
  1. At a command prompt, type the following command:
    ovstatus -c


    The command displays the following status:

    ServicePIDStateLast Message(s)
    OVsPMD

    1552

    RUNNING-
    somtrapreceivermd244RUNNINGInitialization Complete. Trap Receiver is STOPPED.
    somdbmgr1324RUNNINGDatabase available.
    somjboss1360RUNNINGInitialization complete.
    somaction6132RUNNINGInitialization complete.
    ServicePIDStateLast Message(s)
    OVsPMD

    1552

    RUNNING-
    somtrapreceivermd244RUNNINGInitialization Complete. Trap Receiver is STOPPED.
    somjboss1360RUNNINGInitialization complete.
    somaction6132RUNNINGInitialization complete.

     

    Note: The values listed in the PID column are sample Process IDs.
  2. Stop or start SOM services as needed. At the command prompt, type the appropriate command:
    ovstop -c <service>
    ovstart -c <service>

Problem: User cannot access the SOM console.
Solution:
If you cannot access the SOM console when pointing your browser to an SOM management server that is installed on a Linux operating system, you might have a Linux firewall on the SOM management server that is blocking the HTTP port. To remedy this problem, do the following:
  1. Open the Security Level form using one of the following menus or commands:
    • Applications->System Settings->Security Level
    • System->Administration->Security Level and Firewall
    • Run the /usr/bin/system-config-securitylevel command and wait for the dialog box to appear.
  2. After the dialog box appears, complete only one of the following remedies:
    • Disable the firewall.
    • Leave the firewall enabled and add the following specific ports:
    • Ports Protocol
      161 udp
      162 udp
      nmsas.server.port.web.http tcp
      In the table above, nmsas.server.port.web.http represents the port selected for the SOM management server during installation. Add the nmsas.server.port.web.http value shown in the $Data_Dir/conf/nnm/props/nms-local.properties file to the list of allowed ports.
      Note: If you plan to use SSO, add the nmsas.server.port.web.http value shown in the $Data_Dir/conf/nnm/props/nms-local.properties file to the list of allowed ports.
Problem: Disabling a pre-existing PostgreSQL instance on an SOM management server running the Linux operating system.
Solution:
Some Linux servers have an instance of PostgreSQL running. You need to disable the PostgreSQL instance before installing SOM. Complete the following steps to check for an instance of PostgreSQL and to disable it:
  1. To check for the presence of a PostgreSQL instance, type the following command: ps -ef | grep postgres
  2. View the information on your screen. If there is an instance of PostgreSQL running, disable it before continuing with the SOM installation process using the following command: chkconfig posgresql off
  3. Install SOM.
Problem: You cannot start the SOM console when accessing a Windows SOM management server.
Solution:
If you cannot start the SOM console when pointing your browser to a Windows SOM management server, a firewall might be blocking the HTTP port. To troubleshoot this problem, run the browser on the SOM management server. If you can access the SOM console from this browser, but remote browsers fail, you need to check the ports.
 
To remedy this problem, add the jboss.http.port value shown in the <Data_Dir>\conf\nnm\props\nms-local.properties file to the list of allowed ports.

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:

  1. Your IT department disabled the ability to create users and groups by disabling the useradd or groupadd commands.
  2. If the location of the $HOME folder exists over NFS, and the root user is not able to create the $HOME folder.

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:

  1. Create the nmsproc user in the nmsgrp group. Set $HOME to any folder, but that folder must exist.
  2. Create the nmsdbmgr user in the nmsdb group. Set $HOME to any folder, but that folder must exist.

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.

Problem: The SOM installation process fails to continue when the PATH environment variable length exceeds the maximum number of characters limit.
Solution:

Remove all unwanted and unused paths that exists in the PATH environment variable, and then continue the installation.

Problem: After the SOM in place upgrade, the 3PAR data collection fails.
Solution:

Rediscover the 3PAR arrays after the SOM in place upgrade.

Problem: The SOM installation on Linux platform fail with the 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

Solution:

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.

Problem: The SOM install wizard is not launched on Linux boxes.
Solution:

If the X11 component is not installed on your system, the installer uses the console mode installation. Configure the X11 component on your system to install in GUI mode.

Problem: While installing the SOM with an external Oracle database, a warning message appears in the summary screen.
Solution:

If you have provided any incorrect input to the Oracle database, this warning message appears. This does not impact the installation process.

Problem: The console mode installation is not supported on Linux.
Solution:

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:

  • Configure X11 on your system to install in GUI mode.
  • Perform a silent mode installation.
Problem: If Access Control (ACL) is not enabled, the install fails on Linux boxes.
Solution:

Verify that you have enabled the ACL for /opt/OV and /var/opt/OV folders in fstab file. If the ACL is not enabled, change the fstab settings to enable the ACL for /opt/OV and /var/opt/OV directories.

Problem: While uninstalling the SOM, the DLL is missing pop-up message appears.
Solution:
Click Ok on the pop-up window to proceed. This does not interrupt the uninstalling process.

© Copyright 2015-2016 Hewlett Packard Enterprise Development LP