Ad Widget

Collapse

Timeout with cisco devices

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fssilva
    Junior Member
    • Feb 2024
    • 3

    #1

    Timeout with cisco devices

    Hello all,

    I (HAD) a working environment working fine with around 280 network cisco switches until last days, them I decided to upgrade both zabbix to 7.4.2 (it was 7.4.1) and it's templates (not sure which version the template was before). It was running fine for the last maybe 2 years that was installed? More or less like that..

    After that there was no more graphics getting generated and checking the logs, I could see that there was so many timeouts in the logs... I deployed another server (fresh one, with ubuntu and latest version of zabbix, thinking there was some problem with the other server). the server (new) works fine if I leave only one device enabled, as soon I enable more, I get the same errors.

    I have increased the timeout values in the gui, to 3 minutes under SNMP checks and it still continue like that.

    The template I use is the standard "Cisco IOS by SNMP" and I have changed the lower period to at least 3 minutes and not getting data every 1 min as the standard.
    And others are set to higher values since the hostname, serial number and location for example doesn't change, so it will check once every 1 day only.

    It happens for all devices and looks like it affects only the interface snmp walk information... as the other information like temperature, fan, psu, and so on are getting data without any problem....

    If I do a snmpwalk from the cli to the "time out" OID... all works fine.. it is using snmp v2... either in cli and zabbix...

    Below some outputs of the logs.. I changed the hostname and IP just in case.

    5902:20250828:163827.906 error reason for "host.localnet:net.if.out[ifHCOutOctets.274]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.31.1.1.1.1.61' from [[10.10.10.10]:161]: timed out
    5902:20250828:163827.906 error reason for "host.localnet:net.if.out[ifHCOutOctets.209]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.31.1.1.1.1.61' from [[10.10.10.10]:161]: timed out
    5902:20250828:163827.906 error reason for "host.localnet:net.if.out[ifHCOutOctets.154]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.31.1.1.1.1.61' from [[10.10.10.10]:161]: timed out
    5902:20250828:163827.906 item "host.localnet:net.if.speed[ifHighSpeed.308]" became not supported: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.31.1.1.1.1.61' from [[10.10.10.10]:161]: timed out
    5902:20250828:163827.906 item "host.localnet:net.if.speed[ifHighSpeed.452]" became not supported: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.31.1.1.1.1.61' from [[10.10.10.10]:161]: timed out
    5902:20250828:163827.906 item "host.localnet:net.if.speed[ifHighSpeed.407]" became not supported: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.31.1.1.1.1.61' from [[10.10.10.10]:161]: timed out

    4200:20250828:122425.131 error reason for "host.localnet:net.if.type[ifType.98]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.14.31' from [[10.10.10.10]:161]: timed out
    4200:20250828:122425.131 error reason for "host.localnet:net.if.type[ifType.28]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.14.31' from [[10.10.10.10]:161]: timed out
    4200:20250828:122425.131 error reason for "host.localnet:net.if.type[ifType.119]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.14.31' from [[10.10.10.10]:161]: timed out
    4200:20250828:122425.131 error reason for "host.localnet:net.if.type[ifType.603]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.14.31' from [[10.10.10.10]:161]: timed out
    4200:20250828:122425.131 error reason for "host.localnet:net.if.type[ifType.542]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.14.31' from [[10.10.10.10]:161]: timed out


    1542:20250828:121127.872 error reason for "host2.localnet:net.if.duplex[dot3StatsDuplexStatus.43]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.2.30' from [[10.10.10.12]:161]: timed out
    1542:20250828:121127.872 error reason for "host2.localnet:net.if.duplex[dot3StatsDuplexStatus.35]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.2.30' from [[10.10.10.12]:161]: timed out
    1542:20250828:121127.872 error reason for "host2.localnet:net.if.duplex[dot3StatsDuplexStatus.17]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.2.30' from [[10.10.10.12]:161]: timed out
    1542:20250828:121127.872 error reason for "host2.localnet:net.if.duplex[dot3StatsDuplexStatus.59]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.2.30' from [[10.10.10.12]:161]: timed out
    1542:20250828:121127.872 error reason for "host2.localnet:net.if.duplex[dot3StatsDuplexStatus.51]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.2.30' from [[10.10.10.12]:161]: timed out
    1542:20250828:121127.872 error reason for "host2.localnet:net.if.duplex[dot3StatsDuplexStatus.16]" changed: only partial data received, cannot retrieve OID: '.1.3.6.1.2.1.2.2.1.2.30' from [[10.10.10.12]:161]: timed out


    Any tip/idea what could be causing that?
    Thank you
  • fssilva
    Junior Member
    • Feb 2024
    • 3

    #2
    Hello, just an update, as said, I updated everything.. and the problem was with the update interval of the templates... the specific one for nexus 9000 was overloading the snmp agent.. even with high timeout settings.. it was very slow to complete... after I changed the update interval of it, and also changed some update interval from the cisco ios by snmp to longer periods... all restored to normal operation again... and server is working fine again....

    Comment

    Working...