The table of filter profiles. Filter profiles are used to determine whether particular management targets should receive particular notifications.
When a notification is generated, it must be compared with the filters associated with each management target which is configured to receive notifications, in order to determine whether it may be sent to each such management target.
A more complete discussion of notification filtering can be found in section 6. of [SNMP-APPL].
The indexes of the table are snmpNotifyFilterProfileName, IMPLIED snmpNotifyFilterSubtree.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.6.3.13.1.3.1.1 |
snmpNotifyFilterSubtree |
OBJECT IDENTIFIER |
not-accessible |
The MIB subtree which, when combined with the corresponding instance of snmpNotifyFilterMask, defines a family of subtrees which are included in or excluded from the filter profile. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.6.3.13.1.3.1.2 |
snmpNotifyFilterMask |
OCTET STRING{(0,16)} |
read-create |
The bit mask which, in combination with the corresponding instance of snmpNotifyFilterSubtree, defines a family of subtrees which are included in or excluded from the filter profile.
Each bit of this bit mask corresponds to a sub-identifier of snmpNotifyFilterSubtree, with the most significant bit of the i-th octet of this octet string value (extended if necessary, see below) corresponding to the (8*i - 7)-th sub-identifier, and the least significant bit of the i-th octet of this octet string corresponding to the (8*i)-th sub-identifier, where i is in the range 1 through 16.
Each bit of this bit mask specifies whether or not the corresponding sub-identifiers must match when determining if an OBJECT IDENTIFIER matches this family of filter subtrees; a '1' indicates that an exact match must occur; a '0' indicates 'wild card', i.e., any sub-identifier value matches.
Thus, the OBJECT IDENTIFIER X of an object instance is contained in a family of filter subtrees if, for each sub-identifier of the value of snmpNotifyFilterSubtree, either:
the i-th bit of snmpNotifyFilterMask is 0, or
the i-th sub-identifier of X is equal to the i-th sub-identifier of the value of snmpNotifyFilterSubtree.
If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of snmpNotifyFilterSubtree, then the bit mask is extended with 1's to be the required length. Note that when the value of this object is the zero-length string, this extension rule results in a mask of all-1's being used (i.e., no 'wild card'), and the family of filter subtrees is the one subtree uniquely identified by the corresponding instance of snmpNotifyFilterSubtree. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.6.3.13.1.3.1.3 |
snmpNotifyFilterType |
INTEGER{included(1),excluded(2)} |
read-create |
This object indicates whether the family of filter subtrees defined by this entry are included in or excluded from a filter. A more detailed discussion of the use of this object can be found in section 6. of [SNMP-APPL]. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.6.3.13.1.3.1.4 |
snmpNotifyFilterStorageType |
INTEGER{other(1),volatile(2),nonVolatile(3),permanent(4),readOnly(5)} |
read-create |
The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.6.3.13.1.3.1.5 |
snmpNotifyFilterRowStatus |
INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)} |
read-create |
The status of this conceptual row.
To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). |
This object is implemented as defined in the corresponding MIB files. |