Hi Taqdir, The engine id is used with the snmp user password to generate the MD5 digests (the system will not store the passwords - just the engine id and MD5, so if one or the other changes, you need to use the password and regenerate the MD5 hash. RFC2274 discusses the user security model)
Another thing I think was introduced with SNMPv3 but I'm pretty sure can also be used with SNMP 2c is the use of SNMP Views. This basically allow limiting which parts of the MIB tree that can be looked at for a particular user or community, an example would to allow a managed customer to pull out interface stats and cpu load but not see everything else... Cheers, Adam On Tue, Aug 24, 2010 at 4:34 PM, Taqdir Singh <[email protected]>wrote: > *Hi All,* > > ** > *In snmp v1 and v2c there was no concept of engine id and no > authentication and encryption* > ** > *so snmp v3 came with md5 authentication and encryption of packets.* > ** > *what is the purpose of snmp engine id local and remote in snmp v3? .... > default is also set...* > > > -- > -- > Taqdir Singh > /Networks > > Do today what others won't, so you can live tomorrow as others can't > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
