OPERATIONAL DEFECT DATABASE
...
...
The Ethernet Link-OAM daemon process intermittently outputs CPU_STARVED messages when the CPU usage is not significantly high. Link-OAM sessions may also flap.
This issue is seen when the timestamp used by Link-OAM is updated by NTP. In some cases, the timestamp adjustment may caused Link-OAM to try to start timers for an invalid length of time. This will cause link-OAM to stop sending heartbeat messages
Restarting the link-OAM process may reduce the frequency of the messages. If it is possible to remove NTP configuration, this will stop the timestamp update and will prevent the bug from being hit.
Link-OAM includes algorithms to track whether its periodic heartbeat timer is firing at the required intervals. These are used both to check for CPU starvation and to update the time-to-next heartbeat value to prevent drift. The timestamp used for these calculations was incorrectly chosen to be one which varies with NTP adjustments, so the algorithms can be disrupted by NTP-driven changes in the router clock.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
