--- layout: "docs" page_title: "Commands: node-status" sidebar_current: "docs-commands-node-status" description: > Display information about nodes. --- # Command: node-status The `node-status` command is used to display information about client nodes. A node must first be registered with the servers before it will be visible in this output. ## Usage ``` nomad node-status [options] [node] ``` If no node ID is passed, then the command will enter "list mode" and dump a high-level list of all known nodes. This list output contains less information but is a good way to get a bird's-eye view of things. If there is an exact match based on the provided node ID or prefix, then that particular node will be queried, and detailed information will be displayed. Otherwise, a list of matching nodes and information will be displayed. If running the command on a Nomad Client, the -self flag is useful to quickly access the status of the local node. ## General Options <%= general_options_usage %> ## Node Status Options * `-short`: Display short output. Used only when querying a single node. * `-verbose`: Show full information. * `-allocs`: Show running allocations per node. * `-self`: Query the status of the local node. ## Examples List view: ``` $ nomad node-status ID DC Name Drain Status a72dfba2 dc1 node1 false ready 1f3f03ea dc1 node2 false ready ``` List view, with running allocations: ``` $ nomad node-status -allocs ID DC Name Class Drain Status Running Allocs 4d2ba53b dc1 node1 false ready 1 34dfba32 dc1 node2 false ready 3 ``` Single-node view in short mode: ``` $ nomad node-status -short 1f3f03ea ID = c754da1f Name = nomad Class = DC = dc1 Drain = false Status = ready ``` Full output for a single node: ``` $ nomad node-status 1f3f03ea ID = c754da1f Name = nomad Class = DC = dc1 Drain = false Status = ready ==> Resource Utilization CPU Memory MB Disk MB IOPS 0/2600 0/1997 0/34374 0/0 ==> Allocations ID Eval ID Job ID Task Group Desired Status Client Status 3d743cff 2fb686da example cache run complete ``` Using `-self` when on a Nomad Client: ``` $ nomad node-status -self ID = c754da1f Name = nomad Class = DC = dc1 Drain = false Status = ready ==> Resource Utilization CPU Memory MB Disk MB IOPS 0/2600 0/1997 0/34374 0/0 ==> Allocations ID Eval ID Job ID Task Group Desired Status Client Status 3d743cff 2fb686da example cache run complete ``` To view verbose information about the node: ``` $ nomad node-status -verbose c754da1f ID = c754da1f-6337-b86d-47dc-2ef4c71aca14 Name = nomad Class = DC = dc1 Drain = false Status = ready ==> Resource Utilization CPU Memory MB Disk MB IOPS 0/2600 0/1997 0/34374 0/0 ==> Allocations ID Eval ID Job ID Task Group Desired Status Client Status 3d743cff-8d57-18c3-2260-a41d3f6c5204 2fb686da-b2b0-f8c2-5d57-2be5600435bd example cache run complete ==> Attributes arch = amd64 cpu.frequency = 1300.000000 cpu.modelname = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz cpu.numcores = 2 cpu.totalcompute = 2600.000000 driver.docker = 1 driver.docker.version = 1.10.3 driver.exec = 1 driver.java = 1 driver.java.runtime = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2) driver.java.version = 1.7.0_95 driver.java.vm = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) driver.qemu = 1 driver.qemu.version = 2.0.0 driver.raw_exec = 1 driver.rkt = 1 driver.rkt.appc.version = 0.7.4 driver.rkt.version = 1.2.0 hostname = nomad kernel.name = linux kernel.version = 3.19.0-25-generic memory.totalbytes = 2094473216 nomad.revision = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES' nomad.version = 0.3.2dev os.name = ubuntu os.version = 14.04 unique.cgroup.mountpoint = /sys/fs/cgroup unique.network.ip-address = 127.0.0.1 unique.storage.bytesfree = 36044333056 unique.storage.bytestotal = 41092214784 unique.storage.volume = /dev/mapper/ubuntu--14--vg-root ```