snmp-server engineID local|remote:
----------------------------------
Within the SNMP framework, the SNMP engine is the entity that sends/receives SNMP messages. The engine also performs message authentication and encryption. The engine ID is simply an identifier for the engine. Typically, you do not need to specify an engine ID as the router will use a default ID. The local ID is important because it is used as an input when creating security digests for user passwords. You will only configure a remote engine ID when you are sending SNMPv3 traps (informs) to another SNMP engine. In that case, you have to use the remote engine's ID to create the security digest. The 'snmp-server engineID local|remote' commands are used to configure these IDs, if required. If you don't have the correct remote engine ID, the security digest will be incorrect and the SNMP inform will simply be discarded by the remote engine.
snmp-server user
----------------
This command is used to create usernames/passwords that can be used by other SNMP engines to authenticate when they try to access the local router via SNMP. It's a better form of security than using just communities
snmp-server group
----------------
YOu can use this command to create SNMP groups to which you can then assign users. For example, if you have a certain set of users who you would like to provide restricted SNMP access to, you can create a group with the appropriate privileges. You then assign users to these groups so that they inherit these privileges. You can have multiple groups...
Hope that helps - pls rate the post if it does.
Paresh
