Network gear only: FortiGate, switches and access points. Same map as today.
Every device at this site that the FortiGate manages, worst first in each fold. The square is the device's status as on the map; the numbers beside it never change a box colour. API read 2026-11-22 16:13 (full run). Wi-Fi clients are on Find ("Wi-Fi via" their access point).
FortiGate1
| FortiGate | Model | Firmware | CPU 24 h | CPU | Mem | Sessions | WAN use | Config | In plain words | |
|---|---|---|---|---|---|---|---|---|---|---|
| FG-NEWYORK | FortiGate-40F | 7.4.8 | 16% | 49% | 704 | 41% · wan1 | — | Working normally |
Switches11 · 0 need a look · PoE 42 of 370 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-NEWYORK-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 42 of 370 W | — | — | 7.4.5 | Working normally |
Access points22 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-NEWYORK-AP1 | FP231F | — | — | — | — | FG-NEWYORK-SW1 port3 | 7.4.3 | Working normally | |
| FG-NEWYORK-AP2 | FP231F | — | — | — | — | FG-NEWYORK-SW1 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.12.10.0/24 | 10.12.10.1 | 255.255.255.0 /24 | 10.12.10.20 – 10.12.10.250 231 addresses · 5 in use · lease 8 hours | |
| 20 | voice | 10.12.20.0/24 | 10.12.20.1 | 255.255.255.0 /24 | 10.12.20.20 – 10.12.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.12.30.0/24 | 10.12.30.1 | 255.255.255.0 /24 | 10.12.30.20 – 10.12.30.250 231 addresses · 0 in use · lease 7 days · 3 reserved | |
| 40 | printers | 10.12.40.0/24 | 10.12.40.1 | 255.255.255.0 /24 | 10.12.40.100 – 10.12.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.12.50.0/24 | 10.12.50.1 | 255.255.255.0 /24 | 10.12.50.100 – 10.12.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.12.90.0/24 | 10.12.90.1 | 255.255.255.0 /24 | 10.12.90.100 – 10.12.90.199 100 addresses · 0 in use · lease 7 days |
DHCP: "in use" is an estimate – addresses in the scope that answered at the last collection, plus the reservations. A lease held by a device that is switched off is not counted, so the real number free can be lower. Networks whose DHCP is relayed are served elsewhere and show only the relay target.
Other FortiGate networks
| Interface | Type | Subnet | Address |
|---|---|---|---|
| fortilink | FortiLink (switch management) | 10.255.12.0/24 | 10.255.12.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 4 | 3 Computer · 1 Network gear |
| 20 | voice | 2 | 2 Phone (VoIP) |
| 30 | servers | 3 | 2 Storage / server · 1 UPS / power |
| 40 | printers | 1 | 1 Printer |
| 50 | cameras | 1 | 1 Camera |
| 90 | iot | 1 | 1 IoT / industrial (by network) |
| FortiLink | FortiLink | 1 | 1 Network gear |
| 10 | users | 2 | 2 Access point |
Types are a best guess from each MAC address's maker (IEEE registry, offline) and the network's name – useful to spot a camera on the data VLAN or a PC on the camera VLAN. "Private MAC" = phones and laptops using randomised addresses. Search a type on Find.
1 switches · 14 ports in use · 14 free. "In use" = link up, a device learned, or PoE delivering. Device names come from LLDP and the AP list; addresses from the FortiGate's ARP table. Find any IP or MAC →
Capacity by closet1 closet14 of 28 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| New York | Closet 1 FG-NEWYORK-SW1 | 14 / 28 (50%) | 10 | 10 | 42 / 370 W (11%) 328 W headroom |
Free = no link, no device learned and no PoE at the last collection – a device that was switched off may look free. Closets come from each switch's description on the FortiGate ("Building / Closet"). Orange from 85% ports / 75% PoE, red from 95% / 90%. Capacity across sites →
Switches
FG-NEWYORK-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 42 / 370 W · 45 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-NEWYORK-AP1 FortiAP | 10 users | 10.12.10.20 · 00:11:22:0c:00:00 | 11.6 W class 4 | |
| port4 | Up | FG-NEWYORK-AP2 FortiAP | 10 users | 10.12.10.21 · 00:11:22:0c:00:01 | 13.4 W class 4 | |
| port7 | Up | FILE01 | 30 servers | 10.12.30.2 · f8:bc:12:79:d2:8d | ||
| port8 | Up | IPERF01 | 30 servers | 10.12.30.3 · f8:bc:12:20:f7:bb | ||
| port9 | Up | UPS-MDF | 30 servers | 10.12.30.4 · 00:c0:b7:6b:32:3a | ||
| port10 | Up | DOOR-FRONT | 90 iot | 10.12.90.2 · 00:06:8e:b0:3b:3e | 4.2 W class 2 | |
| port13 | Up | NL-NYC-PC011 | 10 users | 10.12.10.120 · d0:43:1e:0c:0a:01 | ||
| port14 | Up | NL-NYC-LT012 | 10 users | 10.12.10.121 · d0:43:1e:0c:0a:02 | ||
| port15 | Up | NL-NYC-PC013 | 10 users | 10.12.10.122 · d0:43:1e:0c:0a:03 | ||
| port16 | Up | NL-NYC-PH01 phone | 20 voice | 10.12.20.20 · 00:04:f2:0c:14:01 | 3.2 W class 2 | |
| port17 | Up | NL-NYC-PH02 phone | 20 voice | 10.12.20.21 · 00:04:f2:0c:14:02 | 4.0 W class 2 | |
| port18 | Up | PRN-NYC-01 | 40 printers | 10.12.40.20 · 3c:2a:f4:0c:28:01 | ||
| port19 | Up | CAM-LOBBY-01 | 50 cameras | 10.12.50.20 · 00:40:8c:0c:32:01 | 5.5 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00120001 |
Free ports: port1–2, port5–6, port11–12, port20–23, port25–28
S124FF12010001 · FortiSwitchOS 7.4.5
On-site contacts
- Avery Chen · (212) 555-1012 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 1/1/2025 to 1/1/2028 · 405 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.22 /29
- Gateway
- 203.0.113.17
- Circuit ID
- NL-121
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 3/2/2025 to 3/2/2028 · 466 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.22 /29
- Gateway
- 198.51.100.17
- Circuit ID
- NL-122
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summaryOSPF configured
From show router static, show router bgp, show router policy and show router ospf at the last collection. Counts only — see Consistency to compare across sites.
| Network | Type | Next hop |
|---|---|---|
| 0.0.0.0/0 | Static | wan1 internet wan2 internet · equal cost |
| 10.12.10.0/24 | Connected | users local network |
| 10.12.20.0/24 | Connected | voice local network |
| 10.12.30.0/24 | Connected | servers local network |
| 10.12.40.0/24 | Connected | printers local network |
| 10.12.50.0/24 | Connected | cameras local network |
| 10.12.90.0/24 | Connected | iot local network |
| 10.255.12.0/24 | Connected | fortilink local network |
| 198.51.100.16/29 | Connected | wan2 local network |
| 203.0.113.16/29 | Connected | wan1 local network |
From get router info routing-table all at the last collection. A tunnel or IPsec aggregate is named with the site it leads to. Want the full path to a device? Use Find → tick two devices → Build path.
Status – last 30 days
WAN quality
Show as table (daily median)
| Day | Circuit | Latency ms | Jitter ms | Loss % |
|---|---|---|---|---|
| 2026-11-22 | Metro Cable | 9 | 1.5 | 0 |
| 2026-11-22 | Example Fiber | 8.6 | 1.5 | 0 |
| 2026-11-21 | Metro Cable | 10.7 | 1.5 | 0 |
| 2026-11-21 | Example Fiber | 8.7 | 1.2 | 0.2 |
| 2026-11-20 | Metro Cable | 10.3 | 1.5 | 0.2 |
| 2026-11-20 | Example Fiber | 8.5 | 1.2 | 0.2 |
| 2026-11-19 | Metro Cable | 8.5 | 1.1 | 0 |
| 2026-11-19 | Example Fiber | 9.1 | 0.8 | 0 |
| 2026-11-18 | Metro Cable | 10.5 | 1.7 | 0 |
| 2026-11-18 | Example Fiber | 7.6 | 1.5 | 0 |
| 2026-11-17 | Metro Cable | 9.2 | 1.7 | 0.2 |
| 2026-11-17 | Example Fiber | 9.1 | 1.5 | 0 |
| 2026-11-16 | Metro Cable | 9.2 | 1.5 | 0 |
| 2026-11-16 | Example Fiber | 8.9 | 1.6 | 0.2 |
| 2026-11-15 | Metro Cable | 8.8 | 1.5 | 0 |
| 2026-11-15 | Example Fiber | 8.8 | 1.4 | 0 |
| 2026-11-14 | Metro Cable | 9.6 | 1.5 | 0 |
| 2026-11-14 | Example Fiber | 8 | 1.6 | 0 |
| 2026-11-13 | Metro Cable | 9.6 | 1.1 | 0 |
| 2026-11-13 | Example Fiber | 7.6 | 1.8 | 0 |
| 2026-11-12 | Metro Cable | 9.4 | 1.1 | 0 |
| 2026-11-12 | Example Fiber | 8.6 | 1 | 0 |
| 2026-11-11 | Metro Cable | 8.9 | 1.5 | 0.2 |
| 2026-11-11 | Example Fiber | 8.8 | 1.6 | 0.2 |
| 2026-11-10 | Metro Cable | 10.3 | 1.1 | 0 |
| 2026-11-10 | Example Fiber | 9.3 | 1.4 | 0.5 |
| 2026-11-09 | Metro Cable | 9.8 | 1 | 0 |
| 2026-11-09 | Example Fiber | 8.8 | 1.2 | 0 |
| 2026-11-08 | Metro Cable | 9.8 | 1.5 | 0 |
| 2026-11-08 | Example Fiber | 8.1 | 1.3 | 0.2 |
| 2026-11-07 | Metro Cable | 9.3 | 1.3 | 0 |
| 2026-11-07 | Example Fiber | 8.5 | 1.7 | 0 |
| 2026-11-06 | Metro Cable | 9.6 | 1.2 | 0.2 |
| 2026-11-06 | Example Fiber | 9.4 | 1.8 | 0.5 |
| 2026-11-05 | Metro Cable | 10.1 | 1.4 | 0.2 |
| 2026-11-05 | Example Fiber | 8.3 | 1.1 | 0 |
| 2026-11-04 | Metro Cable | 10.3 | 1.6 | 0 |
| 2026-11-04 | Example Fiber | 8.6 | 1.6 | 0.2 |
| 2026-11-03 | Metro Cable | 9.3 | 1.1 | 0 |
| 2026-11-03 | Example Fiber | 8.4 | 1.8 | 0 |
| 2026-11-02 | Metro Cable | 9.8 | 1.5 | 0 |
| 2026-11-02 | Example Fiber | 8.3 | 1.5 | 0 |
| 2026-11-01 | Metro Cable | 10.2 | 1.3 | 0.2 |
| 2026-11-01 | Example Fiber | 9.5 | 0.9 | 0 |
| 2026-10-31 | Metro Cable | 9.7 | 1.4 | 0 |
| 2026-10-31 | Example Fiber | 9.2 | 1.6 | 0 |
| 2026-10-30 | Metro Cable | 9.7 | 0.9 | 0 |
| 2026-10-30 | Example Fiber | 8.4 | 1.7 | 0 |
| 2026-10-29 | Metro Cable | 10.4 | 1.6 | 0.2 |
| 2026-10-29 | Example Fiber | 8.2 | 2 | 0 |
| 2026-10-28 | Metro Cable | 10.2 | 1.1 | 0 |
| 2026-10-28 | Example Fiber | 8.4 | 1.1 | 0 |
| 2026-10-27 | Metro Cable | 9.8 | 1.8 | 0.2 |
| 2026-10-27 | Example Fiber | 8.2 | 1.3 | 0 |
| 2026-10-26 | Metro Cable | 9.4 | 1.8 | 0 |
| 2026-10-26 | Example Fiber | 9.7 | 1.5 | 0 |
| 2026-10-25 | Metro Cable | 9.7 | 1 | 0.2 |
| 2026-10-25 | Example Fiber | 8 | 1.5 | 0 |
| 2026-10-24 | Metro Cable | 8.7 | 1.4 | 0 |
| 2026-10-24 | Example Fiber | 8.7 | 1.8 | 0.2 |
| 2026-10-23 | Metro Cable | 8.8 | 2.2 | 0 |
| 2026-10-23 | Example Fiber | 7.6 | 1.3 | 0 |
Tunnel stability – last 7 days
2 tunnels · 2 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 2
| When | Type | What | Detail |
|---|---|---|---|
| Nov 4 9:40 PM | Config | Address srv-backup-14 | added: subnet 10.14.30.14 255.255.255.255 |
| Oct 25 4:43 PM | Config | Interface printers | description: – → Floor 2 printers |
New and moved devices – last 30 days 1
Devices seen on a switch port for the first time, or on a different port – marked Wired, or Wi-Fi when the port is an access point's (the access point is named). A move from one access point to another is listed as a Wi-Fi roam. Devices on Wi-Fi networks that are tunnelled to the FortiGate never appear on a switch port and are not listed here. Private (randomised) MAC addresses are left out.
| When | Type | What | Detail |
|---|---|---|---|
| Nov 8 5:49 PM | New deviceWired | New device 00:04:f2:0c:14:01 | 10.12.20.20 NL-NYC-PH01 on FG-NEWYORK-SW1 port16 |
Worth fixing when there's time. Security items are listed first and marked in red. Open is the default. A muted, hidden, accepted or won't-fix note stays here and does not change the colour.
How this works
- Security exposure1
- ●known-bad addresses not blocked
- No firewall policy drops FortiGuard's known-bad addresses (Malicious servers, Botnet C&C, Tor exit nodes) for traffic coming in from the internet or traffic going out to them. SD-WAN is on: a policy names the zone (virtual-wan-link), not its member ports.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show firewall policy(no policy uses FortiGuard Internet Service entries)How to fix
FortiGuard already knows the addresses of malicious servers, botnet controllers and Tor exit nodes (the Internet Service Database, part of the FortiGuard subscription). A deny policy that uses them stops known-bad traffic at the edge – the FortiGate does the blocking; Vantage only reads the configuration. The policy only works above the allow policies: FortiGate uses the first policy that matches. SD-WAN is on, so the policies name the SD-WAN zone (virtual-wan-link: wan1, wan2). A member port cannot be used in a policy on its own.
- Check the Internet Service names on this firmware (first line below) and adjust them if they differ.
- Block-known-bad-in is added as policy 12, the next free number. No allow policy uses the internet side yet, so it does not need moving.
- Block-known-bad-out is added as policy 13, the next free number. The move line puts it above allow policy 1, the first one that lets internet traffic through.
- Paste the commands in a change window. The last lines show each policy, so you can see it took.
- Watch the logs for a day: if something you need is blocked, find out why before making an exception.
- Blocking another way (an external threat feed, or upstream)? Acknowledge this note in the site file ("acknowledged": {"badip_block": {"fortiguard-block": "why"}}).
Caution: a deny policy placed above your allow policies can stop traffic you need if FortiGuard lists an address you use. Use a change window and keep console or out-of-band access.
# The names differ between firmware versions - check them first: show firewall internet-service-name | grep -i -e malicious -e botnet -e tor config firewall policy edit 12 set name "Block-known-bad-in" set srcintf "virtual-wan-link" set dstintf "any" set internet-service-src enable set internet-service-src-name "Malicious-Malicious.Server" "Botnet-C&C.Server" "Tor-Exit.Node" set dstaddr "all" set action deny set schedule "always" set service "ALL" set logtraffic all next edit 13 set name "Block-known-bad-out" set srcintf "any" set dstintf "virtual-wan-link" set srcaddr "all" set internet-service enable set internet-service-name "Malicious-Malicious.Server" "Botnet-C&C.Server" set action deny set schedule "always" set logtraffic all next move 13 before 1 end # check the result: show firewall policy 12 show firewall policy 13 - Redundancy reduced1
- ●no OSPF neighbour
- OSPF is set up on to-chicago but no neighbour is up there – routes to the far end come another way, or not at all
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get router info ospf neighborOSPF process 0, VRF 0: Neighbor ID Pri State Dead Time Address InterfaceHow to fix
OSPF is configured on this tunnel or aggregate and the tunnel is up, but no neighbour has formed. Usual causes: the aggregate has no running members (see that item), hellos leave on one member and return on another, or the two ends disagree on area, network type, timers or MTU.
- If this page also lists an aggregate that is not running, fix that first – OSPF cannot form over it.
- Compare the OSPF interface settings at both ends.
- Watch whether hellos arrive and leave (below).
# on the PRIMARY unit (get system status | grep -i 'HA mode') # safe to share (no keys): get router info ospf neighbor get router info ospf interface diagnose sniffer packet any 'proto 89' 4 10 - Configuration1
- ●no blackhole routes
- No blackhole route for 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. When a VPN route disappears (tunnel or OSPF down), traffic for that remote network follows the default route to the internet instead of being dropped – and sessions can stick to the wrong path after the tunnel recovers.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get router info routing-table allS* 0.0.0.0/0 [1/0] via 203.0.113.17, wan1, [1/0]How to fix
Fortinet's VPN best practice: a blackhole route for each private range at a high distance (254). If a tunnel or OSPF drops, the more specific VPN route disappears and the blackhole catches the traffic – instead of the default route sending internal traffic to the internet (and sessions sticking to that path after recovery).
- Add the routes below (distance 254, so any real route wins).
- Make sure no local network is only reachable through the default route.
- Check: get router info routing-table all shows the blackholes with [254/0].
config router static edit 0 set dst 10.0.0.0/8 set blackhole enable set distance 254 set comment "RFC1918 blackhole" next edit 0 set dst 172.16.0.0/12 set blackhole enable set distance 254 set comment "RFC1918 blackhole" next edit 0 set dst 192.168.0.0/16 set blackhole enable set distance 254 set comment "RFC1918 blackhole" next end
What is on file about this site – kept in the library folder on the collector and filled in from your documents: check a value against its source before you rely on it. It never changes the site's status.
- floor plan New York floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment4 devices1 with support ended
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-NEWYORK FortiGate · FortiGate 40F | FGDEMO00120001 tag NL-0012 | New York Northline | 2021-01-04 5.9 years old PO PO-55513 · Example Reseller | Standard 2028-02-29 contract NL-SUP-12 warranty 2022-01-04 passed | 2032-09-30 end of order 2027-09-30 | 2027 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-NEWYORK-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF12010001 tag NL-12S01 | New York · Closet 1 · Rack 1 Network team | 2021-02-15 5.8 years old PO PO-56120 · Example Reseller | Standard 2026-03-01 ended contract NL-FSW warranty 2026-03-01 passed | 2033-03-31 end of order 2028-03-31 | 2027 → FortiSwitch 124G-FPOE spare: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-NEWYORK-AP1 FortiAP · FAP231F | FP231F12010001 tag NL-12A01 | New York · Ceiling, zone 1 Network team | 2022-05-10 4.5 years old PO PO-57120 · Example Reseller | Standard 2027-06-01 contract NL-FAP warranty 2027-06-01 | 2033-06-30 end of order 2028-06-30 | 2028 → FortiAP 431G spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-NEWYORK-AP2 FortiAP · FAP231F | FP231F12020001 tag NL-12A02 | New York · Ceiling, zone 2 Network team | 2023-05-10 3.5 years old PO PO-57121 · Example Reseller | Standard 2028-06-01 contract NL-FAP warranty 2028-06-01 | 2033-06-30 end of order 2028-06-30 | 2029 → FortiAP 431G spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
Red = support has ended (the contract's date, or the maker's end of support); orange = the contract ends within 90 days, or the maker's end of support is within a year. All sites together: Lifecycle.
Circuit contracts2 circuits
| Circuit | Bandwidth | Ping | From | Ends | Notice | SLA | |
|---|---|---|---|---|---|---|---|
| Example Fiber Example Fiber · wan1 · NL-121 | 500/500 | 9 ms collector ping | 2025-01-01 | 2028-01-01 give notice within 315 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-122 | 300/30 | 12 ms collector ping | 2025-03-02 | 2028-03-02 give notice within 406 days | 60 days renews by itself: no | 99.5 Made-up circuit. |
Ping is collector ICMP to the ISP gateway (same sample as Circuits). Contract dates stay as filled in from documents.
Networks – the IP plan6 networks
| VLAN | Name | Subnet | Gateway | Purpose | Reserved | |
|---|---|---|---|---|---|---|
| 10 | users | 10.12.10.0/24 | 10.12.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up New York network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.12.20.0/24 | 10.12.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up New York network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.12.30.0/24 | 10.12.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up New York network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.12.40.0/24 | 10.12.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up New York network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.12.50.0/24 | 10.12.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up New York network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.12.90.0/24 | 10.12.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up New York network. | sourcehttps://files.example.com/northline/networks |
Documents0 documents
The demo shows Service desk articles only.
For every site0 documents
The demo shows Service desk articles only.