event-control application-id [event-name | event-number] [generate] [severity-level] [throttle]
event-control application-id [event-name | event-number] suppress
no event-control application [event-name | event-number]
config>log
Supported on all 7210 SAS platforms as described in this document, including those configured in the access-uplink operating mode.
This command specifies that a particular event or all events associated with an application are either generated or suppressed.
Events are generated by an application and contain an event number and description of the cause of the event. Each event has a default designation that 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 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. However, the generation of too many events may cause excessive overhead.
The rate of event generation can be throttled using the throttle parameter.
The no form of this command reverts the parameters to the default setting for events for the application or a specific event within the application. The severity-level, 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.
Specifies the application whose events are affected by this event control filter.
Specifies the event number or short name, which can generate, suppress, or revert to default for a single event. If no event number or name is specified, the command applies to all events in the application. To display a list of all event short names, use the event-control command.
Specifies that logger event is created when this event occurs. The generate keyword can be used with two optional parameters, severity-level and throttle.
Specifies an ASCII string representing the severity level to associate with the specified generated events.
Specifies whether or not events of this type will be throttled. By default, event throttling is on for most event types.
Keyword to indicate that the specified events will not be logged. If the suppress keyword is not specified, the events are generated by default.
route-preference primary {inband | outband} secondary {inband | outband | none}
no route-preference
config>log
Supported on all 7210 SAS platforms as described in this document, including those configured in the access-uplink operating mode.
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, the secondary routing preference will be attempted.
The no form of this command reverts to the default values.
no route-preference
Specifies the primary routing preference for traffic generated for SNMP notifications and syslog messages.
Specifies the secondary routing preference for traffic generated for SNMP notifications and syslog messages. The routing context specified by the secondary route preference will be attempted if the remote destination was not reachable by the primary routing preference, specified by primary route preference. The value specified for the secondary routing preference must be distinct from the value for primary route preference.
Specifies that the logging utility will attempt to use the base routing context to send SNMP notifications and syslog messages to remote destinations.
Specifies that the logging utility will attempt to use the management routing context to send SNMP notifications and syslog messages to remote destinations.
Specifies that no attempt will be made to send SNMP notifications and syslog messages to remote destinations.