5.6. Configuring Logging with CLI
This section provides information to configure logging using the command line interface.
Topics in this section include:
5.7. Log Configuration Overview
Logging on the 7705 SAR is used to provide the operator with logging information for monitoring and troubleshooting. You can configure logging parameters to save information in a log file or direct the messages to other devices. Logging commands allow you to:
- select the types of logging information to be recorded
- assign a severity to the log messages
- select the source and target of logging information
5.8. Log Type
Logs can be configured in the following contexts:
- Log file — log files can contain log event message streams or accounting/billing information. Log file IDs are used to direct events, alarms/traps, and debug information to their respective targets.
- SNMP trap groups — SNMP trap groups contain an IP address and community names that identify targets to send traps following specified events
- Syslog — information can be sent to a syslog host that is capable of receiving selected syslog messages from a network element
- Event control — configures a particular event, or all events associated with an application, to be generated or suppressed
- Event filters — an event filter defines whether to forward or drop an event or trap based on match criteria
- Accounting policies — an accounting policy defines the accounting records that will be created. Accounting policies can be applied to one or more service access points (SAPs) and to network ports.
- Event logs — an event log defines the types of events to be delivered to an associated destination
- Event throttling rate — defines the rate of throttling events
5.9. Basic Event Log Configuration
The most basic log configuration must have the following:
- a log ID or an accounting policy ID
- a log source
- a log destination
The following displays a log configuration example.
5.10. Common Configuration Tasks
The following sections describe basic system tasks that must be performed.
5.10.1. Configuring an Event Log
An event log file is identified by a log-id and contains information used to direct messages generated by system applications (such as events, alarms, traps, and debug information) to their respective destinations. One or more event sources can be specified using the from command. Event destinations (such as file IDs, SNMP trap groups, or syslog IDs) must be configured using the to command before they can be applied to an event log ID. Only one destination can be specified.
Use the file-id log-file-id command to specify the destination compact flash. See Configuring a File ID.
Use the following CLI syntax to configure a log file:
The following displays an example of the event log file configuration command syntax:
The following displays a log file configuration:
5.10.2. Configuring a File ID
To create a log file, a file ID is defined that specifies the target compact flash drive and the rollover and retention interval period for the file. The rollover interval is defined in minutes and determines how long a file will be used before it is closed and a new log file is created. The retention interval determines how long the file will be stored on the compact flash drive before it is deleted.
The minimum amount of free space for log files on a compact flash drive is the lesser of 10% of the compact flash disk capacity or 5 Mb (5 242 880).
Use the following CLI syntax to configure a log file ID:
The following displays an example of the log file ID configuration command syntax:
The following displays the file ID configuration:
5.10.3. Configuring an Accounting Policy
Before an accounting policy can be created, a target log file must be created to collect the accounting records. The files are stored in system memory on the compact flash drive in a compressed (tar) XML format and can be retrieved using FTP or SCP. See Configuring an Event Log and Configuring a File ID.
Accounting policies must be configured in the config>log context before they can be applied to a SAP or service interface, or applied to a network port. For information on associating an accounting policy with a SAP or a network port, see the 7705 SAR Services Guide or the 7705 SAR Interface Configuration Guide (respectively).
An accounting policy must define a record type and collection interval. Only one record type can be configured per accounting policy.
When creating accounting policies, one service accounting policy and one network accounting policy can be defined as default. If statistics collection is enabled on a SAP or network port and no accounting policy is applied, the respective default policy is used. If no default policy is defined, no statistics are collected unless a specifically defined accounting policy is applied.
Use the following CLI syntax to configure an accounting policy:
The following displays an example of the accounting policy configuration command syntax:
The following displays the accounting policy configuration:
5.10.4. Configuring Event Control and Throttle Rate
Use the following CLI syntax to configure event control. The throttle parameter used in the event-control command syntax enables throttling for a specific event type. The config>log>throttle-rate command configures the number of events and interval length to be applied to all event types that have throttling enabled by this event-control command. The throttling rate can also be configured independently for each log event by using the specific-throttle-rate parameter; this rate overrides the globally configured throttle rate for the specified log event.
The following displays an example of throttle rate configuration for all events that have throttling enabled:
The following displays the throttle rate configuration:
The following displays an example of throttle rate configuration for a specific event. The specific-throttle-rate configured for application aps, event 2003, overrides the globally configured throttle-rate.
The following displays the specific throttle rate configuration:
5.10.5. Configuring a Log Filter
Use the following CLI syntax to configure a log filter:
The following displays an example of the log filter configuration command syntax:
The following displays the log filter configuration:
5.10.6. Configuring an SNMP Trap Group
The associated log-id does not have to be configured before a snmp-trap-group can be created; however, the snmp-trap-group must exist before the log-id can be configured to use it.
Use the following CLI syntax to configure an SNMP trap group:
The following displays an example of the SNMP trap group configuration command syntax:
The following displays the SNMP trap group configuration:
5.10.7. Configuring a Syslog Target
Log events cannot be sent to a syslog target host until a valid syslog ID exists.
Use the following CLI syntax to configure a syslog file:
The following displays an example of the syslog file configuration command syntax:
The following displays the syslog configuration:
5.11. Log Management Tasks
This section discusses the following logging tasks:
5.11.1. Modifying a Log File
If the log destination needs to be changed or if the size of an SNMP log or memory log needs to be modified, the log ID must be removed and then recreated.
Use the following CLI syntax to modify a log file:
The following displays the current log configuration:
The following displays an example of modifying log file parameters:
The following displays the modified log file configuration:
5.11.2. Deleting a Log File
The log ID must be shut down first before it can be deleted. In a previous example, file 1 is associated with log-id 2.
Use the following CLI syntax to delete a log file:
The following displays an example of deleting a log file:
5.11.3. Modifying a File ID
 | Note: When the file-id location parameter is modified, log files are not written to the new location until a rollover occurs or the log is manually cleared. A rollover can be forced by using the clear>log command. Subsequent log entries are then written to the new location. If a rollover does not occur or the log is not cleared, the old location remains in effect. |
Use the following CLI syntax to modify a file ID:
The following displays the current file ID configuration:
The following displays an example of modifying file ID parameters:
The following displays the file ID modifications:
5.11.4. Deleting a File ID
| Note: All references to the file ID must be deleted before the file ID can be removed. |
Use the following CLI syntax to delete a file ID:
The following displays an example of deleting a file ID:
5.11.5. Modifying a Syslog ID
Use the following CLI syntax to modify syslog ID parameters:
The following displays an example of the syslog ID modifications:
The following displays the syslog configuration:
5.11.6. Deleting a Syslog ID
| Note: All references to the syslog ID must be deleted before the syslog ID can be removed. Use the show>log>log-id command to view syslog references. |
Use the following CLI syntax to delete a syslog ID:
The following displays an example of deleting a syslog ID:
5.11.7. Modifying an SNMP Trap Group
Use the following CLI syntax to modify an SNMP trap group:
The following displays the current SNMP trap group configuration:
The following displays an example of the command usage to modify an SNMP trap group:
The following displays the SNMP trap group configuration:
5.11.8. Deleting an SNMP Trap Group
Use the following CLI syntax to delete a trap target and SNMP trap group:
The following displays the SNMP trap group configuration:
The following displays an example of deleting a trap target and an SNMP trap group.
5.11.9. Modifying a Log Filter
Use the following CLI syntax to modify a log filter:
The following output displays the current log filter configuration:
The following displays an example of the log filter modifications:
The following displays the log filter configuration:
5.11.10. Deleting a Log Filter
Use the following CLI syntax to delete a log filter:
The following displays an example of the command to delete a log filter:
5.11.11. Modifying Event Control Parameters
Use the following CLI syntax to modify event control parameters:
The following displays the current event control configuration:
The following displays an example of event control modifications:
The following displays the log filter configuration:
5.11.12. Returning to the Default Event Control Configuration
The no form of the event-control command returns modified values back to the default values.
Use the following CLI syntax to return to the default event control configuration:
The following displays an example of the command usage to return to the default values: