6.2.1 HP IBRIX 9000 Storage Release Notes (TA768-96074, December 2012)

which status for all sensors in the array is unavailable. The statuses will be corrected in the
next monitoring polling cycle.
◦ If there is a hardware event involving a fan in a D2700 drive enclosure then the location of
the fan will incorrectly state that it is part of the enclosure’s power supply. The fan is a separate
FRU in the D2700 drive enclosure.
◦ Disconnected SAS cables between D2700 small form factor drive enclosures are not detected
by the hardware. Monitoring software will not report lack of redundancy in connectivity to
drive enclosures that are connected behind the first drive enclosure. If the customer restarts
the other storage controller that has access to the enclosure or removes the other cable to the
enclosure loss of access to storage will occur.
◦ Spurious failure indications and potential system crashes can occur if storage controller or
hard drive firmware is flashed while monitoring is active. Run the hpspmonControl
--pause command on both servers in the couplet before performing the flash operation.
Then, run the hpspmonControl --resume command on both servers in the couplet after
the flash operation is complete.
◦ Disconnecting the cable from the HBA to an MSA or rebooting one or both of the MSA
storage controllers while hardware monitoring is active can result in unexpected hardware
events.
◦ Port monitoring of the HP SC08Ge HBA (3GB) is not functional when the HP SNMP agents
are not running.
• On an IBRIX 9720 or 9730 Storage Platform, when a blade is reseated in the C7000 chassis,
the On-Board Administrator (OA) might allow the blade to be manually powered on before Virtual
Connect (VC) profile is applied. The server might come up with no networking and without any
error in OA. The VC sometimes complains.
• The Active Fusion Manager (FM) might lose track of actively running tasks if the FM on the server
where the specific task coordinator is running is restarted. This situation can happen if the server
has failed over, restarted or if the Fusion Manager itself on that server has restarted.
The following tasks are impacted by this issue:
◦ OnlineQuotacheck
◦ Migrator
◦ SnapReclamation
◦ DataValidation
◦ CaseInsensitive
The following symptoms might be observed:
◦ The task may appear to be hung in the Fusion Manager task display output because it will
only display the last status it received.
◦ Another task of the same type may fail to start on the same file system due to leftover rogue
processes from the previous task.
To resolve this issue:
14 Workarounds