Author: tapasmahanta124

Senior Staff Engineer @Tintri by DDN|Blogger at cloudmaster.co.in/VmwareBlogs.co.in |8x vExpert Providing solutions to common issues related to VMware virtualization technology. I enjoy sharing my knowledge and experience with the VMware community through my blog. I cover topics such as troubleshooting virtual machine performance, optimizing storage and networking, managing virtual infrastructure, and implementing best practices for VMware environments. My goal is to help fellow VMware users overcome challenges and make the most out of their virtualization deployments.

Unlocking Performance and Efficiency with VAAI and Tintri Storage

tapasmahanta124Leave a comment

Introduction: In today’s data-driven world, organizations rely heavily on virtualization technologies to optimize their IT infrastructure. VMware’s vSphere platform has become a popular choice for virtualization, providing efficient resource utilization and simplified management. To further enhance the performance and efficiency of vSphere environments, VMware introduced vStorage APIs for Array Integration (VAAI). This blog explores how VAAI, in conjunction with Tintri storage, can unlock significant benefits for virtualized environments.

1. Understanding VAAI: VAAI is a set of storage APIs developed by VMware to offload storage operations to the underlying storage array, improving performance and reducing the load on vSphere hosts. It enables seamless integration between vSphere and storage arrays, allowing them to work together more efficiently.

2. Overview of Tintri Storage: Tintri storage is a VM-aware storage solution designed specifically for virtualized environments. It provides granular visibility and control at the virtual machine (VM) level, simplifying management and optimizing performance. Tintri’s VMstore arrays offer a range of advanced features, such as VM-level snapshots, clones, replication, and QoS policies.

3. VAAI Integration with Tintri Storage: VAAI integration with Tintri storage brings several benefits to virtualized environments:

a. Full Copy Offload (Hardware Assisted Locking): VAAI’s Full Copy Offload feature allows the storage array to perform data copies and clones without involving the vSphere host. With Tintri storage, Full Copy Offload enables rapid provisioning of VMs and efficient cloning operations, saving time and reducing resource utilization.

b. Block Zeroing: VAAI’s Block Zeroing feature offloads the task of zeroing out blocks on newly created VMs or during storage vMotion operations. Tintri storage, with its VM-awareness, leverages Block Zeroing to optimize the creation and migration of VMs, improving efficiency and reducing latency.

c. Hardware Assisted Locking: VAAI’s Hardware Assisted Locking feature enables the storage array to handle locking mechanisms, reducing contention and improving the performance of concurrent VM operations. Tintri storage, with its fine-grained control at the VM level, leverages Hardware Assisted Locking to enhance performance in multi-tenant environments.

d. Thin Provisioning Stun: VAAI’s Thin Provisioning Stun feature allows the storage array to notify the vSphere host when it reaches its thin provisioned capacity limit. Tintri storage, with its native support for thin provisioning, leverages this feature to prevent overprovisioning and ensure efficient utilization of storage resources.

4. Benefits of VAAI and Tintri Integration:

a. Improved Performance: By offloading storage operations to the Tintri storage array, VAAI reduces the load on vSphere hosts, improving overall performance. With Tintri’s VM-awareness and advanced storage capabilities, organizations can achieve consistent and predictable performance for their virtualized workloads.

b. Enhanced Efficiency: VAAI integration with Tintri storage streamlines storage operations, such as provisioning, cloning, and zeroing, resulting in faster VM deployment and reduced resource utilization. This translates to improved efficiency and better utilization of storage resources.

c. Simplified Management: Tintri’s VM-aware storage platform, coupled with VAAI integration, simplifies management tasks by providing granular visibility and control at the VM level. Administrators can easily monitor and manage VMs, snapshots, clones, and replication through a single pane of glass.

Tintri and Horizon View

tapasmahanta124Leave a comment

Tintri, now part of DDN, is a storage solution designed for virtualized environments and offers several features that integrate well with VMware Horizon View. In this workflow guide, we will discuss how to set up and utilize Tintri storage with Horizon View to enhance the performance, management, and scalability of virtual desktop infrastructure (VDI) deployments.

1. Tintri Overview: – Tintri is a VM-aware storage platform that provides granular visibility and control at the virtual machine (VM) level. – It leverages Tintri Global Center (TGC) for centralized management, analytics, and monitoring of Tintri storage arrays. – Tintri supports features like VM-level snapshots, clones, replication, and integration with VMware vSphere APIs for Storage Awareness (VASA).

2. Horizon View Overview: – VMware Horizon View is a desktop and application virtualization solution that delivers virtual desktops and applications to end-users. – Horizon View provides features like desktop pooling, instant clone technology, application virtualization, and user profile management.

3. Tintri Integration with Horizon View: – Tintri integrates with Horizon View to provide optimized storage for VDI workloads, improving performance and management efficiency. – Tintri offers VAAI (vStorage APIs for Array Integration) support, which offloads storage operations to the Tintri storage array, reducing the load on vSphere hosts. – Tintri provides per-VM performance monitoring and analytics, enabling administrators to identify and troubleshoot performance issues at the VM level.

4. Workflow Steps:

a. Tintri Storage Configuration: – Deploy Tintri storage arrays and connect them to the vSphere environment using iSCSI or NFS protocols. – Configure networking, storage pools, and datastores on the Tintri storage arrays. – Integrate Tintri storage with vSphere using the Tintri vSphere Web Client Plugin or vCenter Server.

b. Horizon View Deployment: – Deploy the Horizon View Connection Server and configure the necessary network settings. – Set up the Horizon View Composer, which provides linked-clone functionality for desktop pools. – Create a VM template with the desired operating system and applications to be used for desktop provisioning.

c. Tintri Storage for Horizon View: – Create a Tintri datastore on the Tintri storage array dedicated to storing Horizon View desktops and other related data. – Configure Tintri VM-level snapshots and replication policies to ensure data protection and disaster recovery for Horizon View desktops.

d. Horizon View Desktop Pool Configuration: – Configure the Horizon View desktop pool settings, including the number of desktops, power management, and user assignment. – Specify the Tintri datastore as the storage location for the desktop pool. – Enable Horizon View Composer and linked-clone technology to optimize storage utilization and improve desktop provisioning speed.

e. Performance Monitoring and Troubleshooting: – Utilize Tintri Global Center (TGC) to monitor performance metrics at the VM and datastore level. – Identify potential performance bottlenecks using Tintri analytics and performance metrics. – Troubleshoot performance issues by drilling down into VM-level statistics and identifying resource contention or misconfigurations.

f. Desktop Provisioning and Management: – Use Horizon View to provision desktops from the VM template stored on the Tintri datastore. – Leverage Horizon View Instant Clone technology for rapid desktop provisioning and efficient storage utilization. – Manage desktops, including power management, user assignments, and desktop pool settings, through the Horizon View Administrator interface.

g. Backup and Disaster Recovery: – Leverage Tintri VM-level snapshots and replication to create backups and ensure disaster recovery capabilities for Horizon View desktops. – Schedule regular snapshot and replication jobs to protect critical desktops and associated data. – Perform restore operations from Tintri snapshots or replicated data in case of data loss or disaster events.

h. Scaling and Expansion: – Monitor storage capacity and performance on the Tintri storage arrays using Tintri Global Center. – Scale the Horizon View environment by adding more Tintri storage arrays or expanding existing storage pools. – Utilize Tintri’s VM-aware features like cloning and replication to simplify the process of deploying additional desktops or expanding the VDI infrastructure.

5. Best Practices and Considerations: – Properly size the Tintri storage arrays based on the expected number of Horizon View desktops and their associated workloads. – Follow VMware’s best practices for Horizon View deployment and configuration, including networking.

NFS and troubleshooting Guide

tapasmahanta124Leave a comment

Network File System (NFS) is a protocol that allows file sharing across a network, enabling clients to access files and directories on remote servers as if they were local. NFS is widely used in both small and large-scale environments due to its simplicity, flexibility, and compatibility with various operating systems. In this explanation, we will discuss the reasons for using NFS and provide a comprehensive troubleshooting guide for NFS-related issues. Reasons for using NFS:

1. Centralized Storage: NFS allows for centralized storage, where multiple clients can access shared files and directories from a single storage location. This simplifies management and reduces the need for individual storage on each client.

2. File Sharing: NFS facilitates easy sharing of files and directories between different operating systems, such as Linux, Unix, and Windows. It provides a common interface for accessing files, regardless of the client’s operating system.

3. Scalability: NFS supports scalability, allowing for the addition of more clients and storage resources as needed. This makes it suitable for environments that require expansion without significant changes to the infrastructure.

4. Performance: NFS is designed to provide efficient file access over a network. It utilizes caching mechanisms and optimizations to minimize latency and maximize throughput, resulting in improved performance.

5. Data Consolidation: With NFS, organizations can consolidate data onto a single storage platform, reducing the complexity of managing multiple storage systems. This simplifies backup, disaster recovery, and data management processes.

6. Virtualization Support: NFS is widely used in virtualization environments, such as VMware vSphere and Citrix XenServer. It provides shared storage for virtual machines, enabling features like live migration, high availability, and centralized management.

7. Compatibility: NFS is supported by various operating systems, including Linux, Unix, macOS, and Windows. This cross-platform compatibility makes it an ideal choice for heterogeneous environments.

NFS Troubleshooting Guide:

1. Verify Network Connectivity: – Ensure that the NFS server and client are on the same network and can communicate with each other. – Verify that the network firewall or security settings are not blocking NFS traffic.

2. Check NFS Server Configuration: – Confirm that the NFS server is properly configured to export the desired directories. – Verify the NFS server’s access control list (ACL) settings to ensure proper permissions for clients.

3. Validate NFS Client Configuration: – Ensure that the NFS client has the necessary packages and modules installed to support NFS. – Verify the NFS client’s configuration file (/etc/fstab or /etc/nfsmount.conf) for correct mount options and server settings.

4. Test NFS Mount: – Manually mount the NFS share on the client using the mount command to validate connectivity and access permissions. – Check the output of the mount command and verify that the NFS share is mounted correctly.

5. Check NFS Server Logs: – Review the NFS server logs (e.g., /var/log/messages or /var/log/syslog) for any error messages or warnings related to NFS operations. – Analyze log entries to identify potential issues, such as permission errors or network connectivity problems.

6. Monitor NFS Performance: – Use tools like nfsstat or nfsiostat to monitor NFS performance metrics, including throughput, latency, and I/O operations. – Identify any performance bottlenecks, such as high latency or excessive I/O wait times, and troubleshoot accordingly.

7. Verify NFS Permissions: – Ensure that the NFS server has the correct permissions set for exported directories, allowing the client to access them. – Check file and directory permissions on the NFS server to ensure proper read and write access for clients.

8. Check NFS Client Mount Options: – Review the mount options used on the client and verify that they are appropriate for the NFS share. – Consider adjusting options like read/write caching, timeouts, or authentication mechanisms to troubleshoot specific issues.

9. Test File Access and Permissions: – Create test files on the NFS share and verify that they can be accessed and modified by the client. – Check file and directory permissions to ensure that they allow the desired level of access for clients.

10. Update NFS Software and Patches: – Ensure that both the NFS server and client systems have the latest software updates and patches installed. – Keep the NFS software up to date to benefit from bug fixes, performance improvements, and security enhancements.

11. Consult Vendor Documentation and Support: – Refer to the vendor’s documentation and knowledge base for specific troubleshooting steps and recommendations. – Reach out to the vendor’s support team for assistance in resolving complex or persistent NFS issues.

12. Capture Network Traces: – Use network packet capture tools like tcpdump or Wireshark to capture NFS-related network traffic. – Analyze the captured packets to identify any network-related issues, such as packet loss, latency, or misconfigured network settings.

13. Test with Different NFS Versions: – If possible, test NFS connectivity and performance using different NFS versions (e.g., NFSv3, NFSv4) to identify any compatibility issues. – Adjust NFS client and server settings to use different NFS versions and compare the results.

14. Monitor System Resource Utilization: – Monitor system resource utilization on both the NFS server and client, including CPU, memory, and network usage. – Identify any resource bottlenecks that may impact NFS performance and take necessary actions, such as optimizing configurations or upgrading hardware.

15. Document and Review Changes: – Keep track of any changes made to the NFS server or client configurations and document them for future reference. – Review configuration changes to identify any potential causes of NFS-related issues and revert or adjust settings as needed.

In conclusion, NFS provides a reliable and efficient way to share files across networks, making it a popular choice for various environments. However, when troubleshooting NFS-related issues, it is essential to validate network connectivity, review server and client configurations, monitor performance metrics, and consult vendor documentation and support resources. By following a comprehensive troubleshooting guide, administrators can effectively diagnose and resolve NFS issues, ensuring optimal file sharing and access within their infrastructure.

Esxi 7.0 vs Esxi 8.0

tapasmahanta124Leave a comment

ESXi 7.0 and ESXi 8.0 are both hypervisors developed by VMware, but they have several differences in terms of features, improvements, and compatibility. Here, we will discuss the key differences between ESXi 7.0 and ESXi 8.0 in detail.

1. Version and Release: – ESXi 7.0: Released in March 2020 as the latest major release before ESXi 8.0. – ESXi 8.0: Not yet released (as of October 2021). It is expected to bring significant updates and enhancements over ESXi 7.0.

2. Hardware Compatibility: – ESXi 7.0: Supports a wide range of hardware platforms, including CPUs, network adapters, and storage controllers. It introduces support for newer hardware technologies, such as AMD Rome processors and Intel Cascade Lake processors. – ESXi 8.0: Expected to further expand hardware compatibility and support newer hardware technologies, potentially including the latest generation processors and other advancements.

3. Security Enhancements: – ESXi 7.0: Introduces several security improvements, such as support for TPM 2.0 (Trusted Platform Module) for enhanced integrity checks and Secure Boot for protecting the hypervisor against unauthorized modifications. – ESXi 8.0: Expected to introduce additional security enhancements to address evolving threats and vulnerabilities, but specific details are not yet available.

4. Performance and Scalability: – ESXi 7.0: Brings several performance improvements, such as increased support for host-level hardware resources like memory and CPU cores. It also includes optimizations for specific workloads, such as performance improvements for vMotion operations. – ESXi 8.0: Expected to continue focusing on performance and scalability improvements. It may introduce enhancements related to resource utilization, workload mobility, and overall system performance.

5. vSphere Lifecycle Manager (vLCM): – ESXi 7.0: Introduces vLCM, a new framework for managing ESXi hosts’ lifecycle, including patching, upgrading, and configuration compliance. It simplifies the management of ESXi hosts in a vSphere environment. – ESXi 8.0: Expected to build upon vLCM capabilities and introduce further improvements for managing the lifecycle of ESXi hosts.

6. vSphere Distributed Resource Scheduler (DRS): – ESXi 7.0: Enhances DRS with new features like predictive DRS, which leverages AI and machine learning to optimize workload placement and resource allocation. – ESXi 8.0: Expected to introduce further enhancements to DRS, potentially leveraging advanced algorithms and technologies to improve workload balancing and resource utilization.

7. VMware vSAN: – ESXi 7.0: Introduces numerous enhancements to vSAN, VMware’s software-defined storage solution. It includes features like HCI Mesh, which allows vSAN clusters to consume external storage resources, and enhanced vSAN File Services for native file sharing. – ESXi 8.0: Expected to bring additional improvements and features to vSAN, potentially focusing on performance, scalability, and integration with other VMware solutions.

8. VMware vSphere with Kubernetes: – ESXi 7.0: Introduces the capability to run Kubernetes natively on ESXi hosts using the vSphere with Kubernetes integration. It enables the deployment and management of containerized applications alongside virtual machines. – ESXi 8.0: Expected to further enhance and expand the vSphere with Kubernetes functionality, potentially introducing new features, performance optimizations, and integration improvements.

9. Management and Monitoring: – ESXi 7.0: Enhances the vSphere Client, the primary management interface, with new features and improvements for easier navigation, monitoring, and troubleshooting. It provides a modern web-based interface for managing vSphere environments. – ESXi 8.0: Expected to continue improving the vSphere Client, potentially introducing new management capabilities, monitoring tools, and user experience enhancements.

10. Compatibility with VMware Ecosystem: – ESXi 7.0: Compatible with VMware vCenter Server 7.0, vSphere Update Manager 7.0, and other VMware products and solutions designed for vSphere 7.0. – ESXi 8.0: Expected to be compatible with the corresponding version of vCenter Server, vSphere Update Manager, and other VMware solutions designed for vSphere 8.0.

In summary, while ESXi 7.0 introduced several enhancements in areas like hardware support, security, performance, and management, ESXi 8.0 is expected to bring further improvements, including expanded hardware compatibility, advanced security features, enhanced performance and scalability, and additional capabilities for managing and monitoring vSphere environments.

Clones using VAAI and migrate them to a different datastore

tapasmahanta124Leave a comment

To create clones using VAAI and migrate them to a different datastore, and then export the data to a CSV file for reporting purposes, you can use the PowerCLI module. Here’s an example script:

powershell
# Connect to vCenter Server
Connect-VIServer -Server <vCenterServer> -User <username> -Password <password>

# Specify the source VM and the destination datastore
$sourceVM = "SourceVM"
$destinationDatastore = "DestinationDatastore"

# Create a clone of the source VM on the destination datastore using VAAI
$cloneVM = New-VM -Name "CloneVM" -VM $sourceVM -Datastore $destinationDatastore -RunAsync -UseVAAI

# Wait for the clone operation to complete
$cloneTask = Get-Task -Name $cloneVM.ExtensionData.Name
$cloneTask | Wait-Task

# Power on the clone VM
Start-VM -VM $cloneVM

# Export VM details to CSV
$vmDetails = Get-VM -Name $cloneVM.Name
$vmDetails | Export-Csv -Path "C:\Path\To\Report.csv" -NoTypeInformation

# Disconnect from vCenter Server
Disconnect-VIServer -Server <vCenterServer> -Confirm:$false

Make sure to replace “, “, and “ with your actual vCenter Server details. Also, update “ and “ with the names of your source VM and destination datastore, respectively. This script creates a clone of the source VM on the destination datastore using VAAI. It then waits for the clone operation to complete and powers on the clone VM. Finally, it retrieves the VM details and exports them to a CSV file for reporting. Please note that the PowerCLI module must be installed and properly configured for this script to work.

Performance metics on VSAN

tapasmahanta124Leave a comment

To check the performance of a VMware vSAN using PowerShell, you can utilize the PowerCLI module to retrieve relevant performance metrics. Here’s an example script:

powershell
# Connect to vCenter Server
Connect-VIServer -Server <vCenterServer> -User <username> -Password <password>

# Specify the vSAN cluster name
$clusterName = "vSANCluster"

# Get the vSAN cluster object
$cluster = Get-Cluster -Name $clusterName

# Get the vSAN performance statistics for the cluster
$performanceStats = Get-Stat -Entity $cluster -Stat "vsan.*" -Realtime

# Loop through each performance stat and display the values
foreach ($stat in $performanceStats) {
    $statName = $stat.MetricId.Replace("vsan.", "")
    $statValue = $stat.Value
    $statUnit = $stat.Unit
    Write-Host "$statName: $statValue $statUnit"
}

# Disconnect from vCenter Server
Disconnect-VIServer -Server <vCenterServer> -Confirm:$false

Make sure to replace “, “, and “ with your actual vCenter Server details. Also, update “ with the name of your vSAN cluster. This script connects to the vCenter Server, retrieves the vSAN cluster object, and then fetches real-time performance statistics using the `Get-Stat` cmdlet. It loops through each performance stat, extracts the metric name, value, and unit, and displays them on the console. Please note that the PowerCLI module must be installed and properly configured for this script to work. Additionally, you may need to adjust the `Get-Stat` cmdlet parameters to retrieve specific vSAN performance metrics based on your requirements.

PowerShell script that uses the Tintri Toolkit APIs to move VMs from a Tintri Global Center (TGC) to another destination

tapasmahanta124Leave a comment 

# Import the Tintri Toolkit module
Import-Module -Name Tintri.Powershell.Toolkit

# Connect to the Tintri Global Center
Connect-TintriServer -Server <TGC_IP> -Credential (Get-Credential)

# Specify the source TGC VMstore name
$sourceVMstore = "<Source_VMstore_Name>"

# Specify the destination TGC VMstore name
$destinationVMstore = "<Destination_VMstore_Name>"

# Get the list of VMs from the source VMstore
$sourceVMs = Get-TintriVM -VMstoreName $sourceVMstore

# Loop through and move VMs to the destination VMstore
foreach ($sourceVM in $sourceVMs) {
    $sourceVMName = $sourceVM.vmName

    # Get the VM details from the source VMstore
    $sourceVMDetails = Get-TintriVM -VMstoreName $sourceVMstore -Name $sourceVMName

    # Create a clone of the VM on the destination VMstore
    $destinationVMDetails = New-TintriVM -VMstoreName $destinationVMstore -Name $sourceVMName -SourceVM $sourceVMDetails

    # Start the clone operation
    Start-TintriVM -VMstoreName $destinationVMstore -Name $sourceVMName

    # Wait for the clone operation to complete
    do {
        Start-Sleep -Seconds 10
        $cloneStatus = Get-TintriVMCloneStatus -VMstoreName $destinationVMstore -Name $sourceVMName
    } while ($cloneStatus -eq "Cloning")

    # Check if the clone operation was successful
    if ($cloneStatus -eq "Success") {
        Write-Host "VM '$sourceVMName' has been successfully moved to '$destinationVMstore'."
    } else {
        Write-Host "Failed to move VM '$sourceVMName' to '$destinationVMstore'."
    }
}

# Disconnect from the Tintri Global Center
Disconnect-TintriServer

Make sure to replace “, “, and “ with the actual IP address of your Tintri Global Center, the name of the source VMstore, and the name of the destination VMstore, respectively. Please note that this script assumes you have the Tintri PowerShell Toolkit module installed and properly configured.

Power shell script to create and clone 100 VMs from one storage and move send 10000 Iops on each VM

tapasmahanta124Leave a comment 

# Connect to the vCenter Server
Connect-VIServer -Server <vCenterServer> -User <username> -Password <password>

# Specify the source VM and storage
$sourceVM = "SourceVM"
$sourceDatastore = "SourceDatastore"

# Specify the destination datastore
$destinationDatastore = "DestinationDatastore"

# Specify the number of VMs to create and clone
$numberOfVMs = 100

# Specify the number of IOPS to send on each VM
$iops = 10000

# Loop through and create/cloning VMs
for ($i = 1; $i -le $numberOfVMs; $i++) {
    $newVMName = "VM$i"

    # Clone the VM from the source to the destination datastore
    $cloneSpec = New-Object VMware.Vim.VirtualMachineCloneSpec
    $cloneSpec.Location = New-Object VMware.Vim.VirtualMachineRelocateSpec
    $cloneSpec.Location.Datastore = Get-Datastore -Name $destinationDatastore
    $cloneSpec.PowerOn = $false

    $sourceVMObj = Get-VM -Name $sourceVM
    New-VM -Name $newVMName -VM $sourceVMObj -Location (Get-Folder) -Datastore (Get-Datastore -Name $destinationDatastore) -CloneSpec $cloneSpec

    # Power on the newly created VM
    Start-VM -VM $newVMName

    # Send IOPS on the VM
    $vm = Get-VM -Name $newVMName
    $disk = $vm | Get-HardDisk
    $disk | Set-HardDisk -Iops $iops
}

# Disconnect from the vCenter Server
Disconnect-VIServer -Server <vCenterServer> -Confirm:$false

Make sure to replace “, “, “, “, “, “ with your actual vCenter Server details and VM/storage names. Please note that this script assumes you have the VMware PowerCLI module installed and properly configured.

IPv6 Support on a Host

tapasmahanta124Leave a comment

The IPv6 support in vSphere lets hosts work in an IPv6 network that has a large address space, enhanced multicasting, simplified routing, and so on.

In ESXi 5.1 and later releases, IPv6 is enabled by default.

Procedure

  1. In the vSphere Web Client, navigate to the host.
  2. On the Manage tab, click Networking and select Advanced.
  3. Click Edit.
  4. From the IPv6 support drop-down menu, enable or disable IPv6 support.
  5. Click OK.
  6. Reboot the host to apply the changes in the IPv6 support.

What to do next

Configure the IPv6 settings of VMkernel adapters on the host, for example, of the management network

To connect an ESXi host over IPv6 to the management network, vSphere vMotion, shared storage, vSphere Fault Tolerance, and so on, edit the IPv6 settings of the VMkernel adapters on the host.

Procedure

  1. In the vSphere Web Client, navigate to the host.
  2. Under Manage, select Networking and then select VMkernel adapters.
  3. Select the VMkernel adapter on the target distributed or standard switch and click Edit.
  4. In the Edit Settings dialog box, click IPv6 settings.
  5. Configure the address assignment of the VMkernel adapter.
    IPv6 Address Option Description
    Obtain IPv6 address automatically through DHCP Receive an IPv6 address for the VMkernel adapter from a DHCPv6 server.
    Obtain IPv6 address automatically through Router Advertisement Receive an IPv6 address for the VMkernel adapter from a router through Router Advertisement.
    Static IPv6 addresses Set one or more addresses. For each address entry, enter the IPv6 address of the adapter, subnet prefix length and IPv6 address of the default gateway.

    You can select several assignment options according to the configuration of your network.

  6. (Optional) From the Advanced Settings section of the IPv6 settings page, remove certain IPv6 addresses that are assigned through Router Advertisement.
    You might delete certain IPv6 addresses that the host obtained through Router Advertisement to stop the communication on these addresses. You might delete all automatically assigned addresses to enforce the configured static addresses on the VMkernel.
  7. Click OK to apply the changes to the VMkernel adapter.