vmware hub

Login to the Virtual Machine and shrink the OS Partition Before we can shrink the VMware virtual machine disk (VMDK), we need to shrink the OS partition. (to avoid file system corruption). In this example I am using Windows 2008 R2, which has a shrink function. Using an RDP (Remote Desktop Protocol) connection or connect via the Console, using the vSphere Client, login to the virtual machine as an Administrator. Press Control-Alt-Delete to login to the virtual machine. Right Click My Computer and Select Manage Select Disk Management, and select the partition you need to shrink. Right Click the Volume/Partition to shrink, and select Shrink. The above dialogue will briefly appear whilst the file system is queried. the above dialogue will appear. Enter a size to reduce the OS partition. In this example the VMware virtual machine disk (VMDK) is 40GB, and we would like to reduce the size of the VMware virtual machine disk (VMDK) to 20GB. The Disk Management utility scans...

A 2-node hyperconverged cluster is useful in branch office where you need high availability or for small infrastructure. With 2-node hyperconverged solution, you don’t need to leverage a NAS or a SAN for the shared storage. So, the hardware footprint is reduced and the manageability is improved because hyperconverged solution are easier to use than standard infrastructure with SAN. VMware provides a Software-Defined Storage solution called vSAN. vSAN can be deployed from 2 nodes to 16 nodes. 2-node cluster should be used for ROBO (Remote Office and Branch Office). A 2-node cluster requires a Witness Appliance provided by VMware freely while the appliance is virtual. The Witness Appliance is based on ESXi. This is the first time that VMware supports a scenario in production with a nested ESXi. This topic describes how to deploy a 2-node vSAN cluster and its witness appliance. Why you need a witness appliance vSAN is something like a RAID over the network. vSAN curre...

Part 1 provides details of the deployment and official documentation, we’ll build the management and control planes by deploying NSX Manager and an NSX Controller cluster. Part 2 will walk through the data plane components; host preparation, VTEP / VXLAN configuration, transport zone, and logical switches. Finally in Part 3 we’ll create and configure NSX Edge and Distributed Logical Routers. In order to get NSX up and running we’ll need: An underlying network with IP connectivity and an MTU size of 1600 or above. FQDN resolution, connectivity, and time synchronisation between NSX and vSphere components – a full list of network port requirements can be viewed in this KB. ESXi and vCenter versions 5.5 – 6.0 U2 for NSX 6.2.x. Update – NSX 6.3.0 is compatible with vSphere 6.5a, download NSX 6.3 here , NSX 6.3 release notes here , NSX 6.3 what’s new here . An FTP/SFTP server is required for NSX backups; VMware NSX Backup and Restore . It’s also good practise to have a syslog...