Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Info
    This function does NOT actually change the Private IP address of the NIC itself. Any such changes must be made locally inside the Operating System of the Cloud Server.
    This function is designed only to update the Cloud system of any subsequent changes to the private IP addresses assigned to a NIC on a Cloud Server in a MCP 2.0 data center location.
  2. For Servers deployed on Hyper-V based Private Cloud data centers, note that Hyper-V requires the server to be stopped. For details about Hyper-V based Private Cloud data centers see: INTRODUCTION TO MULTIPLE DATA CENTER LOCATIONS IN THE SAME GEOGRAPHICAL REGION Introduction to Multiple Data Center Locations in the same Geographic Region.

  3. Only the Primary Administrator OR a User with the Server role assigned by the Primary Administrator can notify the Cloud system of a change to the IP address of an existing Cloud Server.

  4. You must have already fully deployed a Server in order to modify it in any way. You cannot update the private IP address of the Server until the deployment process is complete.

  5. When notifying the Cloud system of an IP change, the "new" private IP address must be part of the private IP block of the VLAN on which the server is located. The new private IP address also cannot be currently registered to any other Cloud Server.

  6. Important Note: This feature has relevance when using the Cloud Backup service and performing an Out of Place File System Backup Restore. For more information, see HOW TO INITIATE A FULL SYSTEM "OUT OF PLACE" SERVER RESTORE