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.
The no form of this command administratively enables an entity.
When a log-id is shut down, no events are collected for the entity. This leads to the loss of event data.
event-control application-id [event-name | event-number] [generate
][ severity-level] [throttle] [specific-throttle-rate
events-limit interval
seconds | disable-specific-throttle
]
event-control application-id [event-name | event-number] suppress
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.
bgp, cflowd, chassis, debug, igmp, lldp, mirror, ospf, pim, port, snmp, system, user, vrtr
The no form of the command reverts to the default values.
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.
|
•
|
aa is the accounting policy-id
|
|
•
|
The timestamp is the actual timestamp when the file is created. The format for the timestamp is yyyymmdd- hhmmss where:
|
|
–
|
yyyy is the year (for example, 2006)
|
|
–
|
mm is the month number (for example, 12 for December)
|
|
–
|
dd is the day of the month (for example, 03 for the 3rd of the month)
|
|
–
|
hh is the hour of the day in 24 hour format (for example, 04 for 4 a.m.)
|
|
–
|
mm is the minutes (for example, 30 for 30 minutes past the hour)
|
|
–
|
ss is the number of seconds (for example, 14 for 14 seconds)
|
|
•
|
The time the file was opened.
|
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.
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.).
Use the no form of this command to revert to default settings.
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.
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.
The no form of the command removes the filter association from log IDs which causes those logs to forward all events.
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).
config>log>filter filter-id>entry
entry-id
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.
The no form of the command removes the specified
action statement.
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.
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.
config>log>filter filter-id>entry
entry-id
Use the application command to display a list of the valid applications.
The no form of the command removes the match criteria for the
entry-id.
config>log>filter filter-id>entry
entry-id>match
The no form of the command removes the application as a match criterion.
no application — No application match criterion is specified.
|
Values
|
application_assurance, aps, atm, bgp, cflowd, chassis, debug, dhcp, dhcps, diameter, dynsvc, efm_oam, elmi, ering, eth_cfm, etun, fiter, gsmp, igh, igmp, igmp_snooping, ip, ipsec, isis, l2tp, lag, ldp, li, lldp, logger, mcpath, mc_redundancy, mirror, mld, mld_snooping, mpls, mpls_tp, msdp, nat, ntp, oam, open_flow, ospf, pim, pim_snooping, port, ppp, pppoe, ptp, radius, rip, rip_ng, route_policy, rsvp, security, snmp, stp, svcmgr, system, user, video, vrrp, vrtr, wlan_gw, wpp
|
message {eq | neq
} pattern pattern [regexp
]
The no form of the command removes messages as a match criterion.
Specifies the type of string comparison to use to determine if the log event matches the value of message command parameters. When the
regexp keyword is not specified, the default matching algorithm used is a basic substring match.
number {eq | neq | lt | lte | gt | gte
} event-id
config>log>filter filter-id>entry
entry-id>match
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.
router {eq
| neq
} router-instance [regexp
]
severity {eq | neq | lt | lte | gt | gte
} severity-level
The no form of the command removes the severity match criterion.
no severity — No severity level match criterion is specified.
config>log>filter filter-id>entry
entry-id>match
The no form of the command removes the subject match criterion.
no subject — No subject match criterion specified.
[no
] handler
event-handler-name
The no form of the command removes the specified EHS handler.
The no form of the command removes the specified EHS handler action-list entry.
[no
] event
application-id event-name-id
The no form of the command removes the specified trigger event.
[no
] trigger-entry
entry-id
The no form of the command removes the specified trigger entry.
A valid syslog-id must have the target syslog host address configured.
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.
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 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.
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.
|
Values
|
kernel, user, mail, systemd, auth, syslogd, printer, netnews, uucp, cron, authpriv, ftp, ntp, logaudit, logalert, cron2, local0, local1, local2, local3, local4, local5, local6, local7
|
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.
The no form of the command removes the log prefix string.
The no form of the command reverts to the default value.
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
] snmp-trap-group
log-id
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.
The log ID value of a log configured in the log-id context. Alarms and traps cannot be sent to the trap receivers until a valid
log-id exists.
trap-target name [address ip-address] [port port] [snmpv1
| snmpv2c
| snmpv3
] notify-community
communityName | snmpv3SecurityName [security-level
{no-auth-no-privacy
| auth-no-privacy
| privacy
}] [replay]
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.
Note that 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.
|
Values
|
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.
Specifies the community string for snmpv1 or
snmpv2c or the
snmpv3 security-name. If no
notify-community is configured, then no alarms nor traps will be issued for the trap destination. If the SNMP version is modified, the
notify-community must be changed to the proper form for the SNMP version.
The security-name as defined in the config>system>security>user context for SNMP v3. The
security-name can be an ASCII string up to 31 characters in length.
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.
The filter command is optional. If no event filter is configured, all events, alarms and traps generated by the source stream will be forwarded to the 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.
from {[main
] [security
] [change
] [debug-trace
]}
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.
The log-id context is used to direct events, alarms/traps, and debug information to respective destinations.
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.
The no form of the command deletes the log destination ID from the configuration.
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.
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.
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.
The size parameter indicates the number of events that can be stored in the memory.
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.
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.
The size parameter defines the number of events stored in this memory 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.
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.
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.
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.
When the no version of this command is selected, optional router information is not include at the top of the file.
NOTE: aa, video and subscriber records are not applicable to the 7950 XRS.
A:ALA-49# show log accounting-records
==========================================================
Accounting Policy Records
==========================================================
Record # Record Name Def. 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 kci-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
56 aa-partition 15
57 complete-pm 5
0 unknown-record-name 0
59 kpi-bearer-traffic-gtp-endpoint 5
60 kpi-ip-reas 5
61 kpi-radius-group 5
62 kpi-ref-pt-failure-cause-code 5
63 kpi-dhcp-group 5
complete-pm 5
===========================================================
A:ALA-49#
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.
The no form of the command removes the record type from the policy.
The file-id option specifies the destination for the accounting records selected for this destination. The characteristics of the file-id must have already been defined in the config>log>file context. A file-id can only be used once.
If the to command is executed while the accounting policy is in operation, then it becomes active during the next collection interval.
The no form of the command returns the value to the default.
The no form of the command reverts the configured values to the defaults.
The no form of the command
The no form of the command
The no form of the command excludes the long duration flow count in the AA subscriber's custom record.
[no
] medium-duration-flow-count
The no form of the command excludes the medium duration flow count.
[no
] short-duration-flow-count
The no form of the command excludes the short duration flow count.
The no form of the command excludes the total flow duration flow count.
[no
] total-flows-completed-count
The no form of the command excludes the total flow duration flow count.
[no
] from-aa-sub-counters
The no form of the command excludes the “from subscriber” count.
The no form of the command excludes the active flow count in the AA subscriber's custom record.
[no
] flows-admitted-count
The no form of the command excludes the flow’s admitted count in the AA subscriber's custom record.
The no form of the command excludes the flow’s denied count.
[no
] max-throughput-octet-count
The no form of the command excludes the maximum throughput octet count.
[no
] max-throughput-packet-count
The no form of the command excludes the maximum throughput packet count.
[no
] max-throughput-timestamp
The no form of the command excludes the timestamp.
[no
] octets-admitted-count
The no form of the command excludes the admitted octet count.
The no form of the command excludes the denied octet count.
[no
] packets-admitted-count
The no form of the command excludes the admitted packet count.
[no
] packets-denied-count
The no form of the command excludes the denied packet count.
The no form of the command excludes the “to subscriber” count.
[no
] override-counter
override-counter-id
The no form of the command removes the ID from the configuration.
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
The no form of the command
[no
] in-profile-octets-discarded-count
The no form of the command excludes the in-profile octets discarded count.
[no
] in-profile-octets-forwarded-count
The no form of the command excludes the in-profile octets forwarded count.
[no
] in-profile-packets-discarded-count
The no form of the command excludes the in-profile packets discarded count.
[no
] in-profile-packets-forwarded-count
The no form of the command excludes the in-profile packets forwarded count.
[no
] out-profile-octets-discarded-count
The no form of the command excludes the out of profile packets discarded count.
[no
] out-profile-octets-forwarded-count
The no form of the command excludes the out of profile octets forwarded count.
[no
] out-profile-packets-discarded-count
The no form of the command excludes the out of profile packets discarded count.
[no
] out-profile-packets-forwarded-count
The no form of the command excludes the out of profile packets forwarded count.
[no
] all-octets-offered-count
The no form of the command excludes the octets offered in the count.
[no
] all-packets-offered-count
The no form of the command excludes the packets offered in the count.
[no
] high-octets-discarded-count
The no form of the command excludes the high octets discarded count.
[no
] high-octets-offered-count
The no form of the command excludes the high octets offered count.
[no
] high-packets-discarded-count
The no form of the command excludes the high packets discarded count.
[no
] high-packets-offered-count
The no form of the command excludes the high packets offered count.
[no
] in-profile-octets-forwarded-count
The no form of the command excludes the in profile octets forwarded count.
[no
] in-profile-packets-forwarded-count
The no form of the command excludes the in profile packets forwarded count.
[no
] low-octets-discarded-count
The no form of the command excludes the low octets discarded count.
[no
] low-packets-discarded-count
The no form of the command excludes the low packets discarded count.
[no
] low-octets-offered-count
The no form of the command excludes the low octets discarded count.
[no
] low-packets-offered-count
The no form of the command excludes the low packets discarded count.
[no
] out-profile-octets-forwarded-count
The no form of the command excludes the out of profile octets forwarded count.
[no
] out-profile-packets-forwarded-count
The no form of the command excludes the out of profile packets forwarded count.
[no
] uncoloured-packets-offered-count
The no form of the command excludes the uncoloured octets offered in the count.
[no
] uncoloured-packets-offered-count
The no form of the command excludes the uncoloured packets offered count.
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.
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
