Hello,
This should be possible. I do have 7.2 systems which have lagg0 on em0/em1
VLANs over lagg0 and carp over those VLANs. So I guess carp over lagg0 should
no be a problem.
lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
ether 00:30:48:c8:2f:50
media: Ethernet autoselect
status: active
laggproto lacp
laggport: em1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
laggport: em0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
vlan4: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=3<RXCSUM,TXCSUM>
ether 00:30:48:c8:2f:50
inet 10.62.4.253 netmask 0xffffff00 broadcast 10.62.4.255
media: Ethernet autoselect
status: active
vlan: 4 parent interface: lagg0
carp4: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 10.62.4.1 netmask 0xffffff00
carp: MASTER vhid 4 advbase 1 advskew 0
On Aug 3, 2010, at 5:55 PM, Andrea Venturoli wrote:
> Hello.
>
> On a couple of 7.2 systems, I've got some carp interfaces build upon a
> physical interface (em0 or igb0) and everything works fine.
>
> On both box I've tried aggregating two interfaces (resp. em0+em1 and
> igb0+igb1) into a lagg0 interface, using LACP.
> However, in this case CARP will stop working as all carp devices which work
> over lagg0 will stay in INIT state.
>
> Is this a bug?
> Is "carp over lagg" possible at all?
>
> bye & Thanks
> av.
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "[email protected]"
--
Best Wishes,
Stefan Lambrev
ICQ# 24134177
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[email protected]"