FW 08.01.00 McDATA E/OS SNMP Support Manual (620-000131-630, November 2005)

G
G-10
E/OS SNMP Support Manual
SNMPv3 MIB
If the new user is to use privacy:
• generate the keyChange value based on the secret privKey of the
clone-from user and the secret key to be used for the new user.
Let us call this pkcValue.
• GET(usmUserSpinLock.0) and save in sValue.
• SET(usmUserSpinLock.0=sValue,
usmUserPrivKeyChange=pkcValue
usmUserPublic=randomValue1)
• GET(usmUserPulic) and check it has randomValue1.
If not, repeat steps 4-6.
If the new user will never use privacy:
• SET(usmUserPrivProtocol=usmNoPrivProtocol)
If the new user is to use authentication:
• generate the keyChange value based on the secret authKey of the
clone-from user and the secret key to be used for the new user.
Let us call this akcValue.
• GET(usmUserSpinLock.0) and save in sValue.
• SET(usmUserSpinLock.0=sValue,
usmUserAuthKeyChange=akcValue
usmUserPublic=randomValue2)
• GET(usmUserPulic) and check it has randomValue2.
If not, repeat steps 9-11.
If the new user will never use authentication:
• SET(usmUserAuthProtocol=usmNoAuthProtocol)
Finally, activate the new user:
• SET(usmUserStatus=active)
The new user should now be available and ready to be used for
SNMPv3 communication. Note however that access to MIB data
must be provided via configuration of the
SNMP-VIEW-BASED-ACM-MIB.
The use of usmUserSpinlock is to avoid conflicts with another SNMP
command responder application which may also be acting on the
usmUserTable.
Sequence
::= { usmUser 2 }