This section provides the log configuration command reference.
Refer to the SR OS Services Guide for information about configuring log filters in a VPRN service.
Refer to the SR OS Services Guide for information about configuring logs in a VPRN service.
Refer to the SR OS Services Guide for information about configuring SNMP trap groups in a VPRN service.
Refer to the SR OS Services Guide for information about configuring syslogs in a VPRN service.
This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of the command removes the string from the configuration.
No text description is associated with this configuration. The string must be entered.
This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
The no form of this command administratively enables an entity.
no shutdown
Specific system applications in SR OS can take action based on a route to certain IP destinations being available. This CLI branch contains configuration related to these route availability notifications. A delay can be configured between the time that a route is determined as available in the CPM, and the time that the application is notified of the available route. For example, this delay may be used to increase the chances that other system modules (such as IOMs/XCMs/MDAs/XMAs) are fully programmed with the new route before the application takes action. Currently, the only application that acts upon these route available or route changed notifications with their configurable delays is the SNMP replay feature, which receives notifications of route availability to the SNMP trap receiver destination IP address.
The time delay that must pass before notifying specific CPM applications that a route is available after a cold reboot.
no cold-start-wait
The time delay that must pass before notifying specific CPM applications after the recovery or change of a route during normal operation.
no route-recovery-wait
This command is used to specify that a particular event or all events associated with an application is either generated or suppressed.
Events are generated by an application and contain an event number and description explaining the cause of the event. Each event has a default designation which directs it to be generated or suppressed.
Events are generated with a default severity level that can be modified by using the severity-level option.
Events that are suppressed by default are typically used for debugging purposes. Events are suppressed at the time the application requests the event’s generation. No event log entry is generated regardless of the destination. While this feature can save processor resources, there may be a negative effect on the ability to troubleshoot problems if the logging entries are squelched. In reverse, indiscriminate application may cause excessive overhead.
The rate of event generation can be throttled by using the throttle parameter.
The no form of the command reverts the parameters to the default setting for events for the application or a specific event within the application. The severity, generate, suppress, and throttle options will also be reset to the initial values.
Each event has a set of default settings. To display a list of all events and the current configuration use the event-control command.
This command allows the user to set the event damping algorithm to suppress QoS or filter change events.
Note: While this event damping is original behavior for some modules such as service manager, QoS, and filters, it can result in the NMS system database being out of sync because of missed change events. On the other hand, if the damping is disabled (no event-damping), it may take much longer to exec a large CLI configuration file after system bootup. |
This command specifies the primary and secondary routing preference for traffic generated for SNMP notifications and syslog messages. If the remote destination is not reachable through the routing context specified by primary route preference then the secondary routing preference will be attempted.
The no form of the command reverts to the default values.
no route-preference
This command configures the number of events and interval length to be applied to all event types that have throttling enabled by the event-control command and do not have a specific-throttle-rate configured.
This command creates the context to configure a file ID template to be used as a destination for an event log or billing file.
This command defines the file location and characteristics that are to be used as the destination for a log event message stream or accounting/billing information. The file defined in this context is subsequently specified in the to command under log-id or accounting-policy to direct specific logging or billing source streams to the file destination.
A file ID can only be assigned to either one log-id or one accounting-policy. It cannot be reused for multiple instances. A file ID and associated file definition must exist for each log and billing file that must be stored in the file system.
A file is created when the file ID defined in this command is selected as the destination type for a specific log or accounting record. Log files are collected in a “log” directory. Accounting files are collected in an “act” directory.
The file names for a log are created by the system as summarized in Table 66.
File Type | File Name |
Log File | logllff-timestamp |
Accounting File | actaaff-timestamp |
Where:
When initialized, each file will contain:
If the process of writing to a log file fails (for example, the compact flash card is full) and if a backup location is not specified or fails, the log file will not become operational even if the compact flash card is replaced. Enter either a clear log command or a shutdown/no shutdown command to reinitialize the file.
If the primary location fails (for example, the compact flash card fills up during the write process), a trap is sent and logging continues to the specified backup location. This can result in truncated files in different locations.
The no form of the command removes the file-id from the configuration. A file-id can only be removed from the configuration if the file is not the designated output for a log destination. The actual file remains on the file system.
No default file IDs are defined.
This command specifies the primary and optional backup location where the log or billing file will be created.
The location command is optional. If the location command not explicitly configured, log files will be created on cf1: and accounting files will be created on cf2: without overflow onto other devices. Generally, cf3: is reserved for system files (configurations, images, etc.).
When multiple location commands are entered in a single file ID context, the last command overwrites the previous command.
When the location of a file ID that is associated with an active log ID is changed, the log events are not immediately written to the new location. The new location does not take affect until the log is rolled over either because the rollover period has expired or a clear log log-id command is entered to manually rollover the log file.
When creating files, the primary location is used as long as there is available space. If no space is available, an attempt is made to delete unnecessary files that are past their retention date.
If sufficient space is not available an attempt is made to remove the oldest to newest closed log or accounting files. After each file is deleted, the system attempts to create the new file.
A medium severity trap is issued to indicate that a compact flash is either not available or that no space is available on the specified flash and that the backup location is being used.
A high priority alarm condition is raised if none of the configured compact flash devices for this file ID are present or if there is insufficient space available. If space does becomes available, then the alarm condition will be cleared.
Use the no form of this command to revert to default settings.
Log files are created on cf1: and accounting files are created on cf2:
This command configures how often an event or accounting log is rolled over or partitioned into a new file.
An event or accounting log is actually composed of multiple, individual files. The system creates a new file for the log based on the rollover time, expressed in minutes.
The retention option, expressed in hours, allows you to modify the default time to keep the file in the system. The retention time is based on the rollover time of the file.
When multiple rollover commands for a file-id are entered, the last command overwrites the previous command.
rollover 1440 retention 12
This command creates a context for an event filter. An event filter specifies whether to forward or drop an event or trap based on the match criteria.
Filters are configured in the filter filter-id context and then applied to a log in the log-id log-id context. Only events for the configured log source streams destined to the log ID where the filter is applied are filtered.
Any changes made to an existing filter, using any of the sub-commands, are immediately applied to the destinations where the filter is applied.
The no form of the command removes the filter association from log IDs which causes those logs to forward all events.
No event filters are defined.
The default action specifies the action that is applied to events when no action is specified in the event filter entries or when an event does not match the specified criteria.
When multiple default-action commands are entered, the last command overwrites the previous command.
The no form of the command reverts the default action to the default value (forward).
default-action forward — The events which are not explicitly dropped by an event filter match are forwarded.
This command specifies a drop or forward action associated with the filter entry. If neither drop nor forward is specified, the default-action will be used for traffic that conforms to the match criteria. This could be considered a No-Op filter entry used to explicitly exit a set of filter entries without modifying previous actions.
Multiple action statements entered will overwrite previous actions.
The no form of the command removes the specified action statement.
Action specified by the default-action command will apply.
This command is used to create or edit an event filter entry. Multiple entries may be created using unique entry-id numbers. The -TiMOS implementation exits the filter on the first match found and executes the action in accordance with the action command.
Comparisons are performed in an ascending entry ID order. When entries are created, they should be arranged sequentially from the most explicit entry to the least explicit. Matching ceases when a packet matches an entry. The entry action is performed on the packet, either drop or forward. To be considered a match, the packet must meet all the conditions defined in the entry.
An entry may not have any match criteria defined (in which case, everything matches) but must have at least the keyword action for it to be considered complete. Entries without the action keyword will be considered incomplete and are rendered inactive.
The no form of the command removes the specified entry from the event filter. Entries removed from the event filter are immediately removed from all log-id’s where the filter is applied.
No event filter entries are defined. An entry must be explicitly configured.
This command creates context to enter/edit match criteria for a filter entry. When the match criteria is satisfied, the action associated with the entry is executed.
If more than one match parameter (within one match statement) is specified, then all the criteria must be satisfied (AND functional) before the action associated with the match is executed.
Use the application command to display a list of the valid applications.
Match context can consist of multiple match parameters (application, event-number, severity, subject), but multiple match statements cannot be entered per entry.
The no form of the command removes the match criteria for the entry-id.
No match context is defined.
This command adds an OS application as an event filter match criterion.
An OS application is the software entity that reports the event. Applications include IP, MPLS, OSPF, CLI, SERVICES etc. Only one application can be specified. The latest application command overwrites the previous command.
The no form of the command removes the application as a match criterion.
no application — No application match criterion is specified.
Operator | Notes |
eq | equal to |
neq | not equal to |
This command adds system messages as a match criterion.
The no form of the command removes messages as a match criterion.
This command adds an SR OS application event number as a match criterion.
SR OS event numbers uniquely identify a specific logging event within an application.
Only one number command can be entered per event filter entry. The latest number command overwrites the previous command.
The no form of the command removes the event number as a match criterion.
no event-number — No event ID match criterion is specified.
Operator | Notes |
eq | equal to |
neq | not equal to |
lt | less than |
lte | less than or equal to |
gt | greater than |
gte | greater than or equal to |
This command specifies the log event matches for the router.
This command adds an event severity level as a match criterion. Only one severity command can be entered per event filter entry. The latest severity command overwrites the previous command.
The no form of the command removes the severity match criterion.
no severity — No severity level match criterion is specified.
Operator | Notes |
eq | equal to |
neq | not equal to |
lt | less than |
lte | less than or equal to |
gt | greater than |
gte | greater than or equal to |
Severity Number | Severity Name |
1 | cleared |
2 | indeterminate (info) |
3 | critical |
4 | major |
5 | minor |
6 | warning |
This command adds an event subject as a match criterion.
The subject is the entity for which the event is reported, such as a port. In this case the port-id string would be the subject. Only one subject command can be entered per event filter entry. The latest subject command overwrites the previous command.
The no form of the command removes the subject match criterion.
no subject — No subject match criterion specified.
Operator | Notes |
eq | equal to |
neg | not equal to |
This command enables the context to configure event handling within the Event Handler System (EHS).
This command configures an EHS handler.
The no form of the command removes the specified EHS handler.
This command enables the context to configure the EHS handler action list.
This command configures an EHS handler action-list entry. A handler can have multiple actions where each action, for example, could request the execution of a different script. When the handler is triggered it will walk through the list of configured actions.
The no form of the command removes the specified EHS handler action-list entry.
This command specifies the minimum delay in seconds between subsequent executions of the action specified in this entry. This is useful, for example, to ensure that a script doesn't get triggered to execute too often.
This command configures the script policy parameters to use for this EHS handler action-list entry. The associated script is launched when the handler is triggered.
This command enables the context to configure log events as triggers for Event Handling System (EHS) handlers.
This command configures a specific log event as a trigger for one or more EHS handlers. Further matching criteria can be applied to only trigger certain handlers with certain instances of the log event.
The no form of the command removes the specified trigger event.
This command configures an instance of a trigger for an EHS handler. A trigger entry binds a set of matching criteria for a log event to a particular handler. If the log event occurs in the system and matches the criteria configured in the associated log filter then the handler will be executed.
The no form of the command removes the specified trigger entry.
This command configures when to trigger, for example after one or more event occurrences. The number of occurrences of an event can be bounded by a time window or left open.
no debounce
This command configures the event handler to be used for this trigger entry.
This command configures the log filter to be used for this trigger entry. The log filter defines the matching criteria that must be met in order for the log event to trigger the handler execution. The log filter is applied to the log event and, if the filtering decision results in a ‘forward’ action, then the handler is triggered.
It is typically unnecessary to configure match criteria for ‘application’ or ‘number’ in the log filter used for EHS since the particular filter is only applied for a specific log event application and number, as configured under config>log>event-trigger
This command creates the context to configure a syslog target host that is capable of receiving selected syslog messages from this network element.
A valid syslog-id must have the target syslog host address configured.
A maximum of 10 syslog-id’s can be configured.
No log events are sent to a syslog target address until the syslog-id has been configured as the log destination (to) in the log-id node.
The syslog ID configured in the configure/service/vprn context has a local VPRN scope and only needs to be unique within the specific VPRN instance. The same ID can be reused under a different VPRN service or in the global log context under config>log.
No syslog IDs are defined.
This command adds the syslog target host IP address to/from a syslog ID.
This parameter is mandatory. If no address is configured, syslog data cannot be forwarded to the syslog target host.
Only one address can be associated with a syslog-id. If multiple addresses are entered, the last address entered overwrites the previous address.
The same syslog target host can be used by multiple log IDs.
The no form of the command removes the syslog target host IP address.
no address — There is no syslog target host IP address defined for the syslog ID.
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x[-interface] |
x:x:x:x:x:x:d.d.d.d[-interface] | |
x: [0..FFFF]H | |
d: [0..255]D | |
interface: 32 characters maximum, mandatory for link local | |
addressesipv6-address x:x:x:x:x:x:x:x[-interface] | |
x:x:x:x:x:x:d.d.d.d[-interface] | |
x: [0..FFFF]H | |
d: [0..255]D | |
interface: 32 characters maximum, mandatory for link localaddresses |
This command configures the facility code for messages sent to the syslog target host.
Multiple syslog IDs can be created with the same target host but each syslog ID can only have one facility code. If multiple facility codes are entered, the last facility-code entered overwrites the previous facility-code.
If multiple facilities need to be generated for a single syslog target host, then multiple log-id entries must be created, each with its own filter criteria to select the events to be sent to the syslog target host with a given facility code.
The no form of the command reverts to the default value.
local7 — syslog entries are sent with the local7 facility code.
Numerical Code | Facility Code |
0 | kernel |
1 | user |
2 | |
3 | systemd |
4 | auth |
5 | syslogd |
6 | printer |
7 | net-news |
8 | uucp |
9 | cron |
10 | auth-priv |
11 | ftp |
12 | ntp |
13 | log-audit |
14 | log-alert |
15 | cron2 |
16 | local0 |
17 | local1 |
18 | local2 |
19 | local3 |
20 | local4 |
21 | local5 |
22 | local6 |
23 | local7 |
This command adds the string prepended to every syslog message sent to the syslog host.
RFC3164, The BSD syslog Protocol, allows a alphanumeric string (tag) to be prepended to the content of every log message sent to the syslog host. This alphanumeric string can, for example, be used to identify the node that generates the log entry. The software appends a colon (:) and a space to the string and it is inserted in the syslog message after the date stamp and before the syslog message content.
Only one string can be entered. If multiple strings are entered, the last string overwrites the previous string. The alphanumeric string can contain lowercase (a-z), uppercase (A-Z) and numeric (0-9) characters.
The no form of the command removes the log prefix string.
no log-prefix — no prepend log prefix string defined.
This command configures the syslog message severity level threshold. All messages with severity level equal to or higher than the threshold are sent to the syslog target host.
Only a single threshold level can be specified. If multiple levels are entered, the last level entered will overwrite the previously entered commands.
The no form of the command reverts to the default value.
level info
Router severity level | Numerical Severity (highest to lowest) | Configured Severity | Definition |
0 | emergency | system is unusable | |
3 | 1 | alert | action must be taken immediately |
4 | 2 | critical | critical condition |
5 | 3 | error | error condition |
6 | 4 | warning | warning condition |
5 | notice | normal but significant condition | |
1 cleared 2 indeterminate | 6 | info | informational messages |
7 | debug | debug-level messages |
This command configures the UDP port that will be used to send syslog messages to the syslog target host.
The port configuration is needed if the syslog target host uses a port other than the standard UDP syslog port 514.
Only one port can be configured. If multiple port commands are entered, the last entered port overwrites the previously entered ports.
The no form of the command reverts to default value.
no port
This command creates the context to configure a group of SNMP trap receivers and their operational parameters for a given log-id.
A group specifies the types of SNMP traps and specifies the log ID which will receive the group of SNMP traps. A trap group must be configured in order for SNMP traps to be sent.
To suppress the generation of all alarms and traps see the event-control command. To suppress alarms and traps that are sent to this log-id, see the filter command. Once alarms and traps are generated they can be directed to one or more SNMP trap groups. Logger events that can be forwarded as SNMP traps are always defined on the main event source.
The no form of the command deletes the SNMP trap group.
There are no default SNMP trap groups.
This command adds/modifies a trap receiver and configures the operational parameters for the trap receiver. A trap reports significant events that occur on a network device such as errors or failures.
Before an SNMP trap can be issued to a trap receiver, the log-id, snmp-trap-group and at least one trap-target must be configured.
The trap-target command is used to add/remove a trap receiver from an snmp-trap-group. The operational parameters specified in the command include:
A single snmp-trap-group log-id can have multiple trap-receivers. Each trap receiver can have different operational parameters.
An address can be configured as a trap receiver more than once as long as a different port is used for each instance.
To prevent resource limitations, only configure a maximum of 10 trap receivers.
Note: If the same trap-target name port port parameter value is specified in more than one SNMP trap group, each trap destination should be configured with a different notify-community value. This allows a trap receiving an application, such as NMS, to reconcile a separate event sequence number stream for each router event log when multiple event logs are directed to the same IP address and port destination. |
The no form of the command removes the SNMP trap receiver from the SNMP trap group.
No SNMP trap targets are defined.
ipv4-address | a.b.c.d (host bits must be 0) |
ipv6-address | x:x:x:x:x:x:x:x[-interface] |
x:x:x:x:x:x:d.d.d.d[-interface] | |
x: [0..FFFF]H | |
d: [0..255]D | |
interface: 32 characters maximum, mandatory for link local addresses |
The keyword snmpv1 selects the SNMP version 1 format. When specifying snmpv1, the notify-community must be configured for the proper SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv1, then the notify-community parameter must be changed to reflect the community string rather than the security-name that is used by snmpv3.
The keyword snmpv2c selects the SNMP version 2c format. When specifying snmpv2c, the notify-community must be configured for the proper SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv2c, then the notify-community parameter must be changed to reflect the community string rather than the security-name that is used by snmpv3.
The keyword snmpv3 selects the SNMP version 3 format. When specifying snmpv3, the notify-community must be configured for the SNMP security-name. If the SNMP version is changed from snmpv1 or snmpv2c to snmpv3, then the notify-community parameter must be changed to reflect the security-name rather than the community string used by snmpv1 or snmpv2c.
Pre-existing conditions are checked before the snmpv3SecurityName is accepted. These are:
The user name must be configured.
The v3 access group must be configured.
The v3 notification view must be configured.
The keyword no-auth-no-privacy specifies no authentication and no privacy (encryption) are required.
The keyword auth-no-privacy specifies authentication is required but no privacy (encryption) is required. When this option is configured the security-name must be configured for authentication.
The keyword privacy specifies both authentication and privacy (encryption) is required. When this option is configured the security-name must be configured for authentication and privacy.
Note: Due to route table change convergence time, it is possible that one or more events may be lost at the beginning or end of a replay sequence. The cold-start-wait and route-recovery-wait timers under the config>log>app-route-notifications context can help reduce the probability of lost events. |
This command adds an event filter policy with the log destination.
The filter command is optional. If an event filter is not configured, all events, alarms and traps generated by the source stream will be forwarded to the destination.
An event filter policy defines (limits) the events that are forwarded to the destination configured in the log-id. The event filter policy can also be used to select the alarms and traps to be forwarded to a destination snmp-trap-group.
The application of filters for debug messages is limited to application and subject only.
Accounting records cannot be filtered using the filter command.
Only one filter-id can be configured per log destination.
The no form of the command removes the specified event filter from the log-id.
no filter — No event filter policy is specified for a log-id.
This command selects the source stream to be sent to a log destination.
One or more source streams must be specified. The source of the data stream must be identified using the from command before you can configure the destination using the to command. The from command can identify multiple source streams in a single statement (for example: from main change debug-trace).
Only one from command may be entered for a single log-id. If multiple from commands are configured, then the last command entered overwrites the previous from command.
The no form of the command removes all previously configured source streams.
No source stream is configured.
This command creates a context to configure destinations for event streams.
The log-id context is used to direct events, alarms/traps, and debug information to respective destinations.
A maximum of 10 logs can be configured.
Before an event can be associated with this log-id, the from command identifying the source of the event must be configured.
Only one destination can be specified for a log-id. The destination of an event stream can be an in-memory buffer, console, session, snmp-trap-group, syslog, or file.
Use the event-control command to suppress the generation of events, alarms, and traps for all log destinations.
An event filter policy can be applied in the log-id context to limit which events, alarms, and traps are sent to the specified log-id.
Log-IDs 99 and 100 are created by the agent. Log-ID 99 captures all log messages. Log-ID 100 captures log messages with a severity level of major and above.
Note: Log-ID 99 provides valuable information for the admin-tech file. Removing or changing the log configuration may hinder debugging capabilities. It is strongly recommended not to alter the configuration for Log-ID 99. |
The no form of the command deletes the log destination ID from the configuration.
no log-id
This command specifies a log ID destination. This parameter is mandatory when configuring a log destination. This command instructs the events selected for the log ID to be directed to the console. If the console is not connected, then all the entries are dropped.
The source of the data stream must be specified in the from command prior to configuring the destination with the to command.
The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then re-created.
No destination is specified.
This command specifies a log ID destination. This parameter is mandatory when configuring a log destination. This command instructs the events selected for the log ID to be directed to a specified file.
The source of the data stream must be specified in the from command prior to configuring the destination with the to command.
The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then re-created.
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 not cleared, the old location remains in effect.
No destination is specified.
This command specifies a log ID destination. This parameter is mandatory when configuring a log destination. This command instructs the events selected for the log ID to be directed to a memory log. A memory file is a circular buffer. Once the file is full, each new entry replaces the oldest entry in the log.
The source of the data stream must be specified in the from command prior to configuring the destination with the to command.
The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then re-created.
to memory
This command specifies a log ID destination. This parameter is mandatory when configuring a log destination. This command instructs the events selected for the log ID to be directed to the current console or telnet session. This command is only valid for the duration of the session. When the session is terminated the “to session” configuration is removed. A log ID with a session destination is saved in the configuration file but the “to session” part is not stored.
The source of the data stream must be specified in the from command prior to configuring the destination with the to command.
The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then re-created.
none
This is one of the commands used to specify the log ID destination. This parameter is mandatory when configuring a log destination. This command instructs the alarms and traps to be directed to the snmp-trap-group associated with log-id.
A local circular memory log is always maintained for SNMP notifications sent to the specified snmp-trap-group for the log-id.
The source of the data stream must be specified in the from command prior to configuring the destination with the to command.
The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then re-created.
none
This is one of the commands used to specify the log ID destination. This parameter is mandatory when configuring a log destination.
This command instructs the alarms and traps to be directed to a specified syslog. To remain consistent with the standards governing syslog, messages to syslog are truncated to 1k bytes.
The source of the data stream must be specified in the from command prior to configuring the destination with the to command.
The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then re-created.
none
This command specifies whether the time should be displayed in local or Coordinated Universal Time (UTC) format.
utc
This command creates an access or network accounting policy. An accounting policy defines the accounting records that are created.
Access accounting policies are policies that can be applied to one or more SAPs. Changes made to an existing policy, using any of the sub-commands, are applied immediately to all SAPs where this policy is applied.
If an accounting policy is not specified on a SAP, then accounting records are produced in accordance with the access policy designated as the default. If a default access policy is not specified, then no accounting records are collected other than the records for the accounting policies that are explicitly configured.
Only one policy can be regarded as the default access policy. If a policy is configured as the default policy, then a no default command must be used to allow the data that is currently being collected to be written before a new access default policy can be configured.
Network accounting policies are policies that can be applied to one or more network ports or SONET/SDH channels. Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all network ports or SONET/SDH channels where this policy is applied.
If no accounting policy is defined on a network port, accounting records will be produced in accordance with the default network policy as designated with the default command. If no network default policy is created, then no accounting records will be collected other than the records for the accounting policies explicitly configured. Default accounting policies cannot be explicitly applied. For example, for accounting-policy 10, if default is set, then that policy cannot be used:
Only one policy can be regarded as the default network policy. If a policy is configured as the default policy, then a no default command must be used to allow the data that is currently being collected to be written before a new network default policy can be configured.
The no form of the command deletes the policy from the configuration. The accounting policy cannot be removed unless it is removed from all the SAPs, network ports or channels where the policy is applied.
No default accounting policy is defined.
This command configures the accounting collection interval.
In the configuration of an accounting policy this designates the accounting policy as the one used for auto-bandwidth statistics collection.
no auto-bandwidth
This command configures the default accounting policy to be used with all SAPs that do not have an accounting policy.
If no access accounting policy is defined on a SAP, accounting records are produced in accordance with the default access policy. If no default access policy is created, then no accounting records will be collected other than the records for the accounting policies that are explicitly configured.
If no network accounting policy is defined on a network port, accounting records will be produced in accordance with the default network policy. If no network default policy is created, then no accounting records will be collected other than the records for the accounting policies explicitly configured.
Only one access accounting policy ID can be designated as the default access policy. Likewise, only one network accounting policy ID can be designated as the default network accounting policy.
The record name must be specified prior to assigning an accounting policy as default.
If a policy is configured as the default policy, then a no default command must be issued before a new default policy can be configured.
The no form of the command removes the default policy designation from the policy ID. The accounting policy will be removed from all SAPs or network ports that do not have this policy explicitly defined.
This command allows operator to optionally include router information at the top of each accounting file generated for a given accounting policy.
When the no form of this command is selected, the optional router information is not include at the top of the file.
no include-router-info
This command allows the operator to optionally include router information at the top of each accounting file generated for a given accounting policy.
When the no version of this command is selected, optional router information is not include at the top of the file.
no include-system-info
This command adds the accounting record type to the accounting policy to be forwarded to the configured accounting file. A record name can only be used in one accounting policy. To obtain a list of all record types that can be configured, use the show log accounting-records command.
Note: aa, video and subscriber records are not applicable to the 7950 XRS. |
To configure an accounting policy for access ports, select a service record (for example, service-ingress-octets). To change the record name to another service record then the record command with the new record name can be entered and it will replace the old record name.
When configuring an accounting policy for network ports, a network record should be selected. When changing the record name to another network record, the record command with the new record name can be entered and it will replace the old record name.
If the change required modifies the record from network to service or from service to network, then the old record name must be removed using the no form of this command.
Only one record may be configured in a single accounting policy. For example, if an accounting-policy is configured with a access-egress-octets record, in order to change it to service-ingress-octets, use the no record command under the accounting-policy to remove the old record and then enter the service-ingress-octets record.
Note: Collecting excessive statistics can adversely affect the CPU utilization and take up large amounts of storage space. |
The no form of the command removes the record type from the policy.
no record
Record Type | Accounting Record Name | Default Interval |
1 | service-ingress-octets | 5 |
2 | service-egress-octets | 5 |
3 | service-ingress-packets | 5 |
4 | service-egress-packets | 5 |
5 | network-ingress-octets | 15 |
6 | network-egress-octets | 15 |
7 | network-ingress-packets | 15 |
8 | network-egress-packets | 15 |
9 | compact-service-ingress-octets | 5 |
10 | combined-service-ingress | 5 |
11 | combined-network-ing-egr-octets | 15 |
12 | combined-service-ing-egr-octets | 5 |
13 | complete-service-ingress-egress | 5 |
14 | combined-sdp-ingress-egress | 5 |
15 | complete-sdp-ingress-egress | 5 |
16 | complete-subscriber-ingress-egress | 5 |
17 | aa-protocol | 15 |
18 | aa-application | 15 |
19 | aa-app-group | 15 |
20 | aa-subscriber-protocol | 15 |
21 | aa-subscriber-application | 15 |
23 | custom-record-subscriber | 5 |
24 | custom-record-service | 5 |
25 | custom-record-aa-sub | 15 |
26 | queue-group-octets | 15 |
27 | queue-group-packets | 15 |
28 | combined-queue-group | 15 |
29 | combined-mpls-lsp-ingress | 5 |
30 | combined-mpls-lsp-egress | 5 |
31 | combined-ldp-lsp-egress | 5 |
32 | saa | 5 |
33 | complete-pm | 5 |
34 | video | 10 |
35 | kpi-system | 5 |
36 | kpi-bearer-mgmt | 5 |
37 | kpi-bearer-traffic | 5 |
38 | kpi-ref-point | 5 |
39 | kpi-path-mgmt | 5 |
40 | kpi-iom-3 | 5 |
41 | kci-system | 5 |
42 | kci-bearer-mgmt | 5 |
43 | kci-path-mgmt | 5 |
44 | complete-kpi | 5 |
45 | complete-kci | 5 |
46 | kpi-bearer-group | 5 |
47 | kpi-ref-path-group | 5 |
48 | kpi-kci-bearer-mgmt | 5 |
49 | kpi-kci-path-mgmt | 5 |
50 | kpi-kci-system | 5 |
51 | complete-kpi-kci | 5 |
52 | aa-performance | 15 |
53 | complete-ethernet-port | 15 |
54 | extended-service-ingress-egress | 5 |
55 | complete-network-ing-egr | 15 |
This command specifies the destination for the accounting records selected for the accounting policy.
No destination is specified.
The file is generated when the file policy is referenced. This command identifies the type of accounting file to be created. The file definition defines its characteristics.
If the to command is executed while the accounting policy is in operation, then it becomes active during the next collection interval.
This command configures the accounting collection interval.
The no form of the command returns the value to the default.
60
This command enables the context to configure the layout and setting for a custom accounting record associated with this accounting policy.
The no form of the command reverts the configured values to the defaults.
This command enables the context to configure information for this custom record.
The no form of the command
This command enables the context to configure subscriber counter information. This command only applies to the 7750 SR.
The no form of the command
This command includes the long duration flow count. This command only applies to the 7750 SR.
The no form of the command excludes the long duration flow count in the AA subscriber's custom record.
no long-duration-flow-count
This command includes the medium duration flow count in the AA subscriber's custom record. This command only applies to the 7750 SR.
The no form of the command excludes the medium duration flow count.
no medium-duration-flow-count
This command includes the short duration flow count in the AA subscriber's custom record.This command only applies to the 7750 SR.
The no form of the command excludes the short duration flow count.
no short-duration-flow-count
This command includes the total flow duration flow count in the AA subscriber's custom record. This command only applies to the 7750 SR.
The no form of the command excludes the total flow duration flow count.
This command includes the total flows completed count in the AA subscriber's custom record. This command only applies to the 7750 SR.
The no form of the command excludes the total flow duration flow count.
This command enables the context to configure Application Assurance “from subscriber” counter parameters. This command only applies to the 7750 SR.
The no form of the command excludes the “from subscriber” count.
This command include all counters and only applies to the 7750 SR.
This command includes the active flow count and only applies to the 7750 SR.
The no form of the command excludes the active flow count in the AA subscriber's custom record.
no flows-active-count
This command includes the admitted flow count and only applies to the 7750 SR.
The no form of the command excludes the flow’s admitted count in the AA subscriber's custom record.
no flows-admitted-count
This command includes the flow’s denied count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of the command excludes the flow’s denied count.
no flows-denied-count
This command enables the collection of a Forwarding Class bitmap information added to the XML aa-sub and router level accounting records, and only applies to the 7750 SR.
no forwarding-class
This command includes the maximum throughput as measured in the octet count. This command only applies to the 7750 SR.
The no form of the command excludes the maximum throughput octet count.
This command includes the maximum throughput as measured in the packet count. This command only applies to the 7750 SR.
The no form of the command excludes the maximum throughput packet count.
This command includes the timestamp of the maximum throughput. This command only applies to the 7750 SR.
The no form of the command excludes the timestamp.
This command includes the admitted octet count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of the command excludes the admitted octet count.
no octets-admitted-count
This command includes the denied octet count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of the command excludes the denied octet count.
no octets-denied-count
This command includes the admitted packet count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of the command excludes the admitted packet count.
no packets-admitted-count
This command includes the denied packet count in the AA subscriber's custom record and only applies to the 7750 SR.
The no form of the command excludes the denied packet count.
no packets-denied-count
This command enables the context to configure Application Assurance “to subscriber” counter parameters and only applies to the 7750 SR.
The no form of the command excludes the “to subscriber” count.
This command enables the context to configure override counter (HSMDA) parameters. This command only applies to the 7750 SR.
The no form of the command removes the ID from the configuration.
This command specifies the queue-id for which counters will be collected in this custom record. The counters that will be collected are defined in egress and ingress counters.
The no form of the command reverts to the default value.
This command configures egress counter parameters for this custom record.
The no form of the command reverts to the default value.
This command configures ingress counter parameters for this custom record.
The no form of the command
This command includes the in-profile octets discarded count.
The no form of the command excludes the in-profile octets discarded count.
This command includes the in-profile octets forwarded count.
The no form of the command excludes the in-profile octets forwarded count.
This command includes the in-profile packets discarded count.
The no form of the command excludes the in-profile packets discarded count.
This command includes the in-profile packets forwarded count.
The no form of the command excludes the in-profile packets forwarded count.
This command includes the out of profile packets discarded count.
The no form of the command excludes the out of profile packets discarded count.
This command includes the out of profile octets forwarded count.
The no form of the command excludes the out of profile octets forwarded count.
This command includes the out of profile packets discarded count.
The no form of the command excludes the out of profile packets discarded count.
This command includes the out of profile packets forwarded count.
The no form of the command excludes the out of profile packets forwarded count.
This command includes all octets offered in the count.
The no form of the command excludes the octets offered in the count.
no all-octets-offered-count
This command includes all packets offered in the count.
The no form of the command excludes the packets offered in the count.
no all-packets-offered-count
This command includes the high octets discarded count.
The no form of the command excludes the high octets discarded count.
no high-octets-discarded-count
This command includes the high octets offered count.
The no form of the command excludes the high octets offered count.
This command includes the high packets discarded count.
The no form of the command excludes the high packets discarded count.
no high-packets-discarded-count
This command includes the high packets offered count.
The no form of the command excludes the high packets offered count.
no high-packets-offered -count
This command includes the in profile octets forwarded count.
The no form of the command excludes the in profile octets forwarded count.
no in-profile-octets-forwarded-count
This command includes the in profile packets forwarded count.
The no form of the command excludes the in profile packets forwarded count.
no in-profile-packets-forwarded-count
This command includes the low octets discarded count.
The no form of the command excludes the low octets discarded count.
no low-octets-discarded-count
This command includes the low packets discarded count.
The no form of the command excludes the low packets discarded count.
no low-packets-discarded-count
This command includes the low octets discarded count.
The no form of the command excludes the low octets discarded count.
This command includes the low packets discarded count.
The no form of the command excludes the low packets discarded count.
This command includes the out of profile octets forwarded count.
The no form of the command excludes the out of profile octets forwarded count.
no out-profile-octets-forwarded-count
This command includes the out of profile packets forwarded count.
The no form of the command excludes the out of profile packets forwarded count.
no out-profile-packets-forwarded-count
This command includes the uncoloured octets offered in the count.
The no form of the command excludes the uncoloured octets offered in the count.
This command includes the uncolored packets offered count.
The no form of the command excludes the uncoloured packets offered count.
This command enables the use of significant-change so only those aa-specific records which have changed in the last accounting interval are written.
The no form of the command disables the use of significant-change so all aa-specific records are written whether or not they have changed within the last accounting interval.
This command configures a reference override counter.
The no form of the command reverts to the default value.
no ref-override-counter
This command configures a reference queue.
The no form of the command reverts to the default value.
no ref-queue
This command configures the significant change required to generate the record.