So here's our address setup: mmces address list
Address Node Group Attribute
-------------------------------------------------------------------------
172.28.45.72 arproto1.ar.nis.isb.internal isb none
172.28.45.73 arproto2.ar.nis.isb.internal isb none
172.28.46.72 arproto2.ar.nis.vtc.internal vtc none
172.28.46.73 arproto1.ar.nis.vtc.internal vtc none
Having some nfs-ganesha weirdness on arproto2.ar.nis.vtc.internal, so I try to
move the address over to its pair so I can look around without impacting users.
However, seems like something insists on moving it right back 60 seconds
later...
Question 1: Is this expected behavior?
Question 2: If it is, what use is 'mmces address move' if it just gets
undone a few seconds later...
(running on arproto2.ar.nis.vtc.internal):
## (date; ip addr show | grep '\.72';mmces address move --ces-ip 172.28.46.72
--ces-node arproto1.ar.nis.vtc.internal; while (/bin/true); do date; ip addr
show | grep '\.72'; sleep 1; done;) | tee migrate.not.nailed.down
Mon Jun 12 15:34:33 EDT 2017
inet 172.28.46.72/26 brd 172.28.46.127 scope global secondary bond1:0
Mon Jun 12 15:34:40 EDT 2017
Mon Jun 12 15:34:41 EDT 2017
Mon Jun 12 15:34:42 EDT 2017
Mon Jun 12 15:34:43 EDT 2017
(skipped)
Mon Jun 12 15:35:44 EDT 2017
Mon Jun 12 15:35:45 EDT 2017
inet 172.28.46.72/26 brd 172.28.46.127 scope global secondary bond1:0
Mon Jun 12 15:35:46 EDT 2017
inet 172.28.46.72/26 brd 172.28.46.127 scope global secondary bond1:0
Mon Jun 12 15:35:47 EDT 2017
inet 172.28.46.72/26 brd 172.28.46.127 scope global secondary bond1:0
^C
pgpaQA6Jtz410.pgp
Description: PGP signature
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
