IBM Storwize V3700: Noisy Powersupply

By | 10/11/2015

UPDATE 9/3-2016:

IBM has a KB for this (This is from IBM support) – remember use this at own risk :):

The command to reset canisters (which usually helps) is:

svctask chenclosurecanister -reset -canister 1 EnclosureID
svctask chenclosurecanister -reset -canister 2 EnclosureID

in this case, the only enclosure in system is “1”

so:

svctask chenclosurecanister -reset -canister 1 1
svctask chenclosurecanister -reset -canister 2 1

Note that you should wait 30 minutes between canister 1 and canister 2
reset. Also multipath needs to be working.

If this does not help, please reseat the power supply(s)

Fan speeds are not directly visible from logs, however this is a known
issue in enclosure management firmware.

UPDATE 8/12-2015: This issue fixed in version 7.6.0.0 😉

During the last monts I had some customers with V3700 SAN, complaining about suddenly noisy power supply’s, and NO errors on the GUI or event logs.

All running firmware 7.5.0.3.

In all occurances, it was the right PSU (Seen from the front), that was running at almost full fan speed.

A reseat of the PSU (Can be done as hotswap if you are on 7.5.x firmware), made no difference.

The fix was to make a case at IBM Service, and get a new PSU ordered.

Once delivered, the PSU is swapped with the new one and after 2 minutes the FANS spins down to normal level.

The old PSU is returned to IBM.

Case closed 😉

 

8 thoughts on “IBM Storwize V3700: Noisy Powersupply

  1. devnull

    I suspect “7.5.0.6” is a typo did you mean “7.4.0.6”?
    (At the moment the latest 7.5 I can find is “7.5.0.3”, but there is a “7.4.0.6/7” available)

    Reply
  2. engedib

    7.6.0.1 is just out, it has the fix for the volume extent bug, and it corrects the noisy fan issue.
    However you will need to have 8GB cache / canister to do the 7.6 firmware upgrade.

    Reply
  3. engedib

    Hi Martin,

    Yes your link is fine, just check IT10470 at the bottom.

    Cheers,

    Reply
    1. Martin Post author

      Ahhh!

      It was fixed in 7.6.0.0 not 7.6.0.1 which I searched for 😉

      Thnaks

      Best regards
      Martin

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *