HP NNM Smart Plug-in for LAN/WAN Edge

for the HP-UX, Linux, Solaris, and Windows operating system

Release Notes

Software version: 7.53 / June 2008

This document provides an overview of the changes made to the HP Network Node Manager Smart Plug-in for LAN/WAN Edge for the 7.53 release. It contains important information not included in the manuals or in online help.

In This Version
Documentation Updates
Installation Notes
Known Problems, Limitations, and Workarounds
Documentation Errata
Verified Environments
Support
Legal Notices

In This Version

This release of the LAN/WAN Edge Smart Plug-in (SPI) adds support for the board down and connection down events generated by the active problem analyzer (APA) functionality of Network Node Manager (NNM).

NNM 7.53 is required for the installation of LAN/WAN Edge SPI 7.53.

Documentation Updates

The first page of this release notes document contains the following identifying information:

Version number, which indicates the software version.
Publish date, which changes each time the document is updated.

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

In the Product list, click the product name.
In the Version list, click the version number.
In the OS list, click the OS type.
In the document list, click the document title.
To retrieve the document, click Open or Download.

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 Notes

Installation requirements, as well as instructions for installing NNM SPI for LAN/WAN Edge, are documented in the HP Network Node Manager Smart Plug-in for LAN/WAN Edge, User Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's CD media as:

./Docs/SPIs/LanWanEdgeSPI.pdf

After installation the document can be found at:

$OV_WWW/htdocs/C/manuals/LanWanEdgeSPI.pdf (UNIX) or %OV_WWW%\htdocs\C\manuals\LanWanEdge_RelNotes.pdf (Windows)

Software and Hardware Requirements

Before installing LAN/WAN Edge SPI, 7.53, make sure that your system meets the following requirements:

Hardware

3 MB (Additional Hard Disk)

OS platform and compatibility

HP-UX 11.0, 11.11, 11iv2 on PA-RISC, Itanium, and 11iv3 on PA-RISC, Itanium
Solaris 8, 9, and 10
Linux Red Hat Enterprise Release 4
Microsoft Windows 2000 with Service Pack 4(Professional Edition, Server Edition, Advanced Server Edition)
Microsoft Windows 2003 operating system with Service Pack 2 ( Standard Edition, Enterprise Edition, Web Edition (Service Pack 1 only)
Microsoft Windows 2003 R2 (Standard Edition, Enterprise Edition)
Microsoft Windows XP with Service Pack 2

Software
- HP Network Node Manager Advanced Edition, version 7.53.
Required MIBs - The LAN/WAN Edge SPI requires the following MIBs
- RFC1315 or RFC2115. Note that the RFC2115 MIB is backwards compatible with the RFC1315 MIB.
- Cisco Frame Relay MIB ( CISCO-FRAME-RELAY-MIB.my)
- Cisco SMI MIB ( CISCO-SMI.my)

Installation Problems

Coexistence with the NNM Frame Relay SPI

Correlation of Avaya VoIP Monitoring Manager (VMM) traps must be disabled in the IP Telephony SPI in order for the IP Telephony SPI to coexist with the Frame Relay SPI.

The corrective action needed depends on which SPI is installed first.

If the Frame Relay SPI is installed first, IP Telephony SPI installation will report correlator store deployment errors if correlation of Avaya VMM traps is enabled during the IPT SPI installation. If Avaya VMM traps are not enabled, no manual workaround is necessary. Otherwise, VMM traps must be disabled to allow the Frame Relay SPI to function correctly:

$OV_BIN/ipt_config_vmm_trap_enrich_corr.ovpl -disable_corr_only

If the IP Telephony SPI is installed first with correlation of VMM traps enabled, Frame Relay SPI installation will report correlator store deployment errors. To use the Frame Relay SPI, correlation of VMM traps must be disabled:

$OV_BIN/ipt_config_vmm_trap_enrich_corr.ovpl -disable_corr_only

Known Problems, Limitations, and Workarounds

General Information

The LAN/WAN Edge SPI returns –1 for failed SNMP queries and displays the variables for which the operation failed. Failed SNMP queries are usually due to an invalid set community string setting or a call timeout.
The LAN/WAN Edge SPI works identically with either the 1315 Frame Relay MIB or the 2115 Frame Relay MIB. As the 2115 MIB is shipped with Network Node Manager, it may by the most convenient. However, if the 1315 MIB has been installed, the LAN/WAN Edge SPI will function with no change in operation.
If you are running OVPI 5.0 and the Frame Relay Report Pack 3.0, you have the ability to launch reports from within the object manager window of the Administration GUI and have them appear pre-populated with the data for the object you have selected. The Frame Relay Report Pack has three classes of objects: Device, Interface and Dlci. If you choose a Dlci object and attempt to launch a form or report, it will appear on the screen but will be empty. If you launch the same form or report using the Device or Interface object, it will be correctly populated.

Limitations

For DLCI status change due to IF down scenario, sysName, along with IFIndex ID (and, in the duplicate IP environment, Route Distinguisher), is used as a unique key to perform the correlation. If the SNMP call to retrieve the sysName fails, the event will not pass this rule and, therefore, will default to the PVC flapping scenario.
Some of the root cause analysis queries are Cisco DTE-dependent making the solution more tailored for a Cisco environment. Future releases should take care of these shortcomings.
For non-Cisco devices frame relay root cause analysis may not show remote destination information due to the query dependency on the Cisco frame relay MIB to retrieve sub-interface information.

DOS Command Windows Appear on the Windows Operating System

Certain events cause ECS to invoke a Perl script that evaluates the values of specified MIB variables. The Perl script calls an executable that displays about five DOS command windows in succession onto the NNM management station. The DOS command windows disappear as soon as the executable completes evaluation of the MIB variable values.

PMD Process Stops

There is a known problem in ECS on the Windows operating systems such that loading or unloading the LAN/WAN Edge SPI occasionally causes the PMD process to stop running. After installing the LAN/WAN Edge SPI and after loading or unloading the LAN/WAN Edge SPI, perform the following steps:

Verify the state of the PMD process by typing:
1. ovstatus –c
If the PMD process is not running, stop and restart all NNM processes by typing:
1. ovstop –c
2. ovstart –c

Root Cause Analysis Fails at High Alarm Rates

Root cause analysis performs SNMP queries with the devices to perform the correlation. These queries are invoked via an embedded Perl script. Because Perl scripts are interpreted at runtime, there could be some performance implications at a high alarm rate. In most cases, the failures are generally with the correlated count.

The ovframerelayload.ovpl Script Fails

If the ovframerelayload.ovpl script fails, ensure that the OV environment variables are set properly. If the problem persists, please contact HP support.

No Alarms appears in Frame Relay Category on Linux platfom

On Linux platform there might a case where there are no alarms in Frame Relay catagory and there are alarms indicating errors like:

Correlation error : Asynchronous function call/s had errors or timed out

This happens because genannoserv exited. Please refer to QXCR1000819320 for fix of this issue.

Documentation Errata

There are no known errors in the LAN/WAN Edge SPI documentation.

Verified Environments

The LAN/WAN Edge SPI has been verified to work in high availability environments. To setup the high availability environment, you must install and configure The LAN/WAN Edge SPI on both the active and standby management stations. Please contact HP technical support for specific configuration needs.

Support

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:

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, 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

Legal Notices

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.