Hi,
I've just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the 'status' tab?
The 6500s have over 20 entries in there for "Fan - Fail" or "PSU - Fail" or "I'm not facing magnetic north - Fail" etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a 'Major-Alarm' failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being 'OK' and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information ---------------------------------------------
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it's just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
ASR, stuff missing from SNMP. Where have I heard this before? Oh yes, every ASR I've ever encountered!
You'd think Cisco would sort their shit out at some point!
We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and are on other devices), but Cisco's QA for ASR software is in the toilet.
I'd recommend opening a TAC case and shouting at them.
Adam.
Sent from BlueMail
On 20 Jan 2016, 10:43, at 10:43, Robert Williams Robert@CustodianDC.com wrote:
Hi,
I've just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the 'status' tab?
The 6500s have over 20 entries in there for "Fan - Fail" or "PSU - Fail" or "I'm not facing magnetic north - Fail" etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a 'Major-Alarm' failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being 'OK' and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it's just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
I’ve opened a TAC for this as it’s quite important because if we miss the Syslog events, then we have nothing else which will tell us about equipment at a remote location having a major fault.
In the meantime, I found this: http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9...
Specifically:
MIBs Used for Physical Entity Management - CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information. - CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the administrative and operational status of field-replaceable units (FRUs), such as fans, RSPs, and transceivers that are listed in the entPhysicalTable of the ENTITY-MIB.
I’m not very well versed (read: no clue at all) on how the various information is polled and correlated between the different MIBs by Observium, but - can you confirm/deny if the MIBs mentioned here are something would indeed be picked up by Observium? (Assuming Cisco were presenting it correctly as they claim in the document).
I’ll update with the outcome of the TAC in due course, if only for humour value.
Cheers,
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: 20 January 2016 10:50 To: Observium Network Observation System observium@observium.org Cc: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
ASR, stuff missing from SNMP. Where have I heard this before? Oh yes, every ASR I've ever encountered! You'd think Cisco would sort their shit out at some point! We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and are on other devices), but Cisco's QA for ASR software is in the toilet. I'd recommend opening a TAC case and shouting at them. Adam.
Sent from BlueMailhttp://www.bluemail.me/r
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
On 20 Jan 2016, at 10:43, Robert Williams <Robert@CustodianDC.commailto:Robert@CustodianDC.com> wrote: Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information ---------------------------------------------
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com
[X]
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hmm. We've never supported that MIB. Is there anything in there on this device?
adam. On 20/01/2016 12:50:37, Robert Williams robert@custodiandc.com wrote: Hi, I’ve opened a TAC for this as it’s quite important because if we miss the Syslog events, then we have nothing else which will tell us about equipment at a remote location having a major fault. In the meantime, I found this: http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... [http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9...] Specifically: MIBs Used for Physical Entity Management * CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information. * CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the administrative and operational status of field-replaceable units (FRUs), such as fans, RSPs, and transceivers that are listed in the entPhysicalTable of the ENTITY-MIB. I’m not very well versed (read: no clue at all) on how the various information is polled and correlated between the different MIBs by Observium, but - can you confirm/deny if the MIBs mentioned here are something would indeed be picked up by Observium? (Assuming Cisco were presenting it correctly as they claim in the document). I’ll update with the outcome of the TAC in due course, if only for humour value. Cheers, From: observium [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org]] On Behalf Of Adam Armstrong Sent: 20 January 2016 10:50 To: Observium Network Observation System observium@observium.org Cc: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected? ASR, stuff missing from SNMP. Where have I heard this before? Oh yes, every ASR I've ever encountered! You'd think Cisco would sort their shit out at some point! We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and are on other devices), but Cisco's QA for ASR software is in the toilet. I'd recommend opening a TAC case and shouting at them. Adam. Sent from BlueMail [http://www.bluemail.me/r] Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com [http://www.CustodianDC.com] On 20 Jan 2016, at 10:43, Robert Williams <Robert@CustodianDC.com [mailto:Robert@CustodianDC.com]> wrote: Hi, I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab? The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever. Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure: canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED LED Information --------------------------------------------- R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again) Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue? Cheers! Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com [mailto:Robert@CustodianDC.com] http://www.CustodianDC.com [http://www.CustodianDC.com]
observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
Yeah it does. It seems its extended version of ENTITY-STATE-MIB
On 20/01/16 15:53, Adam Armstrong wrote:
Hmm. We've never supported that MIB. Is there anything in there on this device?
adam. On 20/01/2016 12:50:37, Robert Williams robert@custodiandc.com wrote: Hi,
I’ve opened a TAC for this as it’s quite important because if we miss the Syslog events, then we have nothing else which will tell us about equipment at a remote location having a major fault.
In the meantime, I found this: http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... [http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9...]
Specifically:
MIBs Used for Physical Entity Management
- CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information.
- CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the administrative and operational status of field-replaceable units (FRUs), such as fans, RSPs, and transceivers that are listed in the entPhysicalTable of the ENTITY-MIB.
I’m not very well versed (read: no clue at all) on how the various information is polled and correlated between the different MIBs by Observium, but - can you confirm/deny if the MIBs mentioned here are something would indeed be picked up by Observium? (Assuming Cisco were presenting it correctly as they claim in the document).
I’ll update with the outcome of the TAC in due course, if only for humour value.
Cheers,
From: observium [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org]] On Behalf Of Adam Armstrong Sent: 20 January 2016 10:50 To: Observium Network Observation System observium@observium.org Cc: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
ASR, stuff missing from SNMP. Where have I heard this before? Oh yes, every ASR I've ever encountered! You'd think Cisco would sort their shit out at some point! We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and are on other devices), but Cisco's QA for ASR software is in the toilet. I'd recommend opening a TAC case and shouting at them. Adam. Sent from BlueMail [http://www.bluemail.me/r]
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com [http://www.CustodianDC.com]
On 20 Jan 2016, at 10:43, Robert Williams <Robert@CustodianDC.com [mailto:Robert@CustodianDC.com]> wrote: Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN130/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com [mailto:Robert@CustodianDC.com] http://www.CustodianDC.com [http://www.CustodianDC.com]
observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Oh great. More duplication \o/
adam. On 20/01/2016 13:17:39, Nikolay Shopik shopik@inblock.ru wrote: Yeah it does. It seems its extended version of ENTITY-STATE-MIB
On 20/01/16 15:53, Adam Armstrong wrote:
Hmm. We've never supported that MIB. Is there anything in there on this device?
adam. On 20/01/2016 12:50:37, Robert Williams wrote: Hi,
I’ve opened a TAC for this as it’s quite important because if we miss the Syslog events, then we have nothing else which will tell us about equipment at a remote location having a major fault.
In the meantime, I found this: http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... [http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9...]
Specifically:
MIBs Used for Physical Entity Management
- CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information.
- CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the administrative and operational status of field-replaceable units (FRUs), such as fans, RSPs, and transceivers that are listed in the entPhysicalTable of the ENTITY-MIB.
I’m not very well versed (read: no clue at all) on how the various information is polled and correlated between the different MIBs by Observium, but - can you confirm/deny if the MIBs mentioned here are something would indeed be picked up by Observium? (Assuming Cisco were presenting it correctly as they claim in the document).
I’ll update with the outcome of the TAC in due course, if only for humour value.
Cheers,
From: observium [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org]] On Behalf Of Adam Armstrong Sent: 20 January 2016 10:50 To: Observium Network Observation System Cc: Observium Network Observation System Subject: Re: [Observium] ASR9k fan failures not detected?
ASR, stuff missing from SNMP. Where have I heard this before? Oh yes, every ASR I've ever encountered! You'd think Cisco would sort their shit out at some point! We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and are on other devices), but Cisco's QA for ASR software is in the toilet. I'd recommend opening a TAC case and shouting at them. Adam. Sent from BlueMail [http://www.bluemail.me/r]
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com [http://www.CustodianDC.com]
On 20 Jan 2016, at 10:43, Robert Williams wrote: Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com [mailto:Robert@CustodianDC.com] http://www.CustodianDC.com [http://www.CustodianDC.com]
observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [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
For the record, CISCO-ENTITY-FRU-CONTROL-MIB is rather useless. I walked my ASR 9006 with it and this was the only thing it reports.
/Markus
2016-01-20 14:27 GMT+01:00 Adam Armstrong adama@memetic.org:
Oh great. More duplication \o/
adam.
On 20/01/2016 13:17:39, Nikolay Shopik shopik@inblock.ru wrote: Yeah it does. It seems its extended version of ENTITY-STATE-MIB
On 20/01/16 15:53, Adam Armstrong wrote:
Hmm. We've never supported that MIB. Is there anything in there on this
device?
adam. On 20/01/2016 12:50:37, Robert Williams wrote: Hi,
I’ve opened a TAC for this as it’s quite important because if we miss
the Syslog events, then we have nothing else which will tell us about equipment at a remote location having a major fault.
In the meantime, I found this:
http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... [ http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... ]
Specifically:
MIBs Used for Physical Entity Management
- CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM
contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information.
- CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and
configure the administrative and operational status of field-replaceable units (FRUs), such as fans, RSPs, and transceivers that are listed in the entPhysicalTable of the ENTITY-MIB.
I’m not very well versed (read: no clue at all) on how the various
information is polled and correlated between the different MIBs by Observium, but - can you confirm/deny if the MIBs mentioned here are something would indeed be picked up by Observium? (Assuming Cisco were presenting it correctly as they claim in the document).
I’ll update with the outcome of the TAC in due course, if only for
humour value.
Cheers,
From: observium [mailto:observium-bounces@observium.org [mailto:
observium-bounces@observium.org]] On Behalf Of Adam Armstrong
Sent: 20 January 2016 10:50 To: Observium Network Observation System Cc: Observium Network Observation System Subject: Re: [Observium] ASR9k fan failures not detected?
ASR, stuff missing from SNMP. Where have I heard this before? Oh yes,
every ASR I've ever encountered!
You'd think Cisco would sort their shit out at some point! We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and
are on other devices), but Cisco's QA for ASR software is in the toilet.
I'd recommend opening a TAC case and shouting at them. Adam. Sent from BlueMail [http://www.bluemail.me/r]
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com [http://www.CustodianDC.com]
On 20 Jan 2016, at 10:43, Robert Williams wrote: Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by
Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail”
or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has
a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm
from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather
critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com [mailto:Robert@CustodianDC.com] http://www.CustodianDC.com [http://www.CustodianDC.com]
observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [
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
Ahh. It just seems like a couple of extensions to entity-mib, support status, power on/off, etc. Not terribly useful indeed.
adam. On 20/01/2016 13:39:50, Markus Klock markus@best-practice.se wrote: For the record, CISCO-ENTITY-FRU-CONTROL-MIB is rather useless. I walked my ASR 9006 with it and this was the only thing it reports.
/Markus
2016-01-20 14:27 GMT+01:00 Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]>:
Oh great. More duplication \o/
adam. On 20/01/2016 13:17:39, Nikolay Shopik <shopik@inblock.ru [mailto:shopik@inblock.ru]> wrote: Yeah it does. It seems its extended version of ENTITY-STATE-MIB
On 20/01/16 15:53, Adam Armstrong wrote:
Hmm. We've never supported that MIB. Is there anything in there on this device?
adam. On 20/01/2016 12:50:37, Robert Williams wrote: Hi,
I’ve opened a TAC for this as it’s quite important because if we miss the Syslog events, then we have nothing else which will tell us about equipment at a remote location having a major fault.
In the meantime, I found this: http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... [http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9...] [http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9... [http://www.cisco.com/c/en/us/td/docs/routers/asr9000/mib/guide/asr9kmib/asr9...]]
Specifically:
MIBs Used for Physical Entity Management
- CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information.
- CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the administrative and operational status of field-replaceable units (FRUs), such as fans, RSPs, and transceivers that are listed in the entPhysicalTable of the ENTITY-MIB.
I’m not very well versed (read: no clue at all) on how the various information is polled and correlated between the different MIBs by Observium, but - can you confirm/deny if the MIBs mentioned here are something would indeed be picked up by Observium? (Assuming Cisco were presenting it correctly as they claim in the document).
I’ll update with the outcome of the TAC in due course, if only for humour value.
Cheers,
From: observium [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org] [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org]]] On Behalf Of Adam Armstrong Sent: 20 January 2016 10:50 To: Observium Network Observation System Cc: Observium Network Observation System Subject: Re: [Observium] ASR9k fan failures not detected?
ASR, stuff missing from SNMP. Where have I heard this before? Oh yes, every ASR I've ever encountered! You'd think Cisco would sort their shit out at some point! We support CISCO-ENTITY-SENSOR-MIB, which is where these should be (and are on other devices), but Cisco's QA for ASR software is in the toilet. I'd recommend opening a TAC case and shouting at them. Adam. Sent from BlueMail [http://www.bluemail.me/r [http://www.bluemail.me/r]]
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com [http://www.CustodianDC.com] [http://www.CustodianDC.com [http://www.CustodianDC.com]]
On 20 Jan 2016, at 10:43, Robert Williams wrote: Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13 0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com [mailto:Robert@CustodianDC.com [mailto:Robert@CustodianDC.com]] http://www.CustodianDC.com [http://www.CustodianDC.com] [http://www.CustodianDC.com [http://www.CustodianDC.com]]
observium mailing list observium@observium.org [mailto:observium@observium.org] [mailto:observium@observium.org [mailto:observium@observium.org]] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium] [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [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 [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 [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 [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 Robert,
We figured out that, in order to see the fans and power, we needed to force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN130/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Really?
What discovery options do you use on the command line?
Adam.
Sent from BlueMail
On 20 Jan 2016, 10:59, at 10:59, Frederic Gargula frederic.gargula@ip-max.net wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com
wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by
Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU -
Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently
has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise
alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080
10080 9870 9990 9900 9810 9990
(fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather
critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
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
I would like to add 4.x releases doesn't expose lot of sensors, they did improve that in 5.2 IOS-XR iirc
On 20/01/16 13:59, Frederic Gargula wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN130/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990 (fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
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,
Thanks for the input, I've just tried a discovery but no change.
The categories of good sensors are:
Processor Memory Storage Current Power Temperature Voltage
but nothing for 'Status':
##### Module Start: status #####
o Status Count 0 o Module time 0.0009s
It's running 5.2.1 by the way.
Cheers,
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Nikolay Shopik Sent: 20 January 2016 11:07 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
I would like to add 4.x releases doesn't expose lot of sensors, they did improve that in 5.2 IOS-XR iirc
On 20/01/16 13:59, Frederic Gargula wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to
force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com
wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by
Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU -
Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently
has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise
alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080
10080 9870 9990 9900 9810 9990
(fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather
critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
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 again,
I was just using the normal “discovery.php -h HOSTNAME”. That’s how I could get the sensors visible in Observium.
I don’t see any status neither, but I see a “Event” column, with all fans at OK state (see attached screenshot).
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 12:18, Robert Williams Robert@CustodianDC.com wrote:
Hi,
Thanks for the input, I've just tried a discovery but no change.
The categories of good sensors are:
Processor Memory Storage Current Power Temperature Voltage
but nothing for 'Status':
##### Module Start: status #####
o Status Count 0 o Module time 0.0009s
It's running 5.2.1 by the way.
Cheers,
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Nikolay Shopik Sent: 20 January 2016 11:07 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
I would like to add 4.x releases doesn't expose lot of sensors, they did improve that in 5.2 IOS-XR iirc
On 20/01/16 13:59, Frederic Gargula wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to
force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com
wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by
Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU -
Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently
has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise
alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080
10080 9870 9990 9900 9810 9990
(fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather
critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
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 Frederic - I’m curious what IOS-XR version was running where you are seeing the fan speed results showing correctly?
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Frederic Gargula Sent: 20 January 2016 12:54 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
Hi again,
I was just using the normal “discovery.php -h HOSTNAME”. That’s how I could get the sensors visible in Observium.
I don’t see any status neither, but I see a “Event” column, with all fans at OK state (see attached screenshot).
Best regards,
Frederic Gargula IP-Max SA
[cid:image001.png@01D1538A.C0AA6600]
On 20 Jan 2016, at 12:18, Robert Williams <Robert@CustodianDC.commailto:Robert@custodiandc.com> wrote:
Hi,
Thanks for the input, I've just tried a discovery but no change.
The categories of good sensors are:
Processor Memory Storage Current Power Temperature Voltage
but nothing for 'Status':
##### Module Start: status #####
o Status Count 0 o Module time 0.0009s
It's running 5.2.1 by the way.
Cheers,
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@custodiandc.com http://www.CustodianDC.comhttp://www.custodiandc.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Nikolay Shopik Sent: 20 January 2016 11:07 To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] ASR9k fan failures not detected?
I would like to add 4.x releases doesn't expose lot of sensors, they did improve that in 5.2 IOS-XR iirc
On 20/01/16 13:59, Frederic Gargula wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams <Robert@CustodianDC.commailto:Robert@CustodianDC.com> wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information ---------------------------------------------
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7 FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990
(fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Robert,
We’re running XR 5.3.2. Make sure you have "asr9k-mgbl-px-5.3.2” (sh install active in admin mode).
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 14:59, Robert Williams Robert@CustodianDC.com wrote:
Hi Frederic - I’m curious what IOS-XR version was running where you are seeing the fan speed results showing correctly?
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Frederic Gargula Sent: 20 January 2016 12:54 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
Hi again,
I was just using the normal “discovery.php -h HOSTNAME”. That’s how I could get the sensors visible in Observium.
I don’t see any status neither, but I see a “Event” column, with all fans at OK state (see attached screenshot).
Best regards,
Frederic Gargula IP-Max SA
<image001.png>
On 20 Jan 2016, at 12:18, Robert Williams Robert@CustodianDC.com wrote:
Hi,
Thanks for the input, I've just tried a discovery but no change.
The categories of good sensors are:
Processor Memory Storage Current Power Temperature Voltage
but nothing for 'Status':
##### Module Start: status #####
o Status Count 0 o Module time 0.0009s
It's running 5.2.1 by the way.
Cheers,
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Nikolay Shopik Sent: 20 January 2016 11:07 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
I would like to add 4.x releases doesn't expose lot of sensors, they did improve that in 5.2 IOS-XR iirc
On 20/01/16 13:59, Frederic Gargula wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to force a manual discovery of our ASR9K from the command-line. I hope this helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’ tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990
(fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just us with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
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 Frederic,
Thanks for that, obviously that's in the 5.3.x train, and newer, so potentially has fixes that ours does not which may well explain it...
I'll drop it onto a lab box and see if they appear. Incidentally we do have the management pie installed so it's not that, but I'll give the upgrade a go and see if it magically appears!
Cheers,
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Frederic Gargula Sent: 20 January 2016 14:23 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
Hi Robert,
We’re running XR 5.3.2. Make sure you have "asr9k-mgbl-px-5.3.2” (sh install active in admin mode).
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 14:59, Robert Williams Robert@CustodianDC.com
wrote:
Hi Frederic - I’m curious what IOS-XR version was running where you
are seeing the fan speed results showing correctly?
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of
Frederic Gargula
Sent: 20 January 2016 12:54 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
Hi again,
I was just using the normal “discovery.php -h HOSTNAME”. That’s how I
could get the sensors visible in Observium.
I don’t see any status neither, but I see a “Event” column, with all
fans at OK state (see attached screenshot).
Best regards,
Frederic Gargula IP-Max SA
<image001.png>
On 20 Jan 2016, at 12:18, Robert Williams Robert@CustodianDC.com
wrote:
Hi,
Thanks for the input, I've just tried a discovery but no change.
The categories of good sensors are:
Processor Memory Storage Current Power Temperature Voltage
but nothing for 'Status':
##### Module Start: status #####
o Status Count 0 o Module time 0.0009s
It's running 5.2.1 by the way.
Cheers,
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Nikolay Shopik Sent: 20 January 2016 11:07 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
I would like to add 4.x releases doesn't expose lot of sensors, they
did
improve that in 5.2 IOS-XR iirc
On 20/01/16 13:59, Frederic Gargula wrote:
Hi Robert,
We figured out that, in order to see the fans and power, we needed to force a manual discovery of our ASR9K from the command-line. I hope
this
helps.
Best regards,
Frederic Gargula IP-Max SA
On 20 Jan 2016, at 11:43, Robert Williams Robert@CustodianDC.com wrote:
Hi,
I’ve just noticed that fan failures on the ASR 9k are not detected by Observium. In fact, it seems have nothing at all under the ‘status’
tab?
The 6500s have over 20 entries in there for “Fan - Fail” or “PSU - Fail” or “I’m not facing magnetic north - Fail” etc. but the ASR9000 have no status tab whatsoever.
Reason for noticing this; is that we have a chassis which currently has a ‘Major-Alarm’ failure indicator LED on the RSP, due to a failed fan tray. Observium shows the device has being ‘OK’ and is not seeing either the Major alarm or the fan tray failure:
canb-server[151]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
LED Information
R/S/I Modules LED Status 0/RSP0/* host Critical-Alarm Off host Major-Alarm On host Minor-Alarm Off host ACO Off host Fail Off
FAN0 FAN1 FAN2 FAN3 FAN4 FAN5 FAN6 FAN7FAN8 FAN9 FAN10 FAN11 FAN12 FAN13
0/FT0/* (Speed) 9900 9900 9870 9780 9870 9780 9780 10080 10080 9870 9990 9900 9810 9990
(fans are now OK again)
Is this a case of Cisco not exporting any of this useful (and rather critical) information properly? Would be good to graph fan speeds if they are exported. Or are other people getting these OK and it’s just
us
with the issue?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
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
On Wed, Jan 20, 2016 at 01:59:17PM +0000, Robert Williams wrote:
Hi Frederic - I’m curious what IOS-XR version was running where you are seeing the fan speed results showing correctly?
Strangely, I *was* getting fanspeed/current on my 5.1.3 ASR9001s until sometime in mid-October, when apparently we did svn up and it stopped working.
Brandon - that's very interesting, I assume you didn’t do an IOS upgrade around then?
Adam - is there anything that springs to mind for why this would have stopped working in October? Maybe ours used to be in there also at some point?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Brandon Ewing Sent: 20 January 2016 16:03 To: observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
On Wed, Jan 20, 2016 at 01:59:17PM +0000, Robert Williams wrote:
Hi Frederic - I’m curious what IOS-XR version was running where you
are seeing the fan speed results showing correctly?
Strangely, I *was* getting fanspeed/current on my 5.1.3 ASR9001s until sometime in mid-October, when apparently we did svn up and it stopped working.
-- Brandon Ewing (nicotine@warningg.com)
On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS upgrade around then?
Adam - is there anything that springs to mind for why this would have stopped working in October? Maybe ours used to be in there also at some point?
Turns out I'm an idiot, and we disabled the sensors module while working on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
I thought it might be something like this. There's not really much scope for some sensors randomly stopping working, especially since I don't think anyone has touched the CISCO-ENTITY-SENSOR-MIB code for a very, very long time :)
adam. On 20/01/2016 18:04:39, Brandon Ewing nicotine@warningg.com wrote: On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS upgrade around then?
Adam - is there anything that springs to mind for why this would have stopped working in October? Maybe ours used to be in there also at some point?
Turns out I'm an idiot, and we disabled the sensors module while working on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
-- Brandon Ewing (nicotine@warningg.com) _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
Thanks for that, unfortunately we already have all modules enabled, including Sensors, are running 5.3.1 (and now testing with 5.3.2 in the lab as well) but still cannot get any sensors at all on 9001 or 9006 chassis :(
Are there any debug outputs or snmpwalks that would help anyone see why this doesn't work for us?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Brandon Ewing Sent: 20 January 2016 18:04 To: observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS
upgrade around then?
Adam - is there anything that springs to mind for why this would have
stopped working in October? Maybe ours used to be in there also at some point?
Turns out I'm an idiot, and we disabled the sensors module while working on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
-- Brandon Ewing (nicotine@warningg.com)
Hi Robert,
That’s strange. Can you make sure you have "snmp-server community ********* SystemOwner IPv4 SNMP-IPV4” in your config ?
The “SystemOwner” keyword is important.
Best regards,
Frederic Gargula IP-Max SA
On 21 Jan 2016, at 11:46, Robert Williams Robert@CustodianDC.com wrote:
Hi,
Thanks for that, unfortunately we already have all modules enabled, including Sensors, are running 5.3.1 (and now testing with 5.3.2 in the lab as well) but still cannot get any sensors at all on 9001 or 9006 chassis :(
Are there any debug outputs or snmpwalks that would help anyone see why this doesn't work for us?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Brandon Ewing Sent: 20 January 2016 18:04 To: observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS
upgrade around then?
Adam - is there anything that springs to mind for why this would have
stopped working in October? Maybe ours used to be in there also at some point?
Turns out I'm an idiot, and we disabled the sensors module while working on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
-- Brandon Ewing (nicotine@warningg.com)
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Frederic,
Thank you so much for that gem of information. The 'systemowner' keyword has allowed Observium to suddenly detect:
2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 66237848 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 57269142 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Power Module Capacity Sensor - capacity 0/PM0/2/SPSensor added: power cisco-entity-sensor 56384724 Power Module Capacity Sensor - capacity 0/PM0/2/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 55495795 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:53 Power Module Current - 0/PM0/0/SPSensor added: current cisco-entity-sensor 53687180 Power Module Current - 0/PM0/0/SP 2016-01-21 14:51:53 Power Module Current - 0/PM0/1/SPSensor added: current cisco-entity-sensor 49413261 Power Module Current - 0/PM0/1/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 44949055 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Power Module Voltage - 0/PM0/2/SPSensor added: voltage cisco-entity-sensor 39607111 Power Module Voltage - 0/PM0/2/SP 2016-01-21 14:51:52 Power Module Current - 0/PM0/3/SPSensor added: current cisco-entity-sensor 39039503 Power Module Current - 0/PM0/3/SP 2016-01-21 14:51:52 Power Module Voltage - 0/PM0/1/SPSensor added: voltage cisco-entity-sensor 32635680 Power Module Voltage - 0/PM0/1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 28612240 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 23403447 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Power Module Current - 0/PM0/2/SPSensor added: current cisco-entity-sensor 22831118 Power Module Current - 0/PM0/2/SP 2016-01-21 14:51:52 Power Module Voltage - 0/PM0/3/SPSensor added: voltage cisco-entity-sensor 22263542 Power Module Voltage - 0/PM0/3/SP 2016-01-21 14:51:52 Power Module Capacity Sensor - capacity 0/PM0/0/SPSensor added: power cisco-entity-sensor 20133606 Power Module Capacity Sensor - capacity 0/PM0/0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 17977066 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Power Module Capacity Sensor - capacity 0/PM0/1/SPSensor added: power cisco-entity-sensor 15858003 Power Module Capacity Sensor - capacity 0/PM0/1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 15177601 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 13805629 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 13443524 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 11741762 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:51 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 6869781 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:51 Power Module Capacity Sensor - capacity 0/PM0/3/SPSensor added: power cisco-entity-sensor 5485929 Power Module Capacity Sensor - capacity 0/PM0/3/SP 2016-01-21 14:51:51 Power Module Voltage - 0/PM0/0/SPSensor added: voltage cisco-entity-sensor 3355929 Power Module Voltage - 0/PM0/0/SP
So whilst it still doesn’t include any "Alarm Status" indicators, we can now at least see a failed fan from setting thresholds on the speeds!!
Many thanks :)
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Frederic Gargula Sent: 21 January 2016 12:59 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
Hi Robert,
That’s strange. Can you make sure you have "snmp-server community ********* SystemOwner IPv4 SNMP-IPV4” in your config ?
The “SystemOwner” keyword is important.
Best regards,
Frederic Gargula IP-Max SA
On 21 Jan 2016, at 11:46, Robert Williams Robert@CustodianDC.com
wrote:
Hi,
Thanks for that, unfortunately we already have all modules enabled,
including Sensors, are running 5.3.1 (and now testing with 5.3.2 in the lab as well) but still cannot get any sensors at all on 9001 or 9006 chassis :(
Are there any debug outputs or snmpwalks that would help anyone see
why this doesn't work for us?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Brandon Ewing Sent: 20 January 2016 18:04 To: observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS
upgrade around then?
Adam - is there anything that springs to mind for why this would
have
stopped working in October? Maybe ours used to be in there also at
some
point?
Turns out I'm an idiot, and we disabled the sensors module while
working
on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
-- Brandon Ewing (nicotine@warningg.com)
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Well that's interesting. What's the motivation behind requiring a specific setting to see fan speeds and voltages? oO
adam. On 21/01/2016 14:58:15, Robert Williams robert@custodiandc.com wrote: Hi Frederic,
Thank you so much for that gem of information. The 'systemowner' keyword has allowed Observium to suddenly detect:
2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 66237848 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 57269142 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Power Module Capacity Sensor - capacity 0/PM0/2/SPSensor added: power cisco-entity-sensor 56384724 Power Module Capacity Sensor - capacity 0/PM0/2/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 55495795 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:53 Power Module Current - 0/PM0/0/SPSensor added: current cisco-entity-sensor 53687180 Power Module Current - 0/PM0/0/SP 2016-01-21 14:51:53 Power Module Current - 0/PM0/1/SPSensor added: current cisco-entity-sensor 49413261 Power Module Current - 0/PM0/1/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 44949055 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Power Module Voltage - 0/PM0/2/SPSensor added: voltage cisco-entity-sensor 39607111 Power Module Voltage - 0/PM0/2/SP 2016-01-21 14:51:52 Power Module Current - 0/PM0/3/SPSensor added: current cisco-entity-sensor 39039503 Power Module Current - 0/PM0/3/SP 2016-01-21 14:51:52 Power Module Voltage - 0/PM0/1/SPSensor added: voltage cisco-entity-sensor 32635680 Power Module Voltage - 0/PM0/1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 28612240 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 23403447 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Power Module Current - 0/PM0/2/SPSensor added: current cisco-entity-sensor 22831118 Power Module Current - 0/PM0/2/SP 2016-01-21 14:51:52 Power Module Voltage - 0/PM0/3/SPSensor added: voltage cisco-entity-sensor 22263542 Power Module Voltage - 0/PM0/3/SP 2016-01-21 14:51:52 Power Module Capacity Sensor - capacity 0/PM0/0/SPSensor added: power cisco-entity-sensor 20133606 Power Module Capacity Sensor - capacity 0/PM0/0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 17977066 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Power Module Capacity Sensor - capacity 0/PM0/1/SPSensor added: power cisco-entity-sensor 15858003 Power Module Capacity Sensor - capacity 0/PM0/1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 15177601 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 13805629 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 13443524 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 11741762 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:51 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 6869781 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:51 Power Module Capacity Sensor - capacity 0/PM0/3/SPSensor added: power cisco-entity-sensor 5485929 Power Module Capacity Sensor - capacity 0/PM0/3/SP 2016-01-21 14:51:51 Power Module Voltage - 0/PM0/0/SPSensor added: voltage cisco-entity-sensor 3355929 Power Module Voltage - 0/PM0/0/SP
So whilst it still doesn’t include any "Alarm Status" indicators, we can now at least see a failed fan from setting thresholds on the speeds!!
Many thanks :)
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Frederic Gargula Sent: 21 January 2016 12:59 To: Observium Network Observation System Subject: Re: [Observium] ASR9k fan failures not detected?
Hi Robert,
That’s strange. Can you make sure you have "snmp-server community ********* SystemOwner IPv4 SNMP-IPV4” in your config ?
The “SystemOwner” keyword is important.
Best regards,
Frederic Gargula IP-Max SA
On 21 Jan 2016, at 11:46, Robert Williams
wrote:
Hi,
Thanks for that, unfortunately we already have all modules enabled,
including Sensors, are running 5.3.1 (and now testing with 5.3.2 in the lab as well) but still cannot get any sensors at all on 9001 or 9006 chassis :(
Are there any debug outputs or snmpwalks that would help anyone see
why this doesn't work for us?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Brandon Ewing Sent: 20 January 2016 18:04 To: observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS
upgrade around then?
Adam - is there anything that springs to mind for why this would
have
stopped working in October? Maybe ours used to be in there also at
some
point?
Turns out I'm an idiot, and we disabled the sensors module while
working
on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
-- Brandon Ewing (nicotine@warningg.com)
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
Indeed…. Never even seen that command until today….!
I’ll ask them when I eventually get someone useful on the TAC case about where the Major/Minor alarms are exported ☺
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: 21 January 2016 18:03 To: observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
Well that's interesting. What's the motivation behind requiring a specific setting to see fan speeds and voltages? oO
adam.
On 21/01/2016 14:58:15, Robert Williams <robert@custodiandc.commailto:robert@custodiandc.com> wrote: Hi Frederic,
Thank you so much for that gem of information. The 'systemowner' keyword has allowed Observium to suddenly detect:
2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 66237848 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 57269142 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Power Module Capacity Sensor - capacity 0/PM0/2/SPSensor added: power cisco-entity-sensor 56384724 Power Module Capacity Sensor - capacity 0/PM0/2/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 55495795 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:53 Power Module Current - 0/PM0/0/SPSensor added: current cisco-entity-sensor 53687180 Power Module Current - 0/PM0/0/SP 2016-01-21 14:51:53 Power Module Current - 0/PM0/1/SPSensor added: current cisco-entity-sensor 49413261 Power Module Current - 0/PM0/1/SP 2016-01-21 14:51:53 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 44949055 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:53 Power Module Voltage - 0/PM0/2/SPSensor added: voltage cisco-entity-sensor 39607111 Power Module Voltage - 0/PM0/2/SP 2016-01-21 14:51:52 Power Module Current - 0/PM0/3/SPSensor added: current cisco-entity-sensor 39039503 Power Module Current - 0/PM0/3/SP 2016-01-21 14:51:52 Power Module Voltage - 0/PM0/1/SPSensor added: voltage cisco-entity-sensor 32635680 Power Module Voltage - 0/PM0/1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 28612240 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 23403447 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Power Module Current - 0/PM0/2/SPSensor added: current cisco-entity-sensor 22831118 Power Module Current - 0/PM0/2/SP 2016-01-21 14:51:52 Power Module Voltage - 0/PM0/3/SPSensor added: voltage cisco-entity-sensor 22263542 Power Module Voltage - 0/PM0/3/SP 2016-01-21 14:51:52 Power Module Capacity Sensor - capacity 0/PM0/0/SPSensor added: power cisco-entity-sensor 20133606 Power Module Capacity Sensor - capacity 0/PM0/0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 17977066 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Power Module Capacity Sensor - capacity 0/PM0/1/SPSensor added: power cisco-entity-sensor 15858003 Power Module Capacity Sensor - capacity 0/PM0/1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 15177601 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT0/SPSensor added: fanspeed cisco-entity-sensor 13805629 Fan Speed Sensor - speed 0/FT0/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 13443524 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:52 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 11741762 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:51 Fan Speed Sensor - speed 0/FT1/SPSensor added: fanspeed cisco-entity-sensor 6869781 Fan Speed Sensor - speed 0/FT1/SP 2016-01-21 14:51:51 Power Module Capacity Sensor - capacity 0/PM0/3/SPSensor added: power cisco-entity-sensor 5485929 Power Module Capacity Sensor - capacity 0/PM0/3/SP 2016-01-21 14:51:51 Power Module Voltage - 0/PM0/0/SPSensor added: voltage cisco-entity-sensor 3355929 Power Module Voltage - 0/PM0/0/SP
So whilst it still doesn’t include any "Alarm Status" indicators, we can now at least see a failed fan from setting thresholds on the speeds!!
Many thanks :)
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Frederic Gargula Sent: 21 January 2016 12:59 To: Observium Network Observation System Subject: Re: [Observium] ASR9k fan failures not detected?
Hi Robert,
That’s strange. Can you make sure you have "snmp-server community ********* SystemOwner IPv4 SNMP-IPV4” in your config ?
The “SystemOwner” keyword is important.
Best regards,
Frederic Gargula IP-Max SA
On 21 Jan 2016, at 11:46, Robert Williams
wrote:
Hi,
Thanks for that, unfortunately we already have all modules enabled,
including Sensors, are running 5.3.1 (and now testing with 5.3.2 in the lab as well) but still cannot get any sensors at all on 9001 or 9006 chassis :(
Are there any debug outputs or snmpwalks that would help anyone see
why this doesn't work for us?
Cheers!
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.commailto:Robert@CustodianDC.com http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Brandon Ewing Sent: 20 January 2016 18:04 To: observium@observium.orgmailto:observium@observium.org Subject: Re: [Observium] ASR9k fan failures not detected?
On Wed, Jan 20, 2016 at 04:57:23PM +0000, Robert Williams wrote:
Brandon - that's very interesting, I assume you didn’t do an IOS
upgrade around then?
Adam - is there anything that springs to mind for why this would
have
stopped working in October? Maybe ours used to be in there also at
some
point?
Turns out I'm an idiot, and we disabled the sensors module while
working
on polling speed, as leaving it enabled was driving us WELL past 300 seconds for a polling round, even with 64+ workers.
Flipped it back on for testing, confirmed sensors work in 5.1.3 and 5.3.1.
-- Brandon Ewing (nicotine@warningg.commailto:nicotine@warningg.com)
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On Thu, Jan 21, 2016 at 06:03:28PM +0000, Adam Armstrong wrote:
Well that's interesting. What's the motivation behind requiring a specific setting to see fan speeds and voltages? oO
adam.
IOS-XR has the concept of SDR (secure domain routers), which allows you to logically split a chassis-based system (or multi-chassis CRS system) into multiple logical routers managed by different groups. Only the owners of the chassis (SystemOwner) would be allowed to read the data.
participants (6)
-
Adam Armstrong -
Brandon Ewing -
Frederic Gargula -
Markus Klock -
Nikolay Shopik -
Robert Williams