Re: Issues with ixl(4)

[Dustin Marquess]

So I've done some more testing, and it's definitely some kind of
interaction between ixl & lagg, and maybe even ix & lagg.

It doesn't matter if lagg is using "lacp" or "loadbalance" (with the
switch set appropriately), it happens on both.  I did find out that
statically adding an arp entry for the "bad hosts" fixes it, so it's
something to do with ARP replies (tcpdump doesn't show it getting the
ARP replies all of the time in the lagg).  Pretty much exactly this
problem:

https://lists.freebsd.org/pipermail/freebsd-net/2015-June/042593.html

Except that fix is already in the code.

I going all the way back to r294499 of -CURRENT and that didn't change
it.  I also tried 10.3, but that immediately panics on the Intel-based
ixl machine.  I'll see if I can get the AMD-based ix machine to boot
10.3 for testing.

-Dustin

On Thu, Apr 21, 2016 at 4:52 PM, K. Macy  wrote:
>
>
> On Wednesday, April 20, 2016, Dustin Marquess  wrote:
>>
>> I tried backing out that change and everything worked for a few minutes
>> and then started acting up again.  Then I notice Sean Bruno's "TCP Packets
>> Drop!!!" email about LACP.  I disabled LACP on the switch side and then
>> changed the lagg config from "lacp" to "roundrobin", and so far so good.  On
>> the switch side it looks like member ports were randomly bounding in the
>> LACP bundle, and when I'd tcpdump an interface I wouldn't see anything until
>> another LACP packet came in.
>>
>> So something seems to be broken with lagg's LACP support recently.  The
>> good news is I don't think the route caching is causing this problem.  I'll
>> put it back in and retest to make sure though.
>>
>
>
> Glad to hear I was in error.
> -M
>
>>
>> Thanks for the help!
>> -Dustin
>>
>> On Tue, Apr 19, 2016 at 6:15 PM, K. Macy  wrote:
>>>
>>> On Mon, Apr 18, 2016 at 10:45 PM, Eggert, Lars  wrote:
>>> > I haven't played with lagg+vlan+bridge, but I briefly evaluated XL710
>>> > boards last year
>>> > (https://lists.freebsd.org/pipermail/freebsd-net/2015-October/043584.html)
>>> > and saw very poor throughputs and latencies even in very simple setups. As
>>> > far as I could figure it out, TSO/LRO wasn't being performed (although
>>> > enabled) and so I ran into packet-rate issues.
>>> >
>>> > I basically gave up and went with a different vendor. FWIW, the XL710
>>> > boards in the same machines booted into Linux performed fine.
>>> >
>>>
>>> FWIW, NFLX sees performance close to that of cxgbe (by far the best
>>> maintained, best performing FreeBSD 40G driver) with an iflib
>>> converted driver. The iflib updated driver will be imported by 11 but
>>> won't become the default driver until 11.1 for wont of QA resources at
>>> Intel.
>>>
>>> -M
>>
>>
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Issues with ixl(4)

[K. Macy]

On Wednesday, April 20, 2016, Dustin Marquess  wrote:

> I tried backing out that change and everything worked for a few minutes
> and then started acting up again.  Then I notice Sean Bruno's "TCP Packets
> Drop!!!" email about LACP.  I disabled LACP on the switch side and then
> changed the lagg config from "lacp" to "roundrobin", and so far so good.
> On the switch side it looks like member ports were randomly bounding in the
> LACP bundle, and when I'd tcpdump an interface I wouldn't see anything
> until another LACP packet came in.
>
> So something seems to be broken with lagg's LACP support recently.  The
> good news is I don't think the route caching is causing this problem.  I'll
> put it back in and retest to make sure though.
>
>

Glad to hear I was in error.
-M


> Thanks for the help!
> -Dustin
>
> On Tue, Apr 19, 2016 at 6:15 PM, K. Macy  > wrote:
>
>> On Mon, Apr 18, 2016 at 10:45 PM, Eggert, Lars > > wrote:
>> > I haven't played with lagg+vlan+bridge, but I briefly evaluated XL710
>> boards last year (
>> https://lists.freebsd.org/pipermail/freebsd-net/2015-October/043584.html)
>> and saw very poor throughputs and latencies even in very simple setups. As
>> far as I could figure it out, TSO/LRO wasn't being performed (although
>> enabled) and so I ran into packet-rate issues.
>> >
>> > I basically gave up and went with a different vendor. FWIW, the XL710
>> boards in the same machines booted into Linux performed fine.
>> >
>>
>> FWIW, NFLX sees performance close to that of cxgbe (by far the best
>> maintained, best performing FreeBSD 40G driver) with an iflib
>> converted driver. The iflib updated driver will be imported by 11 but
>> won't become the default driver until 11.1 for wont of QA resources at
>> Intel.
>>
>> -M
>>
>
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Issues with ixl(4)

[Dustin Marquess]

I tried backing out that change and everything worked for a few minutes and
then started acting up again.  Then I notice Sean Bruno's "TCP Packets
Drop!!!" email about LACP.  I disabled LACP on the switch side and then
changed the lagg config from "lacp" to "roundrobin", and so far so good.
On the switch side it looks like member ports were randomly bounding in the
LACP bundle, and when I'd tcpdump an interface I wouldn't see anything
until another LACP packet came in.

So something seems to be broken with lagg's LACP support recently.  The
good news is I don't think the route caching is causing this problem.  I'll
put it back in and retest to make sure though.

Thanks for the help!
-Dustin

On Tue, Apr 19, 2016 at 6:15 PM, K. Macy  wrote:

> On Mon, Apr 18, 2016 at 10:45 PM, Eggert, Lars  wrote:
> > I haven't played with lagg+vlan+bridge, but I briefly evaluated XL710
> boards last year (
> https://lists.freebsd.org/pipermail/freebsd-net/2015-October/043584.html)
> and saw very poor throughputs and latencies even in very simple setups. As
> far as I could figure it out, TSO/LRO wasn't being performed (although
> enabled) and so I ran into packet-rate issues.
> >
> > I basically gave up and went with a different vendor. FWIW, the XL710
> boards in the same machines booted into Linux performed fine.
> >
>
> FWIW, NFLX sees performance close to that of cxgbe (by far the best
> maintained, best performing FreeBSD 40G driver) with an iflib
> converted driver. The iflib updated driver will be imported by 11 but
> won't become the default driver until 11.1 for wont of QA resources at
> Intel.
>
> -M
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Issues with ixl(4)

[Eggert, Lars]

On 2016-04-20, at 1:15, K. Macy  wrote:
> FWIW, NFLX sees performance close to that of cxgbe (by far the best
> maintained, best performing FreeBSD 40G driver) with an iflib
> converted driver. The iflib updated driver will be imported by 11 but
> won't become the default driver until 11.1 for wont of QA resources at
> Intel.

Nice! I still have the cards, so will be sure to test.

Lars


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: aliases & netmasks, WAS: Issues with ixl(4)

[K. Macy]

On Tue, Apr 19, 2016 at 2:52 PM, Dustin Marquess <dmarqu...@gmail.com> wrote:
> Okay, interestingly, I just updated the AMD machine (the ix one) to the
> latest version of -CURRENT last night, and now it's acting strangeish
> also.  So maybe it's not ixl(4) afterall.
>
> What's obviously "broken" is that the config that is supposed to work:
>
> ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
> ifconfig_bridge0_aliases="inet 192.168.1.11/32"
>
> The alias doesn't work from outside that subnet at least.  However the
> config that shouldn't work:
>
> ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
> ifconfig_bridge0_aliases="inet 192.168.1.11/24"
>
> Does.  Eg, changing the subnet mask on the alias from /32 (which the docs
> say it should be) to /24 (which the docs say it shouldn't be), seems to
> "fix" it.  Although I did seem to lose SSH connectivity to the main IP
> sometime after this change.  I have a bad feeling that changing the network
> mask on the alias is causing other issues.
>
> Was there some recent change in -CURRENT that would have caused this?


Try disabling inpcb route caching.I was afraid that this would happen.

-M

>
> Thanks!
> -Dustin
>
> On Mon, Apr 18, 2016 at 11:06 PM, Dustin Marquess <dmarqu...@gmail.com>
> wrote:
>
>> I'm having some strange issues with ixl(4) and a X710-DA4 card in a
>> new-ish Intel-based server.  I'm pretty much replicating an existing setup
>> from an older AMD machine that used 2 x X520-DA2 cards and ixgbe(4).  This
>> is all on -CURRENT.
>>
>> It's meant to be a bhyve server, so the 4x10GE ports are put into a
>> LACP-based lagg(4), then vlan(4) interfaces are bound to the lagg, and then
>> if_bridge(4) interfaces are created to bind the vlan and tap interfaces
>> together.
>>
>> The X710-DA4 is running the latest NVM from Intel (5.02):
>>
>> dev.ixl.3.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
>> dev.ixl.2.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
>> dev.ixl.1.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
>> dev.ixl.0.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
>>
>> I've tried both the ixl driver that comes with -CURRENT (1.4.3?) and the
>> 1.4.27 driver from Intel and am having the same problem.  The problem is
>> this exactly (sorry it's taken me so long to get to it!):
>>
>> Using just one interface, one interface + VLANs, the lagg without VLANs,
>> etc, everything works perfectly fine.  As soon as I combine
>> lagg+vlan+bridge, all hell breaks loose.  One machine can ping one alias on
>> the server but not the other while other machines can.  The server itself
>> can't ping the DNS server nor the default route, but can ping things
>> through the default route, etc.  The behavior is very unpredictable.  ssh
>> can take a few times to get in, and then once it, "svn update" will work
>> for a few seconds and then bomb out, etc.
>>
>> He is the working config from the X520-DA2 system:
>>
>> ifconfig_ix0="-lro -tso -txcsum up"
>> ifconfig_ix1="-lro -tso -txcsum up"
>> ifconfig_ix2="-lro -tso -txcsum up"
>> ifconfig_ix3="-lro -tso -txcsum up"
>> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
>> ifconfig_lagg0="laggproto lacp laggport ix0 laggport ix1 laggport ix2
>> laggport ix3"
>> ifconfig_vlan1="vlan 1 vlandev lagg0"
>> ifconfig_vlan2="vlan 2 vlandev lagg0"
>> ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
>> ifconfig_bridge1="addm vlan2 addm tap1"
>> defaultrouter="192.168.1.1"
>>
>> Here is the "broken" config from the X710-DA4 system:
>>
>> ifconfig_ixl0="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
>> -vlanhwtso -vlanhwcsum up"
>> ifconfig_ixl1="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
>> -vlanhwtso -vlanhwcsum up"
>> ifconfig_ixl2="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
>> -vlanhwtso -vlanhwcsum up"
>> ifconfig_ixl3="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
>> -vlanhwtso -vlanhwcsum up"
>> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
>> ifconfig_lagg0="laggproto lacp laggport ixl0 laggport ixl1 laggport ixl2
>> laggport ixl3"
>> ifconfig_vlan1="vlan 1 vlandev lagg0"
>> ifconfig_vlan2="vlan 2 vlandev lagg0"
>> ifconfig_bridge0="inet 192.168.1.101/24 addm vlan1 a

Re: aliases & netmasks, WAS: Issues with ixl(4)

[Dustin Marquess]

Okay, interestingly, I just updated the AMD machine (the ix one) to the
latest version of -CURRENT last night, and now it's acting strangeish
also.  So maybe it's not ixl(4) afterall.

What's obviously "broken" is that the config that is supposed to work:

ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
ifconfig_bridge0_aliases="inet 192.168.1.11/32"

The alias doesn't work from outside that subnet at least.  However the
config that shouldn't work:

ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
ifconfig_bridge0_aliases="inet 192.168.1.11/24"

Does.  Eg, changing the subnet mask on the alias from /32 (which the docs
say it should be) to /24 (which the docs say it shouldn't be), seems to
"fix" it.  Although I did seem to lose SSH connectivity to the main IP
sometime after this change.  I have a bad feeling that changing the network
mask on the alias is causing other issues.

Was there some recent change in -CURRENT that would have caused this?

Thanks!
-Dustin

On Mon, Apr 18, 2016 at 11:06 PM, Dustin Marquess <dmarqu...@gmail.com>
wrote:

> I'm having some strange issues with ixl(4) and a X710-DA4 card in a
> new-ish Intel-based server.  I'm pretty much replicating an existing setup
> from an older AMD machine that used 2 x X520-DA2 cards and ixgbe(4).  This
> is all on -CURRENT.
>
> It's meant to be a bhyve server, so the 4x10GE ports are put into a
> LACP-based lagg(4), then vlan(4) interfaces are bound to the lagg, and then
> if_bridge(4) interfaces are created to bind the vlan and tap interfaces
> together.
>
> The X710-DA4 is running the latest NVM from Intel (5.02):
>
> dev.ixl.3.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> dev.ixl.2.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> dev.ixl.1.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> dev.ixl.0.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
>
> I've tried both the ixl driver that comes with -CURRENT (1.4.3?) and the
> 1.4.27 driver from Intel and am having the same problem.  The problem is
> this exactly (sorry it's taken me so long to get to it!):
>
> Using just one interface, one interface + VLANs, the lagg without VLANs,
> etc, everything works perfectly fine.  As soon as I combine
> lagg+vlan+bridge, all hell breaks loose.  One machine can ping one alias on
> the server but not the other while other machines can.  The server itself
> can't ping the DNS server nor the default route, but can ping things
> through the default route, etc.  The behavior is very unpredictable.  ssh
> can take a few times to get in, and then once it, "svn update" will work
> for a few seconds and then bomb out, etc.
>
> He is the working config from the X520-DA2 system:
>
> ifconfig_ix0="-lro -tso -txcsum up"
> ifconfig_ix1="-lro -tso -txcsum up"
> ifconfig_ix2="-lro -tso -txcsum up"
> ifconfig_ix3="-lro -tso -txcsum up"
> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
> ifconfig_lagg0="laggproto lacp laggport ix0 laggport ix1 laggport ix2
> laggport ix3"
> ifconfig_vlan1="vlan 1 vlandev lagg0"
> ifconfig_vlan2="vlan 2 vlandev lagg0"
> ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
> ifconfig_bridge1="addm vlan2 addm tap1"
> defaultrouter="192.168.1.1"
>
> Here is the "broken" config from the X710-DA4 system:
>
> ifconfig_ixl0="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> ifconfig_ixl1="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> ifconfig_ixl2="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> ifconfig_ixl3="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
> ifconfig_lagg0="laggproto lacp laggport ixl0 laggport ixl1 laggport ixl2
> laggport ixl3"
> ifconfig_vlan1="vlan 1 vlandev lagg0"
> ifconfig_vlan2="vlan 2 vlandev lagg0"
> ifconfig_bridge0="inet 192.168.1.101/24 addm vlan1 addm tap0"
> ifconfig_bridge1="addm vlan2 addm tap1"
> defaultrouter="192.168.1.1"
>
> I've changed the various flags in the ifconfig_ixl# lines without any
> obvious differences.  Both machines are connected to the same HPe 5820X
> switch with the same exact config, so I don't believe it's a switch issue.
>
> Any ideas? Has anybody seen something like this before?
>
> Thanks!
> -Dustin
>
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Issues with ixl(4)

[Eggert, Lars]

I haven't played with lagg+vlan+bridge, but I briefly evaluated XL710 boards 
last year 
(https://lists.freebsd.org/pipermail/freebsd-net/2015-October/043584.html) and 
saw very poor throughputs and latencies even in very simple setups. As far as I 
could figure it out, TSO/LRO wasn't being performed (although enabled) and so I 
ran into packet-rate issues.

I basically gave up and went with a different vendor. FWIW, the XL710 boards in 
the same machines booted into Linux performed fine.

Lars

> On 2016-04-19, at 6:06, Dustin Marquess <dmarqu...@gmail.com> wrote:
> 
> I'm having some strange issues with ixl(4) and a X710-DA4 card in a new-ish
> Intel-based server.  I'm pretty much replicating an existing setup from an
> older AMD machine that used 2 x X520-DA2 cards and ixgbe(4).  This is all
> on -CURRENT.
> 
> It's meant to be a bhyve server, so the 4x10GE ports are put into a
> LACP-based lagg(4), then vlan(4) interfaces are bound to the lagg, and then
> if_bridge(4) interfaces are created to bind the vlan and tap interfaces
> together.
> 
> The X710-DA4 is running the latest NVM from Intel (5.02):
> 
> dev.ixl.3.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> dev.ixl.2.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> dev.ixl.1.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> dev.ixl.0.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
> 
> I've tried both the ixl driver that comes with -CURRENT (1.4.3?) and the
> 1.4.27 driver from Intel and am having the same problem.  The problem is
> this exactly (sorry it's taken me so long to get to it!):
> 
> Using just one interface, one interface + VLANs, the lagg without VLANs,
> etc, everything works perfectly fine.  As soon as I combine
> lagg+vlan+bridge, all hell breaks loose.  One machine can ping one alias on
> the server but not the other while other machines can.  The server itself
> can't ping the DNS server nor the default route, but can ping things
> through the default route, etc.  The behavior is very unpredictable.  ssh
> can take a few times to get in, and then once it, "svn update" will work
> for a few seconds and then bomb out, etc.
> 
> He is the working config from the X520-DA2 system:
> 
> ifconfig_ix0="-lro -tso -txcsum up"
> ifconfig_ix1="-lro -tso -txcsum up"
> ifconfig_ix2="-lro -tso -txcsum up"
> ifconfig_ix3="-lro -tso -txcsum up"
> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
> ifconfig_lagg0="laggproto lacp laggport ix0 laggport ix1 laggport ix2
> laggport ix3"
> ifconfig_vlan1="vlan 1 vlandev lagg0"
> ifconfig_vlan2="vlan 2 vlandev lagg0"
> ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
> ifconfig_bridge1="addm vlan2 addm tap1"
> defaultrouter="192.168.1.1"
> 
> Here is the "broken" config from the X710-DA4 system:
> 
> ifconfig_ixl0="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> ifconfig_ixl1="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> ifconfig_ixl2="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> ifconfig_ixl3="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
> -vlanhwtso -vlanhwcsum up"
> cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
> ifconfig_lagg0="laggproto lacp laggport ixl0 laggport ixl1 laggport ixl2
> laggport ixl3"
> ifconfig_vlan1="vlan 1 vlandev lagg0"
> ifconfig_vlan2="vlan 2 vlandev lagg0"
> ifconfig_bridge0="inet 192.168.1.101/24 addm vlan1 addm tap0"
> ifconfig_bridge1="addm vlan2 addm tap1"
> defaultrouter="192.168.1.1"
> 
> I've changed the various flags in the ifconfig_ixl# lines without any
> obvious differences.  Both machines are connected to the same HPe 5820X
> switch with the same exact config, so I don't believe it's a switch issue.
> 
> Any ideas? Has anybody seen something like this before?
> 
> Thanks!
> -Dustin
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"



signature.asc
Description: Message signed with OpenPGP using GPGMail

Issues with ixl(4)

[Dustin Marquess]

I'm having some strange issues with ixl(4) and a X710-DA4 card in a new-ish
Intel-based server.  I'm pretty much replicating an existing setup from an
older AMD machine that used 2 x X520-DA2 cards and ixgbe(4).  This is all
on -CURRENT.

It's meant to be a bhyve server, so the 4x10GE ports are put into a
LACP-based lagg(4), then vlan(4) interfaces are bound to the lagg, and then
if_bridge(4) interfaces are created to bind the vlan and tap interfaces
together.

The X710-DA4 is running the latest NVM from Intel (5.02):

dev.ixl.3.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
dev.ixl.2.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
dev.ixl.1.fw_version: nvm 5.02 etid 80002284 oem 0.0.0
dev.ixl.0.fw_version: nvm 5.02 etid 80002284 oem 0.0.0

I've tried both the ixl driver that comes with -CURRENT (1.4.3?) and the
1.4.27 driver from Intel and am having the same problem.  The problem is
this exactly (sorry it's taken me so long to get to it!):

Using just one interface, one interface + VLANs, the lagg without VLANs,
etc, everything works perfectly fine.  As soon as I combine
lagg+vlan+bridge, all hell breaks loose.  One machine can ping one alias on
the server but not the other while other machines can.  The server itself
can't ping the DNS server nor the default route, but can ping things
through the default route, etc.  The behavior is very unpredictable.  ssh
can take a few times to get in, and then once it, "svn update" will work
for a few seconds and then bomb out, etc.

He is the working config from the X520-DA2 system:

ifconfig_ix0="-lro -tso -txcsum up"
ifconfig_ix1="-lro -tso -txcsum up"
ifconfig_ix2="-lro -tso -txcsum up"
ifconfig_ix3="-lro -tso -txcsum up"
cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
ifconfig_lagg0="laggproto lacp laggport ix0 laggport ix1 laggport ix2
laggport ix3"
ifconfig_vlan1="vlan 1 vlandev lagg0"
ifconfig_vlan2="vlan 2 vlandev lagg0"
ifconfig_bridge0="inet 192.168.1.100/24 addm vlan1 addm tap0"
ifconfig_bridge1="addm vlan2 addm tap1"
defaultrouter="192.168.1.1"

Here is the "broken" config from the X710-DA4 system:

ifconfig_ixl0="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
-vlanhwtso -vlanhwcsum up"
ifconfig_ixl1="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
-vlanhwtso -vlanhwcsum up"
ifconfig_ixl2="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
-vlanhwtso -vlanhwcsum up"
ifconfig_ixl3="-rxcsum -txcsum -lro -tso -vlanmtu -vlanhwtag -vlanhwfilter
-vlanhwtso -vlanhwcsum up"
cloned_interfaces="lagg0 tap0 tap1 bridge0 bridge1 vlan1 vlan2"
ifconfig_lagg0="laggproto lacp laggport ixl0 laggport ixl1 laggport ixl2
laggport ixl3"
ifconfig_vlan1="vlan 1 vlandev lagg0"
ifconfig_vlan2="vlan 2 vlandev lagg0"
ifconfig_bridge0="inet 192.168.1.101/24 addm vlan1 addm tap0"
ifconfig_bridge1="addm vlan2 addm tap1"
defaultrouter="192.168.1.1"

I've changed the various flags in the ifconfig_ixl# lines without any
obvious differences.  Both machines are connected to the same HPe 5820X
switch with the same exact config, so I don't believe it's a switch issue.

Any ideas? Has anybody seen something like this before?

Thanks!
-Dustin
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"