Any idea is UCS 2.0(2r) is still having the old bug of 2.0(1#)? After upgrading to UCS 2.0(2r), apparently some of the UCS vNICs have been renumbered as seen in ESXi 5.
This is a full-width blade with 2 adapters.
I have been researching and it looks like 1 way is to edit esx.conf file to put the vmnic back to their original number.
Other option is to use vNIC/vHBA placement policy, but my question is how to do this? Will it work as in UCS, it is still the same old vNIC and vHBA. IT is the VMware which we have seen it being renumbered.
Appreciate some authoritative advices from Cisco guys or someone else.
If this is a full width blade, I will assume it is a B250, in that case the bug ID is CSCts96949.
In any way, this should be fixed on 2.0(1q) and above. If you have upgraded all the UCS system to 2.0(2r) and the issue remains, it seems something else is going on, but can still try to modify the esx.conf file.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...