Thank you. I found my mistake when adding is that I used the incorrect community string.
//Garrett
On Wed, Jan 4, 2017 at 11:48 AM, Simon Mousey Smith < simonsmith5521@gmail.com> wrote:
:)
Simon
On 4 Jan 2017, at 18:43, Simon Mousey Smith simonsmith5521@gmail.com wrote:
Our setup currently monitors 3 HP cube servers on the iLO interface without any issue
You don’t get much info from the SNMP side of things, but you get temperature which is handy :)
Regards
Simon
On 4 Jan 2017, at 17:15, Jesper Frank Nemholt jfn@dassic.com wrote:
You can include the name/IP of the iLO as a device of its own and it will show up in the management group. This is what I usually use.
If you use shared LAN for the iLO instead of dedicated port, I believe you can get both server data and iLO data to be present for the same entry in Observium by enabling an option on the iLO to share this.
If you want the same behavior across multiple server brands it's easiest to just treat each iLO/iDRAC/etc. as a dedicated device.
/Jesper On Wed, Jan 4, 2017 at 08:05 Garrett Pye gvpye54@gmail.com wrote:
Is there a configuration Observium has to include HP iLO interface IP? Currently it looks like neither adding a device or port inventory does not support monitoring the iLO port.
*Garrett Pye*
*CNOC Engineer | Business Class Voice*
5800 S. Quebec St, Greenwood Village, CO 80111 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
