| commit | bc71251433ce618c95c674d7cbe75b01a94adad9 | |
| author | Martin Schwenke <martin@meltin.net> | |
| Wed, 8 Jul 2015 11:23:48 +0000 (8 21:23 +1000) | ||
| committer | Amitay Isaacs <amitay@samba.org> | |
| Tue, 14 Jul 2015 07:57:16 +0000 (14 09:57 +0200) | ||
| tree | eda403b958541d12173a305b84206fefe6e943ff | treesnapshot (tar.gz zip) |
| parent | 87c5c96b767aa317dd620f89ac3e11bb40dae70f | commitdiff |
ctdb-scripts: Support monitoring of interestingly named VLANs on bonds
VLAN interfaces on bonds with a name other than <iface>.<id>@<iface>
are not currently supported. That is, where the VLAN name isn't based
on the underlying bond name. Such VLAN interfaces can be created with
the "ip link" command, as opposed to the "vconfig" command, or by
renaming a VLAN interface.
This is improved by determining the underlying interface name for a
VLAN from the output of "ip link".
No serious attempt is made to support VLANs with '@' in their name,
although this seems to be legal. Why would you do that?
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
VLAN interfaces on bonds with a name other than <iface>.<id>@<iface>
are not currently supported. That is, where the VLAN name isn't based
on the underlying bond name. Such VLAN interfaces can be created with
the "ip link" command, as opposed to the "vconfig" command, or by
renaming a VLAN interface.
This is improved by determining the underlying interface name for a
VLAN from the output of "ip link".
No serious attempt is made to support VLANs with '@' in their name,
although this seems to be legal. Why would you do that?
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
| ctdb/config/events.d/10.interface | diffblobblamehistory |