This text was hidden. Now it is visible. Click the link to hide the text.
This document provides important information about the Route Analytics Management System (RAMS) version 8.10 and the Traffic Analysis Add-On version 8.10. The information here may not be available elsewhere.
The product version in this release is 8.10. The appliance software version is 6.5.
In This Version
Known Problems, Limitations, and Workarounds
Fixes and Enhancements
To simplify navigation, individual Enhancement and Fix items are hidden until you click the link to expand the collapsed text.
Hidden text example
This text was hidden. Now it is visible. Click the link to hide the text.
Hidden text does not print. To print this document, you can expand selected links before you print or click the Show All button to expand all links. If you use Assistive Technology Tools, activate the Show All button to display all text.
Route Analytics Management System 8.10
RAMS 8.10 includes the following major, new features:
This release adds three significant enhancements to the VPN Traffic feature introduced in the 8.01 release. VPN Traffic provides comprehensive network-wide visibility within an MPLS core to traffic by Customer, by CoS, by Source and/or Destination PE, and by Application group. A rich set of analytic tools and reports help the Network Engineer and Network operator to monitor, analyze, and manage the MPLS core infrastructure. The operator can also set alerts based on various traffic conditions such as aggregate volume, traffic by CoS, etc., and be notified when such conditions are met.
The following enhancements for VPN Traffic are added in the 8.10 release:
Service Providers would like to provide "usage" reports to their key customers periodically either as a paid service or simply for informational purposes.
In this release, we provide an additional reporting capability that allows the Service Provider to generate reports for their enterprise customers. The data for the reports is obtained via the XML RPC APIs. The Service Provider can select up to 100 of their enterprise customers for whom the report data will be generated. The Service Provider can then extract the reports via the API and present them to their customers via a reports portal. The VPN Customer Reports license needs to be installed in order to use this feature. After installation of the VPN Customer Reports license, it is likely that the query server might not work for the VPN Customer Report APIs. Hence, it is recommended that the Modeling Engine be rebooted in order to rectify this problem.
The following reports are available per customer:
As an adjunct to this release, a sample implementation of scripts that use the API to extract information and present them in a web portal is available. This sample implementation can be downloaded from: ftp://hpovrams.external.hp.com/rams/portal/vpnPortal.readme and ftp://hpovrams.external.hp.com/rams/portal/vpnPortal.tar. A Service Provider can use these scripts as an initial starting point to incorporate the VPN Traffic Customer Reports into the Service Provider's own portal.
This feature provides the ability to configure CoS groups that will track together both native IPv4 traffic and VPN traffic having a specified set of CoS code points. For IPv4, the code points can be interpreted either as DSCP or ToS; these can be grouped with EXP code points for VPN traffic. The CoS groups enable tracking traffic in MPLS-VPNs, in native IPv4, and as IPv4 traffic encapsulated in MPLS packets (but not in a VPN).
Reports are provided to display bit rate and utilization statistics for traffic in the CoS groups separately for IPv4 or VPN traffic, or as an aggregate.
This feature is in parallel with the previously available capability to define more detailed Traffic Groups based on a combination of protocols, ports and CoS.
This feature provides the ability to highlight top traffic changes across the entire network on a daily, weekly or monthly basis comparing the current interval to the previous one. The change is tracked for both average and 95th percentile of the following statistics:
In this release we provide an additional recorder to collect static network topology information from the routers using SNMP. The list of routers that will be queried by this recorder is constructed by the RAMS appliance from its knowledge about routers participating in IGPs or BGP. The list may be filtered by user configuration.
The information collected includes router names, software versions, interfaces (type, address and speed), and optionally, static routes. This information was available previously for EIGRP networks but not OSPF or ISIS. Now the information collected with SNMP is presented in the same manner as it was for EIGRP in the various GUI reports and in the node and link info panels on the topology map. The interface speed is used to automatically determine link capacity for traffic utilization calculations.
Links are created between routers having interfaces with matching prefixes so that network areas connected only by static routing will become connected on the map.
The SNMP collector will query routers periodically with a period specified by the user so that the recorder will not place an inappropriate load to the routers that it queries. SNMP v2 or v3 can be used to query the routers. The SNMP v2 community strings and the SNMP v3 profiles are configured by the user.
In a distributed RAMS deployment, multiple SNMP collectors can be configured to query the separate areas of the network.
The following information is important for RAMS or the Traffic Analysis Add-on installation and deployment:
The following information is important for RAMS Traffic Analysis Add-on installation and deployment:
Before installing RAMS or Traffic Analysis, make sure that your system meets the following minimum requirements:
Supported Hardware Platform in descending list of preference:
NOTE: Starting with the release of RAMS 8.01, the hardware component requirements specified in the RAMS 8.01/RAMS 8.10 Support matrix must be adhered. Problems related to inadequate hardware configuration which do not follow the recommended guidelines will not be supported.
IMPORTANT: Consider your disk space requirements and fault tolerance needs and ensure that all available physical drives are installed before powering up the HP ProLiant server for the first time.
Starting with the RAMS 8.01 release, the Flow Collector is only supported on a DL 380 G5 hardware platform. RAMS will require two logical drives be configured for a Flow Collector unit - the first logical drive must be set at RAID 1 + 0, the second logical drive set at RAID 0. If you have an existing Flow Collector unit running a pre-6.1 software version, you must re-configure the server with two logical volumes and install the 6.1 software version from a CD image. Failing to do so can cause unexpected behavior. Cases reported as such will not be supported.
When using a DL 380 G5 hardware platform as the Flow Collector unit, it is required that the HP RAMS Flow Collector HiCap SW LTU license be purchased and installed.
For all non-Flow Collector units, RAMS will only utilize a single logical drive as configured on the ProLiant DL380/360 hardware; this means any extra physical disks configured in a second logical drive will be not be recognized by RAMS.
For detailed steps to configure a RAMS 8.10 Flow Collector, it is recommended that you use a HP Proliant SmartStart CD (shipped with the server). The SmartStart CD provides a more comprehensive Array Configuration Utility interface. Please refer to instructions in the RAMS Appliance Setup Guide.
The following describes a quick way to configure a single logical drive.
During the initial power-up of a new server, an auto-configuration process uses all of the physical drives on the HP Smart Array controller to set up a single logical drive. The default RAID (fault tolerance) level used for the logical drive depends on the number of physical drives as listed below:
* The available disk space is ~5% less than the disk's reported size. Every physical drive in an array will have the usable capacity of the smallest drive in the array.
NOTE: Multiple drives configured as a RAID 0 striped set will provide maximum disk space but will NOT provide any fault tolerance. If you install more than one drive intended for maximum disk space usage, i.e., not for fault tolerance, you MUST configure to use RAID 0 or the hardware will default to RAID 1 +0.
During the initial hardware boot sequence, you have the opportunity to accept the default logical drive configuration as shown above, or you can create the logical drive based on your drive space and fault tolerance needs. Watch for the following message during the boot process:
Slot 0 HP Smart Array Controller
Press <F8> to run the Option ROM Configuration for Arrays Utility
Press <F7> to Accept the default configuration - 2 drives in RAID 1 +0
Refer to the HP Smart Array Controller Reference Guide for configuration options and details.
IMPORTANT: Make sure the logical drive is configured as needed before installing RAMS. Any changes to the logical drive configuration, e.g., adding drives or changing the RAID level, will require a reload of the RAMS software and a restore (from backup) of the RAMS configuration and databases.
This requires the deletion and recreation of the logical drive. The steps to perform that are detailed below:
Slot 0 HP Smart Array Controller
Press < F8 > to run the Option ROM Configuration for Arrays Utility
Press < F7 > to Accept the default configuration - 2 drives in RAID 1 +0
At this point,
Following are selected fixes and enhancements since RAMS 8.01 (Appliance version 6.1.19-R) release.
A downloadable demonstration of the VPN Portal is available at ftp://hpovrams.external.hp.com/rams/portal/vpnPortal.tar. The installation instructions for the demo is available at ftp://hpovrams.external.hp.com/rams/portal/vpnPortal.readme.
Visit the HP Software web site at: http://www.hp.com/go/software
This web site provides contact information and details about the products, services, and support that HP OpenView offers.
You can also go directly to the HP Software Support web site at: http://www.hp.com/go/hpsoftwaresupport
HP Software Support Online 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://support.openview.hp.com/access_level.jsp
To register for an HP Passport ID, go to the following URL: https://passport2.hp.com/hpp/newuser.do
To view release notes and other documentation, go to the following URL: 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 URL: http://www.adobe.com/
© Copyright 2008 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.
The full acknowledgement for open source software components included in the RAMS and Traffic Analysis-Add on product can be obtained by opening the "About HP Route Analytics Management System" link under the Help menu in the RAMS GUI. The "Click Here" link from the "About HP Route Analytics Management System" page also provides information and agreement on the provision of source code for the mentioned software components.
The full acknowledgement for open source software components included in the RAMS and Traffic Analysis-Add on product can also be obtained from the document server at http://h20230.www2.hp.com/selfsolve/manuals. The document containing the license information is RAMS8.10_OpenSourceLicense.pdf.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
© 2007–2008 Hewlett-Packard Development Company, L.P.