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 the FNIC driver 18.104.22.168 which has been unit tested with Netapp and EMC and checked in. We are pushing it through the QA cycle as we speak. This may take weeks - I will give an update once I have a finalized date.
VMware just released a new feature called VMware Virtual Volumes (VVOL) (available in VSphere/VCenter 6.0). This document will help you and the customer understand what it is and how it is supported within UCS. VVol is highly dependent on storage and not so much on compute. So at first we needed to verify if the storage vendor supports it.
Customers have been trying to connect to the VVOL but have not been able to. It turns out that there needs to be an additional capability present on the HBA. It is called second level lun ID (SLLID). This Article will go through how to check if their VIC adapters have this feature available and how to enable it.
Release notes for the VIC adapters at the moment have no documentation over SSLID and if they support it or not. We have reached out to the alias to add this documentation to the release notes since a large number of customers are running VMware on UCS (Flexpod, Vblock, Smartstack). VMware has a KB on this issue located below;
This article gives you a command “esxcli storage core adapter list” which will verify if your adapter has the capability of Second Level Lun ID.
VVOL support is not dependent on a particular compute platform, one of the driver features needed by VVOL is. This results in Cisco having only 4 HBA / CNA adapters that can support VVOL. Based on the VMware compatibility guide (link is also below) it is shown that these are only supported by Cisco 1GigE I350 LOM, UCS VIC P81E, VICm81KR, and VIC-1285 adapters. What was odd are these are all old adapters.
However, The VIC 1340 (in the guise of the MLOM in the b200-M4) shows support for the Second Level Lun ID feature. They just aren’t on the VMware list. As of now FNIC drivers are not supported with SSLID. What it boils down to is that our drivers support the feature, but VMware’s HCL is not up to date on that fact. We are in the process of helping them get the HCL updated.
Hi - I run a lab and noticed after upgrading that the Cisco upgrade to 9.2.1 from 7.0.3.I4.8a where it was corrected in the below bug, seems to exist in the new 9.2.1 code. Before the upgrade to 9.2.1 the fans were running at 4000RPM , after the upgr...
Hi Three CE, CE1, CE2, and CE3 are connected with its PE1, PE2 and PE3 over mpls. We setup the same rt on each PE for CEs to communicate. If we want CE1-CE2 and CE1-CE3 to communicate without CE2-CE3 communication, can we configure it for this only on RT ...
I have two N5K and 2 no of N2K, FEX and VPC configured.
Whenever i connect GLC-TE or any SFP (MM or SM) its not detecting but if i reload the N2K (like power off and ON back) then its detecting. What is the reason and how to fix it.