Documentation Index

Fetch the complete documentation index at: https://cli.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

getServerSpecDetail

Prev Next

Available in VPC

Get details of a server specification.

Syntax

The getServerSpecDetail syntax is as follows:

./ncloud vserver getServerSpecDetail \
    --serverSpecCode <server-spec-code> \
    [--regionCode <KR|SGN|JPN>] \
    [--output <json|xml>]

Options

This section describes the options available when running getServerSpecDetail.

Required options

The following options are required for getServerSpecDetail.

Options Type Required Description
--serverSpecCode String Required Server specification code

Common options

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

Examples

If the request to view detailed server specifications is successful, the server's identification information and specifications are returned.

Command

The command example is as follows:

./ncloud vserver getServerSpecDetail \
    --serverSpecCode c2-g3 \
    --regionCode KR \
    --output json

Output

The output example is as follows:

{
  "getServerSpecDetailResponse": {
    "totalRows": 1,
    "serverSpecList": [
      {
        "serverSpecNo": 236,
        "serverSpecCode": "c2-g3",
        "hypervisorType": {
          "code": "KVM",
          "codeName": "KVM"
        },
        "generationCode": "G3",
        "cpuArchitectureType": {
          "code": "X86_64",
          "codeName": "x86 64bit"
        },
        "cpuCount": 2,
        "memorySize": 4294967296,
        "blockStorageMaxCount": 20,
        "blockStorageMaxIops": 5250,
        "blockStorageMaxThroughput": 84934656,
        "networkPerformance": 1000000000,
        "networkInterfaceMaxCount": 3,
        "serverSpecDescription": "vCPU 2EA, Memory 4GB",
        "serverProductCode": "SVR.VSVR.HICPU.C002.M004.G003"
      }
    ],
    "requestId": "a7b8c9d0-e1f2-3456-abcd-789012345678",
    "returnCode": "0",
    "returnMessage": "success"
  }
}