- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Outgoing connections from a cluster node
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
09-10-2012 08:58 AM
09-10-2012 08:58 AM
Outgoing connections from a cluster node
we have setup a two node cluster using SG A.11.20 running on HP-UX 11.31. Packages run only on one node with failover to another node (i.e. active/standby). An ip address for the cluster (ie. VIP) has been established via the ip_subnet and ip_address parameters in a package configuration file.
When connections are initiated from an external host to a node in the cluster, we use the IP address of the cluster. However when connections are established from within the active node, the SG's cmnetd does not perform a NAT functionality and the external host which has knowledge of the cluster IP at an application level rejects the incoming connection since it finds a different source ip that that of the cluster.
Is there any SG configuration parameter that will fix this?