2.5

Table Of Contents
VMware, Inc. 191
Appendix C Network Fencing
Processor Type Incompatibility
Deployingaconfigurationinfencedmodehostsallthevirtualmachinesonasingle
ManagedServersystem.YoumusthaveaManagedServersystemconnectedtothe
storageserverwherethetemplatesthatserveasthebasisofthisconfigurationreside
on.TheManagedServ ersystemmusthavesufficientresources,such
asmemory,slots,
andfences.
Ifyoudeployaconfiguration,performanoperationwhichsavesthestateofthe
configuration(forexample,suspendorcapturetolibrary),andredeploythe
configurationwithfencing(whichrequireshostingallvirtualmachinesonthesame
physicalmachine),asituationcouldcomeupwherethe
onlyManagedServersystems
availableareoneswithincompatibleprocessortypes.Thecapturedmemoryexpectsa
particularprocessortype.
Toaddressthissituation,deploytheconfigurationwithoutfencing,undeployit
withoutsavingthememorystate(usetheTurnOffdeploymentsettingintheUser
PreferencespageortheUndeploy‐DiscardState
mouseovermenu),andredeploythe
configuration.
Ifdeployingaconfigurationwithoutfencingisnotanoption,resettheMACaddressof
eachvirtualmachinetoremovethesavedstate,andredeploytheconfiguration.See
“ChangingIPorMACAddressesonpage 34.
Viewing Virtual Switches for Fences
YoucanusetheVIClientintheESXServersystemtoseethe“LMNetwork<n>”virtual
switchesornetworksthatLab Managercreatesforeachfence.
To view virtual switches for fences
1 NavigatetotheConfigurationtaboftheVIClient.
2ClicktheNetworkinglinkintheHardwarelisttoviewvirtualswitches(for
example,“LMNetwork001”).
SeetheVMware
Infrastructure3documentationfordetailsonusingVIClient.
CAUTIONDonotconnectthevirtualswitchesthatLab Managercreatestoanexternal
network.Lab Managerneedsthesevirtualswitchesfordeployingfenced
configurations.