Scaling out vSAN cluster Compute, File Service Shares and iSCSI Target Service.

-
Hello Everyone,
Today, we are going to cover up how to scale out the vSAN cluster compute, Storage, File Service Shares and iSCSI Target service.
In my case, I have a cluster of 4 hosts running on vSphere 7 and vSAN 7 and I want to add a new host (ESXi05) to my existing vSAN cluster, expand the vSAN Data store and also expand my vSAN File Services cluster.
Before going forward on this, we need to make sure that this new ESX host has same configuration like the existing ones in terms of CPU, RAM, Network and Disk.
First of all, when you add a host into the cluster you need to make sure that it should be in maintenance mode. If it is not in maintenance mode then vSAN FS will instantly try to clone a vSAN File Services agent VM (FS VM) on it and that process will fail as there’s no disk group yet.
After you added it to the cluster, you have to create the disk group first. Claim all the disks that need to be part of the disk group and create the disk group. When you have done that you can take the host out of maintenance mode. 

Let's do it quickly.
1. Go to the cluster.
2. Add the new host(ESXi05) into the cluster.

3. Add this new ESX hosts in all DvSwitch like other other ones.
Now, it is time to create the disk group for this new host.
1. Click on cluster >> click on Configure then go to vSAN section and choose Disk Management and click on "CLAIM UNUSED DISKS"

Select the disks on this new host for Cache and Capacity tier as shown below.
Click on CREATE and few tasks will initiate on vCenter for disk group creation.

Once the disk group created, vSAN datastore capacity will increase  automatically.

However, one thing you will need to do is expand the IP Pool for the vSAN FS Protocol Stack container. 
  • Go to your cluster
  • Click on vSAN / Services
  • Go to File Service and click Edit on the right
  • Go to the IP Pool page by clicking Next twice
  • Add that additional IP address and DNS Name

  • Click Next / Finish
Exit this new host from Maintenance mode now.

A task will initiate for install a new vSAN File Service Node/Agent on this new ESX host.





So, all looks good.

Now, you can increase the File share size as  the vSAN datastore has enough space available.




Since, vSAN datastore has enough free space available, you can also create/expand iSCSI LUNs if you have enabled iSCSI on vSAN cluster as well.

So, in this post, we have scale out vSAN compute (by add new host with CPU,RAM), vSAN Storage (Add new disks group) as well.

That's all. Have a great day ahead and Cheers..



Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more