attachNetworkInterface

Available in VPC

Assign a network interface to a server instance.

Syntax

The attachNetworkInterface syntax is as follows:

./ncloud vserver attachNetworkInterface \
    --subnetNo <subnet-no> \
    --networkInterfaceNo <nic-no> \
    --serverInstanceNo <server-instance-no> \
    [--regionCode <KR|SGN|JPN>] \
    [--output <json|xml>]

Options

This section describes the options available when running attachNetworkInterface.

Required options

The following options are required for attachNetworkInterface.

Common options

For information about the options common to all vserver subcommands, see Server (VPC) options.

Examples

If the network interface allocation request is successful, the latest information about the network interface is returned.

Command

The command example is as follows:

./ncloud vserver attachNetworkInterface \
    --subnetNo 23456789 \
    --networkInterfaceNo 56789012 \
    --serverInstanceNo 34567890 \    
    --regionCode KR \
    --output json

Output

The output example is as follows:

{
  "attachNetworkInterfaceResponse": {
    "totalRows": 1,
    "networkInterfaceList": [
      {
        "networkInterfaceNo": "56789012",
        "networkInterfaceName": "test-nic-01",
        "subnetNo": "23456789",
        "deleteOnTermination": false,
        "isDefault": false,
        "deviceName": "eth1",
        "networkInterfaceStatus": {
          "code": "SET",
          "codeName": "Configuring"
        },
        "instanceType": {
          "code": "VSVR",
          "codeName": "Server (VPC)"
        },
        "instanceNo": "34567890",
        "ip": "192.0.2.10",
        "macAddress": "F2:20:AF:00:00:01",
        "enableFlowLog": false,
        "accessControlGroupNoList": [],
        "networkInterfaceDescription": "Test network interface",
        "secondaryIpList": [
          "192.0.2.11"
        ]
      }
    ],
    "requestId": "e4f56789-0123-4567-ef01-456789012345",
    "returnCode": "0",
    "returnMessage": "success"
  }
}