Re: SNMPd can register from one keepalived only
Vincent Bernat <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
❦ 19 juillet 2016 00:44 CEST, Quentin Armitage <[email protected]> : > By default, keepalived communicates with snmpd via the Unix domain > socket /var/agentx/master. Since the keepalived instances are already > in separate network namespaces, it might be simplest to specify: > snmp_socket udp:127.0.0.1:161 > in the global section of the keepalived configurations so that > keepalived uses network communication with snmpd, which of course will > be in the separate network namespaces. 2 instances of snmpd will need > to be run prior to running the keepalvied instances, using ip netns > NETNS_NAME1 snmpd ... and ip netns NETNS_NAME2 snmpd ... (or use > nsenter for the keepalived processes to run in the same network > namespaces as the snmpd instances). I doubt that a master agent will listen to subagent on the main socket. The proper port for AgentX protocol is 705 (and should be enabled in snmpd.conf as well). > An alternative would be to use different unix domain sockets, e.g. > /var/agentx/master1 and /var/agentx/master2 (specified with the -x > option to snmpd) and configured in keepalived with "snmp_socket > unix:/var/agentx/master1" etc in the global section of the keepalived > configs. > > A further option might be to run each instance of snmpd in a separate > IPC namespace, and then use nsenter to run the keepalived processes in > the same IPC namespaces as the snmpd processes. I think that IPC namespaces doesn't cover unix sockets, only SysV IPC (semaphores, shared memory and message queue). -- Make it clear before you make it faster. - The Elements of Programming Style (Kernighan & Plauger) ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Keepalived-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/keepalived-devel