Demo – made-up data. Northline, the sites and the numbers are invented. Notices 3.5 – work in progress
VANTAGENorthline
Collected✕7 sites need attention

SASE

FortiSASE dial-up tunnels as each FortiGate shows them · built Sun Nov 22 2026 04:16 PM
17 FortiSASE tunnels17 up

What each FortiGate sees for FortiSASE dial-up IPsec — tunnel name, status when known, and non-secret peer fields. Shown as the firewall reports it; Vantage does not talk to FortiSASE.

What is listed
From already-collected show vpn ipsec phase1-interface (type dynamic, name containing fortisase or sase) and get vpn ipsec tunnel summary for up/down when present. Peer and gateway fields that are secrets are never shown. No new allow-list command on day one. Caption: as the firewall shows it. Related: WAN, VPN access and Post-quantum. FortiSASE tunnels stay out of the post-quantum crypto rows.
Atlanta1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Azure East1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Azure West1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Boston1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Charlotte1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Charlotte OTnone listed

No dial-up tunnel whose name contains fortisase or sase on this FortiGate.

Chicago1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Dallas1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Denver1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Detroit1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Detroit OTnone listed

No dial-up tunnel whose name contains fortisase or sase on this FortiGate.

Houston1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Houston OTnone listed

No dial-up tunnel whose name contains fortisase or sase on this FortiGate.

Los Angeles1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Miami1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Minneapolis1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
New York1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Philadelphia1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Phoenix1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)
Seattle1 tunnel
TunnelStatusInterfaceIKETypePeer / gateway
FortiSASEupwan1IKEv2dynamicdial-up (no remote-gw)

Backups

philadelphia: no backup for 2 days – the FortiGate did not answer (site unreachable). See Change → Backups.