OID reference

bosVacmAccessTable

1.3.6.1.4.1.1411.102.102.11.2.2

Description

The table of access rights for groups. Each entry is indexed by a groupName, a contextPrefix, a securityModel and a securityLevel. To determine whether access is allowed, one entry from this table needs to be selected and the proper viewName from that entry must be used for access control checking. To select the prope…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1411.102.102.11.2 (bosVacmObjects)
Node code
2
Node name
bosVacmAccessTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1411.102.102.11.2.2
URN notation
urn:oid:1.3.6.1.4.1.1411.102.102.11.2.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1411 102 102 11 2 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosVacmObjects(2) bosVacmAccessTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1411/102/102/11/2/2
  • /ISO/Identified-Organization/6/1/4/1/1411/102/102/11/2/2
  • /ISO/3/6/1/4/1/1411/102/102/11/2/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/enterprise/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/enterprises/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/enterprises/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/enterprise/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/enterprise/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/enterprises/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/enterprises/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/ldap-enterprise/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/ldap-enterprise/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/vendor-objects/funk/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • /iso/org/dod/internet/private/vendor-objects/juniper/ex2500/ex2500addon/snmpv3/bosVacmObjects/bosVacmAccessTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF BosVacmAccessEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

bosVacmAccessTable  OBJECT-TYPE
    SYNTAX       SEQUENCE OF BosVacmAccessEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION "The table of access rights for groups.

                 Each entry is indexed by a groupName, a contextPrefix,
                 a securityModel and a securityLevel.  To determine
                 whether access is allowed, one entry from this table
                 needs to be selected and the proper viewName from that
                 entry must be used for access control checking.

                 To select the proper entry, follow these steps:

                 1) the set of possible matches is formed by the
                    intersection of the following sets of entries:

                      the set of entries with identical vacmGroupName
                      the union of these two sets:
                       - the set with identical vacmAccessContextPrefix
                       - the set of entries with vacmAccessContextMatch
                         value of 'prefix' and matching
                         vacmAccessContextPrefix
                      intersected with the union of these two sets:
                       - the set of entries with identical
                         vacmSecurityModel
                       - the set of entries with vacmSecurityModel
                         value of 'any'
                      intersected with the set of entries with
                      vacmAccessSecurityLevel value less than or equal
                      to the requested securityLevel

                 2) if this set has only one member, we're done
                    otherwise, it comes down to deciding how to weight
                    the preferences between ContextPrefixes,
                    SecurityModels, and SecurityLevels as follows:
                    a) if the subset of entries with securityModel
                       matching the securityModel in the message is
                       not empty, then discard the rest.
                    b) if the subset of entries with
                       vacmAccessContextPrefix matching the contextName
                       in the message is not empty,
                       then discard the rest
                    c) discard all entries with ContextPrefixes shorter
                       than the longest one remaining in the set
                    d) select the entry with the highest securityLevel

                 Please note that for securityLevel noAuthNoPriv, all
                 groups are really equivalent since the assumption that
                 the securityName has been authenticated does not hold.
                "
    ::= { bosVacmObjects 2 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The table of access rights for groups. Each entry is indexed by a groupName, a contextPrefix, a securityModel and a securityLevel. To determine whether access is allowed, one entry from this table needs to be selected and the proper viewName from that entry must be used for access control checking. To select the proper entry, follow these steps: 1) the set of possible matches is formed by the intersection of the following sets of entries: the set of entries with identical vacmGroupName the union of these two sets: - the set with identical vacmAccessContextPrefix - the set of entries with vacmAccessContextMatch value of 'prefix' and matching vacmAccessContextPrefix intersected with the union of these two sets: - the set of entries with identical vacmSecurityModel - the set of entries with vacmSecurityModel value of 'any' intersected with the set of entries with vacmAccessSecurityLevel value less than or equal to the requested securityLevel 2) if this set has only one member, we're done otherwise, it comes down to deciding how to weight the preferences between ContextPrefixes, SecurityModels, and SecurityLevels as follows: a) if the subset of entries with securityModel matching the securityModel in the message is not empty, then discard the rest. b) if the subset of entries with vacmAccessContextPrefix matching the contextName in the message is not empty, then discard the rest c) discard all entries with ContextPrefixes shorter than the longest one remaining in the set d) select the entry with the highest securityLevel Please note that for securityLevel noAuthNoPriv, all groups are really equivalent since the assumption that the securityName has been authenticated does not hold.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

bosVacmAccessTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: bosVacmAccessTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bosVacmAccessTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BosVacmAccessEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The table of access rights for groups. Each entry is indexed by a groupName, a contextPrefix, a securityModel and a securityLevel. To determine whether access is allowed, one entry from this table needs to be selected and the proper viewName from that entry must be used for access control checking. To select the proper entry, follow these steps: 1) the set of possible matches is formed by the intersection of the following sets of entries: the set of entries with identical vacmGroupName the union of these two sets: - the set with identical vacmAccessContextPrefix - the set of entries with vacmAccessContextMatch value of 'prefix' and matching vacmAccessContextPrefix intersected with the union of these two sets: - the set of entries with identical vacmSecurityModel - the set of entries with vacmSecurityModel value of 'any' intersected with the set of entries with vacmAccessSecurityLevel value less than or equal to the requested securityLevel 2) if this set has only one member, we're done otherwise, it comes down to deciding how to weight the preferences between ContextPrefixes, SecurityModels, and SecurityLevels as follows: a) if the subset of entries with securityModel matching the securityModel in the message is not empty, then discard the rest. b) if the subset of entries with vacmAccessContextPrefix matching the contextName in the message is not empty, then discard the rest c) discard all entries with ContextPrefixes shorter than the longest one remaining in the set d) select the entry with the highest securityLevel Please note that for securityLevel noAuthNoPriv, all groups are really equivalent since the assumption that the securityName has been authenticated does not hold. \"",
    "::=",
    "{",
    "bosVacmObjects",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BosVacmAccessEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The table of access rights for groups. Each entry is indexed by a groupName, a contextPrefix, a securityModel and a securityLevel. To determine whether access is allowed, one entry from this table needs to be selected and the proper viewName from that entry must be used for access control checking. To select the proper entry, follow these steps: 1) the set of possible matches is formed by the intersection of the following sets of entries: the set of entries with identical vacmGroupName the union of these two sets: - the set with identical vacmAccessContextPrefix - the set of entries with vacmAccessContextMatch value of 'prefix' and matching vacmAccessContextPrefix intersected with the union of these two sets: - the set of entries with identical vacmSecurityModel - the set of entries with vacmSecurityModel value of 'any' intersected with the set of entries with vacmAccessSecurityLevel value less than or equal to the requested securityLevel 2) if this set has only one member, we're done otherwise, it comes down to deciding how to weight the preferences between ContextPrefixes, SecurityModels, and SecurityLevels as follows: a) if the subset of entries with securityModel matching the securityModel in the message is not empty, then discard the rest. b) if the subset of entries with vacmAccessContextPrefix matching the contextName in the message is not empty, then discard the rest c) discard all entries with ContextPrefixes shorter than the longest one remaining in the set d) select the entry with the highest securityLevel Please note that for securityLevel noAuthNoPriv, all groups are really equivalent since the assumption that the securityName has been authenticated does not hold."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: EX2500-BASE-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'DisplayString', 'PhysAddress', 'MacAddress', 'RowStatus', 'TimeInterval', 'TimeStamp'], 'BRIDGE-MIB': ['BridgeId', 'dot1dTp', 'dot1dTpPort', 'dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32', 'Gauge32', 'Counter64', 'TimeTicks', 'IpAddress', 'mib-2'], 'RFC1213-MIB': ['sysName', 'sysLocation', 'sysContact', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['PortList'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpMessageProcessingModel', 'SnmpSecurityModel', 'SnmpSecurityLevel'], 'SNMP-USER-BASED-SM-MIB': ['usmNoAuthProtocol', 'usmNoPrivProtocol']}
    · Download EX2500-BASE-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1411)

Walsh Kevin

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1411.102.102.11.2.2.1 bosVacmAccessEntry77

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1411.102.102.11.2.1 bosVacmSecurityToGroupTable15
1.3.6.1.4.1.1411.102.102.11.2.3 bosVacmViewTreeFamilyTable16