Verify the integration using Nutanix command-line tools, NCC health checks, and the CryptoHub key inventory. This page also covers key rotation, troubleshooting, and log file locations.Documentation Index
Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
Use this file to discover all available pages before exploring further.
Verify encryption status with ncli
SSH to any CVM in the cluster and run the following commands to confirm encryption is active and the KMS is configured correctly. Run these commands to check overall encryption status:Verify keys on the CryptoHub
Log in to the CryptoHub management interface and confirm that new AES-256 symmetric key objects have been created. Nutanix creates Key Encryption Keys (KEKs) on the CryptoHub when encryption is first enabled. In the Generic KMIP service on the CryptoHub, check the KMIP activity logs for Create, Get, and Activate operations originating from the Nutanix CVM IP addresses. The key objects appear in the key inventory of the service.Run NCC health checks
Run the full NCC health check suite to validate KMS configuration, connectivity, and certificate validity.key_manager_checks health check (Nutanix KB-8223) specifically validates KMS configuration and certificate status. Address any FAIL results before considering the integration production-ready.
Rotate encryption keys
Nutanix supports both automatic and on-demand key rotation. To manually rotate encryption keys via the CLI, run the following command:Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Node status shows Uploaded but not Verified | CVM cannot reach CryptoHub on port 5696 | Verify firewall rules allow TCP 5696 from all CVM IPs to the CryptoHub |
| Node status remains Uploaded after certificate upload | Certificate was not issued by the uploaded CA | Confirm the signed cert was issued by the same CA whose cacert.pem was uploaded to Prism |
test-configuration fails | KMIP service not running or port blocked | Verify the Generic KMIP service is deployed and running on the CryptoHub; check port 5696 connectivity |
| Keys not visible on CryptoHub after enabling encryption | Wrong KMS address or identity mismatch | Confirm the KMS address in Prism matches the CryptoHub address; review KMIP activity logs |
| Cluster data inaccessible after cold boot | CryptoHub unreachable at boot time | Restore CryptoHub connectivity; verify the CryptoHub is not hosted on the encrypted cluster |
| Certificate test fails with TLS error | TLS inspection proxy intercepting traffic | Exempt CryptoHub IP or FQDN from TLS inspection on all network path devices |
Log files
| Log | Location on CVM | Contents |
|---|---|---|
| Mantle INFO | ~/data/logs/mantle.INFO | Normal KMIP operations and key retrievals |
| Mantle WARNING | ~/data/logs/mantle.WARNING | Warning-level key management events |
| Mantle ERROR | ~/data/logs/mantle.ERROR | Errors in key retrieval or KMIP communication |
genesis status on any CVM to check the status of the encryption service, and cluster status for overall cluster health.
