05-20-2011 08:17 AM - edited 03-01-2019 09:55 AM
After installing ESX on UCS blade ( adapter type is Palo, number of nics is 2) sometimes I see that the uplinks are vmnic2 and vmnic3 (output of esxcfg-nics -l)
Where are the output of esxcfg-vswitch -l shows uplink as vmnic0 and it also throws a warning saying vmnic0 does not exist.
This does not happen all the time. Anyone know why this could be happening?
Solved! Go to Solution.
05-20-2011 08:50 AM
I've seen this happen quite a bit when you don't have the nics as the first devices in the vNIC/vHBA Placement. By default we put the HBAs first sometimes ESX doesn't like this and will put the NICS as vmnic2 and 3. If you move the nics above the HBAs they come in as vmnic0 and vmnic1. I always reorder and put my nics before my storage.
louis
05-20-2011 08:50 AM
I've seen this happen quite a bit when you don't have the nics as the first devices in the vNIC/vHBA Placement. By default we put the HBAs first sometimes ESX doesn't like this and will put the NICS as vmnic2 and 3. If you move the nics above the HBAs they come in as vmnic0 and vmnic1. I always reorder and put my nics before my storage.
louis
05-20-2011 08:59 AM
Thank you. After I manually changed the order of vnics before HBAs it came up correctly. What bugs me is that, it is not consistent and it only happens some times. Meaning even when the HBAs are before vnics it works sometimes.
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