# @(#)79 1.3 src/bos/usr/lib/nim/methods/HowToConfigure.snmp, cmdnim, bos720 9/26/05 15:38:58

== How To Configure /usr/lp/bos.sysmgt/nim/methods/bladeOps ==

The mm_mib.defs file contains object definitions for BladeCenter
Management Information Base (MIB) variables. Verify that the variables
listed in mm_mib.defs are contained in the /etc/mib.defs file.  If the
variables are not present, you should append the mm_mib.defs variables
to the /etc/mib.defs file.

Once the MIB variables are defined in /etc/mib.defs, setup User-Based 
Security Model values (SNMPv3) or Community-based security  (SNMPv1)
in /etc/clsnmp.conf.

Format of entries:

### User-based Security Model (USM with SNMPV3) ###
winSnmpName  targetAgent  admin  secName  password  context secLevel authProto  authKey  privProto  privKey
-----------------------------------------------------------------------------------------------------------
#example
mmv3          10.10.1.190 snmpv3 nimadmin passw0rd  passw0rd AuthNoPriv HMAC-MD5 -        -         -


### Community-based security  (SNMPv1) ###
winSnmpName  targetAgent   admin  
----------------------------------
#example
mmv1          10.10.1.190  snmpv1

More examples are located under /usr/samples/snmpdv3/clsnmp.conf.  Once the
security models are defined, you may enable snmpv1 and/or snmpv3 agent(s) on
the Management Module of your BladeCenter.  Any values provided for snmpd setup
on the Management Module should match the values stored in /etc/clsnmp.conf.

Use the command /usr/lpp/bos.sysmgt/nim/methods/bladeOps (or create an alias)
for querying / setting values for MIB variables.  The bladeOps command calls
the clsnmp command underneath, so please refer to the man page if you are
unsure of the clsnmp.conf setup.

NOTE: The usage of authkey values for USM does not work well for the Management
Module snmp agent.  Although keys are advised, please use the password field if
authentication does not work for you. (see example above).