Configuring Log Source Thresholds; Checkpointing Logs - Cisco ASR 5500 System Administration Manual

System Logs
Both traps can be enabled or suppressed via the Global Configuration mode snmp trap command.

Configuring Log Source Thresholds

There are three Global Configuration mode commands associated with configuring and implementing Log
Source thresholds.
1 threshold ls-logs-volume – sets the parameters for the upper and lower thresholds for generating and
clearing traps/alarms respectively.
2 threshold poll ls-logs-volume interval – establishes the polling interval for this threshold.
3 threshold monitoring ls-logs-volume – turns monitoring of this threshold on and off.
Use the following example to configure syslog servers:
configure
[ default ] threshold ls-logs-volume upper_percent [ clear lower_percent ]
[ default ] threshold poll ls-logs-volume interval duration
[ no ] threshold monitoring ls-logs-volume
end
Notes:
• upper_percent and lower_percent are expressed as integers from 0 to 100. Default value for upper_percent
• threshold poll ls-logs-volume interval sets the polling interval in seconds. The default interval is 300
• threshold monitoring ls-logs-volume enables or disables this feature.
You can verify the configuration of this threshold by running the Exec mode show threshold command.
Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Checkpointing Logs

Checkpointing identifies logged data as previously viewed or marked. Checkpointing allows you to only
display log information since the last checkpoint.
Individual logs may have up to 50,000 events in the active log. Checkpointing the logs results in at most
50,000 events being in the inactive log files. This gives a maximum of 100,000 events in total which are
available for each facility logged.
You check point log data via the Exec mode logs checkpoint command to set the log contents to a well-known
point prior to special activities taking place. This command may also be a part of periodic regular maintenance
to manage log data.
Checkpointing logs moves the current log data to the inactive logs. Only the most recently check pointed data
is retained in the inactive logs. A subsequent check pointing of the logs results in the prior check pointed
inactive log data being cleared and replaced with the newly check pointed data. Checkpointed log data is not
available for viewing.
is 90%. If lower_percent is not specified, the default clear value is upper_percent.
seconds (5 minutes).
Configuring Log Source Thresholds
ASR 5500 System Administration Guide, StarOS Release 21.5
147