SNMP-VIEW-BASED-ACM-MIB Table View

Table-centric layout grouping table, row, and column objects.

Tables
4
Rows
4
Columns
21
.1.3.6.1.6.3.16.1.1 · 1 row entry · 1 columns
Uses the rfc variant from /opt/observium/mibs/rfc.
Command help
Walk vacmContextTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SNMP-VIEW-BASED-ACM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SNMP-VIEW-BASED-ACM-MIB::vacmContextTable'
The table of locally available contexts.
          
This table provides information to SNMP Command
          
Generator applications so that they can properly
configure the vacmAccessTable to control access to
all contexts at the SNMP entity.
          
This table may change dynamically if the SNMP entity
allows that contexts are added/deleted dynamically
(for instance when its configuration changes).  Such
changes would happen only if the management
instrumentation at that SNMP entity recognizes more
(or fewer) contexts.
          
The presence of entries in this table and of entries
in the vacmAccessTable are independent.  That is, a
context identified by an entry in this table is not
necessarily referenced by any entries in the
vacmAccessTable; and the context(s) referenced by an
entry in the vacmAccessTable does not necessarily
currently exist and thus need not be identified by an
entry in this table.
          
This table must be made accessible via the default
context so that Command Responder applications have
a standard way of retrieving the information.
          
This table is read-only.  It cannot be configured via
SNMP.
vacmContextEntry row .1.3.6.1.6.3.16.1.1.1
Information about a particular context.
Indexes
Column Syntax OID
A human readable name identifying a particular
context at a particular SNMP entity.

The empty contextName (zero length) represents the
default context.
OctetString
Constraints:
range: 0-32
.1.3.6.1.6.3.16.1.1.1.1
.1.3.6.1.6.3.16.1.2 · 1 row entry · 5 columns
Uses the rfc variant from /opt/observium/mibs/rfc.
Command help
Walk vacmSecurityToGroupTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SNMP-VIEW-BASED-ACM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SNMP-VIEW-BASED-ACM-MIB::vacmSecurityToGroupTable'
This table maps a combination of securityModel and
securityName into a groupName which is used to define
an access control policy for a group of principals.
vacmSecurityToGroupEntry row .1.3.6.1.6.3.16.1.2.1
An entry in this table maps the combination of a
securityModel and securityName into a groupName.
Column Syntax OID
The Security Model, by which the vacmSecurityName
referenced by this entry is provided.

Note, this object may not take the 'any' (0) value.
Integer32
Constraints:
range: 1-2147483647
.1.3.6.1.6.3.16.1.2.1.1
The securityName for the principal, represented in a
Security Model independent format, which is mapped by
this entry to a groupName.
OctetString
Constraints:
range: 1-32
.1.3.6.1.6.3.16.1.2.1.2
The name of the group to which this entry (e.g., the
combination of securityModel and securityName)
belongs.

This groupName is used as index into the
vacmAccessTable to select an access control policy.
Ho…
OctetStringr/w
Constraints:
range: 1-32
.1.3.6.1.6.3.16.1.2.1.3
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.
SNMPv2-TCStorageTyper/w
Type Values:
1other
2volatile
3nonVolatile
4permanent
5readOnly
Description:
Describes the memory realization of a conceptual row. A
row which is volatile(2) is lost upon reboot. A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage. A row which is …
.1.3.6.1.6.3.16.1.2.1.4
The status of this conceptual row.

Until instances of all corresponding columns are
appropriately configured, the value of the

corresponding instance of the vacmSecurityToGroupStatus
column…
SNMPv2-TCRowStatusr/w
Type Values:
1active
2notInService
3notReady
4createAndGo
5createAndWait
6destroy
Description:
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of …
.1.3.6.1.6.3.16.1.2.1.5
.1.3.6.1.6.3.16.1.4 · 1 row entry · 9 columns
Uses the rfc variant from /opt/observium/mibs/rfc.
Command help
Walk vacmAccessTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SNMP-VIEW-BASED-ACM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SNMP-VIEW-BASED-ACM-MIB::vacmAccessTable'
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.
vacmAccessEntry row .1.3.6.1.6.3.16.1.4.1
An access right configured in the Local Configuration
Datastore (LCD) authorizing access to an SNMP context.

Entries in this table can use an instance value for
object vacmGroupName even if no entry in tabl…
Column Syntax OID
In order to gain the access rights allowed by this
conceptual row, a contextName must match exactly
(if the value of vacmAccessContextMatch is 'exact')
or partially (if the value of vacmAccessContextMatch
is 'prefix') t…
OctetString
Constraints:
range: 0-32
.1.3.6.1.6.3.16.1.4.1.1
In order to gain the access rights allowed by this
conceptual row, this securityModel must be in use.
SNMP-FRAMEWORK-MIBSnmpSecurityModel
Type Constraints:
range: 0..2147483647
.1.3.6.1.6.3.16.1.4.1.2
The minimum level of security required in order to
gain the access rights allowed by this conceptual
row. A securityLevel of noAuthNoPriv is less than
authNoPriv which in turn is less than authPriv.

If m…
SNMP-FRAMEWORK-MIBSnmpSecurityLevel
Type Values:
1noAuthNoPriv
2authNoPriv
3authPriv
.1.3.6.1.6.3.16.1.4.1.3
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 context…
Enumerationr/w
Enumerated Values:
1exact
2prefix
.1.3.6.1.6.3.16.1.4.1.4
The value of an instance of this object identifies
the MIB view of the SNMP context to which this
conceptual row authorizes read access.

The identified MIB view is that one for which the
vacmViewTreeFamil…
OctetStringr/w
Constraints:
range: 0-32
.1.3.6.1.6.3.16.1.4.1.5
The value of an instance of this object identifies
the MIB view of the SNMP context to which this
conceptual row authorizes write access.

The identified MIB view is that one for which the
vacmViewTreeFami…
OctetStringr/w
Constraints:
range: 0-32
.1.3.6.1.6.3.16.1.4.1.6
The value of an instance of this object identifies
the MIB view of the SNMP context to which this
conceptual row authorizes access for notifications.

The identified MIB view is that one for which the
vacm…
OctetStringr/w
Constraints:
range: 0-32
.1.3.6.1.6.3.16.1.4.1.7
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.
SNMPv2-TCStorageTyper/w
Type Values:
1other
2volatile
3nonVolatile
4permanent
5readOnly
Description:
Describes the memory realization of a conceptual row. A
row which is volatile(2) is lost upon reboot. A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage. A row which is …
.1.3.6.1.6.3.16.1.4.1.8
The status of this conceptual row.

The RowStatus TC [RFC2579] requires that this
DESCRIPTION clause states under which circumstances
other objects in this row can be modified:

The value of…
SNMPv2-TCRowStatusr/w
Type Values:
1active
2notInService
3notReady
4createAndGo
5createAndWait
6destroy
Description:
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of …
.1.3.6.1.6.3.16.1.4.1.9
.1.3.6.1.6.3.16.1.5.2 · 1 row entry · 6 columns
Uses the rfc variant from /opt/observium/mibs/rfc.
Command help
Walk vacmViewTreeFamilyTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SNMP-VIEW-BASED-ACM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyTable'
Locally held information about families of subtrees
within MIB views.
          
Each MIB view is defined by two sets of view subtrees:
  - the included view subtrees, and
  - the excluded view subtrees.
Every such view subtree, both the included and the
          
excluded ones, is defined in this table.
          
To determine if a particular object instance is in
a particular MIB view, compare the object instance's
OBJECT IDENTIFIER with each of the MIB view's active
entries in this table.  If none match, then the
object instance is not in the MIB view.  If one or
more match, then the object instance is included in,
or excluded from, the MIB view according to the
value of vacmViewTreeFamilyType in the entry whose
value of vacmViewTreeFamilySubtree has the most
sub-identifiers.  If multiple entries match and have
the same number of sub-identifiers (when wildcarding
is specified with the value of vacmViewTreeFamilyMask),
then the lexicographically greatest instance of
vacmViewTreeFamilyType determines the inclusion or
exclusion.
          
An object instance's OBJECT IDENTIFIER X matches an
active entry in this table when the number of
sub-identifiers in X is at least as many as in the
value of vacmViewTreeFamilySubtree for the entry,
and each sub-identifier in the value of
vacmViewTreeFamilySubtree matches its corresponding
sub-identifier in X.  Two sub-identifiers match
either if the corresponding bit of the value of
vacmViewTreeFamilyMask for the entry is zero (the
'wild card' value), or if they are equal.
          
A 'family' of subtrees is the set of subtrees defined
by a particular combination of values of
vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask.
          
In the case where no 'wild card' is defined in the
vacmViewTreeFamilyMask, the family of subtrees reduces
to a single subtree.
          
When creating or changing MIB views, an SNMP Command
Generator application should utilize the
vacmViewSpinLock to try to avoid collisions.  See
DESCRIPTION clause of vacmViewSpinLock.
          
When creating MIB views, it is strongly advised that
first the 'excluded' vacmViewTreeFamilyEntries are
created and then the 'included' entries.
          
When deleting MIB views, it is strongly advised that
first the 'included' vacmViewTreeFamilyEntries are
          
deleted and then the 'excluded' entries.
          
If a create for an entry for instance-level access
control is received and the implementation does not
support instance-level granularity, then an
inconsistentName error must be returned.
vacmViewTreeFamilyEntry row .1.3.6.1.6.3.16.1.5.2.1
Information on a particular family of view subtrees
included in or excluded from a particular SNMP
context's MIB view.

Implementations must not restrict the number of
families of view subtrees for a given M…
Column Syntax OID
The human readable name for a family of view subtrees.
OctetString
Constraints:
range: 1-32
.1.3.6.1.6.3.16.1.5.2.1.1
The MIB subtree which when combined with the
corresponding instance of vacmViewTreeFamilyMask
defines a family of view subtrees.
ObjectIdentifier .1.3.6.1.6.3.16.1.5.2.1.2
The bit mask which, in combination with the
corresponding instance of vacmViewTreeFamilySubtree,
defines a family of view subtrees.

Each bit of this bit mask corresponds to a
sub-identifier of vacmViewTre…
OctetStringr/w
Constraints:
range: 0-16
.1.3.6.1.6.3.16.1.5.2.1.3
Indicates whether the corresponding instances of
vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask
define a family of view subtrees which is included in
or excluded from the MIB view.
Enumerationr/w
Enumerated Values:
1included
2excluded
.1.3.6.1.6.3.16.1.5.2.1.4
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.
SNMPv2-TCStorageTyper/w
Type Values:
1other
2volatile
3nonVolatile
4permanent
5readOnly
Description:
Describes the memory realization of a conceptual row. A
row which is volatile(2) is lost upon reboot. A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage. A row which is …
.1.3.6.1.6.3.16.1.5.2.1.5
The status of this conceptual row.

The RowStatus TC [RFC2579] requires that this
DESCRIPTION clause states under which circumstances
other objects in this row can be modified:

The value of…
SNMPv2-TCRowStatusr/w
Type Values:
1active
2notInService
3notReady
4createAndGo
5createAndWait
6destroy
Description:
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of …
.1.3.6.1.6.3.16.1.5.2.1.6