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-SEATTLE | FortiGate-90G | 7.4.8 | 19% | 49% | 6,050 | 31% · wan1 | — | Working normally |
Switches33 · 0 need a look · PoE 151 of 1110 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-SEATTLE-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 62 of 370 W | — | FG-SEATTLE-SW2 port28 (port25) | 7.4.5 | Working normally | |
| FG-SEATTLE-SW2 | FortiSwitch 124F-FPOE | 11 / 28 | 35 of 370 W | — | FG-SEATTLE-SW1 port25 (port28) | 7.4.5 | Working normally | |
| FG-SEATTLE-SW3 | FortiSwitch 124F-FPOE | 10 / 28 | 54 of 370 W | — | FG-SEATTLE-SW1 port26 (port28) | 7.4.5 | Working normally |
Access points1010 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-SEATTLE-AP1 | FP231F | — | — | — | — | FG-SEATTLE-SW1 port3 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP10 | FP231F | — | — | — | — | FG-SEATTLE-SW1 port6 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP2 | FP231F | — | — | — | — | FG-SEATTLE-SW2 port3 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP3 | FP231F | — | — | — | — | FG-SEATTLE-SW3 port3 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP4 | FP231F | — | — | — | — | FG-SEATTLE-SW1 port4 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP5 | FP231F | — | — | — | — | FG-SEATTLE-SW2 port4 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP6 | FP231F | — | — | — | — | FG-SEATTLE-SW3 port4 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP7 | FP231F | — | — | — | — | FG-SEATTLE-SW1 port5 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP8 | FP231F | — | — | — | — | FG-SEATTLE-SW2 port5 | 7.4.3 | Working normally | |
| FG-SEATTLE-AP9 | FP231F | — | — | — | — | FG-SEATTLE-SW3 port5 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.11.10.0/24 | 10.11.10.1 | 255.255.255.0 /24 | 10.11.10.20 – 10.11.10.250 231 addresses · 25 in use · lease 8 hours | |
| 20 | voice | 10.11.20.0/24 | 10.11.20.1 | 255.255.255.0 /24 | 10.11.20.20 – 10.11.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.11.30.0/24 | 10.11.30.1 | 255.255.255.0 /24 | 10.11.30.20 – 10.11.30.250 231 addresses · 0 in use · lease 7 days · 7 reserved | |
| 40 | printers | 10.11.40.0/24 | 10.11.40.1 | 255.255.255.0 /24 | 10.11.40.100 – 10.11.40.199 100 addresses · 0 in use · lease 7 days · 2 reserved | |
| 50 | cameras | 10.11.50.0/24 | 10.11.50.1 | 255.255.255.0 /24 | 10.11.50.20 – 10.11.50.250 231 addresses · 1 in use · lease 7 days | |
| 90 | iot | 10.11.90.0/24 | 10.11.90.1 | 255.255.255.0 /24 | 10.11.90.100 – 10.11.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.11.0/24 | 10.255.11.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 16 | 12 Label printer / scanner · 3 Computer · 1 Network gear |
| 20 | voice | 3 | 3 Phone (VoIP) |
| 30 | servers | 7 | 6 Storage / server · 1 UPS / power |
| 40 | printers | 1 | 1 Printer |
| 50 | cameras | 1 | 1 Camera |
| 90 | iot | 5 | 2 Label printer / scanner · 2 IoT / industrial (by network) · 1 IoT / industrial |
| FortiLink | FortiLink | 3 | 3 Network gear |
| 10 | users | 10 | 10 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.
3 switches · 35 ports in use · 49 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 closet3 closets35 of 84 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Seattle | Closet 1 FG-SEATTLE-SW1 | 14 / 28 (50%) | 12 | 12 | 62 / 370 W (17%) 308 W headroom | |
| Seattle | Closet 2 FG-SEATTLE-SW2 | 11 / 28 (39%) | 14 | 14 | 35 / 370 W (9%) 335 W headroom | |
| Seattle | Closet 3 FG-SEATTLE-SW3 | 10 / 28 (36%) | 15 | 15 | 54 / 370 W (14%) 316 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-SEATTLE-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 62 / 370 W · 2 fiber ports · 40 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-SEATTLE-AP1 FortiAP | 10 users | 10.11.10.20 · 00:11:22:0b:00:00 2 Wi-Fi clients list | 12.6 W class 4 | |
| port4 | Up | FG-SEATTLE-AP4 FortiAP | 10 users | 10.11.10.23 · 00:11:22:0b:00:03 1 Wi-Fi client list | 10.6 W class 4 | |
| port5 | Up | FG-SEATTLE-AP7 FortiAP | 10 users | 10.11.10.26 · 00:11:22:0b:00:06 1 Wi-Fi client list | 12.4 W class 4 | |
| port6 | Up | FG-SEATTLE-AP10 FortiAP | 10 users | 10.11.10.29 · 00:11:22:0b:00:09 1 Wi-Fi client list | 11.9 W class 4 | |
| port13 | Up | NL-SEA-PC011 | 10 users | 10.11.10.120 · d0:43:1e:0b:0a:01 | ||
| port14 | Up | NL-SEA-LT012 | 10 users | 10.11.10.121 · d0:43:1e:0b:0a:02 | ||
| port15 | Up | NL-SEA-PC013 | 10 users | 10.11.10.122 · d0:43:1e:0b:0a:03 | ||
| port16 | Up | NL-SEA-PH01 phone | 20 voice | 10.11.20.20 · 00:04:f2:0b:14:01 | 3.9 W class 2 | |
| port17 | Up | NL-SEA-PH02 phone | 20 voice | 10.11.20.21 · 00:04:f2:0b:14:02 | 3.2 W class 2 | |
| port18 | Up | PRN-SEA-01 | 40 printers | 10.11.40.20 · 3c:2a:f4:0b:28:01 | ||
| port19 | Up | CAM-DOCK-01 | 50 cameras | 10.11.50.20 · 00:40:8c:0b:32:01 | 7.8 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00110001 | ||||
| port25 | Up | ↔ FG-SEATTLE-SW2 port28 trunk S124FF11020001-0 | Fiber 10G-SR | |||
| port26 | Up | ↔ FG-SEATTLE-SW3 port28 trunk S124FF11030001-0 | Fiber 10G-SR |
Free ports: port1–2, port7–12, port20–23, port27–28
S124FF11010001 · FortiSwitchOS 7.4.5
FG-SEATTLE-SW2 FortiSwitch 124F-FPOE · Closet 211 in use · 17 free · PoE 35 / 370 W · 1 fiber port · 44 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-SEATTLE-AP2 FortiAP | 10 users | 10.11.10.21 · 00:11:22:0b:00:01 2 Wi-Fi clients list | 11.7 W class 4 | |
| port4 | Up | FG-SEATTLE-AP5 FortiAP | 10 users | 10.11.10.24 · 00:11:22:0b:00:04 1 Wi-Fi client list | 12.2 W class 4 | |
| port5 | Up | FG-SEATTLE-AP8 FortiAP | 10 users | 10.11.10.27 · 00:11:22:0b:00:07 1 Wi-Fi client list | 10.9 W class 4 | |
| port7 | Up | DC01 | 30 servers | 10.11.30.2 · f8:bc:12:4e:e5:24 | ||
| port8 | Up | FILE01 | 30 servers | 10.11.30.3 · f8:bc:12:62:f7:01 | ||
| port9 | Up | WMS01 | 30 servers | 10.11.30.4 · f8:bc:12:06:60:17 | ||
| port10 | Up | BACKUP01 | 30 servers | 10.11.30.5 · c4:cb:e1:0b:57:d6 | ||
| port11 | Up | IPERF01 | 30 servers | 10.11.30.6 · f8:bc:12:84:02:9c | ||
| port12 | Up | NAS01 | 30 servers | 10.11.30.7 · 00:11:32:46:ca:8b | ||
| port13 | Up | UPS-MDF | 30 servers | 10.11.30.8 · 00:c0:b7:4b:a1:80 | ||
| port28 | Up | ↔ FG-SEATTLE-SW1 port25 trunk S124FF11010001-0 | Fiber 10G-SR |
Free ports: port1–2, port6, port14–27
S124FF11020001 · FortiSwitchOS 7.4.5
FG-SEATTLE-SW3 FortiSwitch 124F-FPOE · Closet 310 in use · 18 free · PoE 54 / 370 W · 1 fiber port · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-SEATTLE-AP3 FortiAP | 10 users | 10.11.10.22 · 00:11:22:0b:00:02 1 Wi-Fi client list | 12.6 W class 4 | |
| port4 | Up | FG-SEATTLE-AP6 FortiAP | 10 users | 10.11.10.25 · 00:11:22:0b:00:05 1 Wi-Fi client list | 12.2 W class 4 | |
| port5 | Up | FG-SEATTLE-AP9 FortiAP | 10 users | 10.11.10.28 · 00:11:22:0b:00:08 1 Wi-Fi client list | 12.0 W class 4 | |
| port7 | Up | PAGE-WHSE | 20 voice | 10.11.20.2 · 00:22:ee:41:1b:c5 | 6.4 W class 3 | |
| port9 | Up | DOOR-DOCK1 | 90 iot | 10.11.90.2 · 00:06:8e:a7:42:df | 4.2 W class 2 | |
| port10 | Up | DOOR-DOCK2 | 90 iot | 10.11.90.3 · 00:06:8e:11:f7:a9 | 4.2 W class 2 | |
| port11 | Up | ENV-FREEZER | 90 iot | 10.11.90.4 · b8:27:eb:dd:88:f2 | 1.9 W class 1 | |
| port14 | Up | DOCK-SEA-01 | 90 iot | 10.11.90.30 · 00:07:4d:a0:64:e8 | ||
| port15 | Up | DOCK-SEA-02 | 90 iot | 10.11.90.31 · 00:07:4d:14:b3:f9 | ||
| port28 | Up | ↔ FG-SEATTLE-SW1 port26 trunk S124FF11010001-0 | Fiber 10G-SR |
Free ports: port1–2, port6, port8, port12–13, port16–27
S124FF11030001 · FortiSwitchOS 7.4.5
On-site contacts
- Morgan Ellis · (211) 555-1011 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 8/17/2022 to 8/17/2027 · 268 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.21 /29
- Gateway
- 203.0.113.17
- Circuit ID
- NL-111
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 10/17/2024 to 10/17/2027 · 329 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.21 /29
- Gateway
- 198.51.100.17
- Circuit ID
- NL-112
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary3 static routes · BGP · 1 neighbour · OSPF 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.0.0.0/8 | Static | blackhole (dropped) |
| 10.1.0.0/16 | OSPF | to-chicago → Chicago |
| 10.2.0.0/16 | OSPF | to-chicago → Chicago |
| 10.3.0.0/16 | OSPF | to-chicago → Chicago |
| 10.4.0.0/16 | OSPF | to-chicago → Chicago |
| 10.5.0.0/16 | OSPF | to-chicago → Chicago |
| 10.6.0.0/16 | OSPF | to-chicago → Chicago |
| 10.7.0.0/16 | OSPF | to-chicago → Chicago |
| 10.8.0.0/16 | OSPF | to-chicago → Chicago |
| 10.9.0.0/16 | OSPF | to-chicago → Chicago |
| 10.10.0.0/16 | OSPF | to-chicago → Chicago |
| 10.11.10.0/24 | Connected | users local network |
| 10.11.20.0/24 | Connected | voice local network |
| 10.11.30.0/24 | Connected | servers local network |
| 10.11.40.0/24 | Connected | printers local network |
| 10.11.50.0/24 | Connected | cameras local network |
| 10.11.90.0/24 | Connected | iot local network |
| 10.12.0.0/16 | OSPF | to-chicago → Chicago |
| 10.13.0.0/16 | OSPF | to-chicago → Chicago |
| 10.14.0.0/16 | OSPF | to-chicago → Chicago |
| 10.16.0.0/16 | OSPF | to-chicago → Chicago |
| 10.17.0.0/16 | OSPF | to-chicago → Chicago |
| 10.19.0.0/16 | BGP | to-chicago → Chicago |
| 10.20.0.0/16 | BGP | to-chicago → Chicago |
| 10.255.11.0/24 | Connected | fortilink local network |
| 172.16.0.0/12 | Static | blackhole (dropped) |
| 192.168.0.0/16 | Static | blackhole (dropped) |
| 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.6 | 1 | 0 |
| 2026-11-22 | Example Fiber | 8.7 | 1.4 | 0 |
| 2026-11-21 | Metro Cable | 10.2 | 1.2 | 0.2 |
| 2026-11-21 | Example Fiber | 9.6 | 1 | 0.5 |
| 2026-11-20 | Metro Cable | 8.7 | 1.1 | 0 |
| 2026-11-20 | Example Fiber | 8.5 | 1.4 | 0 |
| 2026-11-19 | Metro Cable | 10.9 | 1.4 | 0 |
| 2026-11-19 | Example Fiber | 9 | 1.2 | 0.2 |
| 2026-11-18 | Metro Cable | 9.5 | 1.5 | 0 |
| 2026-11-18 | Example Fiber | 8.7 | 1 | 0 |
| 2026-11-17 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-17 | Example Fiber | 8 | 1.2 | 0 |
| 2026-11-16 | Metro Cable | 9.2 | 1.6 | 0 |
| 2026-11-16 | Example Fiber | 8.1 | 1.7 | 0 |
| 2026-11-15 | Metro Cable | 9.8 | 1.6 | 0 |
| 2026-11-15 | Example Fiber | 7.7 | 0.9 | 0 |
| 2026-11-14 | Metro Cable | 10.1 | 2 | 0.2 |
| 2026-11-14 | Example Fiber | 9.3 | 1.3 | 0.2 |
| 2026-11-13 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-13 | Example Fiber | 8.5 | 1 | 0.2 |
| 2026-11-12 | Metro Cable | 9.3 | 1.8 | 0 |
| 2026-11-12 | Example Fiber | 8.3 | 0.8 | 0.2 |
| 2026-11-11 | Metro Cable | 10.2 | 1.2 | 0 |
| 2026-11-11 | Example Fiber | 8.1 | 1 | 0 |
| 2026-11-10 | Metro Cable | 9.6 | 1.8 | 0.2 |
| 2026-11-10 | Example Fiber | 9.5 | 1.6 | 0 |
| 2026-11-09 | Metro Cable | 10.6 | 1.5 | 0 |
| 2026-11-09 | Example Fiber | 9.1 | 1.7 | 0 |
| 2026-11-08 | Metro Cable | 10 | 1.2 | 0 |
| 2026-11-08 | Example Fiber | 8.6 | 1.2 | 0 |
| 2026-11-07 | Metro Cable | 10.1 | 1.1 | 0.2 |
| 2026-11-07 | Example Fiber | 8.2 | 1.3 | 0 |
| 2026-11-06 | Metro Cable | 8.8 | 1.5 | 0.2 |
| 2026-11-06 | Example Fiber | 8.1 | 1.5 | 0 |
| 2026-11-05 | Metro Cable | 9.8 | 1.1 | 0 |
| 2026-11-05 | Example Fiber | 8.7 | 1.8 | 0.2 |
| 2026-11-04 | Metro Cable | 9.5 | 1.2 | 0.2 |
| 2026-11-04 | Example Fiber | 8.6 | 1.7 | 0 |
| 2026-11-03 | Metro Cable | 9.1 | 1.9 | 0 |
| 2026-11-03 | Example Fiber | 8 | 1.4 | 0 |
| 2026-11-02 | Metro Cable | 10.4 | 0.9 | 0 |
| 2026-11-02 | Example Fiber | 8.7 | 1.1 | 0 |
| 2026-11-01 | Metro Cable | 10.3 | 0.8 | 0.2 |
| 2026-11-01 | Example Fiber | 9 | 1.2 | 0.2 |
| 2026-10-31 | Metro Cable | 9.8 | 0.9 | 0 |
| 2026-10-31 | Example Fiber | 7.7 | 1.3 | 0.2 |
| 2026-10-30 | Metro Cable | 9.5 | 1.4 | 0 |
| 2026-10-30 | Example Fiber | 9.1 | 1.3 | 0 |
| 2026-10-29 | Metro Cable | 10.3 | 1.3 | 0.2 |
| 2026-10-29 | Example Fiber | 9.2 | 1.4 | 0.2 |
| 2026-10-28 | Metro Cable | 8.7 | 1.4 | 0 |
| 2026-10-28 | Example Fiber | 8.9 | 1.1 | 0 |
| 2026-10-27 | Metro Cable | 9.4 | 1.6 | 0 |
| 2026-10-27 | Example Fiber | 8.8 | 1.3 | 0.2 |
| 2026-10-26 | Metro Cable | 9.3 | 1.6 | 0 |
| 2026-10-26 | Example Fiber | 8.6 | 2 | 0 |
| 2026-10-25 | Metro Cable | 10.4 | 1.2 | 0.5 |
| 2026-10-25 | Example Fiber | 8.2 | 1.2 | 0.2 |
| 2026-10-24 | Metro Cable | 9 | 1.3 | 0 |
| 2026-10-24 | Example Fiber | 7.8 | 1.1 | 0 |
| 2026-10-23 | Metro Cable | 10.7 | 1.7 | 0 |
| 2026-10-23 | Example Fiber | 8.6 | 1.3 | 0 |
Tunnel stability – last 7 days
2 tunnels · 1 up on every run in the last 7 days.
| Tunnel | Times it went down | Up |
|---|---|---|
| to-chicago-b | 1 | 99% |
Configuration & routing changes – last 30 days 3
| When | Type | What | Detail |
|---|---|---|---|
| Nov 21 9:35 PM | Config | DHCP server 1 | dns-server1: 10.1.30.11 → 10.1.30.12 |
| Nov 9 9:44 AM | Config | Admin netops-21 | trusthost1: 0.0.0.0 0.0.0.0 → 10.1.30.0 255.255.255.0 |
| Oct 29 4:55 PM | Config | DHCP server 1 | dns-server1: 10.1.30.11 → 10.1.30.12 |
New and moved devices – last 30 days 4
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 20 4:36 PM | Device movedWi-Fi | Device moved 90:75:de:0b:aa:09 | 10.11.10.88 FG-SEATTLE-SW3 port9 → FG-SEATTLE-SW3 port5 |
| Nov 20 2:26 PM | New deviceWired | New device f8:bc:12:4e:e5:24 | 10.11.30.2 DC01 on FG-SEATTLE-SW2 port7 |
| Nov 13 12:09 PM | New deviceWi-Fi | New device 90:75:de:0b:aa:03 | 10.11.10.82 on FG-SEATTLE-SW3 port3 |
| Nov 9 11:59 AM | Device movedWired | Device moved f8:bc:12:62:f7:01 | 10.11.30.3 FG-SEATTLE-SW2 port12 → FG-SEATTLE-SW2 port8 |
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
- Redundancy reduced1
- ●aggregate member not running
- IPsec aggregate to-chicago: to-chicago is up but not in the running aggregate (1 of 2 members running) – including its first, preferred member
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system ipsec-aggregateconfig system ipsec-aggregate edit "to-chicago" set member "to-chicago" "to-chicago-b" set algorithm redundant next enddiagnose sys ipsec-aggregate listbundle=to-chicago algo=redundant member=1 tunnel=to-chicago-b weight=10get vpn ipsec tunnel summary'to-chicago' 203.0.113.11:0 selectors(total,up): 1/1 rx(pkt,err): 62128/0 tx(pkt,err): 64790/0 'to-chicago-b' 198.51.100.11:0 selectors(total,up): 1/1 rx(pkt,err): 62278/0 tx(pkt,err): 64982/0How to fix
These tunnels are up, but they are not in the running aggregate – so the FortiGate cannot send anything through them (it still receives, which is what one-way traffic looks like). The configuration is right; the running state is stale. It happens after a live aggregate or one of its tunnels is edited (members, weights, algorithm): a tunnel only joins again the next time it renegotiates.
- Renegotiate ONE of the missing tunnels (below). Only that tunnel drops, for a few seconds – start with one that carries nothing.
- Look at the running aggregate again: the tunnel should now be listed.
- Repeat for each tunnel still missing. If one does not come back, stop and open a Fortinet support case with the two outputs.
- After any later change to an aggregate or its tunnels: renegotiate and check again.
Routes that point at this aggregate: 10.1.0.0/16, 10.2.0.0/16, 10.3.0.0/16, 10.4.0.0/16, 10.5.0.0/16, 10.6.0.0/16, 10.7.0.0/16, 10.8.0.0/16
# on the PRIMARY unit (get system status | grep -i 'HA mode') diagnose vpn ike gateway flush name to-chicago # safe to share (no keys): diagnose sys ipsec-aggregate list get vpn ipsec tunnel summary - Configuration5
- ●auto-negotiate off
- 1 aggregate member(s) with phase 2 auto-negotiate off – they stay down until traffic needs them, so a failover waits for the tunnel to negotiate: to-chicago-b
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show vpn ipsec phase2-interface (no 'set auto-negotiate enable' line = off)config vpn ipsec phase2-interface edit "to-chicago-b" set phase1name "to-chicago-b" next endHow to fix
These backup tunnels only negotiate phase 2 when traffic needs them. When the primary fails, traffic waits for the backup to come up (and a NATed end like Azure may never start it), and this page can't tell an idle backup from a broken one. Enable auto-negotiate at both ends.
- Paste the block below on this FortiGate (it only changes the listed phase 2s).
- Do the same at the other end of each tunnel.
- Check: get vpn ipsec tunnel summary – each should show selectors 1/1.
config vpn ipsec phase2-interface edit "to-chicago-b" set auto-negotiate enable next end get vpn ipsec tunnel summary - ●aggregate-member flag
- in an aggregate with aggregate-member disabled: to-chicago (to-chicago); to-chicago-b (to-chicago)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show vpn ipsec phase1-interfaceconfig vpn ipsec phase1-interface edit "to-chicago" set interface "wan1" set remote-gw 203.0.113.11 next end config vpn ipsec phase1-interface edit "to-chicago-b" set interface "wan2" set remote-gw 198.51.100.11 next endshow system ipsec-aggregateconfig system ipsec-aggregate edit "to-chicago" set member "to-chicago" "to-chicago-b" set algorithm redundant next endHow to fix
A tunnel listed in an IPsec aggregate should have aggregate-member enable; a tunnel with that flag and no aggregate is left out of the bundle. Either way the FortiGate may send on a member the other end does not expect.
- Enable aggregate-member on every tunnel that is in an aggregate.
- Clear the flag on a tunnel that is not in any aggregate, or add it to the aggregate at both ends.
config vpn ipsec phase1-interface edit "to-chicago" set aggregate-member enable next edit "to-chicago-b" set aggregate-member enable next end show system ipsec-aggregate - ●weights on a redundant aggregate
- IPsec aggregate to-chicago is 'redundant' and has weights set (to-chicago-b 10). In redundant mode the first member that is up carries the traffic – the order of 'set member' decides, not the weight. First member: to-chicago
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system ipsec-aggregateconfig system ipsec-aggregate edit "to-chicago" set member "to-chicago" "to-chicago-b" set algorithm redundant next endshow vpn ipsec phase1-interfaceconfig vpn ipsec phase1-interface edit "to-chicago-b" set aggregate-weight 10 next endHow to fix
Fortinet documents 'redundant' as 'use the first tunnel that is up'; aggregate-weight belongs to weighted-round-robin. Weights here suggest the heaviest tunnel was expected to be preferred – what decides is the order of the members, and it has to be the same path order at both ends.
- Put the tunnel on the main circuit first in 'set member' – at both ends, in the same window.
- Set the weights back to 1, so the configuration says what it does.
- Renegotiate the tunnels and check the running aggregate – editing a live aggregate can leave tunnels out of it.
# on the PRIMARY unit (get system status | grep -i 'HA mode') config system ipsec-aggregate edit "to-chicago" set member "to-chicago" "to-chicago-b" # current order – main circuit first next end config vpn ipsec phase1-interface edit "to-chicago-b" set aggregate-weight 1 next end diagnose vpn ike gateway flush name to-chicago diagnose vpn ike gateway flush name to-chicago-b diagnose sys ipsec-aggregate list - ●aggregate not paired
- IPsec aggregate to-chicago: Chicago has no IPsec aggregate whose members all end here, so the order, mode and missing-member checks did not run
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system ipsec-aggregateconfig system ipsec-aggregate edit "to-chicago" set member "to-chicago" "to-chicago-b" set algorithm redundant next endHow to fix
The both-ends checks (order, mode, missing member) only run when every member of an aggregate ends at one known site. When they do not, or when both members leave on the same local WAN, those checks are skipped or treat the members as two paths by the far circuit – this note says so.
- If the members should all go to one site, fix the remote gateways so they map.
- If two members share a WAN on purpose, the path order is still by the far end's circuit.
# safe to share (no keys): show system ipsec-aggregate show vpn ipsec phase1-interface get vpn ipsec tunnel summary - ●IPsec settings differ at the two ends
- Chicago's to-seattle-b ↔ Seattle's to-chicago-b: phase 2 auto-negotiate: enable vs (default)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show vpn ipsec phase1-interfaceconfig vpn ipsec phase1-interface edit "to-seattle-b" set remote-gw 198.51.100.21 set ike-version 2 set proposal aes256-sha256 set dhgrp 14 next end config vpn ipsec phase1-interface edit "to-chicago-b" set remote-gw 198.51.100.11 set ike-version 2 set proposal aes256-sha256 set dhgrp 14 next endHow to fix
The two ends of this path disagree on phase 1 or phase 2 (IKE version, proposal, DH group, dead-peer detection, key life, auto-negotiate, or the phase-2 selectors). `show` omits a setting left at the FortiOS default; a named selector cannot be expanded to its subnets here. A value written on one end and absent on the other is still a mismatch. When the tunnel is one-way and the aggregates already agree, this is the next place to look.
- Compare the settings below at both ends.
- Change both ends together in a maintenance window – a mismatch takes the tunnel down.
- Named address objects are not collected; check those by hand if a selector is a name on one end.
# this end: show vpn ipsec phase1-interface | grep -f to-chicago-b show vpn ipsec phase2-interface | grep -f to-chicago-b # on Chicago: show vpn ipsec phase1-interface | grep -f to-seattle-b show vpn ipsec phase2-interface | grep -f to-seattle-b - Monitoring & housekeeping3
- ●health check
- SD-WAN health check 'Monitor' can't reach its target on any WAN – check its server setting
How to fix
The SD-WAN health check 'Monitor' probes 10.1.30.10 over the internet links, and that address doesn't answer on any of them. A private (10.x) address can only be reached over a tunnel, so this check can never pass. Any SD-WAN rule using it is effectively switched off.
- If nothing depends on it: delete the SD-WAN rule that uses it, then the health check.
- If it's meant to watch a server across the VPN: make the IPsec tunnels its members instead of the WANs.
show system sdwan config system sdwan config health-check delete "Monitor" end end - ●health check probes a private address
- SD-WAN health check(s) probe a private address over WAN members – that target is not on the internet, so the check stays dead and any rule that uses it never fails over: Monitor → 10.1.30.10
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system sdwanMonitor: server 10.1.30.10How to fix
An SD-WAN health check that probes a private address over WAN members can never succeed on the internet path. Rules that depend on it never see the link as up.
- Point the health check at a public address (or a well-known DNS/HTTP target).
- Or move the check onto IPsec tunnel members if it is meant to watch a remote private server.
- Remove the check if nothing uses it.
show system sdwan diagnose sys sdwan health-check - ●Certificate 21 days
- Certificate: Northline-Mgmt expires in 21 days (Dec 13 2026)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get vpn certificate local detailsNorthline-Mgmt: 2026-12-13How to fix
The certificate 'Northline-Mgmt' on this FortiGate expires 2026-12-13. Anything using it – SSL VPN, the admin GUI, an IPsec tunnel with certificate authentication – fails after that date.
- Find what uses it (below).
- Issue a new certificate from your CA, import it on the FortiGate.
- Point the services at the new certificate, then delete the old one.
get vpn certificate local details Northline-Mgmt show vpn ssl settings show system global | grep -f cert show vpn ipsec phase1-interface | grep -f certificate
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 Seattle floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment14 devices1 with support ended
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-SEATTLE FortiGate · FortiGate 90G | FGDEMO00110001 tag NL-0011 | Seattle Northline | 2024-08-24 2.2 years old PO PO-55512 · Example Reseller | Standard 2027-11-24 contract NL-SUP-11 warranty 2025-08-24 passed | 2035-06-30 end of order 2030-06-30 | 2030 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF11010001 tag NL-11S01 | Seattle · Closet 1 · Rack 1 Network team | 2024-02-15 2.8 years old PO PO-56110 · Example Reseller | Standard 2029-03-01 contract NL-FSW warranty 2029-03-01 | 2033-03-31 end of order 2028-03-31 | 2030 → FortiSwitch 124G-FPOE spare: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-SW2 FortiSwitch · FortiSwitch 124F-FPOE | S124FF11020001 tag NL-11S02 | Seattle · Closet 2 · Rack 2 Network team | 2021-02-15 5.8 years old PO PO-56111 · 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: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-SW3 FortiSwitch · FortiSwitch 124F-FPOE | S124FF11030001 tag NL-11S03 | Seattle · Closet 3 · Rack 3 Network team | 2022-02-15 4.8 years old PO PO-56112 · Example Reseller | Standard 2027-03-01 contract NL-FSW warranty 2027-03-01 | 2033-03-31 end of order 2028-03-31 | 2028 → FortiSwitch 124G-FPOE spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-AP1 FortiAP · FAP231F | FP231F11010001 tag NL-11A01 | Seattle · Ceiling, zone 1 Network team | 2024-05-10 2.5 years old PO PO-57110 · Example Reseller | Standard 2029-06-01 contract NL-FAP warranty 2029-06-01 | 2033-06-30 end of order 2028-06-30 | 2030 → FortiAP 431G spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-AP2 FortiAP · FAP231F | FP231F11020001 tag NL-11A02 | Seattle · Ceiling, zone 2 Network team | 2022-05-10 4.5 years old PO PO-57111 · 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-SEATTLE-AP3 FortiAP · FAP231F | FP231F11030001 tag NL-11A03 | Seattle · Ceiling, zone 3 Network team | 2023-05-10 3.5 years old PO PO-57112 · 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. |
| FG-SEATTLE-AP4 FortiAP · FAP231F | FP231F11040001 tag NL-11A04 | Seattle · Ceiling, zone 4 Network team | 2024-05-10 2.5 years old PO PO-57113 · Example Reseller | Standard 2029-06-01 contract NL-FAP warranty 2029-06-01 | 2033-06-30 end of order 2028-06-30 | 2030 → FortiAP 431G spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-AP5 FortiAP · FAP231F | FP231F11050001 tag NL-11A05 | Seattle · Ceiling, zone 5 Network team | 2022-05-10 4.5 years old PO PO-57114 · 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-SEATTLE-AP6 FortiAP · FAP231F | FP231F11060001 tag NL-11A06 | Seattle · Ceiling, zone 6 Network team | 2023-05-10 3.5 years old PO PO-57115 · 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. |
| FG-SEATTLE-AP7 FortiAP · FAP231F | FP231F11070001 tag NL-11A07 | Seattle · Ceiling, zone 7 Network team | 2024-05-10 2.5 years old PO PO-57116 · Example Reseller | Standard 2029-06-01 contract NL-FAP warranty 2029-06-01 | 2033-06-30 end of order 2028-06-30 | 2030 → FortiAP 431G spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-SEATTLE-AP8 FortiAP · FAP231F | FP231F11080001 tag NL-11A08 | Seattle · Ceiling, zone 8 Network team | 2022-05-10 4.5 years old PO PO-57117 · 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-SEATTLE-AP9 FortiAP · FAP231F | FP231F11090001 tag NL-11A09 | Seattle · Ceiling, zone 9 Network team | 2023-05-10 3.5 years old PO PO-57118 · 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. |
| FG-SEATTLE-AP10 FortiAP · FAP231F | FP231F11100001 tag NL-11A10 | Seattle · Ceiling, zone 10 Network team | 2024-05-10 2.5 years old PO PO-57119 · Example Reseller | Standard 2029-06-01 contract NL-FAP warranty 2029-06-01 | 2033-06-30 end of order 2028-06-30 | 2030 → 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-111 | 500/500 | 15 ms collector ping | 2022-08-17 | 2027-08-17 give notice within 178 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-112 | 300/30 | 12 ms collector ping | 2024-10-17 | 2027-10-17 give notice within 269 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.11.10.0/24 | 10.11.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Seattle network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.11.20.0/24 | 10.11.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Seattle network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.11.30.0/24 | 10.11.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Seattle network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.11.40.0/24 | 10.11.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Seattle network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.11.50.0/24 | 10.11.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Seattle network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.11.90.0/24 | 10.11.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Seattle 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.