VSatellite successfully installed but shows as registered instead of active

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

VSatellite successfully installed but shows as registered instead of active

L4 Transporter

I've received successfully installed, there is connectivity to the tenant for the VSAT and in the logs there is no error. During the preflight there were some warnings, but no errors. Still after a time the VSAT appears as registered instead of actvie. Has someone encountered this? Thanks in advanced

2 REPLIES 2

L7 Applicator

Several internal files point to recurring issues that can cause a VSAT to remain in the registered state:

1. Preflight Warnings Indicate Unmet Prerequisites

Even if no errors are thrown, warnings during preflight checks often signal missing or misconfigured elements:

  • Proxy, disk space, or firewall settings not fully aligned
  • Required ports (e.g. 443, 9443) not open or reachable
  • OS compatibility issues or missing updates These are documented as frequent root causes in Tech Training 2025 - VSatellite What's New & Troubleshooting and MIS Portfolio & Strategy Overview. [Tech Train...leshooting], [MIS Portfo...y Overview]

2. Connectivity or Trust Issues

If the VSAT loses connectivity or remains disconnected for too long, it may become untrusted. This can prevent it from transitioning to active status. Instead of uninstalling and reinstalling (which risks breaking automation), use the recovery wizard in Certificate Manager SaaS to re-establish trust. This is covered in ZTPKI and Cert Mgr SaaS - May 2025. [ZTPKI], [Cert Mgr S...- May 2025]

3. Missing DEK or Improper Recovery

If the Data Encryption Key (DEK) isn’t properly backed up or restored, the VSAT may not fully activate. Recovery steps using vsatctl and the DEK are essential in such cases. [Cert Mgr S...- May 2025]

 

✅ Recommended Actions

  1. Review Preflight Logs: Even warnings can block activation. Check for proxy/firewall/disk space issues.
  2. Run Recovery Wizard: Use the Certificate Manager SaaS wizard to re-establish trust without reinstalling.
  3. Verify DEK and API Key: Ensure the DEK is restored correctly using vsatctl if the VSAT was previously lost.
  4. Avoid Reinstalling: Reinstallation may break existing automation and integrations.

 

Hi robert, the issue was that it wasn't open the network connectivity to the default VSAT network CIDR range. After enabling that on the firewall, it was connected.

  • 183 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!