SD-WAN

Hi all, I'm working on a design challenge involving Starlink and Juniper SSR (Mist‑managed), and I'd appreciate insights from anyone who has dealt with real‑time traffic over LEO networks.

 The environment

• Multiple Starlink terminals (3–4) used for path diversity

• Real‑time traffic requirements (telemetry / control / VoIP / low‑latency data)

• Starlink loss patterns:

  • 10–20% bursty loss

  • 100–300 ms micro‑outages

  • Significant jitter

  • Loss events often correlated across terminals during satellite handovers

The goal

Maintain real‑time data integrity across unstable LEO links.

The challenge

On Juniper SSR, the usual way to protect real‑time traffic over unstable links is packet duplication  However:

• Mist‑managed SSR does not support packet duplication

• Mist does not expose the SSR configuration tree

• SSH access only provides operational mode, not config mode

• Mist overwrites any local config changes

• Mist also does not support FEC

So the usual SSR redundancy mechanisms are unavailable.

Has anyone been able to get around this problem? If you let me know if further information is required to respond this.

Many Thanks in advance

Hi,

All this you can do by enabling "Extra CLI" in Mist. You can open a ticket via the GUI and someone will enable it for your Org.

Then you can enable packet duplication, FEC, etc. by CLI commands.

Best Regards,

Ivan

Hi all, I'm working on a design challenge involving Starlink and Juniper SSR (Mist‑managed), and I'd appreciate insights from anyone who has dealt with real‑time traffic over LEO networks.

 The environment

• Multiple Starlink terminals (3–4) used for path diversity

• Real‑time traffic requirements (telemetry / control / VoIP / low‑latency data)

• Starlink loss patterns:

  • 10–20% bursty loss

  • 100–300 ms micro‑outages

  • Significant jitter

  • Loss events often correlated across terminals during satellite handovers

The goal

Maintain real‑time data integrity across unstable LEO links.

The challenge

On Juniper SSR, the usual way to protect real‑time traffic over unstable links is packet duplication  However:

• Mist‑managed SSR does not support packet duplication

• Mist does not expose the SSR configuration tree

• SSH access only provides operational mode, not config mode

• Mist overwrites any local config changes

• Mist also does not support FEC

So the usual SSR redundancy mechanisms are unavailable.

Has anyone been able to get around this problem? If you let me know if further information is required to respond this.

Many Thanks in advance