- Print
- PDF
Network Interface
- Print
- PDF
Available in VPC
Network Interface describes the screen configuration of the Network Interface menu and network interface information, and explains how to create and manage the network interface.
Network Interface is a service for creating network interfaces that can be assigned to servers. Servers with the network interface applied are able to conduct independent network communications through subnets.
You need to create a private subnet and VPC beforehand to use Network Interface. For how to create, see the following guides:
See the following usage tips related to network interfaces.
- You can utilize network interfaces to distinguish multiple servers intuitively based on their purpose of use.
<example> Distinguish 10.1.1.1x as the development server and 10.1.1.2x as the operational server - Create multiple network interfaces in the following cases:
- When you need different subnets based on the characteristics of applications to be used on servers
- When you designed subnets separated by purpose but need to integrate them into one server for use
Check network interface information
You can check network interface information on the Network Interface page.
Network Interface page
From the NAVER Cloud Platform portal, click the Console > Services > Compute> Server > Network Interface menus, in that order, to view the Network Interface page.
The Network Interface page is laid out as follows:
Area | Description |
---|---|
① Menu name | Name of the menu currently being checked and the number of created network interfaces |
② Basic features | Features provided when you initially enter the Network Interface menu
|
③ Post-creation functions | Features provided after creating network interface
|
④ Search bar and filter | You can search the network interface by IP address and network interface/applied server/ VPC/subnet name, and filter in accordance with the creation types and allocation status |
⑤ Network interface list | List of created network interfaces
|
Create network interface
The following describes how to create a network interface.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Compute > Server, in order.
- Click the Network Interface menu.
- Click the [Create network interface] button.
- Specify the settings in the Create network interface pop-up window.
- Network Interface name: it must start with an English letter. Enter between 3-30 characters using lowercase English letters, numbers, and hyphens (-)
- VPC: select VPC to place the network interface
- Subnet: select the subnet to place the network interface
- Primary IP: select Automatic assignment or Enter directly, and enter the IP to be used by the relevant network interface
- Secondary IP: create a subsidiary IP to be used in the same subnet
- Enter the IP in the entry field and click the [Add] button
- Leaving the field blank and clicking the [Add] button automatically assigns it
- To delete the entered IP, click the [x] button
- ACG: select ACG to place the network interface
- You can select up to 3 ACGs, and the applicable ACG differs according to the subnet
- Usage: usage of the network interface, automatically selected as General (exclusively for general VM) or BareMetal (exclusively for the bare metal servers) in accordance with the selected subnet
- Select applied server: select the server to assign the network interface
- Click the [Create] button.
- The created network interface is displayed in the list.
Assign network interface
Among the network interfaces placed in Private Subnet, you can assign the network interfaces not assigned to a server to a server.
The following describes how to assign a network interface to a server.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Compute > Server, in order.
- Click the Network Interface menu.
- In the network interface list, click to select the network interface to assign to the server, and then click the [Assign to server] button.
- Select the server for application in the Assign pop-up window, then click the [OK] button.
- The network interface is assigned to the selected server.
Activate network interface
See the guide for the server OS you are using to activate the added network interface on the server.
CentOS
Access the server and run the following commands: The example activates eth1:
For bare metal servers, enter bond1
instead of eth1
as the value of the device.
$> vi /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
BOOTPROTO=static
Enter IPADDR=Interface IP
NETMASK=255.255.255.0
ONBOOT=yes
$> ifup eth1
Ubuntu
Access the server and run the following commands: The example activates eth1:
For bare metal servers, enter eth3
instead of eth1
as the value of the device.
In the versions of Ubuntu 18.04 and above, you can configure networks with legacy or netplan. However, for Ubuntu 16.04, configure networks with the legacy method.
Legacy configuration
$> vi /etc/network/interfaces
auto eth1
iface eth1 inet static
Enter # eth1 IP
address 192.168.1.8
# Enter subnet mask
netmask 255.255.255.0
$> ifup eth1
$> ip addr list eth1
Netplan configuration
$> vi /etc/netplan/00 Installing-netcfg.yaml
network:
ethernets:
# Enter eth1 IP / subnet mask
eth1:
addresses: [192.168.1.8/24]
version: 2
$> netplan --debug apply
$> ip addr list eth1
Windows
Access the server and run the following tasks:
- Click > > Network & Internet > Change adapter options, in that order.
- Right-click the icon for the added network interface, then click Properties.
- Click the [Networking] tab, click to select Internet Protocol Version 4 (TCP/IPv4), and then click the [Properties] button.
- Click to select Use the following IP address, enter the IP address of the network interface in IP address, and then enter "255.255.255.0" for Subnet mask.
- Click the [OK] button.
Remove assignment of network interface
The following describes how to remove an assigned network interface from a server.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Compute > Server, in order.
- Click the Network Interface menu.
- From the network interface list, click to select the network interface to remove from the server, and then click the [Remove from server] button.
- Check the details in the assignment removal pop-up window, and then click the [Remove] button.
- The network interface is removed from the assigned server.
Return network interface
The following describes how to terminate an unused network interface.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Compute > Server, in order.
- Click the Network Interface menu.
- In the network interface list, click to select the network interface to terminate, and then click the [Terminate] button.
- Check the details in the terminate pop-up window and click the [Terminate] button.
- When assigned to a server, the [Terminate] button is activated only when you agree to the removal of assignment.
- The network interface is terminated and disappears from the list.
Set flow log
Flow log is a function to store the communication logs generated in the network interface in Object Storage. You can set to filter and save only the communication details allowed or rejected by the ACG applied to the network interface.
The following describes how to change the flow log settings.
- To use the Set Flow log function, you must subscribe to Object Storage and have a created bucket. (See Getting started with Object Storage)
- If the bucket selected as the storage position of the log is locked, some of the log may be missed. Pay attention to the bucket lock settings. (See Using object lock)
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Compute > Server, in order.
- Click the Network Interface menu.
- Click to select the network interface to change the flow log settings in the network interface list, and then click the [Set flow log] button.
- Specify the settings in the Set Flow log pop-up window, and then click the [Set] button.
You cannot create flow logs for network interfaces created in subnets dedicated to SFC.
Collection action: select among ALLOW, DENY, or ALL for the collection action
Collection unit (minute): enter the collection cycle between 5-15 minutes (default: 15 minutes)
Bucket name: select the bucket to save the collected logs
- The file name will be generated in the format of ${Region number }${FLOWLOG_configured_NETWORK-INTERFACE_number}${FLOWLOG collection interval_reference time}.
<example>1_000123000_2023-01-01T04:21:00Z_0.log
- The file name will be generated in the format of ${Region number }${FLOWLOG_configured_NETWORK-INTERFACE_number}${FLOWLOG collection interval_reference time}.
Bucket folder name: enter the name of the bucket folder to save the collected logs
The log description is as follows:
(For ncloud resources that have both Public IP and Private IP, the Private IP will be displayed.)Field name Description LOG_TIME Log occurrence time (epoch) DIRECTION Packet direction (inbound/outbound) REGION NCP Region number VPC_NM VPC name VPC_NO VPC unique ID SBNET_NO Subnet unique ID INSTC_NO VM unique ID NIC_ID Network interface unique ID SRC_ADDR Source address of traffic SRC_PORT Source port of traffic DST_ADDR Destination address of traffic DST_PORT Destination port of traffic ACTION ACG setting rules (ALL, ALLOW, DENY) PROTOCOL Communication protocol (TCP, UDP, ICMP) TP_CD Type of network interface
To delete the applied flow log settings, click the [Delete] button from the Flow log of the network interface details. Even if you delete the flow log settings, the logs already saved to Object Storage are not deleted.
Set secondary IP
Secondary IP is a feature that adds secondary IPs to network interfaces assigned to servers to be utilized for HA solutions and so on.
- You can use them if you need to use several IPs in a single subnet.
<example> If you have created redundancy with an Active server and Standby server in a cluster, you can move a secondary IP for services between the two servers. - Up to 5 secondary IPs can be manually specified or randomly assigned within the IP range of the subnet that the network interface belongs to.
The following describes how to change the secondary IP settings.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Compute > Server, in order.
- Click the Network Interface menu.
- Click to select the network interface to change the Secondary IP settings for in the network interface list, and then click the [Set Secondary IP] button.
- Change the settings from the Set Secondary IP pop-up window, and then click the [Set] button.
- Enter the IP in the input field, and click the [Add] button.
- Leaving the field blank and clicking the [Add] button automatically assigns the IP.
- To delete the entered IP, click the [x] button.
Activate Secondary IP
For Secondary IPs to function properly, they need to be created and changed from the console, and then set up from the server. The following describes how to change the Secondary IP settings for each server OS.
CentOS
Access the server and run the following commands: The following example configures a secondary IP on eth1:
$> vi /etc/sysconfig/network-scripts/ifcfg-eth1:0
DEVICE=eth1:0
BOOTPROTO=static
# Enter secondary IP
IPADDR=192.168.1.9
# Enter subnet mask
NETMASK=255.255.255.0
ONBOOT=yes
$> ifup eth1:0
$> ip addr list eth1
Ubuntu
Access the server and run the following commands: The following example configures a secondary IP on eth1:
In the versions of Ubuntu 18.04 and above, you can configure networks with legacy or netplan.
However, for Ubuntu 16.04, configure networks with the legacy method.
Legacy configuration
While working with setting up a network, the network connection may be temporarily interrupted. Therefore, please do not include the services in operation to the tasks if possible.
$> vi /etc/network/interfaces
auto eth1
iface eth1 inet static
# Enter eth1 IP
address 192.168.1.8
# Enter subnet mask
netmask 255.255.255.0
iface eth1 inet static
# Enter secondary IP
address 192.168.1.9
# Enter subnet mask
netmask 255.255.255.0
$> systemctl restart networking.service
$> ip addr list eth1
Netplan configuration
$> vi /etc/netplan/00-installer-config.yaml
network:
ethernets:
# Enter primary eth1 IP, secondary IP / subnet mask
eth1:
addresses: [192.168.1.8/24, 192.168.1.9/24]
version: 2
$> netplan --debug apply
$> ip addr list eth1
Windows
Access the server and run the following tasks:
- Click > > Network & Internet > Change adapter options, in that order.
- Right-click the icon for the added network interface, and then click Properties.
- Click the [Networking] tab, click to select Internet Protocol Version 4 (TCP/IPv4), and then click the [Properties] button.
- Click the [Advanced] button.
- Click the [Add] button from the IP address area.
- Enter the added Secondary IP address, then click the [OK] button.