If the value of this object is exact(1), then all
rows where the contextName exactly matches
vacmAccessContextPrefix are selected.
If the value of this object is prefix(2), then all
rows where the contextName whose starting octets
exactly match vacmAccessContextPrefix are selected.
This allows for a simple form of wildcarding.
Parsed from file SNMP-VIEW-BASED-ACM-MIB.mib
Module: SNMP-VIEW-BASED-ACM-MIB
If the value of this object is exact(1), then all
rows where the contextName exactly matches
vacmAccessContextPrefix are selected.
If the value of this object is prefix(2), then all
rows where the contextName whose starting octets
exactly match vacmAccessContextPrefix are selected.
This allows for a simple form of wildcarding.
vacmAccessContextMatch OBJECT-TYPE
SYNTAX INTEGER
{ exact (1), -- exact match of prefix and contextName
prefix (2) -- Only match to the prefix
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION "If the value of this object is exact(1), then all
rows where the contextName exactly matches
vacmAccessContextPrefix are selected.
If the value of this object is prefix(2), then all
rows where the contextName whose starting octets
exactly match vacmAccessContextPrefix are selected.
This allows for a simple form of wildcarding.
"
DEFVAL { exact }
View at oid-info.com
If the value of this object is exact(1), then all
rows where the contextName exactly matches
vacmAccessContextPrefix are selected.
If the value of this object is prefix(2), then all
rows where the contextName whose starting octets
exactly match vacmAccessContextPrefix are selected.
This allows for a simple form of wildcarding.
Parsed from file rfc3415.mib.txt
Company: None
Module: SNMP-VIEW-BASED-ACM-MIB
If the value of this object is exact(1), then all
rows where the contextName exactly matches
vacmAccessContextPrefix are selected.
If the value of this object is prefix(2), then all
rows where the contextName whose starting octets
exactly match vacmAccessContextPrefix are selected.
This allows for a simple form of wildcarding.
vacmAccessContextMatch OBJECT-TYPE SYNTAX INTEGER { exact (1), prefix (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of this object is exact(1), then all rows where the contextName exactly matches vacmAccessContextPrefix are selected. If the value of this object is prefix(2), then all rows where the contextName whose starting octets exactly match vacmAccessContextPrefix are selected. This allows for a simple form of wildcarding. " DEFVAL { exact } ::= { vacmAccessEntry 4 }
vacmAccessContextMatch OBJECT-TYPE SYNTAX INTEGER { exact(1), prefix(2) } ACCESS read-write STATUS mandatory DESCRIPTION "If the value of this object is exact(1), then all rows where the contextName exactly matches vacmAccessContextPrefix are selected. If the value of this object is prefix(2), then all rows where the contextName whose starting octets exactly match vacmAccessContextPrefix are selected. This allows for a simple form of wildcarding." DEFVAL { exact } ::= { vacmAccessEntry 4 }
Automatically extracted from RFC3415
vacmAccessContextMatch OBJECT-TYPE SYNTAX INTEGER { exact (1), prefix (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of this object is exact(1), then all rows where the contextName exactly matches vacmAccessContextPrefix are selected. If the value of this object is prefix(2), then all rows where the contextName whose starting octets exactly match vacmAccessContextPrefix are selected. This allows for a simple form of wildcarding. " DEFVAL { exact } ::= { vacmAccessEntry 4 }
vacmAccessContextMatch OBJECT-TYPE SYNTAX INTEGER { exact (1), prefix (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "If the value of this object is exact(1), then all rows where the contextName exactly matches vacmAccessContextPrefix are selected. If the value of this object is prefix(2), then all rows where the contextName whose starting octets exactly match vacmAccessContextPrefix are selected. This allows for a simple form of wildcarding. " DEFVAL { exact } ::= { vacmAccessEntry 4 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.6.3.16.1.4.1.1 | vacmAccessContextPrefix | 0 | 0 | In order to gain the access rights allowed by this conceptual row, a contextName must match exactly (if the value of vacmAccessCo… |
1.3.6.1.6.3.16.1.4.1.2 | vacmAccessSecurityModel | 0 | 0 | In order to gain the access rights allowed by this conceptual row, this securityModel must be in use. |
1.3.6.1.6.3.16.1.4.1.3 | vacmAccessSecurityLevel | 0 | 0 | The minimum level of security required in order to gain the access rights allowed by this conceptual row. A securityLevel of noA… |
1.3.6.1.6.3.16.1.4.1.5 | vacmAccessReadViewName | 0 | 0 | The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes read … |
1.3.6.1.6.3.16.1.4.1.6 | vacmAccessWriteViewName | 0 | 0 | The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes write… |
1.3.6.1.6.3.16.1.4.1.7 | vacmAccessNotifyViewName | 0 | 0 | The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes acces… |
1.3.6.1.6.3.16.1.4.1.8 | vacmAccessStorageType | 0 | 0 | The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columna… |
1.3.6.1.6.3.16.1.4.1.9 | vacmAccessStatus | 0 | 0 | The status of this conceptual row. The RowStatus TC [RFC2579] requires that this DESCRIPTION clause states under which circumsta… |