The HP NNM iSPI Network Engineering Toolset (NNM iSPI NET) Server extends NNM's
powerful network management capabilities by providing additional troubleshooting
and diagnostic tools for network engineers.
For a list of supported hardware platforms, operating systems, and database,
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.
Diagnostic flows are executed by the 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 execute 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 iSPI NET Diagnostics Server consists of an embedded version (7.20) of HP Operations
Orchestration (HP OO) and the MySQL relational database.
NOTE: To view files in PDF format (*.pdf), Adobe Acrobat
Reader must be installed on your system. To download Adobe Acrobat Reader, visit
the Adobe web site at
www.adobe.com.
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.
When Network Node Manager is installed, an instant-on license for the iSPI NET
is installed. The iSPI NET instant-on license is valid for 30 days. After 30 days, the
iSPI NET diagnostic flows are no longer executed if you do not obtain a
permanent license. To view information about your NNM iSPI NET license, open the
NNMi console and select Help → About HP Network Node Manager i-series.
From the NNMi informational window, select View
Licensing Information.
For information about installing and managing licenses, see the
Installation Guide.
- 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 NNM's 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 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.
- On the Configuration Workspace > Communication Configuration Form > Default
Device Credentials tab, only one entry is allowed in the Default Device
Credentials table at this time. If you populate more than one row in this
table, the following error message displays when you attempt to save the
Communication Configuration form: "Save failed: An attribute value for this
item is not valid, e.g. a duplicate key value."
- The online help for device credentials notes that credential passwords
are displayed in normal text as they are typed and once entered will appear
as asterisks. This is incorrect. Credential passwords are always displayed as
a series of asterisks when they are typed by the user. To change
the password, you should still erase all of the asterisk characters in the
password field.
- The NNM iSPI NET Server uses the following ports for its processes:
- 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 installation.
- The NNM iSPI NET Installer cannot run from a UNC based path. The
installer must run from the local filesystem.
- Certificates are exchanged to the NNMi server from the HP OO Server,
which allow the NNMi 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
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 NNM 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
NNM system and executing a ping against the hostname identified in the iSPI NET
Server installer. Make sure to use the hostname by which the NNM system
identifies that target HP OO system in the certificate. More information is
available in the
Installation Guide.
- The NNM iSPI NET Server installer adds several components to the system:
.NET if not installed, MySQL (version 5.0.51b), and HP OO. The installer makes
decisions based on what it finds on the system.
- If HP OO already exists on the system, HP OO, MySQL, and .NET are not
installed. In this case, only the NNM Diagnostic flows are loaded in the
existing HP OO, and the installer binds this system to the specified NNM
system. In order to accomplish binding to the NNM system, 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 NNM system.
- 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.0.51b or later.
- If HP OO and MySQL do not exist on the system, MySQL version 5.0.51b 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, make sure to 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.
- 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.
- Note that HP NNM iSPI NET Diagnostics Server is not internationalized. All
content is displayed using the English locale.
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 NNM 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 Server system
by NNM.
Go to the HP Support web site:
www.hp.com/go/hpsoftwaresupport
HP Software online support provides an efficient way to access interactive
technical support tools. As a valued customer, you benefit by being able to do
the following:
- 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
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 and HP Passport, go to the
following URL:
support.openview.hp.com/new_access_levels.jsp
Warranty
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.
Restricted Rights Legend
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.
Copyright Notices
© Copyright 1990-2008 Hewlett-Packard
Development Company, L.P.
Trademark Notices
Java™ is a U.S. trademark of Sun Microsystems,
Inc.
Microsoft©, Windows© and Windows© XP are U.S. registered trademarks of
Microsoft Corporation.
MySQL is a registered trademark of MySQL AB in
the United States, the European Union and other countries.
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32
and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95
branded products.
UNIX© is a registered trademark of The Open Group.
NOTE: For information about third-party license agreements, see the
license-agreements directory on the NNM product DVD-ROM.