Contents


Network connectivity is a key differentiator for GoGrid. One of the first services that is available is Cloud Link. It provides data center inter-connectivity between GoGrid data centers. Cloud Link grants customers the ability to replicate data, create disaster recovery solutions or backup data via the private network between data centers on the GoGrid cloud.


Key Features

  • Private Network Connectivity between data centers
  • Unmetered traffic
  • Monthly pricing based on bandwidth speed
  • Isolated from public internet traffic
  • Redundant and fast

Data Center Availability

Cloud Link is currently available between US-West-1 and US-East-1.

Pricing

Pricing can be found on the GoGrid website.

Ordering Cloud Link

You can order Cloud Link Basic (10Mbps) and Advanced (100Mbps) via the Portal. Elite and additional bandwidths can be ordered via a Sales Representative.

Once you are logged into the Portal, click on the add button in Grid view or List view. You will be presented with three options. Click on "Network" and the Cloud Link icon will be visible.

Add-cloudlink.JPG

After you click on the icon, it opens a page where you can select the Cloud Link option that you are interested in.

Getting Help

See our Support page for information on contacting GoGrid for any questions or issues that arise.

Configuring Static Routes

Cloud Link is infrastructure. Once it is activated, you will need to configure static routes on your servers in order to send traffic from a server in one data center to servers in another.

Assigning Static Private IPs

Note that this step is not necessary if you have Private Network Automation (PNA) enabled on your account. PNA automatically assigns private IP addresses to your servers if you have it enabled. Contact support if you would like this functionality.

Linux - Ubuntu and Debian

To assign a private static IP you can update the interface directly.

nano /etc/network/interfaces

Within the file enter the following (don’t enter anything in brackets):

auto eth1
iface eth1 inet static
address 10.100.10.3 [a private IP address in the West ]
netmask 255.255.255.0

Save the file.

This step assigns a private IP from your West block to a single Ubuntu / Debian server. You will need to activate the new IP so restart your network.

ifdown eth1

and then enter:

ifup eth1

Linux - CentOS and Red Hat

To assign a private static IP you can update the interface directly.

vi /etc/sysconfig/network-scripts/ifcfg-eth1

Edit the file with the following information in bold (don’t enter anything in brackets):

DEVICE=eth1
BOOTPROTO=static
IPADDR=10.100.10.3 [a private IP address in the West]
NETMASK=255.255.255.0

Save the file.

This step assigns a private IP from your West block to a single CentOS/ Red Hat server. You will need to activate the new IP so restart your network interface.

ifdown eth1

and then enter:

ifup eth1

Windows

For Windows users, you will need to do the following.

  1. Click on Start > Control Panel > Network Connections.
  2. Select Local Area Connection 2.
  3. Click Properties.
  4. Double-click TCP/IP in the scroll box.
  5. Enable the radio button titled Use the Following IP Address.
  6. Assign a Private IP address to this machine
    1. You can find your private IP block by going to the GoGrid portal, selecting the List tab and then Network.
    2. Under Type: Private you will see your private IP blocks. If this Windows Server is in the West, make sure to use IPs that have US-West-1 in the Datacenter column.
    3. Select an available private IP address and note the Subnet Mask
  7. Enter the subnet mask as found on your list of private IP blocks.
  8. Leave the gateway blank.
  9. You can enter GoGrid’s name servers under DNS if you are so inclined.
  10. Continue to click OK to exit each subsequent window.
  11. To confirm changes were successful, open a command prompt window and type ipconfig /all.

Those steps will assign a private static IP address to a particular machine. Make sure to enable “Local Area Connection 2”.

Create the Static Routes

Linux - Ubuntu and Debian

You will need to edit the interfaces file to add the static route (use your favorite text editor):

nano /etc/network/interfaces

Within the file enter the following (new entries in bold, this assumes that you have already assigned a private IP to the server. Don’t enter anything in the brackets – the IPs are also examples DO NOT use those when building your routes!):

auto eth1
iface eth1 inet static
address 10.100.10.3 [a private IP address in the West ]
netmask 255.255.255.0
up route add -net 10.200.10.0/24 [East private IP block] gw 10.100.10.1 [West private gateway]

Save the file.

At the command type:

route add –net 10.200.10.0 netmask 255.255.255.0 gw 10.100.10.1

These are the same IPs as what you entered in the interface file. Note that this step makes the route immediately active. The interface file makes it persistent. If you don’t want to do run this command, you will have to restart the interface to activate the route.

Linux – CentOS and Red Hat

You will need to edit the static routes file to add the static route (using your favorite text editor):

vi /etc/sysconfig/static-routes

Insert the following line (don’t enter anything in brackets, the IPs are examples only):

Any net 10.200.10.0/24 [East private IP block] gw 10.100.10.1 [West private gateway]

Save the file.

At the command line enter the following command:

route add –net 10.200.10.0 netmask 255.255.255.0 gw 10.100.10.1

Windows

  1. Open a command prompt by clicking on Start > Run
  2. Type cmd and click OK.
  3. Enter the command

       route add -p 10.200.10.0 [East private IP block] mask 255.255.255.0 [West Gateway IP]

where [West Gateway IP] is +1 from your first IP address in your Private Network block available in the GoGrid user interface. If your Window s Server is in the WEST then you will want to use the Gateway IP for the US-West-1 private network. You will want to connect to the East private IP block, so the number after -p is the first available number in your East Private IP block. For example, you would enter something like:

route add -p 10.200.10.0 mask 255.255.255.0 10.109.32.1

The -p flag ensures that the route is persistent across reboots.

Testing Ping

You may be inclined to test that you are able to traverse Cloud Link by using Ping. This will not work unless you also set up a static route on the target server.

You will need to assign a private IP to the server that you want to ping and also define a static route back to the IP blocks in the other data center. If you have a route from West to East, you will need to setup a static route on an East server that you want to ping back to the West.

For example, you can excute the route command if you don't want to persist the route for Windows:

route add 10.109.32.0 netmask 255.255.255.0 10.200.10.1

And for Linux machines:

route add -net 10.109.32.0 mask 255.255.255.0 gw 10.200.10.1

This command sets a static route to your West private IP block through your East gateway.

ping 10.200.10.5

If you can successfully ping that configured US-East-1 private IP from your server in US-West-1 then this has been configured correctly.

Frequently Asked Questions

What happens if I exceed the bandwidth limit that I have selected?

Traffic does not stop as you approach the limit - this is more of a speed limit for your traffic on Cloud Link. However packet loss is possible as you hit the bandwidth limit. This is something to be aware of.


Is Cloud Link redundant?

Yes, Cloud Link is designed for redundancy. We have multiple physical routes that traverse the route between our data centers.


I am not getting the speed that I purchased!

The speed that you are purchasing on Cloud Link is a speed limit and not your average speed. Depending on the transport protocol that your traffic is using, it is likely that it will be less than your speed limit. TCP window size does come into play in terms of the speed that you will achieve for the amount of traffic that you want to transfer.


Can I link directly to cloud storage?

No, Cloud Link is designed to link customer's servers that reside in different GoGrid data centers. It is not designed to tie cloud storage together. Each cloud storage that you want to link to will need to be associated with a server in that data center in order for it to be accessible via Cloud Link.


Is Cloud Link encrypted?

Traffic on Cloud Link is not encrypted. The line is private and does not travel through any public networks. You do have the option of creating your own VPN encrypted tunnel through Cloud Link if you so desire.
Personal tools