Installation guide

48 Book Title without trademarks, or an abbreviated book title • March 2008
Workaround –Change the Current Volume Ownership when a “communication
error” is encountered during volume expansion: From the Volumes page, select the
“Specific Volume” and then change the value of the “Owning Controller.”
Changing the Current Volume Ownership will create an Alarm because the volume
is not on the preferred controller. Select one of two actions:
■ Change the Volume back to the original owner after performing the desired
command.
OR
■ Change the Preferred Volume Ownership of the desired volumes via sscs(1m).
Note – For best performance, ensure both controllers are connected during
configuration.
In-band Managed Array Listed as Managed Out-of-band When
Communication is Lost
Bug 6588699 – When an in-band managed array loses communication with
management host, the network address listed in the Storage Summary page displays
as an out-of-band address instead of an in-band address.
Workaround – If communication is lost with the array, view the alarms to determine
if an in-band or out-of-band connection is lost.
Linux (Red Hat) 5.1 Version is Required - 5.0 not Supported
Bug 6661742 – SMagent-LINUX-10.00.A2.02-1.i386.rpm will not load. SMagent is not
supported on Redhat 5.0.
Workaround – The SMagent requires Red Hat 5.1 (also known as “5 update 1”) or
higher.
Network Address Column Shows Change from Out-of-band to In-band
when Registering an In-band Array
Bug 6612214 – When one of the arrays behind an in-band management proxy is
removed in Common Array Manager, the Common Array Manager software will
change the management of the other arrays behind the proxy to out-of-band
management if that path exists. An in-band discovery of the proxy agent would
return them to in-band management in this case.