User`s guide

Table Of Contents

ADM User’s Guide

48 VMware, Inc.

Discovery Strategy for Using Only Detail Discovery for Dependencies

HereisonesuggestedstrategytousewhencreatingaDetailDiscoveryplanfordiscoveringdependencies:

1EnsurethatyousetupthePassiveDiscoveryscopewiththeIPrangesofthehostswiththedependencies

youwantincludedorexcludedfromdiscovery.

2 CreateaDetailDiscoverypolicy(orsetofpolicies,

dependingonthediscoveryprotocol)withaShallow

planthatwillrunfrequently(forexample,allhostsonceaday)toquicklyscanthenetworkforminimal

OSandnetworkinginformation.

3 CreateaDetailDiscoverypolicy(orsetofpolicies,dependingonthediscoveryprotocol)withaDeepplan

thatwill

runlessfrequently(forexample,discoverahostonceeveryfewdays)thanthepolicycreatedin

Step 1.

4OncethepoliciesinStep 2andStep 3havediscoveredasubstantialpartofthenetwork,andtherateof

newdiscoverydecreases:

a CreateacustomdiscoveryplanthathastheonlyNetwork

Connectionsenabled.

b CreateanewDetailDiscoverypolicythatrunsfrequentlyandapplythecustomdiscoveryplan

createdintheprevioussteptoit.

ThefrequentSHALLOWscan,inStep 2,servestwopurposes.First,hostswithmorethanoneIPare

mergedtoappearasasinglehost.Second,DetailDiscovery

policieswillbetailoredtomatchthe

discoveryprotocolwiththeOSofthehostsintheirscope.

Thislessfrequent,DEEPpolicy,createdinStep 3,isusedtoretrievedeepconfigurationinformationofthe

environment.

TheNetworkConnectionspolicy,definedinStep 4,willdiscoveronlynetworkconnections,anddo

so

afterthenewdiscoveryrateshavedecreased.ThisisimportantbecauseNetworkConnectionplanscan

haveaperformancepenalty,whichisthereasonthatdiscoveryofnetworkdependenciesisexcludedfrom

theDEEPdiscoveryplanbydefault.

OTETheonlyNetworkConnectionsoptionisdisabledbydefault.

OTEThisphasedapproachcreatesadelayofafewdaystodiscovernetworkdependencies,becauseoption 3

isenabledonlyafterthediscoveryratedecreases.Thisapproachisusedtoavoidtheperformancepenalty

causedbyusingDetailDiscoverytodiscoverdependencies(whichisthereasonthatdiscoveryofnetwork

dependencies

isexcludedfromtheDEEPdiscoveryplanbydefault).Bystartingtodiscovernetwork

dependenciesonlyaftermuchoftheenvironmenthasbeendiscoveredbyDetailDiscovery,theperformance

penaltyisminimized.Alternatively,ifthereisanimmediateneedtoseenetworkdependenciessoonerrather

thanlater,thereistheoption

ofcreatingacustomdiscoveryplanthatincludesnetworkdependenciesand

runningitimmediately.