-
Change Request
-
Resolution: Unresolved
-
Major
-
None
-
1.8.11
-
Ubuntu Linux 11.10
In professional setups proxies and zabbix servers typically use a service ip which can be moved by a cluster management software (like pacemaker)
between two or more nodes.
Very often it is necessary to assign tow different vlans/networks/ip-addresses to a zabbix server. For example to monitor components in a management- and in the webhosting-vlan
zabbix server needs to get direct access to these networks.
The network setup could look like this:
# ip addr ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether b8:ac:6f:8f:f2:44 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether b8:ac:6f:8f:e2:48 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether b8:ac:6f:8f:d2:48 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether b8:ac:6f:8f:d2:4a brd ff:ff:ff:ff:ff:ff
6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether b8:ac:6f:8f:d2:48 brd ff:ff:ff:ff:ff:ff
inet 10.1.2.29/16 brd 10.41.255.255 scope global bond0
inet 10.1.2.101/16 scope global secondary bond0:1
inet6 fe80::baac:6fff:fe8f:d248/64 scope link
valid_lft forever preferred_lft forever
7: vlan9@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether b8:ac:6f:ef:d2:48 brd ff:ff:ff:ff:ff:ff
inet 10.13.5.221/24 brd 10.11.5.255 scope global vlan5
inet6 fe80::baac:6fff:fe8f:d248/64 scope link
valid_lft forever preferred_lft forever
I the example - the ips 10.1.2.101 and 10.13.5.221 and the zabbix server processes can be floated between two physical machines for high availability purposes.
Unfortunately it is not possible to specify multiple ip addresses as source ip´s in the following way:
/etc/zabbix/zabbix_server.conf: .... SourceIP=10.1.2.101,10.13.5.221 ....
If i do not specify a address, zabbix uses sometimes the wrong ip addresses for sending requests.
(this is ugly because i have to add all possible addresses to all zabbix-agents)
If i only specify one of the addresses - one subnet cannot be monitored.
It should be possible to specify multiple source ips and zabbix should use the automatically the correct ip for local subnets.
For non local subnets the first ip should be used.