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

Boston

Guide: Service desk › 2. What the colours mean
▲Warning
Download devices (CSV) ↓
Last collected Nov 22, 4:15 PM · Firmware
Internet
2 / 2
FortiGate
Standalone
Switches
1 / 1
APs
2 / 2
IPsec
1 / 3

Needs attention 13

  • ▲most tunnels down
    • 2 of 3 IPsec tunnels are down: to-chicago, to-chicago-b
    Explain →
    Evidence

    Exact lines from the FortiGate output collected for this site – check them against the live device.

    get vpn ipsec tunnel summary
    'to-chicago' 203.0.113.11:0  selectors(total,up): 1/0  rx(pkt,err): 0/0  tx(pkt,err): 0/0
    'to-chicago-b' 198.51.100.11:0  selectors(total,up): 1/0  rx(pkt,err): 0/0  tx(pkt,err): 0/0
    How to fix

    Some IPsec tunnels to other sites are down. If the aggregate's other member is up, traffic still flows – this is lost redundancy, not an outage. Backup tunnels whose phase 2 isn't set to auto-negotiate stay down until traffic needs them, so they look down here.

    1. Check the tunnel from this end (and the other site's end) – the WAN page's Tunnel paths tab shows both.
    2. For backup tunnels, enable auto-negotiate on their phase 2 (below) so they stay up.
    3. Tunnels that point at the wrong IP or a site that no longer exists: fix the remote gateway, or delete them.

    to-chicago → 203.0.113.11
    to-chicago-b → 198.51.100.11

    get vpn ipsec tunnel summary
    diagnose vpn tunnel list name to-chicago
    diagnose vpn tunnel list name to-chicago-b

    Tunnel paths →

  • ▲FG-BOSTON-SW1 slow ping
    • Collector ping to FG-BOSTON-SW1 (10.255.15.10): 263 ms, 33% loss
    Explain →
    How to fix

    The collector can ping FG-BOSTON-SW1, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲Boston FortiGate slow ping
    • Collector ping to Boston FortiGate (10.250.0.15): 239 ms, 33% loss
    Explain →
    How to fix

    The collector can ping Boston FortiGate, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston FortiGate (users) slow ping
    • Collector ping to boston FortiGate (users) (10.15.10.1): 292 ms, 33% loss
    Explain →
    How to fix

    The collector can ping boston FortiGate (users), but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston servers gateway slow ping
    • Collector ping to boston servers gateway (10.15.30.1): 211 ms, 33% loss
    Explain →
    How to fix

    The collector can ping boston servers gateway, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston printers gateway slow ping
    • Collector ping to boston printers gateway (10.15.40.1): 260 ms, 0% loss
    Explain →
    How to fix

    The collector can ping boston printers gateway, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston cameras gateway slow ping
    • Collector ping to boston cameras gateway (10.15.50.1): 270 ms, 33% loss
    Explain →
    How to fix

    The collector can ping boston cameras gateway, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston iot gateway slow ping
    • Collector ping to boston iot gateway (10.15.90.1): 263 ms, 33% loss
    Explain →
    How to fix

    The collector can ping boston iot gateway, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston FortiLink slow ping
    • Collector ping to boston FortiLink (10.255.15.1): 284 ms, 33% loss
    Explain →
    How to fix

    The collector can ping boston FortiLink, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲FG-BOSTON-AP1 slow ping
    • Collector ping to FG-BOSTON-AP1 (10.15.10.20): 229 ms, 33% loss
    Explain →
    How to fix

    The collector can ping FG-BOSTON-AP1, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲FG-BOSTON-AP2 slow ping
    • Collector ping to FG-BOSTON-AP2 (10.15.10.21): 275 ms, 33% loss
    Explain →
    How to fix

    The collector can ping FG-BOSTON-AP2, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston DNS 10.1.30.2 slow ping
    • Collector ping to boston DNS 10.1.30.2 (10.1.30.2): 272 ms, 0% loss
    Explain →
    How to fix

    The collector can ping boston DNS 10.1.30.2, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

  • ▲boston DNS 10.1.30.3 slow ping
    • Collector ping to boston DNS 10.1.30.3 (10.1.30.3): 263 ms, 33% loss
    Explain →
    How to fix

    The collector can ping boston DNS 10.1.30.3, but latency or loss is high.

    1. Confirm the address still answers from the collector (ping).
    2. Check routing and firewall policy between the collector and the target.
    3. If this is an ISP gateway, check the circuit on Circuits & contacts.

    Ping →

Network gear only: FortiGate, switches and access points. Same map as today.

Boston topologyDrag to pan · Ctrl + scroll to zoom · click a box for details
Loading map…

Backups

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