26.3.1 Configuring a discovery schedule

NNM discovery processes can be executed independently. To migrate discovery to NNMi, all you need to do is to transfer the interval at which NNM discovers nodes.

The following schedule configuration areas are not used in NNMi and cannot be migrated:

• Connector device topology check. Topology checking is now performed automatically every time NNMi finds a trigger indicating the possibility of a change.

• Configuration check. NNMi now performs a configuration check at the time of scheduled discovery or based on various triggers.

• Layer 2 (expanded topology) discovery action. Because NNMi performs Layer 2 discovery when it finds a device, there is no need to schedule this action separately.

• Automatic adjustment of the discovery polling interval

1. Determine when NNM is performing rediscovery.

   a. In the user interface, choose Options and then Network Polling Configuration.

   b. On the IP Discovery tab, check Discovery Polling Interval.

   - If a fixed interval is used, make a note of the value so you can set it in NNMi.

   - If NNM is using an automatically adjusted interval, NNM stands by for a maximum of 24 hours. You can leave NNMi at the default value of 24 hours or you can select a new value.

   - If auto-discovery is not enabled, check the cycle in Perform Configuration Checks on the General tab, and make a note of the value so you can set it in NNMi.

   

   

2. In the NNMi console, from the Configuration workspace, choose Discovery > Discovery Configuration, and then set in Rediscovery Interval the value determined in step 1.

   

   

   All other configuration updates are added automatically, making configuration simpler and discovery more efficient than in NNM.

To Page Top