|
Hi Joe,
>from Vinnie's HOWTO
>
>mcast_src_ip doesn't do it. vrrpd still is listening on 0.0.0.0
This option is used if you want to mangle the src ip present in
outgoing VRRP advert. By default it used the primary interface
IP. You can use this for security reason to completly hide the
real IP. Since this is multicast traffic this is permitted design.
>I see a "master_notify" command in Vinnie's HOWTO. Is there a command
>"backup_notify". If a master goes to a backup in a clean fashion,
>I would like to remove routes. I see an smtp alert on MASTER->BACKUP.
>This is close but not quite what I want.
Yes you have notify call available for the 3 state VRRP instances can
take : MASTER/BACKUP/FAULT.
>Is there a
>
>/etc/init.d/keepalive status
>
>where it returns master|backup and a list of the other nodes that
>it is in contact with (and their status)?
All operations are logged into syslog. You can see state transition
and interface state into syslog /var/log/message (by default).
>Is there a way to force a transition master<->backup, without killing
>the keepalived on any of the nodes?
you can for master->fault by setting down interface VRRP instance
is running on.
Or you can modify the priority in the keepalived.conf and reload
on the fly keepalived.
>Is there a list of the commands available for keepalived.conf?
The fact is that due to hard development process, I have not updated
PDF file for a while. All Keepalived keyword and command can be
found in the tarball in the doc directory in file keepalived.conf.SYNOPSIS.
Best regards,
Alexandre
|
