Using Configure as a Gateway for Virtual Net Devices
This article describes the results of selecting the option to Configure as a Gateway in the Advanced Options section of a Cloud Server network configuration. The article also discusses the possible errors you might experience and how best to address those errors.
Note: The option to configure as a gateway is only available for virtual net devices and is enabled by default.
Enable or Disable the Configure as a Gateway option
- Log in to the Cloud Control Panel.
- In the top navigation bar, click Select a Product > Rackspace Cloud.
- At the top of the page, click Servers > Cloud Servers.
- Click the Create Server button.
- After you select your operating system and flavor, expand the Advanced Options section.
- Select your preferred network settings and then check or uncheck the Configure as a Gateway option.
- Click the Create Server button.
Cloud Network Configuration and Possible Errors
The following table lists the steps taken by the automated process that is used to set up a Cloud Network, along with steps to take if the automation encounters an issue.
| Configuration step | What could go wrong? | What state is the device left in? | Recommended solution |
|---|---|---|---|
| Build a server by using the Configure as a Gateway option. | The server build failed. | The server is now stuck in an error state. | Delete the server and build a new one. |
Create a Cloud Network with the name $servername-net. | Network creation can fail due to exceeding the Cloud Networks quota of 10 networks per region. Response from API: 409 OverQuotaClient: Quota exceeded for resources: ['network'] | The server is built, but the Cloud Network configuration is not complete. | Delete unused Cloud Networks in the region, or open a support ticket to request a quota increase (subject to approval). Next, delete the server and build a new one. |
| Create a subnet. | It is unlikely anything will go wrong at this point in the build. | The server is built, but the Cloud Network configuration is not complete. | Delete the server and Cloud Network, and build a new server. |
| Create a fixed Internet Protocol (IP) port by using the device ID of the server. | It is unlikely anything will go wrong at this point in the build. | The server is built, but the Cloud Network configuration is not complete. Also, the Cloud Network cannot be deleted until the port is deleted. | Delete the server, Cloud Network port, and Cloud Network, and then build a new server. |
| Attach a fixed IP port to the server. | A sync issue between the Cloud Servers and Cloud Networks APIs leads to the Cloud Servers API assigning the wrong IP. | The IP is wrong in the API, but it works. | You can ignore this situation in the short term. If it becomes a problem, you need to detach the network, wait 15 minutes, make a new fixed IP port, and attach to the server. |
Fortigate Virtual Machine Image Configuration and Possible Errors
The following table lists the steps taken by the automated process that is used to set up a Cloud Network, along with steps to take if the automation encounters an issue.
Configuration step | Command to perform action | What could go wrong? | What state is the device left in? | Recommended solution | |
|---|---|---|---|---|---|
Set the IP in Cloud Networks interface. |
|
| Servers built behind the Fortigate-VM are unable to reach the Internet, as the gateway IP is not yet assigned to the Fortigate-VM. | Log in via HTTPS or SSH and set the port3 (Cloud Networks) interface manually. | |
Configure NAT between Cloud Networks and PublicNet (Internet access). |
|
| Servers built behind the Fortigate-VM are unable to reach the Internet, as NAT is unconfigured. | Servers built behind the Fortigate-VM are unable to reach the Internet, as NAT is unconfigured. | Log in via HTTPS or SSH and set the NAT configuration manually exactly as shown at left. |
Updated 7 days ago