This text was hidden. Now it is visible. Click the link to hide the text.

HP RAMS 9.21 includes the following major, new features:

• The G8 series HP Proliant servers support this version of RAMS.
• Support for IS-IS Multi-Topology Routing for IPv4 + IPv6
  Networks using RFC 5120 extensions to Intermediate System to Intermediate System (IS-IS) protocol for Multi-Topology (MT) Routing to provide both IPv4 and IPv6 routing in one domain are now supported. This support is limited to a single topology of each address family. When both address families are present, two protocol instances will be shown under the same label in the topology hierarchy, denoted as ISIS and ISIS/IPv6.
• Support for Huawei Router Software Versions 5.90, 5.100, 5.110
  The Collector recorder adds support for Huawei routers running software versions 5.90, 5.100 and 5.110 using CLI access methods to gather information for connected and static routes as well as RSVP-TE tunnels. This support extends the previous support for software versions 5.50, 5.60 and 5.70. Appendix B in the Administrator's Guide provides details about the accessed CLI commands. RAMS will periodically gather information from each router about the tunnel configuration.
• New Web User Interface and Web Reports
  This release adds a completely new Units page with a faster and more robust implementation of inter-unit communication for adding and deleting clients in a multi-unit system. The new Units page incorporates the operations such as shutdown and reboot that were previously on a separate page, and allows performing those operations on any of the units in the system while accessing the Units page on the master unit.

  • This release provides the first phase of a complete reimplementation of the web user interface using Web 2.0 technology. In this phase, the overall framework and navigation are new, and there is a new Reports tab that will eventually provide web access to all of the reports in the X/VNC GUI. There is also new online documentation accessed from a Help link in the page header and by "?" buttons that provide context-specific document access for some of the UI features.
  • This release includes 38 routing reports in three categories:
    • Current Time Reports show the status of routers, links, prefixes and paths
    • Comparison Reports show changes in the sets of routers, links and prefixes between two points in time
    • History Reports show the list of events, link flaps, prefix changes or path changes during an interval.
  • The server-side processing for these reports uses the same software functions that are part of the X/VNC GUI and have a similar set of controls on the report table including filter selection, expand and collapse of hierarchical data, and sorting on columns. Therefore users should be comfortable switching between the two user interfaces.
  • After the system has been configured and data recorded, the landing page of the new web UI provides a system status dashboard that combines the recorder status and network status displays of the X/VNC GUI. For each database in the topology hierarchy, two "LED" status indicators are shown to summarize the recorder status and network status.
  • Three pages in the Administration menu are new:
    • Traffic Configuration controls the upstream projection option discussed above.
    • Session Maintenance shows the list of users logged in on the web UI so an administrator can monitor usage and remove sessions if needed.
    • License is a new implementation, described next.
  • The Units page now displays information about the hardware model number, installed memory, and number of CPUs for each unit in the system. [13287]
  • The new Units page as shown on a client unit includes a Disassociate operation to unilaterally remove the unit as a client of its master unit so it can then be used stand-alone or added to a different master unit. [10767]
  • A client unit can now be deleted without first deleting the portions of the Recorder Configuration that are bound to it. A warning popup is displayed, but the user may elect to continue. This may be useful when replacing the unit hardware. [7494]
  • When the Dashboard tab of the new web UI is being generated, a progress register is now shown and not removed until the page is complete, so display of a blank white page is avoided. [19930]
  • On the master unit of a distributed system, the new License page can display the license of any of the units as selected by a row of tabs, rather than just its own license as in the old web UI. At the bottom of the license display is a button that toggles between a view of the aggregate license for the unit considering features that it inherits from other units, and a view of the license features bound explicitly to that unit. In the latter mode, expired license terms will also be shown and highlighted in red.
  • Normally an administrator will perform all license installation and examination operations on the master unit. The new License page supports uploading a license file in either zip or text form as an alternative to pasting the license text into an entry box. When copy/paste is used, the new License page will tolerate blank lines between license lines. When a license for a client unit is installed, it will be automatically distributed to the client. This distribution of licenses is much faster with the new implementation. The License page is also present on a client unit if needed, but there it only displays the license for that client. If a license is mistakenly installed on the client unit rather than the master, it will be automatically copied to the master (assuming network communication between the two units is working).
  • The system checks for consistency of the aggregate license as stored on the client and on the master, and puts up a warning message if they differ. In that case a Reapply button appears and when clicked will replace the licenses on the client with those that are on the master.
  • The actions for removing licenses have changed. In the old web UI, there was a button labeled "Remove all licenses from this unit" that did what it said. On the new License page there is a Delete button on the tab for each unit's license. When that button is clicked on the tab of a client unit, all licenses are removed from the client unit and that unit's licenses are deleted from the master unit. If the button is clicked on the tab for the master unit, then the master unit's licenses are deleted from all units, but other units' licenses remain. There is a separate Delete Expired button that will just delete the expired licenses for the selected unit.

  
  In this release, most of the Administration functions and the Recorder Configuration still use the same Web 1.0 implementation as in previous releases, but as displayed within a pane that is part of the new web framework. Similarly, the Reports Portal pages of the old web UI are still available in this release on the Legacy Reports tab, but those reports are now deprecated. Some of them are already covered by equivalent reports available on the Reports tab, and others will be provided in a future release. The License page has improved checking of inconsistency between the licenses for a client as stored on the client and on the master unit.
• User Interface Enhancements
  In addition to the primary new features, this release incorporates several appearance improvements and functional enhancements to the X/VNC user interface, including the following:

  • In previous releases, some simple reports included a "Filter by:" bar at the top of the report window with a collection of drop-down and button controls, while other reports with more complicated navigation provided only an icon to bring up the Advanced Filter dialog. In this release, a new filter widget provides all the functionality of the filter bar in a more compact representation so it can fit in the header for all of the reports. The filter widget has preselected the most commonly used filter for each table so that users can apply the filter simply by entering the desired value and hitting Enter. Other filters can be selected from a drop-down at the left of the widget, including an option to open an improved advanced filter dialog that allows building any desired AND-OR hierarchy. The same filter widget is shown at the right-hand side of the report header in both the X/VNC GUI and the new web reports UI.
  • The main topology map, the mini-maps within reports, and all graphs can now be exported via email or saved to a file that can then be downloaded from the web UI. The supported file formats are JPEG, PNG, PDF or SVG. Exported graphics and reports can be sent to multiple email recipients. [18508, 18898]
  • The dialogs for Planning Mode operations such as Add Router, Add BGP Prefix, Down VRF, etc. have been reimplemented for a more consistent look and better choice of controls and sizing of elements within the panel. It is also possible now to add a BGP peering to a router that did not have a BGP instance before. [8987, 17962]
  • A new feature allows users to provide notations for routers on the map. Users can configure a description or other information along with a URL for each router using the XML RPC API, then that information will be displayed on a new info tab of the inspector panel that is shown on a right-click of the router node on the map. [18238, 19655]
    
  • On the List Links report, filters were added to select by source router or destination router explicitly, versus the existing Router filter that matched either source or destination. Filters were also added to the VPN status reports for the columns with counts of routes. [10168, 18218]
  • The bar charts available in the RIB Browser now have a label for the X axis. [16926]
  • For networks that record both IPv4 and IPv6, the Highlight By Exit Router dialog now includes a radio button to select which address family should be used. [19047]
  • In the RSVP-TE reports, when displaying a tunnel map, a secondary tunnel that is active is indicated by a double arrowhead.
  • In the List Routers, List Links, and List Prefixes reports, the context menu displayed by a right-click on a row in the report now includes options to add that element to a router, link or prefix group, respectively, or to remove it. The context menu has been added to the list of neighbor routers invoked from the node inspector panel as well. [13798, 13800]
  • The Network Summary panel on the main topology map now includes a filter icon that brings up a dialog for adding custom statistics for BGP based on a filter that the user specifies. This function was separated out of the Saved Filter dialog of previous releases where it was less convenient to access and made the dialog confusing. [17089]
  • Web administration UI. The Queries page now provides a Restart button to recover from problems with the Query Server daemon that require restarting. This is particularly useful on Route Recorder clients where the Query Server cannot be disabled. (If the Query Server crashes, it will be restarted automatically.) [15033]
  • All reports now can be exported in PDF format as an alternative to the CSV format that was available before. Graphs, bar charts and pie charts can also be exported in PDF or any of the formats SVG, PNG or JPEG. [19645]
  • A new option is provided in the GUI options dialog at Admin -> Options -> History Navigator to automatically dock the History Navigator at the bottom of the map window after Open Topology. [19405].
  • Several improvements to the traffic groups dialog make it easier to use:
    • In View mode, long fields wrap to multiple lines so the whole content is visible rather than being truncated on one line.
    • The search field was made wider so more input is visible.
    • Hovering the mouse over a group item on the left pane displays the traffic group contents in a tooltip.
  • In the Capacity Planning dialog, a drilldown icon was added as an alternative to the context menu on table rows, making it consistent with other views. The Trending button has also been replaced with an icon to better fit in the icon bar.
  • The List/Find Paths dialog will now accept any prefix or address as the specification of the source for the path, rather than just a router name or address. The best prefix containing the given prefix or address will be found using a longest match in the following priority order: IGP intra-area prefixes, static routes and connected routes; if empty,AS external IGP prefixes; if empty BGP prefixes. Paths will be found from all routers originating the selected prefix to the specified destination. [6146]
• System enhancements
  • RAMS and RAMS Traffic uses database replication between units to reduce topology loading time. The database system implements replication by writing "binary logs" on the unit that is providing the data so these can be streamed to the unit replicating the data. The logs consume three to four times the space than the data actually stored, so trimming them carefully is important. In this release, enhancements to the replication restart procedure allowed reducing the duration that the logs are kept from eight days to one. In addition, standalone units will no longer need to keep binary logs to be ready for incorporation into a distributed system. [19444]
  • This release includes a new alert for BGP Indirect Peering State changes. This complements the existing alert for Peering State that only applies to the direct peers of the recorder. For the indirect BGP peers, when the count of prefixes received through that peer (as indicated by NextHop or Originator attributes) drops to zero, an alert is issued for the Down state transition. When the number of prefixes received transitions from zero to non-zero, and alert is issued for the Up state transition. [14369]
  • Passwords kept in the recorder configuration for access to routers are now encrypted before being stored in the configuration database. [18301]
  • The Adjacency Down alert has been enhanced to optionally allow specifying a minimum amount of time that the adjacency must be down before the alert will be triggered. The threshold is included in the alerts sent in text form and as an additional varbind for SNMP. The adjacency down alert is unchanged if no minimum duration is specified. [17176]
  • The support information downloaded from the Downloads tab now includes status of replication servers and clients. It also includes the time zone setting for the unit. [19981, 20033]
  • In the "ping" diagnostic that is available on the serial console and via ssh to an account with CLI Access privilege level, options are now provided to set the DF (don't fragment) bit and to specify the size of the ICMP payload. Also, in parallel with the "telnet" diagnostic there is now an SSH diagnostic to test outbound ssh connections from the recorder to routers. [18375, 18329]
  • The user can now select any of the syslog facility values local0 through local7 to be assigned when sending RAMS log messages to a remote syslog collectors. The default is local1, which was previously the only value possible. [18492]
  • The daemon used by RAMS appliances to maintain the up/down status of the units has been eliminated, so TCP port 5897 is no longer required to be open in a firewall interposed between units. Unit status is now maintained using the new inter-process communication infrastructure based on HTTPS that has been developed for the new web user interface.
• Enhanced Traffic Groups, Traffic Reports, and Traffic Display
  • In earlier releases, traffic groups were organized in a linear priority list, and received traffic would be counted only in the first group that matched. In this release, the traffic groups can be organized into a tree, and the user can configure the matching process to stop at a matching group or continue down the branch so that the traffic can be counted in multiple dimensions (such as by source and by protocol). The same group definition can be inserted at multiple points in the tree.
  • To facilitate tracking regional traffic within a network, traffic groups can also be based on the router groups in a network topology layout rather than just grouping on NetFlow parameters. Similarly, a traffic group can now be based on a set of AS numbers to be monitored together. The expanded Traffic Groups feature is now accessed from the X/VNC GUI Administration menu.
  • As in previous releases, users can drill down from the top-level set of Traffic Reports to get a breakdown of the data in a row of the top-level report, such as exporting routers, according to another dimension, such as exit routers. The total space of possible reports is so large that the system cannot precompute reports aggregated over hourly, weekly, daily and monthly historical time intervals for all of those dimensions, so the drill-down reports could only show the basic 5-minute average data. In this release, users can drill down to a particular report of interest and save that as a custom history report. For each such report, the historical values will be precomputed for a selected subset of the rows (elements) in the report at the time it is saved, or for the top N elements in that report as the set of N varies over time. The system can accommodate a total of 100K elements over all the custom history reports and a total of 3000 traffic groups.
  • Traffic groups and custom history reports can also be configured using the XML RPC API rather than the GUI when that is more convenient.
  • One or more rows from a custom history report can also be displayed as a time-series graph in the same manner as rows of the top-level reports could be displayed before. In this release, the averaging interval of the data points in these graphs will be automatically selected among 5-minute, hour, day, or week for a clear presentation according to the selected graph time range rather than always using the 5-minute granularity that can be too noisy. When multiple rows are selected, they can be shown in a stacked graph so the total is easy to see.
  • Previous releases included a Neighbor AS report to show the distribution of traffic to downstream neighbors. This release provides a new Incoming Neighbor AS report to show from which neighbors traffic is arriving. That information is not available in NetFlow, but the BGP border routers are configured to export NetFlow traffic to the Flow Recorders and if the Collector is configured to gather interface information from the BGP border routers, then an additional query will be issued to those routers to learn what AS number corresponds to the neighbor on each interface where traffic is recorded. This enables the Incoming Neighbor AS report.
  • This release supports multi-AS IPv4 (non-VPN) traffic recording, and provides new reports for ingress, egress and transit for each AS. There are also new reports providing ingress, egress and total traffic for each router and for router groups that have been defined. RAMS and RAMS Traffic do yet support more than one AS in the MPLS VPN feature.
  • Collection of traffic flows is enhanced in two ways:
    • Support for IPFIX packet formats was added as an alternative to NetFlow. [19153]
    • The configuration of the Flow Recorder now allows specifying a list of interfaces on which the traffic should be ignored. This is useful for cases where there is insufficient information for deduplication to work correctly, so excluding the interface to an upstream router where traffic is also collected is desired. [15727, 18378]
  • Traffic projection across the topology is also improved in two ways. First, when the traffic flows over equal-cost multiple paths (ECMP), that traffic will now be divided evenly across all the paths rather than being all assigned to the first path as in previous releases. This is still not accurate for any particular flow because the routers select among the paths using hash algorithms that are unavailable to RAMS Traffic, but it avoids showing traffic that may exceed the link capacity. Support for BGP ECMP paths was also added. [19288]
  • Second, there is an option to enable upstream projection towards the source router for IPv4 (non-VPN) traffic to complement VPNv4 traffic where the ingress PE router is already known. This projection relies on a heuristic to identify the router that injected the prefix covering the source address in order to project the traffic downstream from that router. This heuristic will scale to enterprise environments where there are very few Internet peering points, but will not work in service provider networks where there are many Internet peering points and where prefixes can be injected from many points in the network. For multi-AS traffic recording, the upstream projection will not cross AS boundaries, so the flow must be recorded in the ingress AS in order to be counted correctly in the Local AS reports (Ingress, Transit, Egress).
    
• Compatibility Changes in XML RPC API
  • Previous releases included a long list of API calls for traffic. In this release, these are all deprecated and may be removed in a future release. They are replaced by two generic calls api_traffic_custom_reports and api_traffic_custom_reports_history. These new API calls take a parameter in XML format that specifies the report to be produced. Some of the deprecated calls will not deliver any results unless a custom history report is created so that the corresponding report will be generated by the Flow Analyzer. The Developer's Guide includes a note in the description for each of the API calls with that requirement.
  • The input parameters and output format for the api_traffic_list_flows call have changed. In 9.20, the call included a parameter specifying a list of exporting indexes to be reported. In 9.21, this has been generalized to take an XML specification of the desired traffic report for which the flows will be listed. In the resulting XML RPC output, the structure is now flat and the tag names have changed. See the Developer's Guide for details.
  • Two traffic API calls that were included on a temporary basis in the 9.20 release have been removed. These are api_traffic_src_nbr_matrix and api_traffic_src_dst_matrix. Instead, api_traffic_custom_reports should be used with the XML report specification the report to be either a drill-down from Source AS to Neighbor AS or from Source AS to Destination AS to produce the two matrices. In the resulting output, the tags names have changed. See the Developer's Guide for details.
    

Note: HP RAMS releases have supported both SSH version 1 and version 2 for X/ssh access to the user interface. Please note that SSH version 1 was deprecated in the HP RAMS 8.11 release and is removed from the HP RAMS 9.xx releases because it is considered a security risk.

• To avoid double counting traffic when a flow is recorded at multiple points in the network, RAMS Traffic implements duplicate suppression by stopping deployment of the first instance of the flow when it reaches the second recorder. If a traffic flow is collected in multiple points in a multi-AS network, this suppression may prevent an instance of the flow from crossing the AS boundaries. As a result, the Transit AS report would not include the flow that it otherwise should. [19640]
• The new web reports feature introduced in this release shares the Query Server daemon to hold the network model from which reports are produced. There can be contention between XML RPC API requests and web reports requests. If either side issues a request that takes a long time to service, requests from the other side will be delayed. The same is true for two API users or two web reports users. If a very complex query is issued, the processing may take longer than the timeout for the API client or the web reports application. In that case, an error will be indicated, and the user must wait for processing of the complex request to be completed and discarded before trying again. Customers can increase the API and web reports capacity by adding a secondary Modeling Engine. [19327, 19676]
• For those reports that include a filter on AS numbers, a 4-byte ASN must be entered in ASPLAIN notation (one 32-bit integer) rather than the ASDOT notation (two 16-bit integers separated by dot) as they are displayed in the application. [19380]
• A custom history report that drills down to Ingress VRF will incorrectly list Ingress PE instead. [19754]
• This release adds export of graphs and maps in addition to exporting reports in CSV format, but the reports that toggle between table and bar chart can only export the CSV. [19645]
• When the Collector recorder is configured to accept syslog messages, the syslog daemon may hit an infrequent crash. There is not yet any automatic mechanism to restart the daemon, so the system must rebooted or remote access for Technical Support must be enabled to manually restart the daemon. [17487]
• When using the RSVP-TE Planning feature to create tunnels, it is possible to create a large number of tunnels in a full mesh. If the number of tunnels and constraint options is too large, attempting to save the edits to the database will cause the GUI process to pop up an error message and then become stuck. [18093]
• After the Collector recorder has finished its topology exploration, its status may report some number of "possibly inaccessible" routers even though all routers were successfully queried. This count is the number of router addresses that were tried unsuccessfully, even though another address tried subsequently for the same router may have allowed a successful connection. [18216]
• In a report window with a tree of reports listed on the left, if the user accidentally moves the mouse while intending to click on one of the entries in the tree, the new entry will be selected, but the report won't change because the input is considered a mouse drag operation rather than a click operation, and the drag operation has no action associated. The workaround is to click again on the desired entry. [16430]
• In the 9.20 release, some of the tables and some of the inspector panels in the GUI will automatically update as time advances in Monitoring mode. Other tables and inspectors will retain their data and display a "reload" icon that must be clicked to see changes in the data. The plan for a future release is for all tables and inspectors to auto-update. [15134]
• Consolidation of router nodes on the map may be incorrect until the second Collector full exploration after starting a fresh database with BGP, IGP and Collector topologies all at once with the Start All Recording button. This problem can be avoided by starting recording individually for each of the protocols except Collector and waiting 15 minutes or so for the full BGP and IGP topologies be recorded. Then start Collector recording separately. Consolidation may also be incorrect if the same interface address is configured on more than one router. [15904]
• In the 8.0 and later releases, the limit on the size of copy/paste transfers from a GUI running inside a VNC session to the clipboard on the VNC client machine is 256KB, compared to a limit of 4MB in earlier releases. The smaller limit results from the 64-bit VNC server using a different method for the transfer. The 4MB limit may be restored in a future release. In addition, the new feature for exporting CSV-format files is an alternative. [4934, 13865]
• RAMS OSPF route calculation conforms to RFC2328 and assumes "RFC1583Compatibility" is disabled, so the path chosen from one ABR to another ABR in the same area will be within that area even if there is a lower-metric path through the backbone. Since some routers enable RFC 1583 compatibility by default, the actual path may differ. A future release will support a configuration option to enable RFC 1583 compatibility. [1897]
• In the RIB Comparison for an OSPF or ISIS domain, the number of down links reported in the table may be fewer than the number shown when the links are listed from the context menu. [12295]
• Path Reports for IPv6 networks will show that some paths are incomplete because to reach the destination requires IPv6 connected interface information. That information is not collected yet. [12452]
• In Traffic Reports -> Top Changes, the context menu on the drill-down button may not appear after sorting a column. The workaround is to select a cell from another column. [12506]
• In the XML RPC API, the method api_mp_list_paths requires the source address to be specified in the form of a prefix now; that is, with both an address and a mask. This is consistent with the specification in the Developer's Guide, but releases before 7.0 were more lenient and would accept just an address without the mask.
• Since release 6.0, the Recorder Configuration allows only a single top-level administrative domain to be created. Users who need multiple domains to configure different portions of their network should create one top-level domain and then subdomains under it. For existing configurations that already contain more than one top-level administrative domain, only the lexicographically first of those domains can have alerts configured. If a recorder client that already contains some configuration is added, that configuration will be pulled up to the master, possibly creating a new top-level domain. This might cause a problem if that new top-level domain comes lexicographically first.
• If a client unit fails and must be replaced, before adding the replacement unit as a client of the master unit, you must stop replication on the master unit. Then after adding the client, start replication again. This will rename the replicated database on the master and start replicating anew from the database on the replacement client.
  

In addition to the primary new features, HP RAMS 9.21 incorporates several appearance improvements and functional enhancements to the user interface, including the following:

Graphical User Interface

• For the MPLS WAN feature, a new configuration option in the VPN Connections Table allows specifying that all the CE routers have full-mesh reachability within the MPLS provider, rather than hub-and-spoke, even when the routes are filtered between the PE and CE to include only the regional summary prefixes that originate from the hub. [14676]
• When opening the Online Events Monitor, it is now possible to select multiple protocols to view their events merged together. [14722]
• In the Path Group dialog, the Edit button has been relabeled Copy since its function is to make a new group without deleting the old one. [14728]
• Bar charts, which are shown in the BGP RIB Browser and other reports, now have the X and Y axes labeled. [16926]
• The Combine Routers function, which can only be used when the full topology is opened, will now be included in the menu but disabled when a partial topology is opened, and a status bar message will be displayed for guidance that the full topology must be opened to use that function. [17287]
• The column configuration dialog for Traffic Reports now shows all the possible columns for the Difference Column option even if no Statistic Column selection has been made. [17939]
• When zooming the map, extra margins are now included and the display size is adjusted for the scrollbars so that the panner widget and nodes are not partially occluded. [18286]
• The internal/external status of a BGP peer was sometimes shown incorrectly in the GUI if the peer status was changed while the recording was running. Now that status change is tracked correctly. [18526]
• When multiple inspector panels are opened and pinned for a node or link on the map, their positions and tab selections will be maintained in Monitoring mode as updates are applied. [18742]
• The Routing Stability - Tunnel Changes report now omits tunnels that have no changes. [18941]
• In Event Analysis, the count of events shown in the distribution now includes meta-events, such as peering changes, so that the count matches the list of events shown on drill-down. [18956]
• An EIGRP router might be shown as up even through the last event for it was Drop Router. The calculation of the effective degree of the router was corrected so the state is now down. [19027]
• As a convenience, the Reports -> Redeploy Traffic menu item is enabled in Planning mode to have the same function as the sameitem in the Planning menu. In both cases, the flows after editing are projected across the network. [19109]
• In Path Reports, the total path delay was sometimes incorrect due to counting the delay of earlier hops in the path more than once. The calculation is now fixed.[19117]
• The GUI could crash when the map is displayed with containers (clouds) on the map if the underlying router groups were changed by another instance of the GUI or through the XML RPC API. This crash is now avoided. [19129]
• In Path Reports, Find Paths dialog, web reports and XML RPC API, when a path is incomplete, this is indicated more clearly indicated in the Cost to Prefix column and in status messages. [19141]
• If the Collector has recorded the status of a link as down, but an IGP indicates that the link is up, the IGP status will have precedence and the link will not be red. [19277]
• The GUI could crash if an item is selected from one router group and dropped into another router group. Interaction with the underlying graphics library was revised to fix this. [19333]
• A potential crash in processes that load the network model is avoided by checking whether creation of a NextHop node failed because it is in an AS in the same confederation AS with the same IGP. [19418]
• The GUI could crash when attempting to delete a VPN customer RT mapping if the mapping belonged to a different topology. Now only those mappings belonging to the specific topology are shown. [19567]
• In some cases, when editing a traffic group and attempting to add another filter field, two fields would be added rather than one. Now only one is added where expected. [19756]
• The contents of a traffic group with "Include if Any Match" operation that was further indented and then saved would not be displayed correctly after reloading of groups browser.This is now fixed. [19760]
• In traffic drill-down reports, if no column other than "Current" was configured, no statistic column would be shown. Now the 5-minute average column will be shown in that case. [19872]
• Applying a filter on the Administration -> Assign Names -> Routers dialog sometimes had no effect, but now it shows the desired filtered list. On a unit that has multiple top-level labels being recorded (this is unusual), and no router names saved for that network, attempting to save names would always fail, but now it will work as expected. [19807, 19655]
• When selecting the name to display for a router that has multiple protocol instances, any instance that is down and timed-out willhave lower priority than those that are not timed out. [19862]
• In the History Navigator, the "start fast animation playback" button was only doing the "take 10 steps forward once" function. Now it initiates continuous fast playback. [19836]
• An internal special value of IP address, 254.254.254.255, was mistakenly visible in Top N reports. This value will no longer be shown. [19780]
• The GUI could crash when viewing Traffic Reports -> Flows or when viewing a newly created custom history report and then moving the network time. These problems are fixed. [19246, 19844]
• The GUI could crash when attempting to export alert configurations from the Alerts table.This is fixed. [19895]
• The GUI could crash when a traffic group is deleted. This is now fixed. [19565]
• The GUI could crash when a statistic column other than Average is added to a traffic report, and applied to all traffic reports, and then any of the Top Source, Top Destinations, or Top Conversations or Top Protocol reports is viewed. Now non-Average columns will not be added to the Top N reports. [19774]
• In some cases, maps generated by the Save Map Scheduler would be drawn with node icons that were much too large, and PNG maps with a background image would not be registered correctly. These problems are now fixed. [19763]
• The GUI could crash if a VPN traffic flow is found to have more than one ingress PE. The heuristic is now more robust to handle this case. It is also now using information from MPLS-aware netflow. [19852]
• The GUI could crash if there are multiple routers having an interface address the same as a BGP peering node's router ID because the multiple routers would be incorrectly consolidated. Now the consolidation will only be done if the AS assignment matches. [19886]
• The stacked graphs for traffic reports were not correctly adding the values of all the graph lines. Now the display is correct. [19932]
• Ingress Router Group to Ingress Routers drill down contains other routers. [20345 ]

RSVP-TE Feature

• When switching from Analysis mode to Planning mode, some traffic flows need to be recalculated to be ready for flow editing, but errors in this recalculation resulted in flows being lost. These errors are fixed so the flows are recalculated correctly, although there may still be some differences as flows shift from tunnel midpoint routers to head-end routers. [18332]
• The Routing Comparison Report was listing some RSVP-TE tunnels as having path changes when in reality there were none. The incorrect listings are now eliminated. [18553]
• On the tunnel map, if information for a node or link is not available because it existed only as a previous time, then a status message is shown when the node or link inspector is requested but not available. [18672]
• Tunnels are not updated when 'tunnel down' SNMP trap is received. [20656]
• Crash inside LSPFragment::adjacencyPrepare() in topod. [15516]
• Traffic reports history drill-down for one item ignores graph selections. [20804]
• Reports sent via email attachments have corrupted file names and it may not be possible to open them. [20643]
• Error parsing 'explicit-paths' command. [20297]
• Incorrect real-time clock setting causes invalid Mysql SSL Certs to be created during initialization. [20101]

 

Planning Mode

• "Link Up" edits would be incorrectly exported as "Link Down" edits. This is now fixed. [18872]
• The format for the identification of OSPFv3 nodes has been corrected so that operations on the pseudonodes or prefixes originated from them can succeed, both as direct input or as imported edits. [18946]
• Dependent edits shown in child rows of the hierarchical table will now be exported correctly independently of whether the table is expanded or collapsed. For VPN edits, the quoting is included on child edits for VPN Flows so they can be imported successfully. [18974, 19548]
• When exporting BGP prefix edits, the correct AFI/SAFI is included so now those edits can be imported successfully. [18993]
• When the NextHop address is edited on a BGP VPN prefix, that change is now included in the Changed Attributes column of the list of edits. [18997]
• In the Planning mode Traffic Reports, the Link reports in earlier release were missing the columns introduced in 9.20 to show the utilization percentage before and after the edits, in addition to the traffic rates, due to the change in the traffic implementation for this release. These columns are now restored. [17901, 19816]
• If the Add Router dialog was not closed after adding one router, then a second added router would be placed on top of the first router rather than in the position where the mouse was clicked to place it. The position is now set correctly. [19205]
• Simulation of route summarization rules has been expanded so that when backbone links are taken down the correct summary routes are also taken down. [19226]
• EIGRP routes not advertised on a link added. [20814]

Route Resolution

• VPN flows that egress from the same PE as the ingress were not being routed correctly, so BGP reports were inaccurate. This routing is now corrected. [19822]
• In Traffic Reports -> Flows, the mini-map path shown for selected flows could be incomplete for flows exiting a Cisco router on a tunnel interface. The correct routing is now calculated and displayed. [19829]
• Routing has been corrected for some cases where the alternative path after a primary tunnel fails is to follow an IGP path rather than another tunnel according to the metrics. [19894]

Consolidation

• When searching for a matching BGP route in another topology to consolidate a BGP NextHop, we now ignore routes that are not /24 or longer to avoid incorrect consolidations. [19206]
• A problem with incorrect router consolidation was avoided by not considering the identifiers picked by the Collector since those are no longer taken from the corresponding IGP router. [19221]
• In an OSPFv3 network, two pseudonodes representing separate LANs might be consolidated incorrectly into one in some cases where a router is the DR for multiple LANs. The pseudonodes will now be kept distinct. [19878]

Web Administration UI

• The detailed NetFlow statistics reported on the Flow Recorder configuration page include a count of packets lost that was previously inaccurate when NetFlow records arrived out of sequence. Now the loss count is correct. [8075]
• In the web UI View Log page, it is now possible to clear the Remote Syslog Collector setting. [18581]
• VLAN interfaces were displayed incorrectly and would not work for the Flow Fanout feature, and were displayed as blank in the Health Report, due to differences in the output format of system utilities to list interfaces.  VLAN interfaces are now displayed correctly and are usable in Flow Fanout. [19214]
• The web UI page for Save Map Scheduler got stuck with a "Loading Layout" message if no layout had been created yet. This scenario no longer causes a problem. [19525]
  
• When configuring MD5 authentication for OSPF, the Key-ID value of zero was incorrectly disallowed, but now it is accepted. [19569]
• In web reports and in the GUI, the "Area or AS" column of the IPv4 or IPv6 Prefix Flap report now shows the same value on the parent row as on its children rows if those rows all have the same value, or "Various" if not, rather than just a blank column. [19767]
• In earlier release, the Exported Graphs item was missing from the menu on the Legacy Reports tab. This is restored. [19889]
• The Saved Top-N Reports now show both the autonomous system name in addition to the AS number if available. [19909]
• With the release, on a unit that is configured with a VLAN interface as the admin interface and no address assigned to the physical interface, the web UI will just display an error popup and not be usable. Now the web UI will work except for installing or deleting licenses on client units. This limitation will be removed in the 9.21 release. [19864]
• Error messages about inter-unit communication could result when attempting to install a license on a system updated to earlier version. Now the client unit properties are properly updated so these errors will not occur. In addition, expired license terms are now shown only in Details or Unit-Specific display mode, not Summary or Aggregate display mode, and the Delete Expired button is only shown if there are expired terms. The procedures for verifying consistency of the licenses stored on the master and client units have also been improved. [19834]
• Tabs in the new web UI are removed or added correctly according to the licensed capabilities of the unit so that functions are not shown when they are not allowed. [19820]
• In the info panel on the Dashboard page, the sentence and URL providing guidance about avoiding SSL certificate warnings has been clarified. [19803]

XML RPC API

• A new XML RPC api_rsvp_te_tunnels will output the RSVP TE tunnel configuration in XML format, the same as could be exported from the GUI's tunnel table in 9.20, and the XML schema for this format is now available one the web UI Downloads tab. [18420]
• The filter expression rtrIsolated can now be used on the List Routers table in the GUI and on api_mp_routers to filter the list of routers to show only those that are isolated. [18501]
• Attempting to set an alert parameter after adding alerts in an api_manage_config script would fail, but this is fixed. [19211]
• For the Path Performance Analysis (Link Delay Modeling) feature, delay values were not correctly looked up in cases where the network model time is moved and link states change. The delay values are now correctly updated in those scenarios. [19664]
• The XML input parameters for api_traffic_custom_reports, api_traffic_custom_reports_history and api_traffic_list_flows are now validated against the XML schema traffic-api-schema.xsd. [19308]
• api_traffic_custom_reports_history sometimes returned no results when key selection was done. Now the correct results are returned. [19974]
• It is now possible to configure AS Groups using the api_manage_config query. [20040]
• The output format of api_traffic_custom_reports has been corrected so that it is now complaint with the XML RPC spec. [19835]
• Hierarchical traffic groups were not exported correctly with api_manage_config. The format has been corrected so that getting the config and then setting on another unit will produce the same result. [19861]
• The QueryServer could crash on an api_manage_config request to get the networkWideConfiguration tag, such as when a BGP comparison report is requested on the web UI. This is fixed. [19175]

Alerts

• Alerts that contain a prefix, such as a Prefix State Change, now include the name assigned to the prefix if there is one. [12379]

Route Recording

• The IS-IS recorder now introduces a delay queue for processing of received LSP fragments so it can correlate prefixes that shift from one LSP fragment to another to avoid treating these as back-to-back Drop/Add events. [7599]
• In some networks the Add Peering event for OSPF and IS-IS recorders was generated after many other events were written during the process of the peering coming up due to the way that the protocol exchange occurs. Now the peering up event will be generated earlier in the sequence. [10603]
• Since BGP peerings with IPv6 addresses are not supported yet, BGP next-hops that only have an IPv6 address will be ignored. [19264]
• Support for VRF Lite in EIGRP networks is expanded to include Cisco Nexus 5K and 7K routers, and for those plus IOS routers, it is expanded to support networks that include multiple VRFs on the same router as virtual router instances. These are shown as separate router nodes on the map. [19536]
  
• Some Cisco routers returned invalid chassis serial numbers in the "show inventory" command, causing two separate routers with the same invalid numbers to be consolidated. Now the invalid numbers (fewer than 5 characters) are ignored. [18845]
• Processes that load the network model could crash due to an invalid router ID written by the Collector when an SNMP response was received for a request that was no longer active. A guard has been installed to avoid this. [17802]
• Support for Cisco Nexus 7K routers in EIGRP networks was enhanced to tolerate output where the Interface Address line is appended to the end of the Description line rather than keeping them separate. [19859]
• For networks with a large number of interfaces on routers that are recorded by the Collector, the amount of memory consumed when loading the Collector database was excessive, possibly causing swapping. The data organization has been optimized to reduce the memory consumption. [19837]
• The IS-IS and OSPFv3 recorder processes could crash when recording IPv6 events are received with certain timing. The root cause has been corrected. [19533]
• When the Collector is configured only with /32 prefixes to just query specific routers, a misleading status message "Collector discovery in progress: collected 100% of total routers" could result. This message has been changed to give the actual number of routers and to consider discovery completed when the query to the QueryServer for a router list succeeds. [19270]
• For Huawei routers, if fetching of the traffic interface index through SNMP fails so the interface index collected through CLI can't be replaced by the traffic interface index needed to deploy traffic, then the index from CLI will be invalidated to avoid incorrect traffic deployment while still keeping the remainder of the interface information. [18723]
• In some cases, the Collector incorrectly marked interfaces as down because the SNMP interface information was not delivered in order. The code now sorts the information first. [18783]
• The Collector screen-scraping code that scans for a command line prompt now requires the prompt to be at the start of a line to avoid an incorrect match in text such as a description line. The incorrect match was causing a crash. [19037]
  
• Collector parsing was extended to support collection of interface index information for T1 interfaces. [19649] Collector parsing of RSVP-TE tunnel autoroute information was extended to accommodate cases where tunnels could belong to a meshgroup. [19656]
• The recorder process for OSPF, IS-IS or EIGRP could crash on a system where the event rate is low enough that more than 248 weeks of data was stored, due to buffer overflow. This is fixed with a dynamic buffer allocation. [19291]

Traffic Recording

• Changes made in the Flow Recorder configuration while the recording is running, such as blacklisting a router, will now be properly seen and executed by the recorder. [18290]
• In the earlier releases, when drilling down to flows in a traffic report at a time that is not on a 5-minute boundary, the attributes of a flow (such as its path) are those recorded at the previous 5-minute boundary, not the next one as might be expected since the flow's bitrate is included in the averaging interval reported as the next 5-minute boundary. This is a change from previous releases in which the traffic was redeployed across the routing topology whenever the network time was changed to be not on a 5-minute boundary. There is now a Redeploy Traffic button at the bottom of the report to initiate the redeploy of the flows with the current routing state. In the 9.21 release, the attributes of the next 5-minute boundary are used. [18824]
• Changing the name of a traffic group or CoS group will no longer break tracking the traffic history for the group before that point. If the group is subsequently deleted, the traffic for that group will be identified by "Original Name: original-group-name (deleted)". [19812]
• The utility program that was intended to update traffic databases for compatibility with the revised traffic software architecture in the earlier release did not perform the necessary changes, but now it does. [19713]
• The system can accommodate a total of 100K elements over all the custom history reports. This limit is now imposed by the software. [19149]
• The process that analyzes traffic data on the Flow Recorder unit is now allowed to consume 75% of the physical RAM or 10GB, whichever is larger, rather than 50% as before. [19959]

System

• Linux kernel bug 16991 causes a kernel "panic" (making the system completely unresponsive) due to a divide-by-zero error in the CPU load balancing calculation that can occur after the system has been running for more than 200 days. A kernel patch is installed to avoid this panic. [18999]
• When user-configured router names or AS names are entered in the GUI or through the XML RPC API, daemons such as the RouteAnalyzer that generates alerts will now detect that new names are available and will use them. [10496, 16758]
• If the top-level domain in the Recorder Configuration is deleted and replaced with a new one, the reports/alerts daemon will now detect that and begin processing the newly recorded database. [12741]
• When Technical Support Access is enabled, a login under that account is allowed to start one additional instance of the GUI even if the licensed limit has already been reached by other accounts. This avoids the need to ask customers to log out in order to investigate their support request. [19228]
• Updating of the router name repository for a new identifier format as part of 4-byte ASN support could be very slow if there were many BGP NextHops with names. This would be seen when updating software or restoring databases, but is now optimized. [18123]
  
• The BGP MD5 authentication implementation was incorrectly disallowing peer addresses with 0 in the last octet. That restriction is now removed. [19376]
  
• Support for a new 3700 hardware platform is added. [18341]
• Customers can now perform a software update on RAMS appliances from their own servers using a URL specifying https as the protocol with self-signed certificates if desired. [19280]
• In ealier release, support was broken for units with the Allow Admin interface configured on a VLAN. Now any of the physical interfaces or VLAN interfaces may be selected as the Allow Admin interface, and it is not necessary to configure an address on the first motherboard interface. [19864]
• The Custom History Report configuration will now be restored correctly after saving in a backup file. [19866]
• Locale-specific message files were not included in earlier release, but have now been added back. [19899]

Documentation

• Separate documentation is now available for the IPMI feature that is available on the 3600 platform.
• The new "Enable upstream projection" feature on the Administration -> Traffic web page is now documented in the User's Guide and with context-sensitive help on the web. [19804]
• Documentation of the BGP Redundancy Alert has be clarified to say that the alert is triggered whenever the number of next hops changes and is not equal to the number of next hops configured for the alert. The label on the alert configuration field is changed to "Next hops" rather than "Threshold". [19824]
• References in the User's Guide to api_traffic_src_nbr_matrix and api_traffic_src_dst_matrix were removed since those calls have been replaced in the earlier release. [19857]
  

IMPORTANT: Consider your disk space requirements, 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 HP RAMS 9.xx release, the Flow Collector is only supported on DL380 G5, DL360 G6, DL380 G6, DL360 G7, and DL380 G7 hardware platforms. HP 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-8.0 appliance version, you must re-configure the server with two logical volumes and install the 8.0 appliance version from a CD image. Failing to do so can cause unexpected behavior. Cases reported as such will not be supported.

When using a DL360 or DL380 G6 hardware platforms 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, HP 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 HP RAMS.

For detailed steps to configure an HP RAMS 9.20 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. See to instructions in the HP 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:

• 1 drive = RAID 0
• 2 drives = RAID 1 +0 (Mirrored set, total disk space* is the size of smallest disk)
• 3 or more drives = RAID 5 (Striped set with 1 drive used for parity, parity drive is not included in total disk space*)

* 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

For configuration options and details, see the HP Smart Array Controller Reference Guide .

IMPORTANT: Make sure the logical drive is configured as needed before installing HP RAMS. Any changes to the logical drive configuration, e.g., adding drives or changing the RAID level, will require a reload of the HP RAMS software and a restore (from backup) of the HP RAMS configuration and databases.

The following information is important for HP RAMS or the Traffic Analysis Add-on installation and deployment:

• For RAMS or RAMS Traffic:
  • It is necessary to update to 9.20.00001 or newer 9.20 prior to upgrading to the 9.21 release. This requirement is to ensure all of the database update steps implemented in earlier releases have been applied before updating to 9.21. It is necessary to execute these database update steps while running 9.20 because some of the steps could fail if executed on a 9.21 system due to the change to a different version of MySQL that was forced by changes in MySQL licensing. The 9.21 release performs a check to ensure the system is running a new-enough 9.20 before proceeding with the 9.21 installation. See the Release Notes for the 9.20 release for the requirements in updating to that release. [19587]
  • The new version of MySQL imposes a restriction on the length of database filenames. The user interface should only display the pathnames of topologies as created in the Recorder Configuration hierarchy, and not show the database filenames that are derived from those pathnames. However, there may be some places in the UI where database names are displayed, and if any of them are longer than 64 characters, the filename will be contracted such that some of the characters are removed and a string of hex digits inserted. [7269]
  • A system that has database filenames longer than 64 characters before the update to 9.21 will show a replication error on the Data Source Configuration of the Modeling Engine, in the recording status and in the health reports. In this case, replication should be restarted to fix the problem. It is not necessary to rename the databases. [7269]
  • Users upgrading from 9.20 should delete browser bookmarks that reference web pages in cgi-bin because those bookmarks will open the old web UI rather than the new one. The old web UI remains available for emergency use during the transition to the new web UI, but will be removed in a future release.
  • After updating to 9.21, requesting to revert to the alternate software and OS or attempting to software update to a version older than 9.21 will result in a warning that the appliance will be reset to factory defaults. If the user still decides to go ahead, all recording configuration, databases, user accounts, etc., will be deleted, but licenses are retained.
  • In previous releases, if the Specific Router Access Configuration of the Collector recorder permitted access to one interface address of a router, the Collector might try querying other interface addresses on that router if the configured one was not successful. In 9.21, for any interface address that is considered for querying, the Collector will find the longest match prefix in the router access configuration and query or not according to the specified access. If there is no match, the address will not be queried. Note that if the recorder configuration was set up to allow most addresses but block access to specific routers using /32 addresses for those routers, it will now be necessary to adjust the configuration to block all interfaces of those routers, not just one. [16504]
  • Since the Query Server daemon is now required to support the new web reports, a newly installed Modeling Engine unit will have the Query Server enabled rather than disabled by default. Remote access to that daemon will still be disabled by default. [19298]
  • A RAMS Traffic system or a distributed RAMS system is comprised of multiple units. One unit will be designated as the master. All licenses should be applied on the master, which
    will then distribute the licenses to the client units. If a license is applied on a client unit, it will be pushed up to the master, and licenses will be pulled up from a client unit when it is added as a client to the master.
  • Before adding a client unit to the master unit using the admin web interface, make sure that both units are configured to run NTP and that time on the client unit is no more than a few seconds behind the time on the master. Otherwise a warning will be issued and the client will not be added.
  • Before shutting down or rebooting a unit that is recording routing or traffic data, first stop recording and make sure that it has stopped by verifying the status on the web page or using the status details available by clicking on the status LED in the GUI. This is to allow time for the recorder daemons to flush any data or reports that may have been in progress.
  • When updating to a new software release, update the master unit first and let it finish coming up after the reboot before rebooting the client units.
  • Before adding a unit as a client, recording must not be running on that client because the databases will be renamed. If recording is not stopped, a warning will be issued and the operation will not complete. [8437]
  • When a new system is first being brought up, it may be necessary to exit the GUI and the start the GUI again if the database has not been created before the GUI was started.
  • For RAMS Traffic
    • Releases 6.0 through 9.20 required Flow Recorder units to have the RAID controller configured with two volumes so that raw flows could be recorded on a separate volume to avoid disk ontention. Beginning with the 9.21 release, this requirement has been removed. New units will be manufactured with a single volume, but 9.21 version will operate equally well on Flow Recorders with either one or two volumes. [18513]
    • The NetFlow sampling ratio should be set appropriately for the traffic level. For a small ISP, a ratio of 4 to 16 could be enough. For larger tier-1 ISP, a sampling ratio of 1024 to 2048 is fine. We recommend that the ratio not be set higher than 8192 to avoid introducing too much inaccuracy.
    • Make sure that the NetFlow sampling ratio specified in the Flow Recorder configuration matches the sampling ratio that is configured on each exporting router. The sampling rate may be set to different values for each exporter if needed. If these settings don't match, RAMS Traffic will over-report or under-report the traffic levels. RAMS Traffic does not currently have any means to detect a mismatch on its own.
    • We recommend that the NetFlow active flow timeout, which is used to detect long-lived flows, be reduced from its default value to no more than to 15 minutes and preferably to one minute. If the aggregation cache is used, its active timeout must also be similarly set. Exceeding these times can cause NetFlow data to be delivered to the Flow Recorder too late for processing, in which case it will be dropped. For the inactive timeout, the default value need not be changed.
    • When opening a collection of topology databases including traffic, the GUI will start in Analysis mode, rather than Monitoring mode, and with the selected time set to the ending time of the traffic data which is typically 20-30 minutes earlier than the current time. For a display that follows the latest traffic data as it becomes available, Traffic Tracking mode can be enabled in Administration -> Options.
    WARNING: Older hardware G3 series (1200, 2400) cannot run in 64-bit mode and therefore cannot be updated to HP RAMS 8.xx or newer. If an update is attempted, the system will fail to boot up. To recover the system will require reinstalling the earlier version of software from CD with loss of all data. In addition, the 2500 hardware is not supported for 64-bit releases because it is limited to 3GB of memory which is not sufficient. [11783]
  • HP RAMS 9.20 uses a licensing version different from HP RAMS 5.x. For this reason, supported migrations of previous versions of HP RAMS (5.x) license keys must be migrated ( http://webware.hp.com/ ) for use in HP RAMS 9.20.
  • After you update from HP RAMS 5.x to HP RAMS 9.20, if you ask to revert to the alternate software and OS, you will receive a warning that the appliance is reset to factory defaults. If you choose to go ahead, all recording configuration, databases, user accounts, etc., are deleted.
  • When updating to a new software release, update the master unit first, and let it finish coming up after the reboot before rebooting the client units.
  • When updating from pre-HP RAMS 8.01 versions, any custom configurations done for the alerts in the previous versions will also have to be manually migrated. This is required since the PD-ROUTE_EXPLORER MIB mib-tree structure has been changed in order to provide a streamlined, smaller set of well-understood, concise alerts in the HP RAMS 8.01 version. Consequently HP RAMS SNMP trap OIDs from the HP RAMS 8.01 release are not compatible with previous versions of HP RAMS.
  • When updating from a HP RAMS 5.x version, the databases are automatically renamed with a "Pre60X" prefix because the database table structure has changed. The older databases can still be viewed, but recording to them is not allowed.
  • When updating the software from a pre-HP RAMS 8.01, the existing accounts configured on each unit will be transferred into the new local authentication server running on that unit. To switch to a single authentication server on the master unit, a common shared secret must be configured on the master and each client unit.

  WARNING: You cannot downgrade the product after installing the RAMS 9.21 due to the schema change in this release. HP recommends you to take a backup of the RAMS 9.20 database and the system configuration on each unit before proceeding with the installation. For more information on performing the backup and restore operation, see Backing Up and Restoring Data section in the HP RAMS 9.21 Administrator’s Guide.

For Route Recorder or RAMS Traffic:

• Software update to HP RAMS 9.21 (appliance version9.6.40-5-R) is supported as below:
  • HPRAMS RAMS920_00001 (appliance version 9.4.46.2-R) to HP RAMS RAMS921_00001 (appliance version 9.6.40-5-R)
    • Direct upgrade is possible by using the Software Upgrade link.
    • You can take a backup before the upgrade process. For information on the upgrade process, see the HP RAMS Administration Guide.
  • HP RAMS 9.20 (appliance version 9.4.34.1-R) to HP RAMS RAMS921_00001 (appliance version 9.6.40-5-R)
    1. HP RAMS 9.20 (appliance version 9.4.34.1-R) to HP RAMS RAMS920_00001(appliance version 9.4.46.2-R)
    2. HP RAMS RAMS920_00001(appliance version 9.4.46.2-R) to HP RAMS RAMS921_00001 (appliance version 9.6.40-5-R)
       • Direct upgrade is possible by using the Software Upgrade link.
       • You can take a backup before the upgrade process. For information on the upgrade process, see the HP RAMS Administration Guide.
  • For previous versions, HP recommends you to upgrade to the HP RAMS 9.20 first and then upgrade to the HP RAMS RAMS920_00001 before you proceed with the installation of HP RAMS 9.21.