MIB Discovery

Recherche :

1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 6 (snmpV2). 3 (snmpModules). 15 (snmpUsmMIB). 1 (usmMIBObjects). 2 (usmUser). 2 (usmUserTable). 1 (usmUserEntry). 9 (usmUserPrivKeyChange)
OID : 1.3.6.1.6.3.15.1.2.2.1.9
TXT : iso. org. dod. internet. snmpV2. snmpModules. snmpUsmMIB. usmMIBObjects. usmUser. usmUserTable. usmUserEntry. usmUserPrivKeyChange
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.6.3.15.1.2.2.1.9
Module SNMP-USER-BASED-SM-MIB (CISCO)
NomusmUserPrivKeyChange
Accesreadwrite
Statuscurrent
DescriptionAn 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 instance of usmUserCloneFrom. When the value of the corresponding usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (DELL)
NomusmUserPrivKeyChange
Accesreadwrite
Statuscurrent
DescriptionAn 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 instance of usmUserCloneFrom. When the value of the corresponding usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (ietf)
NomusmUserPrivKeyChange
Accesreadwrite
Statuscurrent
DescriptionAn 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 instance of usmUserCloneFrom. When the value of the corresponding usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (Alcatel)
NomusmUserPrivKeyChange
Accesreadwrite
Statuscurrent
DescriptionAn 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 instance of usmUserCloneFrom. When the value of the corresponding usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (FS)
NomusmUserPrivKeyChange
Accesreadwrite
Statuscurrent
DescriptionAn 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 instance of usmUserCloneFrom. When the value of the corresponding usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
D. Fournier - 2024