V2ADMIN-MIB
AI MIB Summary
V2ADMIN-MIB provides the standardized object definitions for configuring SNMPv2 entities, specifically enabling the management of protocol parameters such as community strings, access control lists, and trap destinations. This module facilitates the remote administration of SNMP agent behavior and security policies across network devices supporting the SNMPv2 protocol suite.
The MIB module for configuring SNMPv2 entities.
Main OID:
v2AdminMIB.1.3.6.1.6.3.1134
93
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
93 total| Object Name |
|---|
v2AdminMIBThe MIB module for configuring SNMPv2 entities. MODULE-IDENTITY .1.3.6.1.6.3.1134 |
v2AdminSnmpScalars OBJECT IDENTIFIER .1.3.6.1.6.3.1134.1 |
snmpIDAn SNMPv2 entity's administratively-unique identifier.
The initial value for this object may be configured via an
operator console entry or via an algorithmic function
defined by the vendor or administrator. In the later case,
the following guidelines are recommended:
1) The first four octets should be set to the binary
equivalent of the device vendor's SNMP network management
private enterprise number as assigned by the Internet
Assigned Numbers Authority (IANA). For example, if
Acme Networks has been assigned { enterprises 696 },
the first four octets would be assigned '000002b8'H.
2) The remaining eight octets are the cookie whose
contents are determined via one or more enterprise-
specific methods. Such methods must be designed so as
to maximize the possibility that the value of this
object will be unique in the device's administrative
domain. For example, the cookie may be the IP address
of the device, or the MAC address of one of the
interfaces, with each address suitably padded with
random octets, or possibly a unique cookie determined
by the device's model# and serial#. If multiple methods
are defined, then it is recommended that the cookie be
further divided into one octet that indicates the method
being used and seven octets which are a function of
the method.ro SnmpID .1.3.6.1.6.3.1134.1.1 |
snmpMaxMessageSizeThe maximum length in octets of an SNMPv2 message which
this SNMPv2 entity can send or receive and process, determined
as the minimum of the maximum message size values supported
among all of the transports available to and supported by the
entity.ro Integer32 .1.3.6.1.6.3.1134.1.3 |
maxIdentityNameLengthThe maximum length in octets which a particular implementation
will allow for any object which specifies an identityName.
This object may be queried by a manager in order to determine
system-specific limits for use during creation of new entries
in the tables defined in this MIB module.ro Integer32 .1.3.6.1.6.3.1134.1.4 |
maxGroupNameLengthThe maximum length in octets which a particular implementation
will allow for any object which specifies a groupName.
This object may be queried by a manager in order to determine
system-specific limits for use during creation of new entries
in the tables defined in this MIB module.ro Integer32 .1.3.6.1.6.3.1134.1.5 |
maxV2ContextNameLengthThe maximum length in octets which a particular implementation
will allow for the v2ContextName object, the acContextName
object, the notifyContextName object, the proxyContextNameIn
object, and any other objects which specify a contextName.
This object may be queried by a manager in order to determine
system-specific limits for use during creation of new entries
in the tables defined in this MIB module.ro Integer32 .1.3.6.1.6.3.1134.1.6 |
maxViewTreeNameLengthThe maximum length in octets which a particular implementation
will allow for the viewTreeName object, and any other
object which specifies the name of a view. This object may
be queried by a manager in order to determine system-specific
limits for use during creation of new entries in the tables
defined in this MIB module.ro Integer32 .1.3.6.1.6.3.1134.1.7 |
maxTransportLabelLengthThe maximum length in octets which a particular implementation
will allow for objects whose syntax is TransportLabel.
This object may be queried by a manager in order to
determine system-specific limits for use during creation of
new entries in the tables defined in this MIB module.ro Integer32 .1.3.6.1.6.3.1134.1.8 |
v2AdminStats OBJECT IDENTIFIER .1.3.6.1.6.3.1134.2 |
v2AdminStatsUnknownSPIsA count of the number of packets that contained sPI values
which are unknown to or unimplemented by the agent.ro Counter32 .1.3.6.1.6.3.1134.2.1 |
v2AdminStatsUnknownContextsA count of the number of packets that contained a local
contextName value which is unknown to the agent.ro Counter32 .1.3.6.1.6.3.1134.2.2 |
v2AdminStatsUnavailableContextsA count of the number of packets that contained a local
contextName value which specified a context that is currently
not available.ro Counter32 .1.3.6.1.6.3.1134.2.3 |
v2AdminStatsCacheMissesA count of the number of Response or Report messages received
for which no corresponding entry in the cache of outstanding
proxy operations could be found.
Note that a cache miss is not necessarily a serious problem.
This can occur, for example, if packets get duplicated.ro Counter32 .1.3.6.1.6.3.1134.2.4 |
v2ContextTableThe context database portion of the Local Configuration
Datastore. SEQUENCE OF V2ContextEntry .1.3.6.1.6.3.1134.3 |
v2ContextEntryInformation about a particular context. V2ContextEntry .1.3.6.1.6.3.1134.3.1 |
v2ContextSnmpIDThe SNMPv2 entity's administratively-unique
identifier. It is worth noting that in a simple agent
implementation, the value of this object will always be
equal to the entity's local snmpID object. SnmpID .1.3.6.1.6.3.1134.3.1.1 |
v2ContextNameA textual name uniquely identifying a particular context
on a particular agent. AuthName .1.3.6.1.6.3.1134.3.1.2 |
v2ContextLocalEntityIf the value of the corresponding instance of the
v2ContextSnmpID is equal to the local value of snmpID, then
the value of an instance of this object uniquely identifies a
local entity (e.g., a logical device managed by the same agent)
whose management information is available within this context.
The empty string indicates that the context contains the
SNMPv2 entity's own local management information; otherwise,
a non-empty string indicates that the context contains
management information of some other local entity,
e.g., 'Repeater1'.
If the value of the corresponding instance of v2ContextSnmpID
is not equal to the local value of snmpID, then the value of
an instance of this object identifies an entity which is local
to the SNMPv2 entity which realizes this context.rw OCTET STRING .1.3.6.1.6.3.1134.3.1.3 |
v2ContextLocalTimeThis object identifies the temporal domain of the
management information within this context.rw Enumeration .1.3.6.1.6.3.1134.3.1.4 |
v2ContextMemoryTypeThe storage type for this conceptual row in the
v2ContextTable. Conceptual rows having the value 'permanent'
need not allow write-access to any columnar objects in the
row.rw MemoryType .1.3.6.1.6.3.1134.3.1.5 |
v2ContextStatusThe status of this conceptual row in the v2ContextTable.
A context is not qualified for activation until instances of
all corresponding columns have consistent values.
For those columnar objects which permit write-access, their
value in an existing conceptual row can be changed
irrespective of the value of v2ContextStatus for that row.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1134.3.1.6 |
v2AdminViewTree OBJECT IDENTIFIER .1.3.6.1.6.3.1134.4 |
viewTreeSpinLockAn advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of the Set operation in creating view trees.
The values of viewTreeSpinLock, acSpinLock, and notifySpinLock
[if the notifyTable is implemented] should be accessed in
harmony to provide interlocks on the creation of new views.
When creating a new view or altering an existing view, it is
important to understand the potential interactions with other
users of the view. The spinlocks for each table which allows
the creation of named views should be retrieved. The name of
the view to be created should be determined to be unique on
the managed system by consulting each table containing named
views. Finally, the named view may be created, including the
advisory spinlocks.
Since this is an advisory lock, entities acting in an agent
role do not enforce the use of viewTreeSpinLock.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.6.3.1134.4.1 |
viewTreeTableThe view tree database. This contains information about the
subtrees of MIB views known to this SNMPv2 entity. Note that
a MIB view which has no subtrees defined for it has no
entries in this table.
Each MIB view is defined by two collections of view subtrees:
the included view subtrees, and the excluded view subtrees.
Every such subtree, both included and excluded, 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 viewTreeType in the entry whose
value of viewTreeSubTree has the most sub-identifiers. If
multiple entries match and have the same number of
sub-identifiers, then the lexicographically greatest instance
of viewTreeType among those which match 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 viewTreeSubTree for
the entry, and each sub-identifier in the value of
viewTreeSubTree matches its corresponding sub-identifier in X.
Two sub-identifiers match either if the corresponding bit of
viewMask is zero (the 'wild card' value), or if they are equal.
Due to this 'wild card' capability, we introduce the term, a
'family' of view subtrees, to refer to the set of subtrees
defined by a particular combination of values of
viewTreeSubTree and viewTreeMask. In the case where no
'wild card' is defined in viewTreeMask, the family of view
subtrees reduces to a single view subtree. SEQUENCE OF ViewTreeEntry .1.3.6.1.6.3.1134.4.2 |
viewTreeEntryInformation on a particular family of view subtrees
included in or excluded from a particular MIB view.
Implementations must not restrict the number of families of
view subtrees for a given MIB view, except as dictated by
resource constraints on the overall number of entries in the
viewTable. ViewTreeEntry .1.3.6.1.6.3.1134.4.2.1 |
viewTreeNameThe textual name for a family of view subtrees. AuthName .1.3.6.1.6.3.1134.4.2.1.1 |
viewTreeSubTreeA MIB subtree. OBJECT IDENTIFIER .1.3.6.1.6.3.1134.4.2.1.2 |
viewTreeMaskThe bit mask which, in combination with the corresponding
instance of viewTreeSubTree, defines a family of view
subtrees.
Each bit of this bit mask corresponds to a sub-identifier of
viewTreeSubTree, 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 the following
criteria are met:
for each sub-identifier of the value of viewTreeSubTree,
either:
the i-th bit of viewMask is 0, or
the i-th sub-identifier of X is equal to the i-th
sub-identifier of the value of viewTreeSubTree.
If the value of this bit mask is M bits long and there are
more than M sub-identifiers in the corresponding instance of
viewTreeSubTree, 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 viewTreeSubTree.rw OCTET STRING .1.3.6.1.6.3.1134.4.2.1.3 |
viewTreeTypeThe status of a particular family of view subtrees within
the particular context's MIB view. The value 'included(1)'
indicates that the corresponding instances of viewTreeSubTree
and viewTreeMask define a family of view subtrees included in
the MIB view. The value 'excluded(2)' indicates that the
corresponding instances of viewTreeSubTree and viewTreeMask
define a family of view subtrees excluded from the MIB view.rw Enumeration .1.3.6.1.6.3.1134.4.2.1.4 |
viewTreeMemoryTypeThe storage type for this conceptual row in the viewTreeTable.
Conceptual rows having the value 'permanent' need not allow
write-access to any columnar objects in the row.rw MemoryType .1.3.6.1.6.3.1134.4.2.1.5 |
viewTreeStatusThe status of this conceptual row in the viewTreeTable.
For those columnar objects which permit write-access, their
value in an existing conceptual row can be changed
irrespective of the value of viewTreeStatus for that row.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1134.4.2.1.6 |
v2AdminAccessControl OBJECT IDENTIFIER .1.3.6.1.6.3.1134.5 |
acSpinLockAn advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of the Set operation in creating view trees.
The values of viewTreeSpinLock, acSpinLock, and notifySpinLock
[if the notifyTable is implemented] should be accessed in
harmony to provide interlocks on the creation of new views.
When creating a new view or altering an existing view, it is
important to understand the potential interactions with other
users of the view. The spinlocks for each table which allows
the creation of named views should be retrieved. The name of
the view to be created should be determined to be unique on
the managed system by consulting each table containing named
views. Finally, the named view may be created, including the
advisory spinlocks.
Since this is an advisory lock, entities acting in an agent
role do not enforce the use of acSpinLock.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.6.3.1134.5.1 |
acTableThe access control database. SEQUENCE OF AcEntry .1.3.6.1.6.3.1134.5.2 |
acEntryEach conceptual row in this table represents the access policy
for a group of identities within a particular sPI. An access
policy specifies the access privileges authorized and MIB views
accessible by a group of identities for communication concerning
information contained in a particular context. AcEntry .1.3.6.1.6.3.1134.5.2.1 |
acSPIThe security protocol under which this conceptual row
provides access privileges. The sPI which is used to
originate a management request must match this object
in order to be granted access to management information. SPI .1.3.6.1.6.3.1134.5.2.1.1 |
acGroupNameThe textual name of a group associated with a conceptual row
in the acTable. A group name is associated with zero, one, or
more identities which are afforded the access privileges
authorized by the corresponding value of acPrivs to the zero,
one, or more contexts named by the corresponding values of
acContextName and acContextNameMask via the views named by
acReadViewName and acWriteViewName, if any.
For example, if the corresponding value of sPI is usecNoAuth,
usecAuth, or usecPriv, then the value of an instance of this
object identifies the set of identities whose usecUserGroupName
value is equal to the value of the instance of this object. AuthName .1.3.6.1.6.3.1134.5.2.1.2 |
acContextNameThe value of this object combined with the corresponding
value of acContextNameMask identifies zero, one, or more
contexts associated with a particular set of access
privileges. AuthName .1.3.6.1.6.3.1134.5.2.1.3 |
acContextNameMaskThe bit mask, which, in combination with the corresponding
instance of acContextName, identifies zero, one, or more
contexts.
Each bit of this bit mask corresponds to an octet of
acContextName, 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 octet, and the
least significant bit of the i-th octet of this octet string
corresponding to the (8*i)-th octet, where i is in the range
1 through 4.
Each bit of this bit mask specifies whether or not the
corresponding octets must match when determining which
instances of v2ContextEntry are identified by the
corresponding value of acContextName. A '1' indicates that
the corresponding octets must match, and a '0' indicates that
any octet value matches.
Thus, an instance of v2ContextEntry is identified if, for each
bit in the corresponding value of acContextNameMask,
either:
the bit of acContextNameMask is 0, or
the length of acContextName and v2ContextName are both
at least i octets, and the i-th octet of
acContextName is equal to the i-th octet of
v2ContextName.
It is not permitted for multiple conceptual rows in the acTable
to identify the same v2ContextName in this manner, for a
particular acSPI and acGroupName pair. If a Set request
attempts to modify a conceptual row in the acTable in a way such
that the combination of acContextName and acContextNameMask as
described above would yield the same value as the combination of
acContextName and acContextNameMask of another conceptual row in
the same conceptual table, for which the corresponding values of
acSPI are equal and the corresponding values of acGroupName are
equal, then an inconsistentValueError should be returned, and
the Set operation should fail.
If the value of this bit mask is M bits long and there are
more than M octets in the corresponding instance of either
acContextName or v2ContextName, then the bit mask is
extended with 1's up to the maximum of the two lengths.rw OCTET STRING .1.3.6.1.6.3.1134.5.2.1.4 |
acPrivsThis object specifies the types of management operations
that are authorized by this conceptual row. A value of
readOnly(2) indicates that Get, GetNext, and GetBulk
operations are authorized. A value of readWrite(3)
indicates that Get, GetNext, GetBulk, and Set operations
are authorized.rw Enumeration .1.3.6.1.6.3.1134.5.2.1.5 |
acReadViewNameThe value of an instance of this object identifies the MIB
view to be be used to provide access control via read (i.e.,
Get, GetNext, and GetBulk) operations to the zero, one, or
many contexts identified by the combination of the
corresponding instances of acContextName and acContextNameMask,
for a given value of sPI equal to the value of the corresponding
instance of acSPI, if and only if the corresponding value of
acPrivs authorizes read operations, i.e., equals readOnly(2)
or readWrite(3).
The identified MIB view is that for which viewTreeName has
the same value as the instance of this object; if there are
no active view subtrees for that value, or if the value of
this object has zero-length, then the identified MIB view
is the empty set of view subtrees, and the identified set of
objects for which read operations is enabled by this conceptual
row is the empty set.rw AuthName .1.3.6.1.6.3.1134.5.2.1.6 |
acWriteViewNameThe value of an instance of this object identifies the MIB
view to be be used to provide access control via write, i.e.,
Set operations to the zero, one, or many contexts identified
by the combination of the corresponding instances of
acContextName and acContextNameMask, for a given value of sPI
equal to the value of the corresponding instance of acSPI, if
and only if the corresponding value of acPrivs authorizes write
(Set) operations, i.e., equals readWrite(3).
The identified MIB view is that for which viewTreeName has
the same value as the instance of this object; if there are
no active view subtrees for that value, or if the value of
this object has zero-length, then the identified MIB view
is the empty set of view subtrees, and the identified set of
objects for which write (Set) operations is enabled by this
conceptual row is the empty set.rw AuthName .1.3.6.1.6.3.1134.5.2.1.7 |
acMemoryTypeThe storage type for this conceptual row in the acTable.
Conceptual rows having the value 'permanent' need not allow
write-access to any columnar objects in the row.rw MemoryType .1.3.6.1.6.3.1134.5.2.1.8 |
acStatusThe status of this conceptual row in the acTable.
A conceptual row being created in this table is not
considered ready for activation until the values of
acContextName and acContextNameMask are consistent with
all existing active rows in the table, as described above
under acContextNameMask.
For those columnar objects which permit write-access, their
value in an existing conceptual row can be changed
irrespective of the value of acStatus for that row.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1134.5.2.1.9 |
v2AdminTransport OBJECT IDENTIFIER .1.3.6.1.6.3.1134.6 |
transportSpinLockAn advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of Set operations to entries in the transportTable.
A manager application should include the value of
transportSpinLock in every Set operation which accesses the
transportTable. Since this is an advisory lock, entities
acting in an agent role do not enforce the use of
transportSpinLock.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.6.3.1134.6.1 |
transportTableThe transport endpoint database. This table need only be
implemented by entities which will send traps or inform
requests, or which will support proxy operations. SEQUENCE OF TransportEntry .1.3.6.1.6.3.1134.6.3 |
transportEntryA transport endpoint. This specifies a destination to which
notifications or proxy requests will be sent. TransportEntry .1.3.6.1.6.3.1134.6.3.1 |
transportLabelA unique name for a set of transport endpoints. TransportLabel .1.3.6.1.6.3.1134.6.3.1.1 |
transportSubindexThe sub-index for a transport endpoint. For multiply-homed
entities, a single transportLabel might refer to multiple
transport endpoints. INTEGER .1.3.6.1.6.3.1134.6.3.1.2 |
transportDomainIndicates the kind of transport service.rw OBJECT IDENTIFIER .1.3.6.1.6.3.1134.6.3.1.3 |
transportAddressThe transport service address, formatted according to the
corresponding value of transportDomain. For some operations,
this value is further qualified by the corresponding value of
transportReceiveMask, allowing a group of transport
endpoints to be specified.
For example, for the transport domain corresponding to the
snmpUDPDomain, transportAddress is formatted as a 4-octet
IP Address concatenated with a 2-octet UDP port number.rw OCTET STRING .1.3.6.1.6.3.1134.6.3.1.4 |
transportReceiveMaskThis object is used to qualify the value of the
corresponding value of transportAddress. The semantics of
this object depend on the corresponding value of
transportDomain.
For example, for the transport domain corresponding to the
snmpUDPDomain, transportReceiveMask specifies a network mask
value. This allows an entry in the transportTable to
specify an entire sub-network.rw OCTET STRING .1.3.6.1.6.3.1134.6.3.1.5 |
transportMMSThis object specifies the minimum value of the maximum
size of messages which may be sent or received using this
transport endpoint.rw Integer32 .1.3.6.1.6.3.1134.6.3.1.6 |
transportMemoryTypeThe storage type for this conceptual row in the transportTable.
Conceptual rows having the value 'permanent' need not allow
write-access to any columnar objects in the row.rw MemoryType .1.3.6.1.6.3.1134.6.3.1.7 |
transportStatusThe status of this conceptual row in the transportTable.
The values of transportDomain, transportAddress, and
transportReceiveMask in an existing conceptual row cannot be
changed while the corresponding value of transportStatus for
that row is active.
For other columnar objects which permit write-access, their
value in an existing conceptual row can be changed
irrespective of the value of transportStatus for that row.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1134.6.3.1.8 |
v2AdminNotify OBJECT IDENTIFIER .1.3.6.1.6.3.1134.7 |
notifySpinLockAn advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of the Set operation in creating view trees.
The values of viewTreeSpinLock, acSpinLock, and notifySpinLock
should be accessed in harmony to provide interlocks on the
creation of new views.
When creating a new view or altering an existing view, it is
important to understand the potential interactions with other
users of the view. The spinlocks for each table which allows
the creation of named views should be retrieved. The name of
the view to be created should be determined to be unique on
the managed system by consulting each table containing named
views. Finally, the named view may be created, including the
advisory spinlocks.
Since this is an advisory lock, entities acting in an agent
role do not enforce the use of notifySpinLock.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.6.3.1134.7.1 |
notifyTableThe notification destination database. This table need
only be implemented by entities which will send trap
notifications or inform requests.
If an entity will only send trap notifications, it need
only implement this table, in which case all entries in the
table are taken as trap destinations.
If an entity will send inform requests, it must implement
both this table, and the notifyInformParametersTable. In this
case, each entry in this table is taken as a trap or inform
destination, as specified in the corresponding value of
notifyConfirm. SEQUENCE OF NotifyEntry .1.3.6.1.6.3.1134.7.2 |
notifyEntryEach conceptual row in this table identifies a notification
destination, including, directly or indirectly, an identity,
context, and transport endpoint information to be used for
sending a notification. NotifyEntry .1.3.6.1.6.3.1134.7.2.1 |
notifyIndexAn arbitrary unique value for each notification destination. INTEGER .1.3.6.1.6.3.1134.7.2.1.1 |
notifySPIThis object identifies the security protocol to be used
when sending this notification.rw SPI .1.3.6.1.6.3.1134.7.2.1.2 |
notifyIdentityNameThe identity which will be used to send a notification. This
object specifies an identity within the security protocol
specified by the corresponding value of notifySPI.rw AuthName .1.3.6.1.6.3.1134.7.2.1.3 |
notifyTransportLabelAn instance of notifyTransportLabel identifies zero, one, or
more conceptual rows in the transportTable which describe
the transport endpoint(s) to which this notification should
be delivered.rw TransportLabel .1.3.6.1.6.3.1134.7.2.1.4 |
notifyContextNameThe context for which notifications will be sent. There
may or may not be be a corresponding conceptual row in the
v2ContextTable whose value of v2ContextName is equal to the
value of this object. If there is no corresponding conceptual
row in the v2ContextTable, then no notifications shall be
emitted as a result of this entry, even if the value of
notifyStatus is 'active'.rw AuthName .1.3.6.1.6.3.1134.7.2.1.5 |
notifyViewNameThe family of view subtrees to which this notification has
access. A notification will only be delivered to this
destination if all of the objects in the varbind list to be
delivered are included in this MIB view. This object
specifies a set of entries in the viewTreeTable whose
values of viewTreeName are equal to this object.
The identified view is that for which viewTreeName has the
same value as the instance of this object; if there are no
active view subtrees for that value, or if the value of
this object has zero-length, then the identified MIB view
is the empty set of view subtrees, and thus no objects
are included in the identified view.rw AuthName .1.3.6.1.6.3.1134.7.2.1.6 |
notifyMemoryTypeThe storage type for this conceptual row in the notifyTable.
Conceptual rows having the value 'permanent' need not allow
write-access to any columnar objects in the row.rw MemoryType .1.3.6.1.6.3.1134.7.2.1.7 |
notifyStatusThe status of this conceptual row in the notifyTable.
For those columnar objects which permit write-access, their
value in an existing conceptual row can be changed
irrespective of the value of notifyStatus for that row.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1134.7.2.1.8 |
notifyInformParametersTableDatabase of additional parameters for notification
destinations. This table need only be implemented by
entities which are configured to send inform requests
via entries in the notifyTable. SEQUENCE OF NotifyInformParametersEntry .1.3.6.1.6.3.1134.7.3 |
notifyInformParametersEntryAdditional parameters for a notification destination. NotifyInformParametersEntry .1.3.6.1.6.3.1134.7.3.1 |
notifyConfirmIndicates whether a notification should be confirmed. If
this value is true(1), then the notification will be sent
as an inform request. If the value is false(2), then the
notification will be sent as a trap.rw TruthValue (SNMPv2-TC) .1.3.6.1.6.3.1134.7.3.1.1 |
notifyAuthSnmpIDIndicates the SnmpID to be used in the AuthInfo
field of Inform requests. This object is located in this
table because the authSnmpID need only be specified
for an Inform request, since this snmpID must be that
of the entity to which the Inform is being sent. For a trap,
the authSnmpID would be equal to the local value of snmpID
of the trap sender.rw SnmpID .1.3.6.1.6.3.1134.7.3.1.2 |
notifyTimeoutThe timeout interval to be used when waiting for the response
to an inform request. After this period has expired, the
inform request will be resent. This will be repeated a number
of times up to notifyMaxRetry, until a response is
received.rw Integer32 .1.3.6.1.6.3.1134.7.3.1.3 |
notifyMaxRetryThe maximum number of times an inform request should be
re-sent when a response is not received within the interval
specified by the corresponding value of notifyTimeout.rw Integer32 .1.3.6.1.6.3.1134.7.3.1.4 |
v2AdminProxy OBJECT IDENTIFIER .1.3.6.1.6.3.1134.8 |
proxyForwardingTableThe proxy configuration database. Each conceptual row in
this database specifies configuration information for an
entity acting in a proxy role. SEQUENCE OF ProxyForwardingEntry .1.3.6.1.6.3.1134.8.2 |
proxyForwardingEntryA proxy configuration. ProxyForwardingEntry .1.3.6.1.6.3.1134.8.2.1 |
proxyIndexAn arbitrary unique value for each proxy configuration. INTEGER .1.3.6.1.6.3.1134.8.2.1.1 |
proxyTypeIndicates whether the entity will act as a proxy for
management requests being sent from one entity to another
entity (and for the corresponding responses), for traps
operations being sent from an agent to a manager, or for
inform operations being sent from a manager to another manager
(and for the corresponding responses).
If this object is equal to gnb(1), then this conceptual row
is a configuration for performing proxy operations for Get,
GetNext, and GetBulk operations.
If this object is equal to set(2), then this conceptual row
is a configuration for performing proxy operations for Set
operations.
If this object is equal to trap(3), then this conceptual
row is a configuration for performing proxy operations for
Trap operations.
If this object is equal to inform(4), then this conceptual
row is a configuration for performing proxy operations for
Inform operations.rw Enumeration .1.3.6.1.6.3.1134.8.2.1.2 |
proxySPIInThe security protocol for which the agent will act as
a proxy. This entity will only perform proxy operations
for management operations in which the security protocol
in use matches this object.rw SPI .1.3.6.1.6.3.1134.8.2.1.3 |
proxyAuthSnmpIDInThe value of authSnmpID for an incoming message. For
entries for which the value of proxyType is gnb(1), set(2) or
inform(4), this object will have the same value as the local
value for snmpID.rw SnmpID .1.3.6.1.6.3.1134.8.2.1.4 |
proxyIdentityNameInThe identity for which this agent will act as a proxy.
This entity will only perform proxy operations for management
operations in which the identity derived by the security
protocol from the authentication information matches an
instance of this object.rw AuthName .1.3.6.1.6.3.1134.8.2.1.5 |
proxyContextSnmpIDInThis object, along with the corresponding instance of
proxyContextNameIn, specifies the context for which
this entity will act as a proxy. These two objects
identify a particular globally unique context, i.e.,
a particular v2ContextSnmpID and v2ContextName pair.rw SnmpID .1.3.6.1.6.3.1134.8.2.1.6 |
proxyContextNameInThis object, along with the corresponding instance of
proxyContextSnmpIDIn, specifies the context for which
this entity will act as a proxy. These two objects
identify a particular globally unique context, i.e.,
a particular v2ContextSnmpID and v2ContextName pair.rw AuthName .1.3.6.1.6.3.1134.8.2.1.7 |
proxySPIOutThe identifier of the security protocol to be used for
forwarding the proxied requests or trap notifications.rw SPI .1.3.6.1.6.3.1134.8.2.1.8 |
proxyIdentityNameOutThe identity to be used for forwarding proxied requests or
trap notifications.rw AuthName .1.3.6.1.6.3.1134.8.2.1.10 |
proxyTransportLabelOutThe identification of zero, one, or many conceptual rows in
the transportTable whose values of transportLabel equal the
value of this object, designating the transport endpoint(s) to
which proxied requests will be forwarded.
Note that this object may specify multiple transport endpoints
to which a proxied request may be forwarded. If this is the
case, then the first response to the forwarded request which
is received will be accepted, and subsequent responses will
be discarded. In the case of proxy trap forwarding, multiple
transport end-points simply represent a proxy fan-out.rw TransportLabel .1.3.6.1.6.3.1134.8.2.1.11 |
proxyMemoryTypeThe storage type for this conceptual row in the
proxyForwardingTable. Conceptual rows having the value
'permanent' need not allow write-access to any columnar
objects in the row.rw MemoryType .1.3.6.1.6.3.1134.8.2.1.12 |
proxyStatusThe status of this conceptual row in the proxyForwardingTable.
For those columnar objects which permit write-access, their
value in an existing conceptual row can be changed
irrespective of the value of proxyStatus for that row.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1134.8.2.1.13 |
v2AdminMIBConformance OBJECT IDENTIFIER .1.3.6.1.6.3.1134.10 |
v2AdminMIBCompliances OBJECT IDENTIFIER .1.3.6.1.6.3.1134.10.1 |
v2AdminMIBGroups OBJECT IDENTIFIER .1.3.6.1.6.3.1134.10.2 |