VMware, Inc.
51
Chapter 5 Discovery
VMware Infrastructure Discovery Flow
Table 5
‐
5
describes
the
typical
flow
for
VMware
Infrastructure
discovery.
Using VI-SDK for Detail Discovery
ADM
includes
the
VI
‐
SDK
protocol
as
an
option
when
creating
Detail
Discovery
policies.
VI
‐
SDK
is
a
VMware
proprietary
API
used
by
third
‐
party
applications
to
query
a
VMware
model,
control
VMware
Infrastructure’s
behavior,
and
receive
notifications
of
changes
in
the
VMware
Infrastructure
environment.
It
also
allows
its
user
to
discover,
configure,
and
monitor
all
aspects
of
VMware
ESX
Server
and
Virtual
Center.
Table 5-5.
VMware Infrastructure Discovery Flow
Step
Description
Results
1
Passive
discovery
(not
mandatory)
A
passive
discovery
policy
is
created
from
the
Manage
>
Passive
Discovery
page.
Since
the
VMware
Infrastructure
is
discovered
passively,
this
will
be
only
a
partial
discovery.
You
will
be
able
to
view
the
following
information:
The
VMware
Infrastructure
environment
as
a
whole,
the
ESX
Servers
and
services
(VirtualCenter,
Virtual
Infrastructure
Client).
Connections
between
ESX
Servers
and
VirtualCenter.
The
clients
that
are
managing
VirtualCenter
(that
is,
Virtual
Infrastructure
Client,
web
browser).
Connections
between
Virtual
Infrastructure
Client
and
VirtualCenter,
all
labeled
with
VMware’s
proprietary
protocol,
VMDB.
Third
‐
party
software
integrated
with
VMware
Infrastructure.
Virtual
machines.
2
Detail
discovery
A
detail
discovery
policy
is
created
from
the
Detail
Discovery
>
Policies
page.
When
entering
the
protocol
type
during
detail
discovery
policy
creation,
use
any
or
all
of
the
following
protocols:
SSH/SNMP
on
the
ESX
Server
included
in
the
VMware
Infrastructure
deployment.
WMI
on
the
host
running
VirtualCenter.
VI
‐
SDK
on
any
or
all
of
the
VMware
ESX
Servers
and
hosts
running
VirtualCenter.
The
VMware
Infrastructure
is
discovered
fully.
You
will
be
able
to
view
additional
information
that
was
discovered
after
passive
discovery:
Detailed
configuration
information
of
all
ESX
Servers
and
services
(VirtualCenter),
including
configuration
information
and
license
information.
For
each
ESX
Server,
all
the
virtual
machines
defined
on
it,
including
the
detailed
hardware
configuration
information
for
each
virtual
machine.
3
Application
pattern
creation
(optional)
After
performing
passive
or
detail
discovery,
you
might
decide
that
you
want
ADM
to
automatically
detect
instances
of
VMware
Infrastructure
environments
in
your
network.
To
do
this,
create
an
application
pattern
from
the
Manage
>
Application
Pattern
Definitions
page.
ADM
automatically
detects
instances
of
VMware
Infrastructure
environments
in
your
network
and
will
populate
the
MDR
with
the
relevant
data.
4
Virtual
Collector/vCollec
tor
deployment
(optional)
Virtual
machines
running
on
the
same
physical
host
communicate
with
each
other
without
going
out
to
the
network.
Since
ADM
listens
to
network
traffic,
it
will
not
have
visibility
into
this
communication.
In
this
case,
the
vCollector
must
be
deployed.
Details
on
vCollector
deployment
is
found
in
the
VMware
vCenter
Application
Discovery
Manager
Version
6.0
vCollector
Installation
and
Configuration
Guide.
Summary of Contents for VCENTER APPLICATION DISCOVERY MANAGER 6.1.1 - RESPOSITORY
Page 6: ...ADM User s Guide 6 VMware Inc...
Page 14: ...ADM User s Guide 14 VMware Inc...
Page 16: ...ADM User s Guide 16 VMware Inc...
Page 24: ...ADM User s Guide 24 VMware Inc...
Page 30: ...ADM User s Guide 30 VMware Inc...
Page 54: ...ADM User s Guide 54 VMware Inc...
Page 74: ...ADM User s Guide 74 VMware Inc...