HPE StoreVirtual 3200

3. Type the command setGossipList node=<IP1>;<IP2>;<IP3> where each IP address is the
first IP address of the bonded interface on each of the storage controllers running managers. See
Prerequisites for changing the IP address of a bond.
4. Type exit to end the SSH session.
5. Repeat the steps for each of the remaining storage controllers in both storage systems, including the
storage controller that is not running a manager.
The setGossipList command will be the same on each storage controller but each storage
controller must be given the updated IP addresses.
Inaccurate power supply failure status and temperature
alarms
Symptom
If one of the two power supplies in a storage system is unplugged, Active Alarms incorrectly report a
power supply failure and a critical temperature alarm. The same alarms are reported twice.
Cause
In an enclosure, both storage controllers monitor the power supplies and both may report the same event.
The storage controller monitoring does not distinguish between a missing power supply and a failed
power supply, and will generate inaccurate messages.
Action
To clear the alarms, plug in the second power supply.
Hardware monitoring and SAS cable checking require the
system clock setting before January 19, 2038
Symptom
If the system clock is set after January 19, 2038, hardware monitoring and SAS cable checking will not
function correctly. As a result, alerts may be generated and appear in the SVMC and in Remote Support.
Action
Ensure that the system clock of the StoreVirtual 3200 Storage system is set to a date before January 19,
2038. This issue will be fixed in a future release.
Verifying Microsoft DSM operations
If you see two devices that are exactly the same listed in the Disk Manager or My Computer, you may not
have the DSM installed or you may not have logged using the DSM. For more information, see Microsoft
DSM information.
140 Inaccurate power supply failure status and temperature alarms