On 11/4/05, Robert Story <[EMAIL PROTECTED]> wrote:
With the information I got, my OS supports. But by default (if no port number is specified) the agent listens at 161. So will net-snmp agent supports for this kinda accessing same port 161 by more than one virtual IP Address at the same time?
On Thu, 3 Nov 2005 17:45:09 +0530 aakansha wrote:
AR> I restarted the network and started the agent with the IP Address
AR> "snmpd -f -Le 192.162.9.2 < http://192.162.9.2>"
AR>
AR> The agent got started. Now in another shell I executed, "snmpd -f -Le
AR> 192.162.9.3 <http://192.162.9.3 >"
AR>
AR> But the message displayed was,
AR>
AR> Error opening specified endpoint 192.168.9.1:161 <http://192.168.9.1:161 >
AR> Server exiting with error code 1.
AR>
AR> So the virtual IP's are there.. But the access is made to the real IP
AR> address 192.168.9.1 < http://192.168.9.1> and the port 161.
It is going to be up to your OS as to whether or not you can open the same
(non-shared) port on a virtual ip address.
With the information I got, my OS supports. But by default (if no port number is specified) the agent listens at 161. So will net-snmp agent supports for this kinda accessing same port 161 by more than one virtual IP Address at the same time?
It looks like yours won't, so you
are stuck with 1 agent for all the virtual addresses on an interface, or using
different ports.
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: < http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: < http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
