This article describes the cause of an issue with the Syslog file showing an SNMP trap. The article also provides information on how to resolve it. The trap is similar to the following:
Dec 4 12:41:18 name-rtr snmptrapd: 12:41:18 TRAP6.TEXTPASS-AMS-MIB::schedulingIncomplete TEXTPASS-GEN-MIB::deviceType.0 = STRING: "AMS" from name-rtr
schedulingIncomplete trap is generated if the delivery scheduler is not able to serve all pending queues for a time longer than the period set in the
amsPropSchedulerIncompleteThreshold property (the value range is
3600, and the default value is
Resolving the Issue
amsPropSchedulerIncompleteThreshold can be changed in the configuration files
A value too low for this threshold can result in unnecessary warnings. The
schedulingIncomplete trap is closely related to the max delivery rate. If this trap is issued often, even though the threshold attribute has been set to a reasonable value, the AMS could experience delivery problems (causing extra retries), and you may need a license upgrade.
You can check more details in the chapter 3.300 schedulingIncomplete of the SNMP Trap Reference Guide, and the chapter 10.2.1.48 amsschedulerincompletethreshold of the AMS Operator Manual, available in the NewNet Download Center.