HP Network Node Manager iSPI Network Engineering Toolset Diagnostics Server Release Notes

Part -I

This part of the document provides an overview of the NNM iSPI Network Engineering Toolset Software 9.20 released in February, 2014.
For an overview of the NNM iSPI Network Engineering Toolset Software 9.20 released in May 2012, see Part -II.

Software Version: 9.20 / February 2014

The HP NNM iSPI Network Engineering Toolset diagnostic server extends the powerful network management capabilities of NNMi by providing additional troubleshooting and diagnostic tools for network engineers.

For a list of supported hardware platforms, operating systems, and databases, see the support matrix. You can find both the Support Matrix (supportmatrix_en.html) and the Release Notes (releasenotes_en.html) at the root directory of the installation media.

Overview of this Version
Installation Guide and Support Matrix
Licensing
Upgrading
Known Problems, Limitations, and Workarounds
HP Software Support
Legal Notices

Overview of this Version

Overview of the NNM iSPI NET diagnostics server 9.20 Release

Diagnostic flows are run by NNM iSPI NET during the lifecycle of management incidents. These diagnostic flows automate the gathering and analysis of information from network devices. Diagnostic flows log into network devices using SSH or Telnet and run a series of commands defined in the flow. These commands extract troubleshooting information from specified network devices. Diagnostic flows can be run automatically when incidents are registered or manually by the operator against a node or incident.

The NNM iSPI NET diagnostics server consists of an embedded version (9.07) of HP Operations Orchestration (HP OO) and HP OO flows.

For a detailed overview of NNM iSPI NET diagnostics server 9.20, see Introducing HP NNM iSPI Network Engineering Toolset Software in the Planning and Installation Guide (see Installation Guide and Support Matrix).

New Features in version 9.20

The NNM iSPI NET 9.20 diagnostics server provides a new version of the embedded OO server (9.07), a new OO content release (9.00.06), and a hotfix (hf_142835) to provide updated browser support for more recent versions of Firefox and Internet Explorer.

Installation Guide and Support Matrix

Installation requirements, as well as instructions for installing NNM iSPI NET diagnostics server, are documented in the installation guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's installation media as install-guide_en.pdf.

For a list of supported hardware platforms, operating systems, and databases, see the Support Matrix.

Licensing

NNMi installs with an instant-on license for NNM iSPI NET that is valid for 60 days. After 60 days, the NNM iSPI NET diagnostic flows are no longer run if you do not obtain a permanent license. To view information about your NNM iSPI NET license, open the NNMi console and select Help → System Information. From the NNMi informational window, select View Licensing Information.

For information about installing and managing licenses, see the Installation Guide.

Upgrading from NNM iSPI NET diagnostics server version 9.10

Note: Upgrades from the 9.00 version of the iSPI-NET diagnostics server are not supported. You must uninstall MySQL and HP OO before reinstalling the 9.20 version.

The installation wizard (setup_x64.exe) provided with NNM iSPI NET diagnostics server will not upgrade the 9.10 embedded HP OO server to the 9.20 embedded HP OO server. The following manual upgrade procedure can be performed from the NNM iSPI NET diagnostics server 9.20 installation media.

1. With HP OO services running on your system, run the performOOupdates.bat command located on the installation media using the following syntax:

performOOupdates.bat [OO installation folder] [OO admin password] [OO https port] > %TEMP%\upgrade.log 2>&1

performOOupdates.bat "%ICONCLUDE_HOME%" password 8443 > %TEMP%\upgrade.log 2>&1

HP recommends you use "%ICONCLUDE_HOME% as the OO installation folder. If you supply your own path, do not include a trailing "\" in the OO installation folder path, as this will adversely affect upgrade processing.

The processing from this batch file will:

• install OO 9.07
• install OO hotfix hf_142835
• install OO content 9.00.06
• recover all the OO keystores previously in use on your system that were replaced by the OO updates

Be patient while this batch file is running. It can take  60 minutes or longer if running from a DVD drive. Check the upgrade.log file in the %TEMP% for any errors. The log file will be important to troubleshoot any failures during the upgrade.

2. Run the setup_x64.exe command. Specify the required passwords used during the previous installation of HP OO. Also, specify the NNMi location, port, and system password information. Let this installer run to completion. This step will install updated diagnostics flows into the upgraded embedded OO server.
3. Modify the configuration %ICONCLUDE_HOME%\Central\conf\Central.properties file to make a final change to the OO configuration. The line containing

dharma.antisamy.defalt.policy=slashdot.xml

should be changed to

dharma.antisamy.defalt.policy=anythinggoes.xml

This change instructs HP OO to permit reports containing embedded html to be displayed and reverts HP OO to its prior behavior with version 9.00.

After making this change, stop and restart HP OO services

net stop RSJRAS
net stop RSCentral
net start RSCentral
net start RSJRAS

4. Optionally perform the following to address report id generation problems when using MySQL. This step is not required but will be helpful should HP OO experience a problem selecting a new new report id when a flow is run.

Very infrequently HP OO might experience a problem where new report id's are not being selected correctly when using MySQL. The following procedure installs a stored procedure into MySQL that corrects any problems each time MySQL is restarted. You must know the MySQL root password and the database name HP OO is using within MySQL. Before running the following commands make sure that C:\Program Files\MySQL\MySQL Server 5.1\bin or the bin folder from your MySQL installation is in your path.

net stop RSJRAS
net stop RSCentral
cd [iSPI-NET 9.20 dist folder]\Upgrade_9.07.0005\resources
copy sp_reset_run_id.sql %TEMP%
cd %TEMP%

Edit %TEMP%\sp_reset_run_id.sql; then remove the first two lines from the file such that the first line is delimiter $$

Next run the command

mysql.exe --user=root --password=[rootpassword] --execute="show databases"

Note the response that indicates the available databases. Hopefully one is nnminet, the original default database name specified by the NNM iSPI NET diagnostics server 9.00 installer. Otherwise identify the database name used during the original installation.

Run the following mysqlcommand to add the stored procedure contained in the sp_reset_run_id.sql file.

mysql.exe --database=[nnminet] --user=root --password=[rootpassword] --execute="source sp_reset_run_id.sql;"

cd [iSPI-NET 9.20 dist folder]\Upgrade_9.07.0005\resources

Copy the init.sql file to the MySQL installation directory. Typically this would be: C:\Program Files\MySQL\MySQL Server 5.1.

Modify the init.sql file to change database name from dharma to nnminet or use the database configured for OO which should be displayed after running the show databases command above

Add the following line to the end of the MySQL initialization file at MySQLINSTALLDIR\my.ini.

init-file=C:\Program Files\MySQL\MySQL Server 5.1\init.sql

Shutdown and Restart MySQL service

net stop MySQL
net start MySQL

Restart HP OO

net start RSCentral
net start RSJRAS

Recovering from an upgrade failure

While unlikely, it is possible that while running step number 1 above, the upgrade could fail. For example, suppose you provided an incorrect path to the installation location of HP OO. It is important to check the log file to which you redirected the output and verify that no failures occurred. You might rerun step number 1 to perform an upgrade again. Before rerunning the performOOupdates.bat command again you should verify that the HP OO keystores (%ICONCLUDE_HOME%\Central\conf\rc_keystore and %INCONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\ras_keystore.jks) both exist. If these files no longer exist you will need to perform the following manual steps after the next run of the performOOupdates.bat command.

• Remove the %ICONCLUDE_HOME%\Central\conf\nnmgenpas.cer file.
• Remove the %ICONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\nnmgenras.cer file.
• Copy the %ICONCLUDE_HOME%\Central\conf\rc_keystore.original file to the %ICONCLUDE_HOME%\Central\conf\rc_keystore file.
• Copy the %ICONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\ras_keystore.jks.original file to the %ICONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\ras_keystore.jks file.
• cd [iSPI-NET 9.20 dist folder]
• run adjustcerts.bat "%ICONCLUDE_HOME%" [fully qualified hostname]

for example, run adjustcerts.bat "%ICONCLUDE_HOME%" hostname.domain.com

After the adjustcerts.bat command completes, the nnmgenpas and the nnmgenras files will have been recreated and certificates will have been reset in the rc_keystore and ras_keystore.jks files. Continue with step 2 above.

Upgrading and Running with Full Standalone HP OO

In order to use a Full Standalone HP OO system it must be upgraded to the following minimum levels

• 9.07
• hotfix hf_142835
• OO content 9.00.06
• Recover your keystores from the backups made during the upgrade to 9.03 per the upgrade release notes

You will find the appropriate patches for your HP OO server from HP software's online support self service web site or your HP OO support contact.

Note: The OO software upgrades provided on this iSPI-NET installation image have only been tested with a direct upgrade from the base HP OO 9.00 and not from any intermediary levels of OO and are designed to be used with the embedded OO version supplied with the NNMi 9.10 version of iSPI-NET. You should upgrade your full OO server to the software levels indicated above using the recommended installation procedures as identified by the HP Operations Orchestration support team.

Once at this level of OO software, make sure that the nnmgenpas.cer file has been created and matches the certificates used in HP OO. If you are installing for the first time on an HP OO installation you will need to create this file. If upgrading on from an existing installation on HP OO you just need to verify that the nnmgenpas.cer file matches the certificate used by HP OO Central after the upgrade steps have been completed. See Introducing HP NNM iSPI Network Engineering Toolset Software in the Planning and Installation Guide (see Installation Guide and Support Matrix).

Finally follow the instructions in this document starting with step #2 above (run setup_x64.exe) and complete through step #4 to finish the upgrade or complete the setup on a full HP OO system.

Known Problems, Limitations, and Workarounds

• The NNM iSPI NET diagnostics server is initially configured using self-signed certificates. When browsers first connect to the server after installation, an invalid certificate message is displayed due to this configuration. You can continue to the HP OO web site by selecting the appropriate link, depending on your browser type. To alleviate this condition, the HP OO PAS certificate needs to be signed by a valid Certificate Authority. After NNM iSPI NET diagnostics server installation is complete, generate a Certificate Signing Request for the HP OO PAS certificate, and submit the request to your preferred Certificate Authority. After a new certificate is returned by the Certificate Authority, this certificate can be imported back to the PAS keystore (rc_keystore). If the Certificate Authority you utilize is already trusted by Java by default, no further action is needed. If the Certificate Authority you utilize is not trusted by Java by default, import the signed certificate to the NNMi truststore again. Consult the Installation Guide for details on this process.
• The NNM iSPI NET diagnostics server is not supported for use in High Availability (HA) or NNMi application failover implementations. The NNM iSPI NET diagnostics server must be installed on a system separate from the multiple nodes participating in an HA model. Each node in an HA implementation can be bound to the single separate NNM iSPI NET diagnostics server and can dispatch requests to this node.
• The NNM iSPI NET diagnostics server is not supported for use in cluster configurations as provided in the standard HP Operations Orchestration product. The full HP Operations Orchestration product must be purchased and used if you want to facilitate clustering as supported in this implementation.
• When you click on the results link in the Diagnostics tab of a node or incident and the diagnostics flow result is no longer available in the NNM iSPI NET diagnostics server (or HP OO), the following message is displayed in the browser: "Dhamra.dhamra.reports.individual.cannot_find_repair_history[1]". This message indicates that the records in the HP OO database have been removed. This situation can occur if the NNM iSPI NET diagnostics server is reinstalled, if the supporting MySQL database is reinitialized, or if the supporting MySQL database records have been removed.
• When implementing the use of customer-defined HP OO flows in NNMi, only incidents which have a Source Object bound to the incident are able to invoke flows. You can determine if a Source Object is bound to an incident by looking at the Source Object column when viewing incidents or by opening the incident and checking the Source Object field. A value of "None" indicates the incident is not bound to a Source Object. If you manually attempt to run diagnostics from the incident form, the following error message will be displayed: "Invoke of service com.hp.ov.nms.events:name=Rba method submitIncidentsForFlowExecution for ids:[nnnnn] failed: javax.management.RuntimeMBeanException caused by java.lang.NullPointerException".

Potential Installation Issues

• Loading NNMi flows into the embedded HP OO 9.07 server can take upwards of 60 minutes. The installation process, as noted below, reconfigures the embedded HP OO server with new SSL certificates, which requires a stop and restart of the HP OO RSCentral service. The initial stop of the RSCentral Windows service might take 10 minutes with a Java process showing 100% CPU load. The service eventually stops and the installation completes. Please be patient during this processing.
• The NNM iSPI NET diagnostics server installer requires an HTTP connection to the NNMi management server. If you have disabled HTTP on the NNMi management server, you will need to re-enable HTTP before running the NNM iSPI NET diagnostics server installer.
• The NNM iSPI NET diagnostics server installer cannot run from a UNC based path. The installer must run from the local file system.
• The NNM iSPI NET diagnostics server installer adds several components to the system: .NET if not installed on Windows and HP OO. The installer makes decisions based on what it finds on the system.
  • HP OO on Windows requires .NET Framework 2.0 Service Pack 1 and either 3.0 or 3.5 SP1 with ASP.NET enabled. On Windows Server 2008, .NET Framework 3.5.1 must be added using "Server Manager" and can't be installed via the iSPI NET diagnostics server installer. The iSPI NET diagnostics server installer will report the error ".NET V3 Framework Not Installed. Exit Code: 5100" if it tries to install the .NET V3 framework and the system is not yet properly configured. To fix this start "Server Manager". Click on "Features". Select ".NET Framework 3.5.1" and install this feature. You may be prompted to add other required Roles as well. Once .NET Framework 3.5.1 is added as a feature to the system, you can rerun the iSPI NET diagnostics server installer and it will detect that .NET Framework 3.5.1 is now installed.
  • If HP OO already exists on the system, the embedded HP OO and .NET are not installed. In this case, only the NNM iSPI NET diagnostic flows are loaded in the existing HP OO, and the installer binds this system to the specified NNMi management server. In order to accomplish binding to the NNMi management server, the HP OO system's certificates must be inspected and possibly changed to provide a proper hostname within the certificate. See the Installation Guide for details on setting up proper certificates. If these manual steps are not followed, the installer reports an error when binding to the NNMi management server.
• In certain situations you may have uninstalled HP OO and then wish to reinstall the NNMi SPI NET diagnostics server. After uninstalling HP OO several files will remain in the HP OO installation folders which will impact reinstallation of the NNM iSPI NET diagnostics server. Previous versions of the NNM iSPI NET diagnostics server installer would not detect this condition and reinstallation of the iSPI NET diagnostics server would fail to regenerate appropriate SSL certificates for use in HP OO and NNMi. Diagnostics flows would never properly be submitted to HP OO due to the use of invalid certificates. The 9.20 version of the NNM iSPI NET diagnostics server installer will detect this condition and will prompt the user to remove these files before proceeding. If the user answers no, the NNM iSPI NET diagnostics server installer will abort. If the user answers yes, the NNM iSPI NET diagnostics server installer will remove the prior configuration files before continuing.
• If a problem occurs during the HP OO installation step but after the database and user have been created, you can restart the installation using the Start Again button. Before you start the install again, you must change the selected MySQL database name. If you do not change the database name, the installation will fail again when it attempts to create the same database a second time.

English Locale Only

On non-English systems, the HP NNM iSPI NET diagnostics server runs in the English locale.

Domain Name System (DNS) Configuration Known Problems

Security as implemented using a certificate-based infrastructure relies heavily on a well-configured Domain Name System (DNS) to convert discovered IP addresses to hostnames. An improper configuration can result in NNMi being unable to dispatch requests to the HP OO system. See the Installation Guide for more details on proper hostname resolution of the HP NNM iSPI NET diagnostics server system by NNMi.

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

Legal Notices

© Copyright 2008-2014 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP 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.

The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

AMD is a trademark of Advanced Micro Devices, Inc.

Google™ is a trademark of Google Inc.

Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries.

Java is a registered trademark of Oracle and/or its affiliates.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Part -II

This part of the document provides an overview of the NNM iSPI Network Engineering Toolset Software 9.20 released in May, 2012.
For an overview of the NNM iSPI Network Engineering Toolset Software 9.20 released in February 2014, see Part -I.

Software Version: 9.20 / May 2012

The HP NNM iSPI Network Engineering Toolset diagnostic server extends the powerful network management capabilities of NNMi by providing additional troubleshooting and diagnostic tools for network engineers.

For a list of supported hardware platforms, operating systems, and databases, see the support matrix. You can find both the Support Matrix (supportmatrix_en.html) and the Release Notes (releasenotes_en.html) at the root directory of the installation media.

Overview of this Version
Documentation Updates
Installation Guide and Support Matrix
Licensing
Upgrading
Recovering from an upgrade failure
Known Problems, Limitations, and Workarounds
Potential Installation Issues
English Locale Only
Domain Name System (DNS) Configuration
HP Software Support
Legal Notices

Overview of this Version

Overview of the NNM iSPI NET diagnostics server 9.20 Release

Diagnostic flows are run by NNM iSPI NET during the lifecycle of management incidents. These diagnostic flows automate the gathering and analysis of information from network devices. Diagnostic flows log into network devices using SSH or Telnet and run a series of commands defined in the flow. These commands extract troubleshooting information from specified network devices. Diagnostic flows can be run automatically when incidents are registered or manually by the operator against a node or incident.

The NNM iSPI NET diagnostics server consists of an embedded version (9.00) of HP Operations Orchestration (HP OO) and the MySQL relational database.

For a detailed overview of NNM iSPI NET diagnostics server 9.20, see Introducing HP NNM iSPI Network Engineering Toolset Software in the Planning and Installation Guide (see Installation Guide and Support Matrix).

Documentation Updates

The complete documentation set is available on the HP Product Manuals web site at h20230.www2.hp.com/selfsolve/manuals. Choose the "network node manager SPI for NET" product, "9.20" product version, and the Windows operating system.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

Installation Guide and Support Matrix

Installation requirements, as well as instructions for installing NNM iSPI NET diagnostics server, are documented in the installation guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's installation media as install-guide_en.pdf.

For a list of supported hardware platforms, operating systems, and databases, see the Support Matrix.

Licensing

NNMi installs with an instant-on license for NNM iSPI NET that is valid for 60 days. After 60 days, the NNM iSPI NET diagnostic flows are no longer run if you do not obtain a permanent license. To view information about your NNM iSPI NET license, open the NNMi console and select Help → System Information. From the NNMi informational window, select View Licensing Information.

For information about installing and managing licenses, see the Installation Guide.

New Features in version 9.10

• The NNM iSPI NET 9.10 diagnostics server provides the nnmooflow.ovpl command for loading customer-defined HP OO flows into the set of available flows NNMi can run during incident processing. Customer-defined flows can be added to or removed from the NNMi management server.
• NNM iSPI NET 9.10 diagnostics server optionally installs x64-bit versions of MySQL and HP OO. These versions do not install on a 32-bit operating system as the only currently supported platform is Windows Server 2008 x64.

New Features in version 9.20

• The NNM iSPI NET 9.20 diagnostics server provides a new version of the embedded OO server (9.03.0001) , a new OO content release (9.00.06), and a hotfix (hf_142835) to provide updated browser support for more recent versions of Firefox and Internet Explorer.
• LWSSO (Light Weight Single Sign On) is now supported between NNMi and HP OO. The same users can log onto NNMi and have access to HP OO.Tthis feature requires HP OO external accounts to be configured in HP OO. Please see HP OO documentation for configuring external accounts. LWSSO must be configured using the same initialization string and the same domain name between NNMi and HP OO.
• HP OO 9.03 along with OO Content Release 9.00.06 now support the use of mixed case logon prompts when using the telnet protocol.

Upgrading from NNM iSPI NET diagnostics server version 9.10

Note: Upgrades from the 9.00 version of the iSPI-NET diagnostics server are not supported. You must uninstall MySQL and HP OO before reinstalling the 9.20 version.

The installation wizard (setup_x64.exe) provided with NNM iSPI NET diagnostics server will not upgrade the 9.10 embedded HP OO server to the 9.20 embedded HP OO server. The following manual upgrade procedure can be performed from the NNM iSPI NET diagnostics server 9.20 installation media.

1. With HP OO services running on your system, run the performOOupdates.bat command located on the installation media using the following syntax:

performOOupdates.bat [OO installation folder] [OO admin password] [OO https port] > %TEMP%\upgrade.log 2>&1

performOOupdates.bat "%ICONCLUDE_HOME%" password 8443 > %TEMP%\upgrade.log 2>&1

HP recommends you use "%ICONCLUDE_HOME% as the OO installation folder. If you supply your own path, do not include a trailing "\" in the OO installation folder path, as this will adversely affect upgrade processing.

The processing from this batch file will:

• install OO 9.03.0001
• install OO hotfix hf_142835
• install OO content 9.00.06
• recover all the OO keystores previously in use on your system that were replaced by the OO updates

Be patient while this batch file is running. It can take  60 minutes or longer if running from a DVD drive. Check the upgrade.log file in the %TEMP% for any errors. The log file will be important to troubleshoot any failures during the upgrade.

2. Run the setup_x64.exe command. Specify the required passwords used during the previous installation of HP OO. Also, specify the NNMi location, port, and system password information. Let this installer run to completion. This step will install updated diagnostics flows into the upgraded embedded OO server.
3. Modify the configuration %ICONCLUDE_HOME%\Central\conf\Central.properties file to make a final change to the OO configuration. The line containing

dharma.antisamy.defalt.policy=slashdot.xml

should be changed to

dharma.antisamy.defalt.policy=anythinggoes.xml

This change instructs HP OO to permit reports containing embedded html to be displayed and reverts HP OO to its prior behavior with version 9.00.

After making this change, stop and restart HP OO services

net stop RSJRAS
net stop RSCentral
net start RSCentral
net start RSJRAS

4. Optionally perform the following to address report id generation problems when using MySQL. This step is not required but will be helpful should HP OO experience a problem selecting a new new report id when a flow is run.

Very infrequently HP OO might experience a problem where new report id's are not being selected correctly when using MySQL. The following procedure installs a stored procedure into MySQL that corrects any problems each time MySQL is restarted. You must know the MySQL root password and the database name HP OO is using within MySQL. Before running the following commands make sure that C:\Program Files\MySQL\MySQL Server 5.1\bin or the bin folder from your MySQL installation is in your path.

net stop RSJRAS
net stop RSCentral
cd [iSPI-NET 9.20 dist folder]\Upgrade_9.03\resources
copy sp_reset_run_id.sql %TEMP%
cd %TEMP%

Edit %TEMP%\sp_reset_run_id.sql; then remove the first two lines from the file such that the first line is delimiter $$

Next run the command

mysql.exe --user=root --password=[rootpassword] --execute="show databases"

Note the response that indicates the available databases. Hopefully one is nnminet, the original default database name specified by the NNM iSPI NET diagnostics server 9.00 installer. Otherwise identify the database name used during the original installation.

Run the following mysqlcommand to add the stored procedure contained in the sp_reset_run_id.sql file.

mysql.exe --database=[nnminet] --user=root --password=[rootpassword] --execute="source sp_reset_run_id.sql;"

cd [iSPI-NET 9.20 dist folder]\Upgrade_9.03\resources

Copy the init.sql file to the MySQL installation directory. Typically this would be: C:\Program Files\MySQL\MySQL Server 5.1.

Modify the init.sql file to change database name from dharma to nnminet or use the database configured for OO which should be displayed after running the show databases command above

Add the following line to the end of the MySQL initialization file at MySQLINSTALLDIR\my.ini.

init-file=C:\Program Files\MySQL\MySQL Server 5.1\init.sql

Shutdown and Restart MySQL service

net stop MySQL
net start MySQL

Restart HP OO

net start RSCentral
net start RSJRAS

Recovering from an upgrade failure

While unlikely, it is possible that while running step number 1 above, the upgrade could fail. For example, suppose you provided an incorrect path to the installation location of HP OO. It is important to check the log file to which you redirected the output and verify that no failures occurred. You might rerun step number 1 to perform an upgrade again. Before rerunning the performOOupdates.bat command again you should verify that the HP OO keystores (%ICONCLUDE_HOME%\Central\conf\rc_keystore and %INCONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\ras_keystore.jks) both exist. If these files no longer exist you will need to perform the following manual steps after the next run of the performOOupdates.bat command.

• Remove the %ICONCLUDE_HOME%\Central\conf\nnmgenpas.cer file.
• Remove the %ICONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\nnmgenras.cer file.
• Copy the %ICONCLUDE_HOME%\Central\conf\rc_keystore.original file to the %ICONCLUDE_HOME%\Central\conf\rc_keystore file.
• Copy the %ICONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\ras_keystore.jks.original file to the %ICONCLUDE_HOME%\RAS\Java\Defalt\webapp\conf\ras_keystore.jks file.
• cd [iSPI-NET 9.20 dist folder]
• run adjustcerts.bat "%ICONCLUDE_HOME%" [fully qualified hostname]

for example, run adjustcerts.bat "%ICONCLUDE_HOME%" hostname.domain.com

After the adjustcerts.bat command completes, the nnmgenpas and the nnmgenras files will have been recreated and certificates will have been reset in the rc_keystore and ras_keystore.jks files. Continue with step 2 above.

Upgrading and Running with Full Standalone HP OO

In order to use a Full Standalone HP OO system it must be upgraded to the following minimum levels

• 9.03.0001
• hotfix hf_142835
• OO content 9.00.06
• Recover your keystores from the backups made during the upgrade to 9.03 per the upgrade release notes

You will find the appropriate patches for your HP OO server from HP software's online support self service web site or your HP OO support contact.

Note: The OO software upgrades provided on this iSPI-NET installation image have only been tested with a direct upgrade from the base HP OO 9.00 and not from any intermediary levels of OO and are designed to be used with the embedded OO version supplied with the NNMi 9.10 version of iSPI-NET. You should upgrade your full OO server to the software levels indicated above using the recommended installation procedures as identified by the HP Operations Orchestration support team.

Once at this level of OO software, make sure that the nnmgenpas.cer file has been created and matches the certificates used in HP OO. If you are installing for the first time on an HP OO installation you will need to create this file. If upgrading on from an existing installation on HP OO you just need to verify that the nnmgenpas.cer file matches the certificate used by HP OO Central after the upgrade steps have been completed. See Introducing HP NNM iSPI Network Engineering Toolset Software in the Planning and Installation Guide (see Installation Guide and Support Matrix).

Finally follow the instructions in this document starting with step #2 above (run setup_x64.exe) and complete through step #4 to finish the upgrade or complete the setup on a full HP OO system.

Known Problems, Limitations, and Workarounds

• The NNM iSPI NET diagnostics server is initially configured using self-signed certificates. When browsers first connect to the server after installation, an invalid certificate message is displayed due to this configuration. You can continue to the HP OO web site by selecting the appropriate link, depending on your browser type. To alleviate this condition, the HP OO PAS certificate needs to be signed by a valid Certificate Authority. After NNM iSPI NET diagnostics server installation is complete, generate a Certificate Signing Request for the HP OO PAS certificate, and submit the request to your preferred Certificate Authority. After a new certificate is returned by the Certificate Authority, this certificate can be imported back to the PAS keystore (rc_keystore). If the Certificate Authority you utilize is already trusted by Java by default, no further action is needed. If the Certificate Authority you utilize is not trusted by Java by default, import the signed certificate to the NNMi truststore again. Consult the Installation Guide for details on this process.
• The NNM iSPI NET diagnostics server is not supported for use in High Availability (HA) or NNMi application failover implementations. The NNM iSPI NET diagnostics server must be installed on a system separate from the multiple nodes participating in an HA model. Each node in an HA implementation can be bound to the single separate NNM iSPI NET diagnostics server and can dispatch requests to this node.
• The NNM iSPI NET diagnostics server is not supported for use in cluster configurations as provided in the standard HP Operations Orchestration product. The full HP Operations Orchestration product must be purchased and used if you want to facilitate clustering as supported in this implementation.
• When you click on the results link in the Diagnostics tab of a node or incident and the diagnostics flow result is no longer available in the NNM iSPI NET diagnostics server (or HP OO), the following message is displayed in the browser: "Dhamra.dhamra.reports.individual.cannot_find_repair_history[1]". This message indicates that the records in the HP OO database have been removed. This situation can occur if the NNM iSPI NET diagnostics server is reinstalled, if the supporting MySQL database is reinitialized, or if the supporting MySQL database records have been removed.
• When implementing the use of customer-defined HP OO flows in NNMi, only incidents which have a Source Object bound to the incident are able to invoke flows. You can determine if a Source Object is bound to an incident by looking at the Source Object column when viewing incidents or by opening the incident and checking the Source Object field. A value of "None" indicates the incident is not bound to a Source Object. If you manually attempt to run diagnostics from the incident form, the following error message will be displayed: "Invoke of service com.hp.ov.nms.events:name=Rba method submitIncidentsForFlowExecution for ids:[nnnnn] failed: javax.management.RuntimeMBeanException caused by java.lang.NullPointerException".

Potential Installation Issues

• NNMi iSPI NET 9.20 diagnostics server provides two installation commands:

  • Use setup_x64.exe to install the NNM iSPI NET diagnostics server on an x64 Windows 2008 Server or to install only the NNM iSPI NET diagnostic flows into an existing HP OO server on a 64-bit system.
  • Use the 32-bit file setup.exe to install diagnostic flows on an existing 32-bit HP OO version. The 32-bit setup.exe quits when run on a x64 system or if HP OO is not installed on the local system.
• Loading NNMi flows into the embedded HP OO 9.03 server can take upwards of 60 minutes. The installation process, as noted below, reconfigures the embedded HP OO server with new SSL certificates, which requires a stop and restart of the HP OO RSCentral service. The initial stop of the RSCentral Windows service might take 10 minutes with a Java process showing 100% CPU load. The service eventually stops and the installation completes. Please be patient during this processing.
• The NNM iSPI NET Server uses the following ports for its processes by default:
  • HP OO Central: 8080 and 8443
  • HP OO RAS: 9004
  • MySQL: 3306

  Ensure that these ports are not in use prior to NNM iSPI NET diagnostics server installation. The installer verifies that ports 8080 and 8443 are available for HP OO Central. If these ports are not available, the installer requires that you change the port numbers before proceeding with the installation.

• The NNM iSPI NET diagnostics server installer requires an HTTP connection to the NNMi management server. If you have disabled HTTP on the NNMi management server, you will need to re-enable HTTP before running the NNM iSPI NET diagnostics server installer.
• The NNM iSPI NET diagnostics server installer cannot run from a UNC based path. The installer must run from the local file system.
• Certificates are exchanged to the NNMi management server from the HP OO server, which permit the NNMi management server to communicate with HP OO. The default self-signed certificates, installed by HP OO, do not provide adequate security for transfer of device usernames and passwords. Consequently, the original certificates are replaced with self-signed certificates by the NNM iSPI NET diagnostics server installer. By default, these new certificates use the hostname identified by the Java virtual machine. It is important that the hostname stamped in these certificates, which identifies the HP OO system, matches the hostname known by NNMi for the HP OO system. If both systems use the same DNS server, this should be the case. You can confirm the hostname by logging into the NNMi management server and pinging the hostname identified in the NNM iSPI NET diagnostics server installer. Make sure to use the hostname by which the NNMi management server identifies that target HP OO system in the certificate. More information is available in the Installation Guide.
• The NNM iSPI NET diagnostics server installer adds several components to the system: .NET if not installed, MySQL (version 5.1.30), and HP OO. The installer makes decisions based on what it finds on the system.
  • HP OO requires .NET Framework 2.0 Service Pack 1 and either 3.0 or 3.5 SP1 with ASP.NET enabled. On Windows Server 2008, .NET Framework 3.5.1 must be added using "Server Manager" and can't be installed via the iSPI NET diagnostics server installer. The iSPI NET diagnostics server installer will report the error ".NET V3 Framework Not Installed. Exit Code: 5100" if it tries to install the .NET V3 framework and the system is not yet properly configured. To fix this start "Server Manager". Click on "Features". Select ".NET Framework 3.5.1" and install this feature. You may be prompted to add other required Roles as well. Once .NET Framework 3.5.1 is added as a feature to the system, you can rerun the iSPI NET diagnostics server installer and it will detect that .NET Framework 3.5.1 is now installed.
  • If HP OO already exists on the system, HP OO, MySQL, and .NET are not installed. In this case, only the NNM iSPI NET diagnostic flows are loaded in the existing HP OO, and the installer binds this system to the specified NNMi management server. In order to accomplish binding to the NNMi management server, the HP OO system's certificates must be inspected and possibly changed to provide a proper hostname within the certificate. See the Installation Guide for details on setting up proper certificates. If these manual steps are not followed, the installer reports an error when binding to the NNMi management server.
  • If HP OO does not exist on the system and MySQL does exist on the system, only the embedded version of HP OO is installed. The installer requires the input of the appropriate root level username and password for MySQL. The existing copy of MySQL is used by HP OO after installation. The version of MySQL must be 5.1.30 or later.
  • If HP OO and MySQL do not exist on the system, MySQL version 5.1.30 is installed first. HP OO is installed next, and it uses the new installation of MySQL. An existing remote installation of MySQL can also be configured with the installer. Remote MySQL instances must allow root access from remote nodes.
• If MySQL was previously installed on your system, remove all MySQL folders and databases left on the system after MySQL was uninstalled. Preexisting MySQL databases and configuration files negatively impact the installation of a new instance of MySQL.
• In certain situations you may have uninstalled HP OO and then wish to reinstall the NNMi SPI NET diagnostics server. After uninstalling HP OO several files will remain in the HP OO installation folders which will impact reinstallation of the NNM iSPI NET diagnostics server. Previous versions of the NNM iSPI NET diagnostics server installer would not detect this condition and reinstallation of the iSPI NET diagnostics server would fail to regenerate appropriate SSL certificates for use in HP OO and NNMi. Diagnostics flows would never properly be submitted to HP OO due to the use of invalid certificates. The 9.20 version of the NNM iSPI NET diagnostics server installer will detect this condition and will prompt the user to remove these files before proceeding. If the user answers no, the NNM iSPI NET diagnostics server installer will abort. If the user answers yes, the NNM iSPI NET diagnostics server installer will remove the prior configuration files before continuing.
• If a problem occurs during the HP OO installation step but after the database and user have been created, you can restart the installation using the Start Again button. Before you start the install again, you must change the selected MySQL database name. If you do not change the database name, the installation will fail again when it attempts to create the same database a second time.
• HP OO ships JRE version 1.6.0_18 and installs this for use by HP OO. A critical Java security patch should be applied to this version of the HP OO JRE.
  • If you are using the version of HP OO embedded in NNM iSPI NET, the NNM iSPI NET diagnostics server version 9.20 installer applies the FPUpdater patch to the HP OO JRE.
  • If you are using the full version of HP OO, you should apply the FPUpdater patch separately. Contact the HP OO team for instructions on patching the HP OO JRE.
  • Information about the Java security patch can be found at http://www.oracle.com/technetwork/java/javase/downloads/index.html and http://blogs.oracle.com/security/2011/02/security_alert_for_cve-2010-44.html.

English Locale Only

On non-English systems, the HP NNM iSPI NET diagnostics server runs in the English locale.

Domain Name System (DNS) Configuration Known Problems

Security as implemented using a certificate-based infrastructure relies heavily on a well-configured Domain Name System (DNS) to convert discovered IP addresses to hostnames. An improper configuration can result in NNMi being unable to dispatch requests to the HP OO system. See the Installation Guide for more details on proper hostname resolution of the HP NNM iSPI NET diagnostics server system by NNMi.

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

Legal Notices

© Copyright 2008-2012 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP 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.

The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

AMD is a trademark of Advanced Micro Devices, Inc.

Google™ is a trademark of Google Inc.

Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries.

Java™ is a U.S. trademark of Sun Microsystems, Inc.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.