FAQ: Servers (general)
My virtual server is down. What do I do?
If your virtual server is down, use the following steps to bring it back up:
-
Try to access the server by using the KVM console. Depending on the output, you might need to create a support case.
-
Try to power your server off and on. For more information, see Powering a server on or off or Rebooting a device.
For more help, see Getting help and support.
What do I do if my bare metal server is down?
If your bare metal server is down, use the following steps.
- Remotely access the server by using IPMI. Depending on the output, you might need to create a support case.
If your server does not power on, you might need to start your server in rescue mode. For more information, see Rescue mode
For more help, see Getting help and support.
Why does my server status show "disconnected"?
If your server status shows "disconnected", it might mean that the network monitoring service can't ping your device. Your server might be disconnected for several reasons - such as a network configuration, firewall, or a hardware issue.
For more information about monitoring, see Basic Monitoring.
If you need more help, see Getting help and support.
What is the difference between "Boot from image" and "Load from image"?
Boot from image and Load from image both use image templates, which are applied to a device to either replace or supplement the existing operating system to help remedy an existing issue. The main difference between the Boot and Load process is the type of image that is used. When either the boot or load from image process is used, make sure that you back up all data that you might want to recover.
- Boot from image starts a device by using an ISO supplied by IBM Cloud® for system recovery or an ISO that was uploaded by using the Import image feature in the IBM Cloud console. The ISO might be a clean version of the device operating system or a recovery disk that is used in an attempt to remedy an issue with the device.
- Load from image is a method of OS reload that uses an image template that was either captured from a device or uploaded by using the Image import feature in the IBM Cloud console. Load from image uses a VHD that wipes the device of all data and replaces the existing operating system and files with a "like new" version of the selected image.
I lost my password to my server. How can I recover it?
If the root or administrator password to your server is suddenly not working, check the following items. If necessary, use the instructions to start rescue mode and reset your password.
- Are you copying and pasting the password? If not, try to. Also, paste the password in a notepad to make sure that no spaces are copied with the password.
- If the server has cPanel, it's possible that cPHulk blocked your IP address due to failed logins. You can access the server by using the KVM or IPMI and allowlist your IP address. Use cPHulk with "/scripts/cphulkdwhitelist" followed by your IP address.
- Has someone recently tried to change the password for the server by modifying the password in the IBM Cloud console? Changing the password in the IBM Cloud console changes what you see as the password. It doesn't change the server password. If so, you can contact Support and they can usually recover the original, working password.
- You might need to start into rescue mode to reset your password. For more information, see Rescue mode.
If still can't connect to the server by using the password, open a support case and request a password reset. Support needs to restart the server to reset the password, so prepare to approve the restart and set a maintenance time frame for completion. Most password resets are completed in ~15 minutes. In the IBM Cloud console, you can create a support case by going to Support > Create a case and use the subject Accounts and access.
How do I cancel a device?
You can cancel a device at any time. Go to the Device List. Click Actions for the device that you want to cancel, and select the cancel option from the menu. For more information, see Canceling virtual servers.
Are LVM partitions supported as a valid file system?
LVM (Logical Volume Management) provides logical management of Linux file systems. In the IBM Cloud® environment, LVM isn't supported as a bootable partitioning scheme. Virtual server instances can't be ordered with LVM, and importing images that use LVM as a boot partition fail to provision. If you require LVM on the boot partition, bare metal servers can support LVM on boot for certain operating systems. With proper OS support and configuration, secondary virtual server instance disks can be used for LVM partitions. However, it is important to note that LVM isn't a supported file system for Flex Image or Image Templates. For more assistance, contact support.
Preconfigured 161.26.0.0/16
routes on customer hosts
IBM Cloud is enabling a new route on all newly provisioned servers to support future products.
- The route points to any address in the 161.26.0.0/16 range (161.26.0.0 255.255.0.0 | 161.26.0.0 -161.26.255.255) to the backend private network.
- This IP block is assigned to IBM Cloud by IANA and isn't advertised on the public internet.
- Only IBM Cloud systems are addressed out of this space.
- ACLs on customer servers, virtual servers, and Vyatta gateways need to be updated to allow customer's hosts to use Infrastructure services that are configured with IP addresses out of this range.
How do I add the new routing for an operating system?
Use the following table for OS-specific routing information.
Operating system | Steps |
---|---|
CentOS | Create a route by editing or creating the following file: /etc/sysconfig/network-scripts/route-eth0 Replace 10.0.0.1 with your private gateway IP address. After you create that file, you must add the following information:
_161.26.0.0/16 through 10.0.0.1 |
Debian | In the /etc/network/interfaces file, add the following line at the end of the file: up route add -net 161.26.0.0/16 gw 10.0.0.1 Replace 10.0.0.1 with your private gateway IP address. |
Microsoft Windows | Add the persistent route from the command line by entering the following address: route add 161.26.0.0 mask 255.255.0.0 10.0.0.1 -p Replace 10.0.0.1 with your private gateway IP address. |
Red Hat | Create a route by editing or creating the following file: /etc/sysconfig/network-scripts/route-eth0 Replace 10.0.0.1 with your private gateway IP address. After you create that file, you must add the following information:
_161.26.0.0/16 through 10.0.0.1 |
Ubuntu | In the /etc/network/interfaces file, add the following line at the end of the file: up route add -net 161.26.0.0/16 gw 10.0.0.1 Replace 10.0.0.1 with your private gateway IP address. |
VMWare ESXi | Use the following command to add the route to the ESXi host: esxcfg-route -a 161.26.0.0/16 10.0.0.1 . Replace 10.0.0.1 with your private gateway IP address. |
What is a cvsup mirror?
You can update against a local cvsup mirror that was run for you. Make sure that the sup file has the following entry.
*default host=cvsup.service.softlayer.com
The distfiles are also mirrored and available from The FreeBSD Project. You can add the following line into your /etc/make.conf file to attempt to download from the local repository.
MASTER_SITE_OVERRIDE?="http://mirrors.service.softlayer.com/freebsd/distfiles/${DIST_SUBDIR}/"
If the file is not found there, the path follows the individual port makefile and moves to the next mirror.