Release Notes
Document 5502229 Rev B
July 2008
4
Known Issues
PCR17770 — DFU utility doesn't FUP from v53 to T60 SL3 for LTO3 or LTO4
0
On systems with Quantum LTO3 SCSI drives (v2023) and LTO3 HH SAS drives (v2076),
when performing an autoloader code update over the primary interface using the DFU
application versions 1.3.9 or 1.3.10, the code update will fail. To perform the update, use
the RMU interface.
Remote Management Unit
(RMU)
0
PCR17892 — OCP Configuration->Ethernet->Subnet mask doesn't match GUI
0
Under certain conditions, when a user changes between using IPv4 DHCP and static IPv4
addressing, the subnet mask values shown on the OCP and RMU may differ from each
other. The OCP screen is at Configuration->Ethernet->Subnet Mask, and the RMU page is
at Configuration->Networking->Current Network Parameters. After rebooting the
system (e.g. RMU Diagnostics page->Autoloader Reset), the subnet mask values will
resynchronize.
PCR17957 — Client Authorization Control - No error message for invalid characters
and bogus address is saved
0
On the RMU page, Configurations->Security, under the heading “Client Authorization
Control,” be sure that any IP address values that are entered contain valid characters. If
not, the invalid characters will simply be ignored, and the remaining valid characters will
be taken as the IP address. There will be no warning given to the user. This may or may
not produce intended results for the user.
PCR17976 — RMU Client Authorization Control Reset button does not gray out/
Enable IPV4/IPV6 address fields properly
0
On the RMU page, Configurations->Security, under the heading “Client Authorization
Control,” if the user chooses to reset the IP address fields, the user must press the “Reset”
button twice in order to see proper gray-out behavior of any fields under a disabled
control address range.
PCR18052 — After enabling TLR from RMU library DHCP address set to 0.0.0.0
0
On the RMU’s Configuration page of LTO3 HH SAS and LTO4 HH SAS systems, when
the user enables or disables the SAS Transport Layer Retries (TLR), the user is requested
to power cycle the system. After power cycling, the user may be unable to connect a
browser to the system if it is configured to use DHCP address assignment. If this is the
case, one can use the OCP’s Status->Ethernet screen to check the IP address; it may be
0.0.0.0. If so, simply power cycle the system to recover the IP address.
PCR18216 — Setting static site local address to current router assigned
mishandled
0
With an existing static site local IPv6 address set, when setting the IPv6 address to a new
site local address that is the same as the current router-assigned site local address, the new
address is rejected without giving the user an error message that the address was rejected.
Also, when the new address is rejected, the prior old static site local address is removed
from the “Current Network Parameters” section on the Configuration page and is no
longer functional. To restore this site local connectivity, either clear the IPv6 address from
the RMU field and submit or enter a non-router-assigned address value.
