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-CHICAGO | FortiGate-200F | 7.4.8 | 15% | 50% | 31,438 | 35% · wan1 | — | Working normally |
Switches66 · 0 need a look · PoE 164 of 2220 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-CHICAGO-SW1 | FortiSwitch 124F-FPOE | 16 / 28 | 37 of 370 W | — | FG-CHICAGO-SW2 port25 (port25) | 7.4.5 | Working normally | |
| FG-CHICAGO-SW2 | FortiSwitch 124F-FPOE | 19 / 28 | 22 of 370 W | — | FG-CHICAGO-SW1 port25 (port25) | 7.4.5 | Working normally | |
| FG-CHICAGO-SW3 | FortiSwitch 124F-FPOE | 6 / 28 | 24 of 370 W | — | FG-CHICAGO-SW4 port28 (port25) | 7.4.5 | Working normally | |
| FG-CHICAGO-SW4 | FortiSwitch 124F-FPOE | 4 / 28 | 27 of 370 W | — | FG-CHICAGO-SW6 port28 (port25) | 7.4.5 | Working normally | |
| FG-CHICAGO-SW5 | FortiSwitch 124F-FPOE | 3 / 28 | 22 of 370 W | — | FG-CHICAGO-SW3 port26 (port28) | 7.4.5 | Working normally | |
| FG-CHICAGO-SW6 | FortiSwitch 124F-FPOE | 6 / 28 | 32 of 370 W | — | FG-CHICAGO-SW4 port25 (port28) | 7.4.5 | Working normally |
Access points1212 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-CHICAGO-AP1 | FP231F | — | — | — | — | FG-CHICAGO-SW1 port3 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP10 | FP231F | — | — | — | — | FG-CHICAGO-SW4 port4 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP11 | FP231F | — | — | — | — | FG-CHICAGO-SW5 port4 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP12 | FP231F | — | — | — | — | FG-CHICAGO-SW6 port4 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP2 | FP231F | — | — | — | — | FG-CHICAGO-SW2 port3 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP3 | FP231F | — | — | — | — | FG-CHICAGO-SW3 port3 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP4 | FP231F | — | — | — | — | FG-CHICAGO-SW4 port3 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP5 | FP231F | — | — | — | — | FG-CHICAGO-SW5 port3 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP6 | FP231F | — | — | — | — | FG-CHICAGO-SW6 port3 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP7 | FP231F | — | — | — | — | FG-CHICAGO-SW1 port4 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP8 | FP231F | — | — | — | — | FG-CHICAGO-SW2 port4 | 7.4.3 | Working normally | |
| FG-CHICAGO-AP9 | FP231F | — | — | — | — | FG-CHICAGO-SW3 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.1.10.0/24 | 10.1.10.1 | 255.255.255.0 /24 | 10.1.10.20 – 10.1.10.250 231 addresses · 18 in use · lease 8 hours | |
| 20 | voice | 10.1.20.0/24 | 10.1.20.1 | 255.255.255.0 /24 | 10.1.20.20 – 10.1.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.1.30.0/24 | 10.1.30.1 | 255.255.255.0 /24 | 10.1.30.20 – 10.1.30.250 231 addresses · 0 in use · lease 7 days · 13 reserved | |
| 40 | printers | 10.1.40.0/24 | 10.1.40.1 | 255.255.255.0 /24 | 10.1.40.100 – 10.1.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.1.50.0/24 | 10.1.50.1 | 255.255.255.0 /24 | 10.1.50.100 – 10.1.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.1.90.0/24 | 10.1.90.1 | 255.255.255.0 /24 | 10.1.90.100 – 10.1.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.1.0/24 | 10.255.1.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 7 | 6 Computer · 1 Network gear |
| 20 | voice | 2 | 2 Phone (VoIP) |
| 30 | servers | 13 | 11 Storage / server · 2 UPS / power |
| 40 | printers | 1 | 1 Printer |
| 50 | cameras | 1 | 1 Camera |
| 90 | iot | 3 | 2 IoT / industrial (by network) · 1 IoT / industrial |
| FortiLink | FortiLink | 6 | 6 Network gear |
| 10 | users | 12 | 12 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.
6 switches · 54 ports in use · 114 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 closet6 closets54 of 168 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Chicago | Closet 1 FG-CHICAGO-SW1 | 16 / 28 (57%) | 12 | 12 | 37 / 370 W (10%) 333 W headroom | |
| Chicago | Closet 2 FG-CHICAGO-SW2 | 19 / 28 (68%) | 9 | 9 | 22 / 370 W (6%) 348 W headroom | |
| Chicago | Closet 3 FG-CHICAGO-SW3 | 6 / 28 (21%) | 22 | 22 | 24 / 370 W (6%) 346 W headroom | |
| Chicago | Closet 4 FG-CHICAGO-SW4 | 4 / 28 (14%) | 22 | 22 | 27 / 370 W (7%) 343 W headroom | |
| Chicago | Closet 5 FG-CHICAGO-SW5 | 3 / 28 (11%) | 22 | 22 | 22 / 370 W (6%) 348 W headroom | |
| Chicago | Closet 6 FG-CHICAGO-SW6 | 6 / 28 (21%) | 19 | 19 | 32 / 370 W (9%) 338 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-CHICAGO-SW1 FortiSwitch 124F-FPOE · Closet 116 in use · 12 free · PoE 37 / 370 W · 2 fiber ports · 40 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHICAGO-AP1 FortiAP | 10 users | 10.1.10.20 · 00:11:22:01:00:00 | 11.9 W class 4 | |
| port4 | Up | FG-CHICAGO-AP7 FortiAP | 10 users | 10.1.10.26 · 00:11:22:01:00:06 | 10.0 W class 4 | |
| port13 | Up | NL-CHI-PC011 | 10 users | 10.1.10.120 · d0:43:1e:01:0a:01 | ||
| port14 | Up | NL-CHI-LT012 | 10 users | 10.1.10.121 · d0:43:1e:01:0a:02 | ||
| port15 | Up | NL-CHI-PC013 | 10 users | 10.1.10.122 · d0:43:1e:01:0a:03 | ||
| port16 | Up | NL-CHI-LT014 | 10 users | 10.1.10.123 · d0:43:1e:01:0a:04 | ||
| port17 | Up | NL-CHI-PC015 | 10 users | 10.1.10.124 · d0:43:1e:01:0a:05 | ||
| port18 | Up | NL-CHI-LT016 | 10 users | 10.1.10.125 · d0:43:1e:01:0a:06 | ||
| port19 | Up | NL-CHI-PH01 phone | 20 voice | 10.1.20.20 · 00:04:f2:01:14:01 | 4.0 W class 2 | |
| port20 | Up | NL-CHI-PH02 phone | 20 voice | 10.1.20.21 · 00:04:f2:01:14:02 | 4.2 W class 2 | |
| port21 | Up | PRN-CHI-01 | 40 printers | 10.1.40.20 · 3c:2a:f4:01:28:01 | ||
| port22 | Up | CAM-LOBBY-01 | 50 cameras | 10.1.50.20 · 00:40:8c:01:32:01 | 6.8 W class 3 | |
| port25 | Up | ↔ FG-CHICAGO-SW2 port25 trunk S124FF01020001-0 | DAC 10G-CR | |||
| port26 | Up | ↔ FG-CHICAGO-SW2 port26 trunk S124FF01020001-0 | DAC 10G-CR | |||
| port27 | Up | FortiGate · FortiLink trunk _FlInK1_MLAG0_ | Fiber 10G-SR | |||
| port28 | Up | ↔ FG-CHICAGO-SW3 port27 trunk S124FF01030001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–12, port23–24
S124FF01010001 · FortiSwitchOS 7.4.5
FG-CHICAGO-SW2 FortiSwitch 124F-FPOE · Closet 219 in use · 9 free · PoE 22 / 370 W · 2 fiber ports · 42 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHICAGO-AP2 FortiAP | 10 users | 10.1.10.21 · 00:11:22:01:00:01 | 10.2 W class 4 | |
| port4 | Up | FG-CHICAGO-AP8 FortiAP | 10 users | 10.1.10.27 · 00:11:22:01:00:07 | 11.5 W class 4 | |
| port7 | Up | DC01 | 30 servers | 10.1.30.2 · f8:bc:12:14:72:61 | ||
| port8 | Up | DC02 | 30 servers | 10.1.30.3 · f8:bc:12:59:fc:e2 | ||
| port9 | Up | FILE01 | 30 servers | 10.1.30.4 · f8:bc:12:d3:89:7e | ||
| port10 | Up | SQL01 | 30 servers | 10.1.30.5 · f8:bc:12:b7:b9:e1 | ||
| port11 | Up | PRINT01 | 30 servers | 10.1.30.6 · f8:bc:12:a9:64:3f | ||
| port12 | Up | HV01 | 30 servers | 10.1.30.7 · f8:bc:12:5b:8b:7b | ||
| port13 | Up | HV02 | 30 servers | 10.1.30.8 · f8:bc:12:46:55:2d | ||
| port14 | Up | BACKUP01 | 30 servers | 10.1.30.9 · c4:cb:e1:35:d8:06 | ||
| port15 | Up | IPERF01 | 30 servers | 10.1.30.10 · f8:bc:12:dd:76:66 | ||
| port16 | Up | SAN01 | 30 servers | 10.1.30.11 · 00:11:32:fa:66:5e | ||
| port17 | Up | NAS01 | 30 servers | 10.1.30.12 · 00:11:32:d3:17:39 | ||
| port18 | Up | UPS-MDF | 30 servers | 10.1.30.13 · 00:c0:b7:f0:08:9f | ||
| port19 | Up | UPS-IDF2 | 30 servers | 10.1.30.14 · 00:c0:b7:7a:57:0e | ||
| port25 | Up | ↔ FG-CHICAGO-SW1 port25 trunk S124FF01010001-0 | DAC 10G-CR | |||
| port26 | Up | ↔ FG-CHICAGO-SW1 port26 trunk S124FF01010001-0 | DAC 10G-CR | |||
| port27 | Up | FortiGate · FortiLink trunk _FlInK1_MLAG0_ | Fiber 10G-SR | |||
| port28 | Up | ↔ FG-CHICAGO-SW3 port28 trunk S124FF01030001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–6, port20–24
S124FF01020001 · FortiSwitchOS 7.4.5
FG-CHICAGO-SW3 FortiSwitch 124F-FPOE · Closet 36 in use · 22 free · PoE 24 / 370 W · 4 fiber ports · 42 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHICAGO-AP3 FortiAP | 10 users | 10.1.10.22 · 00:11:22:01:00:02 | 13.9 W class 4 | |
| port4 | Up | FG-CHICAGO-AP9 FortiAP | 10 users | 10.1.10.28 · 00:11:22:01:00:08 | 10.1 W class 4 | |
| port25 | Up | ↔ FG-CHICAGO-SW4 port28 trunk S124FF01040001-0 | Fiber 10G-SR | |||
| port26 | Up | ↔ FG-CHICAGO-SW5 port28 trunk S124FF01050001-0 | Fiber 10G-SR | |||
| port27 | Up | ↔ FG-CHICAGO-SW1 port28 trunk S124FF01010001-0 | Fiber 10G-SR | |||
| port28 | Up | ↔ FG-CHICAGO-SW2 port28 trunk S124FF01020001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–24
S124FF01030001 · FortiSwitchOS 7.4.5
FG-CHICAGO-SW4 FortiSwitch 124F-FPOE · Closet 44 in use · 24 free · PoE 27 / 370 W · 2 fiber ports · 40 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHICAGO-AP4 FortiAP | 10 users | 10.1.10.23 · 00:11:22:01:00:03 | 13.6 W class 4 | |
| port4 | Up | FG-CHICAGO-AP10 FortiAP | 10 users | 10.1.10.29 · 00:11:22:01:00:09 | 13.6 W class 4 | |
| port25 | Up | ↔ FG-CHICAGO-SW6 port28 trunk S124FF01060001-0 | Fiber 10G-SR | |||
| port28 | Up | ↔ FG-CHICAGO-SW3 port25 trunk S124FF01030001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–24, port26–27
S124FF01040001 · FortiSwitchOS 7.4.5
FG-CHICAGO-SW5 FortiSwitch 124F-FPOE · Closet 53 in use · 25 free · PoE 22 / 370 W · 1 fiber port · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHICAGO-AP5 FortiAP | 10 users | 10.1.10.24 · 00:11:22:01:00:04 | 11.2 W class 4 | |
| port4 | Up | FG-CHICAGO-AP11 FortiAP | 10 users | 10.1.10.30 · 00:11:22:01:00:0a | 11.0 W class 4 | |
| port28 | Up | ↔ FG-CHICAGO-SW3 port26 trunk S124FF01030001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–27
S124FF01050001 · FortiSwitchOS 7.4.5
FG-CHICAGO-SW6 FortiSwitch 124F-FPOE · Closet 66 in use · 22 free · PoE 32 / 370 W · 1 fiber port · 41 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHICAGO-AP6 FortiAP | 10 users | 10.1.10.25 · 00:11:22:01:00:05 | 10.2 W class 4 | |
| port4 | Up | FG-CHICAGO-AP12 FortiAP | 10 users | 10.1.10.31 · 00:11:22:01:00:0b | 12.0 W class 4 | |
| port9 | Up | DOOR-LOBBY | 90 iot | 10.1.90.2 · 00:06:8e:9b:7b:79 | 4.2 W class 2 | |
| port10 | Up | DOOR-MDF | 90 iot | 10.1.90.3 · 00:06:8e:a5:ab:c3 | 4.2 W class 2 | |
| port11 | Up | ENV-MDF | 90 iot | 10.1.90.4 · b8:27:eb:a2:55:0f | 1.9 W class 1 | |
| port28 | Up | ↔ FG-CHICAGO-SW4 port25 trunk S124FF01040001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–8, port12–27
S124FF01060001 · FortiSwitchOS 7.4.5
On-site contacts
- Jordan Hale · (201) 555-1001 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 1/14/2025 to 1/14/2028 · 418 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.11 /29
- Gateway
- 203.0.113.9
- Circuit ID
- NL-011
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 3/15/2023 to 3/15/2028 · 479 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.11 /29
- Gateway
- 198.51.100.9
- Circuit ID
- NL-012
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Contract ISP3 · 9/22/2025 to 9/22/2026 · term ended, renews by itself
Provider status: Starlink ↗ · all on Service status
- FortiGate WAN IP
- 192.0.2.11 /29
- Gateway
- 192.0.2.9
- Circuit ID
- NL-013
- Bandwidth
- 100 / 20 Mbps
- Support #
- 800-555-0199
Contract ISP4 · 7/15/2025 to 7/15/2028 · 601 days left
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 192.0.2.81 /29
- Gateway
- 192.0.2.86
- Circuit ID
- NL-014
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary5 static routes · BGP · 6 neighbours · 2 policy routes · 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 wan3 internet wan4 internet · equal cost |
| 10.0.0.0/8 | Static | blackhole (dropped) |
| 10.1.10.0/24 | Connected | users local network |
| 10.1.20.0/24 | Connected | voice local network |
| 10.1.30.0/24 | Connected | servers local network |
| 10.1.40.0/24 | Connected | printers local network |
| 10.1.50.0/24 | Connected | cameras local network |
| 10.1.90.0/24 | Connected | iot local network |
| 10.2.0.0/16 | OSPF | to-houston → Houston to-houston-b → Houston · equal cost |
| 10.3.0.0/16 | OSPF | to-houston → Houston to-houston-b → Houston · equal cost |
| 10.4.0.0/16 | OSPF | to-detroit → Detroit to-detroit-b → Detroit · equal cost |
| 10.5.0.0/16 | OSPF | to-detroit → Detroit to-detroit-b → Detroit · equal cost |
| 10.6.0.0/16 | OSPF | to-charlotte → Charlotte to-charlotte-b → Charlotte · equal cost |
| 10.7.0.0/16 | OSPF | to-charlotte → Charlotte to-charlotte-b → Charlotte · equal cost |
| 10.8.0.0/16 | OSPF | to-dallas → Dallas to-dallas-b → Dallas · equal cost |
| 10.9.0.0/16 | OSPF | to-atlanta-b → Atlanta |
| 10.10.0.0/16 | OSPF | to-denver → Denver to-denver-b → Denver · equal cost |
| 10.11.0.0/16 | OSPF | to-seattle-b → Seattle |
| 10.12.0.0/16 | Static | to-newyork → New York |
| 10.13.0.0/16 | OSPF | to-losangeles → Los Angeles to-losangeles-b → Los Angeles · equal cost |
| 10.14.0.0/16 | OSPF | to-miami → Miami to-miami-b → Miami · equal cost |
| 10.16.0.0/16 | OSPF | to-minneapolis → Minneapolis to-minneapolis-b → Minneapolis · equal cost |
| 10.17.0.0/16 | OSPF | to-phoenix → Phoenix to-phoenix-b → Phoenix · equal cost |
| 10.19.0.0/16 | BGP | to-azure-east → Azure East to-azure-east-b → Azure East · equal cost |
| 10.20.0.0/16 | BGP | to-azure-west → Azure West to-azure-west-b → Azure West · equal cost |
| 10.255.1.0/24 | Connected | fortilink local network |
| 172.16.0.0/12 | Static | blackhole (dropped) |
| 192.0.2.0/24 | Static | wan1 |
| 192.0.2.8/29 | Connected | wan3 local network |
| 192.0.2.80/29 | Connected | wan4 local network |
| 192.168.0.0/16 | Static | blackhole (dropped) |
| 198.51.100.8/29 | Connected | wan2 local network |
| 203.0.113.8/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 | Starlink | 42.7 | 1.1 | 0 |
| 2026-11-22 | Metro Cable | 9.9 | 1.6 | 0 |
| 2026-11-22 | Example Fiber | 8.8 | 1 | 0 |
| 2026-11-21 | Starlink | 45.8 | 1.7 | 0 |
| 2026-11-21 | Metro Cable | 8.8 | 1.8 | 0 |
| 2026-11-21 | Example Fiber | 8.4 | 1.2 | 0 |
| 2026-11-20 | Starlink | 40.6 | 1.8 | 0 |
| 2026-11-20 | Metro Cable | 10.7 | 1.9 | 0 |
| 2026-11-20 | Example Fiber | 8.5 | 1.1 | 0 |
| 2026-11-19 | Starlink | 46.1 | 1.1 | 0 |
| 2026-11-19 | Metro Cable | 9.8 | 1.7 | 0 |
| 2026-11-19 | Example Fiber | 8.1 | 1.2 | 0.2 |
| 2026-11-18 | Starlink | 43.9 | 1.8 | 0 |
| 2026-11-18 | Metro Cable | 10.5 | 1.5 | 0 |
| 2026-11-18 | Example Fiber | 8.7 | 1.3 | 0 |
| 2026-11-17 | Starlink | 46.8 | 1 | 0 |
| 2026-11-17 | Metro Cable | 9.8 | 1.5 | 0.2 |
| 2026-11-17 | Example Fiber | 8.8 | 1.2 | 0 |
| 2026-11-16 | Starlink | 45.9 | 1.1 | 0 |
| 2026-11-16 | Metro Cable | 9.7 | 1.7 | 0 |
| 2026-11-16 | Example Fiber | 9.2 | 1.4 | 0 |
| 2026-11-15 | Starlink | 47.3 | 1.6 | 0 |
| 2026-11-15 | Metro Cable | 9.3 | 1.5 | 0 |
| 2026-11-15 | Example Fiber | 8.4 | 1.2 | 0 |
| 2026-11-14 | Starlink | 45.6 | 1.2 | 0.2 |
| 2026-11-14 | Metro Cable | 10.5 | 1.8 | 0 |
| 2026-11-14 | Example Fiber | 8.7 | 1.3 | 0 |
| 2026-11-13 | Starlink | 41.5 | 1.7 | 0 |
| 2026-11-13 | Metro Cable | 10.1 | 1.5 | 0.2 |
| 2026-11-13 | Example Fiber | 7.9 | 1.7 | 0 |
| 2026-11-12 | Starlink | 44.8 | 1.7 | 0 |
| 2026-11-12 | Metro Cable | 10.2 | 1.1 | 0 |
| 2026-11-12 | Example Fiber | 8.6 | 1.3 | 0 |
| 2026-11-11 | Starlink | 40.3 | 1.4 | 0 |
| 2026-11-11 | Metro Cable | 9.8 | 1.7 | 0 |
| 2026-11-11 | Example Fiber | 8.3 | 1.8 | 0 |
| 2026-11-10 | Starlink | 44.6 | 1.1 | 0.2 |
| 2026-11-10 | Metro Cable | 10.3 | 0.9 | 0 |
| 2026-11-10 | Example Fiber | 8.2 | 1.3 | 0 |
| 2026-11-09 | Starlink | 43.3 | 1.5 | 0 |
| 2026-11-09 | Metro Cable | 10.3 | 1.3 | 0 |
| 2026-11-09 | Example Fiber | 8.9 | 0.9 | 0 |
| 2026-11-08 | Starlink | 46.7 | 1.4 | 0 |
| 2026-11-08 | Metro Cable | 10.1 | 1.6 | 0.2 |
| 2026-11-08 | Example Fiber | 8.9 | 1.3 | 0 |
| 2026-11-07 | Starlink | 50.2 | 1.3 | 0 |
| 2026-11-07 | Metro Cable | 8.5 | 1.1 | 0 |
| 2026-11-07 | Example Fiber | 9.5 | 1.8 | 0 |
| 2026-11-06 | Starlink | 44 | 1.1 | 0 |
| 2026-11-06 | Metro Cable | 9.4 | 1.4 | 0.2 |
| 2026-11-06 | Example Fiber | 7.9 | 1.7 | 0 |
| 2026-11-05 | Starlink | 42.4 | 1.4 | 0 |
| 2026-11-05 | Metro Cable | 8.7 | 1.8 | 0.2 |
| 2026-11-05 | Example Fiber | 8.2 | 1.6 | 0 |
| 2026-11-04 | Starlink | 43.8 | 1.7 | 0 |
| 2026-11-04 | Metro Cable | 8.9 | 1.6 | 0 |
| 2026-11-04 | Example Fiber | 9 | 1.5 | 0 |
| 2026-11-03 | Starlink | 44.5 | 1.5 | 0 |
| 2026-11-03 | Metro Cable | 10 | 1.4 | 0.2 |
| 2026-11-03 | Example Fiber | 8.6 | 1.9 | 0 |
| 2026-11-02 | Starlink | 42.8 | 1.5 | 0.2 |
| 2026-11-02 | Metro Cable | 9.9 | 1.5 | 0 |
| 2026-11-02 | Example Fiber | 7.5 | 1.5 | 0.2 |
| 2026-11-01 | Starlink | 41.7 | 1.6 | 0 |
| 2026-11-01 | Metro Cable | 9.2 | 1.3 | 0 |
| 2026-11-01 | Example Fiber | 8.5 | 1.3 | 0 |
| 2026-10-31 | Starlink | 45.3 | 1.3 | 0.2 |
| 2026-10-31 | Metro Cable | 8.3 | 1.1 | 0.5 |
| 2026-10-31 | Example Fiber | 9.3 | 0.9 | 0 |
| 2026-10-30 | Starlink | 44 | 1.4 | 0 |
| 2026-10-30 | Metro Cable | 10.4 | 1.6 | 0.2 |
| 2026-10-30 | Example Fiber | 9.1 | 1.7 | 0.2 |
| 2026-10-29 | Starlink | 45.3 | 1.8 | 0 |
| 2026-10-29 | Metro Cable | 9.2 | 1.4 | 0 |
| 2026-10-29 | Example Fiber | 7.8 | 1.6 | 0 |
| 2026-10-28 | Starlink | 47.3 | 1.9 | 0 |
| 2026-10-28 | Metro Cable | 8.6 | 1.7 | 0 |
| 2026-10-28 | Example Fiber | 7.9 | 1.8 | 0 |
| 2026-10-27 | Starlink | 40.1 | 1.6 | 0 |
| 2026-10-27 | Metro Cable | 9.3 | 1.4 | 0.2 |
| 2026-10-27 | Example Fiber | 9.3 | 1.6 | 0 |
| 2026-10-26 | Starlink | 46.9 | 1.3 | 0 |
| 2026-10-26 | Metro Cable | 10.2 | 1.6 | 0 |
| 2026-10-26 | Example Fiber | 9.1 | 1 | 0 |
| 2026-10-25 | Starlink | 42.2 | 1.4 | 0.2 |
| 2026-10-25 | Metro Cable | 8.9 | 1 | 0 |
| 2026-10-25 | Example Fiber | 8.4 | 1.2 | 0 |
| 2026-10-24 | Starlink | 39.5 | 1.3 | 0 |
| 2026-10-24 | Metro Cable | 10.2 | 1.5 | 0 |
| 2026-10-24 | Example Fiber | 8.8 | 1.2 | 0 |
| 2026-10-23 | Starlink | 43 | 2 | 0 |
| 2026-10-23 | Metro Cable | 10.9 | 1.8 | 0 |
| 2026-10-23 | Example Fiber | 9.1 | 2 | 0 |
Tunnel stability – last 7 days
32 tunnels · 28 up on every run in the last 7 days.
| Tunnel | Times it went down | Up |
|---|---|---|
| to-boston | 1 | 97% |
| to-boston-b | 1 | 97% |
| to-philadelphia | 1 | 97% |
| to-philadelphia-b | 1 | 97% |
Configuration & routing changes – last 30 days 5
| When | Type | What | Detail |
|---|---|---|---|
| Nov 22 4:15 PM | Config | Static route 4 | added: dst 192.0.2.0 255.255.255.0, device wan1 |
| Nov 22 4:15 PM | Routing | Route 192.0.2.0/24 | added – static via wan1 |
| Nov 22 4:15 PM | Routing | Route 10.16.0.0/16 | OSPF via to-minneapolis → OSPF via to-minneapolis, to-minneapolis-b |
| Nov 10 9:42 AM | Config | Interface printers | description: – → Floor 2 printers |
| Nov 4 4:16 PM | Config | Service NL-ERP | added: TCP 8443-8445 |
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 15 3:39 PM | New deviceWired | New device 00:11:32:fa:66:5e | 10.1.30.11 SAN01 on FG-CHICAGO-SW2 port16 |
| Nov 7 12:13 PM | New deviceAccess point | New device 00:11:22:01:00:06 | 10.1.10.26 FG-CHICAGO-AP7 on FG-CHICAGO-SW1 port4 |
| Oct 30 3:07 PM | Device movedAccess point | Device moved 00:11:22:01:00:04 | 10.1.10.24 FG-CHICAGO-SW5 port7 → FG-CHICAGO-SW5 port3 |
| Oct 29 4:33 PM | New deviceWired | New device d0:43:1e:01:0a:01 | 10.1.10.120 NL-CHI-PC011 on FG-CHICAGO-SW1 port13 |
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 exposure2
- ●1 port forward to review
Published to the internet. Confirm each is still needed and limited to who needs it.
- web (203.0.113.11 tcp 8443 → 10.1.30.20)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show firewall vipconfig firewall vip edit "web" set extip 203.0.113.11 set mappedip "10.1.30.20" set portforward enable set extport 8443 next endHow to fix
These addresses/ports on a public IP are forwarded to internal devices. Each is only reachable if a firewall policy allows it – review that each is still needed and limited to the sources that need it.
- Check which firewall policy uses each one (below) and who its source is.
- Not needed: delete the policy, then the VIP.
- Needed: limit the source (set src-filter, or a source address group in the policy) – or use the VPN instead.
- Cameras / DVRs: use the vendor's cloud relay or the VPN rather than an open port.
web: 203.0.113.11 tcp 8443 → 10.1.30.20
show firewall policy | grep -f "web" config firewall vip edit "web" set src-filter <allowed public IPs> next end - ●known-bad address
- 198.51.100.96/28 – Address object: address Partner-FTP-Net (used in policy 20)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show firewall addressconfig firewall address edit "Partner-FTP-Net" set uuid 89683144-2c32-ef70-ce6f-acad015e2c6c set subnet 198.51.100.96 255.255.255.240 set comment "Old EDI partner" next endHow to fix
An address this FortiGate is configured to trust or talk to is on a public list of compromised or hostile hosts (Emerging Threats, rule numbers 2000000-2799999). A list is not proof: addresses are re-used, and a listed address may belong to someone else today.
- Find out who the address belongs to today (whois) and whether anyone still needs it.
- Look at the traffic to and from it in the FortiGate's logs (below; read-only).
- Not needed: remove it from the object, tunnel or neighbour. Needed and checked: acknowledge it in the site file ("acknowledged": {"badip_match": {"198.51.100.96/28": "why"}}).
198.51.100.96/28: address Partner-FTP-Net
execute log filter reset execute log filter category traffic execute log filter field srcip 198.51.100.96/28 execute log display execute log filter reset execute log filter category traffic execute log filter field dstip 198.51.100.96/28 execute log display - Redundancy reduced3
- ●no tunnel to Boston, Philadelphia
- No working IPsec tunnel to Boston, Philadelphia – every tunnel to that site is down
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get vpn ipsec tunnel summary'to-boston' 203.0.113.25:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-boston-b' 198.51.100.25:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-philadelphia' 203.0.113.28:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-philadelphia-b' 198.51.100.28:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0How 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.
- Check the tunnel from this end (and the other site's end) – the WAN page's Tunnel paths tab shows both.
- For backup tunnels, enable auto-negotiate on their phase 2 (below) so they stay up.
- Tunnels that point at the wrong IP or a site that no longer exists: fix the remote gateway, or delete them.
to-boston → 203.0.113.25
to-boston-b → 198.51.100.25
to-philadelphia → 203.0.113.28
to-philadelphia-b → 198.51.100.28get vpn ipsec tunnel summary diagnose vpn tunnel list name to-boston diagnose vpn tunnel list name to-boston-b diagnose vpn tunnel list name to-philadelphia - ●4 tunnels down
- 4 tunnels down: to-boston, to-boston-b, to-philadelphia, to-philadelphia-b
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get vpn ipsec tunnel summary'to-boston' 203.0.113.25:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-boston-b' 198.51.100.25:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-philadelphia' 203.0.113.28:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-philadelphia-b' 198.51.100.28:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0How 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.
- Check the tunnel from this end (and the other site's end) – the WAN page's Tunnel paths tab shows both.
- For backup tunnels, enable auto-negotiate on their phase 2 (below) so they stay up.
- Tunnels that point at the wrong IP or a site that no longer exists: fix the remote gateway, or delete them.
to-boston → 203.0.113.25
to-boston-b → 198.51.100.25
to-philadelphia → 203.0.113.28
to-philadelphia-b → 198.51.100.28get vpn ipsec tunnel summary diagnose vpn tunnel list name to-boston diagnose vpn tunnel list name to-boston-b diagnose vpn tunnel list name to-philadelphia - ●FortiLink split-interface with MCLAG
- FortiLink aggregate fortilink still has fortilink-split-interface enabled while an MCLAG ICL is present. Split-interface keeps only one FortiLink path active – disable it for FortiLink MCLAG.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system interfaceedit "fortilink" … fortilink-split-interface (not disable)diagnose switch-controller switch-info mclag icl2 ICL trunk(s)How to fix
FortiLink split-interface keeps only one uplink active toward the FortiGate. With an MCLAG ICL already formed, leave split-interface disabled so both switches forward on FortiLink.
- On the FortiLink aggregate (fortilink), set fortilink-split-interface disable.
- Confirm LACP active on the FortiLink aggregate.
- Re-check mclag icl and peer-consistency-check.
show system interface config system interface edit "fortilink" set fortilink-split-interface disable set lacp-mode active next end diagnose switch-controller switch-info mclag icl - Performance1
- ●1 optic to check
- FortiGate x2: Rx power warning (-9.62)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get system interface transceiver / modules summaryInterface x1 - SFP/SFP+, 10GBASE-SR Vendor Name : FORTINET Part No. : FN-TRAN-SFP+SR Serial No. : NLFG35644 Interface x2 - SFP/SFP+, 10GBASE-SR Vendor Name : FORTINET Part No. : FN-TRAN-SFP+SR Serial No. : NLFG02130 Optical Temperature Voltage Tx Bias Tx Power Rx Power Interface (Celsius) (Volts) (mA) (dBm) (dBm) ------------ --------------- ------------- ------------- ------------- ------------- x1 36.8 3.30 6.42 -2.31 -3.05 x2 38.1 3.29 6.57 -2.44 -9.62 - ++ : high alarm, + : high warning, - : low warning, -- : low alarm, ? : suspect.How to fix
Optics reporting alarms or warnings, no light on an inserted module, or low receive power. Low light usually means a dirty connector or a damaged/long fiber – it gets worse until the link drops. An inserted optic with no light on an unused port is just a spare – remove it to clear the alarm.
- Clean both ends of the fiber (and the optic) with a fiber cleaner; re-seat the optic.
- Still low: swap the patch cable, then the optic; check the fiber type matches the optic (SR = multimode, LR = single-mode).
- Unused port with an optic: remove it.
FortiGate x2
get system interface transceiver diagnose switch-controller switch-info modules summary <switch> diagnose switch-controller switch-info modules detail <switch> <port> - Configuration3
- ●clear-text admin
- Unencrypted admin access (http/telnet) enabled: users (http)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system interfaceconfig system interface edit "users" set ip 10.1.10.1 255.255.255.0 set allowaccess ping http next endHow to fix
http/telnet send admin passwords unencrypted. Use https (and ssh) only for the admin GUI.
- Confirm nobody manages this FortiGate over http or telnet on these interfaces.
- Remove http and telnet from allowaccess; keep https (and ssh if you use it) – below keeps everything else.
- Also check Best Practices for strong-crypto, admin-https-ssl-versions, and admin-server-cert.
config system interface edit "users" set allowaccess ping next end - ●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-seattle-b show vpn ipsec phase2-interface | grep -f to-seattle-b # on Seattle: show vpn ipsec phase1-interface | grep -f to-chicago-b show vpn ipsec phase2-interface | grep -f to-chicago-b - ●IPsec settings differ at the two ends
- Chicago's to-losangeles ↔ Los Angeles's to-chicago: phase 1 ike-version: 2 vs (default); phase 1 proposal: aes256-sha256 vs aes128-sha1; phase 1 dhgrp: 14 vs 5
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-losangeles" set remote-gw 203.0.113.23 set ike-version 2 set proposal aes256-sha256 set dhgrp 14 next end config vpn ipsec phase1-interface edit "to-chicago" set remote-gw 203.0.113.11 set proposal aes128-sha1 set dhgrp 5 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-losangeles show vpn ipsec phase2-interface | grep -f to-losangeles # on Los Angeles: show vpn ipsec phase1-interface | grep -f to-chicago show vpn ipsec phase2-interface | grep -f to-chicago - Monitoring & housekeeping3
- ●health check misses a WAN
- SD-WAN health check(s) do not cover wan4. Those links are not probed, so a silent ISP failure on them is not seen.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system sdwanedit "virtual-wan-link" edit 1 set interface "wan1"How to fix
Each SD-WAN internet member should be in a health check so a quiet-but-dead ISP is detected. Link-state alone misses brownouts and upstream failures.
- Add a health check (or extend members=) so every WAN/SD-WAN member is probed.
- Use a public probe target reachable on those WANs.
- Confirm with diagnose sys sdwan health-check that each member shows alive or dead.
Not covered: wan4
show system sdwan diagnose sys sdwan health-check # example – probe every member: config system sdwan config health-check edit "Internet" set server "8.8.8.8" set members 1 next end end - ●Certificate 15 days
- Certificate: Northline-Web expires in 15 days (Dec 07 2026)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get vpn certificate local detailsNorthline-Web: 2026-12-07How to fix
The certificate 'Northline-Web' on this FortiGate expires 2026-12-07. 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-Web show vpn ssl settings show system global | grep -f cert show vpn ipsec phase1-interface | grep -f certificate - ●FortiGuard 33 days
- FortiGuard: AV Engine, Virus Definitions, Extended set, Mobile Malware Definitions +2 more expires in 33 days (Dec 25 2026)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
diagnose autoupdate versionsAV Engine, Virus Definitions, Extended set, Mobile Malware Definitions +2 more: 2026-12-25How to fix
FortiGuard service(s) AV Engine, Virus Definitions, Extended set, Mobile Malware Definitions +2 more expire 2026-12-25. After that the FortiGate stops receiving updates for them (signatures, web filtering, etc.); traffic keeps flowing but protection goes stale.
- Renew through your Fortinet partner / FortiCare (support.fortinet.com → Assets) with the serial number.
- After the renewal is applied, the FortiGate picks it up on its next update check (or update it manually).
- If it's not going to be renewed, acknowledge it in the site file so it stops flagging.
get system status diagnose autoupdate versions | grep -A2 -i expiry execute update-now # admin account, after renewal
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 Chicago floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment19 devices1 with support ended
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-CHICAGO FortiGate · FortiGate 200F | FGDEMO00010001 tag NL-0001 | Chicago Northline | 2022-06-08 4.5 years old PO PO-55502 · Example Reseller | Premium 2027-09-15 contract NL-SUP-01 warranty 2023-06-08 passed | 2031-08-31 end of order 2026-08-31 | 2027 → FortiGate 200G spare: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHICAGO-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF01010001 tag NL-01S01 | Chicago · Closet 1 · Rack 1 Network team | 2022-02-15 4.8 years old PO PO-56010 · 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: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHICAGO-SW2 FortiSwitch · FortiSwitch 124F-FPOE | S124FF01020001 tag NL-01S02 | Chicago · Closet 2 · Rack 2 Network team | 2023-02-15 3.8 years old PO PO-56011 · Example Reseller | Standard 2028-03-01 contract NL-FSW warranty 2028-03-01 | 2033-03-31 end of order 2028-03-31 | 2029 → FortiSwitch 124G-FPOE spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHICAGO-SW3 FortiSwitch · FortiSwitch 124F-FPOE | S124FF01030001 tag NL-01S03 | Chicago · Closet 3 · Rack 3 Network team | 2024-02-15 2.8 years old PO PO-56012 · 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: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHICAGO-SW4 FortiSwitch · FortiSwitch 124F-FPOE | S124FF01040001 tag NL-01S04 | Chicago · Closet 4 · Rack 4 Network team | 2021-02-15 5.8 years old PO PO-56013 · 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-CHICAGO-SW5 FortiSwitch · FortiSwitch 124F-FPOE | S124FF01050001 tag NL-01S05 | Chicago · Closet 5 · Rack 5 Network team | 2022-02-15 4.8 years old PO PO-56014 · 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-CHICAGO-SW6 FortiSwitch · FortiSwitch 124F-FPOE | S124FF01060001 tag NL-01S06 | Chicago · Closet 6 · Rack 6 Network team | 2023-02-15 3.8 years old PO PO-56015 · Example Reseller | Standard 2028-03-01 contract NL-FSW warranty 2028-03-01 | 2033-03-31 end of order 2028-03-31 | 2029 → FortiSwitch 124G-FPOE spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHICAGO-AP1 FortiAP · FAP231F | FP231F01010001 tag NL-01A01 | Chicago · Ceiling, zone 1 Network team | 2023-05-10 3.5 years old PO PO-57010 · 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-CHICAGO-AP2 FortiAP · FAP231F | FP231F01020001 tag NL-01A02 | Chicago · Ceiling, zone 2 Network team | 2024-05-10 2.5 years old PO PO-57011 · 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-CHICAGO-AP3 FortiAP · FAP231F | FP231F01030001 tag NL-01A03 | Chicago · Ceiling, zone 3 Network team | 2022-05-10 4.5 years old PO PO-57012 · 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-CHICAGO-AP4 FortiAP · FAP231F | FP231F01040001 tag NL-01A04 | Chicago · Ceiling, zone 4 Network team | 2023-05-10 3.5 years old PO PO-57013 · 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-CHICAGO-AP5 FortiAP · FAP231F | FP231F01050001 tag NL-01A05 | Chicago · Ceiling, zone 5 Network team | 2024-05-10 2.5 years old PO PO-57014 · 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-CHICAGO-AP6 FortiAP · FAP231F | FP231F01060001 tag NL-01A06 | Chicago · Ceiling, zone 6 Network team | 2022-05-10 4.5 years old PO PO-57015 · 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-CHICAGO-AP7 FortiAP · FAP231F | FP231F01070001 tag NL-01A07 | Chicago · Ceiling, zone 7 Network team | 2023-05-10 3.5 years old PO PO-57016 · 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-CHICAGO-AP8 FortiAP · FAP231F | FP231F01080001 tag NL-01A08 | Chicago · Ceiling, zone 8 Network team | 2024-05-10 2.5 years old PO PO-57017 · 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-CHICAGO-AP9 FortiAP · FAP231F | FP231F01090001 tag NL-01A09 | Chicago · Ceiling, zone 9 Network team | 2022-05-10 4.5 years old PO PO-57018 · 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-CHICAGO-AP10 FortiAP · FAP231F | FP231F01100001 tag NL-01A10 | Chicago · Ceiling, zone 10 Network team | 2023-05-10 3.5 years old PO PO-57019 · 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-CHICAGO-AP11 FortiAP · FAP231F | FP231F01110001 tag NL-01A11 | Chicago · Ceiling, zone 11 Network team | 2024-05-10 2.5 years old PO PO-57020 · 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-CHICAGO-AP12 FortiAP · FAP231F | FP231F01120001 tag NL-01A12 | Chicago · Ceiling, zone 12 Network team | 2022-05-10 4.5 years old PO PO-57021 · 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. |
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 contracts4 circuits1 ended
| Circuit | Bandwidth | Ping | From | Ends | Notice | SLA | |
|---|---|---|---|---|---|---|---|
| Example Fiber Example Fiber · wan1 · NL-011 | 500/500 | 8 ms collector ping | 2025-01-14 | 2028-01-14 give notice within 328 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-012 | 300/30 | 6 ms collector ping | 2023-03-15 | 2028-03-15 give notice within 419 days | 60 days renews by itself: no | 99.5 Made-up circuit. | |
| Starlink Starlink · wan3 · NL-013 | 100/20 | 10 ms collector ping | 2025-09-22 | 2026-09-22 ended | 30 days renews by itself: yes | 99.5 Month to month after the first year. | |
| Example Fiber West Example Fiber West · wan4 · NL-014 | 300/30 | 11 ms collector ping | 2025-07-15 | 2028-07-15 give notice within 541 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.1.10.0/24 | 10.1.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Chicago network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.1.20.0/24 | 10.1.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Chicago network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.1.30.0/24 | 10.1.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Chicago network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.1.40.0/24 | 10.1.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Chicago network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.1.50.0/24 | 10.1.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Chicago network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.1.90.0/24 | 10.1.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Chicago 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.