Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Ethernet link aggregation and Lights Out management?



Title: Re: Ethernet link aggregation and Lights Out management?
At 10:39 PM +1100 1/6/07, Nathan Zamprogno wrote:
I will shortly be installing a new Intel XServe, and I would like to do link aggregation (802.3ad) on both the Ethernet interfaces.

Does anyone know if this has any implications for the Lights Out management feature of these new XServes? The LOM documentation makes mention of both eth0 and eth1 being assigned additional static IP addresses not related to the "main" IP address of the server, so does LOM just pick up the fact that the interfaces are bonded and run with it? Keep in mind that the switch that these two interfaces will be plugged into will also need to be set to 802.3ad mode, so there will be no ability to address the XServe except through the bonded interface.

Hope someone can shed some light. Thanks.

I think the answer to your question is going to have more to do with your switch than the XServe so you should be addressing this question to the vendor of that switch rather than making us try and guess for whomever that may be.
--
-dhan
------------------------------------------------------------------------
Dan Shoop                                                   AIM: iWiring

No, I think the answer to this question goes beyond the make of switch I plug it into. The Lights Out configuration screen in Server Monitor lets you set the IP for LOM for each of the two physical ethernet interfaces (listed as Port1 and Port2, but presumably == en0 and en1). However, I have created an aggregated interface called bond1 and enabled LACP (Link Aggregation) on the two ports of my switch (A Procurve 6108) to double-barrel my server bandwidth.

I can see my Intel XServe by using 127.0.0.1 in Server Monitor locally, but the XServe cannot be seen by SM at all at the bond0 IP (in the 192.168.x.x range), nor at the "alternate" IP set in the LOM setup page for Port1 or Port2. Sure, the switch uses the standard LACP standard procedures to fall back to a single port in the event of one interface failing, but Apple's implementation may be fundamentally incompatible with LACP.

I believe LOM is broken for users using link aggregation. At the very least, there is no word from Apple confirming or denying this issue, or to supply any guidance.

-- 
Nathan Zamprogno,
IT Manager, Wycliffe Christian School. Manager, Baliset Solutions consultancy
email@hidden Ph: (02) 47 536422 Mob: 0412 141 811
http://www.wycliffe.nsw.edu.au

"The suspicious believe everybody to be suspicious; the liar feels secure in the thought that he is not so foolish as to believe that there is such a phenomenon as a strictly truthful person; the envious see envy in every soul; the miser thinks everybody is eager to get his money;...and the abandoned sensualist looks upon the saint as a hypocrite"
-James Allen
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden

This email sent to email@hidden



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.