Bug #1023
closed
Carp Status Incorrect
0%
Description
I Have Multiple Carp Interfaces (vip21 - vip24),
on the Status Page and the Dashboard Widget all
Interfaces have the state of the first Interfaces
(in my case vip21). If vip21 is Master all are Shown
as master even if they are in Backup state.
If vip21 is Backup all are shown as backup.
Updated by Jim Pingle about 14 years ago
Do you have a screenshot output of the CARP status and the ifconfig -a output that confirms these are producing conflicting output?
Generally all of the VIPs on the master are master, and all on the backup are backup, and they all flip at once when there is a failover. It's not typical to have only certain VIPs be master and others backup.
Updated by Martin Klein about 14 years ago
Sorry I dont have a screenshot at the moment but here are the ifconfigs:
machine 1:
vip21: flags=8<LOOPBACK> metric 0 mtu 1500
inet 192.168.1.1 netmask 0xffffff00
carp: INIT vhid 21 advbase 1 advskew 0
vip22: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 172.16.1.1 netmask 0xffffff00
carp: MASTER vhid 22 advbase 1 advskew 0
vip23: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.2.1 netmask 0xffffff00
carp: MASTER vhid 23 advbase 1 advskew 0
vip24: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 81.16.52.1 netmask 0xffffff80
carp: MASTER vhid 24 advbase 1 advskew 0
machine 2:
vip21: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.1.1 netmask 0xffffff00
carp: MASTER vhid 21 advbase 1 advskew 100
vip22: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 172.16.1.1 netmask 0xffffff00
carp: BACKUP vhid 22 advbase 1 advskew 100
vip23: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.2.1 netmask 0xffffff00
carp: BACKUP vhid 23 advbase 1 advskew 100
vip24: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 81.16.52.1 netmask 0xffffff00
carp: BACKUP vhid 24 advbase 1 advskew 100
And in the status they both show master status on all
interfaces.
Updated by Ermal Luçi
Updated by Martin Klein almost 14 years ago
Tried the snapshot from today and
everything seems Fixed.
Thank You
Updated by Chris Buechler almost 14 years ago
- Status changed from Feedback to Resolved