I have a spare Dell Poweredge 2800 server that had a couple of drives crash and has been inactive. I decided to bring it to life as an Asterisk server - experimenting with Asterisk and Linux. We have very little Linux experience.
Installation went smooth with a basic CentOS disk and PBX-In-A-Flash. Asterisk is running great as a little PBX.
But the system is running really loud - which makes me think the drivers that got installed are not ideal - at least for monitoring fans, power etc.
I don't think running Asterisk in our environment will tax the drives, CPU and memory of this system - but I was thinking - what key parts of a server are worth chasing drivers for?
CentOS (RHEL from SRPMs) has excellent Dell support.
All hardware should be reporting in properly but, take a look at the command "dmidecode" (grep is your friend - e.g:
dmidecode | grep erial
will find you the service tag). I'd suggest installing OpenManage and monitoring your hardware with the built in tools.Here is a one liner that will attach you to Dell's repo and install OpenManage 6.1
edit
/etc/omarolemap
to add users in.Once installed visit your hardware monitor at: https://localhost:1311/ -or- https://yourserverip:1311/
Hope this helps... ;-)
In my experience with Dell Servers, the fan RPMs are always controlled by the bbmc, thereby not requiring any specific drivers. In fact, upon boot, the fans initially spin up to full speed, but then will idle down to very low speed, even if you stay in the BIOS setup screen (no OS loaded at all).
You may be able to poke at the bbmc using ipmitool - it should be able to give you readouts of the system board temperature sensors and fan speeds.
Edit - another thing to check is to make sure that the chassis is closed securely and that the bbmc isn't reporting any faults. Oftentimes if the bbmc sees any faults, it'll spin up the fans.
It won't be hard to find all of the available drivers on the Dell site, they may be infact be in one big, easy to install, package. I'd certainly go out of my way to make sure I'd installed as many vendor-specific drivers as possible.