Description

This article describes how to Manage a Cloud Server including:

Prerequisites:

  1. Only the Primary Administrator or a Sub-Admin with the Server role can manage a Cloud Server
  2. Changing the CPU/RAM requires a shutdown and restart of the Cloud Server in order for the changes to take effect:
    1. If VM Tools is running, the system will initiate a reboot as part of the change. Ensure your configuration is ready for that downtime. For example, if the server is currently part of a VIP, you may want to take it out of service during the change. See How to Manage a VIP on a Cloud Network in a MCP 1.0 Data Center Location.
    2. If VM Tools is NOT running, the server must be stopped in order to make CPU and RAM changes.
  3. Ensure your O/S and related configuration can support the configuration you're deploying. The system does NOT ensure the vCPU/RAM can actually be recognized by the server's Operating System and/or applications. So it is possible to configure a server with more resources than the underlying O/S can actually support. For example, Windows 2008 32-bit Standard edition only recognizes 4 GB of RAM. The system will allow you to configure more RAM using this feature, but when you log into the machine, it won't be recognized. However, since the assets are deployed to the server, the server will still be billed accordingly.
    Similarly, some versions of Windows OS will only support a maximum number of sockets, so you may add vCPU only to discover the OS does not recognize them.
  4. When changing the number of CPU, the value must be consistent with the cores per socket setting.
    1. For example, if you have the server set up to 2 cores per socket, you cannot set the CPU to an odd numbered value.
  5. Note that changing the CPU count of a server can alter the pricing of the server if it includes any Priced Software packages priced "Per CPU". See Introduction to Cloud ("Priced") Software and step 3 below
  6. If your Server is part of a Consistency Group, some of these functions may be blocked. For an overview, see Introduction to DRS for Cloud
  7. Any changes to CPU and RAM must be supported by the capabilities of the data center location. For details see: How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
  8. Some settings are not supported on Virtual Hardware versions older than Virtual Hardware 8. See  Edit Server Options Requiring Virtual Hardware Upgrades for details.
  9. If the Server is in a state that requires a restart, you cannot edit the Server's metadata (Name, Description). See How do I determine if my Server Requires a Restart Using REST API?

Content / Solution:

  1. From the Home page, select the Data Center where the Cloud Server you want to manage is located:


  2. The Data Center dashboard will be displayed. Select the Network (MCP 1.0) or Network Domain (MCP 2.0) where the Cloud Server you want to manage is located:


  3. The Network (MCP 1.0) or Network Domain (MCP 2.0) dashboard will be displayed. Click on the Server tab to expand the list of Servers:

Edit Server Name and Description

  1. Locate the Server that you want to manage. Click on the Manage gear for the Server and select Modify Server:


  2. The Modify Server dialog will be displayed:


  3. From this screen, you can edit the Name and/or Description of the Server. Once you have made the desired changes, click the Save button:

    • Server Name - The Server Name is a descriptive name that will appear with the Cloud Server when viewing Servers in the administrative interface. It has no effect on the Server's functionality, machine name, or host name. Therefore, server names are not required to be unique.
    • Server Description - Optionally, you may also enter a more detailed description (up to 255 characters) to be associated with the Server. Again, this is only for descriptive purposes.
       
  4.  Once complete, the system will display a success message:


  5. The system will be updated with the changes:

    NOTE: If there is a problem with the modification (I.e. if the server does not update), the error will appear in the Administrator Logs. For details, see How to View an Administrator Logs Report.

Reconfigure Server Hardware

  1. Locate the Server that you want to manage. Click on the Manage gear for the Server and select Reconfigure Server:

     

  2. The Reconfigure Server Dialog will be displayed:

     

  3. From this screen, you can edit the various data. Once you have made the desired changes, click the Save button:

    • CPU - Select the desired number of CPUs to be allocated to the Server. Enter the desired amount or use the up/down arrows to make your selection.
    • Cores per socket (MCP 2.0 only) - Set the desired number of cores per socket. The system will only present you with acceptable options. You will notice that the system displays the number of sockets beneath the CPU dropdown.   
    • CPU Speed - (MCP 2.0 only) - Set the desired CPU Speed.  For more information on CPU Speeds, see Introduction to CPU Speeds (vCPU Classes)
    • RAM - Set the amount of RAM to be allocated to the Server. 
       
    • Notes: 
      • If the server being modified is the Source Server in a Consistency Group, then the number of vCPUs and amount of RAM must be supported by the cluster of the associated Target Server.
      • A Server can be reconfigured without VM Tools running but only if the Server is in a stopped state. For more information please see Understanding Support for VM Tools in CloudControl.

  4. The system will display a message indicating that the change is being processed:


  5. The system will show the progress of the update in the Server bar:


  6. Once complete, the system will display a success message:


  7. The system will be updated with the changes:

    NOTE: If there is a problem with the modification (I.e. if the server does not update), the error will appear in the Administrator Logs. For details, see How to View an Administrator Logs Report.

Modify IP Address

  1. For instructions on how to modify an IP Address, see:

Start Server

  1. Click on the Manage gear of the Server that you would like to start, then select Start:


  2. The system will display a message indicating that the server is being started:


  3. The system will show the progress in the Server bar:


  4. Once complete, the system will display a success message:


  5. The system start the Server and the UI will be updated to reflect the change:

    Note: the green server icon  indicates that the server is running.

Restart/Reset Server

  1. Click on the Manage gear of the Server that you would like to restart or reset, then select Restart:

     

  2. The system will display the Restart Server dialog. Click on the type of restart you wish to perform:

    Info

    1. Restart - A general restart or reboot.
      1. This option requires a VM Tools installation. For more information please see Understanding Support for VM Tools in CloudControl.
    2. Reset - A hard or a forced restart - equivalent to pulling the power cord. 



  3. The system will display a message indicating that the reset is in progress:


  4. The system will show the progress in the Server bar:


  5. Once complete, the system will display a success message:

    NOTE: If there is a problem restarting the server(I.e. if the server does not restart), the error will appear in the Administrator Logs. For details, see How to View an Administrator Logs Report.

Stop Server

Users should avoid locally shutting down a Source Sever for extended amounts of time since such an action interferes with replication for the entire Consistency Group. For more details, see What happens to a Source Server when it is added to a Consistency Group?

If you want to stop a Server that is a Source Server in a DRS Consistency Group, see: How to Power Off a DRS Source Server

  1. Click on the Manage gear of the Server that you would like to stop, then select Stop:



  2. The system will display the Shutdown Server dialog:

    Info

    1. Graceful Shutdown - A general shutdown - similar to powering off a machine.
      1. This option requires a VM Tools installation. For more information please see Understanding Support for VM Tools in CloudControl.
    2. Hard Stop - A hard or forced shutdown - similar to pulling the power plug.



  3. The system will display a message indicating that the Server shutdown is in progress:

     

  4. The system will show the progress of the shutdown in the Server bar:

     

  5. The system will display a success message: 

    NOTE: If there is a problem with stopping the server (I.e. if the server does not end up in a stopped state), the error will appear in the Administrator Logs. For details, see How to View an Administrator Logs Report.