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

WAN & IPsec

Guide: Service desk › 2. What the colours meanEvery site-to-site path, checked from both ends

Same geographic map as Overview (WAN at a Vantage). SASE is in Plano, Texas; each Azure region has an IPsec / cloud VPN to every site. Hover a site for its status and what is wrong; click a site to open it.

Atlanta ↔ SASE: 1 of 1 paths upAzure East ↔ Chicago: 2 of 2 paths upAzure East ↔ SASE: 1 of 1 paths upAzure West ↔ Chicago: 2 of 2 paths upAzure West ↔ SASE: 1 of 1 paths upBoston ↔ Dallas: 1 of 1 paths upBoston ↔ SASE: 1 of 1 paths upCharlotte ↔ Chicago: 2 of 2 paths upCharlotte ↔ SASE: 1 of 1 paths upChicago ↔ Dallas: 2 of 2 paths upChicago ↔ Denver: 2 of 2 paths upChicago ↔ Detroit: 2 of 2 paths upChicago ↔ Houston: 2 of 2 paths upChicago ↔ Los Angeles: 2 of 2 paths upChicago ↔ Miami: 2 of 2 paths upChicago ↔ Minneapolis: 2 of 2 paths upChicago ↔ New York: 2 of 2 paths upChicago ↔ Phoenix: 2 of 2 paths upChicago ↔ SASE: 1 of 1 paths upChicago ↔ Seattle: 2 of 2 paths upDallas ↔ SASE: 1 of 1 paths upDenver ↔ SASE: 1 of 1 paths upDetroit ↔ SASE: 1 of 1 paths upSASE ↔ Houston: 1 of 1 paths upSASE ↔ Los Angeles: 1 of 1 paths upSASE ↔ Miami: 1 of 1 paths upSASE ↔ Minneapolis: 1 of 1 paths upSASE ↔ New York: 1 of 1 paths upSASE ↔ Philadelphia: 1 of 1 paths upSASE ↔ Phoenix: 1 of 1 paths upSASE ↔ Seattle: 1 of 1 paths upAtlanta ↔ Chicago: 1 of 2 paths up – Atlanta Example Fiber ↔ Chicago Example Fiber: Up – one-way trafficChicago ↔ Philadelphia: 0 of 2 paths up – Chicago Example Fiber ↔ Philadelphia Example Fiber: Up on one end only; Chicago Metro Cable ↔ Philadelphia Metro Cable: Up on one end onlyBoston ↔ Chicago: 0 of 2 paths up – Boston Example Fiber ↔ Chicago Example Fiber: Down; Boston Metro Cable ↔ Chicago Metro Cable: DownAzure East ↔ Atlanta: 2 of 2 paths upAzure East ↔ Boston: 2 of 2 paths upAzure East ↔ Dallas: 2 of 2 paths upAzure East ↔ Denver: 2 of 2 paths upAzure East ↔ Los Angeles: 2 of 2 paths upAzure East ↔ Miami: 2 of 2 paths upAzure East ↔ Minneapolis: 2 of 2 paths upAzure East ↔ New York: 2 of 2 paths upAzure East ↔ Philadelphia: 2 of 2 paths upAzure East ↔ Phoenix: 2 of 2 paths upAzure East ↔ Seattle: 2 of 2 paths upAzure East ↔ Charlotte: 2 of 2 paths upAzure East ↔ Detroit: 2 of 2 paths upAzure East ↔ Houston: 2 of 2 paths upAzure West ↔ Atlanta: 2 of 2 paths upAzure West ↔ Boston: 2 of 2 paths upAzure West ↔ Dallas: 2 of 2 paths upAzure West ↔ Denver: 2 of 2 paths upAzure West ↔ Los Angeles: 2 of 2 paths upAzure West ↔ Miami: 2 of 2 paths upAzure West ↔ Minneapolis: 2 of 2 paths upAzure West ↔ New York: 2 of 2 paths upAzure West ↔ Philadelphia: 2 of 2 paths upAzure West ↔ Phoenix: 2 of 2 paths upAzure West ↔ Seattle: 2 of 2 paths upAzure West ↔ Charlotte: 2 of 2 paths upAzure West ↔ Detroit: 2 of 2 paths upAzure West ↔ Houston: 2 of 2 paths upSASE – Plano, Texas (seen from the firewalls only)SASEPlano, TXGEHA Field at Arrowhead Stadium – Kansas City, Missouri (Chiefs)Atlanta – Warning Chicago: 1 of 2 paths up Atlanta Example Fiber ↔ Chicago Example Fiber: Up – one-way trafficAtlantaAzure East – HealthyAzure EastAzure West – HealthyAzure WestBoston – Warning 2 of 3 IPsec tunnels are down: to-chicago, to-chicago-b Collector ping to FG-BOSTON-SW1 (10.255.15.10): 263 ms, 33% loss Collector ping to Boston FortiGate (10.250.0.15): 239 ms, 33% loss Collector ping to boston FortiGate (users) (10.15.10.1): 292 ms, 33% loss Collector ping to boston servers gateway (10.15.30.1): 211 ms, 33% loss Collector ping to boston printers gateway (10.15.40.1): 260 ms, 0% loss Collector ping to boston cameras gateway (10.15.50.1): 270 ms, 33% loss Collector ping to boston iot gateway (10.15.90.1): 263 ms, 33% loss Collector ping to boston FortiLink (10.255.15.1): 284 ms, 33% loss Collector ping to FG-BOSTON-AP1 (10.15.10.20): 229 ms, 33% loss Collector ping to FG-BOSTON-AP2 (10.15.10.21): 275 ms, 33% loss Collector ping to boston DNS 10.1.30.2 (10.1.30.2): 272 ms, 0% loss Collector ping to boston DNS 10.1.30.3 (10.1.30.3): 263 ms, 33% loss Chicago: 0 of 2 paths up Boston Example Fiber ↔ Chicago Example Fiber: Down Boston Metro Cable ↔ Chicago Metro Cable: DownBostonCharlotte: Charlotte, Charlotte OT2CharlotteCharlotte, Charlotte OTChicago – Healthy Boston: 0 of 2 paths up Boston Example Fiber ↔ Chicago Example Fiber: Down Boston Metro Cable ↔ Chicago Metro Cable: Down Atlanta: 1 of 2 paths up Atlanta Example Fiber ↔ Chicago Example Fiber: Up – one-way traffic Philadelphia: 0 of 2 paths up Chicago Example Fiber ↔ Philadelphia Example Fiber: Up on one end only Chicago Metro Cable ↔ Philadelphia Metro Cable: Up on one end onlyChicagoDallas – HealthyDallasDenver – Warning Collector ping to Example Fiber gateway (203.0.113.17): 289 ms, 0% lossDenverDetroit: Detroit, Detroit OT2DetroitDetroit, Detroit OTHouston: Houston, Houston OT Collector ping to PLC-LINE2 (10.3.90.5) failed: no reply2HoustonHouston, Houston OTLos Angeles – HealthyLos AngelesMiami – Warning Data is 30 hours old – last successful collection Nov 21, 10:16 AMMiamiMinneapolis – HealthyMinneapolisNew York – HealthyNew YorkPhiladelphia – Down Collection failing since Nov 22, 11:16 AM (4 attempts): timed out – showing data from Nov 20, 2:16 PM Data is 50 hours old – last successful collection Nov 20, 2:16 PM Collector ping to FG-PHILADELPH-SW1 (10.255.18.10) failed: no reply Collector ping to Example Fiber gateway (203.0.113.1) failed: no reply Collector ping to Philadelphia FortiGate (10.250.0.18) failed: no reply Collector ping to philadelphia FortiGate (users) (10.18.10.1) failed: no reply Collector ping to philadelphia servers gateway (10.18.30.1) failed: no reply Collector ping to philadelphia printers gateway (10.18.40.1) failed: no reply Collector ping to philadelphia cameras gateway (10.18.50.1) failed: no reply Collector ping to philadelphia iot gateway (10.18.90.1) failed: no reply Collector ping to philadelphia FortiLink (10.255.18.1) failed: no reply Collector ping to FG-PHILADELPH-AP1 (10.18.10.20) failed: no reply Collector ping to FG-PHILADELPH-AP2 (10.18.10.21) failed: no reply Collector ping to philadelphia DNS 10.1.30.2 (10.1.30.2) failed: no reply Collector ping to philadelphia DNS 10.1.30.3 (10.1.30.3) failed: no reply Chicago: 0 of 2 paths up Chicago Example Fiber ↔ Philadelphia Example Fiber: Up on one end only Chicago Metro Cable ↔ Philadelphia Metro Cable: Up on one end onlyPhiladelphiaPhoenix – Warning WAN Metro Cable (wan2) is downPhoenixSeattle – HealthySeattleAll paths upSome paths down / one-way – still connectedNo working pathCloud VPN / IPsec up (Azure ↔ every site, SASE in Plano)Cloud VPN with issuesCloud VPN downCloud tunnel (SASE), dashed when downIPsec between places · dot = site status

Backups

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