On 19/05/2014 13:28, Borzenkov, Andrey wrote:
It is better to completely unconfigure ifgrp before destroying it, just to be on safe side.
You mean: - ifconfig LAG_CIFS down - ifgrp delete LAG_CIFS e0a - ifgrp delete LAG_CIFS e0b - ifgrp delete LAG_CIFS e0c - ifgrp delete LAG_CIFS e0d - ifgrp destroy LAG_CIFS
- ifgrp create lacp LAG_CIFS -b ip e1a e1b
No ifconfig after that? You will need to configure new interface.
Forgot it. It would mean: ifconfig LAG_CIFS `hostname`-LAG_CIFS netmask 255.255.255.0 partner LAG_iSCSI nfo
You will also need to edit /etc/rc to make change persistent. And ideally perform takeover/giveback (in both directions) to verify changes in /etc/rc.
Sure, that was my plan too. Forgot to mention it.
Would I need to restart services like iSCSI/NFS/CIFS/.... ?
Should not, at least as long as IP remains the same.
It is also possible to do it as non-disruptively as theoretically possible (but you say "CIFS", so it is already disruptive ...) by performing takeover, editing /etc/rc of taken over partner and performing giveback. Then repeating for second node.
True. CIFS is always disruptive, though minimally if failover times are short.