SNMP support for blades' internal components (CPU, memory DIMMs, etc.)
Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered"
Could you try the following query to see what comes back
snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr I think you need to validate that your server is actually answering SNMP queries for you.
VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired.
Cheers,
Michael
On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote:
Dear Observium,
This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364.
We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers.
I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status.
I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached).
Do you think it would be possible / interesting to recover such information ?
Thank you for your feedback.
Best regards.
Youssef BENGELLOUN - ZAHR - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr <image23bec5.PNG> Web : prodware.fr
<image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG>
<par01-esx02-bl2.txt><par01-esx03-bl2.txt>_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
for environment monitoring use the IPMI Interface of the blades' ILOM.
lg.
TF
Am 27.02.2017 um 12:48 schrieb Michael:
Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered"
Could you try the following query to see what comes back
snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr
I think you need to validate that your server is actually answering SNMP queries for you.
VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired.
Cheers,
Michael
On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote:
Dear Observium,
This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364.
We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers.
I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status.
I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached).
Do you think it would be possible / interesting to recover such information ?
Thank you for your feedback.
Best regards.
Youssef BENGELLOUN - ZAHR - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr <image23bec5.PNG> Web : prodware.fr
<image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG>
<par01-esx02-bl2.txt><par01-esx03-bl2.txt>_______________________________________________ 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
Dear Thoralf,
That’s not what we are trying to achieve here. For environmental sensors, we poll the chassis’ management modules directly (whatever they are called : AMM/CMM, CMC, IMM, ILO, etc.) and we get it if they are supported by observium.
What I’m trying to get is the state of the components in each blade : CPU or memory DIMM dead, etc.
Best regards.
Le 28/02/2017 06:18, « observium au nom de Thoralf Freitag » <observium-bounces@observium.org au nom de teeff.bln@gmail.com> a écrit :
Hi,
for environment monitoring use the IPMI Interface of the blades' ILOM.
lg.
TF
Am 27.02.2017 um 12:48 schrieb Michael: > Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered" > > Could you try the following query to see what comes back > > snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr > > I think you need to validate that your server is actually answering SNMP queries for you. > > VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired. > > Cheers, > > Michael > > > > > > > > >> On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote: >> >> >> Dear Observium, >> >> This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364. >> >> We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers. >> >> I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status. >> >> I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached). >> >> Do you think it would be possible / interesting to recover such information ? >> >> Thank you for your feedback. >> >> Best regards. >> >> >> Youssef BENGELLOUN - ZAHR - Consultant Expert >> Prodware France >> T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr >> <image23bec5.PNG>Web : prodware.fr >> >> <image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG> >> >> >> >> <par01-esx02-bl2.txt><par01-esx03-bl2.txt>
BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr
_______________________________________________ >> 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
Hi,
we have Fujitsu systems. On these every blade has its own ilom. Before we had IBM BladeCenterH, the amm provides such information (I'm not sure, if it supports ipmi). But if I remember right, the X5-Blades there reacable via IMM directly. Did you try configure the iloms, imms, iDRACs for ipmi (at each blade if possible) and configured this at the ipmi tab of each bare metall system ?
lg.
TF
Am 28.02.2017 um 07:11 schrieb Youssef BENGELLOUN - ZAHR:
Dear Thoralf,
That’s not what we are trying to achieve here. For environmental sensors, we poll the chassis’ management modules directly (whatever they are called : AMM/CMM, CMC, IMM, ILO, etc.) and we get it if they are supported by observium.
What I’m trying to get is the state of the components in each blade : CPU or memory DIMM dead, etc.
Best regards.
Le 28/02/2017 06:18, « observium au nom de Thoralf Freitag » <observium-bounces@observium.org au nom de teeff.bln@gmail.com> a écrit :
Hi, for environment monitoring use the IPMI Interface of the blades' ILOM. lg. TF Am 27.02.2017 um 12:48 schrieb Michael: > Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered" > > Could you try the following query to see what comes back > > snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr > > I think you need to validate that your server is actually answering SNMP queries for you. > > VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired. > > Cheers, > > Michael > > > > > > > > >> On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr> wrote: >> >> >> Dear Observium, >> >> This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364. >> >> We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers. >> >> I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status. >> >> I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached). >> >> Do you think it would be possible / interesting to recover such information ? >> >> Thank you for your feedback. >> >> Best regards. >> >> >> Youssef BENGELLOUN - ZAHR - Consultant Expert >> Prodware France >> T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr >> <image23bec5.PNG>Web : prodware.fr >> >> <image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG> >> >> >> >> <par01-esx02-bl2.txt><par01-esx03-bl2.txt>BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr
>> 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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
IMHO every compute node should have an imm, which is ipmi capable. Configure ipmi at the imm and try
ipmitool -H SERVER_IMM_IP -U USER -P PASSWORD sdr
ipmitool -H SERVER_IMM_IP -U USER -P PASSWORD fru
IF you have success, configure the imm-ip, username and password on the ipmi tab of your compute node. For example, my server has 192.168.2.9 und the ilom (imm) has 192.168.2.10, as shown below.
Am 28.02.2017 um 14:35 schrieb Youssef BENGELLOUN - ZAHR:
Dear Thoralf,
I'm in the process of opening SNMP on a test blade IMM. I'll let update you as soon as I have access.
In the mean time, I have SNMP opened on a CMM and I was able to gather snmpwalk and discovery information (in debug mode). Please see attached.
I believe this would be more relevant for the chassis enclosure itself.
Best regards.
*Youssef BENGELLOUN - ZAHR* - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr
mailto:ybzahr@prodware.fr
Web : prodware.fr http://www.prodware.fr http://twitter.com/Prodware/ http://www.facebook.com/Prodware/ https://www.linkedin.com/company/prodwarefrance https://www.youtube.com/c/ProdwareFrance http://www.viadeo.com/fr/company/prodware http://www.prodware.fr/social-network/
*De :* observium observium-bounces@observium.org de la part de Thoralf Freitag teeff.bln@gmail.com *Envoyé :* mardi 28 février 2017 07:51 *À :* observium@observium.org *Objet :* Re: [Observium] SNMP support for blades' internal components (CPU, memory DIMMs, etc.)
Hi,
we have Fujitsu systems. On these every blade has its own ilom. Before we had IBM BladeCenterH, the amm provides such information (I'm not sure, if it supports ipmi). But if I remember right, the X5-Blades there reacable via IMM directly. Did you try configure the iloms, imms, iDRACs for ipmi (at each blade if possible) and configured this at the ipmi tab of each bare metall system ?
lg.
TF
Am 28.02.2017 um 07:11 schrieb Youssef BENGELLOUN - ZAHR:
Dear Thoralf,
That’s not what we are trying to achieve here. For environmental sensors, we poll the chassis’ management modules directly (whatever they are called : AMM/CMM, CMC, IMM, ILO, etc.) and we get it if they are supported by observium.
What I’m trying to get is the state of the components in each blade : CPU or memory DIMM dead, etc.
Best regards.
Le 28/02/2017 06:18, « observium au nom de Thoralf Freitag » <observium-bounces@observium.org au nom de teeff.bln@gmail.com> a écrit :
Hi, for environment monitoring use the IPMI Interface of the blades' ILOM. lg. TF Am 27.02.2017 um 12:48 schrieb Michael: > Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered" > > Could you try the following query to see what comes back > > snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr > > I think you need to validate that your server is actually answering SNMP queries for you. > > VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired. > > Cheers, > > Michael > > > > > > > > >> On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr> wrote: >> >> >> Dear Observium, >> >> This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364. >> >> We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers. >> >> I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status. >> >> I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached). >> >> Do you think it would be possible / interesting to recover such information ? >> >> Thank you for your feedback. >> >> Best regards. >> >> >> Youssef BENGELLOUN - ZAHR - Consultant Expert >> Prodware France >> T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr >> <image23bec5.PNG>Web : prodware.fr >> >> <image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG> >> >> >> >> <par01-esx02-bl2.txt><par01-esx03-bl2.txt>BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr
>> 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
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
Hi Youssef,
I told you the general way getting such information as you're looking for.
Oberservium is a great monitoring solution with an intuitive WebUI. It covers a wide number auf vendors. But IMHO it is limited. Everything wich is provided by the developers, it works fine, out of the box, in a short time. But you're limited to this. There is no easy way to exted the functionality, or i didn't found it yet.
From my point of view the main focus of Oberservium is more statistics and accounting than alerting.
Had you tried using ipmi as I told you before ? If the result does not covers what you are expecting, presumably Obervium is not able to do this.
https://wikitech.wikimedia.org/wiki/Monitoring_package_survey is a very good overview of existing monitoring systsms. Maybe you can find there an additional tool, which helps solving your requirement.
Best regards
Thoralf
Am 28.02.2017 um 16:15 schrieb Youssef BENGELLOUN - ZAHR:
Dear Thoralf,
Thank you for feedback.
Were you able to get the information I’m looking for using IPMI ? Could you please share a screenshot of what you got ?
Thank you.
*Youssef BENGELLOUN - ZAHR* - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr
mailto:ybzahr@prodware.fr
Web : prodware.fr http://www.prodware.fr http://twitter.com/Prodware/ http://www.facebook.com/Prodware/ https://www.linkedin.com/company/prodwarefrance https://www.youtube.com/c/ProdwareFrance http://www.viadeo.com/fr/company/prodware http://www.prodware.fr/social-network/
*De : *observium observium-bounces@observium.org au nom de Thoralf Freitag teeff.bln@gmail.com *Répondre à : *Observium Public Support observium@observium.org *Date : *mardi 28 février 2017 à 16:00 *À : *Observium Public Support observium@observium.org *Objet : *Re: [Observium] SNMP support for blades' internal components (CPU, memory DIMMs, etc.)
IMHO every compute node should have an imm, which is ipmi capable. Configure ipmi at the imm and try
ipmitool -H SERVER_IMM_IP -U USER -P PASSWORD sdr
ipmitool -H SERVER_IMM_IP -U USER -P PASSWORD fru
IF you have success, configure the imm-ip, username and password on the ipmi tab of your compute node. For example, my server has 192.168.2.9 und the ilom (imm) has 192.168.2.10, as shown below.
Am 28.02.2017 um 14:35 schrieb Youssef BENGELLOUN - ZAHR:
Dear Thoralf, I'm in the process of opening SNMP on a test blade IMM. I'll let update you as soon as I have access. In the mean time, I have SNMP opened on a CMM and I was able to gather snmpwalk and discovery information (in debug mode). Please see attached. I believe this would be more relevant for the chassis enclosure itself. Best regards. *Youssef BENGELLOUN - ZAHR*- Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr <mailto:ybzahr@prodware.fr> ------------------------------------------------------------------------ Web : prodware.fr <http://www.prodware.fr> <http://twitter.com/Prodware/> <http://www.facebook.com/Prodware/> <https://www.linkedin.com/company/prodwarefrance> <https://www.youtube.com/c/ProdwareFrance> <http://www.viadeo.com/fr/company/prodware> <http://www.prodware.fr/social-network/> ------------------------------------------------------------------------ *De :*observium <observium-bounces@observium.org> <mailto:observium-bounces@observium.org> de la part de Thoralf Freitag <teeff.bln@gmail.com> <mailto:teeff.bln@gmail.com> *Envoyé :* mardi 28 février 2017 07:51 *À :* observium@observium.org <mailto:observium@observium.org> *Objet :* Re: [Observium] SNMP support for blades' internal components (CPU, memory DIMMs, etc.) Hi, we have Fujitsu systems. On these every blade has its own ilom. Before we had IBM BladeCenterH, the amm provides such information (I'm not sure, if it supports ipmi). But if I remember right, the X5-Blades there reacable via IMM directly. Did you try configure the iloms, imms, iDRACs for ipmi (at each blade if possible) and configured this at the ipmi tab of each bare metall system ? lg. TF Am 28.02.2017 um 07:11 schrieb Youssef BENGELLOUN - ZAHR: Dear Thoralf, That’s not what we are trying to achieve here. For environmental sensors, we poll the chassis’ management modules directly (whatever they are called : AMM/CMM, CMC, IMM, ILO, etc.) and we get it if they are supported by observium. What I’m trying to get is the state of the components in each blade : CPU or memory DIMM dead, etc. Best regards. Le 28/02/2017 06:18, « observium au nom de Thoralf Freitag » <observium-bounces@observium.org au nom de teeff.bln@gmail.com> <mailto:observium-bounces@observium.orgaunomdeteeff.bln@gmail.com> a écrit : Hi, for environment monitoring use the IPMI Interface of the blades' ILOM. lg. TF Am 27.02.2017 um 12:48 schrieb Michael: > Looks to me like there's no data at all coming back from either of those esxi hosts. "WARNING: 0 devices discovered" > > Could you try the following query to see what comes back > > snmpwalk -v3 <your-snmpv3-details-here> par01-esx02-bl2 sysDescr > > I think you need to validate that your server is actually answering SNMP queries for you. > > VMware have long been reluctant to do much with SNMP (prefering to push people towards vCenter/vCOPS). As a result, their support for revealing lots of physical host information leaves a bit to be desired. > > Cheers, > > Michael > > > > > > > > >> On 27 Feb 2017, at 9:35 pm, Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr> <mailto:ybzahr@prodware.fr> wrote: >> >> >> Dear Observium, >> >> This is a request for information / enhancement, I hope you will find it relevant / useful. Actually running latest stable version 17.2.8364. >> >> We run quite a lot of blade chassis (DELL M1000e, IBM bladecenterH, IBM pureflex) and monitor the blades in the enclosures, more specifically the ESXi hosts servers. >> >> I recently noticed that we were not able to recover SNMP information about physical components’ status (CPU, memory DIMMs, etc.). We are more interested in memory DIMM status. >> >> I have run a discovery against a couple of hosts in debug mode and can see that recovered SNMP information is pretty basic (see attached). >> >> Do you think it would be possible / interesting to recover such information ? >> >> Thank you for your feedback. >> >> Best regards. >> >> >> Youssef BENGELLOUN - ZAHR - Consultant Expert >> Prodware France >> T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr <mailto:ybzahr@prodware.fr> >> <image23bec5.PNG>Web : prodware.fr >> >> <image9b26f1.JPG> <image5c3e4c.JPG> <image0119e3.JPG> <imagee569c0.JPG> <image93eaa0.JPG> <image039eb0.JPG> >> >> >> >> <par01-esx02-bl2.txt><par01-esx03-bl2.txt> BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr <mailto:ybzahr@prodware.fr> Web : prodware.fr _______________________________________________ >> observium mailing list >> observium@observium.org <mailto:observium@observium.org> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > _______________________________________________ > observium mailing list > observium@observium.org <mailto:observium@observium.org> > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto: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
participants (3)
-
Michael -
Thoralf Freitag -
Youssef BENGELLOUN - ZAHR