Global Configuration Mode Filtering - Cisco ASR 5000 Series Administration Manual

Configuring Event Log Filters
You can display the instance numbers for enabled instances per facility using the Exec mode show
instance-logging command.

Global Configuration Mode Filtering

You can filter the contents of event logs at the Exec mode and Global Configuration mode levels.
Follow the example below to configure run time event logging parameters for the system:
configure
logging filter runtime facility facility level report_level
logging display { event-verbosity | pdu-data | pdu-verbosity }
end
Notes:
• facility facility and level severity_level – Configure the logging filter that determines which system
facilities should be logged and at what levels. For detailed information, see
page 172
• Repeat for every facility that you would like to log.
• Optional: Configure event ID restrictions by adding the logging disable eventid command. The system
provides the ability to restrict the sending of a specific event ID or a range of event IDs to minimize the
amount of data logged to that which is most useful. Repeat to disable logging for additional event IDs
or event ID ranges.
• If an administrator restricts event logging for an Event ID or Event ID range using the above command
(logging disable eventid ), the system will generate a Critical Event log "cli 30999 critical" as well as
an SNMP trap "1361 (DisabledEventIDs)" with the specific Event IDs or Event ID range that was
disabled.
These event logs and traps are enabled by default in this release, and cannot be disabled.
• If an administrator lowers the logging level (using the logging filter runtime facility facility level
report_level command below the default level of "error", the system will generate a Critical Event log
"cli 30998 critical" as well as an SNMP trap "1362 (LogLevelChanged)" with the specific Event IDs or
Event ID range that was disabled.
These event logs and traps are enabled by default in this release, and cannot be disabled.
The following examples show the CLI output of the traps generated when event logging or logging levels are
changed.
[local]host# show snmp trap statistics
SNMP Notification Statistics:
...
Trap Name
----------------------------------- ----- -----
...
DisabledEventIDs
LogLevelChanged
[local]host# show snmp trap history
There are x historical trap records (5000 maximum)
Timestamp
------------------------
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
...
Thu May 11 15:28:03 2017 Internal trap notification 1362 (LogLevelChanged) Logging level
of facility resmgr is changed to critical by user #initial-config# context local privilege
level Security Administrator ttyname /dev/pts/0 address type IPV4 remote ip address 0.0.0.0
ASR 5500 System Administration Guide, StarOS Release 21.4
170
and Event Severities, on page
Trap Information
197.
#Gen #Disc Disable Last Generated
------- --------------------
1 0 0 2017:05:11:15:35:25
2 0 0 2017:05:11:15:28:03
System Logs
Specifying Facilities, on