Configuring the virtual manager external IP address

Configure this IP address to provide external access to the virtual manager.

Before you begin

Procedure

  1. Click System > Network Configuration.
  2. In the System Management IP section, verify that the IPv4 IP addresses are defined.
  3. Under Optional, click Virtual Manager external IP address.
  4. Select the Configure IPv4 addresses check box.
    The Netmask and Gateway fields are pre-filled with information that is obtained from the System Management IP section.
  5. In the Virtual Manager FQDN field, type the fully qualified domain name for the Virtual Manager. This value must be resolved to the external IP address of the Virtual Manager. You can use the default FQDN, which is purevc if VMware Virtualization is enabled and rhvm if Red Hat® Virtualization is enabled.

    In case of a VMware Virtualization based IBM® Cloud Pak System, detach the MKS IPv4 from the compute nodes before configuring the new Virtual Manager FQDN. Changing the Virtual Manager FQDN reinstalls the Virtual Manager and the reinstall takes approximately 6 hours to complete. The Virtual Manager is not available during the last hour of the reinstall and you cannot deploy or manage virtual machines while the Virtual Manager is unavailable.

    In a Red Hat Virtualization-based IBM Cloud Pak System, changing the Virtual Manager FQDN is not supported in this release. The default hostname that is configured on the RHV-Manager virtual machine is rhvm. Use it as the FQDN when you assign an IP address to the RHV-Manager.

  6. In the Virtual Manager IP address field, type the external IP address for the virtual manager.
    Specify an IP address that is in the same subnet as the ones provided in the System Management IP section.
  7. Click Save.
    Important: This operation takes approximately 6 hours to complete.
  8. Check the job from System > Job Queue and wait for the job to successfully complete.
    • Name: network configure
    • Type: global_config
  9. If you changed the default FQDN from purevc to a user-defined FQDN as stated in Step 5, contact IBM Cloud Pak System Support to activate the Windows product key.

What to do next

Use external application access settings to gain access to internal components such as the virtual manager, compute nodes, and storage controllers. For details, see Configuring external application access.