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

The following is an example:

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:

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.

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

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

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

Potential Installation Issues

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:

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

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

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.

NOTE: For information about third-party license agreements, see the license-agreements directory on the product media.

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

New Features in version 9.20

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

The following is an example:

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:

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.

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

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

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

Potential Installation Issues

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:

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

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

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.

NOTE: For information about third-party license agreements, see the license-agreements directory on the NNMi product DVD-ROM.