ChrisOk
Contributor
Contributor

NSX-T Upgrade 3.1.1 => 3.1.3.1: PSOD on ESXi host 7.0.2

Dear NSX-T community,

updating our edges from NSX-T 3.1.1 to 3.1.3.1 worked without any problems. No errors at post checks at all.

The update ran on several hosts without any problem afterwards either until one host stopped with a PSOD:

TEs:0xB1B57bB027;0xc169463007;0x0;
r0=0xB001003d cr2=0x27 cr3=0x94614000 cr4=0x10216c MS=06/55/4 uCade=0x2006a09

ax=0x4321Bd20d0c0 rbx=0x4321Bd20d0c0 rcx=0x27
dx=0x42002b42b7b7 rbp=0x4321Bd21590B rsi=0x0
di=0x17 rB=0x100000000 r9=0x0
10=0x0 r11=0x100000000 r12=0x0
13=0x4 r14=0x4321Bd20d140 r15=0x0
CPU5:2101265/vMnic7-pallWarld-0-0x4301d3ca7200
CPU 0: SSSSUSUUSSUSUSSSSUSSSSUSSSSSSUUSSSUSSSSI
ade start: 0x42002b400000 VMK uptiMe: 4:00:16:11.720

· x453a1229b63B:[0x42002b500ba01MCS_DaAcqWriteLackWithRA@vr􀀗kernelnnaver+0x30 stack: 0x42002cd99a75
· x453a1229b640:[0x42002b42b7c1]vMk_SpinlackWriteLack@vMkernelnnaver+0x16 stack: 0x4321Bd215900
· x453a1229b650:[0x42002cd99a741BridgeSyncFdbEntry@(nsxt-vdrb-174B3060)D<Nane>+0x19 stack: 0x45baBbr16206
· x453a1229b670:[0x42002cdBd99a1BridgeLearnFdbEntryByMac@(nsxt-vdrb-174B3060)D<Nane>+0x2Br stack: 0x84000013000000ra
· x453a1229b6d0:[0x42002cd9165d1BridgeFarwardOnePkt@(nsxt-vdrb-174B3060)D<Nane>+0x5e6 stack: 0x4321Bd2111d0
· x453a1229b7c0:[0x42002cdd63551VdrEtherlnput@(nsxt-vdrb-174B3060)D<Nane>+0x52 stack: 0x0
· x453a1229b7r0:[0x42002cde5Bc31VdrPracessPackets@(nsxt-vdrb-174B3060)D<Nane>+0x1aB stack: 0x45ba5c967dB0
· x453a1229ba10:[0x42002b60Bc4d110Chain_ResuMe@vMkernelnnaver+0x2c6 stack: 0x4306de50e230
· x453a1229bab0:[0x42002b64cB271Part0utput@vMkernelnnaver+0x34B stack: 0x20
· x453a1229bb40:[0x42002b6B61651vMk_Part0utput@vMkernelDnaver+0xd6 stack: 0x84000013
· x453a1229bb90:[0x42002cba9a0B1VSwitchFarwardLearParts@caM.vMware.vswitchn1.0.7.0.17483060+0x235 stack: 0x0
· x453a1229bc10:[0x42002cbb04b91VSwitchPartDispatch@caM.vMware.vswitchn1.0.7.0.174B3060+0x9Ba stack: 0x0
· x453a1229be70:[0x42002b64c9421Part_lnputResuMe@vMkernelnnaver+0x10b stack: 0x42002b64c931
· x453a1229bec0:[0x42002b5d57Br1Net_AcceptRxList@vMkernelnnaver+0x264 stack: 0x4316e12c5220
· x453a1229br70:[0x42002b6B47751NetPallWarldCallback@vMkernelnnaver+0xc2 stack: 0x31
· x453a1229bre0:[0x42002b7B1ead]CpuSched_StartWarld@vMkernelnnover+0xB6 stack: 0x0
· x453a1229c000:[0x42002b4c2c231Debug_lslnitialized@vMkernelnnover+0xc stack: 0x0
ase rs=0x0 gs=0x420041400000 Kgs=0x0
a place an disk ta duMp data.
inalized duMp header (15/15) FileDuMp: Successrul.
apart rar reMate debugger. "Escape" rar lacal debugger.

 

On NSX-T manager the error message

"Unexpected error while upgrading upgrade unit: Install of offline bundle failed on host 90da9c5a-d282-525d-14a2-123424-c12a7 with error : VI SDK invoke exception:java.rmi.RemoteException: VI SDK invoke exception:org.dom4j.DocumentException."

Googling around a only find some old posting concerning NSX-T 2.5. So, what might went wrong?

 

 

0 Kudos
0 Replies