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

Before installing RAMS or Traffic Analysis, make sure that your system meets the following minimum requirements:

Supported Hardware Platform in descending list of preference:

1. HP Proliant DL 380 G6
2. HP Proliant DL 360 G6
3. HP ProLiant DL 380 G5
4. DL 360 G5
5. DL 380 G4
6. DL 360 G4p
7. DL 360 G4
   

NOTE: Starting with the release of RAMS 8.01, the hardware component requirements specified in the 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, 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 9.0 release, the Flow Collector is only supported on DL380 G5, DL 360 G6 and DL 380 G6 hardware platforms. 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 software version, you must re-configure the server with two logical volumes and install the 8.0 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 360 or DL 380 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, 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 9.00 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 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 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.

• RAMS 9.00 uses a licensing version different from RAMS 5.x. For this reason, supported migrations of previous versions of RAMS (5.x) license keys must be migrated ( http://webware.hp.com/ ) for use in RAMS 9.00.
• A software update from 5.x version of a Flow Collector to the 7.5 software version in RAMS 9.0 without reconfiguring the hardware minimally with two logical drives is not supported. See text in the above "Hardware Requirements" section for more information.
• After you update from 5.x to 9.0, 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-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 8.01 version. Consequently RAMS SNMP trap OIDs from the RAMS 8.01 release are not compatible with previous versions of RAMS.
• Software update to software version 8.11 is only supported from 5.5 release; updating from pre-5.5 requires updating to 5.5 first. [10535]
• When updating from a 5.x software 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-8.01 software version release, 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.

• Important: RAMS integration with NNM
  • Since the RAMS 8.01 release, the integration of RAMS is with the NNMi series alone. The integration of RAMS 8.01 and upwards with the NNM 7.x series is not supported.
  • No separate NNM Integration Module is available for RAMS 8.01 and upwards apart from the integration, that is part of the NNMi series.
• Reverting to RAMS version 5.5 from RAMS 8.01 or higher hangs at grub
  

  This requires the deletion and recreation of the logical drive. The steps to perform that are detailed below:

  • During the boot sequence, the following message would appear:
    

    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,

    • Press F8 to enter the array configuration utility.
    • Delete the existing logical drives first.
    • Create a new single logical drive containing the 2 disks.
    • Reboot the system and proceed with the RAMS 5.5 installation.
• Consolidation of router nodes on the map may be incorrect when 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. [12578]
• In the RAMS9.0 release, 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.
• The OSPF route calculation of RAMS 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]
• If the Route Recorder is configured as a BGP peer with a Cisco router, and the router is configured to send MPLS L3 VPN routes, but you disable MP-BGP support of unicast IPv4 routes (AFI 1, SAFI 1), the BGP peering will constantly reset. [12124]
• In Path Reports, the table All Paths by Destination may show a "Reachable by" count of 1 when the drill-down would show many source routers able to reach the destination. [12163]
• 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 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 earlier releases were more lenient and would accept just an address without the mask.
• In 8.x, 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 it comes 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.
• 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.
• If the VNC server was not stopped prior to updating from a 5.x version, the VNC "started" state is retained after the update to 8.10 version. If the RAMS GUI is opened via VNC display 1 soon after the update completes, the RAMS GUI will display a " No valid GUI and router count license" error message. The fix is to stop and restart the VNC server. Note: VNC displays 2 and higher do not exhibit this behavior.

Following are selected fixes and enhancements since RAMS 8.12 release.

• Since prefixes can now be assigned names, the Prefix filter that appears on tables such as List IPv4 Prefixes will accept prefix names in addition to numerical prefixes. [12182]
• When recording BGP, each peering can record more than one address family (IPv4, IPv4-VPN, IPv6). Now the topology map will only show those BGP peers that are recording the address families of the topologies that are opened. [12240]
• If a router A inside a group G is connected to a router B obscured by the same group G, then router B and the link from A to B won't be shown because otherwise they would appear to be included in G. Now if one holds down the left mouse button on router A, then router B and the link between A and B will be displayed for as long as the button is held down. [12668]
• The View -> Unhighlight All Paths menu item was incorrectly enabled when topologies were first opened but no paths were highlighted. Now that menu item is disabled initially. [12785]
• In the "Assign BGP ASs to Routers" dialog, "The Selected Routers are in AS" pull down menu is now sorted for easier selection of an AS number when there are many. [13005]
• In Path Reports, the reports on asymmetric paths are intended to include only one entry for a path. The method for choosing between the forward and reverse paths for the one to be listed has been changed so that it will now be consistent from one invocation of the Path Reports to the next. [13016]
• In various tables, the filters for bandwidth and delay defaulted the option choice to "greater than" but the option drop-down did not show any choice marked. The default is now changed to "equal to", which is presumed to be more in line with user expectations, and the corresponding box in the option drop-down is checked. [13056]
• When consolidating BGP peer nodes and NextHop nodes with IGP routers, the algorithm now avoids considering an IGP domain that is more closely related to a different BGP AS or confederation AS in the recorder hierarchy. This is to avoid incorrect consolidations. The new Combine Routers dialog in the GUI can be used to manually combine the nodes if this change incorrectly leaves nodes unconsolidated. [13057]
• When the mapping of colors to topologies is changed with Administration -> Options -> Colors, the color is now changed in the Network Summary and in related cloud icons as it should be. The color change is now also retained after exiting and restarting the GUI. [13226]
• The Highlight by Exit Router function will now highlight the last router node on the path to the exit even in cases where the path continues to a node that is not a real router (a pseudonode or a NextHop node). Correct highlighting is also implemented for the exit router report in Prefix Diagnostics. [13255]
• In the VPN Connection Configuration dialog, the VPN filter would only match VPNs that existed when the dialog was opened. Now the filter will include newly added VPNs as well. [13270]
• Links comprised of multiple physical links are changed to be drawn as two parallel lines. Now the same change is made for links between groups of routers that represent multiple individual links. [13361]
• When in Monitoring Mode, if the time range selected in the History Navigator was changed from Online to something else, such as 1hour, and then the Events button was clicked to open an events panel, the time range would change back to Online. It no longer does this. [13437]
• In the RIB Browser for an OSPF or ISIS domain, the number of down links reported in the table will now match the number shown when the links are listed from the context menu because the same treatment is given to links that are down. [12171]
• In Planning mode, when adding a BGP peering, it is now possible to configure the "next hop self" attribute for the peering. [13064]
• When resolving a BGP route, infinite recursion could occur when it should have stopped on a connected route to a loopback interface. The recursion is now terminated correctly and the path is shown correctly. [13065]
• The Static topology model now accommodates the case where two routers are connected by multiple physical links. These are displayed as multiple tabs in the link info panel, as for other protocols. [13087]
• In the RAMS 8.12 release, tables that displayed EIGRP prefixes were missing the indication of External prefixes in the Attributes column due to a change made for internationalization. This is fixed. [13104]
• A crash could occur in the GUI and in daemons that load the routing topology model for large BGP topologies. This was fixed by changing the processing of one component of the the data to be incremental. [13066]
• The GUI could crash when using the Edit IPv4 Traffic Flows function in Planning mode or upon opening a topology where Static nodes and nexthops need to be consolidated in certain cases. These bugs are fixed. [12926, 12977]
• New filters have been added to prefix tables and the event list for the BGP "Cluster List" attribute and for IPv4, IPv6, and VPN prefix groups. [11387, 12211]
• If a router with connections to one or more routers inside a group container on the map was hidden, then the layout was saved and later reloaded after which the node was unhidden, the link between the router and the container was not drawn. This is now fixed. [12647]
• When a link connecting to a router group container on the map represents more than one actual link, but the metrics of all the links are the same, then the metric will be displayed on the link if that link label mode is selected. [12649]
• The logic has been revised for automatically including pseudonodes into a router group when routers are moved into or out of the group using the group edit dialog or the group edit mode on the map. The rule is that the pseudonode is moved into the group when all connected routers are in the group, and is moved out when all connected routers are moved out. If some of the router are in the group and some are out, then if the pseudonode is manually dragged into or out of the group, it will stay where it is put, except for the case of just two nodes connected to the pseudonode, in which case the pseudonode is placed in the middle of a straight line between the two nodes. [12669]
• If the neighbors of a pseudonode were hidden from the button on the info panel of the pseudonode, the pseudonode would also be hidden. If the neighbors were then unhidden, the pseudonode was not. Similarly, if a node created in Planning Mode was marked down and then all failed nodes were hidden, it would not come back when failed nodes were unhidden. These bugs are now fixed. [12694, 12719]
• The table for setting Interface Capacities is no longer allowed to be open during Monitoring Mode since changes in the network can cause the capacities to be calculated incorrectly. When switching into Monitoring Mode, a warning is displayed saying that the table will be closed. [12908]
• Several changes were made to improve the layout of pseudonodes between a pair of routers when there are many such links. First, the spread of the pseudonodes is limited so that they don't form a large diamond perpendicular to the line between the two routers. Second, to allow for the pseudonode layout to be improved manually, the pseudonodes are not moved due to a partial-layout unless the adjacent routers are moved. [13019]
• In some cases, a path traced in an OSPF network was stopping at a pseudonode when it should have continued to the DR. The problem was that the forwarding address was resolved by the pseudonode. This is now fixed so that the path resolves to the connected route on the ABR. [13022]
• When a Link Group is selected to be hidden, any link between groups will also be hidden if all the adjacencies that are coalesced into the link are included in the Link Group. [13054]
• When moving a router group container on the map, if there was a router not in the group that was drawn underneath the container, then the container could not be moved because the underlying router was also selected. Now that underlying router is not selected. [13072]
• On the map, when a link between groups represented multiple actual links between routers, the group link's color was not updated to indicate when any of the underlying links went down. Now it is shown as dark red if some of the links are down, or bright red if all of the links are down. [13353]
• Down nodes and links in the Static topology are now subject to being timed out and hidden from the map and tables according to the auto-hide timeouts as for the protocol topologies. The timeouts are specified in Administration -> Options menu of the GUI. [13105]
• Two crashes in the GUI have been fixed: when the MPLS WAN Expected prefixes dialog was loaded, and when the parent window behind a progress register dialog was closed. Also, a memory leak in the Static topology has been plugged. [3291, 13317, 13339]
• A harmless message "Wrong Mode 0" would appear in the log at the time of GUI startup. This is now eliminated. [13358]
• Sorting and grouping on a table column containing IPv6 addresses was not producing the correct order, but now it does, including /128 addresses. [13386]
• The current topology time displayed on the History Navigator window was not in sync with the time displayed on the main map window after an animation. They are now the same. [13367]
• After manually configuring some values in the Set Interface Capacities table and saving them, it is now possible to delete all of the saved values in case the recorder configuration is later expanded to include automatic acquisition of capacities. [13406]
• In the GUI Routing Analysis reports for link or prefix flap, if the first transition is from up to down, that will now be counted as a flap. [13566]
• Fixes were implemented for crashes in the GUI when selecting "Show AS groups inside VPNs" for an MPLS WAN configuration; when closing a topology that included a Static database; and in Traffic Reports when drilling down to customers from a link. [13185, 13700, 13770]
• In the Routing Analysis Reports, the naming of filters was made more explicit, such as "IPv4 Prefix Group", and consistent across various drilldowns. [13245]
• In the Expected Prefixes dialog for the MPLS WAN feature, the buttons to Set Expected or Clear Expected were disabled even after some table rows were selected to be modified. Now the buttons are enabled when they should be. [13538]
• When moving the state of the network from one point in time to an earlier time, BGP events will be executed backwards if that would be more efficient than jumping to an earlier snapshot time and then executing forward to the desired time. In some cases, the backwards execution did not process all the events in the correct order; now it does. [13788]
• In Planning Mode, when adding an EBGP peering, it now works to add BGP routes specifying an intermediate AS using the "Add routes containing neighbor AS" option. [13838]
• The Prefix Diagnostics report for "Routers Unable to Reach" could show an EIGRP hop in a network with no EIGRP if the path was incomplete with zero hops. This is fixed. [13797]
• Releases before RAMS 9.0 needed protection in the GUI against exceeding the 32-bit virtual address space limit. Now that the systems has been converted to 64 bits, this protection has been removed to allow handling larger networks and higher traffic rates. [13871]
• Consolidation of an EBGP NextHop node with a BGP peer in the NextHop's AS can now be done even if there is no IGP running on that BGP peer router if the BGP ID matches the NextHop address. [13986]
• The limit on the size of copy-and-paste transfers from a GUI running inside a VNC session to the clipboard on the VNC client machine has been increased from 64KB to 256KB. This is an interim fix pending a solution to restore the 4MB limit. [13865]
• When filtering the Interfaces table based on Delay values, it was necessary to divide the desired value by 1000 because of a units mismatch. Now the value should be the same as shown in the column. [13260]
• A memory leak that occurred when moving time in the GUI and daemons on systems that include collection of a Static database has been fixed. [13816]
• In traffic flow de-duplication, some of the duplicates might not be found, which resulted in incorrect reports and also caused memory to be leaked. These problems are now fixed. [13880]
• The GUI and the QueryServer could crash if time was moved backwards on a Static database that includes VRF information. This is fixed by not using backwards execution of the events. [13806]
• A crash in the GUI that occurred when undoing edits in Planning Mode if new prefixes had been created has been fixed. [13571]
• The GUI could crash when highlighting a path if the destination prefix is the BGP Router ID of a router for which only BGP is the only protocol being recorded. This is fixed. [13992]

• The SNMP agent in the appliance now implements the standard MIBs correctly so an SNMP walk returns correct results. [12748]

• In the List/Find Paths table, when there were multiple recursion levels in the BGP route resolution, the path was correctly but the "Resolved-by Prefix" was displayed incorrectly. The display has been corrected. [12520]
• Finding the path to exit routers for an IPv6 prefix now works correctly. [12607]
• Some problems were fixed when finding paths in an OSPF network for cases involving AS external routes with a forwarding address and for non-backbone summary routes on an area border router with an active backbone connection. [13426]
• In some cases, attributes for BGP prefixes were not read from the database correctly, leading to incorrect routing and consequently incorrect traffic utilization. This is fixed. [13779]

• For MPLS WAN systems, if databases are restored from a backup file, the expected prefixes configuration will be restored as well. [13383]
• For configurations with primary and backup VPNs, the counts for the columns "Announcing Any Prefixes" and "Receiving Any Prefixes" in the report "Reachability by VPN" were sometimes incorrect when moving back in time to a point where the backup VPN was active.This is now fixed. [12702]
• A crash due to running out of memory was eliminated in the daemon that generates MPLS WAN reports by flushing unneeded data sooner. [12946]

• In the automatically generated daily Routing Reports, the various tables now list the top 10 entities of interest rather than just the top 5. Also, in some cases, the Summary Link table would show invalid characters in the destination address field. The addresses have been corrected. [11632, 13996]
• Deleting a protocol instance from the Recorder Configuration no longer requires a license for that protocol. Such a protocol instance might have been added when the protocol was enabled by temporary license that has subsequently expired. [13059]
• On the Network and Interface web page, there is now a pop-up warning when changes are made to a VLAN that is recording to let the user know that recording will be restarted. [13293]
• An option was added for the VNC Configuration of displays 2-10 to require authentication with the display 1 password at the VNC client before the connection to the VNC server is established. After that, the normal user login is performed. [13851]
• Configuration of NTP servers has been improved. Now up to three servers may be configured, and the fields have been renamed to remove the false notion of priority among the servers. [11529]
• Before configuring the "Top N" reports on a system including Traffic, recording must be started so that all the databases exist. A warning will now be shown if this sequence has not been followed. [12663]
• The System Health Report now includes the status of VLAN interfaces, alias interfaces, and static routes. The report also includes a report on the health of the RAID system (this was missing for some platforms). [12900, 13018]
• Several fixes were made in the Update All Units feature: When client units are rebooted at the end of the operation, now the recording status is restored to what it was before the update rather than always starting all recording; some problems with formatting of the Software Update web page are fixed; and several error conditions are now caught correctly and displayed. [6249]
• When replication is turned off using the Data Source Configuration page, the previous enabled or disabled state of the Central Reports/Alerts daemon continues to be show as a grayed-out checkbox rather than always appearing to be disabled. [13349]
• If an administrative domain was configured using the Master unit's IP address and later deleted, the Master unit could be deleted from the list of units in the distributed system which would result in several problems such as not being able to delete the first client unit. Now the deletion of the Master unit is prevented. [12755]
• The absence of a Traffic license is now checked more carefully so that Traffic options do not appear in the Recorder Configuration protocol instance menu and for Capacity Planning in the GUI Planning menu. [13423, 13428]
• In the daily Routing Report, for the IGP table Top 5 Flapping Links, if a link is present in multiple ISIS or OSPF areas, it will no longer be listed multiple times with the same area name. [13060]
• In the Administrator's Guide and on the Home page of the web admin UI, the sequence of initial configuration steps now puts setting the time and date first because the correct, synchronized time is required before adding clients to the master unit and for initializing temporary licenses on some systems. [13621]

• When multiple adjacencies are configured from the route recorder to an OSPF or ISIS area, the state of each adjacency is now tracked separately. This allows a Peering State Change alert to be generated on a transition of each adjacency rather than on just the first coming up and the last going down. Those alerts will also now contain the correct IP address and/or System ID of the neighbor router. [10603]
• Two changes were made in the way the EIGRP route recorder issues CLI queries and parses the output to accommodate Cisco 12K routers. Another change in the parsing accommodates routers that emit duplicate "Route not in topology table" messages. [13085,13118, 13113]
• The EIGRP recorder now supports route filters using prefix-list in addition to those using access-list as supported previously. [5526]
• The static information collector now records static routes with multiple nexthops correctly as a single Add Prefix event. [12662]
• The node representing the Route Recorder has been renamed from PD-REX-RECORDER to ROUTE-RECORDER to be more clear. [13228]
• Two changes make the EIGRP recorder's parsing of CLI output more tolerant of unusual conditions: the output of the "show ip eigrp topology active" command can sometimes have a line with "active never" instead of "active 00:01:25", so this is now treated as 0; and in case no ACL name is shown on a route redistribution filter line, set the ACL name to "-" to avoid an error. [13329, 13330]
• Rudimentary support for EIGRP in NX-OS switches was added in RAMS 8.12, but the information regarding network prefixes included in the routing was not recorded correctly. This is fixed. [12764,13331]
• In some cases, an EIGRP route recorder could reset its adjacency with the peer router at the end of a full topology exploration if the workload of validating distances took too long. Now this activity is properly managed at a lower priority so the adjacency is maintained. [13460]
• Fixed a crash in the Static Information Collector that may occur when an interface is removed from a router in the network. [13427]
• If more than one Static protocol instance was configured on a recorder unit, all but one of the corresponding daemons would open a listening socket for the configuration manager using a random high-numbered port that was open on the network rather than a specific port bound to the loopback interface only. This is now fixed. [13627]
• Collection of EIGRP topology information from Cisco switches running NX-OS was improved in three ways: EIGRP passive interfaces were missed before (since there is no "show ip protocols" command to tell what networks are included), but now are included based on having joined the EIGRP protocol multicast group; the variance value, which is also not displayed, is defaulted to 1; and eigrp processes that are given a tag (name) rather than just using the AS number are now accommodated. [13482, 13723, 13771]
• A latent bug related to pointers increasing to 64 bits has been fixed to avoid an EIGRP recorder crash when dynamically allocated memory grew above 2 GB. [13708]
• The EIGRP recorder was not detecting changes in ACLs used for route filters or offsets if the only change was to add more lines to the end of the ACL. These changes are now detected and are indicated by a "Change Route ACL" event in the Events table. [13850]
• The LED status light for the static information collector was set to yellow when it was waiting until the next (weekly) polling interval to run. That was misleading; now it is green. [13342]

• I n the RAMS 9.0 release, the output format of the api_list_paths call was changed to properly show recursive route lookups in a new "lookups" array added to the hop struct rather than as a separate hop. In this release the Developer's Guide is updated to show that change plus some other corrections. [12697]

• In the XML RPC API, an additional "mpname" field has been added to the router struct that appears in calls such as api_mp_links and api_traffic_links to show the same name that is shown for the router node in the GUI. This is to assist with cross-referencing the information in the these calls. [13081]
• The method api_traffic_egress_router_ipv4_history was fixed to use the <i4> data type instead of <double> so it is consistent with the other api_traffic_*_history methods. [12534]
• The Customer Report APIs now accept more variations in the format of the statistic type parameter: min/minimum, max/maximum, avg/average, and percentile (all case insensitive). [12538]
• The method api_traffic_links was changed to report traffic levels in bits per seconds using a <double> type to avoid overflow. [13144]
• An optional flag parameter was added to the XML RPC API calls api_mp_event and api_mp_event_handle to request that protocol packet events be included in the result. [13320]
• In tables and XML RPC calls, BGP New Announce events can now be selected with the filter expression "eventType new announce". The User's Guide description of the filter expression syntax has been updated to include this addition and to explain the differences among announce, reannounce, and new announce. [13435]
• The XML RPC API call api_vpn_customer_wan_connection_get_config could return empty prefix lists. This is fixed. [13397]

• The order of varbinds in trafficLinkCoSUtilization was wrong, but has now been corrected. [12658]
• False path change traps were emitted for EIGRP topologies because an error in the metric calculation gave the appearance of a change. This is now fixed. [13223]
• When the peering between the EIGRP Route Recorder and its neighbor router went down, no Peering alert was generated. This is now fixed. [13274]

• Accounts configured as "CLI User" privilege were not able to log in on Flow Collectors or Flow Analyzers units. This is now fixed so login is allowed. [12889]
• On the serial console, if changes to the primary ethernet port were declined by entering 'N' when confirmation was requested, the changes were made anyway. Now they are not. [13269]
• Security updates were applied for the following vulnerabilities: RHSA-2009-1148 in httpd; RHSA-2009-1159 in libtiff; RHSA-2009-1206 in libxml2; and RHSA-2009-1204 in apr and apr-util. [13389, 13392,13394, 13395]
• The menu-driven command line interface on the serial console can now have a password set so that login with that password is required to gain access. The default remains that no password is set, so no login is required. Setting of the Master Access password was moved to a new submenu where setting of the new serial console password was added. For both passwords, the method is now to enter the password twice for confirmation, and the characters are not echoed. [13268, 13429]
• Fixed a crash that could affect the GUI or any of the daemons holding a topology model at the time the model is deleted if it included VRF objects that were not auto-discovered. [13416]
• The RouteAnalyzer daemon that produces BGP reports and alerts could crash when the topology hierarchy changed (e.g., when a new protocol area was added or an old one deleted) or when databases that were configured to record were renamed or deleted. These problems are now fixed. [13452, 13035]
• Suppressed some unnecessary log messages that were brand-specific when a reset to factory defaults operation was done. [13345]
• Calculation of the time range for a weekly or monthly traffic report was incorrect when crossing a Daylight Savings Time boundary. This case is now accommodated correctly. [13898]
• Redundant alerts were being issued when one link in a set of parallel links between two routers changed state. Now the alert is issued just for the one link that changed state. [13971]
• When reading the (hexadecimal) serial number of a unit for license checks, the letters are converted to uppercase to match the serial number in the license. [13988]
• The traffic report daemon could crash or be stuck in an infinite loop. This is fixed. [13523, 13943]
• On MPLS WAN systems, the RouteAnalyzer daemon that produces reports and alerts would leak prepared statement handles in the MySQL server and could also crash. [13849]

• The RouteAnalyzer daemon could crash if one IGP process on a router advertised the same prefix with 2 different types (for example, area internal and area external) and an alert was configured for that prefix. This scenario is now supported. [13007]
• Authenticating logins to the appliance using a remote TACACS server with one-time passwords is now supported. The authentication exchange is done only once, then multiple authorization exchanged may be done to determine which user class is authorized for the given account name. [13079]
• The messages displayed during an initial software installation from CD have been cleaned up to eliminate some useless warnings and to avoid inappropriate branding. Some of the changes also apply to messages during a reboot sequence. [13306, 13336, 13378]
• Two problems related to starting up database replication have been fixed. The first would occur on systems that were so close to disk capacity that the topology databases were trimmed to a single week. The second caused a delay of five minutes before replication restarted after reboot. [13354, 13360]
• For the Update All Units feature, some client units might fail to be rebooted without an indication of that error in the log window that is displayed. Now those errors are collected and added at the end of the log. [13370]
• This release fixes crashes in traffic report daemons that occurred when a topology database could not be loaded and after the Static database was trimmed, a crash in the XML RPC Query Server when static routes were updated, and an assert (not fatal) MPLS WAN report daemon that occurred when reports were recalculated after the VPN configuration was changed. [13227, 13321, 13462, 13466]
• The result formats for api_load_topology have been changed to improve the error checking and reporting and make the format more consistent with other XML RPC API calls. The Developer's Guide has been updated correspondingly. [13357]
• If the configuration of the VNC server for Display 1 was set to not allow sharing, the server would fail to start. This is now fixed. [13503]
• When the Event Analysis feature was invoked with pre-filtering of the events, and then a drilldown to Show Events was selected, the pre-filtering would not be applied. This is now fixed. [13444]
• If alerts were configured with rate limits in a suppression specification, the alerts would permanently cease being issued if the rate limit was exceeded. This is now fixed. [12581]
• In the User's Guide, a section title was revised to "Generating VPN Customer Traffic Reports" to be more clear about the purpose of the feature, and in the Administrator's Guide the new console password commands were documented. [13519, 13429]
• The SysKonnect SK-9E92 2-port fiber PCIe card, the Intel Gigabit ET two-port PCIe card, and the Compaq NC7170 Dual Port Gigabit Server Adapter are now supported as option cards. Identification of unconfigured ports on SysKonnect cards was improved.
• The ppgd-trs daemon that is part of the FlowCollector function was leaking memory. This is now fixed. [14163]
• By default, the Traffic Reports page was showing a blank frame for systems configured with only IPv4 traffic and the MPLS WAN feature. Now the Exporting Links report is set as the default report always. [14149]
• If edits were made to add peerings in an OSPFv3 topology, the bandwidth field would not be properly formatted if those edits were exported, causing an error on a subsequent import. The format is now fixed. [14033]
• On the Backup and Restore web page, the renaming from Static/snmp to Collector/base was incomplete in that databases listed from the backup file were shown as Collector/snmp. Now they are shown as Collector/base. [13775]
• On the Traffic recorder configuration page, a note was updated to change "0/0" to "0.0.0.0/0" to be more clear that it is a prefix. [14133]
• In the Flow Collector configuration, the sampling rate configured for each exporter was being ignored so a sampling rate of 1:1 was assumed. The configured sampling rate is now being applied. [14206]
• In Planning mode, if the user tried to change the exporter of a flow, the edit would fail. This edit now works. [14213]

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.