Unsolved
This post is more than 5 years old
2 Posts
0
5306
February 19th, 2019 01:00
SMI-S Provider, SCv3020 SAS and SC-VMM
I am attempting to set up a new virtual farm. The farm has three Dell R630 servers and a Compellent SCv3020 disk array, attached to the virtual hosts via SAS.
The farm is running Hyper-V on Windows Server 2019 and I'm managing the cluster using System Center Virtual Machine Manager v1807.
Ideally, I'd like to be able to manage the Compellent array through SCVMM as well so to that end, I have installed the Dell Data Collector on a VM and connected it to the array. I have enabled SMI-S on the data collector, created a user for SMI-S on the data collector and assigned it to the array. I have created a connection to data collection from SC-VMM in the Fabric/Storage/Providers section, created a storage classification for it and assigned it to the folder in SC-VMM that the cluster is in.
If I go to the Fabric/Storage/Providers section inside SCVMM, I can click on the "Create Logical Unit" button and create volumes on the array so SC-VMM is talking to the data collector which in turn is talking to the array. However, I think I must be missing something because when SCVMM creates the volume, it comes back with the following warning:
Warning (26129)
Storage logical unit Test2 has been allocated to host group All Hosts\Knights\Hyper-V where none of the hosts in host group has access to storage array Knights Virtual Storage SAN.
Recommended Action
Give access to at least one host in the host group to the array through zoning.
If I go to Fabric/Servers/Folder, get the properties of the cluster or a server in the cluster and go to available storage, no volumes show as available. If I press the Add button and attempt to create a volume from there, the storage pool that I created doesn't appear, see screenshot:
No pools
I've clearly missed a step but I can't see what it is. Can anyone help?
DELL-Sam L
Moderator
•
7.6K Posts
0
February 19th, 2019 09:00
Hello IanNorth,
I am not seeing that SCVMM showing as supported for 2019 on a SCv3020. If you look at the Storage Administrator guide for 2018, on page 27 it list out compatibility for 2012, 2012 SP1, 2012 R2, and 2016. https://topics-cdn.dell.com/pdf/dell-storage-manager_administrator-guide3_en-us.pdf
I am not sure if the issue is with some change in setting or a change in 2019.
Please let us know if you have any other questions.
DELL-Bob Mi
2 Intern
•
230 Posts
0
February 23rd, 2019 09:00
Here is a link to the most recent version of Dell EMC SC Series Storage and SMI-S Integration with Microsoft SCVMM
https://downloads.dell.com/solutions/storage-solution-resources/SC-Series-and-SMI-S-Integration-with-SCVMM-(CML1003).pdf
Please follow the Prerequisite steps checklist on page 9.
My colleague had sent you a link to the Storage Administrator guide for 2018. Here is a link to Dell SC Series Storage and Microsoft Hyper-V: https://downloads.dell.com/solutions/storage-solution-resources/Dell%20SC%20Series%20Storage%20Best%20Practices%20for%20Microsoft%20Hyper-V%202016%20(CML1009V6o).pdf
To my knowledge there is no change between server 2016 and server 2019, but one issue one user hit is a problem with TLS1.2
https://www.dell.com/community/Compellent/Add-CT-SCv3020-to-SCVMM-Fabric-SSL-Error/m-p/7186181#M2674
SuhasJ
1 Message
0
April 18th, 2019 11:00
Hello @IanNorth, hope you got your answer for this and I think you must have resolved why this warning is appearing on the SC-VMM.
I am just keen to share my observation here, the windows server 2019 OS had a similar issue on my setup as well, hence I recommend to use a 2016 server OS and try the same operation and if that is working, this can well be an issue with the windows patch.
If this is the scenario you encounter just upgrade the Windows server 2019 OS to the latest patch and that should fix the issue.
Kindly let me know if the solution to this issue was different.
-Suhas
IanNorth
2 Posts
0
July 25th, 2019 05:00
Coming back to this a few months down the line...
We have four SCv3020 arrays attached to Windows Server 2019 Hyper-V clusters. Two of the arrays are iSCSI, two of them are SAS. They are all managed by the same installation of SCVMM, currently running SCVMM 2019. The servers are all on the same patch level,
The iSCSI ones work as expected with the SMI-S connector, I can create volumes, assign them to the cluster and store virtual machines on them. The SAS ones don't want to know.
MattO-ARN
1 Message
0
August 22nd, 2020 20:00
Im having the same issue. We have 5 x 3020 and 1 x 5020 on our DSM
5020 works fine and maps as a fibre array, however the 3020 does not map as a sas array.
This is then not getting the WWN to map the devices.
Any have a work around?