Server Running State Pre-Requisites

The UI will display what running state is required in order to initiate and complete a change

1. Server Must Be Stopped To Make a Change - System requires server to be in a stopped state in order to initiate and perform a change. This is visible as:
   
2. Server Will Be Stopped As Part of Change - System allows request to be initiated when server is in a running state, but the system will gracefully shutdown the server as part of the change process. Ensure your configuration is ready for that downtime. This is visible as:
   
   
   • For example, if the server is currently part of a Virtual Listener, you may want to take it out of service during the change. See How to Manage Virtual Listeners on a Network Domain. 
3. "Hot Change" Supported  - Changes that can be made and implemented while the server is running. No shutdown is required. This is visible as:
   

These settings will be based on the following matrix:

Additional Pre-Requisites

1. Only the Primary Administrator or a Sub-Admin with the Server role can manage a Cloud Server
2. 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
3. If the Server is in a state that requires a restart, no changes can be made until the server is restarted
4. CPU Changes
   1. Note that changing the CPU count of a server can alter
      1. OS Units incurred by Server - See Introduction to OS Units
      2. Software Units incurred by Server - See Introduction to Cloud ("Priced") Software
   2. The CPU count must be supported by Server's Virtual Hardware version - see Edit Server Options Requiring Virtual Hardware Upgrades for details
   3. 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. RAM Changes
   1. When "Hot Add" RAM is true, the maximum RAM value that can be set is still limited to the server's Maximum Hot Add RAM value. This value is based on the amount of RAM that was running on the server when it was last powered on:
      1. Maximum Hot Add RAM = 16 x RAM setting was the last time the Server was powered on
         1. EXCEPTION TO ABOVE: If Server is UNIX and the server was powered on with 3 GB or less RAM, then Maximum Hot Add RAM = 3 GB
   2. The RAM must be supported by Server's Virtual Hardware version - see Edit Server Options Requiring Virtual Hardware Upgrades for details.
6. 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.
7. If the Server is part of a DRS Consistency Group (for more details, see  Introduction to DRS for Cloud)
   1. Some of these functions may be blocked
   2. 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
8. Advanced Virtualization Settings - The following settings can only set to the specified values if the ESX Cluster that the Server resides on must support Advanced Virtualization Settings as described in How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
   
   1. Nested Hardware Virtualization set to True
   2. CPU Latency Sensitivity set to High
   3. Numa Autosize set to True
   4. Enable Host Info to VMTools set to True
   5. In addition, if a Server has Snapshots enabled and Snapshot Replication is enabled, the replication location must support Advanced Virtualization Settings if you want to reconfigure the server to any of the inputs listed above
9. You cannot enable or disable Hot Add CPU and/or Ram on a Windows 2012 Server

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 Domain 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 Hot Add Settings

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

2. The Reconfigure Hot Add Settings Dialog will be displayed:
   
   
   

3. Set the Hot Add CPU Enabled and/or Hot Add RAM Enabled settings to their desired value, then click Save:
   
   

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

   1. The Server Dashboard will display whether or not Hot Add CPU and/or Hot Add Ram are enabled on the Server. See Navigating the Server Dashboard

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:
   

   Note: Modifying CPUs can change the amount of OS Units accrued. See Introduction to OS Units for more information
   
   

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  - 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.   
     • Note: One core per socket will provide the highest performance in all scenarios. When dealing with larger numbers of vCPUs on a Cloud Server (generally greater than 8 vCPUs), be aware that presenting multiple cores per socket may adversely impact performance due to NUMA calculations. For a more detailed discussion on this issue, see http://www.virtadmin.com/sockets-vs-cores-vmware/ or VMware’s blog post at http://blogs.vmware.com/vsphere/2013/10/does-corespersocket-affect-performance.html 
   • CPU Speed - 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. 
   • Hot Add CPU Enabled - Indicates whether the Hot Add CPU feature is Enabled or Disabled. In order to Hot Add CPU, you must meet the preconditions as outlined above.  For more information, see Introduction to Cloud Servers
   • Hot Add RAM Enabled - Indicates whether the Hot Add RAM feature is Enabled or Disabled. In order to Hot Add RAM, you must meet the preconditions as outlined above. For more information, see Introduction to Cloud Servers
   • Advanced Virtualization Settings - See Introduction to Advanced Virtualization Settings for more details. Note the preconditions listed above
   
   
4. If the Server is running, the system may display a message indicating that the Server will be stopped in order to proceed with the changes. Click Confirm:
   
   
   

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

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

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

8. The system will be updated with the changes:
   
   

   NOTES: 
   1. If the change was made on a running server and the system is unable to vMotion the server for the change to fully take effect, the server will be flagged as requiring a restart.
   2. 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:

   • How to Notify CloudControl of a Change to the Private IP Address of a Server in a MCP 1.0 Data Center

   • How to Notify CloudControl of a Change to the IP Addresses of a NIC in a MCP 2.0 Data Center

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 will 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

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.