How-to guides

Users can create the service by entering the required information for a Bare Metal Server and selecting detailed options through the Samsung Cloud Platform Console.

Create Bare Metal Server

You can create and use the Bare Metal Server service from the Samsung Cloud Platform Console.

To create a Bare Metal Server, follow these steps.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Create Bare Metal Server button. 2. Go to the Bare Metal Server Creation page.
3. Bare Metal Server Creation page, enter the information required to create the service and select detailed options.
   • Select the required information in the Image and version selection area.

     Category	required status	Detailed description
     Image	Required	Select the type of Image provided RHEL, Rocky Linux, Ubuntu, Windows Refer to the caution information below for the server types available for each OS Image
     Image version	Required	Select version of the selected Image Provide a version list of the provided server Image

     Table. Bare Metal Server Image and version input items

     Caution

     The server types that can be requested vary by OS image as follows.

     OS Image version	s4/h4 server type	s3/h3 server type	s2/h2 server type
     Oracle Linux 9.6	O	O	O
     RHEL 8.10	X	O	O
     RHEL 9.4	O	O	O
     RHEL 9.6	O	O	O
     Rocky Linux 8.10	X	O	O
     Rocky Linux 9.6	O	O	O
     Ubuntu 22.04	Confirmation needed	O	O
     Ubuntu 24.04	O	O	Confirmation needed
     Windows 2019	X	O	O
     Windows 2022	O	O	O

     • s3/h3, s2/h2 server types are no longer accepting new service applications. * There is no impact on the services currently in use.
     • For Ubuntu, the server types you can request may vary depending on resource availability. * Please confirm before applying for the service.
   • Enter or select the required information in the Service Information Input area.

     Category	required status	Detailed description
     Number of servers	Required	Number of Bare Metal Servers to create simultaneously Only numeric input is allowed, and up to 20 servers of the same type can be created simultaneously
     Service Type > Server Type	Required	Bare Metal Server server type Select the desired vCPU, Memory, and Disk specifications For detailed information about the server types provided by Bare Metal Server, refer to Bare Metal Server 서버 타입
     Service Type > Planned Compute	Required	Status of resources with Planned Compute configured In Use: Number of resources with Planned Compute that are currently in use Configured: Number of resources with Planned Compute configured Coverage Preview: Amount applied per resource by Planned Compute Create Planned Compute Service: Go to the Planned Compute application page For more details, see Planned Compute 신청하기

     Table. Bare Metal Server Service Information Input Items
   • In the Required Information Input area, enter or select the required information.

     Category	required status	Detailed description
     Administrator account	Required	Set the administrator account and password to be used when connecting to the server RHEL and Ubuntu OS are provided with a fixed root account For Windows OS, enter 5 to 20 characters using lowercase letters and numbers Administrator Not allowed
     Server name	Required	When the selected number of servers is 1, enter a name to distinguish the Bare Metal Server It must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters (-) within 3 to 15 characters It must not end with a special character (-) Set the hostname to the entered server name
     Server name (auto-generated number)	Required	It is enabled when the number of selected servers is 2 or more, and you must enter a name for distinguishing the Bare Metal Server in the format name-### (e.g., test-001) It must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters (-) within 3 to 15 characters It must not end with a special character (-) Set the hostname to the entered server name Automatically generate by incrementing from the entered number by 1 (excluding numbers already in use)
     Network Settings	Required	Set the network where the Bare Metal Server will be installed Select a pre-created VPC General Subnet: Select a pre-created general Subnet IP can be auto-generated or user-provided, and if input is selected, the user enters the IP manually NAT: Available only when there is one server and the VPC is connected to an Internet Gateway When checked, a NAT IP can be selected NAT IP: Select a NAT IP If no NAT IP is available to select, click the Create New button to generate a Public IP Click the Refresh button to view and select the generated Public IP Creating a Public IP incurs charges according to the Public IP pricing policy Local Subnet (optional): Choose to use a local Subnet It is not a required element for creating the service Select a pre-created local Subnet IP can be auto-generated or user-provided, and if input is selected, the user enters the IP manually

     Table. Bare Metal Server required information entry items

4. On the Bare Metal Server Creation page, in the Additional Information Input area, enter or select the required information.

   Category	required status	Detailed description
   Local disk partition	Selection	Set whether to use the local disk partition Up to 10 partitions can be created, including the root partition Can use up to 90% of the total capacity After checking Use, you can configure partition information Configure root partition information Partition type: flat, lvm selectable Partition name: enter partition name Can be entered only when partition type is lvm Enter up to 15 characters starting with a letter and containing letters, numbers, and special characters (-_) Partition size: enter at least 50 GB Filesystem type: select according to the used image For RHEL, Rocky Linux: xfs, ext4 For Ubuntu: ext4, xfs, btrfs For SLES: btrfs, xfs, ext4 Mount point: start with special character / and include letters, numbers, and special characters (-_) up to 15 characters Cannot be entered when Filesystem type is swap Available capacity: 90% of the default disk capacity provided when selecting a server When setting partition size, the remaining capacity is automatically calculated and displayed The total partition disk size cannot exceed the available capacity Configure additional partition information Partition type: flat, lvm selectable Partition name: enter partition name Partition type can be entered only when it is lvm Enter up to 15 characters starting with a letter and containing letters, numbers, and special characters (-_) up to 15 characters Partition size: enter at least 1 GB Filesystem type: select according to the used image> For RHEL, Rocky Linux: xfs, ext4, swap For Ubuntu: ext4, xfs, btrfs, swap For SLES: btrfs, xfs, ext4, swap Mount point: start with special character / and include letters, numbers, and special characters (-_) up to 15 characters Cannot be entered when Filesystem type is swap Available capacity: 90% of the default disk capacity provided when selecting a server When setting partition size, the remaining capacity is automatically calculated and displayed The total partition disk size cannot exceed the available capacity
   Placement Group	Selection	Servers belonging to the same Placement group are distributed across different racks Provides distributed placement for up to two servers belonging to the same Placement group For distributed placement of three or more servers, add additional Placement groups Applicable only at initial creation and cannot be modified afterward If you terminate the last server in a Placement group, that Placement group is automatically deleted
   Lock	Selection	Using a lock prevents actions caused by mistakes, such as terminating, starting, or stopping the server.
   Init Script	Selection	Script to run when the server starts The Init Script must be selected differently depending on the Image type For Windows: Select Batch Script For Linux: Shell Script

   Table. Bare Metal Server Additional Information Input Items

5. Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.

   • Once creation is complete, check the created resources on the Bare Metal Server List page.

Check detailed information of Bare Metal Server

The Bare Metal Server service allows you to view and edit the complete resource list and detailed information. The Bare Metal Server Details page consists of Details, Tags, Activity History tabs.

To view detailed information about the Bare Metal Server, follow these steps.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Bare Metal Server menu. 2. Go to the Bare Metal Server List page.
3. On the Bare Metal Server List page, click the resource to view detailed information. 3. Go to the Bare Metal Server Details page.
   • Bare Metal Server Details page displays status information and additional feature information, and consists of Details, Tags, Operation History tabs.

     Category	Detailed description
     Bare Metal Server status	Status of the Bare Metal Server created by the user Creating: State while the server is being created Running:: State when creation is complete and the server is usable Editing:: State while the IP is being changed Unknown: Error state Starting: State while the server is starting Stopping: State while the server is stopping Stopped: State when the server has stopped Terminating: State while terminating Terminated: State when termination is complete
     Server operation control button	Button to change server status Start: Start a stopped server Stop: Stop a running server
     Service cancellation	Cancel service button

     Table. Bare Metal Server status information and additional functions

Detailed Information

On the Bare Metal Server List page, you can view the detailed information of the selected resource and, if needed, modify the information.

Tag

Bare Metal Server list page lets you view the tag information of the selected resource, and you can add, modify, or delete it.

Job History

Bare Metal Server List page allows you to view the operation history of the selected resource.

Bare Metal Server Resource Management

If you need server control and management functions for the created Bare Metal Server resources, you can perform tasks on the Bare Metal Server List or Bare Metal Server Details page.

Bare Metal Server Control Operation

You can start, stop, and restart a running Bare Metal Server.

To control the operation of a Bare Metal Server, follow these steps.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Bare Metal Server menu. 2. Go to the Bare Metal Server List page.
3. Bare Metal Server List page, after selecting multiple servers, you can control multiple servers simultaneously using the Start and Stop buttons at the top of the table.
   • Bare Metal Server Details The page also allows you to start and stop the server.
4. On the Bare Metal Server List page, click the resource to control its operation and navigate to the Bare Metal Server Detail page.
5. Check the server status and click the server operation control button to complete the change.
   • Start: Start the stopped server.
   • Stop: Stops the running server.

Add Block Storage

You can add Block Storage to a Bare Metal Server.

To add Block Storage, follow the steps below.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Bare Metal Server menu. 2. Go to the Bare Metal Server List page.
3. Bare Metal Server List page, click the server to which you want to add Block Storage. 3. Go to the Bare Metal Server Details page.
4. On the Bare Metal Server Details page, click the Add button in the Block Storage section.
5. When the popup confirming Block Storage addition opens, click the Confirm button. 5. Block Storage (BM) Creation Navigate to the page.
6. On the Block Storage(BM) Creation page, enter the information required to create the service and create a Block Storage.
   • For detailed information on creating Block Storage (BM), see Block Storage(BM) 생성하기-create).
7. Navigate to the Bare Metal Server Details page where Block Storage was added and confirm that Block Storage has been added.

Configure CPU

You can configure the CPU of a Bare Metal Server. To configure the CPU, follow these steps.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.

2. On the Service Home page, click the Bare Metal Server menu. 2. Go to the Bare Metal Server List page.

3. On the Bare Metal Server List page, click the resource to configure the CPU. 3. Go to the Bare Metal Server Details page.

4. On the Bare Metal Server Details page, click the Edit button in the CPU Settings item. 4. Edit CPU Settings A popup window opens.

5. After entering whether to use the CPU settings and the configuration information, click the Confirm button.

   Category	required status	Detailed description
   Use status	Required	Select whether to enable the CPU setting When Use is set, Thread per core and core count are required inputs
   Threads per core	Required	Set Hyper threading usage To disable Hyper threading, set Thread per core to 1
   Number of cores	Required	Set the number of vCPUs to activate Changing the number of cores does not affect the price.
   Total vCPU count	-	The final number of vCPUs to be activated on the server Automatically calculate and display the value obtained by multiplying Thread per core by number of cores

   Table. CPU configuration information items

6. When the pop-up notifying CPU setting changes opens, click the Confirm button.

7. Check that the CPU settings have been correctly modified on the Bare Metal Server Details page.

Terminate Bare Metal Server

If you terminate an unused Bare Metal Server, you can reduce operating costs. However, if you terminate a Bare Metal Server, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact of service interruption.

To cancel a Bare Metal Server, follow the steps below.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Bare Metal Server menu. 2. Go to the Bare Metal Server List page.
3. On the Bare Metal Server List page, select the resource to terminate, and click the Terminate Service button.
   • You can select multiple resources and delete them simultaneously.
   • You can also delete the resource by clicking the Cancel Service button on the Bare metal Server Details page.
4. Once the termination is complete, check the Bare Metal Server List page to see if the resource has been terminated.

Termination constraints

If a Bare Metal Server termination request cannot be completed, a popup will provide guidance. Please refer to the case below.

Configure local Subnet

After completing the creation of a Bare Metal Server, when adding a local Subnet on the Bare Metal Server Details page, the user must manually configure the network settings of the local Subnet.

First connection (kr-west)

If there is no local subnet connected to the Bare Metal Server and you are adding the first connection, follow the guide below.

Linux - Setting up Subnet on Ubuntu

To add a local Subnet and configure the network on an Ubuntu operating system, follow these steps.

1. On the Bare Metal Server Details page, check the Interface Name.

2. Retrieve the network configuration information.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
   network:
   ethernets:
    ens2f1:
    match:
    macaddress: 68:05:ca:d4:09:91
    mtu: 1500
    set-name: ens2f1
    ens4f1:
    match:
    macaddress: 68:05:ca:d4:09:01
    mtu: 1500
    set-name: ens4f1

   [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
   network:
   ethernets:
    ens2f1:
    match:
    macaddress: 68:05:ca:d4:09:91
    mtu: 1500
    set-name: ens2f1
    ens4f1:
    match:
    macaddress: 68:05:ca:d4:09:01
    mtu: 1500
    set-name: ens4f1

3. After adding a new VLAN, set the IP for the bonding configuration.

   • Replace the example code’s ID and IP with the assigned ID and IP.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
             bond-mgt:
                 interfaces:
                 - ens2f1      // **Bare Metal Server Details** Enter the Interface Name displayed on the page.
                 - ens4f1      // **Bare Metal Server Details** Enter the Interface Name shown on the page.
                 mtu: 1500
                 parameters:
                     mii-monitor-interval: 100
                     mode: active-backup
                     transmit-hash-policy: layer2
         ethernets:
             ens2f1:
                 match:
                 macaddress: 68:05:ca:d4:09:91
                 mtu: 1500
                 set-name: ens2f1
             ens4f1:
                 match:
                 macaddress: 68:05:ca:d4:09:01
                 mtu: 1500
                 set-name: ens4f1
         vlans:
             bond-mgt.20:   // Enter the Vlan ID you verified in the SCP Console instead of 20.
             addresses:
                 - 192.168.0.10/24 // Set it to the local Subnet IP confirmed in the SCP Console.
                 id: 20    // Set to the Vlan ID verified in the SCP Console.
                 link: bond-mgt
                 mtu: 1500

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
             bond-mgt:
                 interfaces:
                 - ens2f1      // **Bare Metal Server Details** Enter the Interface Name displayed on the page.
                 - ens4f1      // **Bare Metal Server Details** Enter the Interface Name shown on the page.
                 mtu: 1500
                 parameters:
                     mii-monitor-interval: 100
                     mode: active-backup
                     transmit-hash-policy: layer2
         ethernets:
             ens2f1:
                 match:
                 macaddress: 68:05:ca:d4:09:91
                 mtu: 1500
                 set-name: ens2f1
             ens4f1:
                 match:
                 macaddress: 68:05:ca:d4:09:01
                 mtu: 1500
                 set-name: ens4f1
         vlans:
             bond-mgt.20:   // Enter the Vlan ID you verified in the SCP Console instead of 20.
             addresses:
                 - 192.168.0.10/24 // Set it to the local Subnet IP confirmed in the SCP Console.
                 id: 20    // Set to the Vlan ID verified in the SCP Console.
                 link: bond-mgt
                 mtu: 1500

4. Apply the changes to the system.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # netplan apply

   # netplan apply

5. Check the interface status.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # ip a
   or
   # bash /usr/local/bin/ip.sh

   # ip a
   or
   # bash /usr/local/bin/ip.sh

Linux – Configuring Subnet on CentOS/Red Hat

After adding a local Subnet on a CentOS/Red Hat operating system, follow these steps to configure the network.

1. On the Bare Metal Server Details page, check the Interface Name.

2. Modify the following command and execute it.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as observed in the Console.
   VLAN_ID="7"             // Set the Vlan ID as observed in the console.
   
   BOND_NAME="bond-mgt"
   BOND_IF_name1="ens2f1"  // Enter the Interface Name as found on the **Bare Metal Server Detailed** page.
   BOND_IF_name2="ens4f0"  // **Bare Metal Server Details** page, enter the Interface Name you verified.
   
   
   # Delete Connection
   nmcli con down "Bond ${BOND_NAME}"
   nmcli con del  "Bond ${BOND_NAME}"
   
   nmcli con down "System ${BOND_IF_name1}"
   nmcli con down "System ${BOND_IF_name2}"
   
   nmcli con del  "System ${BOND_IF_name1}"
   nmcli con del  "System ${BOND_IF_name2}"
   
   
   # Create Bonding
   nmcli con add con-name ${BOND_NAME} type bond ifname ${BOND_NAME}
   nmcli conn mod ${BOND_NAME} con-name "Bond ${BOND_NAME}"
   nmcli conn mod "Bond ${BOND_NAME}" ipv4.method    disabled
   nmcli conn mod "Bond ${BOND_NAME}" ipv6.method    ignore
   nmcli conn mod "Bond ${BOND_NAME}" connect.autoconnect yes
   
   nmcli conn mod "Bond ${BOND_NAME}" +bond.options mode=active-backup      \
                                      +bond.options xmit_hash_policy=layer2
                                      +bond.options miimon=100              \
                                      +bond.options num_grat_arp=1          \
                                      +bond.options downdelay=0
                                      +bond.options updelay=0
   
   # Assign bond-slave
   nmcli conn add type bond-slave ifname ${BOND_IF_name1}  con-name "${BOND_IF_name1}" master ${BOND_NAME}
   nmcli conn mod ${BOND_IF_name1} con-name "System ${BOND_IF_name1}"
   
   nmcli conn add type bond-slave ifname ${BOND_IF_name2}  con-name "${BOND_IF_name2}" master ${BOND_NAME}
   nmcli conn mod ${BOND_IF_name2} con-name "System ${BOND_IF_name2}"
   
   # Connection UP
   nmcli conn up   "Bond ${BOND_NAME}"
   # add vlan
   nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
   nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
   nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli      device reapply ${BOND_NAME}.${VLAN_ID}

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as observed in the Console.
   VLAN_ID="7"             // Set the Vlan ID as observed in the console.
   
   BOND_NAME="bond-mgt"
   BOND_IF_name1="ens2f1"  // Enter the Interface Name as found on the **Bare Metal Server Detailed** page.
   BOND_IF_name2="ens4f0"  // **Bare Metal Server Details** page, enter the Interface Name you verified.
   
   
   # Delete Connection
   nmcli con down "Bond ${BOND_NAME}"
   nmcli con del  "Bond ${BOND_NAME}"
   
   nmcli con down "System ${BOND_IF_name1}"
   nmcli con down "System ${BOND_IF_name2}"
   
   nmcli con del  "System ${BOND_IF_name1}"
   nmcli con del  "System ${BOND_IF_name2}"
   
   
   # Create Bonding
   nmcli con add con-name ${BOND_NAME} type bond ifname ${BOND_NAME}
   nmcli conn mod ${BOND_NAME} con-name "Bond ${BOND_NAME}"
   nmcli conn mod "Bond ${BOND_NAME}" ipv4.method    disabled
   nmcli conn mod "Bond ${BOND_NAME}" ipv6.method    ignore
   nmcli conn mod "Bond ${BOND_NAME}" connect.autoconnect yes
   
   nmcli conn mod "Bond ${BOND_NAME}" +bond.options mode=active-backup      \
                                      +bond.options xmit_hash_policy=layer2
                                      +bond.options miimon=100              \
                                      +bond.options num_grat_arp=1          \
                                      +bond.options downdelay=0
                                      +bond.options updelay=0
   
   # Assign bond-slave
   nmcli conn add type bond-slave ifname ${BOND_IF_name1}  con-name "${BOND_IF_name1}" master ${BOND_NAME}
   nmcli conn mod ${BOND_IF_name1} con-name "System ${BOND_IF_name1}"
   
   nmcli conn add type bond-slave ifname ${BOND_IF_name2}  con-name "${BOND_IF_name2}" master ${BOND_NAME}
   nmcli conn mod ${BOND_IF_name2} con-name "System ${BOND_IF_name2}"
   
   # Connection UP
   nmcli conn up   "Bond ${BOND_NAME}"
   # add vlan
   nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
   nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
   nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli      device reapply ${BOND_NAME}.${VLAN_ID}

3. Check the interface status.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # ip a
   or
   # bash /usr/local/bin/ip.sh

   # ip a
   or
   # bash /usr/local/bin/ip.sh

Setting up Subnet in Windows

After adding a local Subnet on the Windows operating system, follow these steps to configure the network.

1. Windows Start icon, right-click it, then run the Windows PowerShell(Administrator) program.

2. On the Bare Metal Server Details page, check the Interface Name.

3. Run ncpa.cpl from the Windows Run menu.

   

4. Check whether the interface is enabled, and enable it if necessary.

   • Activate the Interface Name identified on the Bare Metal Server Details page.
     

5. Create a Teaming.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   PS C:\> New-NetLbfoTeam –Name “bond-mgt” –TeamMembers ens2f1,ens4f1
   PS C:\> Set-NetLbfoTeam –Name “bond-mgt” –LoadBalancingAlgorithm Dynamic

   PS C:\> New-NetLbfoTeam –Name “bond-mgt” –TeamMembers ens2f1,ens4f1
   PS C:\> Set-NetLbfoTeam –Name “bond-mgt” –LoadBalancingAlgorithm Dynamic

   

6. After adding a new VLAN, configure the IP.

   • Enter the VLAN ID and local Subnet IP confirmed on the Bare Metal Server Details page.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
     PS C:\> Get-NetAdapter
     PS C:\> netsh interface ip set address bond-mgt.20 static “192.168.0.10/24”

     PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
     PS C:\> Get-NetAdapter
     PS C:\> netsh interface ip set address bond-mgt.20 static “192.168.0.10/24”

7. In the Windows Run menu, execute ncpa.cpl to check the interface status.

First connection(kr-south)

If there is no local subnet connected to the Bare Metal Server and you are adding the first connection, follow the guide below.

Linux - Setting up Subnet on Ubuntu

To add a local Subnet and configure the network on an Ubuntu operating system, follow these steps.

1. After adding a new VLAN, set the IP.

   • Replace the example code’s ID and IP with the assigned ID and IP.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
             bond-mgt:
                 interfaces:
                 - ens2f1
                 - ens4f1
                 mtu: 1500
                 parameters:
                     mii-monitor-interval: 100
                     mode: active-backup
                     transmit-hash-policy: layer2
         ethernets:
             ens2f1:
                 match:
                 macaddress: 68:05:ca:d4:09:91
                 mtu: 1500
                 set-name: ens2f1
             ens4f1:
                 match:
                 macaddress: 68:05:ca:d4:09:01
                 mtu: 1500
                 set-name: ens4f1
         vlans:
             bond-mgt.20:
             addresses:
                 - 192.168.0.10/24
                 id: 20
                 link: bond-mgt
                 mtu: 1500
         vlans:
             bond-mgt.21: // Enter the VLAN ID you verified on the console instead of 21.
             addresses:
                 - 192.168.0.20/24 // Set it to the local Subnet IP verified in the console.
                 id: 21    // Set to the VLAN ID verified in the console.
                 link: bond-mgt
                 mtu: 1500

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
             bond-mgt:
                 interfaces:
                 - ens2f1
                 - ens4f1
                 mtu: 1500
                 parameters:
                     mii-monitor-interval: 100
                     mode: active-backup
                     transmit-hash-policy: layer2
         ethernets:
             ens2f1:
                 match:
                 macaddress: 68:05:ca:d4:09:91
                 mtu: 1500
                 set-name: ens2f1
             ens4f1:
                 match:
                 macaddress: 68:05:ca:d4:09:01
                 mtu: 1500
                 set-name: ens4f1
         vlans:
             bond-mgt.20:
             addresses:
                 - 192.168.0.10/24
                 id: 20
                 link: bond-mgt
                 mtu: 1500
         vlans:
             bond-mgt.21: // Enter the VLAN ID you verified on the console instead of 21.
             addresses:
                 - 192.168.0.20/24 // Set it to the local Subnet IP verified in the console.
                 id: 21    // Set to the VLAN ID verified in the console.
                 link: bond-mgt
                 mtu: 1500

2. Apply the changes to the system.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # netplan apply

   # netplan apply

3. Check the interface status.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # ip a
   or
   # bash /usr/local/bin/ip.sh

   # ip a
   or
   # bash /usr/local/bin/ip.sh

Linux – Configuring Subnet on CentOS/Red Hat

CentOS/Red Hat operating system, after adding a local Subnet, follow these steps to configure the network.

1. Check the Bond Name for the local Subnet.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # sh /usr/local/bin/ip.sh

   # sh /usr/local/bin/ip.sh

2. Modify the following command and execute it.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as observed in the Console.
   VLAN_ID="7"             // Set the Vlan ID as observed in the console.
   
   BOND_NAME="bond-mgt" // 1. Set the Bond Name you confirmed.
   
   # add vlan
   nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
   nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
   nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
   
   nmcli      device reapply ${BOND_NAME}.${VLAN_ID}

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as observed in the Console.
   VLAN_ID="7"             // Set the Vlan ID as observed in the console.
   
   BOND_NAME="bond-mgt" // 1. Set the Bond Name you confirmed.
   
   # add vlan
   nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
   nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
   nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
   
   nmcli      device reapply ${BOND_NAME}.${VLAN_ID}

3. Check the interface status.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # ip a
   or
   # bash /usr/local/bin/ip.sh

   # ip a
   or
   # bash /usr/local/bin/ip.sh

Configuring Subnet on Windows

After adding a local Subnet on the Windows operating system, follow these steps to configure the network.

1. Windows Start icon, right-click it, then run the Windows PowerShell(Administrator) program.

2. Check the Teaming name for the local Subnet.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   PS C:\> Get-NetAdapter

   PS C:\> Get-NetAdapter

3. After adding a new VLAN, set the IP.

   • Enter the Teaming name confirmed in step 2, and the Vlan ID and local Subnet IP confirmed in the Console.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
     PS C:\> Get-NetAdapter
     PS C:\> netsh interface ip set address bond-mgt.20 static “192.168.0.10/24”

     PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
     PS C:\> Get-NetAdapter
     PS C:\> netsh interface ip set address bond-mgt.20 static “192.168.0.10/24”

4. In the Windows Run menu, execute ncpa.cpl to check the interface status.

   

Add second connection (kr-west, kr-south)

If there is a local subnet connected to the Bare Metal Server, the guide for the second additional connection is below.

Because a Bonding was already created when connecting the first local Subnet, there is no procedure to create Bonding when connecting the second local Subnet.

Please refer to the details below.

Linux - Setting up Subnet on Ubuntu

To add a local Subnet and configure the network on an Ubuntu operating system, follow these steps.

1. After adding a new VLAN, set the IP.

   • Replace the example code’s ID and IP with the assigned ID and IP.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
             bond-mgt:
                 interfaces:
                 - ens2f1
                 - ens4f1
                 mtu: 1500
                 parameters:
                     mii-monitor-interval: 100
                     mode: active-backup
                     transmit-hash-policy: layer2
         ethernets:
             ens2f1:
                 match:
                 macaddress: 68:05:ca:d4:09:91
                 mtu: 1500
                 set-name: ens2f1
             ens4f1:
                 match:
                 macaddress: 68:05:ca:d4:09:01
                 mtu: 1500
                 set-name: ens4f1
         vlans:
             bond-mgt.20:
             addresses:
                 - 192.168.0.10/24
                 id: 20
                 link: bond-mgt
                 mtu: 1500
         vlans:
             bond-mgt.21: // Enter the VLAN ID you verified on the console instead of 21.
             addresses:
                 - 192.168.0.20/24 // Set it to the local Subnet IP verified in the console.
                 id: 21    // Set to the VLAN ID verified in the console.
                 link: bond-mgt
                 mtu: 1500

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
             bond-mgt:
                 interfaces:
                 - ens2f1
                 - ens4f1
                 mtu: 1500
                 parameters:
                     mii-monitor-interval: 100
                     mode: active-backup
                     transmit-hash-policy: layer2
         ethernets:
             ens2f1:
                 match:
                 macaddress: 68:05:ca:d4:09:91
                 mtu: 1500
                 set-name: ens2f1
             ens4f1:
                 match:
                 macaddress: 68:05:ca:d4:09:01
                 mtu: 1500
                 set-name: ens4f1
         vlans:
             bond-mgt.20:
             addresses:
                 - 192.168.0.10/24
                 id: 20
                 link: bond-mgt
                 mtu: 1500
         vlans:
             bond-mgt.21: // Enter the VLAN ID you verified on the console instead of 21.
             addresses:
                 - 192.168.0.20/24 // Set it to the local Subnet IP verified in the console.
                 id: 21    // Set to the VLAN ID verified in the console.
                 link: bond-mgt
                 mtu: 1500

2. Apply the changes to the system.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # netplan apply

   # netplan apply

3. Check the interface status.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # ip a
   or
   # bash /usr/local/bin/ip.sh

   # ip a
   or
   # bash /usr/local/bin/ip.sh

Linux – Configuring Subnet on CentOS/Red Hat

After adding a local Subnet on CentOS/Red Hat operating systems, follow the steps below to configure the network.

1. Check the Bond Name for the local Subnet.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # sh /usr/local/bin/ip.sh

   # sh /usr/local/bin/ip.sh

2. Modify the following command and execute it.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as observed in the Console.
   VLAN_ID="7"             // Set the Vlan ID as observed in the console.
   
   BOND_NAME="bond-mgt" // 1. Set the Bond Name you confirmed.
   
   # add vlan
   nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
   nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
   nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
   
   nmcli      device reapply ${BOND_NAME}.${VLAN_ID}

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as observed in the Console.
   VLAN_ID="7"             // Set the Vlan ID as observed in the console.
   
   BOND_NAME="bond-mgt" // 1. Set the Bond Name you confirmed.
   
   # add vlan
   nmcli conn add type vlan ifname "${BOND_NAME}.${VLAN_ID}" con-name "${BOND_NAME}.${VLAN_ID}" id ${VLAN_ID} dev ${BOND_NAME}
   nmcli con  mod ${BOND_NAME}.${VLAN_ID} con-name "Vlan ${BOND_NAME}.${VLAN_ID}"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.addresses ${IP_ADDR}
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv4.method manual
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" ipv6.method "ignore"
   nmcli con  mod "Vlan ${BOND_NAME}.${VLAN_ID}" connect.autoconnect yes
   nmcli con  up  "Vlan ${BOND_NAME}.${VLAN_ID}"
   
   nmcli      device reapply ${BOND_NAME}.${VLAN_ID}

3. Check the interface status.
   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   # ip a
   or
   # bash /usr/local/bin/ip.sh

   # ip a
   or
   # bash /usr/local/bin/ip.sh

Configuring Subnet on Windows

After adding a local Subnet on the Windows operating system, follow these steps to configure the network.

1. Windows Start icon, right-click it, then run the Windows PowerShell(Administrator) program.

2. Check the Teaming name for the local Subnet.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   PS C:\> Get-NetAdapter

   PS C:\> Get-NetAdapter

3. After adding a new VLAN, configure the IP.
   

   • Enter the Teaming name confirmed in step 2, the Vlan ID confirmed in the Console, and the local Subnet IP.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
     PS C:\> Get-NetAdapter
     PS C:\> netsh interface ip set address bond-mgt.20 static “192.168.0.10/24”

     PS C:\> Add-NetLbfoTeamNIC -Team bond_bond-mgt -VlanID 20 -Name bond-mgt.20
     PS C:\> Get-NetAdapter
     PS C:\> netsh interface ip set address bond-mgt.20 static “192.168.0.10/24”

4. In the Windows Run menu, execute ncpa.cpl to check the interface status.

   

Change IP

The IP can be changed to carry out migration, server replacement, and similar tasks.

Follow these steps to change the IP.

1. All Services > Compute > Bare Metal Server Click the menu. 1. Go to the Service Home page of the Bare Metal Server.

2. On the Service Home page, click the Bare Metal Server menu. 2. Go to the Bare Metal Server List page.

3. Bare Metal Server List page, click the server whose IP you want to change. Navigate to the Bare Metal Server Detail page.

4. On the Bare Metal Server Details page, click the Edit button next to the IP field.

5. When the popup notifying IP modification opens, click the Confirm button. 5. IP Change The popup window opens.

6. IP Change popup window’s Step 1, Step 2, Step 3 tasks should be performed sequentially.

   Notice

   • When changing the IP, the detailed configuration method for the IP change step varies depending on the subnet of the IP to be changed. * Be sure to refer to the following example and proceed with the tasks step by step.
     • When changing to an IP that uses the same subnet: Change to an IP of the same Subnet Reference
     • When changing to an IP that uses a different subnet: Change to IP of a different Subnet See
   • When each step is completed successfully, the task status in the upper right corner is displayed as Completed, and you can proceed to the next step.
   • When performing the final check of Step 3, it is recommended to restart the server before proceeding with the inspection.

7. After confirming that all tasks have completed successfully, click the Confirm button.

Change to an IP in the same Subnet

This explains how to configure IP settings per operating system when the IP to be changed uses the same subnet.

Linux – centos/redhat operating system

Step 1

Follow the steps below and proceed with Step 1.

1. Select the Subnet to modify.
2. Enter the IP to change.
3. Click the IP Allocation Request button.
4. When a pop-up notifying you of an IP change opens, click the Confirm button.
   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Caution

     If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Follow the steps below to perform Step 2.

1. For the IP change operation, connect to the target server using the NAT IP.

   Notice

   To prevent communication failures during operation, it is recommended to connect through another Virtual Server or Bare Metal Server created in the same subnet.

2. Enter the assigned IP from Step 1 and set the new IP on the server.

   • In the following example, replace 172.17.34.150 with the assigned IP address.
   • After checking the information of the Interface you want to change on the server, replace it with bond-srv.9 in the following example.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # nmcli con mod "Vlan bond-srv.9" ipv4.addresses 172.17.34.150/24
     # nmcli con mod "Vlan bond-srv.9" ipv4.method manual
     # nmcli  device reapply bond-srv.9

     # nmcli con mod "Vlan bond-srv.9" ipv4.addresses 172.17.34.150/24
     # nmcli con mod "Vlan bond-srv.9" ipv4.method manual
     # nmcli  device reapply bond-srv.9

     Notice

     • Setting the IP disconnects the terminal session.
     • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.

3. When all tasks are completed, select the task completion checkbox for Step 2 in the IP 변경 popup window.

   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Notice

     • If the task status of Step 2 has changed to Completed but you still have issues with terminal access, go to the All Services > Management > Support Center Contact Us menu and contact us.

Step 3

Proceed with Step 3 according to the following procedure.

1. Connect to the server to be changed using the NAT IP and check its communication status.

   • Use the following command to verify whether any pre‑change configuration information remains and whether the change was applied correctly. * If you can successfully connect to the server targeted for IP change, the changed IP is in normal communication state.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # bash /usr/local/bin/ip.sh

     # bash /usr/local/bin/ip.sh

     Reference

     The NAT IP does not change.

2. After all tasks are completed, restart the server and then perform a final check.

   Reference

   It is recommended to perform the final check after restarting the server.

3. If the final inspection shows no issues, select the work‑completion checkbox for Step 3 in the IP change popup.

Linux – Ubuntu operating system

Step 1

Follow the steps below and proceed with Step 1.

1. Select the Subnet to modify.
2. Enter the IP to change.
3. Click the IP Allocation Request button.
4. When a pop-up notifying you of an IP change opens, click the Confirm button.
   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Caution

     If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Follow the steps below to perform Step 2.

1. For the IP change operation, connect to the target server using the NAT IP.

   Notice

   To prevent communication failures during operation, it is recommended to connect through another Virtual Server or Bare Metal Server created in the same subnet.

2. Enter the assigned IP from Step 1 and set the new IP on the server.

   • In the following example, replace 172.17.34.150/24 with the assigned IP address.
   • After checking the information of the Interface you want to change on the server, replace it with bond-srv.9 in the following example.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
         ......................     Omitted
         ethernets:
         ......................     Omitted
         vlans:
             bond-srv.9:
             addresses:
                 - 172.17.34.150/24   # Enter the IP assigned in Step1.
                 gateway4: 172.17.34.2
                 id: 9
                 link: bond-srv
                 mtu: 1500
             bond-srv.350:
                 addresses:
                 - 172.16.87.150/24
                 routes:
                 - to: 172.17.87.0/24
                   via: 172.16.87.1
     - to: 172.17.87.0/24
                   via: 172.16.87.1
                 id: 350
                 link: bond-srv

     [root@localhost ~]# vi /etc/netplan/50-cloud-init.yaml
     network:
         bonds:
         ......................     Omitted
         ethernets:
         ......................     Omitted
         vlans:
             bond-srv.9:
             addresses:
                 - 172.17.34.150/24   # Enter the IP assigned in Step1.
                 gateway4: 172.17.34.2
                 id: 9
                 link: bond-srv
                 mtu: 1500
             bond-srv.350:
                 addresses:
                 - 172.16.87.150/24
                 routes:
                 - to: 172.17.87.0/24
                   via: 172.16.87.1
     - to: 172.17.87.0/24
                   via: 172.16.87.1
                 id: 350
                 link: bond-srv

3. Use the Netplan apply command to apply the changes to the system.

   • Tab 0

   Sample Code Download

   Copy Code

   Color mode

   [root@localhost ~]# netplan apply

   [root@localhost ~]# netplan apply

   Notice

   • Setting the IP disconnects the terminal session.
   • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.

4. When all tasks are completed, select the task completion checkbox for Step 2 in the IP Change popup.

   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Notice

     • If the task status of Step 2 has changed to Completed but you still have issues with terminal access, go to the All Services > Management > Support Center Contact Us menu and submit an inquiry.

Step 3

Proceed with Step 3 according to the following procedure.

1. Connect to the server to be changed using the NAT IP and check its communication status.

   • Use the following command to verify whether any pre‑change configuration information remains and whether the change was applied correctly. * If you can successfully connect to the server targeted for IP change, the new IP is operating normally.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # bash /usr/local/bin/ip.sh

     # bash /usr/local/bin/ip.sh

     Reference

     The NAT IP does not change.

2. After all tasks are completed, restart the server and then perform a final check.

   Reference

   It is recommended to perform the final check after restarting the server.

3. If there are no issues in the final inspection results, select the work completion checkbox for Step 3 in the IP Change popup window.

Windows operating system

Step 1

Follow the steps below and proceed with Step 1.

1. Select the Subnet to modify.
2. Enter the IP to change.
3. Click the IP Allocation Request button.
4. When the popup notifying IP change verification opens, click the Confirm button.
   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Caution

     If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Follow the steps below to perform Step 2.

1. For the IP change operation, connect to the target server using the NAT IP.

   Notice

   To prevent communication failures during operation, it is recommended to connect through another Virtual Server or Bare Metal Server created in the same subnet.

2. Windows Start icon, right‑click it, then run Windows PowerShell(Administrator).

3. Enter the assigned IP from Step 1 and set the new IP on the server.

   • In the following example, replace 172.17.34.150 with the assigned IP address.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     PS C:\> netsh interface ip set address "bond-srv.20" static 172.17.34.150 255.255.255.0

     PS C:\> netsh interface ip set address "bond-srv.20" static 172.17.34.150 255.255.255.0

     Notice

     • Setting the IP disconnects the terminal session.
     • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.

4. When all tasks are completed, select the task completion checkbox for Step 2 in the IP 변경 popup window.

   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Notice

     • If the task status of Step 2 has changed to Completed but you still have issues with terminal access, go to the All Services > Management > Support Center Contact Us menu and contact us.

Step 3

Proceed with Step 3 according to the following procedure.

1. Connect to the server to be changed using the NAT IP and check its communication status.

   • Use the following command to verify whether any pre‑change configuration information remains and whether the change was applied correctly. * If you can successfully connect to the server targeted for IP change, the changed IP is in normal communication state.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     PS C:\> Get-NetIPAddress | Format-Table

     PS C:\> Get-NetIPAddress | Format-Table

     Reference

     The NAT IP does not change.

2. After all tasks are completed, restart the server and then perform a final check.

   Reference

   It is recommended to perform the final check after restarting the server.

3. If there are no issues in the final inspection results, select the work completion checkbox for Step 3 in the IP Change popup window.

Change to IP of another Subnet

This explains how to configure IP settings for each operating system when the IP to be changed uses a different subnet.

Linux – centos/redhat operating system

Step 1

Follow the steps below and proceed with Step 1.

1. Select the Subnet to modify.
2. Enter the IP to change.
3. Click the IP Allocation Request button.
4. When the popup notifying IP change verification opens, click the Confirm button.
   • When the operation completes successfully, Vlan ID check, Default Gateway check information is displayed, and the operation status in the upper right corner shows Completed.
     Caution

     If you proceed with the IP allocation request of Step 1, you cannot cancel or restore the IP change.

Step 2

Follow the steps below to perform Step 2.

1. For the IP change operation, connect to the target server using the NAT IP.

   Notice

   To prevent communication failures during operation, it is recommended to connect through another Virtual Server or Bare Metal Server created in the same subnet.

2. Add a new VLAN and configure the IP to add the IP to the server.

   • Add VLAN: Create the interface of the Vlan ID identified in Step 1. * In the following example, enter the assigned ID instead of 20.
   • IP configuration: Enter the IP assigned in Step 1. * In the following example, replace 192.168.0.10/24 with the assigned IP address.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # nmcli conn add type vlan ifname "bond-srv.20" con-name "bond-srv.20" id 20 dev bond-srv
     # nmcli con mod bond-srv.20 con-name "Vlan bond-srv.20"
     # nmcli con mod "Vlan bond-srv.20" ipv4.addresses 192.168.0.10/24
     # nmcli con mod "Vlan bond-srv.20" ipv4.method manual
     # nmcli con mod "Vlan bond-srv.20" ipv6.method "ignore"
     # nmcli con up  "Vlan bond-srv.20"

     # nmcli conn add type vlan ifname "bond-srv.20" con-name "bond-srv.20" id 20 dev bond-srv
     # nmcli con mod bond-srv.20 con-name "Vlan bond-srv.20"
     # nmcli con mod "Vlan bond-srv.20" ipv4.addresses 192.168.0.10/24
     # nmcli con mod "Vlan bond-srv.20" ipv4.method manual
     # nmcli con mod "Vlan bond-srv.20" ipv6.method "ignore"
     # nmcli con up  "Vlan bond-srv.20"

3. Set the default gateway for the new VLAN.

   • Default gateway configuration: Enter the Default gateway IP assigned in Step 1. * In the following example, replace 192.168.0.1 with the assigned Default gateway IP.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # nmcli con mod "Vlan bond-srv.20"  ipv4.gateway 192.168.0.1
     # nmcli device reapply bond-srv.20

     # nmcli con mod "Vlan bond-srv.20"  ipv4.gateway 192.168.0.1
     # nmcli device reapply bond-srv.20

     Notice

     • If you set a Default Gateway on a new VLAN, the terminal session gets disconnected.
     • Step 2 After completing the task, if the task status changes to Completed, you can reconnect to the terminal.

4. When all tasks are completed, select the task completion checkbox for Step 2 in the IP 변경 popup window.

   • When the task completes successfully, the task status in the upper right corner will be displayed as Completed.
     Notice

     • If the task status of Step 2 has changed to Completed but you still experience problems with terminal access, navigate to the All Services > Management > Support Center Contact Us menu and submit an inquiry.

Step 3

Proceed with Step 3 according to the following procedure.

1. Connect to the server subject to IP change using a NAT IP.

2. Verify the Default Gateway IP of the existing (pre-change) interface, then delete it.

   • In the following example, replace 192.168.10.1 with the IP you verified.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # ip route del   default  via 192.168.10.1

     # ip route del   default  via 192.168.10.1

3. Connect to the server to be changed using the NAT IP and check its communication status.

   • Use the following command to verify whether any pre‑change configuration information remains and whether the changes were applied correctly. * If you can successfully connect to the server targeted for IP change, the changed IP is in normal communication state.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # netstat –nr
     # bash /usr/local/bin/ip.sh

     # netstat –nr
     # bash /usr/local/bin/ip.sh

     Reference

     The NAT IP does not change.

4. Check the VLAN information of the existing IP and then delete it from the server.

   • Enter the verified ID in place of 30 in the following example.
     • Tab 0

     Sample Code Download

     Copy Code

     Color mode

     # nmcli con delete "Vlan bond-srv.30"

     # nmcli con delete "Vlan bond-srv.30"

5. After all tasks are completed, restart the server and then perform a final check.

   Reference

   It is recommended to perform the final check after restarting the server.

6. If the final inspection results show no issues, select the work‑completion checkbox for Step 3 in the IP Change popup window.