@Brian Bennett
Some more information:
$dladm show-aggr -x
LINK PORT SPEED DUPLEX STATE ADDRESS PORTSTATE
aggr0 -- 1000Mb full up 44:a8:42:34:87:63 --
bge0 1000Mb full up 44:a8:42:34:87:63 attached
bge1 1000Mb full up 44:a8:42:34:87:64 attached
$dladm show-aggr
LINK POLICY ADDRPOLICY LACPACTIVITY LACPTIMER FLAGS
aggr0 L4 auto active short -----
$dladm show-link
LINK CLASS MTU STATE BRIDGE OVER
bge0 phys 1500 up -- --
bge1 phys 1500 up -- --
aggr0 aggr 1500 up -- bge0 bge1
@ Robert Mustacchi
Shure, we can dig a litt more into that. If i run snoop against bge0 interface,
nothing changes and i am still unable to ping the other host in my subnet:
###
$snoop -d bge0
$ping 192.168.234.20
no answer from 192.168.234.20
###
If i run snoop on the bge1 interface i'm able to ping:
###
$snoop -d bge1
$ping 192.168.234.20
192.168.234.20 is alive
###
Some further testing showed that the ICMP request leaves the host via the bge0
interface but returns via bge1:
###
$snoop -d bge0 |grep ICMP
Using device bge0 (promiscuous mode)
hostname -> 192.168.234.20 ICMP Echo request (ID: 6326 Sequence number: 0)
$snoop -d bge1 |grep ICMP
Using device bge1 (promiscuous mode)
192.168.234.20 -> hostname ICMP Echo reply (ID: 6326 Sequence number: 0)
###
Normally it should return on the same interface it was sent from (which is the
case if i try to ping the gateway):
###
$snoop -d bge0 |grep ICMP
Using device bge0 (promiscuous mode)
hostname -> 192.168.234.1 ICMP Echo request (ID: 6337 Sequence number: 0)
192.168.234.1 -> hostname ICMP Echo reply (ID: 6337 Sequence number: 0)
###
So the problem only occurs on some IPs, not on all:
ping 192.168.234.1 (gateway) works
ping 192.168.235.16 (other smartos host) works
ping 192.168.234.20 (other smartos host) doesn't work
Greets
Kilian
_____________________________________
__
Von: Robert Mustacchi <[email protected]>
Gesendet: Freitag, 8. April 2016 16:55
An: [email protected]
Betreff: Re: AW: [smartos-discuss] Link Aggregation Problem
On 4/8/16 7:50 , Kilian Ries wrote:
> Hi Robert,
>
> seems like a driver problem to me... Found some other users in the illumos
> forum which have problems with that chipset.
>
>
> dladm show-aggr -x
> LINK PORT SPEED DUPLEX STATE ADDRESS
> PORTSTATE
> aggr0 -- 1000Mb full up 44:a8:42:34:87:63 --
> bge0 1000Mb full up 44:a8:42:34:87:63
> attached
> bge1 1000Mb full up 44:a8:42:34:87:64
> attached
>
>
> The strange thing is:
>
> While i'm running "snoop -d aggr0" i am able to ping every other host in the
> subnet and the outgoing mac-address seems to be right. When i'm canceling
> snoop, the failure is back again and i can only ping some host in the subnet.
Rather than run snoop on the aggr, what happens if you run it on the
individual bge devices? Otherwise from your switch, which device is it
that we're seeing the wrong mac on? I'd presume it's on bge1. From the
switch is there any pattern to the traffic with the incorrect mac address?
> I think i'm going to put another network-card into the host ...
If possible, could we do a bit more debugging before you do that?
Otherwise I'm afraid we'll never get to the root cause here.
Robert
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
