VMkernel TCP/IP Stacks





3 major TCP/IP stack

One of the primary reasons for creating a separate TCP/IP stack from the default one in many cases is to use a different default gateway

當你需要將 VMware 唔同既 traffic 分開唔同 network 經唔同既 default gateway 走就需要 configure TCP/IP stack

Default TCP/IP stack

Management traffic between ESXi hosts and vCenter server are considered as the default TCP/IP stack. Also, host related traffic like vMotion, NFS/iSCSI storage, HA and vSphere FT are part of it.

vMotion TCP/IP stack

By creating a VMkernel port on the vMotion TCP/IP stack you can isolate vMotion traffic to this stack. By doing so, vMotion traffic will be disabled on the default TCP/IP stack. The vMotion TCP/IP stack is used for live VM migrations.

VMware recommends configuring a separate vMotion TCP/IP stack and isolate management traffic from vMotion traffic.

依個 vMotion TCP/IP stack 係 for Layer 3 vMotion, 原本既 vMotion traffic 只係 Layer 2 only. 要 enable 左 vMotion TCP/IP stack 先可以做到 Layer 3 vMotion.

Provisioning TCP/IP stack

The provisioning TCP/IP stack is used for cold VM migration, cloning and snapshotting traffic. In case of a long-distance vMotion (new in vSphere 6), NFC (network file copy) traffic can be configured to use the provisioning TCP/IP stack. Setting up a provisioning TCP/IP stack is useful when you want to isolate this traffic from other TCP/IP stacks. A dedicated provisioning TCP/IP stack is common in VDI environments and in setups with frequent VM snapshots.



WordPress.com 標誌

您的留言將使用 WordPress.com 帳號。 登出 /  變更 )

Google photo

您的留言將使用 Google 帳號。 登出 /  變更 )

Twitter picture

您的留言將使用 Twitter 帳號。 登出 /  變更 )


您的留言將使用 Facebook 帳號。 登出 /  變更 )

連結到 %s

在 WordPress.com 建立免費網站或網誌.

向上 ↑

%d 位部落客按了讚: