RE: snmp configuration via xinetd fails

Thanks Dave for quick clarifications. I have few more queries. Please see inline.
 

> Date: Fri, 28 Jan 2011 14:11:03 +0000
> Subject: Re: snmp configuration via xinetd fails
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> 
> On 28 January 2011 13:59, biplab datta <[email protected]> wrote:
> > I interpreted that as launching multiple daemons (snmpd) is possible.
> > I take that is not the case for net-snmp.
> 
> No - the SNMP daemon expects to be a single process,
> responsible for handling all network management requests.
> The idea of running multiple snmpd processes is not the
> normal mode of operation.
> 
> You *might* be able to start snmpd as a "single-threaded"
> service, though I'm not sure it really buys you much.
> And delaying the agent startup until the first request comes
> in, means that this first request is more likely to time out
> (and be re-sent).
> My gut reaction is that the cure is worse than the disease!
> 
> 
> 
> > - is this one standalone deamon limitation specific to net-snmp only?
> > - do other snmp vendors support multiple agent deamons?
> 
> I've no idea - you would have to ask them yourself.
> 
> > - I was successfully able to create  multiple instances of snmpd using
> > different port number on net-snmp via this command: /usr/sbin/snmpd
> > <proto>:<HostIPaddress>:<port>
> > - I guess it uses one deamon to keep track of all instances?
> 
> No - if you start multiple daemons (listing on different ports),
> then that's what you'll get. That's something I do all the time,
> when developing new versions of the software (while leaving
> the "production" agent in service).
> 
[Biplab]: This is exactly what I wanted to do but via xinetd. Xinted supposed to just launch snmp 
daemon on the specified port when configuration is updated. So I am not sure why it did not work or did I misunderstood
something? 
By the way, how does one delete a snmpd instance started dynamically as mentioned above?
 

> But that's a relatively unusual scenario. It would be more
> usual to run a single daemon listening on multiple ports:
> 
> snmpd address1:port1 address2:port2 etc
> 
[Biplab]: My solution does not need to have multiple snmpd instances running. What I need
for snmpd is to listen on multiple ports. My solution requires that those ports can be 
updated (added/deleted) dynmically. Is this doable?
> 
> The only reason for running different agents on different ports
> would be if you needed to return different information (and hence
> have a different configuration and/or binary for each agent).
> But that counts as "advanced use of SNMP".
> 
[Biplab]: Understood.

> If you're still getting used to the basics of SNMP, then I'd suggest
> you stick to the normal model until you've gained a bit more experience
> and familiarity with how things work.
> 
> 
> Dave

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users