Page History
...
Start
Perform the following steps to enable SNMPv3.
From SBC CLI, obtain the SBC engineId using the following CLI command:
Code Block language none > show table oam snmp community engineId 80:00:0b:3f:03:00:0c:29:c4:63:86;
Use
Use the EMS or a third-party manager to generate the authKey and privKey for SBC admin userSpacevars 0 model3 Info Open source tools such as snmpkey can be used to generate keys if the passphrase is shared. See
for additional details.Link_in_new_tab Text http://search.cpan.org/~dtown/Net-SNMP-5.2.0/snmpkey.PL URL http://search.cpan.org/~dtown/Net-SNMP-5.2.0/snmpkey.PL
In this example, the generated keys are:<usmUserAuthKey>1E:29:3D:1C:2A:BE:67:BD:E5:B8:F0:23:56:B9:90:62</usmUserAuthKey>
<usmUserPrivKey>1E:29:3D:1C:2A:BE:67:BD:E5:B8:F0:23:56:B9:90:62</usmUserPrivKey>
From SBC CLI, enable snmpv3 for user admin on the SBC with the authKey and privKey generated from the step 2.
Code Block language none > configure Entering configuration mode private [ok][2015-02-06 06:06:46] [edit] % set oam snmp securityLevel authPriv version v3only users admin authProtocol HMACMD5 authKey 1E:29:3D:1C:2A:BE:67:BD:E5:B8:F0:23:56:B9:90:62 privProtocol DES privKey 1E:29:3D:1C:2A:BE:67:BD:E5:B8:F0:23:56:B9:90:62 group admin % commit
From EMS
or third-party manager, perform issue the snmpwalk command to confirm SNMPv3 is working on the SBC.Spacevars 0 model3
...
Overview
Content Tools