If private networking is enabled, by default when your server is provisioned, private networking will be enabled. However, if you self-install an OS or self-reinstall an OS, you will need to manually enable private networking.

Get your private networking details from the My NodeSpace portal. Your private network address will be a subnet that starts with 10.90 if you're in our Lenior, NC data center. For example: 10.90.125.16/28. You will need the following details:

• Subnet mask
• Gateway
• Assigned IP

Please do not change your server's IP to another IP from the subnet! If you wish to change the IP, please open a ticket with Support first!

Adding your private network access will depend on which OS you are using.

Windows Server

1. Login to Windows with an administrator account.
2. Open your network settings and go to your device adapters. You will have two adapters. Select the adapter that does not have a valid IP config.
3. Edit the TCP/IP IPv4 properties with the following values:
   • IP address: the assigned IP address from My NodeSpace.
   • Netmask: 255.255.255.240 (or in some cases 255.255.255.248). If your network has a /28 use the former, if your network has a /29 use the latter.
   • Gateway: Leave this blank! Do not enter the gateway! You will lose connection to your server and you will need to use IPMI or contact Support to regain access.
   • DNS: (optional) set to our internal DNS servers (be sure to clear any DNS servers on your public interface!)
4. Open a command prompt with administrator permissions.
5. Run the following command:

   route -p ADD 10.0.0.0 MASK 255.0.0.0 <GATEWAY>

   For example, you would enter:

   route -p ADD 10.0.0.0 MASK 255.0.0.0 10.90.1.254

   Hint: This route is valid for Lenior, NC.

If you did everything correctly, you should have access to your private subnet.

Linux

Coming soon.