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. Click the All Services > Compute > Bare Metal Server menu. Navigate to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Create Bare Metal Server button. You will be taken to the Create Bare Metal Server page.
3. On the 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
     Image version	Required	Select version of the chosen image Provide a list of versions for the supplied server image

     Table. Bare Metal Server image and version input fields
   • 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 Server instances to create simultaneously Only numeric input is allowed, and it must be between 1 and 5
     Service Type > Server Type	Required	Bare Metal Server server type Select the desired vCPU, Memory, Disk specifications For detailed information about the server types provided by Bare Metal Server, refer to Bare Metal Server Server Type
     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, refer to Planned Compute Apply
     Automation account	Required	Automatically create an account to provide automation features after creating a Bare Metal Server This account is used only for inter-system interfaces The password is encrypted and cannot be accessed from outside the system If the account is deleted, network changes and some automation functions may be restricted

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

     Category	Required	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 Set the hostname to the entered server name Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) to enter between 3 and 15 characters Must not end with a special character (-)
     Server name Prefix	Required	Enter a prefix to distinguish each Bare Metal Server generated when the selected number of servers is 2 or more Automatically generated in the form of user input value (prefix) + ‘-###’ Must start with a lowercase English letter and be 3 to 15 characters long, using lowercase letters, numbers, and special characters (-) Must not end with a special character (-)
     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 set to auto‑generate or user input, and if input is selected, the user enters the IP manually NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway Checking the option allows selection of a NAT IP NAT IP: Select a NAT IP If no NAT IP is available, click the Create New button to generate a Public IP Refresh button to view and select the created 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 set to auto‑generate or user input, and if input is selected, the user enters the IP manually

     Table. Required information input fields for Bare Metal Server

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

   Category	Required	Detailed description
   Local disk partition	Selection	Set usage of local disk partitions Up to 10 partitions can be created, including the root partition Up to 90% of total capacity can be used After checking Use, partition information can be set Set root partition information Partition type: flat or 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 (-_) Partition size: enter at least 50 GB Filesystem type: select according to the image used 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 Filesystem type cannot be entered when it 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 size of partition disks cannot exceed the available capacity Set additional partition information Partition type: flat or 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 (-_) Partition size: enter at least 1 GB Filesystem type: select according to the image used> 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 Filesystem type cannot be entered when it 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 size of partition disks 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 accidental actions that could terminate, start, or stop the server.
   Hyper Threading	Selection	Set the logical core count to operate at twice the number of physical cores To turn off Hyper-Threading, clear the checkbox Cannot be changed after server creation
   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 entry fields
5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.
   • Once creation is complete, check the created resources on the Bare Metal Server List page.

Bare Metal Server Check detailed information

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

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

1. All Services > Compute > Bare Metal Server Click the menu. Navigate to the Service Home page of Bare Metal Server.
2. On the Service Home page, click the Bare Metal Server menu. You will be taken to the Bare Metal Server List page.
3. Bare Metal Server List page, click the resource to view detailed information. You will be taken to the Bare Metal Server Details page.
   • The Bare Metal Server Details page displays status information and additional feature information, and consists of Details, Tags, Activity Log tabs.

     Category	Detailed description
     Bare Metal Server status	Status of user-created Bare Metal Server Creating: state while the server is being created Running:: state after creation, ready for use Editing:: state while IP is being changed Unknown: error state Starting: state while the server is starting Stopping: state while the server is stopping Stopped: state after the server has stopped Terminating: state while termination is in progress Terminated: state after termination is complete
     Server control	Button to change server status Start: Start a stopped server Stop: Stop a running server
     Service termination	Cancel service button

     Table. Bare Metal Server status information and additional features

Detailed Information

Bare Metal Server List page lets you view detailed information of the selected resource and modify it if necessary.

tag

On the Bare Metal Server List page, you can view the tag information of the selected resource, and 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 the tasks on the Bare Metal Server List or Bare Metal Server Details page.

Bare Metal Server Operation Control

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

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

1. Click the All Services > Compute > Bare Metal Server menu. You will be taken to the Service Home page of the Bare Metal Server.
2. On the Service Home page, click the Bare Metal Server menu. You will be taken to the Bare Metal Server List page.
3. Bare Metal Server List page allows you to select multiple servers and control them simultaneously using the Start and Stop buttons at the top of the table.
   • Bare Metal Server Details 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 Details page.
5. Check the server status and complete the changes using each Server Management button.
   • Start: Starts a 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. Click the All Services > Compute > Bare Metal Server menu. Navigate to the Service Home page of the Bare Metal Server.
2. Click the Bare Metal Server menu on the Service Home page. You will be taken to the Bare Metal Server List page.
3. On the Bare Metal Server List page, click the server to which you want to add Block Storage. You will be taken 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 the addition of Block Storage opens, click the Confirm button. You will be taken to the Block Storage (BM) Creation 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), please refer to Create Block Storage(BM).
7. Go to the Bare Metal Server Details page where Block Storage was added and verify that Block Storage has been added.

Terminate Bare Metal Server

Terminating an unused Bare Metal Server can reduce operating costs. However, terminating a Bare Metal Server may cause the running service to stop immediately, so you should proceed with termination only after fully considering the impact of service interruption.

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

1. Click the All Services > Compute > Bare Metal Server menu. Navigate to the Service Home page of the Bare Metal Server.
2. Click the Bare Metal Server menu on the Service Home page. You will be taken to the Bare Metal Server List page.
3. 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 it by clicking the Service Termination button on the Bare metal Server Details page of the resource to be terminated.
4. When termination is complete, verify on the Bare Metal Server list page that the resource has been terminated.

Cancellation constraints

If termination is not possible when requesting cancellation of a Bare Metal Server, a popup will inform you. Please refer to the cases 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 directly configure the network settings of the local Subnet.

first connection(kr-west)

There is no local Subnet currently connected to the Bare Metal Server, and if you are adding the first connection, follow the guide below.

Linux - Configuring 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.

   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 ID and IP in the example code with the assigned ID and IP.
     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** page: enter the Interface Name you verified.
                 - ens4f1      // **Bare Metal Server Details** page: enter the Interface Name you verified.
                 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 it 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** page: enter the Interface Name you verified.
                 - ens4f1      // **Bare Metal Server Details** page: enter the Interface Name you verified.
                 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 it to the VLAN ID verified in the SCP Console.
                 link: bond-mgt
                 mtu: 1500

4. Apply the changes to the system.

   Sample Code Download

   Copy Code

   Color mode

   # netplan apply

   # netplan apply

5. Check the interface status.

   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.

   Sample Code Download

   Copy Code

   Color mode

   #!/usr/bin/bash
   
   IP_ADDR="10.1.1.3/24"   // Set the local Subnet IP as verified in the Console.
   VLAN_ID="7"             // Set the Vlan ID you verified in the console.
   
   BOND_NAME="bond-mgt"
   BOND_IF_name1="ens2f1"  // **Bare Metal Server Details** Enter the Interface Name as shown on the 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 verified in the Console.
   VLAN_ID="7"             // Set the Vlan ID you verified in the console.
   
   BOND_NAME="bond-mgt"
   BOND_IF_name1="ens2f1"  // **Bare Metal Server Details** Enter the Interface Name as shown on the 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.

   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. 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 confirmed on the Bare Metal Server Details page.
     

5. Create a teaming.

   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 verified on the Bare Metal Server Details page.
     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 already connected to the Bare Metal Server and you are adding the first connection, follow the guide below.

Linux - Configuring 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.

   • Change the ID and IP in the example code to the assigned ID and IP.
     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 in the console instead of 21.
             addresses:
                 - 192.168.0.20/24 // Set it to the local Subnet IP you 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 in the console instead of 21.
             addresses:
                 - 192.168.0.20/24 // Set it to the local Subnet IP you 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.

   Sample Code Download

   Copy Code

   Color mode

   # netplan apply

   # netplan apply

3. Check the interface status.

   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. Check the Bond Name for the local Subnet.
   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.
   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 you verified in the console.
   
   BOND_NAME="bond-mgt" // Set the Bond Name identified in step 1.
   
   # 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 you verified in the console.
   
   BOND_NAME="bond-mgt" // Set the Bond Name identified in step 1.
   
   # 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.
   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.

   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 verified in step 2, and the Vlan ID and local Subnet IP verified in the Console.
     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. Run ncpa.cpl from the Windows Run menu 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.

Since a Bonding was already created when connecting the first local Subnet, there is no need to create a 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, configure the IP.

   • Change the ID and IP in the example code to the assigned ID and IP.
     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 it 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 it to the VLAN ID verified in the console.
                 link: bond-mgt
                 mtu: 1500

2. Apply the changes to the system.

   Sample Code Download

   Copy Code

   Color mode

   # netplan apply

   # netplan apply

3. Check the interface status.

   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 – Setting 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. Verify the Bond Name for the local Subnet.
   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.
   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" // Set the Bond Name confirmed in step 1.
   
   # 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" // Set the Bond Name confirmed in step 1.
   
   # 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.
   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 launch the Windows PowerShell(Administrator) program.

2. Check the Teaming name for the local Subnet.

   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, and the local Subnet IP confirmed in the Console.
     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. Run ncpa.cpl from the Windows Run menu to check the interface status.

   

Change IP

The IP address may be changed to carry out migration, server replacement, and similar operations.

To change the IP, follow the steps below.

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

2. Click the Bare Metal Server menu on the Service Home page. You will be taken to the Bare Metal Server List page.

3. Bare Metal Server List page, click the server whose IP you want to change. You will be taken to the Bare Metal Server Details page.

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

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

6. In the IP Change popup, complete Step 1, Step 2, and Step 3 in order.

   information

   • When changing an 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 examples and perform the work for each step.
     • When changing to an IP that uses the same subnet: Change to an IP in the same Subnet See
     • When changing to an IP that uses a different subnet: see Changing to an IP in a different Subnet
   • When each step is completed successfully, the task status in the upper right corner is shown 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 document 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 procedure below to carry out Step 1.

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

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

Step 2

Follow the procedure below to carry out Step 2.

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

   guide

   To prevent situations where communication becomes impossible during operation, we recommend connecting via another Virtual Server or Bare Metal Server created in the same subnet.

2. Enter the IP assigned in Step 1 and configure 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.
     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

     information

     • 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 Step 2 completion checkbox in the IP Change popup window.

   • When the task completes successfully, the task status in the upper right corner is displayed as Completed.
     information

     • 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

Follow the procedure below to carry out Step 3 work.

1. Connect to the server subject to IP change using the NAT IP and check the communication status.

   • Use the following command to verify whether any pre‑change configuration remains and whether the change was applied correctly. If you can connect successfully to the target server whose IP was changed, the new IP is communicating properly.
     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 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.

Linux – Ubuntu operating system

Step 1

Follow the procedure below to carry out Step 1.

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

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

Step 2

Follow the procedure below to perform Step 2.

1. To perform the IP change, connect to the target server using its NAT IP.

   Information

   To prevent situations where communication becomes impossible during operation, we recommend connecting via another Virtual Server or Bare Metal Server created in the same subnet.

2. Enter the IP assigned in Step 1 and configure 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 the following example bond-srv.9.
     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.

   Sample Code Download

   Copy Code

   Color mode

   [root@localhost ~]# netplan apply

   [root@localhost ~]# netplan apply

   information

   • 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 window.

   • When the task completes successfully, the task status in the upper right corner is displayed as Completed.
     information

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

Step 3

Follow the procedure below to carry out Step 3.

1. Connect to the server subject to IP change using the NAT IP and check the communication status.

   • Use the following command to verify whether any pre‑change configuration remains and whether the change was applied correctly. If you can connect successfully to the target server whose IP was changed, the new IP is communicating properly.
     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 results show no issues, select the work completion checkbox for Step 3 in the IP Change popup window.

Windows operating system

Step 1

Follow the procedure below to perform Step 1 work.

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

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

Step 2

Follow the procedure below to perform Step 2.

1. To perform the IP change, connect to the target server using its NAT IP.

   Information

   To prevent communication failures during operation, we recommend connecting through another Virtual Server or Bare Metal Server created in the same subnet.

2. Right-click the Windows Start icon, then run Windows PowerShell(Administrator).

3. Enter the assigned IP from Step 1 and set the IP to be changed on the server.

   • In the following example, replace 172.17.34.150 with the assigned IP address.
     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

     information

     • 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 window.

   • When the task completes successfully, the task status in the upper right corner is displayed as Completed.
     Information

     • 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

Follow the procedure below to carry out Step 3.

1. Connect to the server targeted for IP change using its NAT IP and verify the communication status.

   • Use the following command to verify whether any pre‑change configuration remains and to confirm that the change was applied correctly. If you can connect successfully to the target server whose IP was changed, the new IP is communicating properly.
     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 an IP of a different 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 procedure below to carry out Step 1.

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

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

Step 2

Follow the steps below to carry out Step 2.

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

   information

   To prevent situations where communication becomes impossible during operation, we recommend connecting via another Virtual Server or Bare Metal Server created in the same subnet.

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

   • Add VLAN: Create the interface for the Vlan ID identified in Step 1. In the following example, replace 20 with the assigned ID.
   • IP configuration: Enter the IP assigned in Step 1. In the following example, replace 192.168.0.10/24 with the assigned IP.
     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. Configure the default gateway for the new VLAN.

   • Default gateway setting: Enter the Default gateway IP assigned in Step 1. In the following example, replace 192.168.0.1 with the assigned Default gateway IP.
     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

     Info

     • Setting a Default Gateway on a new VLAN 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 of Step 2 in the IP change popup window.

   • When the task completes successfully, the task status in the upper right corner is displayed as Completed.
     information

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

Step 3

Follow the procedure below to proceed with Step 3.

1. Connect to the server to be changed using the NAT IP.

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

   • In the example below, replace 192.168.10.1 with the IP you have verified.
     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 subject to IP change using the NAT IP and check the communication status.

   • Use the following command to verify whether any pre‑change configuration remains and whether the change was applied correctly. If you can connect successfully to the target server whose IP was changed, the new IP is communicating properly.
     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. Verify the VLAN information of the existing IP and delete it from the server.

   • Enter the verified ID in place of 30 in the following example.
     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.

Linux – Ubuntu operating system

Step 1

Follow the procedure below to perform Step 1.

1. Select the Subnet to modify.
2. Enter the IP address to change.
3. Click the IP Allocation Request button.
4. When a popup notifying you of an IP change opens, click the Confirm button.
   • When the operation completes successfully, Vlan ID verification, Default Gateway verification 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 revert the IP change.

Step 2