### Human: Can you tell about Which Alerts Automatically Generate a Support Case with Nutanix Support. ### Assistant: This article provides details about who Nutanix contacts when a case is generated, how to change the contact, and which alerts generate cases.. When enabled, a Nutanix cluster automatically sends alerts to Nutanix Support.Alert cases are raised with Nutanix Support for a subset of alerts that have been identified as being important, so action can be taken on them.Most of the alert cases are created with a P4 priority level, which has a target response time of 24 hours. NodeDegraded and CassandraSSTableHealth are created with a P2 priority level, which has a target response time of two hours.Nutanix has also enabled an automatic first response email for most P4 alerts. If a primary Support Contact is listed for a node, the email is sent to that contact, with Nutanix Support following up on the email within the next two business days.Nutanix sends parts to the Parts Shipment Address listed for the node in the Nutanix Support Portal. It is important to keep this address up-to-date for timely dispatch of parts and prompt resolution of hardware issues.. Who is Contacted?Alert cases are handled by Nutanix Support, who reach out to the primary Support Contact (also referred to as the break/fix contact) associated with the node or cluster in question. For customers with a third-party providing front-line support, it is normal to have a representative from that company listed as the Primary Support Contact.

To Whom Are Parts Sent?By default, parts are sent to the Parts Shipment Address listed on the node's asset details in the Nutanix Support Portal. It is important to keep this address up-to-date for timely dispatch of parts and prompt resolution of hardware issues. Out-of-date addresses may result in parts being sent to the wrong address/person, which results in delays in receiving the parts and getting your system back to a healthy state.

Changing the Contact and Parts Shipment AddressPerform the following to modify the break/fix contact in the Support Portal:

Go to Assets > BlocksSelect the asset for which you want to modify the contact and/or Parts Shipment AddressClick Actions -> Update and specify the new contact/address details

Which Alerts Generate Cases?The following alerts generate alert cases.

Notes:

The table is updated for the latest AOS and NCC releases; earlier releases do not send all of these alerts. Nutanix recommends keeping the NCC version update to the latest release. NCC can be updated independently from the AOS.Alert cases are generated only when the cluster is under an active support contract.You may need to log in to the Support Portal to view some of the KB articles below.As per FA-83, on March 1st, 2021, Nutanix has deprecated the automatic support case creation functionality via nos-alert/nos-asup email (SMTP) notifications in favour of automatic case creation via Insights Discoveries using Pulse.For performing Discovery-based case creation on Nutanix clusters, the minimum NCC requirement is 3.10.x.A1031 HomePartitionUsageHigh and A3038 FsInconsistencyCheck are temporarily disabled and do not generate support cases.

Case Generating Alert Table

 

NameAlert IDDescriptionTypeSFDC Case PriorityKBAlert SeverityAlert TypeMetadataDiskMountedCheckA101055Check that all metadata disks are mountedSWP4KB 4541CriticalNormalCassandraSSTableHealthA21021Health warnings detected in metadata serviceSWP2KB 7077CriticalCluster wideCuratorScanFailureA1081Curator scan has failedSWP4KB 3786CriticalCluster wideDiskSpaceUsageHighA1005Disk capacity is above 90%SWP4KB 3787CriticalCluster wideNodeDegradedA130087One or more critical processes on a node are not responding to the rest of the clusterSWP2KB 3827CriticalCluster wideStargateTemporarilyDownA1030The Stargate process on a node has been down for more than 3 hoursSWP4KB 3784CriticalCluster wideSATADomPECyclesErrorA1180The SATADOM has exceeded a wear thresholdHWP4KB 4137CriticalNormalECCErrorsLast1Day*A1187ECC errors over the last day have exceeded the one day thresholdHWP4KB 4116CriticalCluster wideECCErrorsLast10Days*A1188ECC errors over the last 10 days have exceeded the 10 day thresholdHWP4KB 4116CriticalCluster wideHardwareClockFailure*A1059Hardware Clock FailureHWP4KB 4120CriticalNormalPhysicalDiskBad*A1104A physical drive in the node has been reported as badHWP4KB 4158CriticalNormalDiskDiagnosticFailure*A1139Drive diagnostic has failed.HWP4KB 6287WarningNormalPowerSupplyDown*A1046One of the power supplies in the chassis has been reported downHWP4KB 4141CriticalCluster wideSystemTemperatureHigh*A1012A node in the cluster has an abnormally high temperatureHWP4KB 4138CriticalNormalSATADOMUnreachableA1177SATA DOM in the node cannot be reachedHWP4KB 7813CriticalNormalSATADOMFailedA1165SATA DOM in the node has failedHWP4KB 1850CriticalNormalShellvDisksAboveThresholdA1182Number of Shell vDisks in the cluster is above the thresholdSWP4KB 8559CriticalNormalIPMISELUECCCheckA15039Check for number of UECC errors for last one day in the IPMI SELHWP4KB 8885CriticalNormalLcmFamilyMismatchD3-0035Incorrect LCM family can cause upgrade failureSWP4KB 9898CriticalNormalM2BootDiskFailureA106042M.2 Boot Disk change checkHWP4KB 4874WarningNormalHwRaidCheckFailureA106053Host Hardware RAID status CheckHWP4KB 6627CriticalNormalDiskStatusCheckFailureA106061Disk status check for SATA disksHWP4KB 8094CriticalNormalDiskStatusCheckFailureA106062Disk status check for SAS disksHWP4KB 8094CriticalNormalDiskStatusCheckFailureA106063Disk status check for host boot disksHWP4KB 8094CriticalNormalDiskInodeUsageHighA1027High inode usage on this node may cause cluster performance to be significantly degraded.HWP2KB 1532CriticalCluster uuidCvmBootRaidDegradedA1107The node is operating wih a degraded boot RAID volume on the Controller VM.HWP2KB 2463CriticalCluster uuidStoragePoolSpaceUsageCheckA1128Space usage in the storage pool has exceeded the critical threshold (90% of usable space by default)SWP2KB 2475CriticalCluster uuidNvmeCheckFailureA1196The node is operating with a problematic NVMe driveHWP4KB 3751CriticalCluster uuidStargateMergedvBlockCrashD3-0075Stargate crashed due to merged vblock pointing to non-existing eidsSWP2KB 12431CriticalAlert group and cluster uuidMetadataDiskUnmountedFatalD6-004A metadata disk that is expected to be in-use is no longer mountedSWP4KB 4494CriticalAlert group and cluster uuidDiskRemovalStuckA130156External alert generated by Curator for when Disk removal process is stuck for a long timeSWP4KB 2159CriticalCluster uuidCassandraRingSkewThresholdD3-0114-ACluster performance at risk due to detected Cassandra metadata imbalance on 3 node clusterSWP4KB 1342CriticalCluster uuidCuratorExtentRegionInfoCrashD4-0015Curator has recently crashed due to an extent region having multiple vblocks pointing to the same egroupIDSWP2KB 13306CriticalCluster uuidCuratorMetadataInconsistencyFatalD4-0016Curator scans may crash due to metadata inconsistencySWP2KB 13779CriticalCluster uuidCuratorVblockMetadataInconsistencyFatalD4-0017Curator service has crashed due to inconsistent vblock reference in metadataSWP2KB 13860CriticalCluster uuidDiskOfflineD0-1044Node storage capacity potentially affected due to a drive marked offlineHWP4KB 8453CritcalCluster uuidStargateErasureCodingFTCrashD4-0018Stargate has recently crashed due to two EC strip members found on the same nodeSWP2KB 14286CriticalCluster uuid

ECC Alert Case Creation Logic 


			ECC Discovery Name
			
			Platform
			
			Alert ID
			
			Additional Logic
			
			Case Creation
			
			Discovery Recommendation
			
			KB
			
			D0-1187-UECC
			
			NX platforms
			
			A15039
			
			n/a
			
			Enabled
			
			Replace DIMM
			
			KB 8885
			
			D0-1187-Generic
			
			NX platforms
			
			A1187 / A1188
			
			Alert msg could not be retrieved
			
			Enabled
			
			Troubleshoot DIMM alert
			
			KB 4116
			
			D0-1187-G4G5-BIOS
			
			G4/G5
			
			A1187 / A1188
			
			BIOS < G4G5
			
			Disabled
			
			Upgrade BIOS and BMC to latest version. Do not replace DIMM.
			
			KB 3357
			
			D0-1187-G4G5-DIMM
			
			G4/G5
			
			A1187 / A1188
			
			DIMM CECC error message and BIOS version >= G4G5
			
			Enabled
			
			Replace DIMM
			
			KB 3357
			
			D0-1187-G6G7-DIMM-BIOS
			
			G6/G7
			
			A1187 / A1188
			
			DIMM CECC error message and BIOS version < 41.x
			
			Enabled
			
			Replace DIMM. Upgrade BIOS to latest version
			
			KB 9137
			
			D0-1187-G6G7-BIOS
			
			G6/G7
			
			A1187 / A1188
			
			DIMM CECC error message and BIOS = 41.x
			
			Disabled
			
			Upgrade BIOS and BMC to latest version. Do not replace DIMM.
			
			KB 9137
			
			D0-1187-G6G7-DIMM
			
			G6/G7
			
			A1187 / A1188
			
			DIMM CECC error message and BIOS >= 42.x
			
			Enabled
			
			Replace DIMM
			
			KB 7503
			
			D0-1187-hPPR-Fail
			
			G6/G7
			
			A15040
			
			n/a
			
			Enabled
			
			Replace DIMM
			
			KB 7503
			
			D0-1187-hPPR
			
			G6/G7
			
			A1187 / A1188
			
			DIMM RAS event error message and BIOS >= 42.x
			
			Disabled
			
			Reboot host for hPPR (Hardware Post Package Repair) feature
			
			KB 9137
			

 

PSU Alert Case Creation Logic 


			ECC Discovery Name
			
			Platform
			
			Alert ID
			
			Additional Logic
			
			Case Creation
			
			Discovery Recommendation
			
			KB
			
			D0-1046
			
			All
			
			A1046
			
			n/a
			
			NX Platforms Only
			
			Replace PSU
			
			KB 7386
			
			D0-1046-ENV
			
			All
			
			A1046
			
			PSU State value = 0x0 or 0xb
			
			Disabled
			
			Confirm the power supply is connected to its power source
			
			KB 7386
			

* This is an auto-first response eligible alert.  Where a primary Support Contact is configured, an initial email will be sent.

You can find more information about automatic alerts and the Pulse functionality in Alert and Event Monitoring of the Prism Web Console Guide for your AOS release.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.