6.7
Table Of Contents
- vCenter Server and Host Management
- Contents
- About VMware vCenter Server and Host Management
- vSphere Concepts and Features
- Using the vSphere Client
- Log in to vCenter Server by Using the vSphere Client
- Use the vSphere Client Navigator
- Customize the User Interface
- Install the VMware Enhanced Authentication Plug-in
- Pause and Resume a Task in Progress in the vSphere Web Client
- Refresh Data
- Searching the Inventory
- Use Quick Filters
- View Recent Objects
- Configure the vSphere Web Client Timeout Value
- Remove Stored User Data
- Drag Objects
- Export Lists
- Attach File to Service Request
- Keyboard Shortcuts
- Configuring vCenter Server
- Configure License Settings for vCenter Server
- Configuring Statistics Settings
- Configure Runtime Settings for vCenter Server
- Configure User Directory Settings
- Configure Mail Sender Settings
- Configure SNMP Settings
- View Port Settings
- Configure Timeout Settings
- Configure Logging Options
- Configure Database Settings
- Verifying SSL Certificates for Legacy Hosts
- Configure Advanced Settings
- Send a Message to Other Logged In Users
- Edit the Settings of Services
- Start, Stop, and Restart Services
- Configuring Services in the vSphere Web Client
- Using Enhanced Linked Mode
- Configuring Communication Among ESXi , vCenter Server, and the vSphere Web Client
- Configuring Hosts and vCenter Server
- Configuring Customer Experience Improvement Program
- Organizing Your Inventory
- vSphere Tags and Attributes
- License Management and Reporting
- Licensing Terminology and Definitions
- The License Service in vSphere 6.7
- Licensing for Environments with vCenter Server Systems 6.0 and Later, and 5.5
- Licensing for Products in vSphere
- Suite Licensing
- Managing Licenses
- Viewing Licensing Information
- Generating Reports for License Use in the vSphere Web Client
- Synchronizing Licenses with Your My VMware Account
- vCenter Server Domain Repoint License Considerations
- Working with Tasks
- Managing Hosts with vCenter Server in the vSphere Client
- Migrating Virtual Machines
- Cold Migration
- Migration with vMotion
- Migration with Storage vMotion
- CPU Compatibility and EVC
- CPU Compatibility Scenarios
- CPU Families and Feature Sets
- About Enhanced vMotion Compatibility
- EVC Requirements for Hosts
- Create an EVC Cluster
- Enable EVC on an Existing Cluster
- Change the EVC Mode for a Cluster
- Determine the EVC Mode of a Virtual Machine
- Determine the EVC Mode that a Host Supports
- Prepare Clusters for AMD Processors Without 3DNow!
- CPU Compatibility Masks
- View CPUID Details for an EVC Cluster
- Migrate a Powered-Off or Suspended Virtual Machine in the vSphere Web Client
- Migrate a Virtual Machine to a New Compute Resource
- Migrate a Virtual Machine to a New Compute Resource and Storage in the vSphere Web Client
- Migrate a Virtual Machine to New Storage in the vSphere Web Client
- Place vMotion Traffic on the vMotion TCP/IP Stack of an ESXi Host
- Place Traffic for Cold Migration on the Provisioning TCP/IP Stack
- Limits on Simultaneous Migrations
- About Migration Compatibility Checks
- Automating Management Tasks by Using vRealize Orchestrator
- Concepts of Workflows
- Performing Administration Tasks on the vSphere Objects
- Configure the Default vRealize Orchestrator
- Managing Associations of Workflows with vSphere Inventory Objects
- Managing Workflows
- Workflows for Managing Inventory Objects
- Cluster and Compute Resource Workflows
- Guest Operation Files Workflows
- Guest Operation Processes Workflows
- Custom Attributes Workflows
- Data Center Workflows
- Datastore and Files Workflows
- Data Center Folder Management Workflows
- Host Folder Management Workflows
- Virtual Machine Folder Management Workflows
- Basic Host Management Workflows
- Host Power Management Workflows
- Host Registration Management Workflows
- Networking Workflows
- Distributed Virtual Port Group Workflows
- Distributed Virtual Switch Workflows
- Standard Virtual Switch Workflows
- Resource Pool Workflows
- Storage Workflows
- Storage DRS Workflows
- Basic Virtual Machine Management Workflows
- Clone Workflows
- Linked Clone Workflows
- Linux Customization Clone Workflows
- Tools Clone Workflows
- Windows Customization Clone Workflows
- Device Management Workflows
- Move and Migrate Workflows
- Other Workflows
- Power Management Workflows
- Snapshot Workflows
- VMware Tools Workflows
- About Headless Systems
- Troubleshooting Overview
- Troubleshooting vCenter Server
- Guidelines for Troubleshooting
- Identifying Symptoms
- Defining the Problem Space
- Testing Possible Solutions
- Troubleshooting with Logs
- vCenter Server Upgrade Fails When Unable to Stop Tomcat Service
- Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail
- Troubleshooting the vSphere Web Client
- Troubleshooting vCenter Server and ESXi Host Certificates
- Troubleshooting Hosts
- Troubleshooting vSphere HA Host States
- vSphere HA Agent Is in the Agent Unreachable State
- vSphere HA Agent is in the Uninitialized State
- vSphere HA Agent is in the Initialization Error State
- vSphere HA Agent is in the Uninitialization Error State
- vSphere HA Agent is in the Host Failed State
- vSphere HA Agent is in the Network Partitioned State
- vSphere HA Agent is in the Network Isolated State
- Configuration of vSphere HA on Hosts Times Out
- Troubleshooting vSphere Auto Deploy
- vSphere Auto Deploy TFTP Timeout Error at Boot Time
- vSphere Auto Deploy Host Boots with Wrong Configuration
- Host Is Not Redirected to vSphere Auto Deploy Server
- Package Warning Message When You Assign an Image Profile to a vSphere Auto Deploy Host
- vSphere Auto Deploy Host with a Built-In USB Flash Drive Does Not Send Coredumps to Local Disk
- vSphere Auto Deploy Host Reboots After Five Minutes
- vSphere Auto Deploy Host Cannot Contact TFTP Server
- vSphere Auto Deploy Host Cannot Retrieve ESXi Image from vSphere Auto Deploy Server
- vSphere Auto Deploy Host Does Not Get a DHCP Assigned Address
- vSphere Auto Deploy Host Does Not Network Boot
- Recovering from Database Corruption on the vSphere Auto Deploy Server
- Authentication Token Manipulation Error
- Active Directory Rule Set Error Causes Host Profile Compliance Failure
- Unable to Download VIBs When Using vCenter Server Reverse Proxy
- Troubleshooting vSphere HA Host States
- Troubleshooting Licensing
- Troubleshooting vCenter Server
10 (Optional) On the IPv6 settings page, select an option for obtaining IPv6 addresses.
Option Description
Obtain IPv6 addresses automatically
through DHCP
Use DHCP to obtain IPv6 addresses. A DHCPv6 server must be present on the
network.
Obtain IPv6 addresses automatically
through Router Advertisement
Use router advertisement to obtain IPv6 addresses.
In ESXi 6.5 and later router advertisement is enabled by default and supports the
M and O flags in accordance with RFC 4861.
Static IPv6 addresses a Click Add IPv6 address to add a new IPv6 address.
b Enter the IPv6 address and subnet prefix length, and click OK.
c To change the VMkernel default gateway, click Override default gateway for
this adapter.
The VMkernel Default Gateway address for IPv6 is obtained from the selected
TCP/IP stack.
11 Review your settings selections on the Ready to complete page and click Finish.
After you create a VMkernel adapter on the provisioning TCP/IP stack, you can use only this stack for
cold migration, cloning, and snapshots on this host. The VMkernel adapters on the default TCP/IP stack
are disabled for the provisioning service. If a live migration uses the default TCP/IP stack while you
configure VMkernel adapters with the provisioning TCP/IP stack, the data transfer completes successfully.
However, the involved VMkernel adapters on the default TCP/IP stack are disabled for future cold
migration, cross-host cloning, and snapshot sessions.
Limits on Simultaneous Migrations
vCenter Server places limits on the number of simultaneous virtual machine migration and provisioning
operations that can occur on each host, network, and datastore.
Each operation, such as a migration with vMotion or cloning a virtual machine, is assigned a resource
cost. Each host, datastore, or network resource, has a maximum cost that it can support at any one time.
Any new migration or provisioning operation that causes a resource to exceed its maximum cost does not
proceed immediately, but is queued until other operations complete and release resources. Each of the
network, datastore, and host limits must be satisfied for the operation to proceed.
vMotion without shared storage, migrating virtual machines to a different host and datastore
simultaneously, is a combination of vMotion and Storage vMotion. This migration inherits the network,
host, and datastore costs associated with those operations. vMotion without shared storage is equivalent
to a Storage vMotion with a network cost of 1.
Network Limits
Network limits apply only to migrations with vMotion. Network limits depend on the version of ESXi and
the network type. All migrations with vMotion have a network resource cost of 1.
vCenter Server and Host Management
VMware, Inc. 156