User`s guide

VMware Stage Manager User’s Guide
182 VMware, Inc.
Fromaperformanceperspective,networkfencingimpactsthetrafficflowbetween
modules.Fencingrequiresaslightlyhighernumberofresourcesonthehost,suchas
memory,CPU,networking,andvirtualmachineslots.Ifyouenablefencingbutnever
useit,theseresourcesdonotcomeintoplay.
Fencing Overview
Virtualmachinesinaconfigurationhavepreconfigured(internal)IPaddresses.When
youdeployvirtualmachinesinfencedmode,Stage Managerassignsauniqueexternal
IPaddresstoeachofthesemachines.Throughtheseexternaladdresses,virtual
machinesbothinsideandoutsidethefencecancommunicatewitheachother.
Stage Managerusesavirtual
machinecalledavirtualroutertoroutepacketsbetween
thesevirtualmachines.Stage Managerconfiguresthevirtualrouterwhenyoudeploy
afencedconfigurationanddeletesitwhenyouundeploytheconfiguration.
Figure C1illustratesconfigurationswithoutfencingandwithfencing.
Figure C-1. Configuration A (Without Fencing) and Configuration B (With Fencing)
N
OTEWhenyoudeployaconfigurationinfencedmodewiththeBlockTr afficInand
Outoption,Stage M anagerdoesnotcreate avirtualrouterorassignexternalIP
addresses.See“FencingOptions”onpage 183.
fenced
network
ESX Server host 2ESX Server host 1
client machine
configuration a configuration b
(fenced)
network
legend
connection
fenced connection
IIP internal IP address
EIP external IP address for fenced configurations
VR virtual router
EIP 192.168.0.4 EIP 192.168.0.3
IIP 192.168.0.1
MAC 00:50:56:00:00:01
IIP 192.168.0.2
MAC 00:50:56:00:00:02
VM1 VM2
IIP 192.168.0.1
MAC 00:50:56:00:00:01
IIP 192.168.0.2
MAC 00:50:56:00:00:02
VM1 VM2
VR