Skip to content

ybcli: status

Return the status of various system components.

status all
status blade [ <chassis>/<bay> ]
status cmp [ <chassis>/<cmp> ]
status database
status manager [ local | remote | all ]
status storage
status system

Note: For status blade and status cmp, specify a chassis number (or all) and a bay or cmp number (or all). For example: 0/1, all/1, all/all, 1/all (without spaces).

all

Return the status of all components.

blade

Return the UUID, current status, CPU and memory usage, uptime, encryption status, and drive status/wear for one or all blades. For example, when run on Tinman:

YBCLI(8911) (PRIMARY - yb100-mgr0)> blade status 1/3

Chassis:  1
-----------
Blade Bay:  3 -> BOOTED  UUID: 00000000-0000-0000-0000-38B8EBD006F4 - Version: YBOS-2.0.4-DEBUG   
		 BIOS: v05.04.21.0038.00.011 - Memory total/free: 65587652/1870728 KiB - IB-FW: 2.36.5000
		 CPU: Intel(R) Xeon(R) CPU E5-2618L v4 @ 2.20GHz - Cores: 10 - Load: 1%
		 Address: 192.168.20.12 - Uptime: 0 day(s), 01:59:29 - Worker: Running
		 Encryption Supported: YES - Encryption Enabled: NO - locked: N/A
               SSD: 4: S3EWNWAJ312492R    5: S3EWNWAJ330205H    6: S3EWNWAJ312493K    7: S3EWNWAJ330206Z
                       OK/0% 2B6QCXP7        OK/0% 2B6QCXP7        OK/0% 2B6QCXP7        OK/0% 2B6QCXP7
                    0: S3EWNWAJ311166N    1: S3EWNWAJ330207R    2: S3EWNWAJ311169V    3: S3EWNWAJ330208K
                       OK/0% 2B6QCXP7        OK/0% 2B6QCXP7        OK/0% 2B6QCXP7        OK/0% 2B6QCXP7     
		 Cluster status: OPERATIONAL - Cluster role: MEMBER - Last seen: just now

For example, when run on Andromeda:

YBCLI(416590) (PRIMARY - y2b21-mgr1)> blade status 0/1

Chassis:  0
-----------
Blade Bay:  1 -> YBOS READY UUID: 00000000-0000-0000-0000-38B8EBD20E88 - Version: YBOS-3.0.0-20200917181022-DEBUG
		 BIOS: Athn_1.01.3 - Memory total/free: 1056744476/18735500 KiB
		 BMC: 00.17.01 - Kalidah-1: 0x0DE38309 - Kalidah-2: 0x0DE38309 - IB-FW: 16.28.1002
		 CPU: AMD EPYC 7702P 64-Core Processor - Microcode: 0x8301034 - Cores: 64 - Load: 1%
		 Address: 192.168.10.10 - Uptime: 0 day(s), 00:15:14 - Worker: Running
		 Encryption Supported: YES - Encryption Enabled: NO - locked: N/A
               SSD: 4: S439NE0MA00440     5: S439NE0MA00287     6: S439NE0MA00271     7: S439NE0MA00284
                       OK/0% EDA5502Q        OK/0% EDA5502Q        OK/0% EDA5502Q        OK/0% EDA5502Q
                    0: S439NE0MA00442     1: S439NE0MA00253     2: S439NE0MA00264     3: S439NE0MA00288
                       OK/0% EDA5502Q        OK/0% EDA5502Q        OK/0% EDA5502Q        OK/0% EDA5502Q    
		 Cluster status: OPERATIONAL - Cluster role: MEMBER - Last seen: just now

Note: If the amount of memory installed on the blades varies (based on the amount reported for the first blade), you will see red text for the memory information and a warning message at the end of the output. You will also see a warning if the BIOS is being flashed on one or more blades. These blades will automatically reset when BIOS flashing is complete.

cmp

Return the status of the chassis management processors (CMPs) and InfiniBand switches on the manager nodes. The output includes link status for all of the InfiniBand ports. For example:

YBCLI (PRIMARY)> status cmp 1/1

Chassis:  1
-----------
CMP1 version: 2.53 Role: PRIMARY
Blade link status
Port 1 -> UP - Link: FDR,x4
Port 2 -> UP - Link: FDR,x4
Port 3 -> UP - Link: FDR,x4
Port 4 -> UP - Link: FDR,x4
Port 5 -> UP - Link: FDR,x4
Port 6 -> UP - Link: FDR,x4
Port 7 -> UP - Link: FDR,x4
Port 8 -> UP - Link: FDR,x4
Port 9 -> UP - Link: FDR,x4
Port10 -> UP - Link: FDR,x4
Port11 -> UP - Link: FDR,x4
Port12 -> BLADE NOT INSTALLED
Port13 -> BLADE NOT INSTALLED
Port14 -> BLADE NOT INSTALLED
Port15 -> BLADE NOT INSTALLED

External link status
Ext port 1 -> UP - Link: FDR,x4
Ext port 2 -> UP - Link: FDR,x4
Ext port 3 -> UP - Link: FDR,x4
Ext port 4 -> UP - Link: FDR,x4
Ext port 5 -> UP - Link: FDR,x4
Ext port 6 -> UP - Link: FDR,x4
Ext port 7 -> UP - Link: FDR,x4
Ext port 8 -> UP - Link: FDR,x4
database

Return the status of the database software stack, including uptime. For example:

YBCLI (PRIMARY)> status database

Database system running        : YES
Database system ready          : YES
Database system read-only      : NO
Database system uptime         : 02:32:49
Database system users connected: 4 (including system users)
manager

Return uptime and CPU and memory usage on one or both manager nodes. For example:

YBCLI (PRIMARY)> status manager all

Host         : yb1000-mgr0.ybd.io
Uptime       : 15 days, 05:55:48
Users online : 2
CPU usage    : 3.1 %
Memory used  : 10G GiB
Memory free  : 229G GiB

Remote manager node
-------------------

Host         : yb1000-mgr1.ybd.io
Uptime       : 15 days, 05:56:52
Users online : 0
CPU usage    : 0.0 %
Memory used  : 2.6G GiB
Memory free  : 246G GiB
storage

Return free and used storage space on the manager node file systems, including the database row store, and storage quotas on the primary manager node. For example:

YBCLI(912) (PRIMARY - yb00-mgr1)> status storage

OS filesystem       : 112G free -  39G used
HA filesystem       : 847G free - 941G used
Rowstore filesystem : 457G free -  21G used
Spool filesystem    : 954G free -  33M used

Storage quotas: 
        Catalog rowstore   : 2.2G of 200G used
        Cluster manager    : 146.1M of 330G used

This command returns two entries for storage quotas:

  • Catalog rowstore: Amount of storage space being used for the database system catalog.
  • Cluster manager: Amount of storage space being used by the compiler.
system

Return the overall status of the system, indicating the status of the manager nodes and whether the database is running. For example, when run on Tinman:

YBCLI(30354) (PRIMARY - yb98-mgr0)> status system

Manager nodes configured: 2
---------------------------
Node 1 (PRIMARY - LOCAL NODE ) : yb98-mgr0 -> ONLINE
Node 2 (SECONDARY - REMOTE NODE ) : yb98-mgr1 -> ONLINE

HW Platform                        : Tinman
Database system running            : YES
Database system ready              : YES (Responding: YES)
Database system read-only          : NO
Database system catalog rowstore   : NORMAL
Database system rowstore           : NORMAL
Database system storage used       : 20%
Database system uptime             : 14:59:42
System work status                 : gc:idle  parityrebuild:idle  analyzer:idle  system:idle  user:active,idle 
Data collection running            : YES
Blade parity                       : Enabled
Blade parity rebuilding            : NO (Progress: N/A)
Blade data check in-progress       : NO
Shard rewriting                    : NO (0 shards pending)
Capacity expansion in-progress     : YES (5 Tables and 1752898 MBs remaining) 
Cluster degraded mode              : YES (Reason: Drive(s) failed)
Maintenance mode                   : NO
Software update in-progress        : NO (Version: 4.1.1-24805)
Floating system IP                 : 10.10.102.10 - 255.255.255.0
System registered                  : NO
LDAP status                        : Not configured
Logging status                     : Enabled
Encryption keystore                : Available - Status: Not setup
Chassis configuration              : Found: 1 - Configured: 1
Add-ons                            : None

For example, when run on Andromeda:

YBCLI(51453) (PRIMARY - y2b23-mgr0)> system status
 
Manager nodes configured: 2
---------------------------
Node 1 (PRIMARY   - LOCAL NODE  ) : y2b23-mgr0.slc.yellowbrick.io -> ONLINE
Node 2 (SECONDARY - REMOTE NODE ) : y2b23-mgr1.slc.yellowbrick.io -> ONLINE

HW Platform                        : Andromeda
Database system running            : YES (9/9/9 active/powered/installed blades)
Database system ready              : YES (Responding: YES)
Database system read-only          : NO
Database system catalog rowstore   : NORMAL
Database system rowstore           : NORMAL
Database system storage used       : 20%
Database system uptime             : 00:36:20
System work status                 : gc:idle  parityrebuild:idle  analyzer:idle  system:idle  user:idle 
Data collection running            : YES
Blade parity                       : Enabled
Blade parity rebuilding            : NO (Progress: N/A)
Blade data check in-progress       : NO
Shard rewriting                    : NO (0 shards pending)
Capacity expansion in-progress     : YES (3 Tables and 764036 MBs remaining)
Cluster degraded mode              : NO
Maintenance mode                   : NO
Software update in-progress        : NO (Version: 5.1.0-33380) 
Floating system IP                 : 10.10.223.10 - 255.255.255.0
System registered                  : YES (Tenant: yb - System: y2b23)
LDAP status                        : Not configured
Logging status                     : Enabled
Encryption keystore                : Available - Status: READY - Locked: YES
Chassis configuration              : Found: 1 - Configured: 1
System FRU configuration           : All components match records
Add-ons                            : None

Note: In the Database system running line, the active/powered/installed blades text will be yellow if not all installed blades are active or online.

Attention: The statistics under Capacity expansion in-progress only update once a table has been completely moved. Therefore, it may appear at times as though no progress is being made.