27. Periodic
Monitoring
MN700004 Rev 01
327
7. To check CPU usage monitoring, the trap output can be routed to the console:
device-name
#
configure terminal
device-name
(config)#
log cli-console
device-name
(config)#
log-history nvram trap errors
Traps are displayed on the CLI console. Note that the CPU usage is checked at 10 second
intervals, as specified with the
period
command:
tHiSwMonitr: 1970/01/01 00:54:43 alerts: CPU Usage BIST fail:
7(limit 5)
tHiSwMonitr: 1970/01/01 00:54:43 alerts: CPU usage delta: current 7
tHiSwMonitr: 1970/01/01 00:54:53 alerts: CPU Usage BIST OK: 5(max 7)
tHiSwMonitr: 1970/01/01 00:55:03 alerts: CPU Usage BIST fail:
6(limit 5)
tHiSwMonitr: 1970/01/01 00:55:03 alerts: CPU usage delta: current 6
tHiSwMonitr: 1970/01/01 00:55:23 alerts: CPU usage delta: current 7
tHiSwMonitr: 1970/01/01 00:55:33 alerts: CPU Usage BIST OK: 5(max 7)
RAM Usage Monitoring
In the following example, RAM usage monitoring is enabled and configured with
period
,
limit
and
delta
commands.
1. Enable RAM usage monitoring:
device-name
(config)#
monitor ram-usage enable
2. Enter into the RAM usage Monitoring Configuration mode:
device-name
(config)#
monitor ram-usage
3. Display RAM usage monitoring settings:
device-name
(config monitor ram-usage)#
show
Period : 30 sec.
Traps : Enabled
Log : Enabled
Limit value : 1000Kb
4. Set the limit for RAM usage monitoring alerts to 10%:
device-name
(config monitor ram-usage)#
limit 10
5. Set the delta to trigger alerts for changes of 3% in the error rate:
device-name
(config monitor ram-usage)#
delta 3 less
6. Set the period of alerts to 5 seconds:
device-name
(config monitor ram-usage)#
period seconds 5
device-name
(config monitor ram-usage)#
end
7. Display RAM usage monitoring configuration:
