When you assign an internal IP to your Virtual Machine you will initially only be able to access other IPs in the same subnet, which would be all other VMs in the same cloud. To access other servers on our network, including the backup systems, follow these directions:
Important: Do not set a regular gateway for the internal network in /etc/sysconfig/network-scripts/ifcfg-eth1, /etc/network/interfaces or Windows Network configuration. These will cause the external network connection to work improperly.
Once the internal network is set up, you should be able to successfully ping int.shell01.backup.steadfast.net
Linux
CentOS or Fedora
- Edit the file /etc/sysconfig/network-scripts/route-eth1 (replace "eth1" with your actual interface name) to establish the default route for the subnet:
10.0.0.0/9 via 10.3.128.1
- Also remember to set the Internal NIC to boot on startup. In /etc/sysconfig/network-scripts/ifcfg-eth1 (replace "eth1" with your actual interface name) set:
/>
IPADDR=10.x.x.x
NETMASK=255.255.128.0
Do not put a GATEWAY line in this file, or you may experience public network connectivity issues.
- Once this is done, reload the network configuration:
/etc/init.d/network restart
Debian or Ubuntu
- Make sure to include this interface definition below the one for eth0 in /etc/network/interfaces. Replace ''10.x.x.x'' with your internal network IP and all three instances of "eth1" with your actual interface name. Make sure to maintain the indentation as listed below:
auto eth1
iface eth1 inet static
address ''10.x.x.x''
netmask 255.255.128.0
post-up ip route add 10.0.0.0/9 via 10.3.128.1 dev eth1
pre-down ip route del 10.0.0.0/9
Do not put a gateway line (as in eth0) in the eth1 section of this file, or you may experience public network connectivity issues.
- Once this is done, reload the network configuration:
/etc/init.d/networking restart
Windows
Windows 2008
- Access your internal network interface properties and configure the correct IP address and subnet mask (255.255.128.0) are entered, but do not enter anything in the gateway field.
- Start a command prompt and run the following:
route -p add 10.0.0.0 mask 255.128.0.0 10.3.128.1
This avoids the need for installation of Routing and Remote Access which is not supported by Windows Web Server 2008. Installing RRAS is an alternate method for other editions of Windows Server 2008, and the process for Windows 2003 can be used in that case.
The -p flag stores the route in the registry (so it can be restored at reboot) under the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes
If you modify the entries directly in the registry, you must restart Windows for the changes to take effect.
Windows 2003
- Access your internal network interface properties and configure the correct IP address and subnet mask (255.255.128.0) are entered, but do not enter anything in the gateway field.
- Under Control Panel -> Administrative Tools -> Routing and Remote Access, right click on the name of the system and select Configure and Enable Routing and Remote Access.
- Select Custom configuration, check LAN routing, select Finish and choose Yes for starting the service.
- When prompted to wait, it is recommended you wait. Continue to '''wait a few seconds''' after the wait dialog box has gone away. Additional items will eventually show up under the computer name in the Routing and Remote Access window.
- Click on '''IP Routing''' if it does not expand automatically
- Right click on Static Routes and select New Static Route.
- Select the correct Interface that is connected to the internal network.
- Destination should be set to 10.0.0.0, netmask of 255.128.0.0 and gateway of 10.x.x.x where the x.x.x is set accordingly for the servers own internal IP address. Metric should be left at 1.
- Click Ok and now you have created that route. Hooray!
If you experience trouble with Internal Network routing, please feel free to contact support.
|