SNMPv2-PARTY-MIB

MIB Reference — IPNetwork Monitor

All MIBsSNMPv2-PARTY-MIB

Organization: IETF SNMP Security Working Group

Last Updated: 1993-04-01

Category: SNMP Framework

Description:

Defines managed objects for SNMPv2 parties, contexts, and access control policies used in the original party-based security model.

Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
snmpModules

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

What Is SNMPv2-PARTY-MIB?

SNMPv2-PARTY-MIB is a historical IETF standards-track module (from the original, largely abandoned SNMPv2 'party-based' administrative security framework defined in RFC 1447) that models SNMPv2 parties, contexts, and the access-control policies governing communication between them. It does not expose device performance or hardware data at all; instead its objects describe security-framework entities -- party identities, transport addresses, authentication/privacy protocol parameters, and context/access-policy relationships. The SNMPv2-PARTY-MIB OIDs that do exist describe party and access-policy identities rather than anything a modern monitoring tool would poll for device health. Because this security model was superseded early on by the community-based and later USM/VACM frameworks, this MIB carries no monitoring value for hardware or software status such as uptime, temperature, or CPU load; it is essentially of historical/compatibility interest only. It has no meaningful runtime dependency beyond the SNMPv2 framework definitions it was designed alongside. In modern deployments it is essentially unused, occasionally retained in MIB archives for legacy compatibility or historical reference rather than active monitoring.

IPNetwork Monitor allows you to monitor SNMP objects defined in SNMPv2-PARTY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • vendor-neutral, standards-based MIB (obsolete SNMPv2 party security model), not tied to a specific manufacturer or device class

Monitoring Examples

There is no realistic modern monitoring scenario for this MIB -- the party-based security model it describes (party identities, authentication/privacy parameters, and context-to-party access mappings) was never widely deployed and was replaced by the community-string and USM/VACM security models still in use today. An engineer might encounter it only when working with very old SNMPv2p implementations or reviewing IETF SNMP history, not when polling a live device.

OIDs
OID symbolicOID numericTypeAccessDescription
partyMIB1.3.6.1.6.3.3The MIB module describing SNMPv2 parties.
partyAdmin1.3.6.1.6.3.3.1
partyProtocols1.3.6.1.6.3.3.1.1
noAuth1.3.6.1.6.3.3.1.1.1
noPriv1.3.6.1.6.3.3.1.1.2
desPrivProtocol1.3.6.1.6.3.3.1.1.3
v2md5AuthProtocol1.3.6.1.6.3.3.1.1.4
temporalDomains1.3.6.1.6.3.3.1.2
currentTime1.3.6.1.6.3.3.1.2.1
restartTime1.3.6.1.6.3.3.1.2.2
cacheTime1.3.6.1.6.3.3.1.2.3
initialPartyId1.3.6.1.6.3.3.1.3
initialContextId1.3.6.1.6.3.3.1.4
partyMIBObjects1.3.6.1.6.3.3.2
snmpParties1.3.6.1.6.3.3.2.1
partyTable1.3.6.1.6.3.3.2.1.1not-accessibleThe SNMPv2 Party database.
partyEntry1.3.6.1.6.3.3.2.1.1.1not-accessibleLocally held information about a particular SNMPv2 party.
PAR partyIdentity1.3.6.1.6.3.3.2.1.1.1.1Partynot-accessibleA party identifier uniquely identifying a particular SNMPv2 party.
INT partyIndex1.3.6.1.6.3.3.2.1.1.1.2INTEGERread-onlyA unique value for each SNMPv2 party. The value for each SNMPv2 party must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
OID partyTDomain1.3.6.1.6.3.3.2.1.1.1.3OBJECT IDENTIFIERread-createIndicates the kind of transport service by which the party receives network management traffic.
ADR partyTAddress1.3.6.1.6.3.3.2.1.1.1.4TAddressread-createThe transport service address by which the party receives network management traffic, formatted according to the corresponding value of partyTDomain. For snmpUDPDomain, partyTAddress is formatted as a 4-octet IP Address concatenated with a 2-octet UDP port number.
INT partyMaxMessageSize1.3.6.1.6.3.3.2.1.1.1.5INTEGERread-createThe maximum length in octets of a SNMPv2 message which this party will accept. For parties which execute at an agent, the agent initializes this object to the maximum length supported by the agent, and does not let the object be set to any larger value. For parties which do not execute at the agent, the agent must allow the manager to set this object to any legal value, even if it is larger than the agent can generate.
T/F partyLocal1.3.6.1.6.3.3.2.1.1.1.6TruthValueread-createAn indication of whether this party executes at this SNMPv2 entity. If this object has a value of true(1), then the SNMPv2 entity will listen for SNMPv2 messages on the partyTAddress associated with this party. If this object has the value false(2), then the SNMPv2 entity will not listen for SNMPv2 messages on the partyTAddress associated with this party.
OID partyAuthProtocol1.3.6.1.6.3.3.2.1.1.1.7OBJECT IDENTIFIERread-createThe authentication protocol by which all messages generated by the party are authenticated as to origin and integrity. The value noAuth signifies that messages generated by the party are not authenticated. Once an instance of this object is created, its value can not be changed.
CLO partyAuthClock1.3.6.1.6.3.3.2.1.1.1.8Clockread-createThe authentication clock which represents the local notion of the current time specific to the party. This value must not be decremented unless the party's private authentication key is changed simultaneously.
OCT partyAuthPrivate1.3.6.1.6.3.3.2.1.1.1.9OCTET STRINGread-createAn encoding of the party's private authentication key which may be needed to support the authentication protocol. Although the value of this variable may be altered by a management operation (e.g., a SNMPv2 Set-Request), its value can never be retrieved by a management operation: when read, the value of this variable is the zero length OCTET STRING. The private authentication key is NOT directly represented by the value of this variable, but rather it is represented according to an encoding. This encoding is the bitwise exclusive-OR of the old key with the new key, i.e., of the old private authentication key (prior to the alteration) with the new private authentication key (after the alteration). Thus, when processing a received protocol Set operation, the new private authentication key is obtained from the value of this variable as the result of a bitwise exclusive-OR of the variable's value and the old private authentication key. In calculating the exclusive-OR, if the old key is shorter than the new key, zero-valued padding is appended to the old key. If no value for the old key exists, a zero-length OCTET STRING is used in the calculation.
OCT partyAuthPublic1.3.6.1.6.3.3.2.1.1.1.10OCTET STRINGread-createA publically-readable value for the party. Depending on the party's authentication protocol, this value may be needed to support the party's authentication protocol. Alternatively, it may be used by a manager during the procedure for altering secret information about a party. (For example, by altering the value of an instance of this object in the same SNMPv2 Set-Request used to update an instance of partyAuthPrivate, a subsequent Get-Request can determine if the Set- Request was successful in the event that no response to the Set-Request is received, see [4].) The length of the value is dependent on the party's authentication protocol. If not used by the authentication protocol, it is recommended that agents support values of any length up to and including the length of the corresponding partyAuthPrivate object.
INT partyAuthLifetime1.3.6.1.6.3.3.2.1.1.1.11INTEGERread-createThe lifetime (in units of seconds) which represents an administrative upper bound on acceptable delivery delay for protocol messages generated by the party. Once an instance of this object is created, its value can not be changed.
OID partyPrivProtocol1.3.6.1.6.3.3.2.1.1.1.12OBJECT IDENTIFIERread-createThe privacy protocol by which all protocol messages received by the party are protected from disclosure. The value noPriv signifies that messages received by the party are not protected. Once an instance of this object is created, its value can not be changed.
OCT partyPrivPrivate1.3.6.1.6.3.3.2.1.1.1.13OCTET STRINGread-createAn encoding of the party's private encryption key which may be needed to support the privacy protocol. Although the value of this variable may be altered by a management operation (e.g., a SNMPv2 Set-Request), its value can never be retrieved by a management operation: when read, the value of this variable is the zero length OCTET STRING. The private encryption key is NOT directly represented by the value of this variable, but rather it is represented according to an encoding. This encoding is the bitwise exclusive-OR of the old key with the new key, i.e., of the old private encryption key (prior to the alteration) with the new private encryption key (after the alteration). Thus, when processing a received protocol Set operation, the new private encryption key is obtained from the value of this variable as the result of a bitwise exclusive-OR of the variable's value and the old private encryption key. In calculating the exclusive-OR, if the old key is shorter than the new key, zero-valued padding is appended to the old key. If no value for the old key exists, a zero-length OCTET STRING is used in the calculation.
OCT partyPrivPublic1.3.6.1.6.3.3.2.1.1.1.14OCTET STRINGread-createA publically-readable value for the party. Depending on the party's privacy protocol, this value may be needed to support the party's privacy protocol. Alternatively, it may be used by a manager as a part of its procedure for altering secret information about a party. (For example, by altering the value of an instance of this object in the same SNMPv2 Set-Request used to update an instance of partyPrivPrivate, a subsequent Get-Request can determine if the Set- Request was successful in the event that no response to the Set-Request is received, see [4].) The length of the value is dependent on the party's privacy protocol. If not used by the privacy protocol, it is recommended that agents support values of any length up to and including the length of the corresponding partyPrivPrivate object.
PAR partyCloneFrom1.3.6.1.6.3.3.2.1.1.1.15Partyread-createThe identity of a party to clone authentication and privacy parameters from. When read, the value { 0 0 } is returned. This value must be written exactly once, when the associated instance of partyStatus either does not exist or has the value `notReady'. When written, the value identifies a party, the cloning party, whose status column has the value `active'. The cloning party is used in two ways. One, if instances of the following objects do not exist for the party being created, then they are created with values identical to those of the corresponding objects for the cloning party: partyAuthProtocol partyAuthPublic partyAuthLifetime partyPrivProtocol partyPrivPublic Two, instances of the following objects are updated using the corresponding values of the cloning party: partyAuthPrivate partyPrivPrivate (e.g., the value of the cloning party's instance of the partyAuthPrivate object is XOR'd with the value of the partyAuthPrivate instances of the party being created.)
STO partyStorageType1.3.6.1.6.3.3.2.1.1.1.16StorageTyperead-createThe storage type for this conceptual row in the partyTable.
ROW partyStatus1.3.6.1.6.3.3.2.1.1.1.17RowStatusread-createThe status of this conceptual row in the partyTable. A party is not qualified for activation until instances of all columns of its partyEntry row have an appropriate value. In particular: A value must be written to the Party's partyCloneFrom object. If the Party's partyAuthProtocol object has the value md5AuthProtocol, then the corresponding instance of partyAuthPrivate must contain a secret of the appropriate length. Further, at least one management protocol set operation updating the value of the party's partyAuthPrivate object must be successfully processed, before the partyAuthPrivate column is considered appropriately configured. If the Party's partyPrivProtocol object has the value desPrivProtocol, then the corresponding instance of partyPrivPrivate must contain a secret of the appropriate length. Further, at least one management protocol set operation updating the value of the party's partyPrivPrivate object must be successfully processed, before the partyPrivPrivate column is considered appropriately configured. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the partyStatus column is `notReady'.
snmpContexts1.3.6.1.6.3.3.2.2
contextTable1.3.6.1.6.3.3.2.2.1not-accessibleThe SNMPv2 Context database.
contextEntry1.3.6.1.6.3.3.2.2.1.1not-accessibleLocally held information about a particular SNMPv2 context.
STR contextIdentity1.3.6.1.6.3.3.2.2.1.1.1Contextnot-accessibleA context identifier uniquely identifying a particular SNMPv2 context.
INT contextIndex1.3.6.1.6.3.3.2.2.1.1.2INTEGERread-onlyA unique value for each SNMPv2 context. The value for each SNMPv2 context must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
T/F contextLocal1.3.6.1.6.3.3.2.2.1.1.3TruthValueread-createAn indication of whether this context is realized by this SNMPv2 entity.
INT contextViewIndex1.3.6.1.6.3.3.2.2.1.1.4INTEGERread-createIf the value of an instance of this object is zero, then this corresponding conceptual row in the contextTable refers to a SNMPv2 context which identifies a proxy relationship; the values of the corresponding instances of the contextProxyDstParty, contextProxySrcParty, and contextProxyContext objects provide further information on the proxy relationship. Otherwise, if the value of an instance of this object is greater than zero, then this corresponding conceptual row in the contextTable refers to a SNMPv2 context which identifies a MIB view of a locally accessible entity; the value of the instance identifies the particular MIB view which has the same value of viewIndex; and the value of the corresponding instances of the contextLocalEntity and contextLocalTime objects provide further information on the local entity and its temporal domain.
OCT contextLocalEntity1.3.6.1.6.3.3.2.2.1.1.5OCTET STRINGread-createIf the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object identifies the local entity whose management information is in the SNMPv2 context's MIB view. The empty string indicates that the MIB view contains the SNMPv2 entity's own local management information; otherwise, a non-empty string indicates that the MIB view contains management information of some other local entity, e.g., 'Repeater1'.
OID contextLocalTime1.3.6.1.6.3.3.2.2.1.1.6OBJECT IDENTIFIERread-createIf the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object identifies the temporal context of the management information in the MIB view.
PAR contextProxyDstParty1.3.6.1.6.3.3.2.2.1.1.7Partyread-createIf the value of the corresponding instance of the contextViewIndex is equal to zero, then the value of an instance of this object identifies a SNMPv2 party which is the proxy destination of a proxy relationship. If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object is { 0 0 }.
PAR contextProxySrcParty1.3.6.1.6.3.3.2.2.1.1.8Partyread-createIf the value of the corresponding instance of the contextViewIndex is equal to zero, then the value of an instance of this object identifies a SNMPv2 party which is the proxy source of a proxy relationship. Interpretation of an instance of this object depends upon the value of the transport domain associated with the SNMPv2 party used as the proxy destination in this proxy relationship. If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object is { 0 0 }.
OID contextProxyContext1.3.6.1.6.3.3.2.2.1.1.9OBJECT IDENTIFIERread-createIf the value of the corresponding instance of the contextViewIndex is equal to zero, then the value of an instance of this object identifies the context of a proxy relationship. Interpretation of an instance of this object depends upon the value of the transport domain associated with the SNMPv2 party used as the proxy destination in this proxy relationship. If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object is { 0 0 }.
STO contextStorageType1.3.6.1.6.3.3.2.2.1.1.10StorageTyperead-createThe storage type for this conceptual row in the contextTable.
ROW contextStatus1.3.6.1.6.3.3.2.2.1.1.11RowStatusread-createThe status of this conceptual row in the contextTable. A context is not qualified for activation until instances of all corresponding columns have the appropriate value. In particular, if the context's contextViewIndex is greater than zero, then the viewStatus column of the associated conceptual row(s) in the viewTable must have the value `active'. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the contextStatus column is `notReady'.
snmpAccess1.3.6.1.6.3.3.2.3
aclTable1.3.6.1.6.3.3.2.3.1not-accessibleThe access privileges database.
aclEntry1.3.6.1.6.3.3.2.3.1.1not-accessibleThe access privileges for a particular subject SNMPv2 party when asking a particular target SNMPv2 party to access a particular SNMPv2 context.
INT aclTarget1.3.6.1.6.3.3.2.3.1.1.1INTEGERnot-accessibleThe value of an instance of this object identifies a SNMPv2 party which is the target of an access control policy, and has the same value as the instance of the partyIndex object for that party.
INT aclSubject1.3.6.1.6.3.3.2.3.1.1.2INTEGERnot-accessibleThe value of an instance of this object identifies a SNMPv2 party which is the subject of an access control policy, and has the same value as the instance of the partyIndex object for that SNMPv2 party.
INT aclResources1.3.6.1.6.3.3.2.3.1.1.3INTEGERnot-accessibleThe value of an instance of this object identifies a SNMPv2 context in an access control policy, and has the same value as the instance of the contextIndex object for that SNMPv2 context.
INT aclPrivileges1.3.6.1.6.3.3.2.3.1.1.4INTEGERread-createThe access privileges which govern what management operations a particular target party may perform with respect to a particular SNMPv2 context when requested by a particular subject party. These privileges are specified as a sum of values, where each value specifies a SNMPv2 PDU type by which the subject party may request a permitted operation. The value for a particular PDU type is computed as 2 raised to the value of the ASN.1 context-specific tag for the appropriate SNMPv2 PDU type. The values (for the tags defined in [5]) are defined in [3] as: Get : 1 GetNext : 2 Response : 4 Set : 8 unused : 16 GetBulk : 32 Inform : 64 SNMPv2-Trap : 128 The null set is represented by the value zero.
STO aclStorageType1.3.6.1.6.3.3.2.3.1.1.5StorageTyperead-createThe storage type for this conceptual row in the aclTable.
ROW aclStatus1.3.6.1.6.3.3.2.3.1.1.6RowStatusread-createThe status of this conceptual row in the aclTable.
snmpViews1.3.6.1.6.3.3.2.4
viewTable1.3.6.1.6.3.3.2.4.1not-accessibleLocally held information about the MIB views known to this SNMPv2 entity. Each SNMPv2 context which is locally accessible has a single MIB view which 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 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 viewType in the entry whose value of viewSubtree has the most sub- identifiers. If multiple entries match and have the same number of sub-identifiers, then the lexicographically greatest instance of viewType determines the inclusion or exclusion. An object instance's OBJECT IDENTIFIER X matches an entry in this table when the number of sub- identifiers in X is at least as many as in the value of viewSubtree for the entry, and each sub- identifier in the value of viewSubtree 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 viewSubtree and viewMask. In the case where no 'wild card' is defined in viewMask, the family of view subtrees reduces to a single view subtree.
viewEntry1.3.6.1.6.3.3.2.4.1.1not-accessibleInformation on a particular family of view subtrees included in or excluded from a particular SNMPv2 context's 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.
INT viewIndex1.3.6.1.6.3.3.2.4.1.1.1INTEGERnot-accessibleA unique value for each MIB view. The value for each MIB view must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
OID viewSubtree1.3.6.1.6.3.3.2.4.1.1.2OBJECT IDENTIFIERnot-accessibleA MIB subtree.
OCT viewMask1.3.6.1.6.3.3.2.4.1.1.3OCTET STRINGread-createThe bit mask which, in combination with the corresponding instance of viewSubtree, defines a family of view subtrees. Each bit of this bit mask corresponds to a sub- identifier of viewSubtree, 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 viewSubtree, 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 viewSubtree. If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of viewSubtree, 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 viewSubtree.
INT viewType1.3.6.1.6.3.3.2.4.1.1.4INTEGERread-createThe status of a particular family of view subtrees within the particular SNMPv2 context's MIB view. The value 'included(1)' indicates that the corresponding instances of viewSubtree and viewMask define a family of view subtrees included in the MIB view. The value 'excluded(2)' indicates that the corresponding instances of viewSubtree and viewMask define a family of view subtrees excluded from the MIB view.
STO viewStorageType1.3.6.1.6.3.3.2.4.1.1.5StorageTyperead-createThe storage type for this conceptual row in the viewTable.
ROW viewStatus1.3.6.1.6.3.3.2.4.1.1.6RowStatusread-createThe status of this conceptual row in the viewTable.
partyMIBConformance1.3.6.1.6.3.3.3
partyMIBCompliances1.3.6.1.6.3.3.3.1
unSecurableCompliance1.3.6.1.6.3.3.3.1.1The compliance statement for SNMPv2 entities which implement the Party MIB, but do not support any authentication or privacy protocols (i.e., only the noAuth and noPriv protocols are supported).
partyNoPrivacyCompliance1.3.6.1.6.3.3.3.1.2The compliance statement for SNMPv2 entities which implement the Party MIB, and support an authentication protocol, but do not support any privacy protocols (i.e., only the noAuth, v2md5AuthProtocol, and noPriv protocols are supported).
partyPrivacyCompliance1.3.6.1.6.3.3.3.1.3The compliance statement for SNMPv2 entities which implement the Party MIB, support an authentication protocol, and support a privacy protocol ONLY for the purpose of accessing security parameters. For all aclTable entries authorizing a subject and/or target SNMPv2 party whose privacy protocol is desPrivProtocol, to be used in accessing a SNMPv2 context, the MIB view for that SNMPv2 context shall include only those objects subordinate to partyMIBObjects, or a subset thereof, e.g., viewSubtree = { partyMIBObjects } viewMask = ''H viewType = { included } Any attempt to configure an entry in the partyTable, the contextTable, the aclTable or the viewTable such that a party using the desPrivProtocol would be authorized for use in accessing objects outside of the partyMIBObjects subtree shall result in the appropriate error response (e.g., wrongValue or inconsistentValue).
fullPrivacyCompliance1.3.6.1.6.3.3.3.1.4The compliance statement for SNMPv2 entities which implement the Party MIB, support an authentication protocol, and support a privacy protocol without restrictions on its use.
partyMIBGroups1.3.6.1.6.3.3.3.2
partyMIBGroup1.3.6.1.6.3.3.3.2.1The collection of objects allowing the description and configuration of SNMPv2 parties. Note that objects which support proxy relationships are not included in this conformance group.

RFC description

SNMPv2 security MIB (RFC 1445) defining party-based authentication and privacy mechanisms for SNMPv2 communications.

Start monitoring vendor-neutral, standards-based MIB, obsolete SNMPv2 party security model, not tied to a specific manufacturer or device class with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SNMPv2-PARTY-MIB