![Cisco ASR 9000 Serie Configuration Manuals Download Page 334](http://html.mh-extra.com/html/cisco/asr-9000-serie/asr-9000-serie_configuration-manuals_66679334.webp)
The
clear logging onboard
command permanently deletes all OBFL data for a node or for all nodes.
Do not clear the OBFL logs without specific reasons because the OBFL data is used to diagnose and
resolve problems in FRUs.
Caution
If OBFL is actively running on a card, issuing the
clear logging onboard
command can result in a corrupt
or incomplete log at a later point in time. OBFL should always be disabled before this command is issued.
Caution
For more information, see the
Onboard Failure Logging Commands
module in the
Cisco ASR 9000 Series
Aggregation Services Router System Monitoring Command Reference
.
Configuration Examples for OBFL
This section provides these configuration examples:
Enabling and Disabling OBFL: Example
The following example shows how to disable OBFL:
RP/0/RSP0/CPU0:router(admin-config)#
hw-module all logging onboard disable
The following example shows how to enable OBFL again:
RP/0/RSP0/CPU0:router(admin-config)#
no hw-module all logging onboard disable
The following example shows that OBFL is enabled and message severity level is reset to the default:
RP/0/RSP0/CPU0:router(admin-config)#
no hw-module all logging onboard
Configuring Message Severity Levels: Example
The following example shows how to save only the syslog message in which the severity level is set to 0
(emergency) to a storage device:
RP/0/RSP0/CPU0:router(admin-config)#
hw-module subslot 0/2/CPU0 logging onboard severity
emergencies
The following example shows how to save the syslog message in which the severity level is set to 0 (emergency)
and 1 (alert) to a storage device:
RP/0/RSP0/CPU0:router(admin-config)#
hw-module subslot 0/2/CPU0 logging onboard severity
alerts
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
318
Onboard Failure Logging
Configuration Examples for OBFL