Viewing the VM Status with the CLI
- For Linux, log into the VM as
root. For Windows, log in as a System Administrator and open a Command Prompt or start Windows PowerShell. -
Run the
hcl statuscommand.
Example
# hcl status Summary -------------------------------------------------------------------------------- KeyControl: 192.168.200.175:443 KeyControl list: 192.168.200.175:443 Status: Connected Last heartbeat: Fri Jul 27 11:31:57 2018 (pass) AES_NI: enabled Certificate Expiration: Sep 11 22:16:13 2020 GMT HTCRYPT: Not Installed Registered Devices -------------------------------------------------------------------------------- Disk Name Cipher Status Clear -------------------------------------------------------------------------------- sde1 AES-XTS-512 Detached (RK 10.25%) /dev/mapper/clear_sde1 '--> auto_attach=ENABLED, attach_handler=DEFAULT, detach_handler=DEFAULT sda3 AES-XTS-512 Attached /dev/mapper/clear_3463E620-D268-4377-8020-36C53513C8FD (swap) '--> auto_attach=ENABLED, attach_handler=DEFAULT, detach_handler=DEFAULT sdc2 AES-XTS-512 Attached /dev/mapper/clear_44B72469-EDEE-4061-BDF8-E05A12DB5063 (/data) '--> auto_attach=ENABLED, attach_handler=DEFAULT, detach_handler=DEFAULT Available Devices -------------------------------------------------------------------------------- Disk Name Device Node Size (in MB) -------------------------------------------------------------------------------- sde7 /dev/sde7 580 sde6 /dev/sde6 203 sde5 /dev/sde5 125 sdc1 /dev/sdc1 118 sdb /dev/sdb 256 vg--sdd-d1g1ts /dev/dm-0 252 vg--sdd-long /dev/dm-1 252 Other Devices -------------------------------------------------------------------------------- Disk Name Device Node Status -------------------------------------------------------------------------------- sda2 /dev/sda2 Mounted (/) sda1 /dev/sda1 Mounted (/boot) sdd /dev/sdd LVM (vg-sdd)
The VM status can be one of the following:
- Not registered — The Policy Agent software is installed but the VM has not yet been registered with KeyControl.
- Connected — The VM can communicate with KeyControl and everything is running normally.
- Could not connect — KeyControl is not reachable. If this condition continues, the VM will need to be re-authenticated with KeyControl when communication is re-established.
- Need to update certificate — The certificate for the is VM is no longer valid and should be updated.
- Reauth needed — The VM needs to be re-authenticated.
- Virtual Machine not authenticated — VM permissions have been revoked from KeyControl. To fix this issue, see Reactivating a Revoked Disk.
- Identity verification failed — Permissions are not available because the VM heartbeat has timed out or its IP address or hardware signature has changed. This can occur if you have changed the IP address on a VM or copied the VM to a new server.
- Unknown error from KeyControl cluster — An unknown error has occurred. Please contact HyTrust support if you see this message.
