Describes how to update the record of a  Private IP Address of a NIC stored in the Cloud system. This feature is useful if users are making manual changes to a NIC IP address or if they are using the "out of place" full system restore feature of Cloud Backup.


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.

  1. 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.

  2. 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.

  3. 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 ("In use")

  4. The new private IP Address cannot currently be exclusively reserved. For more information on exclusively reserved IP Addresses, see Introduction to IP Addressing in MCP 2.0

  5. 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.

  6. You cannot change the IP Address of a NIC if the server is in a state which requires it to be restarted. See the "Adding and Managing Disks" section of Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds

  7. If the Server is a DRS Target Server, and there is a Re-IP Address Rule defined:
    1. DRS Service must be in a Normal state
    2. The Consistency Group must be in a Normal state

Content / Solution:

  1. From the Home page, select the MCP 2.0 Data Center where you want to update the IP Address of a NIC:

  2. The Data Center dashboard will be displayed. Select the Network Domain where the NIC whose IP address you want to change is located:

  3. The Network Domain Dashboard will be displayed. Click on the Servers tab. Locate the Server whose IP Address you want to change and click on the Manage gear for that Server. Click the Modify IP Address button:


  4. The Modify Server NIC Properties dialog will be displayed: 


  5. Make the desired change to the IP Address, then click Save:

    It is recommended that you take note of the current Private IP Address of the Server at this point in case you wish to revert to this exact IP Address later.
    Note: The system reserves X.X.X.0 - X.X.X.7 and X.X.X.255 for its own use, meaning X.X.X.8 - X.X.X.254 are available for use. See Introduction to IP Addressing and Routing in MCP 2.0
    Note: The IPv4 Address cannot be exclusively reserved

    1. If the IP Address you are attempting to change to is being utilized by another Cloud resource, the system will present a message indicating that an IP Conflict is possible if you proceed:

    2. After you click Save, the system will present another confirmation window, asking you to confirm your choice:

  6. The system will display a message indicating that the request is being processed:


  7. The system will indicate that the change is in progress:

    Note: You will not be able to perform any Manage functions on this Server until the update is complete.

  8. The system will display a success message:


  9. The IP Address will be updated and the UI will update to reflect the change:

    When the update is complete, the Server will return to its normal state and you can now perform other managerial tasks on the Server.