All MIBs › RFC1353-MIB › viewMask
viewMask
Module: RFC1353-MIB
OID (symbolic): RFC1353-MIB::viewMask
OID (numeric): 1.3.6.1.2.1.21.3.1.1.4
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: The bit mask which, in combination with the corresponding instance of viewSubtree, defines a family of view subtrees. Each bit of this bit mask corresponds to a sub- identifier of viewSubtree, 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 is in this family of view 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 view subtrees if the following criteria are met:
for each sub-identifier of the value of viewSubtree, either:
the i-th bit of viewMask is 0, or
the i-th sub-identifier of X is equal to the i-th sub-identifier of the value of viewSubtree.
If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of viewSubtree, 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 view subtrees is the one view subtree uniquely identified by the corresponding instance of viewSubtree.
What is viewMask?
A bitmask (up to 16 bytes) that, paired with viewSubtree, marks which sub-identifiers must match exactly versus which are wildcarded -- a 0 bit in the mask makes the corresponding OID sub-identifier a wildcard, letting one row cover a whole family of subtrees instead of just one exact OID.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.21.3.1.1.4 snmpwalk -v2c -c public <target> RFC1353-MIB::viewMask
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.21.3.1.1.4.1 snmpget -v2c -c public <target> RFC1353-MIB::viewMask.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.21.3.1.1.4.1 s <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> viewMask.1
Start monitoring vendor-neutral, standards-based MIB, legacy SNMPv2p-capable network devices (obsolete security model) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1353-MIB::viewMask OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, legacy SNMPv2p-capable network devices (obsolete security model) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.21 | snmpSecrets | RFC1353-MIB |
| 1.3.6.1.2.1.21.3 | partyViews | RFC1353-MIB |
| 1.3.6.1.2.1.21.3.1 | viewTable | RFC1353-MIB |
| 1.3.6.1.2.1.21.3.1.1 | viewEntry | RFC1353-MIB |
| 1.3.6.1.2.1.21.3.1.1.4 | viewMask | RFC1353-MIB |