Performing an incremental discovery

After a full discovery with full topology split, you should use incremental discovery with incremental topology split for topology updates. Topology updates are due to the adding of new devices to the managed IP network, the decommissioning of devices, or the changing of configurations.

Incremental discovery is invoked by adding new devices as seed devices to the Topology Split Manager or placing the new devices on the Topology Split Manager’s Pending Devices list. Seed devices are specified in a seed file or in Add Agent commands.

Incremental topology split assigns the new devices to an existing topology split, which might result in the moving of some devices from one IP Availability Manager to another in an attempt to improve the split.

To perform an incremental discovery with incremental topology split:

1. Configure the Topology Split Manager as follows:

   • Enable topology split

     Set the NumberOfDomains configuration parameter to the number of domains that are specified in the TSM_BASEDIR/smarts/local/conf/discovery/topo-split/ topo-split.conf file. That number must be greater than 1.

     • Select normal mode

       Ensure that the IsTrialLearningEnabled configuration parameter is FALSE.

     • Select incremental topology split

       Ensure that the IsSplitFromScratch configuration parameter is FALSE.

     • Optional but recommended: Enable automatic topology synchronization

       Set the IsTopoSyncEnabled configuration parameter to TRUE.

     • Optional but recommended: Enable edge management

       Set the EnableAutoEdgeManagement configuration parameter to TRUE. Note that automatic topology synchronization must be enabled before edge management can be enabled.

     • Enable the TSM hook script

       Set the IsTSMHookEnabled configuration parameter to TRUE.

2. Create a seed file and add the new devices to the seed file.

   The Topology Split Manager uses the hostnames or IP addresses of the seed devices that are specified in the seed file to discover the devices in the managed IP network. The seed file resides in the TSM_BASEDIR/smarts/local/conf directory. The VMware Smart Assurance IP Manager User Guide includes the procedure for creating seed files.

3. Import the seed file and initiate an incremental discovery with incremental topology split.

   “Initiating a discovery” on page 81 describes various methods to import a seed file and initiate a discovery. One method is to open a Domain Manager Administration Console that is attached to the Topology Split Manager and do the following:

   Select Topology > Import from seed file to launch the Import From Seed File dialog box. In the dialog box, specify the complete path and name of the seed file. (By default, the path to the seed file is TSM_BASEDIR/smarts/local/conf.) Click OK to import the seed devices and to start the incremental discovery with incremental topology split.

   If IsTopoSyncEnabled is TRUE, the Topology Split Manager splits the new topology and places a seed file for each domain in the Topology Split Manager’s local/logs directory, and in each IP Availability Manager’s local/logs directory. The Topology Split Manager adds the new devices in a domain’s seed file to the Pending Devices list of the appropriate IP Availability Manager. It also deletes outdated devices from the appropriate IP Availability Manager’s repository. Outdated devices are devices that are already in the IP Availability Manager’s topology and are either not assigned by the topology-split algorithm or are assigned and are unmanaged.

   If IsTopoSyncEnabled is FALSE, the Topology Split Manager splits the new topology and places a seed file for each domain in the Topology Split Manager’s local/logs directory, but not in each IP Availability Manager’s local/logs directory. Because the seed files are retained by the Topology Split Manager, administrators can use them later to initiate IP Availability Manager discovery manually.

   Note:

   If you use these seed files to initiate IP Availability Manager discovery manually, ensure that you use the set of seed files with the most recent timestamp.

   Each new seed file in the Topology Split Manager’s local/logs directory contains previously discovered devices and newly discovered devices, whereas each new seed file in a domain’s local/logs directory contains the new devices only. Outdated devices are commented out in the domain’s seed file.

4. If IsTopoSyncEnabled is TRUE: For each IP Availability Manager, go to the BASEDIR/smarts/bin directory in the appropriate IP Manager installation area and enter the following command to invoke a pending discovery:

                  dmctl -s <AM name>   invoke ICF_TopologyManager::ICF-TopologyManager discoverPending
                  dmctl -s AM001 invoke 
                  
                    ICF_TopologyManager::ICF-TopologyManager discoverPending
               

5. If IsTopoSyncEnabled is FALSE: For each IP Availability Manager, use the associated seed file in the Topology Split Manager’s local/logs directory to manually initiate a discovery at the IP Availability Manager. If the IP Availability Manager is on a different host, copy the associated seed file to that host and place it in the BASEDIR/smarts/local/conf directory.

6. After the IP Availability Managers have completed their discoveries, check all critical numbers to determine if they meet your predefined criteria.