MIB Discovery
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). 7 (usmUserOwnAuthKeyChange)
OID : 1.3.6.1.6.3.15.1.2.2.1.7
TXT : iso. org. dod. internet. snmpV2. snmpModules. snmpUsmMIB. usmMIBObjects. usmUser. usmUserTable. usmUserEntry. usmUserOwnAuthKeyChange
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.6.3.15.1.2.2.1.7
Module SNMP-USER-BASED-SM-MIB (CISCO)
NomusmUserOwnAuthKeyChange
Accesreadwrite
Statuscurrent
DescriptionBehaves 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. In addition, the USM security model must be used for 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). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (DELL)
NomusmUserOwnAuthKeyChange
Accesreadwrite
Statuscurrent
DescriptionBehaves 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. In addition, the USM security model must be used for 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). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (ietf)
NomusmUserOwnAuthKeyChange
Accesreadwrite
Statuscurrent
DescriptionBehaves 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. In addition, the USM security model must be used for 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). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (Alcatel)
NomusmUserOwnAuthKeyChange
Accesreadwrite
Statuscurrent
DescriptionBehaves 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. In addition, the USM security model must be used for 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). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)
Module SNMP-USER-BASED-SM-MIB (FS)
NomusmUserOwnAuthKeyChange
Accesreadwrite
Statuscurrent
DescriptionBehaves 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. In addition, the USM security model must be used for 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). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned.
SyntaxeKeyChange (SNMP-USER-BASED-SM-MIB)