we have upgraded a ASG 220 from 7.501 to 7.504 yesterday night.
After that there is a strange problem with the snmp.
I connected today to the box and saw a load of 100% in the dashboard. When I check top on the console I found the following:
top - 18:26:57 up 1 day, 3 min, 1 user, load average: 0.53, 0.71, 0.93
Tasks: 99 total, 2 running, 95 sleeping, 0 stopped, 2 zombie
Cpu(s): 1.3%us, 0.3%sy, 97.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 1.3%si, 0.0%st
Mem: 1028204k total, 1001088k used, 27116k free, 96168k buffers
Swap: 1052248k total, 128k used, 1052120k free, 391556k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
12738 root 39 19 9400 5180 1732 R 98.5 0.5 0:38.12 snmpd
3301 root 16 0 14848 9592 2588 S 0.3 0.9 4:46.23 selfmonng.plx
1 root 16 0 720 284 244 S 0.0 0.0 0:00.86 init
2 root 34 19 0 0 0 S 0.0 0.0 0:00.02 ksoftirqd/0
3 root 10 -5 0 0 0 S 0.0 0.0 0:00.02 events/0
I've stopped snmp by the webgui and the load went back to 5%.
After that I started snmp againg and everything was ok. So I did a snmpwalk (snmpwalk -c public -v 2c 192.168.1.1) on my monitoring box.
I got the following output (only the relevant part):
IP-MIB::ipNetToPhysicalRowStatus.4.ipv4."192.168.1.20" = INTEGER: active(1)
IP-MIB::ipNetToPhysicalRowStatus.4.ipv4."192.168.1.30" = INTEGER: active(1)
IP-MIB::ipNetToPhysicalRowStatus.4.ipv4."192.168.1.40" = INTEGER: active(1)
IP-MIB::ipNetToPhysicalRowStatus.6.ipv4."192.168.0.25" = INTEGER: active(1)
IP-MIB::ipNetToPhysicalRowStatus.6.ipv4."192.168.0.36" = INTEGER: active(1)
Timeout: No Response from 192.168.1.1
The SNMPD was no longer answering. I've checked the top and it was the same as before: snmpd uses 98% of the CPU.
As temporary solution I've disabled snmpd but this is not the right way.
Is there another solution?
Best Regards
Marco
This thread was automatically locked due to age.
