---

Subject:	Have you ran a ping test from
Author:	[Not Specified]
Posted:	2014-06-04 09:22

Have you ran a ping test from the zenoss server to the "DMZ Server" for an hour or two to see if there is a lot of packet loss Also is the "DMZ Server" being slammed from the outside Any interfaces maxed or with errors

Hydruid

---

Subject:	You're Welcome! You'll figure
Author:	[Not Specified]
Posted:	2014-06-06 08:07

You're Welcome! You'll figure it out, just dig deep. It's most likely not a zenoss issue but latency across the firewall or WAN or somewhere in between!

Hydruid

---

Subject:	I was able to test this: No
Author:	[Not Specified]
Posted:	2014-06-10 05:27

I was able to test this: No errors on the interface and not a single ping that took more than 0.5 ms (in fact they were all around 0.3 ms)

What struck to me: on our target server theres no route back to the zenoss server. ping from zenossserver to target works perfect like snmpwalk and zenperfsnmp from both, command line and the frontend. ping from targetserver to zenossserver doesn't work.

Is it possible, that zenoss needs a route from the target server back to zenossserver Does it send packets on its own to zenossserver (not just replies)

thanks again for your help, much appreciated.

---

Subject:	Ok I was able to narrow the
Author:	[Not Specified]
Posted:	2014-09-10 06:27

Ok I was able to narrow the problem down:

We use snmp v3 with AES what works on almost all hosts. only one is screwed. After I switched to snmp v2c on the faulty host, everything began to work fine. Then black magic struck:

After switching back to snmp v3 it still worked. but all of a sudden another server had exactly the behaviour and errors as our first server before.

I did switch to snmp v2c on this second server and back to snmp v3 and all of a sudden, it was again the first server again throwing exactly the same errors.

Well what have this servers in common The second server is a VMWare-Clone of the first with changes to networking and and others. But it seems that for some reasons zenoss is not happy with the fact that they are clones.

Whats noteworthy:
- I deleted both nodes completely out of zenoss (via webfrontend) and reintegrated them. to no avail.
- I removed and reinstalled on both nodes net-snmp package.
- i did check the zenoss installation with the toolboxtools: zodbscan, zenchkrels, zencatalogscan, findposkeyerror. to no avail.

I looked for a way to manually manipulate the mysql-db and to manually delete the device because I fear that the webfrontend deletion of the device does not delete all the stuff.

Could anyone provide me some insight about doing so Or could anyone provide me a way to delete it via a zendmd-script

Thank you very much.

---

Subject:	Friendlypenguin:
Author:	Andrew Kirch
Posted:	2014-09-11 08:52

Friendlypenguin:

did mac addresses and similar get changed Something is causing Zenoss confusion with regard to indexing these hosts. I recommend against manually editing the database ever as it can cause corruption. Would you mind hopping on IRC and I'll take a closer look at this

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

---

Subject:	^^ Above advice is
Author:	[Not Specified]
Posted:	2016-07-12 17:19

^^ Above advice is destructive !!

Do not execute'yum remove -y net-snmp' unless you are prepared to see zenoss uninstalled.

Instead, you can do:

service snmpd stop
rm/var/lib/net-snmp/snmpd.conf
yum reinstall net-snmp
service snmpd start

After this,you should see new values for 'setserialno' and 'oldEngineID'