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.

The indexes of the table are vacmViewTreeFamilyViewName, vacmViewTreeFamilySubtree.

OID

Object

Syntax

Max Access

Description

Implemented Specifications

1.3.6.1.6.3.16.1.5.2.1.1

vacmViewTreeFamilyViewName

OCTET STRING{(1,32)}

not-accessible

The human readable name for a family of view subtrees.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.6.3.16.1.5.2.1.2

vacmViewTreeFamilySubtree

OBJECT IDENTIFIER

not-accessible

The MIB subtree which when combined with the

corresponding instance of vacmViewTreeFamilyMask

defines a family of view subtrees.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.6.3.16.1.5.2.1.3

vacmViewTreeFamilyMask

OCTET STRING{(0,16)}

read-create

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 vacmViewTreeFamilySubtree, 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, for

each sub-identifier of the value of

vacmViewTreeFamilySubtree, either:

the i-th bit of vacmViewTreeFamilyMask is 0, or

the i-th sub-identifier of X is equal to the i-th

sub-identifier of the value of

vacmViewTreeFamilySubtree.

If the value of this bit mask is M bits long and

there are more than M sub-identifiers in the

corresponding instance of vacmViewTreeFamilySubtree,

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 vacmViewTreeFamilySubtree.

Note that masks of length greater than zero length

do not need to be supported. In this case this

object is made read-only.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.6.3.16.1.5.2.1.4

vacmViewTreeFamilyType

INTEGER{included(1),excluded(2)}

read-create

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.6.3.16.1.5.2.1.5

vacmViewTreeFamilyStorageType

INTEGER{other(1),volatile(2),nonVolatile(3),permanent(4),readOnly(5)}

read-create

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.6.3.16.1.5.2.1.6

vacmViewTreeFamilyStatus

INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)}

read-create

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 this object has no effect on whether

other objects in this conceptual row can be modified.

This object is implemented as defined in the corresponding MIB files.

Creation Restriction

You can create entries in this table.

Modification Restriction

The entries in this table can be modified.

Deletion Restriction

The entries in this table can be deleted.

Access Restriction

The entries in this table can be read without restriction.
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic