05-24-2024 03:19 AM
at
* some Service-Profiles
did UCS-Manager
* double each VIF
so we have
* 2x VIFs per configured vNIC or vHBA
... causing 50% of those VIFs to be (of course) "down" since the OS doesn't detect and initialize them...
Did anybody (no match at Bug-Toolkit for my searches at least) experience this behaviour before?
# show service-profile circuit server 2/3 | no
Service Profile: **ORG**/**SP**
Server: 2/3
Fabric ID: A
Path ID: 1
VIF vNIC Link State Oper State Prot State Prot Role Admin Pin Oper Pin Transport
---------- --------------- ----------- ---------- ------------- ----------- ---------- ---------- ---------
1237 vNIC_FIA_10G_01 Down Link Down 0/0/0 0/0/0 Ether
1238 vNIC_FIA_10G_02 Down Link Down 0/0/0 0/0/0 Ether
1239 vNIC_FIA_10G_03 Down Link Down 0/0/0 0/0/0 Ether
1243 vHBA_FIA Down Link Down 0/0/0 0/0/0 Fc
1245 vNIC_FIA_10G_01 Up Active No Protection Unprotected 0/0/0 0/0/1 Ether
1246 vNIC_FIA_10G_02 Up Active No Protection Unprotected 0/0/0 0/0/1 Ether
1247 vNIC_FIA_10G_03 Up Active No Protection Unprotected 0/0/0 0/0/1 Ether
1251 vHBA_FIA Up Active No Protection Unprotected 0/0/0 1/0/29 Fc
9435 Down Link Down 0/0/0 0/0/0 Ether
9443 Up Active No Protection Unprotected 0/0/0 0/0/0 Ether
Fabric ID: B
Path ID: 1
VIF vNIC Link State Oper State Prot State Prot Role Admin Pin Oper Pin Transport
---------- --------------- ----------- ---------- ------------- ----------- ---------- ---------- ---------
1240 vNIC_FIB_10G_01 Down Link Down 0/0/0 0/0/0 Ether
1241 vNIC_FIB_10G_02 Down Link Down 0/0/0 0/0/0 Ether
1242 vNIC_FIB_10G_03 Down Link Down 0/0/0 0/0/0 Ether
1244 vHBA_FIB Down Link Down 0/0/0 0/0/0 Fc
1248 vNIC_FIB_10G_01 Up Active No Protection Unprotected 0/0/0 0/0/1 Ether
1249 vNIC_FIB_10G_02 Up Active No Protection Unprotected 0/0/0 0/0/1 Ether
1250 vNIC_FIB_10G_03 Up Active No Protection Unprotected 0/0/0 0/0/1 Ether
1252 vHBA_FIB Up Active No Protection Unprotected 0/0/0 1/0/29 Fc
9436 Down Link Down 0/0/0 0/0/0 Ether
9444 Up Active No Protection Unprotected 0/0/0 0/0/0 Ether
3 from ~20 Service-Profiles (all SPs bound to the same SP-Template) are affected:
* all other SPs list their vNICs only once as expected
...better ideas than
(a) placing hosts in ESXi-maintenance mode and
(b) un- and re-assign SP-to-Blade?
05-27-2024 11:26 PM
What works for us is reacknowledging the server. Slightly less complex than disassociating and reassociating? I would love to have a more elegant and non-disruptive workaround.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide