Problem: Cannot discover more than one device, or device resynchronization fails

Consider the following:

When using SNMPv3 encryption, the engine ID of the managed device must be unique. As well, SNMP issues may result in Polling Problem alarms. Otherwise, the following issues may occur:
- unreliable or slow discovery of network devices
- resynchronization during scheduled polling fails
- slow communication and synchronization times
- polling fails completely
When NFM-P resynchronizes some functions on an NE, for example, BGP configurations for the 7750 SR, the SNMP packets may be broken into two or more smaller packets, when the maximum PDU size of 9216 bytes is exceeded.
Each MIB entry policy has its own polling interval. When there is insufficient time in a polling interval for a resynchronization to occur, the interval may need to be changed to ensure proper resynchronization.


1	For resynchronization issues that may be caused due to insufficient MIB polling intervals.
2	Choose Administration→Mediation from the NFM-P main menu. The Mediation (Edit) form opens with the General tab selected.
3	Ensure that the Polling Admin State is Up. Note: Polling and scanning use system resources, and can increase the amount of management traffic. Consider your network needs and network management domain capabilities before setting these parameters.
4	Check the MIB polling intervals for different managed devices, as required, by clicking on the MIB Entry Policies tab. A list of MIBs appears, organized by managed device type. Select a MIB in the list and click Properties. Configure the Polling Interval parameter to ensure that sufficient time is configured for the polling to occur. Configure the Administrative State of polling for the MIB entry, if required. Click OK to save the changes and close the form, or click Cancel to close the form without saving changes, as required. End of steps