Zabbix permanent SNMP "Not Supported" after restart

[Rudolfmdlt]

Hi All,

I am monitoring Centos 6.4 and Asterisk 1.8.22 with SNMP using a fresh Zabbix 2.0.6 server install.

The problem is that when the device is rebooted or a monitored service restarted, Zabbix server permanently disables the SNMP "probe"? I understand the SNMP service won't be able to provide a response while it is rebooting, but surely it is not up to the zabbix server to automatically stop querying? Is there any way to turn this off or to force checks to on?

Any help would greatly be appreciated!

Thanks,

Rudolf

[bagni]

Hi,
the probes was ever disabled or stops to work after asterisk restart?

Please check:

• Administration -> General -> Macros -> {$SNMP_COMMUNITY}
• snmpd service on asterisk host
• no firewall or firewall rule for snmp traffic on asterisk host

[Rudolfmdlt]

Hi Bagni,

Thank you for your reply:

Please check:
Administration -> General -> Macros -> {$SNMP_COMMUNITY}

-> public

snmpd service on asterisk host

-> The service works fine - I monitor other parameters as well.

no firewall or firewall rule for snmp traffic on asterisk host

-> IPtables and SELinux are both disabled.

The monitoring works fine, until I restart asterisk, after which the zabbix server stops monitoring with the error "Not Supported" next to the item - Please see the graph attached: I have highlighted the gap in data, which only resumed once I manually reset the "Not Supported" error to "Enabled".

From the Logfile:

  1752:20130612:150203.682 item [Office.PBX:PBX.Asterisk.Configuration.ReloadTime] became not supported: No Such Object available on this agent at this OID
  1752:20130612:150203.682 item [Office.PBX:PBX.Asterisk.Configuration.UpTime] became not supported: No Such Object available on this agent at this OID
  1757:20130612:150208.686 item [Office.PBX:PBX.Asterisk.Configuration.ActiveCalls] became not supported: No Such Object available on this agent at this OID

I assume SNMPD - the SNMPD agent running on Centos monitoring asterisk - returns this error while asterisk is restarted. Is there any way to force these checks to on?

Thank you for your time and help this far!

Regards,

Rudolf

[bagni]

Hi Rudolfmdlt,
there is an opened issue https://support.zabbix.com/browse/ZBXNEXT-1249 but anyway consider this: not supported is a safe mechanism to avoid system block.

Generally, on my environment, the not supported status happens, but sometimes the items come back to enabled automatically.

The only method to force (as I know) is chande manually not supported -> enabled, but the items fall back on scheduled queue, so is not immediate.

If you want know which items are in 'not supported' status use the filter capabilities on Items page.

Bye