My Top 5 Reason Dell Servers Are Better than HP
I have been working in IT for quite some time and have worked primarily with Dell and Compaq/HP servers over the years. I know this Dell vs HP debate is not new, nor will it ever die so long as both companies are in business. However I wanted to post my top 5 reasons that I feel Dell provides a better server than HP does. The term better is a very general one, however hopefully the reasons below will define what I mean by it.
This post is purely subjective but I wanted to write it anyways, feel free to comment if you agree or disagree with my thoughts here.
Out-of-Band Management
I have used out-of-band management to save me multiple times, because I work mostly with Dell that safety is the Dell Remote Access Controller (DRAC). I have used their 4th, 5th, and 6th (current) generation. I have also used HP's Integrated Lights-Out (iLO) in their ProLiant G3, G5, and G6 servers to save me time/trouble as well. While both provide the same functionality I feel that Dell has a better product that is easier to use and manage. Below are some reasons why I say this based on my experience.
- IP Configuration - You can assign an IP during POST on both systems, however with Dell you are able to use OpenManage Server Administrator to make this change. HP does have a Windows based application called HP Lights-Out Online Configuration Utility however this is just another software that has to be loaded on a system.
- Keyboard input - For some reason HP requires you to assign hot keys to function keys or key combinations. Without doing this you would be unable to press f9 for example while connected to the console. With Dell the keyboard interaction is much more seamless and does not require you to pre-define hot keys.
- Virtual media - This feature allows you to mount an ISO so that you can boot from it or load software from it. For example you would be able to install VMware vSphere remotely without ever having access to the server. While I have had problems with the DRAC on this point I have had the iLO totally fail me all together.
- User management - If you lose, forget, or don't know the username/password to log into the interface you can reset it with Dell OpenManage Server Administrator. With HP you have to use a command line software in conjunction with an XML file that defines configurations
- Licensing - Dell is a hardware product that you buy whereas the iLO comes installed and needs to be licensed. Dell adopted HP's implementation in their current line of server with the iDRAC Express which provides the functionality that the unlicensed iLO provided. You still must buy the iDRAC Enterprise to get console access but there is no license to purchase or manage.
Management Software
Dell server management software is called OpenManage Server Administrator. Through OpenManage you are able to manage all of your hardware, DRAC, and storage controllers and arrays, view system information, and setup alerting. It also provides SNMP management functionality so that you can remotely monitor the system and remediate issues when they arise such as disk or power supply failures.
HP's System Management Homepage provides much of the same functionality, however there is also generally a ton of other software installed for management of the system. For example if you look in the add/remove programs or startup menu of a HP server you will find much more installed which means much more to update. While HP does provide their support pack to update everything at once I find that their management software is very bloated and cumbersome.
Furthermore doing a P2V of a HP server is so much more time consuming compared to a Dell server. After the P2V process there is more software to uninstall, NIC teaming software that glues itself into the TCP/IP configuration, files scattered everywhere on the hard drive (root, program files, system32) where as with Dell you simply uninstall OpenManage and any other unnecessary drivers.
Serial Numbers
Dell uses a service tag for their serial numbers, it is a short alpha numeric string that can be inputted on their support site to identify your system, check warranty status and download software. This serial number is also what you provide when you call in for technical support or need to renew a warranty. HP on the other hand uses a serial number and part number. The warranty checker on HP's website requires both of these to check the warranty status. As far as I know you are not able to look up your HP system by the serial number either.
Price
Dell is always less expensive than HP when buying direct or through a large distributor like CDW. While I really like my CDW rep and would love to give him more business I refuse to buy HP whenever possible.
Design
In my experience Dell servers have been easier to get into and work with, HP require a torx screw to remove or get into certain areas while Dell uses standard Phillips screws.
Dell OpenManage 6.1.0 Fails To Install on ESX 4.0
Normally, the installation of OpenManage can be run after extracting the archive with the following command unless you want to supply optional arguements.
./srvadmin-install.sh
We had upgraded one of the two servers from VMware ESX 3.5 to 4.0 and upgraded OpenManage from the previous version to 6.1 with no problems. However, on this server, after upgrading VMware from 3.5 to 4.0 we recieved the following error when trying to install OpenManage 6.1. The error message is basically saying that three OpenMange packages were already installed and during the upgrade process could not find asssociated files. The problem with this is that this was a fresh installation and those packages should not have existed at all.
Server Administrator version 6.1.0-426 is currently installed.
Installed components are:
- srvadmin-omilcore-6.1.0-426
- srvadmin-hapi-6.1.0-426
- srvadmin-ipmi-6.1.0-426.DUP
Upgrading Server Administrator to 6.1.0-648warning: srvadmin-hapi-6.1.0-648.i386.rpm: Header V3 DSA signature: NOKEY, key ID 23b66a9d
Preparing... ########################################### 100%
/var/tmp/rpm-tmp.49620: line 355: /tmp/dellupdatepackage-hapi-12342-24438/omil/prereqcheck/Funcs.sh: No such file or directory
error: %pre(srvadmin-omilcore-6.1.0-648.i386) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping srvadmin-omilcore-6.1.0-648
/var/tmp/rpm-tmp.49620: line 6: /tmp/dellupdatepackage-hapi-12342-24438/omil/prereqcheck/Funcs.sh: No such file or directory
error: %pre(srvadmin-hapi-6.1.0-648.i386) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping srvadmin-hapi-6.1.0-648
/var/tmp/rpm-tmp.49620: line 2: /tmp/dellupdatepackage-hapi-12342-24438/funcs/srvadmin-omilcore.sh: No such file or directory
error: %preun(srvadmin-omilcore-6.1.0-426.i386) scriptlet failed, exit status 1
I called Dell technical support to for assistance since I did not know what the issue was even after Googling. She had me check to see what packages were installed on the system.
rpm -qa | grep srv
With those packages identified she had more remove them.
rpm -e --nodeps --nofiles --noscripts srvadmin-ipmi-6.1.0-426.DUP
rpm -e --nodeps --nofiles --noscripts srvadmin-omilcore-6.1.0-426
rpm -e --nodeps --nofiles --noscripts srvadmin-hapi-6.1.0-426
Once the packages were removed the isntallation was successful. She explained that this was caused by upgrading the BIOS before OpenManage was installed, and that once the BIOS upgrade was complete it was trying to update OpenManage to report the BIOS version. However because OpenManage was not installed it could not update the version and left the packages on the server.
So with that said, you have two options. You can upgrade the BIOS and firmware, remove the orphaned packages, and install OpenManage 6.1 or better yet isntall OpenManage 6.1 then upgrade the BIOS and firmware so that those upgrades are completed successfully. On the other hand, Dell should correct this issue as it is more of a bug than working as it should since the orphaned packages should be deleted if OpenManage is not installed.
Invalid CD/DVD-ROM Selection Error When Attempting To Attach Virtual Media ISO on DRAC
This issue is isolated to Internet Explorer 8, I have tried this on multiple systems running version 8 and all have the same problem. When you try and attach the media it throws an error saying "Invalid CD/DVD-ROM Selection" and the CD/DVD-ROM drive path behind the error is changed to C:\fakepath\whatever.is. This issue does not occur in Internet Explorer 7 and I would assume would be fine in version 6.
I called Dell technical support and the error can be resolved by adding the IP address as a trusted site in Internet Explorer 8. Once that is done you should be able to connect your ISO. The person I talked to at Dell had never seen this error so it could possibly be fixed with a future firmware upgrade. Nevertheless it is another example of the problems encountered when forcing users to use Internet Explorer due to ActiveX rather than creating web based software that relies on open standards.
Bring A Dell PowerVault MD3000i Disk Online From The Command Line
When two drives in a RAID 5 array going offline, so goes your data. If this happens, hopefully the disks are not truly failed but simply offline for some reason. This was the case with a client recently. For some reason when we put new drives in the Dell PowerVault MD3000i it took 2 drives in a RAID 5 array offline which took down a virtual machine that resided on that datastore.
If you have more than one drive offline and simply re-insert those drives they will still show as failed and will not come back online and rebuild if necessary. Instead you can force the state of the drive back to good condition which will bring them back online, after which the SAN can determine which disks if any needed to be rebuilt.
Below is the command to bring slot 12 in enclosure 0 back online. You will need to modify it according to what disks have failed, if more than one drive has failed re-run the command a second time and change the drive number. If you have one or more MD1000 connected to your MD3000i you will also need to change the enclosure number (in this case 0) to the correct number.
C:\Program Files\Dell\MD Storage Manager\client>smcli -n "<Storage Array Name>" -c "revive physicalDisk [0,12]";
After this command is run the drive should come back online and hopefully your data will be intact.
Syntax check complete.
Executing script...
Script execution complete.
SMcli completed successfully.
Bring A Dell PowerVault MD3000i Disk Group Offline/Online
If you need to take a disk group offline you will need to do it via the command line, you can't do it in the Modular Disk Storage Manager.
The Storage Array Name can be found by opening the Modular Disk Storage Array and it will be at the top left hand corner. The syntax is case sensitive so make sure the storage array name is correct.
The disk group (in this case [3]) will also change depending on which disk group you need to take offline. To find your disk group number click the 'Disk Groups & Virtual Disks' link from the Summary tab of the Modular Disk Storage Manager.
Run the command below, it will check the syntax, execute the script, and let you know if it completes successfully. Once you have taken the disk group offline, physically remove the drives then re-seat them and run the second command (almost identical to the first) to bring it back online.
C:\Program Files\Dell\MD Storage Manager\client>SMCli -n <Storage Array Name> "set diskGroup [3] availability=offline;"
Performing syntax check...
Syntax check complete.
Executing script...
Script execution complete.
SMcli completed successfully.
C:\Program Files\Dell\MD Storage Manager\client>SMCli -n <Storage Array Name> "set diskGroup [3] availability=online;"
How Mouse Poop Killed our VMware vCenter Server
With all the redundancy built into a server these days apparently a mouse is able to bring down a server. We had our VMware VirtualCenter running on an old Dell PowerEdge 2650 and the other day I was told it just wouldn't boot. This morning I went about troubleshooting, the LCD on the front said that there was no memory so I opened up the case to make sure the memory was seated correctly. As soon as I opened it I noticed what looked like rust on what I believe is the northbridge and other areas of the motherboard. Upon further investigation I noticed that it looked like mouse poop. Normally this probably would have seemed ridiculous but we were aware that there was a mouse in the office since an employee had seen it and we had noticed that it had been eating our food and pooping. The mouse seems to have gained entry into the server through one of the PCI slots that did not have a cover on it.
We have an extra working Dell PowerEdge 2650 so I put the two hard drives which were configured with RAID and thankfully the server booted and all is well. So, I guess a lesson learned is in addition to server redundancy, backups, and all the other fancy nice things that go along with a stable network infrastructure you need to make sure you don't have rodents in your server room, or at least make sure your PCI slots are covered.

