Problem SNMP polling on Omnivista NMS

[wolverineZena]

Hi,
I ha ve a "SNMP polling problem" on Omnivista 2500 NMS.
Every 4/5 minutes Omnivista generates these two notifications about many different switches (different Model and different firmware version):
- alaOvSwitchDown Switch has STOPPED responding to OmniVista: Couldn't send SNMP message (Timeout or Authentication Problem).
- alaOvSwitchUp Switch has resumed responding to OmniVista.

This continuos UP & DOWN of switches doesn't allow me to monitot the real status of my network (over 200 devices recorded in Omnivista).
Devices aren't really DOWN, in fact if I didn't wait the notification "alaOvSwitchUp", but manually polling the node, it become UP again!
Can someone help me?

Thanks

Andrea

[a3093]

hello Andrea,

could you fix it? I have the same problem.

thanks

[strelok]

Hello, guys.

I have the same problem on Omnivista 2500, ver.3.5.6
Did anybody find root cause of problem ?

I captured trace from Omnivista side, but did not find not responded requests (
I am still trying to find problem.

Alex.

[virat07ec]

Hi,

Could you try increasing the SNMP timeout values and check for the issue?

[strelok]

Hello virat07ec.

I solved this problem by disabling polling. (you can find button for enabling/disabling on the top of panel).

[Mi0]

Hi,

what's the reason to receiving such message, server is slow, incorrect setting or simple bug? I have the same problem, but I'm not sure if I disable polling, it will definitly solved my problem.

Thanks

[strelok]

Hi,

I think it could be follwoing reasons:

1. Slow server
2. Too big amount requests (polling).

After I increased perfomance of our OmniVista server problem was still exist.
I just disabled polling and problem has gone.

But I belive that problem can be solved by dicreasing polling interval.
So, I will try today/tommorow and let you know about result, if you interesting.

[MarkusOS]

Hi guys,

i guess you run in an old Problem.
Please check your time Settings.
The Problem appears when the time on the omnivista Server is different to Switch time.
The best solution is to use ntp Server. But check time after aos update. In a few cases some Switches are in the future after aos update!

hope it helps

regards
Markus

[strelok]

Hi guys,

We have again problem with snmp polling.

A lot of messages in Notifications:

- alaOvSwitchDown Switch has STOPPED responding to OmniVista: Couldn't send SNMP message (Timeout or Authentication Problem).
- alaOvSwitchUp Switch has resumed responding to OmniVista.

We noted that problem starts when enabled Polling functions on OmniVista server. As result all resources of server (vitual machine) CPU and memory are consumed by Java process. 100% CPU utilization. We added 2 then 4 then 6 cores for this server but all resources were consumed without remainder.

So, the main problem is java process (generated by OmniVista) consume all resources. As result server can't work properly and didn't catch (handle) snmp responeses from swithces.

So, may be somebody faced the same behavior ?