Monitoring Your Deployed VSatellites
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure Akamai Connection
- 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
-
-
-
- Working with the Built-in CA
- Add AWS Public CA
- Add AWS Private CA
- Add DigiCert One Certificate Authority
- Add Entrust
- Add GlobalSign Atlas
- Add GlobalSign MSSL
- Add GoDaddy
- Add Google Cloud Private CA
- Add a HID PKIaaS CA
- Add Certificate Manager - Self-Hosted
- Set Up an OpenSSL Certificate Authority Connector
- Create a Sectigo Certificate Manager Certificate Authority
- Add Zero Touch PKI
- Set Up Certificate Expiration Notifications
- Using a Custom DNS Provider
-
-
-
-
- Create an F5 BIG-IP LTM Machine
- Create a Microsoft Azure Private Key Vault Machine
- Create a Microsoft Azure Application Registration 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
- Create a Radware Alteon 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
- Provision Certificates to Radware Alteon
-
-
- 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
- Domain-Based Validation for External Emails
-
- Create a Workload Identity Management or Discovery Agent Built-in Account
- Create an OCI Registry Built-in Account
- Create a Certificate Manager - Self-Hosted Built-in Account
- Create a Scanafi Built-in Account
- Toggling a Built-in Account on or Off
- Editing Built-in Accounts
- Deleting Existing Built-in Accounts
- Renew Existing Built-in Accounts
- Troubleshooting
Monitoring Your Deployed VSatellites
Use the VSatellite's page to monitor your deployed VSatellites. From the Drawer view, you can do the following:
- view a VSatellite's current status
- verify the last time a VSatellite checked in to Next-Gen Trust Security
- view each VSatellite's list of currently supported services
To Monitor a VSatellite
- Sign in to Next-Gen Trust Security.
- Click Configuration > VSatellites.
- Select the VSatellite you want to monitor.You can view the status of a VSatellite by looking in the Status column of the VSatellites List view or at the top of the slideout drawer under the VSatellite's name.
- (Optional) Scroll to the Supported Services table to view the list of services assigned to the selected VSatellite.To view the details of a specific service, click a service's name.
Unhealthy Status in HSM-Protected DEK Deployments
If your tenant is configured to use HSM-protected DEK, a VSatellite may enter an Unhealthy state due to issues related to HSM access or configuration.
Common causes include:
- The HSM is unreachable from the VSatellite host.
- Incorrect HSM-related configuration values were provided during installation (for example, an incorrect PIN, client path, library path, or configuration file).
- The DEK is missing or was deleted from the HSM partition.
- The VSatellite was installed using a different HSM or partition than other VSatellites.
In some cases, the VSatellite may automatically return to a healthy state after HSM connectivity or configuration issues are resolved.
Note: HSM-related configuration values are not fully validated during installation. A VSatellite can deploy successfully and still enter an Unhealthy state if issues are detected later.
For details about HSM requirements, limitations, and lifecycle behavior, see Using HSM-protected DEK with VSatellites.
What's Next?
Get help troubleshooting your VSatellites.