Reference record for OID 1.3.6.1.6.3.16.1.4.1.4


parent
1.3.6.1.6.3.16.1.4.1 (vacmAccessEntry)
node code
4
node name
vacmAccessContextMatch
dot oid
1.3.6.1.6.3.16.1.4.1.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpVacmMIB(16) vacmMIBObjects(1) vacmAccessTable(4) vacmAccessEntry(1) vacmAccessContextMatch(4)}
  • {iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpVacmMIB(16) vacmMIBObjects(1) vacmAccessTable(4) vacmAccessEntry(1) vacmAccessContextMatch(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpVacmMIB(16) vacmMIBObjects(1) vacmAccessTable(4) vacmAccessEntry(1) vacmAccessContextMatch(4)}
  • iri oid
  • /iso/identified-organization/dod/internet/snmpV2/snmpModules/snmpVacmMIB/vacmMIBObjects/vacmAccessTable/vacmAccessEntry/vacmAccessContextMatch
  • /iso/org/dod/internet/snmpV2/snmpModules/snmpVacmMIB/vacmMIBObjects/vacmAccessTable/vacmAccessEntry/vacmAccessContextMatch
  • /iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/snmpVacmMIB/vacmMIBObjects/vacmAccessTable/vacmAccessEntry/vacmAccessContextMatch
  • iri by oid_info
    /ISO/Identified-Organization/6/1/6/3/16/1/4/1/4

    Description by circitor

    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

    Description by cisco_v1

    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.

    Description by oid_info

    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

    Description by mibdepot

    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

    Description by cisco

    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.

    Information by circitor

    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 }

    Information by cisco_v1

    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 }

    Information by oid_info

    Automatically extracted from RFC3415

    Information by mibdepot

    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 }

    Information by cisco

    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 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6)

    US DoD

    Brothers (8)

    OIDNameSub childrenSub Nodes TotalDescription
    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…