Thank you I'll try testing it on FreeBSD / NetBSD / OpenBSD when I have
a moment.

The Dell - RHEL - Broadcom/Intel crew have something similar to bonding
called "NIC Team"; but I'm pretty sure its proprietary (not 802.3ad)

http://www.dell.com/content/topics/global.aspx/power/en/ps1q03_bhutani?c=us&cs=555&l=en&s=biz

BASP and Intel ANS; I'm not sure if either of those create a logical
layer 2 interface...

~BAS

On Fri, 2007-05-04 at 13:21 +0200, Jan Safranek wrote:
> I have submitted patch #1712645, which prints something more useful and 
> prints it only once.
> 
> Jan
> 
> On Fri, 2007-05-04 at 09:53 +0200, Jan Safranek wrote:
> > [I am sorry for not sending cc: to the list]
> > 
> > On Thu, 2007-05-03 at 10:44 -0400, Brian A. Seklecki wrote:
> > > I've never used the bonding feature in RHEL described here; but I've
> > > used Cisco IOS EthernetChannel, FreeBSD Netgraph, OpenBSD trunk(4); --
> > > all 802.3ad + LACP compliant.
> > > 
> > > They all use underlying physical interfaces in IPv4-less mode; while
> > > assigning IPv4 to the new logical a
> > > ddress.
> > > 
> > > You're saying that is not the case with this implementation?
> > > 
> > > ~BAS
> > 
> > It looks like your configuration: physical NICs do not have IP, the
> > virtual bonding does:
> > 
> > $ ifconfig
> > 
> > bond0     Link encap:Ethernet  HWaddr 00:0C:29:76:C2:C2  
> >           inet addr:192.168.2.104  Bcast:192.168.2.255 
> >           inet6 addr: fe80::20c:29ff:fe76:c2c2/64 Scope:Link
> > ...
> > eth1      Link encap:Ethernet  HWaddr 00:0C:29:76:C2:C2  
> >           inet6 addr: fe80::20c:29ff:fe76:c2c2/64 Scope:Link
> > ...
> > eth2      Link encap:Ethernet  HWaddr 00:0C:29:76:C2:CC  
> >           inet6 addr: fe80::20c:29ff:fe76:c2c2/64 Scope:Link
> > ...
> > 
> > And the log is full of 
> > error on subcontainer 'ia_addr' insert (-1) 
> > error on subcontainer 'ia_addr' insert (-1) 
> > 
> > Jan
> > 
> > > On Thu, 2007-05-03 at 09:53 +0200, Jan Safranek wrote:
> > > > On Mon, 2007-04-30 at 14:12 -0400, Brian A. Seklecki wrote:
> > > > > > Unfortunately it's quite common to have one IP shared among more
> > > > > > interfaces - e.g. in PPTP server. 
> > > > > 
> > > > > This is a proxy-arp config?  Are we talking about an embedded platform
> > > > > here?
> > > > 
> > > > No, it's simple Red Hat Linux box.
> > > > 
> > > > > Besides, if this is some type of RAS/Concentrator appliance, wouldn't
> > > > > there be a separate management interface for system-service 
> > > > > abstraction?
> > > > 
> > > > Well, I do not know the customer configuration in detail, but I am able
> > > > to reproduce the ugly log messages by setting channel bonding for
> > > > cluster: 
> > > > http://kbase.redhat.com/faq/FAQ_79_258.shtm
> > > > 
> > > > 
> > > > Anyway, I think it's not that important why there is such configuration
> > > > - the customer just wants it. I went through some of the MIBs and it
> > > > seems to me that IP-MIB does not allow to manage/monitor two interfaces
> > > > with the same IP address - there would be two values for one OID (e.g.
> > > > if both eth0 and eth1 have address 5.5.5.5, then e.g.
> > > > IP-MIB::ipAddressIfIndex.ipv4."5.5.5.5" should have value 2 and 3, which
> > > > is not possible from MIB point of view). 
> > > > 
> > > > So, if I understand it correctly, the second interface will be invisible
> > > > in IP-MIB. The appropriate CONTAINER_INSERT will fail, causing memory
> > > > leak (fixed by patch #1710632) and ugly error message every 30 seconds.
> > > > 
> > > > I'll try to get rid of the periodical error messages and display
> > > > something meaningful only once.
> > > > 
> > > > Jan
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > 
> > 
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Net-snmp-users mailing list
> > Net-snmp-users@lists.sourceforge.net
> > Please see the following page to unsubscribe or change other options:
> > https://lists.sourceforge.net/lists/listinfo/net-snmp-users
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Net-snmp-users mailing list
> Net-snmp-users@lists.sourceforge.net
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
> 
> 
> 
> 
> 
> 
> 
-- 
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.




IMPORTANT: This message contains confidential information and is intended only 
for the individual named. If the reader of this message is not an intended 
recipient (or the individual responsible for the delivery of this message to an 
intended recipient), please be advised that any re-use, dissemination, 
distribution or copying of this message is prohibited.  Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system.



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to