VMware VC-VLM4-C User Guide - Page 57
Fencing Connectivity,
View all VMware VC-VLM4-C manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 57 highlights
Chapter 7 Working with Configurations NOTE When you deploy a configuration in fenced mode with the Block In and Out option, Lab Manager does not create a virtual router or assign external IP addresses. See "Fencing Connectivity" on page 57. Figure 7‐1 illustrates configurations without fencing and with fencing. Figure 7-1. Configuration A (Without Fencing) and Configuration B (With Fencing) ESX Server host 1 192.10608:5.00.:156:00:00:01 IIPMAC VM1 configuration a ESX Server host 2 192.10608:5.00.:256:00:00:02 192.10608:5.00.:156:00:00:01 192.10608:5.00.:256:00:00:02 IIPMAC IIPMAC IIPMAC VM2 VM1 VM2 fenced network configuration b VR (fenced) client machine legend IIP EIP VR physical network EIP 192.168.0.4 EIP 192.168.0.3 connection fenced connection internal IP address external IP address for fenced configurations virtual router Fencing a configuration does not require any changes to its virtual machines. Within a fenced configuration, virtual machines continue to use preassigned IP addresses to communicate with each other. Fencing Connectivity Three connectivity modes are available when you fence a configuration: Allow In and Out - Virtual machines can communicate with machines outside the fence, and machines outside the fence can communicate with virtual machines inside the fenced configuration. Figure 7-2. Allow In and Out Fencing Mode ESX Server host VM1 fenced network VR configuration physical network VMware, Inc. 57