Determine if an external script is starting discovery process on the Domain Manager via logs

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

Ways to determine if an external script is starting discovery process the Domain Manager via logs

Environment

All Supported Smarts relesaes

Resolution

Smarts will not kick off a discovery automatically on its own. However, Smarts does have the capability to perform an automatic pending list discovery and discover-all.

Here are three log excerpts that would work as examples of what to look for in your logs:

1: First example of logs

ADTM-N-TMG2_STATUS_START-Last discovery started at <Date & Time>

ADTM-N-AD_LOG-<Date & Time>, at 'pre process t@<EPOCH>', while
discovering '', Pre-Processor-Driver starts

ADTM-N-AD_LOG-<Date & Time>, at 'pre process t@<EPOCH>', while
discovering '', Pre-Processor-Driver ends

ADTM-N-AD_LOG-<Date & Time>, at 'pre process t@<EPOCH>', while
discovering '', Pre-Processor-3Com-CB9000-Driver starts

ADTM-N-AD_LOG-<Date & Time>, at 'pre process t@<EPOCH>', while
discovering '', Pre-Processor-3Com-CB9000-Driver ends

ADTM-N-AD_LOG-<Date & Time>, at 'pre process t@<EPOCH>', while
discovering '', Pre-Processor-Custom-Driver starts

<Date & Time> custom-start-fulldscv.asl-<EPOCH>: Activated (srvrType=SOAK; appVar=/appl/gfpip/gfp-ip5.05/var; macName=<name>
ADTM-N-AD_LOG-<Date & Time>, at 'pre process t@<EPOCH>', while
discovering '', Pre-Processor-Custom-Driver ends

The last line above indicates that there was a full discovery initiated through the asl file : "custom-start-fulldscv.asl" and the above log does tells the same.

2: Second example of logs:

ADTM-N-TMG2_STATUS_START-Last discovery started at <Date & Time>

ADTM-N-AD_LOG-<Date & Time>, at 'TM rediscover t@<EPOCH>', while
discovering '#.#.#.#', start rediscovery

The above message indicates that there was a selective re-discovery kick started on a particular device "ch0il01ebc.els-an.att.net".  The letters TM stand TopologyManager as in sm_tpmgr, perl script or an asl script.   
The exact source will not be known here.

3: Third example of logs:

ADTM-N-TMG2_STATUS_START-Last discovery started at <Date & Time>

ADTM-N-AD_LOG-<Date & Time>, at 'TM rediscover t@<epoch>', while
discovering '#.#.#.#', start rediscovery

This also explains that a re-discovery was triggered on a particular device through external client. Again, it is the TopologyManager(TM) that kicks it off.

The above three examples show two reasons why discovery was triggered.

1: custom-start-fulldscv.asl was executed.
2: The TopologyManager was triggered to start a discovery on a single device.