⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2274.mib

📁 wm PNE 3.3 source code, running at more than vxworks6.x version.
💻 MIB
📖 第 1 页 / 共 2 页
字号:
    {        usmUserEngineID         SnmpEngineID,        usmUserName             SnmpAdminString,        usmUserSecurityName     SnmpAdminString,        usmUserCloneFrom        RowPointer,        usmUserAuthProtocol     AutonomousType,        usmUserAuthKeyChange    KeyChange,        usmUserOwnAuthKeyChange KeyChange,        usmUserPrivProtocol     AutonomousType,        usmUserPrivKeyChange    KeyChange,        usmUserOwnPrivKeyChange KeyChange,        usmUserPublic           OCTET STRING,        usmUserStorageType      StorageType,        usmUserStatus           RowStatus    }usmUserEngineID  OBJECT-TYPE    SYNTAX       SnmpEngineID    MAX-ACCESS   not-accessible    STATUS       current    DESCRIPTION "An SNMP engine's administratively-unique identifier.                 In a simple agent, this value is always that agent's                 own snmpEngineID value.                 The value can also take the value of the snmpEngineID                 of a remote SNMP engine with which this user can                 communicate.                "    ::= { usmUserEntry 1 }usmUserName      OBJECT-TYPE    SYNTAX       SnmpAdminString (SIZE(1..32))    MAX-ACCESS   not-accessible    STATUS       current    DESCRIPTION "A human readable string representing the name of                 the user.                 This is the (User-based Security) Model dependent                 security ID.                "    ::= { usmUserEntry 2 }usmUserSecurityName OBJECT-TYPE    SYNTAX       SnmpAdminString    MAX-ACCESS   read-only    STATUS       current    DESCRIPTION "A human readable string representing the user in                 Security Model independent format.                 The default transformation of the User-based Security                 Model dependent security ID to the securityName and                 vice versa is the identity function so that the                 securityName is the same as the userName.                "    ::= { usmUserEntry 3 }usmUserCloneFrom OBJECT-TYPE    SYNTAX       RowPointer    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "A pointer to another conceptual row in this                 usmUserTable.  The user in this other conceptual                 row is called the clone-from user.                 When a new user is created (i.e., a new conceptual                 row is instantiated in this table), the privacy and                 authentication parameters of the new user are cloned                 from its clone-from user.                 The first time an instance of this object is set by                 a management operation (either at or after its                 instantiation), the cloning process is invoked.                 Subsequent writes are successful but invoke no                 action to be taken by the receiver.                 The cloning process fails with an 'inconsistentName'                 error if the conceptual row representing the                 clone-from user is not in an active state when the                 cloning process is invoked.                 Cloning also causes the initial values of the secret                 authentication key and the secret encryption key of                 the new user to be set to the same value as the                 corresponding secret of the clone-from user.                 When this object is read, the ZeroDotZero OID                 is returned.                "    ::= { usmUserEntry 4 }usmUserAuthProtocol OBJECT-TYPE    SYNTAX       AutonomousType    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "An indication of whether messages sent on behalf of                 this user to/from the SNMP engine identified by                 usmUserEngineID, can be authenticated, and if so,                 the type of authentication protocol which is used.                 An instance of this object is created concurrently                 with the creation of any other object instance for                 the same user (i.e., as part of the processing of                 the set operation which creates the first object                 instance in the same conceptual row).  Once created,                 the value of an instance of this object can not be                 changed.                 If a set operation tries to set a value for an unknown                 or unsupported protocol, then a wrongValue error must                 be returned.                "    DEFVAL      { usmHMACMD5AuthProtocol }    ::= { usmUserEntry 5 }usmUserAuthKeyChange OBJECT-TYPE    SYNTAX       KeyChange   -- typically (SIZE (0..32))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "An object, which when modified, causes the secret                 authentication key used for messages sent on behalf                 of this user to/from the SNMP engine identified by                 usmUserEngineID, to be modified via a one-way                 function.                 The associated protocol is the usmUserAuthProtocol.                 The associated secret key is the user's secret                 authentication key (authKey). The associated hash                 algorithm is the algorithm used by the user's                 usmUserAuthProtocol.                 When creating a new user, it is an 'inconsistentName'                 error for a Set operation to refer to this object                 unless it is previously or concurrently initialized                 through a set operation on the corresponding value                 of usmUserCloneFrom.                "    DEFVAL      { ''H }    -- the empty string    ::= { usmUserEntry 6 }usmUserOwnAuthKeyChange OBJECT-TYPE    SYNTAX       KeyChange  -- typically (SIZE (0..32))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "Behaves exactly as usmUserAuthKeyChange, with one                 notable difference: in order for the Set operation                 to succeed, the usmUserName of the operation                 requester must match the usmUserName that                 indexes the row which is targeted by this                 operation.                 The idea here is that access to this column can be                 public, since it will only allow a user to change                 his own secret authentication key (authKey).                "    DEFVAL      { ''H }    -- the empty string    ::= { usmUserEntry 7 }usmUserPrivProtocol OBJECT-TYPE    SYNTAX       AutonomousType    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "An indication of whether messages sent on behalf of                 this user to/from the SNMP engine identified by                 usmUserEngineID, can be protected from disclosure,                 and if so, the type of privacy protocol which is used.                 An instance of this object is created concurrently                 with the creation of any other object instance for                 the same user (i.e., as part of the processing of                 the set operation which creates the first object                 instance in the same conceptual row).  Once created,                 the value of an instance of this object can not be                 changed.                 If a set operation tries to set a value for an unknown                 or unsupported protocol, then a wrongValue error must                 be returned.                "    DEFVAL      { usmNoPrivProtocol }    ::= { usmUserEntry 8 }usmUserPrivKeyChange OBJECT-TYPE    SYNTAX       KeyChange  -- typically (SIZE (0..32))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "An object, which when modified, causes the secret                 encryption key used for messages sent on behalf                 of this user to/from the SNMP engine identified by                 usmUserEngineID, to be modified via a one-way                 function.                 The associated protocol is the usmUserPrivProtocol.                 The associated secret key is the user's secret                 privacy key (privKey). The associated hash                 algorithm is the algorithm used by the user's                 usmUserAuthProtocol.                 When creating a new user, it is an 'inconsistentName'                 error for a set operation to refer to this object                 unless it is previously or concurrently initialized                 through a set operation on the corresponding value                 of usmUserCloneFrom.                "    DEFVAL      { ''H }    -- the empty string    ::= { usmUserEntry 9 }usmUserOwnPrivKeyChange OBJECT-TYPE    SYNTAX       KeyChange  -- typically (SIZE (0..32))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one                 notable difference: in order for the Set operation                 to succeed, the usmUserName of the operation                 requester must match the usmUserName that indexes                 the row which is targeted by this operation.                 The idea here is that access to this column can be                 public, since it will only allow a user to change                 his own secret privacy key (privKey).                "    DEFVAL      { ''H }    -- the empty string    ::= { usmUserEntry 10 }usmUserPublic    OBJECT-TYPE    SYNTAX       OCTET STRING (SIZE(0..32))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "A publicly-readable value which is written as part                 of the procedure for changing a user's secret                 authentication and/or privacy key, and later read to                 determine whether the change of the secret was                 effected.                "    DEFVAL      { ''H }  -- the empty string    ::= { usmUserEntry 11 }usmUserStorageType OBJECT-TYPE    SYNTAX       StorageType    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "The storage type for this conceptual row.                 Conceptual rows having the value 'permanent'                 must allow write-access at a minimum to:                 - usmUserAuthKeyChange, usmUserOwnAuthKeyChange                   and usmUserPublic for a user who employs                   authentication, and                 - usmUserPrivKeyChange, usmUserOwnPrivKeyChange                   and usmUserPublic for a user who employs                   privacy.                 Note that any user who employs authentication or                 privacy must allow its secret(s) to be updated and                 thus cannot be 'readOnly'.                "    DEFVAL      { nonVolatile }    ::= { usmUserEntry 12 }usmUserStatus    OBJECT-TYPE    SYNTAX       RowStatus    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "The status of this conceptual row.                 Until instances of all corresponding columns are                 appropriately configured, the value of the                 corresponding instance of the usmUserStatus column                 is 'notReady'.                 In particular, a newly created row cannot be made                 active until the corresponding usmUserCloneFrom,                 usmUserAuthKeyChange, usmUserOwnAuthKeyChange,                 usmUserPrivKeyChange and usmUserOwnPrivKeyChange                 have all been set.                 The  RowStatus TC [RFC1903] 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.                "    ::= { usmUserEntry 13 }-- Conformance Information *******************************************usmMIBCompliances OBJECT IDENTIFIER ::= { usmMIBConformance 1 }usmMIBGroups      OBJECT IDENTIFIER ::= { usmMIBConformance 2 }-- Compliance statementsusmMIBCompliance MODULE-COMPLIANCE    STATUS       current    DESCRIPTION "The compliance statement for SNMP engines which                 implement the SNMP-USER-BASED-SM-MIB.                "    MODULE       -- this module        MANDATORY-GROUPS { usmMIBBasicGroup }        OBJECT           usmUserAuthProtocol        MIN-ACCESS       read-only        DESCRIPTION     "Write access is not required."        OBJECT           usmUserPrivProtocol        MIN-ACCESS       read-only        DESCRIPTION     "Write access is not required."    ::= { usmMIBCompliances 1 }-- Units of complianceusmMIBBasicGroup OBJECT-GROUP    OBJECTS     {                  usmStatsUnsupportedSecLevels,                  usmStatsNotInTimeWindows,                  usmStatsUnknownUserNames,                  usmStatsUnknownEngineIDs,                  usmStatsWrongDigests,                  usmStatsDecryptionErrors,                  usmUserSpinLock,                  usmUserSecurityName,                  usmUserCloneFrom,                  usmUserAuthProtocol,                  usmUserAuthKeyChange,                  usmUserOwnAuthKeyChange,                  usmUserPrivProtocol,                  usmUserPrivKeyChange,                  usmUserOwnPrivKeyChange,                  usmUserPublic,                  usmUserStorageType,                  usmUserStatus                }    STATUS       current    DESCRIPTION "A collection of objects providing for configuration                 of an SNMP engine which implements the SNMP                 User-based Security Model.                "    ::= { usmMIBGroups 1 }END

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -