RE: migrate from V2 to V3

This is a discussion on RE: migrate from V2 to V3 within the SNMP Users forums, part of the Networking and Network Related category; On Wed, 2005-12-14 at 09:42 +0800, Jim Su wrote: > Thanks for the reply. > > The ...


Go Back   Usenet Forums > Networking and Network Related > SNMP Users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 12-14-2005
Dave Shield
 
Posts: n/a
Default RE: migrate from V2 to V3

On Wed, 2005-12-14 at 09:42 +0800, Jim Su wrote:
> Thanks for the reply.
>
> The agent is based on the Net-SNMP 5.1.2.
> Your reply confirmed that there's not much change in
> agent side other than to set --with-default-snmp-version=3,
> to include the V3 mibs such as: SNMP-TARGET-MIB.txt ,
> SNMP-USER-BASED-SM-MIB.txt , SNMP-VIEW-BASED-ACM-MIB.txt,


No - those MIBs have absolutely nothing to do with the
option "--with-default-snmp-version".

> (may be the configure option automatically includes these),


They almost certainly will be included - the View Based ACM
forms the mechanism for *all* access control (including SNMPv1
and SNMPv2c). Unless you ran a *very* stripped down "configure"
originally, all the SNMPv3 framework will already be in place.


--with-default-snmp-version is only relevant to the client
side tools. The agent doesn't use it at all.


> The manager (client) is an inherited in house application to
> monitor the interface counter, CPU and memory usage.


Built using which SNMP toolkit? Net-SNMP, or something else?


> It takes the configuration from front end UI then insert to
> the schedule for polling by the defined interval constantly.
> The in house library call the snmp_sess_init, snmp_sess_open,
> snmp_sess_session , read_objid , snmp_add_null_var ,
> snmp_sess_synch_response , snmp_sess_close etc. to get the
> values of desired counters.


That'd be using Net-SNMP then :-)


> I guess to make it work with V3 the security data such as
> username, authentic key, and private key (parameters required
> by V3 application - snmpget, snmpwalk, etc.) are needed and
> passed to the structure in the pdu, correct?


Yes.


> So all I need to do is to find out the V3 specific fields
> in the pdu structure and fill them up, correct?


Correct.
See 'snmplib/snmp_parse_args.c' for how this is done with the
standard Net-SNMP tools.


> How about the engine ID, authprotocal, and privprotocal?


The engineID will be discovered automatically, you don't
need to worry about that.
You *do* need to set the authentication and privacy protocols.
Again, see 'snmp_parse_args()'

Dave


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 10:42 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0