Quantcast
Channel: ONTAP Discussions topics
Viewing all articles
Browse latest Browse all 4949

ONTAP Select 2.6 : cluster create failed (Invalid/missing disk 'scsi0:0')

$
0
0

Hi all, 

 

As I've stated in other post (cf https://community.netapp.com/t5/Data-ONTAP-Discussions/ONTAP-Select-Cannot-create/td-p/131724 ) I'm in a process of evaluating  Ontap Deploy 2.6.

But each time I try to deploy a simple "single node evaluation cluster " , the cluster deployment fails with same message : ".... create failed. Reason: Error during configuration of vnics:  InvalidRequestFault.

 

Esxadmin.log contains some errors:

[INFO] [Thu Nov 23 05:43:31 2017] [8815] Configuring Network ...
[INFO] [Thu Nov 23 05:43:31 2017] [8815] Error encountered while creating VM
[INFO] [Thu Nov 23 05:43:31 2017] [8815] [13] InvalidArg: <scsiC:N> invalid - Invalid/missing disk 'scsi0:0'
[ERROR] [Thu Nov 23 05:43:31 2017] [8815] [51] Err: Error during configuration of vnics: InvalidRequestFault

 

 

 

Our Vmware environment is as follows:

  • vsphere (vcenter managed) version = 6.0.0 build 4510822 
  • Vcenter version : 6.0.0 3634793
  • Each tested host has 2 Distributed vswitch. One with 2*40G uplinks, and one with 2*10G uplinks. Both uplinks are configured in LACP mode
  • Ontap Select networks are using 2 distributed port group: one for external/management network, and one for internal (only used for HA pair) . Both distributed PG comes from same distributed vswitch (the one using 2*40G LAG)
  • local datastore tested comes from 2 local SAS disks, grouped in a RAID 1 LV managed by a Smart Array P840ar.
  • SAN datastore tested comes from external LUN accessed by Fiber channel
  • all our hardware stack (servers, san switchs, external array, bios firmware, etc ...) is fully supported by Vmware and in the compatibility matrix. 

 

 

FYI, below  is an example of CLI commands I used for a "single node eval cluster deployment " : 

  • host add --host-id ESXHost01.lan--username vsphere.local\\myuser --password mypassword --vcenter VCenter01.lan
  • host configure --host-id ESXHost01.lan --location MyLocation --storage-pool SAN_Datastore_01 --eval --management-network NFSDATA_PG --data-network NFSDATA_PG --instance-type small --capacity-limit 3072
  • cluster create --name ONSCluster01 --cluster-mgmt-ip A.B.C.D --netmask 255.255.255.0 --gateway A.B.C.E --ontap-image-version 9.2P1 --node-names ONSNode1 --node-hosts ESXHost01.lan --node-mgmt-ips A.B.C.F

where :

  • ESXHost01.lan is the ESX host where I want to deploy Ontap Select Node n°1. This ESX is part of a Vsphere Cluster (this ESX, and the associated Vsphere Cluster, is also a production one, with other working VM on it)
  • VCenter01.lan is the Vcenter managing ESXHost01 (this Vcenter is a production one, managing many ESX clusters )
  • SAN_Datastore_01 is the Shared storage datastore (from an external array accessed by FiberChannel) 
  • NFSDATA_PG is the Distributed PortGroup to be used (this DPG is a production working port group, with other working VM using it)
  • ONSCluster01 is the the Ontap Select cluster name (the name is already registered in the .lan DNS domain) 
  • ONSNode1 is the the Ontap Select cluster name (the name is already registered in the .lan DNS domain) 

 

 

What we have tested so far:

  • We have tested Ontap Deploy 2.5 and 2.6 without any improvement 
  • wa have tested with Local Datastore and SAN Datastore without any improvement 
  • we have tested from GUI and from CLI without any improvement 

 

We don't know what to test anymore and are about to give up with Ontap Select (and replace it with a non Netapp solution). So if someone has a new idea it is the moment to tell us :-) 

 

Thanks. 

 

Regards

 

Pierre. . 

 

 

 

 

 

 


Viewing all articles
Browse latest Browse all 4949

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>