Recovering lost VSatellites
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure AWS connection
- Configure Azure Key Vault connection
-
- Workload Identity Federation authentication
- Workload Identity Federation - Azure Identity Provider authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Workload Identity Federation authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Supported OIDC claims
-
-
-
-
- Create an F5 BIG-IP LTM machine
- Create a Microsoft Azure Private Key Vault machine
- Create a Microsoft IIS machine
- Create a Microsoft Windows (PowerShell) machine
- Create a Microsoft SQL Server machine
- Create a Common KeyStore machine
- Create a Citrix ADC machine
- Create an Imperva WAF machine
- Create a VMware NSX Advanced Load Balancer (AVI) machine
- Create an A10 Thunder ADC machine
- Create a Cloudflare machine
- Create Kemp Virtual LoadMaster machine
- Create a Palo Alto Panorama machine
-
- Provision to an F5 BIG-IP LTM
- Provision to a Microsoft Azure Private Key Vault
- Provision to Microsoft IIS
- Provision to Microsoft Windows (PowerShell)
- Provision to Microsoft SQL Server
- Provision to a Common KeyStore
- Provision to a Citrix ADC
- Provision to an Imperva WAF
- Provision to VMware NSX Advanced Load Balancer (AVI)
- Provision to an A10 Thunder ADC
- Provision to Cloudflare
- Provision to a Kemp Virtual LoadMaster
- Provision to Palo Alto Panorama
-
-
- 47-Day Validity Readiness TLS Certificates dashboard
- About the Certificate Inventory
- Managing certificate lifecycle settings
- Reissuing certificates in Next-Gen Trust Security
- Downloading certificates, certificate chains, and keystores
- Retiring, recovering, and deleting certificates
- Finding certificates in the certificate inventory
- Importing certificates from a CA using EJBCA
- Notification Center overview
- Domain-based validation for external emails
- Managing user accounts
- Troubleshooting
Recovering lost VSatellites
Use this procedure to recover a disconnected VSatellite that appears in a Lost Connection state on the VSatellites page. You can use the Recovery wizard to restore a single node or perform a full disaster recovery if all VSatellites are lost.
Warning (Not supported for HSM-protected DEK):The Recovery wizard and vsatctl recover are not supported for VSatellites deployed with HSM-protected DEK.
The procedures in this topic apply only to VSatellites using software-based DEK protection.
Warning: If all VSatellites are deleted, recovery will fail. A backup DEK cannot be used unless at least one VSatellite remains in the system.
The Recovery wizard supports both scenarios:
- Disaster recovery – When all of your VSatellites are unreachable, you’ll need to manually supply a previously exported DEK file and passphrase.
- Node reinstallation – When one or more VSatellites are lost but at least one is still active, you only need to supply a recovery code. The DEK is handled automatically.
Prerequisite
Before starting the recovery process, ensure that you have:
- The vsatctl CLI must be available on the host performing the recovery and make sure you are running the latest version.
- The passphrase for the DEK used in your environment; this is the passphrase you used when exporting the DEK.
- The recovery code provided by the wizard (included when you copy the command).
- For disaster recovery only: a previously exported DEK file; this is the backup copy of your DEK. Learn more
To recover a disconnected VSatellite
- Sign in to Next-Gen Trust Security.
- Click Configuration > VSatellites.
- Locate a VSatellite with status Lost Connection.
- Click Recover.
- This button appears only on disconnected nodes.
- In a disaster recovery scenario (all nodes disconnected), the Recover button appears on all nodes.
- In a node reinstallation scenario, it appears only on the affected node.
- In Step 1 – Download:
- (Optional) Click the system requirements link to review prerequisites.
- Click Copy to copy the vsat download command and run it in your terminal.
- Click Continue.
- ONLY if you are doing disaster recovery:Issue the following command:sudo ./vsatctl uninstall --forceIn Step 2 – Preflight:
- Review the system requirements again if needed.
- Click Copy to copy the preflight check command and run it in your terminal.
- Verify the output is successful.
- Click Continue.
In Step 3 – Recover:- Click Copy to copy the vsatctl recover command, paste it into your terminal, and then edit the following, depending on your situation:
- If this is a disaster recovery, specify the path to your DEK file (--dek /path/to/dek.pem), and enter the DEK passphrase.
- If this is a node reinstallation, you do not need to specify the DEK file.
- In both cases:
- The recovery code should be included in the command you copied from the wizard.Example:
chmod +xx ./vsatctl && sudo ./vsatctl recover\ --dek /backup/dek115.pem \ --passphrase P23x225zw \ --recovery-code d8923dc2-0a89-8765-b416-8c9693847122After the command completes, click Test to verify that the VSatellite is online.If the test fails, ensure the recovery command completed successfully, then rerun the test.Click Done to close the wizard.The restored VSatellite should now appear in Active state on the Next-Gen Trust Security dashboard and resume communication with the control plane.No additional configuration is required. The recovered VSatellite replaces the original one in the system, and all settings or services that were using the old node will continue to work with the recovered node automatically.