VMware VC-VLM4-C User Guide - Page 60

Host Spanning Transport Networks, Setting Up a Host Spanning, Deploying and Undeploying Configurations

Page 60 highlights

Lab Manager User's Guide Host Spanning Transport Networks Host spanning transport networks are Lab Manager resources that enable Host Spanning and consist of a vNetwork Distributed Switch and a LAN or VLAN. Host spanning transport networks require a VMware vSphere Enterprise Plus license and ESX/ESXi 4.0 hosts. If your environment meets these requirements, you can create a vNetwork Distributed Switch, which is a type of vSphere virtual switch that spans multiple ESX/ESXi hosts. Lab Manager creates and uses a virtual machine (VMwareLM‐ServiceVM) on each of these hosts to send packets between the hosts using the vNetwork Distributed Switch. Setting Up a Host Spanning A configuration that uses fencing or virtual networks must meet the following requirements before you can deploy it across multiple hosts.  A host spanning transport network exists and is enabled. See "Add a Host Spanning Transport Network" on page 21 and "Enable or Disable a Host Spanning Transport Network" on page 104.  Host Spanning is enabled for the organization containing the configuration. See "Disable or Enable Host Spanning" on page 103.  Host Spanning is enabled for at least two ESX/ESXi hosts that are available to the configuration. See "Disable and Enable Host Spanning for a Host" on page 92. Deploying and Undeploying Configurations Deploying a configuration registers its virtual machines on ESX/ESXi hosts and provides access to its virtual machine consoles and guest operating systems. You can deploy an entire configuration or individual virtual machines in the configuration. See "Deploy a Virtual Machine" on page 73 for information about deploying an individual virtual machine in a configuration. You can only deploy workspace configurations. If you want to deploy a library configuration, clone it to a workspace first and then deploy it. The first time you deploy a configuration, all of its virtual machines with guest customization enabled go through a customization process, which might involve multiple reboots. Do not shut down the virtual machines until the customization is complete. When you deploy a configuration, you can either provide custom settings or use the default settings. Deploy a Configuration with Custom Settings When you deploy a configuration with custom settings, you can specify various deployment options that determine the configuration's network connectivity, deployment lease, resource pool, and so on. To deploy a configuration with custom settings 1 Move the pointer over the configuration name and select Deploy. If you have already partially deployed the configuration, you can only modify certain settings. 2 Select the Fence Virtual Machines check box to deploy the configuration in fenced mode. This option is only available if the configuration allows fencing and includes a physical network that also allows fencing. Use the Connectivity drop‐down menu to select a connectivity mode for each physical network. See "Fencing Connectivity" on page 57 for more information. 3 Select the Connect Virtual Networks to Physical Networks check box to connect virtual networks to physical networks. This option is only available if the configuration includes a virtual network. Select a physical network to connect to and use the Connectivity drop‐down menu to select a connectivity mode. See "Virtual to Physical Network Connectivity" on page 59 for more information. 60 VMware, Inc.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180

Lab Manager User’s Guide
60
VMware, Inc.
Host Spanning Transport Networks
Host spanning transport networks are Lab Manager resources that enable Host Spanning and consist of a
vNetwork Distributed Switch and a LAN or VLAN. Host spanning transport networks require a VMware
vSphere Enterprise Plus license and ESX/ESXi 4.0 hosts. If your environment meets these requirements, you
can create a vNetwork Distributed Switch, which is a type of vSphere virtual switch that spans multiple
ESX/ESXi hosts. Lab Manager creates and uses a virtual machine (VMwareLM
ServiceVM) on each of these
hosts to send packets between the hosts using the vNetwork Distributed Switch.
Setting Up a Host Spanning
A configuration that uses fencing or virtual networks must meet the following requirements before you can
deploy it across multiple hosts.
A host spanning transport network exists and is enabled. See
“Add a Host Spanning Transport Network”
on page 21 and
“Enable or Disable a Host Spanning Transport Network”
on page 104.
Host Spanning is enabled for the organization containing the configuration. See
“Disable or Enable Host
Spanning”
on page 103.
Host Spanning is enabled for at least two ESX/ESXi hosts that are available to the configuration. See
“Disable and Enable Host Spanning for a Host”
on page 92.
Deploying and Undeploying Configurations
Deploying a configuration registers its virtual machines on ESX/ESXi hosts and provides access to its virtual
machine consoles and guest operating systems. You can deploy an entire configuration or individual virtual
machines in the configuration. See
“Deploy a Virtual Machine”
on page 73 for information about deploying
an individual virtual machine in a configuration.
You can only deploy workspace configurations. If you want to deploy a library configuration, clone it to a
workspace first and then deploy it.
The first time you deploy a configuration, all of its virtual machines with guest customization enabled go
through a customization process, which might involve multiple reboots. Do not shut down the virtual
machines until the customization is complete.
When you deploy a configuration, you can either provide custom settings or use the default settings.
Deploy a Configuration with Custom Settings
When you deploy a configuration with custom settings, you can specify various deployment options that
determine the configuration’s network connectivity, deployment lease, resource pool, and so on.
To deploy a configuration with custom settings
1
Move the pointer over the configuration name and select
Deploy
.
If you have already partially deployed the configuration, you can only modify certain settings.
2
Select the
Fence Virtual Machines
check box to deploy the configuration in fenced mode.
This option is only available if the configuration allows fencing and includes a physical network that also
allows fencing.
Use the
Connectivity
drop
down menu to select a connectivity mode for each physical network. See
“Fencing Connectivity”
on page 57 for more information.
3
Select the
Connect Virtual Networks to Physical Networks
check box to connect virtual networks to
physical networks.
This option is only available if the configuration includes a virtual network.
Select a physical network to connect to and use the
Connectivity
drop
down menu to select a connectivity
mode. See
“Virtual to Physical Network Connectivity”
on page 59 for more information.