Start


Perform the following steps to enable SNMPv3.

  1. From SBC CLI, obtain the SBC engineId using the following CLI command:

    > show table oam snmp community
engineId 80:00:0b:3f:03:00:0c:29:c4:63:86;

  2. Use RAMP or a third-party manager to generate the authKey and privKey for SBC admin user

    Open source tools such as snmpkey can be used to generate keys if the passphrase is shared. See

    http://search.cpan.org/~dtown/Net-SNMP-5.2.0/snmpkey.PL
    for additional details.


    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>

  3. From SBC CLI, enable snmpv3 for user admin on the SBC with the authKey and privKey generated from the step 2.

    > 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 

  4. From RAMP or third-party manager, issue the snmpwalk command to confirm SNMPv3 is working on the SBC.

References

See the following pages for SNMP configuration options using CLI and EMA.