CloudArena

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 d

                                              Native File Services on vSAN 7.0 Hello Everyone, Today, we are covering up about the new and exciting feature of vSAN 7.0 i.e. Native File Services over vSAN. This is quite an interesting feature for File share platform which can leverage the benefit of HCI powered storage i.e. VMware vSAN. vSAN File Services, fully integrated into vSAN 7, now has the ability to create file shares alongside block volumes on your vSAN data store. These file shares are accessible via NFS v3 and NFS v4.1 protocols. It is very simple to setup and use, as you would expect with vSAN. It is also fully integrated with vSAN Virtual Object Viewer and Health, with its own set of checks for both File Server Agents and the actual File Shares themselves. Let’s begin with a look at how to deploy vSAN File Services. It really is very straight-forward, and is enabled in much the same way as previous vSAN services. We’ll begin with a 4-node vSAN 7 clus

VTEP also know as VXLAN Tunnel Endpoint  has a very significant role on NSX platform. VTEP works on VMKernel port group created on ESXi host. VXLAN is hyper-visor based kernel module and installed during ESX host preparation via NSX manager. It handles all encapsulation and decapsulation for VXLAN network. VTEP Table - Every VTEP on ESXi hosts reports the VNIs that they are a member of to the NSX                            Controller. NSX Controllers maintain this list and send it to all VTEPs.                       Each VTEPs has a full inventory for VNIs in which they participate. NSX Controllers                          also use this list to select the VTEP Proxies as well. MAC Table - VTEPs will report every known MAC address in each VNI to the NSX Controller. this                        will cut the unnecessary ARP request flooded among the individual hosts VTEPs. If a                         VTEP needs a MAC of an IP, it will request to NSX controller. If NSX Controller

VMware vSphere 7.0 has been announced by VMware and available from 02 April 2020. There are so many new features introduced on this new vCenter server version 7.0. 1. vSphere with Kubernetes 2. Improved DRS 3. Assignable Hardware 4. vSphere Life-cycle Manager. 5. Refactored vMotion. 6. Intrinsic Security 7. External PSC model deprecated. 8. vCenter Server on Windows is no more  available . 9. P recision clock for PTP support and Many more. Here is how to install VMware vCenter Server 7.0 (or VCSA 7.0) First, download the VCSA installation media from your https://my.vmware.com account. Next, mount the ISO on your local machine – In this example, I have mounted it to the E: drive. Depending on your OS, you can launch the installer. For my Windows machine, this is simply at: E:\vcsa-ui-installer\win32\installer.exe The installer will launch. Select Install: Here, we don't have option for External PSC selection, as External PSC has been deprecated on this