Jason Brooks
Dabbler
- Joined
- Jul 16, 2013
- Messages
- 23
Hello,
I have been playing with the ability to have redundant interfaces, but ran into a problem.
The output of ifconfig shows LAGG0 having em0 and em1 as members. when I add the second vlan (vlan999) and it's ip address, ifconfig's output for vlan100 changes: vlan: 100 goes to vlan:0 and Parent interface goes from lagg0 to <none>.
This also happens if I use interfaces em1 and bce1.
So I ran some tests to see if I was configuring link aggregation and vlans correctly:
First I tried just setting up two ethernet interfaces with link aggregation (failover mode) with success.
Setup em0
FreeBSD 9.3-RELEASE-p28 amd64
running on an HP Proliant DL360G5.
Is this a bug, or am I doing it wrong?
I have been playing with the ability to have redundant interfaces, but ran into a problem.
- build link aggregation (failover mode) of em0 and em1 -> LAGG0
- build vlans(100,999) using parent interface of LAGG0
- assign ip addresses to vlan interfaces
The output of ifconfig shows LAGG0 having em0 and em1 as members. when I add the second vlan (vlan999) and it's ip address, ifconfig's output for vlan100 changes: vlan: 100 goes to vlan:0 and Parent interface goes from lagg0 to <none>.
Code:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:15:17:cb:8a:30 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: no carrier em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:15:17:cb:8a:31 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex>) status: active bce0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE> ether 00:21:5a:af:77:00 inet 192.168.1.28 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex>) status: active bce1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=c01bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE> ether 00:15:17:cb:8a:31 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex>) status: active vlan100: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=103<RXCSUM,TXCSUM,TSO4> ether 00:00:00:00:00:00 inet 10.37.50.29 netmask 0xffffff00 broadcast 10.37.50.255 nd6 options=9<PERFORMNUD,IFDISABLED> vlan: 0 parent interface: <none> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO> ether 00:15:17:cb:8a:31 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: active laggproto failover lagghash l2,l3,l4 laggport: bce1 flags=0<> laggport: em1 flags=5<MASTER,ACTIVE> vlan999: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=103<RXCSUM,TXCSUM,TSO4> ether 00:15:17:cb:8a:31 inet 192.168.3.29 netmask 0xffffff00 broadcast 192.168.3.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: active vlan: 999 parent interface: lagg0
This also happens if I use interfaces em1 and bce1.
So I ran some tests to see if I was configuring link aggregation and vlans correctly:
First I tried just setting up two ethernet interfaces with link aggregation (failover mode) with success.
- setup lagg0 with em0 and em1 as members
- tested failover worked...
Setup em0
- added vlan100 (interface ip: 10.37.50.29/24)
- added vlan999 (interface ip: 192.168.3.29/24)
- pinging ip addresses on the lans works.
FreeBSD 9.3-RELEASE-p28 amd64
running on an HP Proliant DL360G5.
Is this a bug, or am I doing it wrong?