On 2 of my 5 VCSA 6.0 appliances, SNMP polls are not working. VCSA is 6.0 build 2656761 on all. The non-working ones are using an external PSC (another VCSA) which appears to be the only difference. Commands I used...
*Community string replaced for this post
Command> snmp.set --communities myCommunityString
Command> snmp.enable
When I use the Windows tool MIB walk with myCommunityString, it fails the test immediately. It works fine on my other 3 VCSAs. I have logged into the shell and verified snmpd service is running.
Anyone know what is incorrect?
Hi Matt,
Just saw this same issue reported elsewhere. Using strace and see that it stalls, then eats cpu.
So its going to take a fix to the vmware-snmp rpm for that platform.
Having this exact same issue.. do you know if there is a patch or a KB out for this issue?
Same problem here.
VCSA appliance with embedded PSC - Managed to set SNMP no problems.
VCSA with External Load Balanced HA PSC (Citrix Netscaler) wont respond.
All running on the same build. Going to log a call with VMware and see what they say.
Adam
1) Enter Appliance Shell (if you are not already)
1 | chsh -s /bin/appliancesh root |
2) log out, log back in. (depending on above)
3) If SNMP is not currently enabled you wont be able to progress, so enable it:
1 | snmp.enable |
3) Set the communities (seperated by commas)
1 | snmp. set --communities whatever |
Sorry to resurface the old thread, but I am facing the same issue.
Did anyone found a workaround for this?
Thanks
Kapil
Also have this issue.
SNMP polling not work on vCenter Server Appliance 6.0.0.20000
Hi all, please see the KB articles below. I was affected by the first issue and then the second after the upgrade to update 2. We have 3 VCSA's all with an external PSC. Please note that, after the VCSA/PSC upgrade from 6.0 u1 to 6.0 u2, SNMP does work initially. Then after a while it consumes 100% CPU and stops responding. Doesn't look like VMWare have a fix for the second issue yet. I have just opened an SR for it.
This issue is now fixed in 6.0 U2a
This problem also occurred on VCSA 6.0 U2
I have updated to VCSA 6.0 U3 all problem fixed