mc admin info

The mc admin info command displays information on an AIStor server. For distributed AIStor deployments, mc admin info displays information for each node in the deployment.

The output of the command resembles the following for a four-node cluster:

●  node1.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 4/4 OK
   Drives: 4/4 OK
   Pool: 1

●  node2.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 4/4 OK
   Drives: 4/4 OK
   Pool: 1

●  node3.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 4/4 OK
   Drives: 4/4 OK
   Pool: 1

●  node4.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 4/4 OK
   Drives: 4/4 OK
   Pool: 1

Pools:
   1st, Erasure sets: 1, Drives per erasure set: 16

1.5 TiB Used, 12 Buckets, 48000 Objects
16 drives online, 0 drives offline, EC:4

Syntax

Example Syntax

The command has the following syntax:

mc admin info TARGET      \
              [--offline]

Brackets [] indicate optional parameters.
Parameters sharing a line are mutually dependent.
Parameters separated using the pipe | operator are mutually exclusive.

Copy the example to a text editor and modify as-needed before running the command in the terminal/shell.

Parameters

TARGET

Required

The alias about which you want to display information.

--offline

Optional

Show only offline drives or nodes.

Node states

The mc admin info command displays the current state of each node in the cluster. Nodes can be in one of the following states:

State	Description
Online	Node is operational and serving requests. Displays uptime duration.
Draining	Node is completing existing requests before cordoning. Displayed in yellow.
Cordoned	Node is offline for maintenance. Displayed in yellow.
Offline	Node is not responding. Displayed in red.

For cordoned or draining nodes, the output displays the state in place of the uptime. The following example shows a four-node cluster with one node cordoned for maintenance:

●  node1.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 3/4 OK
   Drives: 4/4 OK
   Pool: 1

●  node2.example.com:9000
   Uptime: cordoned
   Drives: 0/4 OK
   Pool: 1

●  node3.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 3/4 OK
   Drives: 4/4 OK
   Pool: 1

●  node4.example.com:9000
   Uptime: 3 days
   Version: 2025-01-01T00-00-00Z
   Network: 3/4 OK
   Drives: 4/4 OK
   Pool: 1

Pools:
   1st, Erasure sets: 1, Drives per erasure set: 16

1.5 TiB Used, 12 Buckets, 48000 Objects
12 drives online, 4 drives offline, EC:4