Operating System - HP-UX
1827809 Members
2175 Online
109969 Solutions
New Discussion

an issue with implementing service guard on WAN

 
miki leon
Advisor

an issue with implementing service guard on WAN

Hi

i want to ask all the service guard expert a que. on :

if it is posible to implemening a service guard that have 2 node with diff network that is connecting with a brige .
love unix
5 REPLIES 5

Re: an issue with implementing service guard on WAN

If the two nodes are not in the same IP subnet, then you cannot fail-over using just serviceguard.

HTH

Duncan

I am an HPE Employee
Accept or Kudo
PIYUSH D. PATEL
Honored Contributor

Re: an issue with implementing service guard on WAN

Hi Miki,

Just some thoughts.

MCSG requires that both the nodes should be on the same network. Both the nodes communicate with each other , whether they are online or not through heartbeat signals. This hearbeat signals are sent every 1 sec. If the other node doesnt receive the heartbeats properly in time then there is always a chance that the node in the cluster can go down.

It is recommended that if both nodes are in same n/w then it will be good.

Piyush
Jeff Schussele
Honored Contributor

Re: an issue with implementing service guard on WAN

Hi Miki,

No sorry, both nodes must reside in the same subnet. Cannot have a bridge in the middle.
Consider changing the network architecture to expand the subnet & remove the bridge - thus creating a single collision domain. Or move one node into the other's subnet.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Gene Crowley
New Member

Re: an issue with implementing service guard on WAN

If you need the servers to be in diffrent lans (ie disaster recovery at another site) you will need Metro or Continental Cluster to go along with Service Guard.
melvyn burnard
Honored Contributor

Re: an issue with implementing service guard on WAN

MetroCluster does not support going across different networks. It still has to comply with the standard SG requirement of all nodes being on the same subnets.
Continental Cluster is 2 completely separate clusters on different networks, so different rulesets.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!