Recently under VIF paths tab, on 3 different UCS domains, I did noticed that some virtual circuits were notified "unpinned".
It was under 3 different UCS domain running 2.1(1a), 2.2(1b) and 2.1(3b).
In order to correct, the issue :
- first time, I have unassociated the Service Profile + re acknowledged the blade + re associated the SP ; I have to do that for few SP from 2 chassis.
- second time, we have reload the IOM-B : for some blades/SP from a same chassis (but not all blade), all vEth/vFC were unpinned for the IOM-B
- the third time, please see the photo in attach, both vFC are unpinned for several SP... it is impossible, the ESXi hosts on the blade do work.... the ESXi 5.1 is configured on BootOnSan.... so the VIF paths must to work correctly.
At present, for this third case, I done any action but it is not clear to have these "unpinned" state.
... it seems to me that it is a cosmetic error
Any idea or any same feedback about unpinned vNIC/vFC state are welcome.
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...