IntroductionYou may need to re-initialize discovery in your installation based on your changing requirements.? This procedure describes how to do this.
ProcedureWARNING: Do NOT perform this procedure on NMS 7.0 or later. It can cause severe queue backups in larger environments.
Follow these steps;
For every discovery_agent host:
?????? 1.? Stop the discovery_agent.
?????? 2.? Stop discovery_server.
?????? 3.? Delete discovered computers from db by running the following queries:
delete from CM_COMPUTER_SYSTEM;
delete from CM_NIMBUS_ROBOT;
delete from DS_ROBOT_XREF;
????? ? 4.? On every discovery_agent system, remove local database from discovery_agents by deleting
??????? 5.? On the discovery_server host remove the database for each hub by deleting the hub directories in:
??????? 6.? Restart nis_server to clean up the groups.
At this time your discovery is empty. All your views should be empty. You may get transient ?failed to connect? messages, but that is expected. Although you can adjust your discovery scopes at any time, now is a good time to adjust them if needed before restarting discovery. Once you are ready to restart discovery, follow these steps to do so:
??????? 1. Start discovery_server probe.
??????? 2. Start all discovery_agents.
??????? 3. Wait for network discovery to complete.
Review the results in either UMP => NimsoftRemoteAdmin or in Infrastructure Manager => Nis Manger.