CSCvz62711 - Unexpected BMC reset on Pilot 4 servers

[GeorgePerkins0204]

Is there a fix scheduled for this bug?!

This bug shows up frequently on our system at the current available fix package:

HXDP 5.0(1c)

UCS firmware package 4.2(1m)C

HyperFlex releases combined firmware with HXDP release and vSphere release. Just need to know what version of HXDP to wait for. 

Our HyperFlex M6 clusters throw this error intermittently about 3x per month. Not quite frequently enough for the service desk to recognize it is not critical, too frequent to keep getting a good nights' sleep.  

<failureDetail>
	<lsServer
	agentPolicyName=""
	assignState="assigned"
	assocState="associated"
	biosProfileName="hx-bios-m6"
	bootPolicyName="HyperFlex-m2r1"
	configQualifier=""
	configState="applied"
	descr=""
	dn="org-root/org-Server01/ls-rack-unit-6"
	dynamicConPolicyName=""
	extIPPoolName="hx-ext-mgmt"
	extIPState="pooled"
	fltAggr="0"
	fsmDescr=""
	fsmFlags=""
	fsmPrev="ConfigureSuccess"
	fsmProgr="100"
	fsmRmtInvErrCode="none"
	fsmRmtInvErrDescr=""
	fsmRmtInvRslt=""
	fsmStageDescr=""
	fsmStamp="2022-10-20T17:18:46.155"
	fsmStatus="nop"
	fsmTry="0"
	graphicsCardPolicyName=""
	hostFwPolicyName="HyperFlex-m6"
	identPoolName=""
	intId="464586"
	kvmMgmtPolicyName=""
	localDiskPolicyName="hx-flex-disabled"
	maintPolicyName="HyperFlex"
	mgmtAccessPolicyName=""
	mgmtFwPolicyName=""
	name="rack-unit-6"
	operBiosProfileName="org-root/org-Server01/bios-prof-hx-bios-m6"
	operBootPolicyName="org-root/org-Server01/boot-policy-HyperFlex-m2r1"
	operDynamicConPolicyName=""
	operExtIPPoolName="org-root/org-Server01/ip-pool-hx-ext-mgmt"
	operGraphicsCardPolicyName="org-root/graphics-card-policy-default"
	operHostFwPolicyName="org-root/org-Server01/fw-host-pack-HyperFlex-m6"
	operIdentPoolName=""
	operKvmMgmtPolicyName="org-root/kvm-mgmt-policy-default"
	operLocalDiskPolicyName="org-root/org-Server01/local-disk-config-hx-flex-disabled"
	operMaintPolicyName="org-root/org-Server01/maint-HyperFlex"
	operMgmtAccessPolicyName=""
	operMgmtFwPolicyName=""
	operPersistentMemoryPolicyName=""
	operPowerPolicyName="org-root/org-Server01/power-policy-HyperFlex"
	operPowerSyncPolicyName="org-root/power-sync-default"
	operScrubPolicyName="org-root/org-Server01/scrub-HyperFlex"
	operSolPolicyName="org-root/org-Server01/sol-HyperFlex"
	operSpdmCertificatePolicyName=""
	operSrcTemplName="org-root/org-Server01/ls-compute-nodes-m6-m2r1"
	operState="inaccessible"
	operStatsPolicyName="org-root/thr-policy-default"
	operVconProfileName="org-root/org-Server01/vcon-profile-HyperFlex"
	operVmediaPolicyName=""
	owner="management"
	persistentMemoryPolicyName=""
	pnDn="sys/rack-unit-6"
	policyLevel="0"
	policyOwner="local"
	powerPolicyName="HyperFlex"
	powerSyncPolicyName=""
	propAcl="0"
	resolveRemote="yes"
	sacl="addchild,del,mod"
	scrubPolicyName="HyperFlex"
	solPolicyName="HyperFlex"
	spdmCertificatePolicyName=""
	srcTemplName="compute-nodes-m6-m2r1"
	statsPolicyName="default"
	status="modified"
	svnicConfig="yes"
	type="instance"
	usrLbl="hxdpesxi01"
	uuid="derived"
	uuidSuffix="0000-000000000000"
	vconProfileName="HyperFlex"
	vmediaPolicyName=""/>
	<faultInst
	ack="no"
	cause="equipment-inaccessible"
	changeSet=""
	code="F0322"
	created="2022-11-16T07:43:25.527"
	descr="Server 6 (service profile: org-root/org-Server01/ls-rack-unit-6) inaccessible"
	dn="sys/rack-unit-6/fault-F0322"
	highestSeverity="minor"
	id="863250"
	lastTransition="2022-11-16T07:43:25.527"
	lc=""
	occur="1"
	origSeverity="minor"
	prevSeverity="minor"
	rule="compute-physical-assigned-inaccessible"
	sacl="addchild,del,mod"
	severity="minor"
	status="created"
	tags="server"
	type="equipment"/>
	</failureDetail>

[Riaan van Niekerk · Accepted solution]

According to a recent update on the bug report, this has been fixed on 4.2.2c.

[GeorgePerkins0204]

HXDP 5.0(2c) aka 5.0.2-42548:

• Contains ESXi 7.0 Update 3k 2023/02/21 Build 21313628 is included. 
• Contains support for M6 firmware 4.2(1i), 4.2(1m), 4.2(1n), 4.2(2d), 4.2(3b), 4.2(3d). We are presently on 4.2(1m). I have been monitoring defects, we have noted 5 impacting firmware bugs, only 2 are fixed so far (this one, CSCvz62711 being one of those). 

[Riaan van Niekerk]

We would love to go HXDP 5.0(2c) and the newer (4.2) UCS firmware versions that it supports, but as of today, it is still not a suggested release download yet, and our local Cisco contacts recommend staying with HXDP 5.0(2a) (we are not running it in any stretch environments where there is a big HXDP 5.0(2a) bug).