Parallels H-Sphere Documentation System Administrator Guide


Winbox IP Migration


Related Docs:   Changing IPs for the H-Sphere Cluster Winbox IP Management Tools

Last modified: 27 Dec 2007


WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the official Parallels site.

This document explains how to migrate a pool of IPs on H-Sphere winbox, including physical server IPs, logical server IPs, and user dedicated IPs. It is important that H-Sphere winbox software is working correctly at the time of migration.


Step 1. Bind Target IPs on the Winbox

Make sure all the target IPs are up. If they aren't you can either bind them manually or use the following steps:

  1. Create a file named, for instance, target_ips.txt with the list of IPs and masks to bind, as follows:
    <IP1> <netmask>
    <IP2> <netmask>
    <IPn> <netmask>
  2. Download IpCreator utility.
  3. Run the IpCreator utility:

    IpCreator.exe target_ips.txt > log.txt


Step 2. Add Double Bindings on IIS

On this step, we'll duplicate IP bindings for virtual web hosts on IIS to use old and new IP bindings simultaneously, which will help us avoid DNS propagation downtime.

  1. Create a file named, for instance, ip_map.txt with space separated old and new IP correspondences, according to the following format:
    <old IP1> <new IP1>
    <old IP2> <new IP2>
    <old IPn> <new IPn>
  2. Download IpMigrator utility.
  3. Run the IpMigrator utility:

    ipmigrator.exe ip_map.txt > ipmigrator.log

Note: IpMigrator inserts new bindings AFTER the corresponding old bindings in the IIS metabase. H-Sphere uses the first binding to obtain virtual web host name and IP, which means, while the old bindings exist in the bindings list, H-Sphere will manage resources with the old IP. For instance, H-Sphere will add host aliases to the old IP's. Thus it is strongly recommended to remove old IP bindings as soon as they aren't needed.


Step 3. Create Migration XML

Create file ipmigration.xml of the following format and put it on the CP server:

<?xml version="1.0"?>
<!DOCTYPE ips [
<!ELEMENT ips (ip+)>

<!ATTLIST ip new_mask CDATA "[New_NetMask]">
    <!-- Delete the lines with IPs you don't want to migrate! -->
    <ip name="[Old_IP1]" new_ip="[New_IP1]"/>
    <ip name="[Old_IP2]" new_ip="[New_IP2]"/>
    <ip name="[Old_IP3]" new_ip="[New_IP3]"/>
    <ip name="[Old_IP4]" new_ip="[New_IP4]" new_mask="[New_NetMask2]"/>

You can find more information on ipmigration.xml in Changing IPs For The H-Sphere Cluster.


Step 4. Run The Migration

  1. Stop H-Sphere
  2. Execute the following commands one by one on the CP server. Replace <LS_ID> with the ID of the Winbox logical server. To find out the ID of the logical server, go to E.Manager -> L.Servers in H-Sphere admin panel.

    java -Xms64M -Xmx512M --ip-change --lServerIds=<LS_ID> ipmigration.xml
    java -Xms64M -Xmx512M --recreate-zone --lServerIds=<LS_ID> ipmigration.xml
    java -Xms64M -Xmx512M --service-zone --lServerIds=<LS_ID> ipmigration.xml
    java -Xms64M -Xmx512M --custom-rec --lServerIds=<LS_ID> ipmigration.xml
  3. Start H-Sphere


Step 5. Remove Old IP Bindings on IIS

At this point in time, you have duplicate bindings of new and old IPs. It is recommended that you remove old IP bindings as soon as DNS servers across the world refresh themselves (usually in no more than 2 days).

The old bindings on IIS can be removed with the IpChange utility, which uses the same IP map file as the IpMigrator utility (step 2 above).

  1. Download IpChange Utility
  2. Run IpChange utility:

    ipchange.exe ip_map.txt > ipchange.log
  3. Restart H-Sphere

Related Docs:   Changing IPs for the H-Sphere Cluster Winbox IP Management Tools

© Copyright 2018. Parallels Holdings. All rights reserved.