Batch device synchronization first pulls all devices from Smarts Manager and Network Configuration Manager, and attempts to match the devices based upon an algorithm that balances performance with accurate results in a wide variety of environments. Due to the potentially long-running and processor intensive nature of full synchronization, it is a manual step to begin the initial synchronization.
The batch device synchronization algorithm attempts to match devices first by name matching, then through management IP (SNMP) addresses, and if needed, it will inspect devices down to the interface level to produce a mapping.
This reconciliation is then used for multiple purposes.
In event notification, it is used to associate device events with the proper Smarts Manager device, even when names or management IP addresses do not match.
Credential synchronization uses the mapping to ensure that password changes in Network Configuration Manager are propagated to the correct Smarts Manager device.
It facilitates contextual launch by ensuring that launch points in Smarts Manager lead to the correct devices in Network Configuration Manager.
Once the mapping is complete, devices that are not managed by IP Availability Manager, but are managed by Network Configuration Manager are put on the Smarts Manager pending list. Devices that are managed by IP Availability Manager, but not managed by Network Configuration Manager are scheduled for discovery in Network Configuration Manager.
Also, when batch synchronization is complete, the adapter enables active device synchronization, and credential synchronization.
Batch synchronization can be run at any time if the mapping information becomes outdated for any reason. For example, if the server hosting the adapter was down for a number of days, the device mapping could be out of date, depending on the rate of change in the network.
Run batch synchronization again after rebooting the server to immediately synchronize the systems. Remember, with a large number of devices, this is a long running operation that is computationally expensive, so it is advisable to complete this operation during off-peak hours.Note:
Until the initial batch synchronization completes successfully, active synchronization and credential synchronization remain inactive.