Quantcast
Channel: Zenoss Community : All Content - All Communities
Viewing all articles
Browse latest Browse all 853

Zenping correlation problem 4.2.3

$
0
0

Hi all,

 

sicne I have updated our zenoss form 3.2.1 to 4.2.3 layer3 correlation between devices doesn't work.

When remote site goes down zenoss is sending several alerts insted of one for a router.

For example:

 

tracepath.py Server-Bydgoszcz

Getting path from zenoss to Server-Bydgoszcz...

zenoss -> SC10 -> fw-a -> 192.168.16.4 -> Router_Bydgoszcz -> Server-Bydgoszcz

 

tracepath.py Router_Bydgoszcz

Getting path from zenoss to Router_Bydgoszcz...

zenoss -> SC10 -> fw-a -> 192.168.16.4 -> Router_Bydgoszcz

 

In 3.2.1 alert was sent for Router_Bydgoszcz only, in 4.2.3 - two alerts for Server-Bydgoszcz and Router_Bydgoszcz

Is it a bug??

 

Zenping configuration:

duallog False

allowduplicateclears False

zenhubpinginterval 30

ping-backend nmap

watchdog False

eventflushseconds 5.0

hubhost localhost

traceroute-interval 5

monitor localhost

hubusername admin

maxqueuelen 5000

duplicateclearinterval 0

initialHubTimeout 30

logseverity 20

maxlogsize 10240

disable-correlator False

maxbackuplogs 3

connected-ip-suppress True

maxparallel 500

logTaskStats 0

disable-event-deduplication False

eventflushchunksize 50

hubport 8789


Viewing all articles
Browse latest Browse all 853

Trending Articles