How to Work with Virtual IP addresses

[Philippe Gagne]

Hi guys,

Could you tell me what is the best practice to work with clusters & VIP and how to avoid having alarms with no meaning (like OV_ARPChgNewPhysAddr event) caused by the VIPs.

There is many platforms set in cluster in the network I work in. This means I have a lot of virtual IP addresses (VIP). Those VIP generate a lot OV_ARPChgNewPhysAddr events which make no sense since a VIP don't neccessary have there own MAC address. Setting "netmon.noDiscover" file accordingly is not appropriate since I still want to see those VIP.

[Joaquin Gil de Vergara]

you can assign multiple IP address to a lan card

only be carefull not to assign IP to idle lan card (backup lan card from MC/SG)

not assign IP in the same subnet to varios interfaces, IPs in the same subnet always must be over the same card

you can identify idle card with netstat -in marked with *


#netstat -in
Name Mtu Network Address Ipkts Opkts
lan0:1 1500 128.1.96.0 128.1.98.129 9259959 52541
lan0 1500 128.1.96.0 128.1.99.128 66878122 338257205
lo0 4136 127.0.0.0 127.0.0.1 128916391 128916393
#

to assign multiple IP's to a lan interface add the : suffix

[Wodisch_1]

Hi Phillipe,

why not simply copy these events in NNM, make them work only for the IP-addresses you use for the cluster packages, and set those events to "don't log or display"...

Just my $0.02,
Wodisch

[Philippe Gagne]

Thanks guys for the replies. I beleive the setting you suggested is the only thing I can do for the moment. If you have further information to give to me I would appreciate.

Here is an example of a cluster:

Virtual IP
/ / IP managementA IP managementB
IP InterfaceA IP InterfaceB
\ /
\ /
IP Virtual Interface

Openview sees some IP correctly as interfaces of the corresponding platform but don't treat properly Virtual IPs and don't realized there is a cluster. It would be great if it could do so... (with an add-on or something)...