Carp master problem
Chris McGee
chris at gliq.com
Thu Jun 30 04:38:02 GMT 2005
I have to machines in a test environment, the carp0 interface on the
machines will not become master. The config is as follows:
test1# ifconfig
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 192.168.1.252 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::230:48ff:fe82:a77c%em0 prefixlen 64 scopeid 0x1
ether 00:30:48:82:a7:7c
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 10.10.10.2 netmask 0xfffffff8 broadcast 10.10.10.7
inet6 fe80::230:48ff:fe82:a77d%em1 prefixlen 64 scopeid 0x2
ether 00:30:48:82:a7:7d
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
carp0: flags=41<UP,RUNNING> mtu 1500
inet 192.168.1.10 netmask 0xffffff00
carp: BACKUP vhid 1 advbase 1 advskew 0
carp1: flags=41<UP,RUNNING> mtu 1500
inet 10.10.10.1 netmask 0xfffffff8
carp: MASTER vhid 2 advbase 1 advskew 0
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 192.168.1.253 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::230:48ff:fe80:21bc%em0 prefixlen 64 scopeid 0x1
ether 00:30:48:80:21:bc
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 10.10.10.3 netmask 0xfffffff8 broadcast 10.10.10.7
inet6 fe80::230:48ff:fe80:21bd%em1 prefixlen 64 scopeid 0x2
ether 00:30:48:80:21:bd
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
carp0: flags=41<UP,RUNNING> mtu 1500
inet 192.168.1.10 netmask 0xffffff00
carp: BACKUP vhid 1 advbase 1 advskew 100
carp1: flags=41<UP,RUNNING> mtu 1500
inet 10.10.10.1 netmask 0xfffffff8
carp: BACKUP vhid 2 advbase 1 advskew 100
both test1 and test2 have these sysctl variables:
net.inet.carp.allow: 1
net.inet.carp.preempt: 1
net.inet.carp.log: 1
net.inet.carp.arpbalance: 0
If I down the carp1 interface on either box the other box becomes
master. If I down the carp0 interface on either box, the other stays
backup. Both carp0 interfaces stay backup all the time and therefore I
can't access 192.168.1.10.
Thanks,
Chris
More information about the freebsd-pf
mailing list