blade

Run operations on the compute blades.
blade add [ <chassis>/<bay> | <uuid> [ [ <chassisN>/<bayN> | <uuidN> ] ]
blade beacon [ <chassis>/<bay> ] [ on | off ]
blade disable [ <chassis>/<bay> | <uuid> ]
blade enable [ <chassis>/<bay> | <uuid> ]
blade erase [ <chassis>/<bay> | <uuid> ]
blade erase clear [ <chassis>/<bay> | <uuid> ]
blade health [ <chassis>/<bay> | all ]
blade poweroff [ <chassis>/<bay> | all ]
blade poweron [ <chassis>/<bay> | all ]
blade reboot [ <chassis>/<bay> | all ]
blade reset  [ <chassis>/<bay> | all ]
blade status [ <chassis>/<bay> | all ]
Note: Specify a chassis number (or all) and a bay number (or all). For example: 2/1, all/1, all/all, 1/all (without spaces). For some commands, you can enter all instead of a chassis/bay combination. For example:
blade health all
add
Expand the capacity of the cluster by adding one or more compute blades. Specify each blade by its bay number or its UUID. In general, the cluster must be online and in a healthy operational state when you run this command. Be sure to add blades that are already physically installed in the chassis and fully powered on. If you specify a list of blades to add and one or more of them does not exist or is not powered on, the command will fail for all of the blades. You can run the status blade all command to see the current state of the system before running the blade add command.
beacon
Turn the beacon LED on or off either for all blades or for a specific blade (identified by its bay number). Use this command to make the blue beacon LED flash on a blade that needs to be swapped out.
disable
Disable a blade so it no longer participates in the system as a worker node. Specify the bay number or the UUID of the blade.
YBCLI (PRIMARY)> blade disable 0/10

Are you sure you want to disable blade with UUID: 00000000-0000-0000-0000-38B8EBD00C35

Type yes to continue: yes

Should the blade be powered off after being disabled?

Type yes to power off blade after disable: no
Blade will not be powered off.
Blade 00000000-0000-0000-0000-38B8EBD00C35 has been disabled.
It takes about 30 seconds to change the blade state to disabled.
To see which blades are currently disabled, use the blade status all command.
enable
Enable a blade that is currently not in use (make it a worker node). Specify the bay number or the UUID of the blade.
YBCLI (PRIMARY)> blade enable 0/10

Blade 00000000-0000-0000-0000-38B8EBD003DE has been enabled
It can take 30s before the blade state changes to enabled

If the blade is already provisioned for use, you will see the following message:

Blade 00000000-0000-0000-0000-38B8EBD003DE has already been enabled
erase
Erase all data from a single specified blade. Specify the bay number or the UUID of the blade. When you run the blade erase command, you see a series of warnings and prompts for your protection. Type yes at each prompt to continue.
YBCLI(37002) (PRIMARY - yb98-mgr0)> blade erase 1/1
 
Erasing a blade will destroy all data on the blade. The data will not be recoverable
This command will perform a SECURE erase of all drives on the blade
Continue (yes/no)? yes
 
All data on this blade will now be deleted
Please verify again that you want to complete this operation.
Continue (yes/no)? yes
 
Should the blade be powered off after being erased?
Response (yes/no): yes
Powering blade off after being erased
 
Starting to erase blade in chassis: 1 bay: 1
Erasing blade in chassis: 1 bay:  1 -> 
       Using Yellowbrick Secure Erase Utility v4.0.0-1168-release
       Retrieving drive details. Standby... Done
       DRIVE-0 - Serial: S3EWNX0JC12534E -> 3 pass erase starting [2019-09-19 13:54:57 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-0 - Serial: S3EWNX0JC12534E -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:54:57 host:yb98-mgr1]
       DRIVE-1 - Serial: S3EWNX0K200853L -> 3 pass erase starting [2019-09-19 13:54:57 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-1 - Serial: S3EWNX0K200853L -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:54:58 host:yb98-mgr1]
       DRIVE-2 - Serial: S3EWNX0K202426R -> 3 pass erase starting [2019-09-19 13:54:58 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-2 - Serial: S3EWNX0K202426R -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:54:59 host:yb98-mgr1]
       DRIVE-3 - Serial: S3EWNX0K200684P -> 3 pass erase starting [2019-09-19 13:54:59 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-3 - Serial: S3EWNX0K200684P -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:54:59 host:yb98-mgr1]
       DRIVE-4 - Serial: S3EWNX0JC12542B -> 3 pass erase starting [2019-09-19 13:54:59 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-4 - Serial: S3EWNX0JC12542B -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:55:00 host:yb98-mgr1]
       DRIVE-5 - Serial: S3EWNX0K100445J -> 3 pass erase starting [2019-09-19 13:55:00 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-5 - Serial: S3EWNX0K100445J -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:55:00 host:yb98-mgr1]
       DRIVE-6 - Serial: S3EWNX0K100372P -> 3 pass erase starting [2019-09-19 13:55:00 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-6 - Serial: S3EWNX0K100372P -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:55:01 host:yb98-mgr1]
       DRIVE-7 - Serial: S3EWNX0JC12602K -> 3 pass erase starting [2019-09-19 13:55:01 host:yb98-mgr1]
              Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
              DRIVE-7 - Serial: S3EWNX0JC12602K -> ALL 3 ERASE PASSES SUCCEEDED [2019-09-19 13:55:02 host:yb98-mgr1]
       All 8 drives on blade in chassis: 1 bay:  1 successfully erased with 3 passes of NIST 800-88 PURGE and CLEAR [2019-09-19 13:55:02 host:yb98-mgr1]
Blade has been erased
Powering off blade. Standby...
Blade(s) in chassis: 1 were instructed to power off
Waiting for blade(s) to power off
Blades powered off: 0/1
Blades powered off: 1/1
Blade will have to be reset to participate in the cluster.

The blade erase command cannot be run on the secondary manager node.

If you need to erase data from the whole system, you can use the system factory command.

erase clear
Erase all data from a single specified blade through the block-by-block writing of zeroes in addition to the standard secure erase process of blade erase. Specify the bay number or the UUID of the blade.

Note that the blade erase clear command must be run in a screen or tmux session because the process takes longer to complete than the blade erase command. Additionally, the blade erase clear command cannot be run on the secondary manager node. When you run the blade erase clear command, you see a series of warnings and prompts for your protection. Type yes at each prompt to continue.

If you need to erase data from the entire system, you can use the system factory command.

YBCLI(64318) (PRIMARY - yb98-mgr0)> blade erase clear 0/1                                                                                                                                         
                                                                                                                                                                                                  
Execution Start: Thu Dec  5 14:30:14 PST 2019                                                                                                                                                     
Erasing a blade will destroy all data on the blade. The data will not be recoverable                                                                                                              
Clear erase will destroy all data on the blade by writing zeros to all bytes on the drive       
This command will perform a SECURE erase of all drives on the blade                                                                                                                               
Continue (yes/no)? yes                                                                                                                                                                            
                                                                                                                                                                                                  
All data on this blade will now be deleted                                                                                                                                                        
Please verify again that you want to complete this operation.                                                                                                                                     
Continue (yes/no)? yes                                                                                                                                                                            
                                                                                                                                                                                                  
Should the blade be powered off after being erased?                                                                                                                                               
Response (yes/no): yes                                                                                                                                                                            
Powering blade off after being erased                                                                                                                                                             
                                                                                                 
                                                                                                                                                                                                  
Starting to erase blade in chassis: 0 bay: 1                                                                                                                                                      
Erasing blade in chassis: 0 bay:  1 ->  Using Yellowbrick Secure Erase Utility v3.3.0-20502-release
        Retrieving drive details. Standby... Done                                                                                                                                                 
        Affected Inventory of Disks found on the Yellowbrick Appliance host:yb98-mgr0:                                                                                                            
        Chassis 0 bay: 1                                                                                                                                                                          
        DRIVE-0 - Serial: S469NF0K510756B                                                                                                                                                         
        DRIVE-1 - Serial: S469NF0K510762E                                                                                                                                                         
        DRIVE-2 - Serial: S469NF0K501083Z                                                                                                                                                         
        DRIVE-3 - Serial: S469NF0K501067B                                                                                                                                                         
        DRIVE-4 - Serial: S469NF0K501097L                                                        
        DRIVE-5 - Serial: S469NF0K510767N                                                                                                                                                         
        DRIVE-6 - Serial: S469NF0K510759X                                                                                                                                                         
        DRIVE-7 - Serial: S469NF0K501064H                                                                                                                                                         
                                                                                                                                                                                                  
        Clear erasing drives, it may take an extended amount of time. Erasing...                                                                                                                  
        DRIVE-0, Chassis 0, Bay 1 - Serial: S469NF0K510756B -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]                                                                         
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR                                                            
                  512110190592 bytes written to Drive 0 (Clear) completed at 2019-12-05 14:49:34                                                                                                  
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:49:34                                                 
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 0 (Clear) completed at 2019-12-05 15:11:51 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:11:51
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 0 (Clear) completed at 2019-12-05 15:30:07 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:30:07
                DRIVE-0 - Serial: S469NF0K510756B -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-1, Chassis 0, Bay 1 - Serial: S469NF0K510762E -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 1 (Clear) completed at 2019-12-05 14:48:15
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:48:15
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 1 (Clear) completed at 2019-12-05 15:07:40 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:07:40
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 1 (Clear) completed at 2019-12-05 15:29:07 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:29:07
                DRIVE-1 - Serial: S469NF0K510762E -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-2, Chassis 0, Bay 1 - Serial: S469NF0K501083Z -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 2 (Clear) completed at 2019-12-05 14:47:57
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:47:57
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 2 (Clear) completed at 2019-12-05 15:07:56 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:07:56
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 2 (Clear) completed at 2019-12-05 15:30:26 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:30:26
                DRIVE-2 - Serial: S469NF0K501083Z -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-3, Chassis 0, Bay 1 - Serial: S469NF0K501067B -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 3 (Clear) completed at 2019-12-05 14:55:40
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:55:40
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 3 (Clear) completed at 2019-12-05 15:17:39 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:17:39
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 3 (Clear) completed at 2019-12-05 15:32:05 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:32:05
                DRIVE-3 - Serial: S469NF0K501067B -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-4, Chassis 0, Bay 1 - Serial: S469NF0K501097L -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 4 (Clear) completed at 2019-12-05 14:47:54
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:47:54
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 4 (Clear) completed at 2019-12-05 15:08:15 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:08:15
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 4 (Clear) completed at 2019-12-05 15:28:43 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:28:43
                DRIVE-4 - Serial: S469NF0K501097L -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-5, Chassis 0, Bay 1 - Serial: S469NF0K510767N -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 5 (Clear) completed at 2019-12-05 14:53:11
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:53:11
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 5 (Clear) completed at 2019-12-05 15:17:58 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:17:58
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 5 (Clear) completed at 2019-12-05 15:32:38 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:32:38
                DRIVE-5 - Serial: S469NF0K510767N -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-6, Chassis 0, Bay 1 - Serial: S469NF0K510759X -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 6 (Clear) completed at 2019-12-05 14:48:43
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:48:43
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 6 (Clear) completed at 2019-12-05 15:07:40 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:07:40
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 6 (Clear) completed at 2019-12-05 15:28:51 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:28:51
                DRIVE-6 - Serial: S469NF0K510759X -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        DRIVE-7, Chassis 0, Bay 1 - Serial: S469NF0K501064H -> 3 pass erase starting [2019-12-05 14:30:27 host:yb98-mgr0]
                Pass 1 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  512110190592 bytes written to Drive 7 (Clear) completed at 2019-12-05 14:48:05
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 14:48:05
                Pass 2 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1024220381184 bytes written to Drive 7 (Clear) completed at 2019-12-05 15:07:48 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:07:48
                Pass 3 of 3 -> DRIVE ERASED SUCCESSFULLY using method: NIST 800-88 PURGE and CLEAR
                  1536330571776 bytes written to Drive 7 (Clear) completed at 2019-12-05 15:28:51 
                  Cryptographic Key Delete and Disk Erase (Purge) completed at 2019-12-05 15:28:51
                DRIVE-7 - Serial: S469NF0K501064H -> ALL 3 ERASE PASSES SUCCEEDED [2019-12-05 15:32:38 host:yb98-mgr0]
        All 8 drives on blade in chassis: 0 bay:  1 successfully erased with 3 passes of Secure erase + format [2019-12-05 15:32:38 host:yb98-mgr0]

Summary of Yellowbrick Secure Erase Utility 2019-12-05 14:30:27
8 Drives Erased Successfully with NIST 800-88 PURGE and CLEAR
0 Drives Erased Failed
Blade has been erased
Powering off blade. Standby...
Blade(s) in chassis: 0 were instructed to power off
Waiting for blade(s) to power off
Blades powered off: 0 of 1
Blades powered off: 1 of 1
Blade will have to be reset to participate in the cluster.
health
Check the hardware health and boot status of one or all blades. For example:
YBCLI (PRIMARY)> blade health 0/10

Chassis:  0
-----------
Bay: 10 HW Status: ok    Power: on LED: [ OFF  ON   OFF  ] FRU: C4-0013-00 R01 Serial: TAA18040900C35 Temp: 49C CPU: Booted (YBOS) Worker: Running

Retrieving blade alerts...

Blade alerts reported: None
Note: The health blade command provides the same information.
If a blade is powered off, it returns:
YBCLI (PRIMARY)> blade health 0/15

Bay: 15 Status: off
poweroff, poweron
Power on or power off one blade or all blades. For example, power off blade 15:
YBCLI (PRIMARY)> blade poweroff 15

Blade in bay 15 was instructed to power off
Waiting for blade(s) to power off
Blades powered off: 0/1
Blades powered off: 1/1
When a blade is powered on, it passes through three states to come online:
  • CPU: Powering up/Self-test
  • CPU: Booting YBOS
  • CPU: Booted (YBOS)
The blade health command reports these states. This process may take a few minutes. An attempt to reboot a blade before it is in the Booted (YBOS) state will fail. For example:
YBCLI (PRIMARY)> blade poweron 15

Blade in bay 15 instructed to power on
Waiting for blade(s) to power on
Blades powered on: 0/1
Blades powered on: 1/1

YBCLI (PRIMARY)> blade health 15

Bay: 15 Status: ok Power: on FRU: C4-0005-00     Serial: NOT READ YET   CPU: Powering up/Self-test
reboot
Reboot one blade or all blades. This operation is a graceful reboot; the Yellowbrick software stack is shut down first.
YBCLI (PRIMARY)> blade reboot all

Gracefully rebooting blade in bay:  1 -> OK
Gracefully rebooting blade in bay:  2 -> OK
Gracefully rebooting blade in bay:  3 -> OK
Gracefully rebooting blade in bay:  4 -> OK
Gracefully rebooting blade in bay:  5 -> OK
...
reset
Perform an immediate hardware reset on one blade or all blades.
YBCLI (PRIMARY)> blade reset 15

Blade in bay 15 was reset
status
Return the UUID, current status, CPU and memory usage, uptime, encryption status, and drive status/wear for one or all blades. For example:
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
		 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 status/wear: 0: S3EWNWAJ311166N  OK/0%       1: S3EWNWAJ330207R  OK/0%       
		                  2: S3EWNWAJ311169V  OK/0%       3: S3EWNWAJ330208K  OK/0%       
		                  4: S3EWNWAJ312492R  OK/0%       5: S3EWNWAJ330205H  OK/0%       
		                  6: S3EWNWAJ312493K  OK/0%       7: S3EWNWAJ330206Z  OK/0%       
		 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.

The status blade command provides the same information.

If the database is not running, the output does not include cluster status information.

This example shows the status of one bay that does not have a blade installed:
YBCLI (PRIMARY)> blade status 1/14

Chassis:  1
-----------
Blade Bay: 14 -> BLADE NOT INSTALLED