OmniVista 2500 4.4R1 discoveres Switches with wrong IP

[gear0]

Hello everyone,

I have a Problem according to the discovery of Switches with OmniVista 2500 4.4R1 (Build 58).
The Problem is that OmniVista discovers some of our OS6860E Switches with the wrong IP.
For example we have a switch with management IP address of 10.63.52.101/24 but OmniVista discovers
this switch with its actual management IP address and with the IP address 10.63.52.255 (which is selected by default).
I can change the IP address in OmniVista (through "Edit Discovery Manager Entry") to the actual IP address, but after
a scheduled rediscovery the switch shows up with IP address 10.63.52.255.
This behaviour is only shown by a few OS6860E Switches.
Any ideas how to solve this problem?

If you need more information, please let me know.

[silvio]

The discovery ranges in OV should only cover the management ip's.
In the switches (with more than one ip interface) change the source-ip of service snmp to the management interface.
regards
Silvio

[gear0]

Hi Silvio,

thanks for the answer. I'll try your suggestion and report the result. What I find a little strange is that the switch doesn't have the address 10.63.52.255 and it is however listed at the addresses of the switch. As soon as I adjust the address of the switch in OmniVista, the address 10.63.52.255 disappears from the selection options.

[silvio]

I assume that this address is a broadcast address? Normaly I use for an /24 net the range up to .254
But, you are right: no normal behavior. But if it solved now all is okay.
best regards
Silvio

[gear0]

Hi Silvio,

unfortunately, the problem still persists. Tonight was another Full Discovery. The switches where I had set the service source-ip are displayed again with the .255 address in OmniVista.

You assume right, these addresses are broadcast addresses. Maybe I should try setting the discovery ranges only up to .254.

best regards
gear0

[silvio]

I hope that this will help. Otherwise you has to check with wireshark the packets from the switches to the ov-server.
regards
Silvio

[gear0]

For the record. I changed the discovery ranges to exclude broadcast addresses and the problem is gone.
Thanks for your help.

Edit: Is there a way to mark this thread as solved?