1833210 Members
2972 Online
110051 Solutions
New Discussion

Re: Lan configuration

 
SOLVED
Go to solution
Carlos Vanegas
Occasional Advisor

Lan configuration

I have that situation. I have the IP virtual xx.xx.26.60 configurated in cluster and the IP xx.xx.26.20 the physical IP, and I can connect to the Virtual Ip (60), but I saw the output its going for the physical IP (20).

My problem is the rules of firewall are activated for the Virtual IP and all the output its going for the physical.

Where or What can I check or do?

thanks
Carlos
2 REPLIES 2
melvyn burnard
Honored Contributor
Solution

Re: Lan configuration

well ths is standard operation.
If you require the application to "use" the floating IP address, you need to get it to "bind" to that address.
See Appendix B of http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02437444/c02437444.pdf
Specifically page 435
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Matti_Kurkela
Honored Contributor

Re: Lan configuration

I agree with Melvyn's answer.

However, not all applications have the configuration option to select an IP address to bind to.

If your application does not have that option, you have to either a) change your firewall rules, or b) use the workarounds listed in the "Managing Serviceguard" manual (the document linked by Melvyn).

If you change the firewall rules, remember this:
- incoming TCP connections to the cluster should always be using the package IPs, and the system will respond to them using the package IPs

- outgoing TCP connections initiated by the software running in the cluster will use the physical IPs. Both your firewall *and* the target(s) of those connections must be aware that there are multiple physical nodes the outgoing connections might originate from,

If you connect to some external service, the provider of that service must be made aware that while your connections normally come from the physical IP of the primary node, they might some day switch to one of the alternate nodes' physical IPs without any prior warning (= as your cluster performs an automatic failover).

MK
MK