Search Our Database

Managing private IP networks and instance assignment in Customer Portal

Last updated on |
under |

Introduction

Whether you are scaling your network infrastructure or adjusting your resource allocation, efficiently organizing your internal network is essential for seamless server communication. This guide explains how customers can control their internal networking environment directly through the IPServerOne Customer Portal. System administrators and infrastructure managers can perform these updates at any time from their account dashboard to ensure optimal connectivity and security. By organizing internal network spaces and binding private addresses to specific compute nodes, you can safely isolate backend traffic from the public internet. This manual covers creating, editing, and deleting private IPs, mapping them to your instances, and verifying the configuration across different operating systems.

 

Prerequisite

  • Access to the IPServerOne Customer Portal
  • Portal user account with instances created or with privileges
  • Basic knowledge of private networking and IP addressing concepts

 

Step-by-step guide

Step 1: Access to networks managing site

 

Step 2: Managing private IP networks

Important Note ⚠️: The private IP network is DHCP enabled by default, which mean the IP address will be automatically assign to the instance. To run as static private IP, you will need to manually edit the configuration within the OS level.
  • There are 2 ways to create new private IP network in Customer Portal, which create within the network managing site and instance’s network managing site.
  • For instance’s network managing site, the guidance will be share in the next step, Step 3: Assigning private IP networks.
Create private IP network
  • Click on the CREATE NETWORK button

 

  • Enter you desired name and choose the private IP subnet you wish to have

 

  • You may choose Custom and enter your desired subnet

 

  • Once you have entered the details, click CREATE button to save

 

Rename private IP network
  • Click on the ACTIONS drop-down menu and select Rename option

 

  • Enter your new desired name and click RENAME to save

 

Delete private IP network
  • Click on the ACTIONS drop-down menu and select Delete option

 

  • Click DELETE again to confirm you wish to delete the private IP subnet

 

  • If the private IP subnet is attached to any of the instances, you will be getting the message below to prevent it being delete

 

Step 3: Private IP network instance assignment

  • There are 2 ways to assign the private IP network to instances in Customer Portal, in network managing site and instance’s network managing site.
  • Using network managing site allow you to perform the actions in the fastest way. While instance’s network managing site allow you to fully review the instance before performing any actions.
Network managing site
  • Once you have created a new private IP network, a window will show up and provide the option ASSIGN or SKIP FOR NOW. Click ASSIGN to start assigning the private IP network to the instances

 

  • If you have missed the window or the private IP network was not created recently, you may click on the NAME to start assigning the private IP network to the instances

 

  • In this screen, you will be seeing the assigned instances listed. Click MANAGE INSTANCES to start the assignment

 

  • Make sure you have selected Instance and the Instance type (Cloud Instance or GPU Instance). Tick on the instance you wish to assign then ATTACH to apply

 

Instance's network managing site
  • Navigate Cloud Instance and select NAME to enter the instance management page

 

  • Switch to NETWORK tab then open the Private Networks tab. Select the Private Networks from the drop-down then click ATTACH button to apply
    Tips 🖊️: You can use CREATE & ATTACH to create new private IP network on the spot and attach it after creation

 

  • To detach the private IP network from the instances in network managing site and instance’s network managing site.
Important Note ⚠️: Please make sure you have removed the private IP network configuration in the OS level before detaching in Customer Portal
Detaching private IP network
  • In network managing site, click on DETACH INSTANCES to detach in batch or using DETACH to detach from an instance

 

  • In instance’s network managing site, click DETACH to detach the private IP network from the instance

 

Step 4: Verifying private IP network assignment in OS level

  • After the private IP network is assigned to instance, it should be showing in the OS level automatically without rebooting the server and changing any configuration. To verify the private IP network within the OS level:
Linux OS (Debian-based and RHEL-based)

 

  • Run the command below and the private IP network should be showing
    sudo ip a

 

  • Example output of the command
Tips 🖊️: Refer to the guidance for configuring the instance’s network – [How to configure network settings using nmtui on Linux]

 

Windows OS

 

  • Run the command below in Windows Command Prompt (CMD) and the private IP network should be showing
    ipconfig

 

  • Example output of the command

 

  • In Windows Network Settings will also be showing, there will be 2 networks and one of it should be the private IP network
Tips 🖊️: Refer to the guidance for configuring the instance’s network – [How to configure network settings on Windows Server]

 

Conclusion

By following this guidance, you can successfully create, remove, and map private IP resources to your infrastructure instances using the portal dashboard, as well as confirm status changes inside your system environment.

 

For additional assistance or if you encounter any issues, please contact our support team at support@ipserverone.com.