Article ID: 3430, created on Nov 30, 2007, last review on May 7, 2014

  • Applies to:
  • H-Sphere

Resolution

There are three main concepts to implement LoadBalancing cluster IP configuration: 1. External IPs (all servers are using extenal IPs) You should have all external IPs for master and slaves. Master IP should be pre-routed between itself and slave servers. So your LoadBalancer device should be set on the network gateway and route the master IP, i.e. loadbalance it. In this case it doesn't need to setup NAT and ip-map.xml file. But just assign master external IP to logical server and add this IP with the correspondent external ones of slave servers to /hsphere/local/config/lb.map and /etc/hsphere/lb.id files as described at http://www.psoft.net/HSdocumentation/sysadmin/lb_cluster.html#map 2. NAT (external IPs are located behind the LoadBalancer device outside, internal ones - across the servers) Master and slave servers have internal IPs. External IPs should correspond to master internal IPs and properly set in ip-map.xml. External IPs should be bound or routed or somehow else balanced on LoadBalancer device which is doing the NAT so between master and slaves. In this case if youn want to add dedicated IP to web server, it needs to assign master internal IP to logical server and add this IP with the correspondent internal ones of slave servers to /hsphere/local/config/lb.map and /etc/hsphere/lb.id files as described at http://www.psoft.net/HSdocumentation/sysadmin/lb_cluster.html#map 3. Mixed IP configuration (external IPs can be assigned to master web server, internal IPs - to slave ones) Master external IP should be pre-routed by LoadBalancer device which can forward the traffic directly to master server through its external IP or using LoadBalancer NAT - direct traffic to slave internal IPs. In this case it doesn't need to setup ip-map.xml as the slave internal IPs nowhere figure in DNS and Hsphere may does not know about the correspondance between slave internal IP and its external one as the correspondance is setting just for master internal IP but it is not the current case. So you may simply assign external IP to logical server and add this IP as master one with the correspondent internal ones of slave servers to /hsphere/local/config/lb.map and /etc/hsphere/lb.id files as described at http://www.psoft.net/HSdocumentation/sysadmin/lb_cluster.html#map

f213b9fa8759d57bee5d547445806fe7 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF