HP StorageWorks Enterprise File Services WAN Accelerator Manager 2.1.5 Release Notes (AG424-96002, February 2007)

HP StorageWorks Enterprise File Services WAN AcceleratorManager 2.1.5 release notes 5

Resolved issues for the WAN Accelerator Manager (WAM)

Resolved issues since WAM 2.1.4 #21

13290 Fixed adding and removing profiles on profile send page. Problem was that if a profile is added,

then removed, it may still be pushed even if the web interface does not show that it was pushed.

Resolved issues since WAM 2.1.3 #19

8775 Upgrading a client side and server side HP EFS WAN Accelerator together no longer causes the

image fetch to fail.

10997 Fixed a problem when contacting an HP EFS WAN Accelerator running 2.1.8.

11035 Fixed a problem where deleting an existing profile causes "[web.ERR]: ts_str(), tstring.c:1374,".

11261 Fixed a hyperlink error on the shutdown appliances page.

11386 Fixed a problem where checking the checkbox for "clear hosts before sending" when checked

always causes the configuration push to fail.

11518 The log rotation criteria for "Frequency" now works.

11740 Fixed a problem that occurs when upgrading a legacy appliance.

12206 Updated time zone information for 2007 changes in US daylight time.

12243 Updated OpenSSH from 4.3 to 4.4 prevent CVE-2006-5051 DoS attack.

Resolved issues since WAM 2.1.3 #16

7369 The Throughput report graphs are line plot graphs. You might encounter a report where the graph

appears to be missing.

Assume a case the following sample set:

0 1 2 0 0 0 4

The ascii line plot would look like this:

In this scenario above, note that the last sample '4' is a vertical line. In this particular case, our graph

currently has an issue such that the black border that surrounds the graph is drawn on top of the vertical

line, so it looks like there is no value when there is value.

The reporter of the bug saw that the table claimed a 7.8Mbps peak, but that the graph showed only a

2Mbps peak. The 7.8Mbps sample point was the last sample and the previous sample before this peak

had been 0Mbps; thus, there was a vertical line that was obscured by the graph border.

2/| |

1___/ |_______|

0 1 2 0 0 0 4