Detailed statistics on em(4) driver

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Detailed statistics on em(4) driver

bernd-34
Hi,

I've got problems with increasing Ierrs on several machines with several
em(4) interfaces. Is there a way to get *detailed* information on these?

# netstat -I em3 -d
Name    Mtu   Network     Address              Ipkts Ierrs    Opkts
Oerrs Colls Drop
em3     1500  <Link>      de:ad:be:ef          95655063 435896 63427593  
    0     0    0
em3     1500  fe80::%em3/ fe80::xx:ff:ffe      95655063 435896 63427593  
    0     0    0

is not that verbose.

Thanks in advance,

Bernd

Reply | Threaded
Open this post in threaded view
|

Re: Detailed statistics on em(4) driver

bernd-34
> Hi,
>
> I've got problems with increasing Ierrs on several machines with
> several em(4) interfaces. Is there a way to get *detailed* information
> on these?
>
> # netstat -I em3 -d
> Name    Mtu   Network     Address              Ipkts Ierrs    Opkts
> Oerrs Colls Drop
> em3     1500  <Link>      de:ad:be:ef          95655063 435896
> 63427593     0     0    0
> em3     1500  fe80::%em3/ fe80::xx:ff:ffe      95655063 435896
> 63427593     0     0    0
>
> is not that verbose.

We hacked the kernel. The interface(s) just miss packets, see
screenshot:

http://imageshack.us/f/96/fkad.png/

Customer urged to move from OpenBSD to Ubuntu for BGP routing.

> Thanks in advance,
>
> Bernd

Reply | Threaded
Open this post in threaded view
|

Re: Detailed statistics on em(4) driver

Philip Guenther-2
On Wed, Jun 19, 2013 at 11:38 PM, Bernd <[hidden email]> wrote:

>> I've got problems with increasing Ierrs on several machines with
>> several em(4) interfaces. Is there a way to get *detailed* information
>> on these?
>>
>> # netstat -I em3 -d
>> Name    Mtu   Network     Address              Ipkts Ierrs    Opkts
>> Oerrs Colls Drop
>> em3     1500  <Link>      de:ad:be:ef          95655063 435896
>> 63427593     0     0    0
>> em3     1500  fe80::%em3/ fe80::xx:ff:ffe      95655063 435896
>> 63427593     0     0    0
>>
>> is not that verbose.
>
> We hacked the kernel. The interface(s) just miss packets, see screenshot:
>
> http://imageshack.us/f/96/fkad.png/

No dmesg (which would have included the output of your printfs, in
text form!), fail to describe your kernel hacks, and then you *upload
a picture of your console*?!?


> Customer urged to move from OpenBSD to Ubuntu for BGP routing.

Good luck with that!


Philip Guenther

Reply | Threaded
Open this post in threaded view
|

Re: Detailed statistics on em(4) driver

Otto Moerbeek
In reply to this post by bernd-34
On Thu, Jun 20, 2013 at 08:38:11AM +0200, Bernd wrote:

> >Hi,
> >
> >I've got problems with increasing Ierrs on several machines with
> >several em(4) interfaces. Is there a way to get *detailed* information
> >on these?
> >
> ># netstat -I em3 -d
> >Name    Mtu   Network     Address              Ipkts Ierrs    Opkts
> >Oerrs Colls Drop
> >em3     1500  <Link>      de:ad:be:ef          95655063 435896
> >63427593     0     0    0
> >em3     1500  fe80::%em3/ fe80::xx:ff:ffe      95655063 435896
> >63427593     0     0    0
> >
> >is not that verbose.
>
> We hacked the kernel. The interface(s) just miss packets, see
> screenshot:
>
> http://imageshack.us/f/96/fkad.png/
>
> Customer urged to move from OpenBSD to Ubuntu for BGP routing.
>
> >Thanks in advance,
> >
> >Bernd

What does

        sysctl net.inet.ip.ifq

say?

On a side note: you are not sharing *any* details, so expect your
emails to be ignored by most people here. And with good reason.

        -Otto

Reply | Threaded
Open this post in threaded view
|

Re: Detailed statistics on em(4) driver

Christiano F. Haesbaert
In reply to this post by bernd-34
On 20 June 2013 08:38, Bernd <[hidden email]> wrote:

>> Hi,
>>
>> I've got problems with increasing Ierrs on several machines with
>> several em(4) interfaces. Is there a way to get *detailed* information
>> on these?
>>
>> # netstat -I em3 -d
>> Name    Mtu   Network     Address              Ipkts Ierrs    Opkts
>> Oerrs Colls Drop
>> em3     1500  <Link>      de:ad:be:ef          95655063 435896
>> 63427593     0     0    0
>> em3     1500  fe80::%em3/ fe80::xx:ff:ffe      95655063 435896
>> 63427593     0     0    0
>>
>> is not that verbose.
>
>
> We hacked the kernel. The interface(s) just miss packets, see screenshot:
>
> http://imageshack.us/f/96/fkad.png/
>
> Customer urged to move from OpenBSD to Ubuntu for BGP routing.
>

Missed packets means the ring buffer is full and the card has to drop
the packet.
In other words, you're not fast enough.

Send a dmesg, and we need an idea of the packet rate you're pushing,
chances are you're hitting our stack limit.