Nutanix Advisory SATADOM Failure Issue found

Recently nutanix engineering team found an issue in specific SATADOM model & firmware root cause of this issue is “AC power cycle of node can result in SATADOM failure“

Versions Affected:
SATADOM model 3IE3 using firmware S160130N or S560301

Description:

Nutanix has identified an issue with the S160130N and S560301N firmware on 3IE3 model SATADOMs which can cause the device to fail after an AC power cycle of the node.
To determine if the SATADOM is affected by this issue, ensure you are running NCC 3.7.1 or higher, login to any CVM in the cluster and perform the following NCC check:

 ncc health_checks hardware_checks disk_checks sata_dom_fwv_check

If the output returns anything other than PASS, follow the steps in the Resolution section below. Please refer to KB 4395 for more details on this NCC check.

Resolution:

This issue is fixed in both the S671115N and S670330N SATADOM firmware versions. Customers are advised to use a minimum of LCM 2.1.6835 or LCM 1.4.5563 to upgrade the SATADOM firmware. Please refer to KB 7194 for more details.
Customers will need to upgrade both LCM and Foundation versions to a minimum of those listed in the table below before upgrading the SATADOM firmware. Please reference KB 5373 for additional information on
upgrading LCM and the documentation here for upgrading Foundation.

Clusters already running LCM 2.x with Auto Update enabled, will be automatically upgraded to this refresh upon its release. The LCM Auto Update status is found on the LCM page in Prism via the Options > Advanced Settings menu. Review the LCM documentation here for instructions on how to enable the LCM Auto Update capability.
Nutanix Field Advisory #66 v1

# Give Your One-Click Contribution 🙂
To Follow my Blog, Social networks, one Comment, one Like, one Share !
Your valuable query & feedback will encourage me to write more latest post on cutting edge Hyperconverged HCI Technology.
…………………………………………………………………………………………………….
Thank you to visit my blog enjoy Nutanix with HyperHCI
…………………………………………………………………………………………………….