FreeBSD 10-STABLE and CARP states

mxb mxb at alumni.chalmers.se
Wed Apr 2 13:18:28 UTC 2014


OK, thanks everyone whom replayed. E.g. NONE.

The problem seems to be related to LACP trunking.
Disabling LACP and configuring trunk in ‘loadbalance’ mode puts all in desired state (even after reboot).

lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
	options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
	ether 00:25:90:e3:71:f2
	inet 172.16.0.234 netmask 0xfffff800 broadcast 172.16.7.255
	inet6 fe80::225:90ff:fee3:71f2%lagg0 prefixlen 64 scopeid 0x5
	inet 172.16.0.231 netmask 0xfffff800 broadcast 172.16.7.255 vhid 201
	inet 172.16.0.233 netmask 0xfffff800 broadcast 172.16.7.255 vhid 202
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	media: Ethernet autoselect
	status: active
	carp: MASTER vhid 201 advbase 1 advskew 1
	carp: BACKUP vhid 202 advbase 5 advskew 100
	laggproto loadbalance lagghash l2,l3,l4
	laggport: ix1 flags=4<ACTIVE>
	laggport: ix0 flags=4<ACTIVE>
vlan2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
	options=303<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 00:25:90:e3:71:f2
	inet 10.11.11.201 netmask 0xffffff00 broadcast 10.11.11.255
	inet6 fe80::225:90ff:fee3:71f2%vlan2 prefixlen 64 scopeid 0x6
	inet 10.11.12.203 netmask 0xffffff00 broadcast 10.11.12.255 vhid 12
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	media: Ethernet autoselect
	status: active
	vlan: 2 parent interface: lagg0
	carp: BACKUP vhid 12 advbase 1 advskew 100

//mxb
 
On 2 apr 2014, at 09:35, mxb <mxb at alumni.chalmers.se> wrote:

> 
> Moving this to freebsd-pf.
> 
> On 31 mar 2014, at 22:21, mxb <mxb at alumni.chalmers.se> wrote:
> 
>> 
>> Manually setting net.inet.carp.demotion brought BOTH VHIDs in desired state.
>> pfsync bulk update seems to not put everything back as it should.
>> 
>> lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
>> 	options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
>> 	ether 00:25:90:e3:71:f2
>> 	inet 172.16.0.234 netmask 0xfffff800 broadcast 172.16.7.255
>> 	inet6 fe80::225:90ff:fee3:71f2%lagg0 prefixlen 64 scopeid 0x5
>> 	inet 172.16.0.231 netmask 0xfffff800 broadcast 172.16.7.255 vhid 201
>> 	inet 172.16.0.233 netmask 0xfffff800 broadcast 172.16.7.255 vhid 202
>> 	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>> 	media: Ethernet autoselect
>> 	status: active
>> 	carp: MASTER vhid 201 advbase 1 advskew 1
>> 	carp: BACKUP vhid 202 advbase 5 advskew 100
>> 	laggproto lacp lagghash l2,l3,l4
>> 	laggport: ix1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>> 	laggport: ix0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>> 
>> 
>> On 31 mar 2014, at 20:42, mxb <mxb at alumni.chalmers.se> wrote:
>> 
>>> 
>>> Hi list,
>>> 
>>> hopefully this is the right place to have my question regarding CARP on 10-STABLE.
>>> 
>>> I have two nodes with following setup(node1):
>>> 
>>> lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
>>> 	options=8407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
>>> 	ether 00:25:90:e3:71:f2
>>> 	inet 172.16.0.234 netmask 0xfffff800 broadcast 172.16.7.255
>>> 	inet6 fe80::225:90ff:fee3:71f2%lagg0 prefixlen 64 scopeid 0x5
>>> 	inet 172.16.0.231 netmask 0xfffff800 broadcast 172.16.7.255 vhid 201
>>> 	inet 172.16.0.233 netmask 0xfffff800 broadcast 172.16.7.255 vhid 202
>>> 	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>> 	media: Ethernet autoselect
>>> 	status: active
>>> 	carp: BACKUP vhid 201 advbase 1 advskew 1
>>> 	carp: BACKUP vhid 202 advbase 5 advskew 100
>>> 	laggproto lacp lagghash l2,l3,l4
>>> 	laggport: ix1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>>> 	laggport: ix0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>>> 
>>> net.inet.carp.preempt=1 on both nodes. as well as PSYNC as this:
>>> 
>>> pfsync0: flags=41<UP,RUNNING> metric 0 mtu 1500
>>> 	pfsync: syncdev: vlan22 syncpeer: 10.22.22.2 maxupd: 128 defer: off
>>> 
>>> The problem is (if it is not clear from the ifconfig-output for the lagg0) the state of VHID 201.
>>> Node2 with advskew of 100 is currently MASTER, but it SHOULD NOT as of setup.
>>> 
>>> Am I hitting a bug or doing something wrong?
>>> 
>>> I also have noted that after the pfsync bulk update the demotion counter never setts to 0, but stays on 480,
>>> thus preventing node1 become a MASTER 201(?). Or is this a normal behavior?
>>> 
>>> Regards,
>>> mxb
>>> 
>>> 
>> 
> 



More information about the freebsd-pf mailing list