We were looking through our environment in OCI to see if we had any disks showing up with a status of "Failed". For our NetApp and EMC VMAXes all of the disks show up as either "Normal" or "Failed". However, for all of our VNXes and CXes, the only status that is given is "Other" and there is no Normal/Failed status shown.
Is this a limitation of NaviSECCli or possibly some parameter of NaviSECCli that is not being called by OCI? (i.e. naviseccli.exe faults -list)
I may have answered my own question here but just wanted to confirm.
Our historical experience with both naviseccli.exe for Clariion/VNX for block arrays, and SSSU.exe for HP Eva, is that when disks die on these platforms, their presence disappears from the CLI output we have historically gathered. On platforms like this, you will see OCI's changes view show a change showing raw capacity of the array shrinking, because it is as if someone unplugged a disk from the array, and ran down the hall with it, cackling maniacally.
I can file a RFE for us to look into adding that -fault CLI command. Do you have any example output of it from when a dead disk is present?
Another challenge for OCI is that sometimes arrays cannot tell us everything we need to know about a dead disk - it may not be able to report the model/capacity/etc of it.
Thanks a lot. Yeah, I gathered that might be the case after I went and read in the OCI Operations Guide about what NaviSECCli commands were getting passed. I'll do an RFE. It would be nice to be able to dashboard that stuff. We have full dial-home on our arrays but it's always nice to verify. Also, our very old CXs are off of mainline proactive support so we have to keep an eye on those ourselves.