Steps to adjust the MaximumNumberOfSystems Parameter for Device Discovery

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

In environments with a large number of devices, the discovery process may stop prematurely after identifying only a small subset of systems.

This often occurs because the MaximumNumberOfSystems parameter—which defines the processing scope for the topology manager—is set to a value lower than the number of devices you are attempting to discover.

Environment

All Supported Smarts releases

Resolution

You can verify the current limit and adjust it to accommodate your discovery requirements:

1. Verify the current configuration 

Run the following command to check the current value for the MaximumNumberOfSystems attribute:

./dmctl -s <domain_name> get ICF_TopologyManager::ICF-TopologyManager::MaximumNumberOfSystems

Example: ./dmctl -s AM-PM get ICF_TopologyManager::ICF-TopologyManager::MaximumNumberOfSystems

2. Update the configuration 

If the returned value is insufficient for your environment, update the attribute to a higher limit that matches your requirements. Replace <new_value> with the target number of devices:

On the InCharge APM domain manager, open Domain Manager Admin Console → Select the respective AM-PM domain and review the Current Systems Limit as shown below and hit Apply:

To set this value as a persistent setting, please update the discovery.conf as follows:

<Base-Dir>/smarts/bin/sm_edit conf/discovery/discovery.conf

Add the following entries:

#MaximumNumberOfSystems to set the count of devices that an InCharge AM-PM can discover.
#MaximumNumberOfSystems Default = 50
MaximumNumberOfSystems = <enter_new_value>

Restart the Domain Manager for the settings to take effect. 

Additional Information

Reference Documentation: Setting a current system limit for the topology