HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Lan configuration
Operating System - HP-UX
1833210
Members
2972
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2010 07:49 AM
08-20-2010 07:49 AM
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
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
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2010 10:17 AM
08-20-2010 10:17 AM
Solution
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
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2010 01:37 PM
08-20-2010 01:37 PM
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
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP