It is never nice when devices on a network go belly-up, but to know why or what happened right before they went belly-up, is crucial.
By enabling CPU and Memory thresholding, you can be sure to get those vital notifications when it happen allowing you to respond a lot quicker.
When a router is overloaded by processes, the amount of available memory might fall to levels insufficient for it to issue critical notifications, so the first step is to reserve some memory:
memory reserve critical {kilobytes}
Now we can configured the thresholds.
This example specifies a threshold of 20000 KB of free processor memory before the router issues notifications:
memory free low-watermark processor 20000
This example specifies a threshold of 20000 KB of free I/O memory before the router issues notifications
memory free low-watermark io 20000
Lastly enable CPU Rising and Falling threshold notifications.
This example shows how to set a falling CPU thresholding notification for total CPU utilization. When the total CPU utilization, rises above 80 percent for a period of 5 seconds or longer a rising threshold notification will be triggered. When the total CPU utilization falls below 30 percent for a period of 5 seconds or longer, a falling threshold notification will be sent:
process cpu threshold type total rising 80 interval 5 falling 30 interval 5
Routing-Bits 