samba - Sep 2016 - 答复: 答复: How to disable CTDB pulling up NICs

If eth0 holds virtual IP as its secondary IP and I bring down eth0 by command
"ifdown eth0", CTDB will automatically pull eth0 up. Sometime it goes
wrong. The virtual IP becomes primary IP, and origin primary IP turns into a
secondary IP or just missing. If the origin primary IP is missing, I have to run
"ifup eth0" though CTDB has pulled eth0 up. CTDB uses “ip link set
eth0 up” to pull up a NIC. I suppose “ifdown/ifup” are not compatible with “ip
link set”.

-----邮件原件-----
发件人: Martin Schwenke [mailto:martin at meltin.net]
发送时间: 2016年9月14日 19:00
收件人: Weidong via samba
抄送: weidong 12656 (RD); xusangdi 11976 (RD)
主题: Re: [Samba] How to disable CTDB pulling up NICs

On Wed, 14 Sep 2016 06:02:13 +0000, Weidong via samba <samba at
lists.samba.org> wrote:
> Thanks for your attention. CTDB manages NICs with event scripts.
> Virtual IP attaches on a NIC as a secondary IP. When noticing the NIC
> down, CTDB will pull it up. Does any one know how to disable the
> action? I do not want CTDB pull any NIC up. Does the command 'ctdb
> disablescript 10.interface' has any unexpected effect?
10.interface actually removes/adds public IP addresses from/to interfaces.  So,
without this script CTDB's public IP addresses will not work.

There is no supported way to disable the behaviour of pulling up interfaces.

Why do you want to want to disable this?

peace & happiness,
martin
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which
is
intended only for the person or entity whose address is listed above. Any use of
the
information contained herein in any way (including, but not limited to, total or
partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify
the sender
by phone or email immediately and delete it!

On Sun, 18 Sep 2016 01:36:20 +0000, Weidong via samba
<samba at lists.samba.org> wrote:
> If eth0 holds virtual IP as its secondary IP and I bring down eth0 by
> command "ifdown eth0", CTDB will automatically pull eth0 up.
Sometime
> it goes wrong. The virtual IP becomes primary IP, and origin primary
> IP turns into a secondary IP or just missing. If the origin primary
> IP is missing, I have to run "ifup eth0" though CTDB has pulled
eth0
> up.
Why do you want to take an interface down if it is used for CTDB public
IP addresses?

An interface that hosts CTDB public IP addresses should be used only
for that purpose.  You can put a static address on that interface,
which can help the node reach infrastructure (e.g. DNS or Active
Directory server) but there should never be a need to take the
interface down.

You should use another, separate private network for the fixed, private
node IP addresses.

If you need to do anything else then you should consider a 3rd network.
> CTDB uses “ip link set eth0 up” to pull up a NIC. I suppose
> “ifdown/ifup” are not compatible with “ip link set”.
Depending on your platform, the ip command (as in "ip link set") might
be used as a low-level primitive in the implementation of ifdown/ifup.

You can not expect to be doing arbitrary network configuration on an
interface while CTDB is trying to use and manage it...

peace & happiness,
martin

Thank you very much for reply. Our test team insists on simulating network
failure by using ifdown instead of just unpluging the cable. I have to modify
the event script 10.interface. When noticing a NIC failure, CTDB just marks the
NIC down and do not try to pull it up. It seems to work fine.

-----邮件原件-----
发件人: Martin Schwenke [mailto:martin at meltin.net]
发送时间: 2016年9月18日 18:49
收件人: Weidong via samba
抄送: weidong 12656 (RD)
主题: Re: [Samba] 答复: How to disable CTDB pulling up NICs

On Sun, 18 Sep 2016 01:36:20 +0000, Weidong via samba <samba at
lists.samba.org> wrote:
> If eth0 holds virtual IP as its secondary IP and I bring down eth0 by
> command "ifdown eth0", CTDB will automatically pull eth0 up.
Sometime
> it goes wrong. The virtual IP becomes primary IP, and origin primary
> IP turns into a secondary IP or just missing. If the origin primary IP
> is missing, I have to run "ifup eth0" though CTDB has pulled eth0
up.
Why do you want to take an interface down if it is used for CTDB public IP
addresses?

An interface that hosts CTDB public IP addresses should be used only for that
purpose.  You can put a static address on that interface, which can help the
node reach infrastructure (e.g. DNS or Active Directory server) but there should
never be a need to take the interface down.

You should use another, separate private network for the fixed, private node IP
addresses.

If you need to do anything else then you should consider a 3rd network.
> CTDB uses “ip link set eth0 up” to pull up a NIC. I suppose
> “ifdown/ifup” are not compatible with “ip link set”.
Depending on your platform, the ip command (as in "ip link set") might
be used as a low-level primitive in the implementation of ifdown/ifup.

You can not expect to be doing arbitrary network configuration on an interface
while CTDB is trying to use and manage it...

peace & happiness,
martin
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which
is
intended only for the person or entity whose address is listed above. Any use of
the
information contained herein in any way (including, but not limited to, total or
partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify
the sender
by phone or email immediately and delete it!