That's true Jimmy. And the setting might still be there. I havn't chekked.   As Torsten write. even thoug the installer packages is different the firmware is excactly the same.   A FW packages e.i FW 1.70 for i.e Ilo. would be named 14123.exe for windows and 14124.scexe for linux. But the FW is the same. no difference at all. Aboave numbers are made up by me.  Some times you will find that a FW 1.70 has been replaced by 1.70(B). This is due to a bug in the installer packages. The 1.70 fw is still the very same. Alos sometimes will find there's a fw xxxx. and one called FW DVD/SPP supplemtary. And the supplementary is a Linux packages, that is ment for off-line installation (boot on the SPP)   For FW and driver maintenance I will recommend that you use the SPP (Support Pack for ProLiant). This will run on both Windows and Linux. If you boot on it, it do use Linux.   Most servers come as bare metal from factory, then customers install what ever they like.   A few years ago. A customer of mine, who got a BWA system. They got a production system and a test system. They wanted to add an extra blade to the  test system. The BWA is running Linux. Customer got more than 100 decomissioned BL460 G6's setting on the shelf (former windows and ESX systems). We just pick one from the shelf. We did upgrade FW, to match the FW baseline, that is based on the SPP's. And ofcource to have identical fw.   There's no difference on FW used for Linux, Windwos Vmware, or whatever. As per Jimmys comment, there might still be a settnig in the BIOS. Do open the BIOS setup (RBSU). And if you hit CTRL+A. You will get more setup options.   BR /jag ... View more

Hi Anthony   Blade servers work the same way as stand alone servers.   I have no knowledge on networking og Linux.   However. The Cisco switch is a standard Cisco switch. It work like any other Cisco switch and is configured and adminstered. Like any other Cisco switch. Only difference is, it's in another box. And the cabling between the servers and the switch has been replaced by a midplane. Using a midplane, also mean that ports is fixed, and can't be changed. Server in bay 1, Nic port 1 is wired to Switch in interconnect bay 1, port 1. On the C7000 Nic port 2 would be wired to Switch in IC bay 2, port 1.   The C3000 is a cut down/half of the C7000. >Half as many servers, and half as many interconnects. > the high availebility design of the C7000 is cut in half.   Servers is still having 2 embedded nic ports, and 2 or 3 Mezzanine slots (depend on full/half hight servers).   C7000 is designed for 16 half hight servers. So the interconnect modules got 16 internal ports (ports between servers and switches).   When you put the servers and inteconnects into a C3000, Then NIC port 2 is wired to Interconnect 1. in N+8. So on the C3000 Server 1, nic 2 is wired to IC 1 port 9. and so on.   On a C3000. If you want to use 2 switches, you must put an extra NIC card in Mezzanin 1.   Since you are running old Cisco switches in a C3000, do remain on an old FW version on the OA. There is temperature detection issues with the 3020 on C3000. So newer FW will run fans at full speed.   To understand the hardware. HP got som very good technoligy briefs. I will recommend you to study the C7000 first, then move on to the C3000. Then what seem to be odd, will make perfect sence. C7000 tech: http://h20565.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c00816246 C3000 Tech: http://www.ts.avnet.com/uk/vendors/hp/assets/c3000_enclosure   As fo Linux to use NIC teaming.You will need Linux stuff, that can do that. I know that HP support SUSE, Red Hat and more. But you will have to look for your Linux distro. Start look for driver fra a balde, that you do have. Here's an example: http://h20566.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3884100&lang=en&cc=us Well, Ubuntu is in there.   Good luck :) BR /jag ... View more