eventsCriteria
MX-NLM-MIB ·
.0.1100.1.200.1.400
Object
column
r/w
OctetString
Expression Criteria
Expression that an event must match in order to apply the
specified action. An expression can contain several 'basic'
criteria, separated by commas. The syntax accepts a group of
inclusion criteria followed by a group of exclusion criteria.
The group of exclusion criteria begins with a hyphen (-).
A basic criteria has the following syntax:
(Service NumKey || All).(Notification Numkey || Severity level
|| All).
* Keyword All can be used to specify a criteria that applies
to all services or all notifications.
* Severity level is specified using a single letter: W for
Warnings, I for Information, C for Critical, D for Debug,
and E for Error.
* Several basic criteria can be specified on the same line,
separated by commas.
* Criteria can specify inclusion or exclusion. A group of
exclusion criteria can follow the group of inclusion
criteria. The group of exclusion criteria must begin with a
hyphen (-).
* Matching an inclusion criteria causes the action to be
executed unless an exclusion criteria is also matched.
* Exclusion criteria have precedence over inclusion criteria.
Instead of using an expression such as described above, the
single keyword 'All' can be used to accept any notification
from any service.
If the whole expression is empty, the criteria never matches
any notification and no action is executed.
Spaces can be present before or after a basic criteria.
However, spaces are not accepted within a basic criteria, i.e.
before or after the dot.
Examples
Basic criteria for the ISDN Service (service number key =
1850), Message 'Physical link state changed to up' (message
number key = 5): Basic criteria is 1850.5.
Expression 1850.All,1600.200,1600.W,-1850.500,1600.300.
* 1850.All,1600.200,1600.W are inclusion criteria and
* All notifications from service 1850, except notification
500, will match the expression.
* All notifications from service 1600 with Warning level,
except notification 300, will match the expression.
* Notification 200 from service 1600 will match the
expression, no matter the severity level.
Context
- MIB
- MX-NLM-MIB
- OID
.0.1100.1.200.1.400- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- eventsEntry
- Table
- eventsTable
- Siblings
- 6
Syntax
OctetString
Values & Constraints
Object Constraints
range: 0-512
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| eventsIndex Index
Unique identifier of the row in the table. | column | SNMPv2-SMIUnsigned32 | .0.1100.1.200.1.100 |
| eventsDelete Delete
Delete this row. | column | Enumeration | .0.1100.1.200.1.10000 |
| eventsActivation Activation
Current activation state for the routing rule defined in this
table entry.
* Enable: This action is enabled for this table entry.
* Di… | column | MX-TCMxEnableState | .0.1100.1.200.1.200 |
| eventsType Event Type
Type of system event for which the routing rule applies.
Currently, the only type of supported event is the system
notification. | column | Enumeration | .0.1100.1.200.1.300 |
| eventsAction Action
Action to apply to the system event if the criteria matches.
The possible actions are:
* SendViaSyslog: The event notificatio… | column | Enumeration | .0.1100.1.200.1.500 |
| eventsConfigStatus Configuration Status
Configuration status of the row.
It indicates whether the configuration of the row is valid.
* Valid: The curre… | column | Enumeration | .0.1100.1.200.1.600 |