Re: problem with link aggregation failover
On Sat, 12.09.2009 at 22:34:41 +0200, Maciej Jan Broniarz wrote: Hello, I am trying to configure lagg failover mode on 7.2. I do: # ifconfig xl0 up # ifconfig fxp0 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0 # dhclient lagg0 And all seems to work ok. Still I disconnect the cable from the master card the connection stops. Although fxp0 becomes active the connection is still dead. If I start pinging any host from that machine the conection comes back to live, but having ping in background all the time is not the solution. Am I doing something wrong or have I missed something in the configuration? Well, where is xl0 and fxp0 connected to? My first bet would be a standard switch, if so try setting both devices to the same MAC address. Otherwise the peers you connect to will send the IP packets to the wrong MAC address and only after a timeout (or a forced push thanks to the ping) will get their ARP cache into shape. Regards, Uli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with link aggregation failover
On Sun, 27 Sep 2009, Ulrich Sp??rlein wrote: On Sat, 12.09.2009 at 22:34:41 +0200, Maciej Jan Broniarz wrote: Hello, I am trying to configure lagg failover mode on 7.2. I do: # ifconfig xl0 up # ifconfig fxp0 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0 # dhclient lagg0 And all seems to work ok. Still I disconnect the cable from the master card the connection stops. Although fxp0 becomes active the connection is still dead. If I start pinging any host from that machine the conection comes back to live, but having ping in background all the time is not the solution. Am I doing something wrong or have I missed something in the configuration? Well, where is xl0 and fxp0 connected to? My first bet would be a standard switch, if so try setting both devices to the same MAC address. Otherwise the peers you connect to will send the IP packets to the wrong MAC address and only after a timeout (or a forced push thanks to the ping) will get their ARP cache into shape. lagg should automatically make xl0 and fxp0 appear at the same MAC address. The only time you should have to manually set the MAC address would be on cloned interfaces such as wlan, because the cloned interfaces don't propagate the MAC change down to the interface from which they were cloned. -- DE___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with link aggregation failover
On Sun, 27.09.2009 at 09:49:03 -0400, Daniel Eischen wrote: On Sun, 27 Sep 2009, Ulrich Spörlein wrote: On Sat, 12.09.2009 at 22:34:41 +0200, Maciej Jan Broniarz wrote: Hello, I am trying to configure lagg failover mode on 7.2. I do: # ifconfig xl0 up # ifconfig fxp0 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0 # dhclient lagg0 And all seems to work ok. Still I disconnect the cable from the master card the connection stops. Although fxp0 becomes active the connection is still dead. If I start pinging any host from that machine the conection comes back to live, but having ping in background all the time is not the solution. Am I doing something wrong or have I missed something in the configuration? Well, where is xl0 and fxp0 connected to? My first bet would be a standard switch, if so try setting both devices to the same MAC address. Otherwise the peers you connect to will send the IP packets to the wrong MAC address and only after a timeout (or a forced push thanks to the ping) will get their ARP cache into shape. lagg should automatically make xl0 and fxp0 appear at the same MAC address. The only time you should have to manually set the MAC address would be on cloned interfaces such as wlan, because the cloned interfaces don't propagate the MAC change down to the interface from which they were cloned. Interesting, thanks for the hint. I only use it for LAN/WLAN failover, so that's why I have to do this anyway. Regards, Uli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with link aggregation failover
On 2009-Sep-13 12:11:45 +0200, Maciej Jan Broniarz gau...@gausus.net wrote: I have configured the same mac on both cards. This should be done automatically by lagg. When I disconnect the cable from xl0, the network connection dies, and my lagg0 looks like this: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9RXCSUM,VLAN_MTU ether 00:01:02:20:24:ef inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect status: active laggproto failover laggport: fxp0 flags=4ACTIVE laggport: xl0 flags=1MASTER What might be the problem with that setup? Both sides of a lagg need to co-operate to pass packets. You need to configure the switch to failover as well. -- Peter Jeremy pgpMQ4Rr2dl4y.pgp Description: PGP signature
Re: problem with link aggregation failover
Hello, What might be the problem with that setup? Both sides of a lagg need to co-operate to pass packets. You need to configure the switch to failover as well. A simple LACP configuration should do? mjb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with link aggregation failover
On 2009-Sep-15 09:50:49 +0200, Maciej Jan Broniarz gau...@gausus.net wrote: What might be the problem with that setup? Both sides of a lagg need to co-operate to pass packets. You need to configure the switch to failover as well. A simple LACP configuration should do? Yes. I use LACP at $work. See lagg(4) for other options. -- Peter Jeremy pgpuoDPA53s7j.pgp Description: PGP signature
Re: problem with link aggregation failover
Hello, xl0 and fxp0 both need to have the same mac address I have configured the same mac on both cards. My lagg0 looks like this: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9RXCSUM,VLAN_MTU ether 00:01:02:20:24:ef inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect status: active laggproto failover laggport: fxp0 flags=0 laggport: xl0 flags=5MASTER,ACTIVE When I disconnect the cable from xl0, the network connection dies, and my lagg0 looks like this: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9RXCSUM,VLAN_MTU ether 00:01:02:20:24:ef inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect status: active laggproto failover laggport: fxp0 flags=4ACTIVE laggport: xl0 flags=1MASTER Still, if I start pinging anything from that host, the connections comes back to live: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9RXCSUM,VLAN_MTU ether 00:01:02:20:24:ef inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect status: active laggproto failover laggport: fxp0 flags=4ACTIVE laggport: xl0 flags=1MASTER What might be the problem with that setup? Thanks for your help, mjb On Sat, Sep 12, 2009 at 1:34 PM, Maciej Jan Broniarz gau...@gausus.net wrote: Hello, I am trying to configure lagg failover mode on 7.2. I do: # ifconfig xl0 up # ifconfig fxp0 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0 # dhclient lagg0 And all seems to work ok. Still I disconnect the cable from the master card the connection stops. Although fxp0 becomes active the connection is still dead. If I start pinging any host from that machine the conection comes back to live, but having ping in background all the time is not the solution. Am I doing something wrong or have I missed something in the configuration? Best regards, mjb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- And what is good, Phaedrus, And what is not good— Need we ask anyone to tell us these things? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
problem with link aggregation failover
Hello, I am trying to configure lagg failover mode on 7.2. I do: # ifconfig xl0 up # ifconfig fxp0 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0 # dhclient lagg0 And all seems to work ok. Still I disconnect the cable from the master card the connection stops. Although fxp0 becomes active the connection is still dead. If I start pinging any host from that machine the conection comes back to live, but having ping in background all the time is not the solution. Am I doing something wrong or have I missed something in the configuration? Best regards, mjb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
