bsnmpd & 64bits counters problem

Andrew Thompson thompsa at FreeBSD.org
Tue Dec 16 10:46:20 PST 2008


On Tue, Dec 16, 2008 at 07:12:24PM +0100, Harti Brandt wrote:
> On Tue, 16 Dec 2008, Sergey Matveychuk wrote:
> SM>> 
> SM>> The highspeed counters are only there if this is a high-speed interface.
> SM>> High speed means that the baudrate in the interface MIB (the one in the
> SM>> kernel) must be larger than 20Mbaud.
> SM>
> SM>Well, these is lagg interfaces:
> SM>lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
> SM>        options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
> SM>        ether 00:30:48:67:d4:68
> SM>        media: Ethernet autoselect
> SM>        status: active
> SM>        laggproto lacp
> SM>        laggport: em2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
> SM>        laggport: em0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
> SM>
> SM>There is no baudrate on them. But they are really high-speed however.
> 
> All interfaces have a baudrate. Its in net/if.h ifi_baudrate. We had the 
> problem in the past with other interface types. 'virtual' interfaces must 
> take care to somehow propagate the rate of the underlying physical 
> interfaces up to the virtual one.

This patch should fix it for the lacp case. What is the correct value to
use for a collection of interfaces with possibly different speeds?
highest/lowest?


Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ieee8023ad_lacp.diff
Type: text/x-diff
Size: 731 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20081216/1cc89a2b/ieee8023ad_lacp.bin


More information about the freebsd-net mailing list