Re: AoE does not discover

I have finally resolved all of my AoE issues. Turns out the reason AoE 
did not seem to be discovering was because I had the wrong driver 
installed for the network interface I was using. The fact that this 
machine has several ethernet ports and chipsets on it which need 
different drivers caused confusion. So AoE was working perfectly all along.

Now I have a cpu node network booting and mounting the root fs from the 
disk node. Now I am working on getting a 64 bit version of our standard 
CentOS load built for using as the dom0 and domU's on our cpu nodes 
under Xen.

Now that I have a working AoE install a couple more questions:

What is the best practice for managing the AoE disk volumes? Currently 
everything is named by shelf and slot. I am concerned about accidentally 
mounting or mkfs'ing or something on the wrong slot. It would be nice if 
the AoE volumes could be named something more meaningful and something 
could be done to ensure that only the right machine accesses the right 
disk. I guess I will just have to be very careful for now.

Any performance tips on making AoE perform optimally? In production we 
will have a dedicated gig-e switch for the SAN. How important are jumbo 
frames? Unfortunately it seems that the ethernet chipset in our disk 
nodes are Broadcom 5721 gig-e which does not support jumbo frames. Hope 
that isn't going to kill us.

--

-- 
Tracy R Reed                  http://ultraviolet.org
A: Because we read from top to bottom, left to right
Q: Why should I start my reply below the quoted text

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV