Saving Log Files; Event Id Overview - Cisco ASR 5500 System Administration Manual

Saving Log Files

Important
Important
Saving Log Files
Log files can be saved to a file in a local or remote location specified by a URL. Use the following Exec mode
command to save log files:
save logs { url } [ active ] ] [ inactive ] [ callid call_id ] [event-verbosity evt_verboseness ] [ facility
facility ] [level severity_level ] [ pdu-data pdu_format ] [ pdu-verbosity pdu_verboseness ] [ since
from_date_time [ until to_date_time ] ] [ | { grep grep_options | more } ]
For detailed information on the save logs command, see the Exec Mode Commands chapter in the Command
Line Interface Reference.

Event ID Overview

Important
Identification numbers (IDs) are used to reference events as they occur when logging is enabled on the system.
As described previously, logs are collected on a per facility basis. Each facility possesses its own range of
event IDs as indicated in the following table.
Table 7: System Facilities and Event ID Ranges
Facility
a10
a11
a11mgr
aaa-client
aaamgr
aaaproxy
aal2
acl-log
acsctrl
ASR 5500 System Administration Guide, StarOS Release 21.5
148
Checkpointing logs should be done periodically to prevent the log files becoming full. Logs which have
50,000 events logged will discard the oldest events first as new events are logged.
An Inspector-level administrative user cannot execute this command.
The use of event IDs depends on the platform type and the licenses running on the platform.
Description
A10 Protocol Facility
A11 Protocol Facility
A11 Manager Facility
AAA Client Facility
AAA Manager Facility
AAA Proxy Facility
AAL2 Protocol Facility
IP Access Control List (ACL) Facility
Active Charging Service Controller (ACSCtrl) Facility
System Logs
Event ID Range
28000-28999
29000-29999
9000-9999
6000-6999
36000-36999
64000-64999
173200-173299
21000-21999
90000-90999