This document provides an overview of the HP Network Node Manager i SPI for IP Multicast (iSPI for IP Multicast) for the 9.10 release. It contains important information not included in the manuals or in online help.
For a list of supported hardware platforms, operating systems, and database, see the support matrix. You can find both the Support Matrix and the Release Notes at the root directory of the installation media.
In This Version
Documentation Updates
Installation Notes
Known Problems, Limitations, and Workarounds
Documentation Errata
Support
Legal Notices
The iSPI for IP Multicast in conjunction with Network Node Manager, 9.10 provides real-time data that enables you to monitor the health of the multicast network. The iSPI for IP Multicast uses the properties of NNMi to gather the information and monitor the Multicast-enabled nodes, PIM interfaces, and multicast flows.
This release of the iSPI for IP Multicast includes the following new features:
NNMi 9.10 is required for the installation of iSPI for IP Multicast. The iSPI for IP Multicast, version 9.10 is supported with NNMi version 9.10.
Before you begin in iSPI for IP Multicast installation, follow these steps:
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition,
go to the following web site:
http://h20230.www2.hp.com/selfsolve/manuals
NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system.
To download Adobe Acrobat Reader, go to the following web site:
http://www.adobe.com
Installation requirements, as well as instructions for installing the iSPI for IP Multicast are documented in the installation guide provided in Adobe Acrobat (.pdf) format. The document is included on the iSPI for IP Multicast media kit, as: Mcast_install_guide_en.pdf.
Note: If you plan to upgrade iSPI for IP Multicast from version 9.00 to 9.10 on HP-UX platform, see NNMI Release Notes and perform the additional steps required for HP-UX platform before upgrading from version 9.00 to version 9.10.
mcastjboss - FAILED Unable to start process using start command.
ovspmd: Attempt to start HP OpenView services is complete or The LRF-specified stop command failed.
ovspmd: Could not successfully run the status command (ovstatus -c) for process mcastjboss
mcastjboss - FAILED The LRF-specified status command failed.
This problem might occur if there is a conflict in the port numbers. You can perform the following steps to resolve this problem:
If the listed steps do not resolve the problem, you might have to uninstall and install the iSPI for IP Multicast again.
Workaround:
This problem might occur if the mcastjboss fails to start due to installation issues, port conflicts, or authentication issues. You can perform the following steps to resolve this problem:
Check if the mcastjboss process is running as follows:
Using the ps command on HP-UX, Solaris, or Linux operating systems
Using the Task Manager on Microsoft Windows operating systems
Use the ovstart -c mcastjboss, ovstop -c mcastjboss, and ovstatus - c commands to verify the problem.
Verify the jbossServer.log file present at the following location %NNMDataDir%\log\multicast for any entry specified as ROOT CAUSE in the deployment of Java MBeans. Also, make sure that there are no port-related exceptions in the log file.
Verify the spiOvspmd.log file present in the multicast log folder for any authentication problem logged while running the twiddle commands to start the mcastjboss process. If you see any error messages in the log file from the following command: start, stop, and status for issues related to authentication or port numbers, you must update the proper user name and password using the encryptmulticastpassword.ovpl script and update the port numbers in the nms-multicast.ports.properties file and the nnm.extended.properties file present in the %NNMDataDir%\shared\conf\multicast directory.
Workaround:
This problem might occur due to a failure by the twiddle commands to start the mcastjboss process due to the high system resource usage. You can resolve this problem as follows:
Stop the mcastjboss process using the ovstop -c mcastjboss command and check for the shutdown complete message for the process in the jBossServer.log file to see if the process is stopped.
If you did not find the shutdown complete message for the process in the previous step, run the nmsmulticasthalt.ovpl to halt the mcastjboss process. Verify the jBossServer.log file to make sure that no instances of the process is still running. You can also check the Task Manager (for Microsoft Windows operating systems) and use the ps command on the HP-UX, Solaris, or Linux operating systems to verify that there are no instances of the mcastjboss process running.
If you are unable to stop the mcastjboss process with the steps listed, you can end the process as follows and then perform the step to start the process:
End the process from the Task Manager for Microsoft Windows operating systems
Kill the process using the kill <process_id> where <process_id> is the process ID of the Java instance for the mcastjboss process.
Run the ovstart -c mcastjboss command to start the mcastjboss process
Run the ovstatus -c command to confirm that the OVsPMD commands now use the current status of the mcastjboss process
Multiple instances of the mcastjboss process result in the mcastjboss process not working as expected.
Workaround:
This problem might occur when you restart all the processes including the NNMi processes after you encounter a FAILED state for the mcastjboss process. The ovstop command does not stop the underlying Java processes when you execute this command after encountering a FAILED state for the mcastjboss process. The ovstart command executed, creates another instance of the mcastjboss process, thus resulting in multiple mcastjboss processes. This causes port conflicts and the mcastjboss process does not work as expected. You can resolve this problem as follows:
Stop the mcastjboss process using the ovstop -c mcastjboss command and check for the shutdown complete message for the process in the jBossServer.log file to see if the process is stopped.
If you did not find the shutdown complete message for the process in the previous step, run the nmsmulticasthalt.ovpl halt the mcastjboss process. Verify the jBossServer.log file to make sure that no instances of the process is still running. You can also check the Task Manager (for Microsoft Windows operating systems) and use the ps command on the HP-UX, Solaris, or Linux operating systems to verify that there are no instances of the mcastjboss process running.
If you are unable to stop the mcastjboss process with the steps listed, you can end the process as follows and then perform the step to start the process:
End the process from the Task Manager for Microsoft Windows operating systems
Kill the process using the kill <process_id> where <process_id> is the process ID of the Java instance for the mcastjboss process.
Run the ovstart -c mcastjboss script to start the mcastjboss process
Run the ovstatus -c command to confirm that the OVsPMD commands now use the current status of the mcastjboss process.
Workaround:
Wait till the mcastjboss initialization is complete. This exception occurs if you start the Multicast views immediately after you start the Multicast process.
Workaround:
Install any available PDF reader to read the document. The document is included on the product's installation media as: Multicast_install_guide_en.pdf.
Workaround:
The iSPI for IP Multicast log files are available on the local disk on each server in the cluster environment.
Workaround:
You can know the actual status of the interface through the analysis pane or the interface form.
Workaround:
Delete all existing Regional Manager connections and recreate the Regional Manager connections manually.
There are no known errors in the iSPI for IP Multicast documentation.
You can visit the HP Software Support web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP offers.
HP Software online 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 do the following:
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 the following URL:
http://www.hp.com/managementsoftware/access_level
To register for an HP Passport ID, go to the following URL:
http://h20229.www2.hp.com/passport-registration.html
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.
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. For information about third-party license agreements, see the license-agreements directory on the product installation media.
©Copyright 2008, 2010-2011 Hewlett-Packard Development Company, L.P.
Acrobat® is a trademark of Adobe Systems Incorporated.
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.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Programs delivered subject to the DOD FAR Supplement are ‘commercial computer software’ and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are ‘restricted computer software’ and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
For the full Oracle license text, see the license-agreements directory on the NNMi product DVD.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Portions Copyright © 1999-2003 The Apache Software Foundation. All rights reserved.
This product includes ASM Bytecode Manipulation Framework software developed by Institute National de Recherche en Informatique et Automatique (INRIA). Copyright © 2000-2005 INRIA, France Telecom. All Rights Reserved.
This product includes Commons Discovery software developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 2002-2008 The Apache Software Foundation. All Rights Reserved.
This product includes Netscape JavaScript Browser Detection Library software, Copyright © Netscape Communications 1999-2001
This product includes Xerces-J xml parser software developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 1999-2002 The Apache Software Foundation. All rights reserved.
This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). Xpp-3 Copyright © 2002 Extreme! Lab, Indiana University. All rights reserved.