Li,
Why do you run with this configuration? If this is for network resilience you
would run a bond/team, not keepalived.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 22/04/2019, 14:37, "li jerry" <div...@hotmail.com> wrote:
HI All
my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via
keepalived.
After I started the cloudstack-agent, I got vip[10.226.16.10] and I
couldn't get the correct IP [10.226.16.11];
Can I have any way to get the cloudstack agent to get the correct IP
address?
Cloudstack 4.11.2
CentOS 7.5
br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute br2
valid_lft forever preferred_lft forever
inet 10.226.16.10/24 scope global secondary br2
valid_lft forever preferred_lft forever
inet6 fe80::1456:f9ff:fe06:6228/64 scope link
valid_lft forever preferred_lft forever
dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
