- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- VVol goes Inactive
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2016 08:55 AM
тАО10-05-2016 08:55 AM
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!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2016 10:16 AM
тАО10-05-2016 10:16 AM
Re: VVol goes Inactive
Hi,
Did you already engage support? That would be the first place to reach when having a issue like this.
Bgrds,
Finnur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 02:21 AM
тАО10-06-2016 02:21 AM
Re: VVol goes Inactive
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:15 AM
тАО10-06-2016 06:15 AM
SolutionWhat 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:25 AM
тАО10-06-2016 06:25 AM
Re: VVol goes Inactive
I also should mention that this was for fnic (fibre channel). Not sure if the same applies to iSCSI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:31 AM
тАО10-06-2016 06:31 AM
Re: VVol goes Inactive
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:32 AM
тАО10-06-2016 06:32 AM
Re: VVol goes Inactive
It is FC we are using, so it would apply. Away to verify on the HCL now (if it shows such info).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:36 AM
тАО10-06-2016 06:36 AM
Re: VVol goes Inactive
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:37 AM
тАО10-06-2016 06:37 AM
Re: VVol goes Inactive
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2016 06:49 AM
тАО10-06-2016 06:49 AM
Re: VVol goes Inactive
Great find, also to add on top of that there is the VMware KBA:
The esxcli storage core adapter list command will let you know if your adapter support SLLID.