Items not supported and I don't know why

[NeoFireRaziel]

Hello to all again. I'm facing the following problem:

When I go to see the items status in Zabbix 2.2.5 I found that many of them are marked as "Not supported", when I think that they must be perfectly supported. For example in a Cisco SG300 Gb switch I found this:

Inbound errors on interface gigabitethernet12 ------------- Not supported
Inbound errors on interface gigabitethernet8 -------------- Enabled

Incoming traffic on interface gigabitethernet20 (64 bits) --- Not supported
Incoming traffic on interface gigabitethernet19 (64 bits) --- Enabled

And the same for many other items...

The item configuration in both cases is the same and I'm using the default "SNMP Device" template. I really don't understand why some items work perfectly and why many others don't.

As always I really appreciate you help. Thanks a lot and best regards,

Mauro.

[NeoFireRaziel]

Sorry, I forgot to include a fragment of log from Zabbix Server:

13046:20150612:135245.693 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifHCOutOctets[Po1]" became not supported: No Such Instance currently exists at this OID
13046:20150612:135346.221 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifOutErrors[Po3]" became not supported: No Such Instance currently exists at this OID
13046:20150612:135649.249 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifHCInOctets[gigabitethernet12]" became not supported: No Such Instance currently exists at this OID
13046:20150612:135649.249 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifHCInOctets[gigabitethernet16]" became not supported: No Such Instance currently exists at this OID

The logs correspond to others item that are suffering the same issue.

Agan, thanks and best regards,

Mauro.

[LenR]

what does snmpget say?

[zabbixx]

Sorry, I forgot to include a fragment of log from Zabbix Server:

13046:20150612:135245.693 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifHCOutOctets[Po1]" became not supported: No Such Instance currently exists at this OID
13046:20150612:135346.221 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifOutErrors[Po3]" became not supported: No Such Instance currently exists at this OID
13046:20150612:135649.249 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifHCInOctets[gigabitethernet12]" became not supported: No Such Instance currently exists at this OID
13046:20150612:135649.249 item "Switch Cisco 2 - SG300-20 - TV Digital Salidas:ifHCInOctets[gigabitethernet16]" became not supported: No Such Instance currently exists at this OID

The logs correspond to others item that are suffering the same issue.

Agan, thanks and best regards,

Mauro.

you just have a OID mismatch!

how LenR says try to snmpget or snmpwalk of this value.

[LenR]

I've been told that many switches don't prioritize snmp, they prioritize network traffic. Most snmp devices work OK, but since they do, we never debug those :-)

The ones that fail will sometimes not answer, sometimes they don't like bulk queries and they will answer snmp at idle times and fail when busy.

I use the snmp commands to see if the device is functional, before debugging Zabbix.

[zabanist]

I've been told that many switches don't prioritize snmp, they prioritize network traffic. Most snmp devices work OK, but since they do, we never debug those :-)

The ones that fail will sometimes not answer, sometimes they don't like bulk queries and they will answer snmp at idle times and fail when busy.

I use the snmp commands to see if the device is functional, before debugging Zabbix.

Yes to this.

While it is rare for a switch to behave in such a manner, definitely do your due diligence and talk to the swtich via common commands (snmpget and snmpwalk). Without something sad and weird happening, it may simply be that your discovery rules need to run more often if the ifIndex is changing.