This article describes how to get Console Access on a Cloud Server.
The process to get Console Access is identical for MCP 1.0 and MCP 2.0 Data Center locations.
The Console Access feature allows you to troubleshoot your Cloud Server if an OS or VM Network failure occurs. Using this feature, you will be able to Console in to your server to address issues which may render the Cloud Server unreachable via RDP or SSH.
- The Cloud Server's Data Center location needs to be enabled for Virtual Console Access. For details, see: How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- The Cloud Server must be running (started). See How to Manage a Cloud Server
- Note: If you are troubleshooting a Server startup issue, you can reboot and/or reset a Cloud Server after opening a Console session. However, the Cloud server must be in a Started state when initially opening the Console session.
- Only the Primary Administrator or a Sub-Admin with the Server role can access Virtual Console.
- Virtual Console can only be accessed through the CaaS Admin UI. There are no APIs available to enable Console sessions outside of CloudControl's UI.
- Your browser will need to allow popups in order to open the Console window.
Content / Solution:
From the Home page, select the Data Center where the Server to which you want to gain Console access is located:
The Data Center dashboard will be displayed. Select the Network Domain (MCP 2.0) or Network (MCP 1.0) on which the Cloud Server on which you want to gain Console Access is located:
The Network Domain (MCP 2.0) or Network (MCP 1.0) dashboard will be displayed. Select the Server on which you want to gain Console Access:
The Server Dashboard will be displayed. Click on the Console button in the menu on the left side of the screen:
Note: Your browser MUST allow popups in order to open the Console window. Otherwise, the system will display an error message:
The system will open a new frame in your browser and ask you to wait while it is connecting:
In some cases, you will also see a Windows 2008 R2 screen while the Console session is established:
It may take 20-30 seconds for the session to be enabled. Do not press any key combination (such as Ctrl-Alt-Delete) while the session is being established. Once the session is established, you will see a screen with a blue row with the IP address of the Cloud Server:Warning: In the event that your browser window is set to the width of the CloudControl UI, you won't be able to see the 'Send Ctrl-Alt-Delete' and 'Full Screen' buttons since these buttons do not resize based on browser window. Increase the width of your screen to be able to see these buttons!
Once the session is established, click anywhere in the Console session window during the Console launch to bring up or activate the Console screen. Assuming you don't have an active Console window, click the 'Send Ctrl-Alt-Delete' button to bring up the login screen and log in using your Cloud Server Admin credentials. Note that the 'Send Ctrl-Alt-Delete' button should only be used for Windows Servers.
Once the session is established, click anywhere in the Console session window to bring up or activate the Console screen. (You may also need to hit Enter during the Console launch.) Next, you can use the Linux Console command line to log into your Cloud Server.
1. Remember to log out when you finish your work in Console. If you fail to log out, the same session may be open when Console is used again.
2. You cannot copy the URL from the new frame and paste it in a new window. If you do so, you will get a "Session Invalid" error. All console sessions must be enabled directly from the Cloud Admin UI.
3. To disable a Linux system from rebooting automatically when <Ctrl>+<Alt>+<Del> keys are pressed, see Disable Linux System from Rebooting when CTRL ALT DELETE is Pressed
4. The Console window will close automatically if idle for 2 minutes.