2.4
Table Of Contents
- VMware® Lab Manager User’s Guide
- Contents
- Preface
- Introducing Lab Manager
- Getting Started with Lab Manager
- Working with Virtual Machines
- Accessing Virtual Machines
- Reviewing the Virtual Machine Console Page
- Reviewing Virtual Machine Operations
- Summary of Virtual Machine Operations
- Summary of Virtual Machine States
- Changing IP or MAC Addresses
- Setting Up Remote Desktop Connections
- Taking Snapshots and Reverting the Snapshots
- Inserting CDs
- Ejecting CDs
- Inserting Floppy Disks
- Ejecting Floppy Disks
- Adding Virtual Hard Disks to Virtual Machines (Templates)
- Editing Virtual Machine Properties
- Working with Machine Templates
- About Templates
- Accessing the Templates Page
- Reviewing Template Operations
- Summary of Template Operations
- Summary of Template States and Attributes
- Creating Templates
- Importing Templates
- Creating Templates from Scratch
- Creating Templates from Active Virtual Machines in Lab Manager
- Cloning Templates
- Copying Templates
- Undeploying Templates
- Sharing Templates
- Exporting Templates
- Consolidating Templates
- Editing Template Properties
- Deleting Templates
- Working with Configurations
- About Configurations
- Accessing Configurations
- Reviewing Configuration Operations
- Summary of Configuration Operations
- Summary of Configuration States and Attributes
- Creating Configurations
- Adding Virtual Machines to Existing Configurations
- Deploying Configurations
- Undeploying Configurations
- Capturing Configurations to the Library
- Checking Out Configurations from the Library
- Stopping Configurations
- Cloning Configurations
- Copying Configurations
- Exporting Configurations
- Importing Configurations
- Sharing Configurations
- Creating and Restoring Configuration LiveLinks
- Taking Snapshots and Reverting to Snapshots
- Editing Configuration Properties
- Viewing Details on Virtual Machines in a Configuration
- Accessing a Virtual Machine Console
- Accessing All Virtual Machine Consoles in a Configuration
- Deleting Configurations
- Working with Media
- Administering and Monitoring Lab Manager
- Monitoring Lab Manager
- Managing Users
- Managing Managed Server Systems
- Managing Storage Servers
- Configuring Network Settings
- Configuring Lab Manager Settings
- Troubleshooting Lab Manager
- Blank Screen Appears When Accessing Lab Manager
- Lab Manager Does Not Display Virtual Machine Console
- Duplicate IP Address Errors Appear
- Addition of SCSI Virtual Hard Disk Fails
- Mouse Navigation on Virtual Machine Console Fails
- Remote Access to Virtual Machine Fails
- LiveLink URL Error Appears
- Host Server CD Drive Cannot Install Software
- Importing a Virtual Machine as a Template Fails
- Import from VMFS Operation Fails
- Inserting Media from NFS Server Fails
- Lab Manager Server Fails, Loses Connectivity, or Reboots the System
- SMB Media Storage Server Fails
- Permanent Failure of Managed Server Occurs
- Temporary Failure of Managed Server Occurs (Reboot or Turn Off)
- Temporary Failure of Managed Server Occurs (Networking)
- Network Fencing
- Extending LM Tools
- Index
VMware® Lab Manager User’s Guide
162 VMware, Inc.
Why Should I Fence Configurations?
Typically,youwanttoenablenetworkfencingunderthesecircumstances:
Youhaveaconfigurationwithoneormoreservers,andyouanticipatecloningthe
configurationnumeroustimes.
Youhaveaconfigurationinvolvingadifficultandcomplexsetup,andcloningthe
configurationisaneasierroutethanrepeatingthesetup.
Withfencing,engineerscanrunmultiple,independenttestsonaconfiguration
deployedmultipletimes.Fencingisparticularlyusefulwhenadeveloperneedsto
examineabugwithoutinterruptingor
stoppingongoingtestingonaconfiguration.
LabManageralsoenablesyoutoreproducethebugatalatertimeifthedeveloperis
unavailable.
Moreinstancesofasmallerconfigurationmightrequireraisingthenumberoffenced
configurations.Asmallernumberofconfigurationscontainingmorevirtualmachines
ineachconfigurationmay
requireloweringthenumberoffencedconfigurations.No
penaltyexistsinchoosingalargernumber.
Fromaperformanceperspective,networkfencingimpactsthetrafficflowbetween
modules.FencingrequiresaslightlyhighernumberofresourcesontheManaged
Server,suchasmemory,CPU,networking,andvirtualmachineslots.Ifyouenable
fencingbutneveruseit,theseresourcesdonotcomeintoplay.
How Does Fencing Work?
Virtualmachinesinaconfigurationhavepre‐configured(internal)IPaddresses.When
youdeployvirtualmachinesinfencedmode,LabManagerassignsauniqueexternal
IPaddresstoeachofthesemachines.Throughtheseexternaladdresses,virtual
machinesbothinsideandoutsidethefencecancommunicatewitheachother.Lab
Manager
automatestheaddresstranslationandroutingsupportthroughthecreation
ofavirtualrouter.
Fencingaconfigurationdoesnotrequireanychangestoitsvirtualmachines.Withina
fencedconfiguration,virtualmachinescontinuetousepreassignedIPaddressesto
communicatewitheachother.FormoreinformationonIPaddressallocationin
fenced
configurations,see“UnderstandingIPAddressManagement”onpage 139.
Fencing Options
Youcandeployfencedconfigurationsinthreeways: