There is summary screen confirming our configuration before we see our created NAS server. I have configured my domain and entered both my Lab DNS servers: I also do not need Unix Directory, so I next on this. My share is only going to be used by ESXi so I am not setting up a Windows share. Now we need to create a NAS server, this is on a new subnet to my previous 192.168.199.0 network. This refers to the part above where I allocated the 2nd and 3rd interface to my VSAN port group, and it looks like it was auto configured. The disk I added to the VM previously is now visible here, and as its an SSD I am adding it to the performance tier. NTP servers are fairly self explanatory and in my case a reboot was required, but as I am half way through the configuration I elected to set the NTP servers and reboot after the initial configuration. You can install a license here (available from ) (default credentials: admin/Password123#) we now need to configure the disk using Unisphere, this is the IP address we set up earlier in the OVA deployment.I have again used thin provisioning as I am low on space, and I have specified a different datastore than the system disks. Once the OVA is deployed and running we need to add a disk to be used for our user data, this is done by adding a 4th disk to the vVNX (first 3 are used for system) the 4th disk should be be on a different datastore. Deployment will take a while and you can see the status of the initial start up by checking the console. Here is a look at the switch I am connecting the vVNX too, not the 3 hosts that previously used VSAN on this port group.ħ. Here you need to choose 2 networks that will be used to present NFS storage to your ESXi hosts, and 1 for management which should be self explanatory.I had an existing port group used for VMware VSAN that I used previously used that.ĥ. I am putting this in my Management Cluster (Recommended)ģ.Despite the recommendation from EMC I am going to thin provision mine as this will not be running many workloads and this is only a Lab.Ĥ. This is really very simple if you have deployed an OVA before you can likely skip this section and go to the next heading (Adding Data Disk to vVNX).Ģ. Note: It does need 12GB of RAM and 2 vCPU, so it is very RAM hungry and my lab will struggle with this so I don’t think it will replace my lab storage any time soon but the learning experience is worth investing a few hours in. I found the EMC virtual VNX download link, and followed the below guide to deploy and configure it in my lab. With a VMware background I really needed to brush up on my storage skills, particularly since working at EMC technologies, so I decided to set up the EMC Virtual VNX (vVNX) in my lab and it is suprisingly easy.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |