TCP/IP stack

In the Ultra Transcenders books

2V0-15.25

Each book explains TCP/IP stack in context, with comparison tables and the common traps.

Terms in this definition

• ESX

  VMware's bare-metal hypervisor, installed on each host in a VCF fleet. Up to version 9.0 it was known as ESXi.

• VMkernel

  At the heart of ESX sits this kernel. Network access for host services (iSCSI, NFS, vSAN, vMotion, management and so on) goes through VMkernel adapters, also called vmknics.

• vMotion

  Moves a running VM to another host with no downtime; its storage counterpart, Storage vMotion, relocates the files between datastores instead.

• CRUD

  Shorthand for create, read, update and delete, the four basic things you do with data. Data-plane roles in Azure Cosmos DB, for instance, authorise those operations on items.

• VMkernel adapter

  An ESX host's own virtual network interface, named vmk0, vmk1 and so forth. It handles host services like management, vMotion, vSAN and IP storage, as opposed to traffic from VMs.

• Stop sequence

  One of up to four strings that make the model halt generation; the sequence itself is not included in the output.

Related terms

• Network File Copy

  The vSphere service that copies files from one datastore to another, for jobs such as cloning, cold migration and moving snapshots. Its traffic may run over the provisioning TCP/IP stack.

• NFC

  Cold migrations, clones and snapshot migrations all rely on this vSphere service, which ESX hosts use to move and copy files from one datastore to another. If needed, its traffic can be kept separate by placing it on the provisioning TCP/IP stack.

• vMotion TCP/IP stack

  A VMkernel TCP/IP stack kept for vMotion alone, with a default gateway of its own, so the traffic stays isolated and can cross subnets. After you add an adapter on it, vMotion is disabled on adapters using the default stack.