May 2005
This document provides important information about Network Node Manager and Route Analytics Management System Integration Module (NNM and RAMS Integration Module), version 3.5. The information here may not be available elsewhere.
In This Version
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Errata
Verified Environments
Local Language Support
Support
Legal Notices
The following lists features which are new to version 3.5 of the NNM RAMS Integration Module. See the NNM RAMS Integration Module User Guide for details on these features.
This feature provides the ability to launch IGP and BGP reports from NNM dynamic views as well as the alarm browser. These reports provide near real time routing information provided by the RAMS appliance.
This feature gives users the ability to pinpoint OSPF router misconfigurations that can cause adjacency loss. This feature can be launched from a selected RAMS Adjacency Lost alarm in the alarm browser.
Previous version of the NNM RAMS Integration Module only integrated IGP Alarms with NNM Advanced Edition root cause analysis. This version includes support for BGP Alarms.
In order for this feature to be fully utilized BGP routes of the network being managed must be in Extended Topology of NNM Advanced Edition. In the past some NNM customers have chosen to put their BGP Routers in the netmon.noDiscover file. This was done to keep netmon (which does layer 3 discovery) from pulling routing tables from BGP routers. These tables can be quite large and some network device vendors algorithms for getting these tables, via SNMP, causes router CPU usage to balloon to 100 percent.
In the April 2005 NNM patch a configuration parameter was added to netmon so that routing tables will not be pulled from routers which are running BGP. This option can be turned on by adding "-k neverPullBGP=true" to the netmon lrf file. See the netmon man page for more information.
Users who want to use the BGP root cause feature should turn the neverPullBGP option on and remove the BGP routers from the netmon.noDiscover file.
The HP Proliant DL380 is now supported by RAMS Operating System 3.5.38R.
Instructions for installing the NNM and RAMS Integration Module from the CD media are documented in the NNM and RAMS Integration Module User's Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's CD media as:
./Docs/Integration/NNM_RAMS_integration.pdf
When you install the NNM and RAMS Integration Module, the user guides and release notes are copied to the
$OV_WWW/htdocs/$LANG/ (on UNIX) or %OV_WWW%\htdocs\%LANG%\ (on Windows) directory
on your NNM management station.
Updated versions of the SPI manuals and release notes are posted on the HP OpenView Product Manuals web site at http://ovweb.external.hp.com/lpe/doc_serv/. Please visit this site to obtain the latest versions of the documentation.
Before installing the NNM and RAMS Integration Module, make sure that your system meets the following minimum requirements:
Windows® 2000 users are required to have Windows Script 5.6.
Ensure that this prerequisite and its most recent patch (April 2005 or later) are installed on all systems in the management environment prior to installing the Integration Module. To download the patch, go to http://support.openview.hp.com and select Patch Downloads from the I want to go to drop down list. The patch ids of the required Consolidated Patch are as follows:
The event IDs for RAMS alarms have changed. Therefore it is recommended that users who are upgrading from earlier NNM RAMS Module releases remove all events from from the "Route Analytics Alarms" alarm category.
In the 3.5 version of the RAMS Integrations Module the severities of certain RAMS Alarms have changed. Upgrades will not include these changes. These changes can be incorporated into an upgrade by editing the trapd.conf file. The following table shows the default severity for each RAMS alarm.
|
Event |
Severity |
|---|---|
|
RAMS Adjacency Lost |
Major |
|
RAMS Adjacency Established |
Normal |
|
RAMS Route Change |
Major |
|
RAMS Adjacency Flap |
Minor |
|
RAMS Prefix Origination Change |
Warning |
|
RAMS Prefix Change |
Warning |
|
RAMS Routing Event |
Normal |
|
RAMS Excess Net Churn |
Major |
|
RAMS Peering Change |
Major |
|
RAMS Prefix Flap |
Minor |
|
RAMS BGP Prefix Drought |
Critical |
|
RAMS BGP Prefix Flood |
Major |
|
RAMS BGP Route Flap |
Critical |
|
RAMS BGP Lost Redundancy |
Major |
Users who are upgrading from earlier NNM RAMS Module release and do not have the latest consolidated NNM patch must run setupRAMS.ovpl after installing the patch and before upgrading to 3.5.
Users who forget to run setupRAMS.ovpl after the patch will find that the Extended Topology Configuration GUI will no longer run properly. This is due to the fact that the $OV_CONF/$LANG/etconfig_ext.xml file is missing a line. This XML file is used to govern the creation of the tabs (including RAMS) in the Extended Topology Config GUI.
One of the tags in this XML file is a
The contents of a correct file are displayed below, with the missing line
shown in red. Once this line is restored, the ET Config GUI will function
correctly.
<?xml version='1.0' encoding='utf-8'?>
<EXTENSIBILITY>
<Tab Id="RAMS">
<Name>RAMS</Name>
<ClassForName>com.hp.ov.dynamicViews.servlets.rex.RAMSConfigHTML</ClassForName>
<NumberSectionsUsed>1</NumberSectionsUsed>
<Onload>RAMS_onload();</Onload>
<Javascript>RAMS.js</Javascript>
</Tab>
</EXTENSIBILITY>
The time/date entry fields in these views now have a drop down calendar which can be used to enter a data and time. The slider for the adjusted time entry in the RAMS Path History View has also been replaced by a time/date entry field. This allows users to select any time/date with out the restriction of the minimum and maximum values allowed by the previous slider.
Currently the "Neighbor View" action in the alarm browser does not display the correct source node for RAMS alarms. To correct this problem a new "RAMS Neighbor" action was added to launch a neighbor view from a RAMS alarm.
The launching of the "RAMS Path History View" from the alarm browser has been changed so that it properly fills in the "Source Node" and "Destination Node" fields from a RAMS Route Change alarm.
The latest release of the RAMS operating system is required for this version of the NNM and RAMS Integration Module (available on the NNM SPIs 9.0 CD media). The supported RAMS operating system version is 3.5.38R.
You can download the latest RAMS operating system in one of two ways:
System Update tab, and click Check For Update. Note that if internet access is controlled by a proxy server you will need to select the Use Proxy checkbox and enter the information for your proxy server. The key for this release is update. mckinley.external.hp.com, go to the rams directory, set binary transfer mode, and get the file named ramsOS-0.2.36-2.5.97-R.update . After ftp’ing the package, access the RAMS administrative interface, and select the System Update tab. In the field labeled URL , enter the ftp path to your internal ftp server. For example, ftp://myserver.com/pub/ramsOS-0.5.18-3.5.38-R.update. In the field labeled Key, enter the value
grizzly. Workaround:
ovstop, as well as any other OpenView product processes.\newconfig\OVWWW-FW\setupIIS.vbs from NNM 7.5 disk #1.A network which contains OSPF or ISIS routers that are not in DNS can cause slow Dynamic View performance due to DNS timeouts. To improve performance add *.*.*.* to the $OV_CONF/ipnolookup.conf file (create the file if it does not exist). ovstop and ovstart is required after creating or editing the file.
RAMS requires a key be configured on all tunnel interfaces.
Any differences in perceived current time between a client (a machine running either the RAMS IGP View or Path History View), NNM and the RAMS appliance can affect the data displayed in the RAMS IGP and Path History views. Clock differences can lead, for example, to the IGP View asking the RAMS appliance for data which, from the appliance’s point of view, is in the future!
HP strongly recommends that all systems in a RAMS installation synchronize clocks with an NTP server or other appropriate Internet time service.
Verify that RAMS has been enabled through the customary menu-driven NNM plug-in installation and configuration procedure. You can safely run the installation multiple times as you find and fix any problems which might have prevented the installation from finishing.
Correct configuration in the RAMS tab of the Extended Topology Configuration GUI is critical for the Integration Module to successfully communicate with a RAMS appliance. You must enter a valid RAMS IP address or DNS hostname, the RAMS query password, and the RAMS database name (also known as Administrative Domain). The RAMS database name is case sensitive.
If you are unable to launch RAMS dynamic views after applying RAMS configuration changes in the Extended Topology Configuration GUI, you can use the RAMS-to-NNM topology seeding tool to test whether NNM can communicate with the RAMS appliance. If the topology tool works as expected, there is likely a problem with Dynamic Views and not the RAMS appliance itself.
See the OVRams2NNM.ovpl.README file in $OV_CONTRIB (Unix) or %OV_CONTRIB% (Windows) for details about this tool.
If you are experiencing unexpected behavior in either the RAMS IGP View or Path History View, first verify that all RAMS settings in the Extended Topology Configuration GUI are correct. If they are correct, you can use the RAMS appliance’s native interfaces to verify the operational stability of the appliance itself. Some basic tests include the following activities:
Under certain conditions a report may return a "NO RAMS appliance connectivity" error. This can occur when multiple reports are launched concurrently. If the page is refreshed then the report will appear correctly.
A "Unable to retrieve router ID from Extended Topology" error while launching reports may indicate that the Extended Topology database is not synchronized with the topology database on the RAMS appliance. The RAMS Integration Module should automatically synchronize the data. In cases where it has not the following command will synchronize the data and should fix this issue.
$OV_BIN/OVRams2NNM.ovpl -populate
The event object IDs for RAMS alarms are not correct in non-english trapd.conf files. The work around is to edit the file and do a global search and replace of ".1.3.6.1.4.1.8083.1.1.7." with ".1.3.6.1.4.1.8083.1.1.9.".
The protocol diagnosis feature is not currently supported on non-english systems.
Currently no fixes.
The NNM and RAMS Integration Module is supported in a high availability environment. To setup the high availability environment, install and configure the NNM and RAMS Integration Module on both the active and standby server systems. Please contact HP technical support for specific configuration needs.
Please visit the HP OpenView support web site at:
http://www.hp.com/managementsoftware/support
This web site provides contact information and details about the products, services, and support that HP OpenView offers.
HP OpenView 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 valuable support customer, you can benefit by being able to:
NOTE: Most of the support areas require that you register as an HP Passport user and log 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://www.managementsoftware.hp.com/passport-registration.html
To view release notes and other documentation:
The product manuals search window opens. It is located at:
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 URL:
©Copyright 2005 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
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.