Before vSphere 6.0, the TCP/IP configuration was mainly managed by a single network stack. But now we can have multiple and different TCP/IP stacks (also called netstacks) for different VMkernel interfaces. These are the built-in TCP/IP stacks available in vSphere:
- Default TCP/IP stack: General-purpose stack that can be used for any VMkernel service.
- vMotion TCP/IP stack: Stack optimized for vMotion. The goal is to fully isolated vMotion traffic. Once used, the vMotion traffic will be removed from the default TCP/IP stack.
- Provisioning TCP/IP stack: Dedicated stack that is used to isolate several VM operations as migrations, cloning, or traffic generated by snapshots.
By using a separate TCP/IP stack, you can handle different ...