
10
Sun StorageTek 2500 Series Array Release Notes • April 2007
Sharp Edges and Corners on Array
Bugs 6540408, 6538961, 6538960 -
Watch out for sharp corners and edges on:
■
The Controller Module (corners)
■
Power Modules (corners)
■
Tray edges (chassis ears edges)
Workaround –
Handle the array carefully to avoid the sharp corners and edges.
Upgrading IOM Firmware May Fail During Heavy I/0
Bug 6507700
– IOM firmware upgrades may fail when the array is servicing a heavy
amount of host IO.
Workaround
– No IOM upgrades are scheduled at this time. If one occurs, schedule
a maintenance period of low activity in order to execute the upgrade process.
If the upgrade fails, reset the controllers before updating the IOM firmware again.
Upgrading IOM Firmware Can Result In Failback Failure
Bug 6509762 -
After a firmware upgrade to an Input-Output Module (IOM), the
array will display a Check Condition - Microcode Changed message on all hosts.
After a firmware upgrade, an automatic failback was generated. When the switch
port connecting the data host was enabled, the auto failback failed, indicating that it
did not process the MICROCODE_CHANGED message.
Workaround
– No IOM upgrades are scheduled at this time. If one occurs, there are
two workarounds:
1) Perform a manual failover. The issue will not happen.
2) After updating the IOM firmware, manually forcing a failover and failback of all
effected LUNs on any mapped Solaris host will clear out the condition.
Failover May Generate False Error Messages
Bug 6509331
– In Solaris, under heavy data traffic, host-initiated failover may
generate error messages in /var/adm/messages even though the failover is
successful.
Workaround
– In the CLI, use the Solaris
luxadm
command to verify that the
failover was successful.