WM3600 drops multiple snmp requests.

  • 0
  • 1
  • Problem
  • Updated 12 months ago
  • Not a Problem
Hi,

I am monitoring some clients via snmp using ZABBIX, from a certain number of requests a pause of a few seconds is introduced, I think this is due to some rule in the firewall.
Photo of Junio Calú

Junio Calú

  • 190 Points 100 badge 2x thumb

Posted 12 months ago

  • 0
  • 1
Photo of Christoph S.

Christoph S., Employee

  • 2,804 Points 2k badge 2x thumb
Hello Junio,

What firmware version are you running?
Is the best practises firewall policy implemented? Best practices firewall policy
Do you have a screenshot of what is happening or provide more details?

Please let us know how we can assist you on this.

Regards,

Chris
Photo of Junio Calú

Junio Calú

  • 190 Points 100 badge 2x thumb
Firmware version: WM3600-5.5.0.0-090R

Command output:

$ snmpwalk -v2c -c public 10.17.0.101 -On wingStatsDev

.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.89.54.223 = STRING: 0:4:96:59:36:df
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.18.136 = STRING: 0:4:96:66:12:88
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.54.56 = STRING: 0:4:96:66:36:38
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.32 = STRING: 0:4:96:66:9b:20
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.96 = STRING: 0:4:96:66:9b:60
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.100 = STRING: 0:4:96:66:9b:64
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.220 = STRING: 0:4:96:66:9b:dc
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.68 = STRING: 0:4:96:77:4a:44
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.132 = STRING: 0:4:96:77:4a:84
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.140 = STRING: 0:4:96:77:4a:8c
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.216 = STRING: 0:4:96:77:4a:d8
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.248 = STRING: 0:4:96:77:4a:f8
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.75.12 = STRING: 0:4:96:77:4b:c
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.75.44 = STRING: 0:4:96:77:4b:2c
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.75.48 = STRING: 0:4:96:77:4b:30
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.75.56 = STRING: 0:4:96:77:4b:38
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.75.84 = STRING: 0:4:96:77:4b:54
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.75.104 = STRING: 0:4:96:77:4b:68
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.76.128 = STRING: 0:4:96:77:4c:80
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.76.132 = STRING: 0:4:96:77:4c:84
Timeout: No Response from 10.17.0.101

After a few seconds:

$ snmpwalk -v2c -c public 10.17.0.101 -On wingStatsDev

.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.89.54.223 = STRING: 0:4:96:59:36:df
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.18.136 = STRING: 0:4:96:66:12:88
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.54.56 = STRING: 0:4:96:66:36:38
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.32 = STRING: 0:4:96:66:9b:20
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.96 = STRING: 0:4:96:66:9b:60
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.100 = STRING: 0:4:96:66:9b:64
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.102.155.220 = STRING: 0:4:96:66:9b:dc
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.68 = STRING: 0:4:96:77:4a:44
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.132 = STRING: 0:4:96:77:4a:84
.1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.140 = STRING: 0:4:96:77:4a:8c
Error in packet.
Reason: (genError) A general failure occured
Failed object: .1.3.6.1.4.1.1916.2.131.50.1.4.2.1.1.1.0.4.150.119.74.140
(Edited)