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

Philadelphia

Guide: Service desk › 2. What the colours mean
✕Down
Download devices (CSV) ↓
Last collected Nov 20, 2:16 PM · latest attempt failed 2026-11-22T16:15:09 · Firmware
FortiGate
Standalone
Switches
1 / 1
APs
2 / 2
IPsec
2 / 2

Needs attention 15

  • ✕unreachable
    • Collection failing since Nov 22, 11:16 AM (4 attempts): timed out – showing data from Nov 20, 2:16 PM
    Explain →
    Evidence

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

    collector
    timed out  ·  TCP 22: no answer on port 22
    How to fix
    No other site has a tunnel up to Philadelphia (2 configured) – the site may really be down.

    The collector couldn't log in to this FortiGate this time (timed out), so the page shows the last good data. It has failed 4 times in a row since Nov 22, 11:16 AM.

    1. Check the site is up some other way.
    2. From NET-DEMO01: test the path (below).
    3. Read the FortiGate's event log for the login.
    # on NET-DEMO01 (PowerShell):
    Test-NetConnection 10.250.0.18 -Port 22
    
    # on the FortiGate (your admin account) – why it refused the login:
    execute log filter category event
    execute log filter field user netmap
    execute log display
    
    # --- on Philadelphia's FortiGate. Safe to share – no keys:
    get router info routing-table details 10.250.0.5
    diagnose sniffer packet any 'host 10.250.0.5 and port 22' 4 20
    #   nothing arrives          -> the request never left the far end on a tunnel that reaches this site
    #   arrives, no reply leaves -> this FortiGate ignores it: policy, or the source is no longer the trusted host
    #   reply leaves elsewhere   -> the return route is wrong here
    
    # The next commands print LIVE KEYS (tunnel encryption keys, pre-shared keys). Read them on the FortiGate –
    # never paste their output into a ticket, an email or a chat.
    #   diagnose vpn tunnel list   ·   diagnose vpn ike gateway list   ·   show vpn ipsec phase1-interface
  • ▲FG-PHILADELPH-SW1 unreachable
    • Collector ping to FG-PHILADELPH-SW1 (10.255.18.10) failed: no reply
    Explain →
    How to fix

    The collector cannot ping FG-PHILADELPH-SW1 (10.255.18.10). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲Philadelphia FortiGate unreachable
    • Collector ping to Philadelphia FortiGate (10.250.0.18) failed: no reply
    Explain →
    How to fix

    The collector cannot ping Philadelphia FortiGate (10.250.0.18). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia FortiGate (users) unreachable
    • Collector ping to philadelphia FortiGate (users) (10.18.10.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia FortiGate (users) (10.18.10.1). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia servers gateway unreachable
    • Collector ping to philadelphia servers gateway (10.18.30.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia servers gateway (10.18.30.1). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia printers gateway unreachable
    • Collector ping to philadelphia printers gateway (10.18.40.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia printers gateway (10.18.40.1). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia cameras gateway unreachable
    • Collector ping to philadelphia cameras gateway (10.18.50.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia cameras gateway (10.18.50.1). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia iot gateway unreachable
    • Collector ping to philadelphia iot gateway (10.18.90.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia iot gateway (10.18.90.1). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia FortiLink unreachable
    • Collector ping to philadelphia FortiLink (10.255.18.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia FortiLink (10.255.18.1). A critical internal address is unreachable from the Vantage server.

    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-PHILADELPH-AP1 unreachable
    • Collector ping to FG-PHILADELPH-AP1 (10.18.10.20) failed: no reply
    Explain →
    How to fix

    The collector cannot ping FG-PHILADELPH-AP1 (10.18.10.20). A critical internal address is unreachable from the Vantage server.

    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-PHILADELPH-AP2 unreachable
    • Collector ping to FG-PHILADELPH-AP2 (10.18.10.21) failed: no reply
    Explain →
    How to fix

    The collector cannot ping FG-PHILADELPH-AP2 (10.18.10.21). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia DNS 10.1.30.2 unreachable
    • Collector ping to philadelphia DNS 10.1.30.2 (10.1.30.2) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia DNS 10.1.30.2 (10.1.30.2). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲philadelphia DNS 10.1.30.3 unreachable
    • Collector ping to philadelphia DNS 10.1.30.3 (10.1.30.3) failed: no reply
    Explain →
    How to fix

    The collector cannot ping philadelphia DNS 10.1.30.3 (10.1.30.3). A critical internal address is unreachable from the Vantage server.

    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 →

  • ▲Example Fiber gateway unreachable
    • Collector ping to Example Fiber gateway (203.0.113.1) failed: no reply
    Explain →
    How to fix

    The collector cannot ping Example Fiber gateway (203.0.113.1). An ISP gateway or external service is unreachable from the Vantage server.

    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 →

  • ✕data 50 h old
    • Data is 50 hours old – last successful collection Nov 20, 2:16 PM
    Explain →
    How to fix

    No successful collection for over a day – everything on this page may be out of date.

    1. Check the scheduled task ran (Task Scheduler → History of the hourly task).
    2. Read the latest log in C:\netmap\logs – a failed site's line ends with a diagnosis.
    3. Run the hourly task now and read the log again (manual runs go through the task – only its account can read the key).
    # on NET-DEMO01 (elevated PowerShell):
    Start-ScheduledTask "Vantage hourly"
    Get-Content (Get-ChildItem C:\netmap\logs\daily-*.log | Sort-Object LastWriteTime | Select-Object -Last 1) -Encoding UTF8 -Tail 30
Notes to reviewHousekeeping 1

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

Philadelphia 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.