On 06/17/10 12:02, Martin Turgeon wrote:
Hi again everyone,
I just realized after posting my question on optimal RAID config that
the best solution for hardware monitoring would be to use the
integrated iDRAC6. I have the Express version (no dedicated port). I
have never worked with DRAC cards and I would like to know your
opinions about the best way to use it for hardware monitoring. I'm not
really planning on using the remote control features, but it would be
nice too.
In addition to using DRAC notifications for hardware events, I would
suggest that you still run some local checks on the system itself
(Nagios checks via NRPE). There are several checks available that check
the status of the PERC controller and drives using mfiutil, amrstat, or
MegaCLI.
As I understand it, I have to configure an additional IP for iDRAC. In
my case, the servers are going to be installed in a colocation
datacenter so I guess I have to reserve an additional public IP for
each servers so I can access the iDRAC remotely? What are the securiy
implications?
This depends on what your options are - if you're colocating one server,
they may be pretty slim. In any case, I would strongly advise not
putting it out there on an unrestricted public address. I'm not sure of
the DRAC's history of security issues, but keep in mind that someone
using it essentially has physical access to your server. If you have to
put it out there on the internet, be sure to create a new user on the
iDRAC and disable the existing root account.
I'm also configuring a Nagios installation for monitoring. Is there a
way to plug iDRAC with Nagios to handle the notifications (snmp
maybe)? Or should I configure an email alert in the iDRAC config (I
assume there is a way to do that)?
You can configure the iDRAC to send SNMP traps, or even e-mails for
hardware events.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
