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.10 released in February, 2014.
For an overview of the NNM iSPI Network Engineering Toolset Software 9.10 released in
March 2011, see Part -II.
Software Version: 9.10 / 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
Known Problems, Limitations, and Workarounds
HP Software Support
Legal Notices
Overview of the NNM iSPI NET diagnostics server 9.10 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.10, see Introducing HP NNM
iSPI Network Engineering Toolset Software in the Planning and Installation Guide (see
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.
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.
The NNM iSPI NET 9.10 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.
- 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".
- 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.10 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.
On non-English systems, the HP NNM iSPI NET diagnostics server runs in 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 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.
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.
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.
© 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.10 released in March, 2011.
For an overview of the NNM iSPI Network Engineering Toolset Software 9.10 released in
February 2014, see Part -I.
Software Version: 9.10 / March 2011
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
Known Problems, Limitations, and Workarounds
Potential Installation Issues
English Locale Only
Domain Name System (DNS) Configuration
HP Software Support
Legal Notices
Overview of the NNM iSPI NET diagnostics server 9.10 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.10, see Introducing HP NNM
iSPI Network Engineering Toolset Software in the Planning and Installation Guide (see Installation Guide and Support Matrix).
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.10" 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 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.
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.
- 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.
- 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.
- 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."
- HP OO 9.00 and later require the use of non-mixed case logon prompts for the telnet protocol. For example, Cisco devices use a default telnet logon prompt of
Username: . If NNMi runs flows against a device that only supports the telnet protocol (that is, a device that does not support SSH), the flow might not run properly and might fail at the device logon step. This situation is probably due to the use of a mixed case device logon prompt. To work around this issue, change the logon prompt on the device to use all lowercase username: or configure the device to support the use of SSH.
- 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".
-
NNMi iSPI NET 9.10 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.00 server can take upwards of 10 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.10 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.
On non-English systems, the HP NNM iSPI NET diagnostics server runs in 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 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.
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.
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.
© Copyright 2008-2011 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.