Virtual IP Relocated

Question

Hi Guys,
Quick question - I hope !
I have recently seen the following three critical alerts:
on Target abc2 CRS resource ora.scan3.vip was relocated to abc2
on Target abc2 CRS resource ora.scan2.vip was relocated to abc2
on Target abc1 CRS resource ora.scan1.vip was relocated to abc1
I have googled and googled this but can't find out if this is in fact a potential train smash or if I need to relocate them back.
We did have a failure last week and everything failed over but when the failed node was restarted ASM did not start automatically, when it was manually started these alerts appeared.
The set up is:
2 node 11gr2  RAC install on Windows 2008 64bit with ASM.
3 SCAN listeners split over the two nodes
If there is anything else config wise please let me know.
Thanks in advance.
Tim

Answer 1

pilog wrote:
Or to boil it down to the question: Is there a feature for a sqlnet connection like "-b" for ssh ?Nope. Cannot recall ever seeing such an option. On the server side that feature is obviously available to bind tcp end points to specific IPs.
Why exactly do you need this feature on the client side? I do not understand the "+the client connects using changing IP addresses, although the application is having a single and constant virtual IP. This requires more open conenctions on the FW between DB and client than necessary+" problem you've stated.
If the client opens 2 connections to the database, then that will be 2 connections via the firewall. As the private port of the client will differ for each connection and thus make the connection unique.
Now whether those 2 client connection use IP1 or IP2 on the client for binding, will not matter - as 2 distinct connections will be created irrespective.
If for some reason you want from the firewall or db server see these inbound client connections as minimal IP sources - then you can do this by using a single IP for all inbound connection by NAT'ing.
You put down a NAT firewall (using iptables for example) and simply rewrite inbound IP headers for tcp packets on 1521 to the NAT IP and forward the packet to the firewall/db server.
That server will see a single client IP only for all incoming traffic. Works pretty well for Oracle as the client connection string includes the client hostname/hostid - so you can still in Oracle see which session is from which client, despite all these sessions having the same source IP.