Release Notes

ID Issue Description Workaround/Solution
and what version was
running, or were able to
uninstall the plug-in, was the
original user who was logged
on when the plug-in was
installed.
Corrected in the 3.0.0.1
release
18453 The error message that resulted from executing
the container -- delete --name [container_name]
command when the container was not empty
needed more information.
Corrected in the 3.0.0.1
release
18452 Update the GUI help menu to include other DR
Series system documents in addition to the DR
Series Admininistrator Guide.
Corrected in the 3.0.0.1
release.
18451
A wrong message displayed when you entered
the wrong container name in the connection --
disable command. When you issued a connection
-- disable --name [name of container that does
not exist on the DR] --type OST the following
message appeared: Failed to update connection
entry - Container "use a container name that is not
a container on the DR" is not configured with OST
connection type.
Corrected in the 3.0.0.1
release. The message more
accurately describes the
error condition.
18393
When the machine was down or rebooted, the
usage graph information was not collected and
you saw a blank in the usage graphs upon reboot.
Corrected in the 3.0.0.1
release.
18375 When you widen the scope to over ten hours or
more, the maximum CIFS connections reduced,
and the usage graph statistical output was not
accurate.
Corrected in the 3.0.0.1
release. The graph now uses
MAX aggregate instead of
AVERAGE to calculate max
values. This change was
implemented for all graphs
(not only for CIFS
connections).
18338
After naming a DR and successfully joining the
domain, a Windows server within the domain
using domain credentials could not access DR
containers. DR containers are configured to allow
access to that client; however, you could only
access the container by using DR local
administrator credentials. This was caused by you
renaming the DR during configuration or changing
the name in the GUI or CLI by issuing the #system
--setname --name <with a name exceeding 15
characters>.
When changing the DR host
name, the GUI will display a
message that no more than
15 characters are allowed as
a host name.
18325
When using Advanced Networking and
configuring 2 bonds it showed the same host
name for both IP addresses.
Corrected in the 3.0.0.1
release.
25