Search Engine: Elastic

Article ID: 129058, created on Jul 1, 2016, last review on Apr 5, 2017


This atricle is applicable to the migration process of Operation Automation Management Node from RHEL 5 to RHEL 6 if Windows Azure Pack components are installed.

To check that Windows Azure Pack components are intalled on the Management Node, execute the command:

rpm -qa | grep WAP

If the command reports that the WAP rpm package is installed, then the additioanl action is required to migrate Windows Azure Pack components during migration of the Management Node from RHEL 5 to RHEL 6

For example, the output is:



  1. Get the WAP rpm package of the same version as installed on the RHEL 5 node
  2. Save the WAP rpm package to any safe external storage
  3. Archive WAP configuration files by executing commands:

    cd /usr/local/share
    tar -czvf WAP.tar.gz WAP
  4. Copy WAP.tar.gz to any safe location


Restore the WAP component after migration of the Managenet Node is finised:

  1. Copy the backed up data to the destination host:

    • WAP rpm
    • WAP.tag.gz
  2. Execute commands:

    # mkdir /var/log/WAP
    # rpm -ihv --noscripts <WAP.rpm>
    # tar -xf WAP.tar.gz -C /usr/local/share


    • <WAP.rpm> - the name of the WAP rpm package, for example: WAP-1.4-307.parallels.noarch.rpm. Use the same version of RPM that is installed on the source node.
  3. For rhel\centOS 6 MN execute: # chkconfig --level 3 WAP on # service WAP start

  4. For rhel\centOS 7 MN:

    1. remove first empy line in file:

    2. execute:

      # systemctl enable WAP
      # systemctl start WAP

Email subscription for changes to this article
Save as PDF