topic Re: VVol goes Inactive in Array Setup and Networking

VVol goes Inactive

liamgp106 — Wed, 05 Oct 2016 15:55:46 GMT

I upgraded our arrays this week to NimbleOS 3.5 and today I have been starting to look at VVols.

I've followed the steps and watched this video > https://www.youtube.com/watch?v=FEwQYhTYd3U and it all seems to go OK. Then all of a sudden my new VVol datastore shows as 'Inactive' and I can't do anything with it.

Can't find much info out there just now, so wondered if anyone here could shed any light?

We're running ESX 6.0 Update 2 and NimbleOS 3.5. NCM is 3.3.0 and is the ESX6 specific version.

Any help most appreciated!

Re: VVol goes Inactive

Finnzi — Wed, 05 Oct 2016 17:16:58 GMT

Hi,

Did you already engage support? That would be the first place to reach when having a issue like this.

Bgrds,

Finnur

Re: VVol goes Inactive

liamgp106 — Thu, 06 Oct 2016 09:21:10 GMT

No as it's just something I've been looking at on the side and don't have time to spend with support just now.

Just wondered if anyone else had seen the same issue and there was something I was missing.

Re: VVol goes Inactive

jason_crossley — Thu, 06 Oct 2016 13:15:03 GMT

What is your server platform? If you are running a newer Cisco UCS blade and VIC, it does not currently support SLLID which is required for vVol support. Nimble Support and I discovered that last week. There is an open enhancement with Cisco for this feature that has been open already for 9 months.

Re: VVol goes Inactive

jason_crossley — Thu, 06 Oct 2016 13:25:35 GMT

I also should mention that this was for fnic (fibre channel). Not sure if the same applies to iSCSI.

Re: VVol goes Inactive

liamgp106 — Thu, 06 Oct 2016 13:31:24 GMT

Yes it is Cisco UCS. Not so new blades though, we are running B200 M3 with 1240 & 1280 VIC's.

Embarrassingly, I have not checked the HCL, generally with the UCS I just assume it is supported as everything usually is. Is it a software limitation just now? Do you have an enhancement ID request number I can contact TAC with?

Thanks Jason.

Re: VVol goes Inactive

liamgp106 — Thu, 06 Oct 2016 13:32:56 GMT

It is FC we are using, so it would apply. Away to verify on the HCL now (if it shows such info).

Re: VVol goes Inactive

liamgp106 — Thu, 06 Oct 2016 13:36:07 GMT

I've found this article Jason. Seems you will be correct and I'll be hitting this issue with SSLID not being supported. Good work!

https://supportforums.cisco.com/discussion/12597111/ucs-support-vmware-virtual-volumes-vvol-hba-driver-update

Re: VVol goes Inactive

jason_crossley — Thu, 06 Oct 2016 13:37:54 GMT

So definitely check the HCL. I made the same mistake thinking current gen hardware would come enabled with a feature they have known was coming for 4 years.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux64473/?referring_site=bugquickviewredir

Re: VVol goes Inactive

mblumberg16 — Thu, 06 Oct 2016 13:49:22 GMT

Great find, also to add on top of that there is the VMware KBA:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2114975

The esxcli storage core adapter list command will let you know if your adapter support SLLID.

Re: VVol goes Inactive

liamgp106 — Thu, 06 Oct 2016 14:03:34 GMT

Yep, I can confirm that the command does not show the Second Level LUN ID for either of our UCS VICS

Thanks again Jason! I've opened a case with TAC and referenced the bug ID.

Re: VVol goes Inactive

PeterCNZ — Mon, 13 Mar 2017 03:37:51 GMT

Looks like it is supported now in the latest Cisco VIC FNIC driver, 1.6.0.33 released on the 22nd of Feb 2017.

These are the release notes

New Features:
- Supports Secondary Lun ID (VVOL)

Bugs Fixed (in fnic 1.6.0.33 since fnic 1.6.0.28)
CSCux64473 : Request for Virtual volume support in ESXi fnic driver

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX60-CISCO-FNIC-16033&productId=491