VMware, Inc.
59
Chapter 7 Working with Configurations
The
Block
In
and
Out
option
is
useful
in
these
circumstances:
You
are
testing
software
viruses
that
need
to
remain
isolated
from
the
physical
network.
You
are
testing
a
client
‐
server
application
in
isolation.
Virtual Networks
Virtual
networks
are
based
on
the
specifications
defined
in
a
network
template
and
get
created
by
Lab Manager
when
you
deploy
a
configuration.
See
“Setting
Up
Network
Templates”
on
page 29
and
“Managing
Network
Templates”
on
page 123
for
more
information
about
network
templates.
Virtual
networks
are
configuration
local
networks.
They
exist
inside
configurations
and
do
not
span
configurations.
Virtual
machines
connected
to
a
virtual
network
cannot
communicate
with
virtual
machines
connected
to
a
different
virtual
network.
Each
virtual
network
that
Lab Manager
creates
is
unique
and
isolated
from
other
virtual
networks,
even
if
the
networks
are
based
on
the
same
network
template.
vSwitches
and
port
groups
created
by
Lab Manager
for
virtual
networks
are
named
with
the
network
name
concatenated
with
IDs
associated
with
the
network,
installation,
and
host.
Connecting Virtual Networks to Physical Networks
Virtual
networks
can
be
connected
to
physical
networks
at
deploy
time.
Connecting
virtual
networks
to
physical
networks
provides
the
virtual
machines
using
those
virtual
networks
access
to
physical
networks.
Lab Manager
uses
a
virtual
router
to
connect
the
virtual
and
physical
networks.
Virtual to Physical Network Connectivity
Two
connectivity
modes
are
available
when
you
connect
a
virtual
network
to
a
physical
network:
Allow
In
and
Out
–
Virtual
machines
can
communicate
with
machines
on
the
selected
physical
network,
and
machines
on
the
selected
physical
network
can
communicate
with
virtual
machines
inside
the
configuration.
Allow
Out
–
Virtual
machines
in
the
configuration
can
initiate
communication
with
machines
on
the
selected
physical
network
and
can
receive
messages
back
on
the
same
connection.
Machines
on
the
selected
physical
network
cannot
initiate
communication
with
virtual
machines
inside
the
configuration.
Host Spanning
Host
Spanning
is
a
feature
that
enables
the
virtual
machines
in
a
configuration
that
uses
fencing
or
virtual
networks
to
be
deployed
on
different
ESX/ESXi
hosts.
When
you
deploy
a
configuration
that
uses
Host
Spanning,
some
of
the
virtual
machines
can
get
deployed
to
one
ESX/ESXi
host
and
some
of
the
virtual
machines
can
get
deployed
to
a
different
host.
For
a
configuration
that
is
unfenced
and
does
not
include
any
virtual
networks,
Lab Manager
can
always
deploy
its
virtual
machines
across
multiple
hosts.
For
a
configuration
that
is
fenced
or
includes
a
virtual
network,
you
can
enable
Host
Spanning,
provided
that
the
configuration
has
access
to
an
enabled
host
spanning
transport
network.
If
you
do
not
enable
Host
Spanning
for
a
configuration
that
uses
fencing
or
a
virtual
network,
all
of
its
virtual
machines
must
deploy
to
the
same
host.
In
some
cases,
this
restriction
may
prevent
you
from
deploying
a
configuration.
For
example,
for
a
large
configuration,
there
might
not
be
any
single
host
available
that
has
enough
resources
to
deploy
the
configuration.
In
addition,
Host
Spanning
is
required
in
order
to
support
VMware
DRS
and
HA
for
configurations
that
use
fencing
or
a
virtual
network.
Host Spanning Networks
Host
spanning
networks
are
logical
overlay
networks
that
use
the
resources
of
an
underlying
host
spanning
transport
network
to
enable
Host
Spanning.
Lab Manager
creates
a
host
spanning
network
when
you
deploy
a
configuration
with
Host
Spanning
enabled.
Host
spanning
networks
are
not
visible
within
Lab Manager.
Summary of Contents for Lab Manager 4.0
Page 12: ...Lab Manager User s Guide 12 VMware Inc...
Page 18: ...Lab Manager User s Guide 18 VMware Inc...
Page 22: ...Lab Manager User s Guide 22 VMware Inc...
Page 26: ...Lab Manager User s Guide 26 VMware Inc...
Page 48: ...Lab Manager User s Guide 48 VMware Inc...
Page 88: ...Lab Manager User s Guide 88 VMware Inc...
Page 108: ...Lab Manager User s Guide 108 VMware Inc...
Page 122: ...Lab Manager User s Guide 122 VMware Inc...
Page 126: ...Lab Manager User s Guide 126 VMware Inc...
Page 148: ...Lab Manager User s Guide 148 VMware Inc...