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-ATLANTA | FortiGate-90G | 7.4.8 | 16% | 50% | 5,834 | 39% · wan1 | — | Working normally |
Switches55 · 0 need a look · PoE 194 of 1850 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-ATLANTA-SW1 | FortiSwitch 124F-FPOE | 13 / 28 | 49 of 370 W | — | FG-ATLANTA-SW2 port28 (port25) | 7.4.5 | Working normally | |
| FG-ATLANTA-SW2 | FortiSwitch 124F-FPOE | 12 / 28 | 36 of 370 W | — | FG-ATLANTA-SW4 port28 (port25) | 7.4.5 | Working normally | |
| FG-ATLANTA-SW3 | FortiSwitch 124F-FPOE | 6 / 28 | 37 of 370 W | — | FG-ATLANTA-SW1 port26 (port28) | 7.4.5 | Working normally | |
| FG-ATLANTA-SW4 | FortiSwitch 124F-FPOE | 4 / 28 | 34 of 370 W | — | FG-ATLANTA-SW2 port25 (port28) | 7.4.5 | Working normally | |
| FG-ATLANTA-SW5 | FortiSwitch 124F-FPOE | 7 / 28 | 38 of 370 W | — | FG-ATLANTA-SW2 port26 (port28) | 7.4.5 | Working normally |
Access points1717 · 3 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-ATLANTA-AP15 | FP231F | — | — | — | — | FG-ATLANTA-SW5 port5 | 7.4.3 | Off – Wi-Fi near it may be patchy | |
| FG-ATLANTA-AP16 | FP231F | — | — | — | — | FG-ATLANTA-SW1 port6 | 7.4.3 | Off – Wi-Fi near it may be patchy | |
| FG-ATLANTA-APNEW | FP231F | — | — | — | — | FG-ATLANTA-SW1 port9 | 7.4.3 | Off – Wi-Fi near it may be patchy | |
| FG-ATLANTA-AP1 | FP231F | — | — | — | — | FG-ATLANTA-SW1 port3 | 7.2.2 | Working normally | |
| FG-ATLANTA-AP10 | FP231F | — | — | — | — | FG-ATLANTA-SW5 port4 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP11 | FP231F | — | — | — | — | FG-ATLANTA-SW1 port5 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP12 | FP231F | — | — | — | — | FG-ATLANTA-SW2 port5 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP13 | FP231F | — | — | — | — | FG-ATLANTA-SW3 port5 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP14 | FP231F | — | — | — | — | FG-ATLANTA-SW4 port5 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP2 | FP231F | — | — | — | — | FG-ATLANTA-SW2 port3 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP3 | FP231F | — | — | — | — | FG-ATLANTA-SW3 port3 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP4 | FP231F | — | — | — | — | FG-ATLANTA-SW4 port3 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP5 | FP231F | — | — | — | — | FG-ATLANTA-SW5 port3 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP6 | FP231F | — | — | — | — | FG-ATLANTA-SW1 port4 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP7 | FP231F | — | — | — | — | FG-ATLANTA-SW2 port4 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP8 | FP231F | — | — | — | — | FG-ATLANTA-SW3 port4 | 7.4.3 | Working normally | |
| FG-ATLANTA-AP9 | FP231F | — | — | — | — | FG-ATLANTA-SW4 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.9.10.0/24 | 10.9.10.1 | 255.255.255.0 /24 | 10.9.10.120 – 10.9.10.139 20 addresses · 18 in use · lease 8 hours | |
| 20 | voice | 10.9.20.0/24 | 10.9.20.1 | 255.255.255.0 /24 | 10.9.20.20 – 10.9.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.9.30.0/24 | 10.9.30.1 | 255.255.255.0 /24 | 10.9.30.20 – 10.9.30.250 231 addresses · 0 in use · lease 7 days · 7 reserved | |
| 40 | printers | 10.9.40.0/24 | 10.9.40.1 | 255.255.255.0 /24 | 10.9.40.100 – 10.9.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.9.50.0/24 | 10.9.50.1 | 255.255.255.0 /24 | 10.9.50.20 – 10.9.50.250 231 addresses · 1 in use · lease 7 days | |
| 90 | iot | 10.9.90.0/24 | 10.9.90.1 | 255.255.255.0 /24 | 10.9.90.100 – 10.9.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.9.0/24 | 10.255.9.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 39 | 20 Label printer / scanner · 18 Computer · 1 Network gear |
| 20 | voice | 3 | 3 Phone (VoIP) |
| 30 | servers | 6 | 5 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 | 5 | 5 Network gear |
| 30 | servers | 1 | 1 Storage / server |
| 10 | users | 17 | 17 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.
5 switches · 42 ports in use · 98 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 closet5 closets42 of 140 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Atlanta | Closet 1 FG-ATLANTA-SW1 | 13 / 28 (46%) | 13 | 13 | 49 / 370 W (13%) 321 W headroom | |
| Atlanta | Closet 2 FG-ATLANTA-SW2 | 12 / 28 (43%) | 15 | 15 | 36 / 370 W (10%) 334 W headroom | |
| Atlanta | Closet 3 FG-ATLANTA-SW3 | 6 / 28 (21%) | 19 | 19 | 37 / 370 W (10%) 333 W headroom | |
| Atlanta | Closet 4 FG-ATLANTA-SW4 | 4 / 28 (14%) | 21 | 21 | 34 / 370 W (9%) 336 W headroom | |
| Atlanta | Closet 5 FG-ATLANTA-SW5 | 7 / 28 (25%) | 18 | 18 | 38 / 370 W (10%) 332 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-ATLANTA-SW1 FortiSwitch 124F-FPOE · Closet 113 in use · 15 free · PoE 49 / 370 W · 2 fiber ports · 43 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-ATLANTA-AP1 FortiAP | 10 users | 10.9.10.20 · 00:11:22:09:00:00 2 Wi-Fi clients list | 12.0 W class 4 | |
| port4 | Up | FG-ATLANTA-AP6 FortiAP | 10 users | 10.9.10.25 · 00:11:22:09:00:05 4 Wi-Fi clients list | 12.8 W class 4 | |
| port5 | Up | FG-ATLANTA-AP11 FortiAP | 10 users | 10.9.10.30 · 00:11:22:09:00:0a 3 Wi-Fi clients list | 10.8 W class 4 | |
| port13 | Up | NL-ATL-PC011 | 10 users | 10.9.10.120 · d0:43:1e:09:0a:01 | ||
| port14 | Up | NL-ATL-LT012 | 10 users | 10.9.10.121 · d0:43:1e:09:0a:02 | ||
| port15 | Up | NL-ATL-PC013 | 10 users | 10.9.10.122 · d0:43:1e:09:0a:03 | ||
| port16 | Up | NL-ATL-PH01 phone | 20 voice | 10.9.20.20 · 00:04:f2:09:14:01 | 4.1 W class 2 | |
| port17 | Up | NL-ATL-PH02 phone | 20 voice | 10.9.20.21 · 00:04:f2:09:14:02 | 3.4 W class 2 | |
| port18 | Up | PRN-ATL-01 | 40 printers | 10.9.40.20 · 3c:2a:f4:09:28:01 | ||
| port19 | Up | CAM-DOCK-01 | 50 cameras | 10.9.50.20 · 00:40:8c:09:32:01 | 5.7 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00090001 | ||||
| port25 | Up | ↔ FG-ATLANTA-SW2 port28 trunk S124FF09020001-0 | Fiber 10G-SR | |||
| port26 | Up | ↔ FG-ATLANTA-SW3 port28 trunk S124FF09030001-0 | Fiber 10G-SR |
Free ports: port1–2, port6–12, port20–23, port27–28
S124FF09010001 · FortiSwitchOS 7.4.5
FG-ATLANTA-SW2 FortiSwitch 124F-FPOE · Closet 212 in use · 16 free · PoE 36 / 370 W · 3 fiber ports · 44 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-ATLANTA-AP2 FortiAP | 10 users | 10.9.10.21 · 00:11:22:09:00:01 3 Wi-Fi clients list | 13.6 W class 4 | |
| port4 | Up | FG-ATLANTA-AP7 FortiAP | 10 users | 10.9.10.26 · 00:11:22:09:00:06 4 Wi-Fi clients list | 12.0 W class 4 | |
| port5 | Up | FG-ATLANTA-AP12 FortiAP | 10 users | 10.9.10.31 · 00:11:22:09:00:0b 2 Wi-Fi clients list | 10.7 W class 4 | |
| port7 | Up | DC01 | 30 servers | 10.9.30.2 · f8:bc:12:0e:77:f6 | ||
| port8 | Up | FILE01 | 30 servers | 10.9.30.3 · f8:bc:12:a4:9d:d7 | ||
| port9 | Up | WMS01 | 30 servers | 10.9.30.4 · f8:bc:12:90:02:4e | ||
| port11 | Up | IPERF01 | 30 servers | 10.9.30.6 · f8:bc:12:54:77:10 | ||
| port12 | Up | NAS01 | 30 servers | 10.9.30.7 · 00:11:32:a7:fb:f2 | ||
| port13 | Up | UPS-MDF | 30 servers | 10.9.30.8 · 00:c0:b7:c4:f4:46 | ||
| port25 | Up | ↔ FG-ATLANTA-SW4 port28 trunk S124FF09040001-0 | Fiber 10G-LR | |||
| port26 | Up | ↔ FG-ATLANTA-SW5 port28 trunk S124FF09050001-0 | Fiber 10G-LR | |||
| port28 | Up | ↔ FG-ATLANTA-SW1 port25 trunk S124FF09010001-0 | Fiber 10G-SR |
Free ports: port1–2, port6, port10, port14–24, port27
S124FF09020001 · FortiSwitchOS 7.4.5
FG-ATLANTA-SW3 FortiSwitch 124F-FPOE · Closet 36 in use · 22 free · PoE 37 / 370 W · 1 fiber port · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-ATLANTA-AP3 FortiAP | 10 users | 10.9.10.22 · 00:11:22:09:00:02 2 Wi-Fi clients list | 12.9 W class 4 | |
| port4 | Up | FG-ATLANTA-AP8 FortiAP | 10 users | 10.9.10.27 · 00:11:22:09:00:07 2 Wi-Fi clients list | 11.7 W class 4 | |
| port5 | Up | FG-ATLANTA-AP13 FortiAP | 10 users | 10.9.10.32 · 00:11:22:09:00:0c 2 Wi-Fi clients list | 12.8 W class 4 | |
| port14 | Up | DOCK-ATL-01 | 90 iot | 10.9.90.30 · 00:07:4d:f8:0d:65 | ||
| port15 | Up | DOCK-ATL-02 | 90 iot | 10.9.90.31 · 00:07:4d:97:0a:86 | ||
| port28 | Up | ↔ FG-ATLANTA-SW1 port26 trunk S124FF09010001-0 | Fiber 10G-SR |
Free ports: port1–2, port6–13, port16–27
S124FF09030001 · FortiSwitchOS 7.4.5
FG-ATLANTA-SW4 FortiSwitch 124F-FPOE · Closet 44 in use · 24 free · PoE 34 / 370 W · 1 fiber port · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-ATLANTA-AP4 FortiAP | 10 users | 10.9.10.23 · 00:11:22:09:00:03 2 Wi-Fi clients list | 13.1 W class 4 | |
| port4 | Up | FG-ATLANTA-AP9 FortiAP | 10 users | 10.9.10.28 · 00:11:22:09:00:08 1 Wi-Fi client list | 10.6 W class 4 | |
| port5 | Up | FG-ATLANTA-AP14 FortiAP | 10 users | 10.9.10.33 · 00:11:22:09:00:0d 1 Wi-Fi client list | 10.0 W class 4 | |
| port28 | Up | ↔ FG-ATLANTA-SW2 port25 trunk S124FF09020001-0 | Fiber 10G-LR |
Free ports: port1–2, port6–27
S124FF09040001 · FortiSwitchOS 7.4.5
FG-ATLANTA-SW5 FortiSwitch 124F-FPOE · Closet 57 in use · 21 free · PoE 38 / 370 W · 1 fiber port · 39 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-ATLANTA-AP5 FortiAP | 10 users | 10.9.10.24 · 00:11:22:09:00:04 4 Wi-Fi clients list | 10.5 W class 4 | |
| port4 | Up | FG-ATLANTA-AP10 FortiAP | 10 users | 10.9.10.29 · 00:11:22:09:00:09 3 Wi-Fi clients list | 10.4 W class 4 | |
| port7 | Up | PAGE-WHSE | 20 voice | 10.9.20.2 · 00:22:ee:bd:00:87 | 6.4 W class 3 | |
| port9 | Up | DOOR-DOCK1 | 90 iot | 10.9.90.2 · 00:06:8e:27:c3:73 | 4.2 W class 2 | |
| port10 | Up | DOOR-DOCK2 | 90 iot | 10.9.90.3 · 00:06:8e:05:bc:dd | 4.2 W class 2 | |
| port11 | Up | ENV-FREEZER | 90 iot | 10.9.90.4 · b8:27:eb:40:0a:c9 | 1.9 W class 1 | |
| port28 | Up | ↔ FG-ATLANTA-SW2 port26 trunk S124FF09020001-0 | Fiber 10G-LR |
Free ports: port1–2, port5–6, port8, port12–27
S124FF09050001 · FortiSwitchOS 7.4.5
On-site contacts
- Samira Patel · (209) 555-1009 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 12/15/2025 to 12/15/2028 · 754 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.19 /29
- Gateway
- 203.0.113.17
- Circuit ID
- NL-091
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 2/14/2026 to 2/14/2029 · 815 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.19 /29
- Gateway
- 198.51.100.17
- Circuit ID
- NL-092
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary3 static 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 · equal cost |
| 10.0.0.0/8 | Static | blackhole (dropped) |
| 10.1.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.2.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.3.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.4.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.5.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.6.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.7.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.8.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.9.10.0/24 | Connected | users local network |
| 10.9.20.0/24 | Connected | voice local network |
| 10.9.30.0/24 | Connected | servers local network |
| 10.9.40.0/24 | Connected | printers local network |
| 10.9.50.0/24 | Connected | cameras local network |
| 10.9.90.0/24 | Connected | iot local network |
| 10.10.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.11.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.12.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.13.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.14.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.16.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.17.0.0/16 | OSPF | to-chicago-b → Chicago |
| 10.255.9.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.4 | 1.4 | 0 |
| 2026-11-22 | Example Fiber | 8.8 | 1.4 | 0 |
| 2026-11-21 | Metro Cable | 9.2 | 1.1 | 0.5 |
| 2026-11-21 | Example Fiber | 8.2 | 1.2 | 0 |
| 2026-11-20 | Metro Cable | 9.1 | 1.5 | 0 |
| 2026-11-20 | Example Fiber | 8.5 | 1.6 | 0 |
| 2026-11-19 | Metro Cable | 9 | 1.2 | 0 |
| 2026-11-19 | Example Fiber | 8.8 | 1.7 | 0.5 |
| 2026-11-18 | Metro Cable | 9.7 | 1.3 | 0 |
| 2026-11-18 | Example Fiber | 9.3 | 1.7 | 0 |
| 2026-11-17 | Metro Cable | 9.6 | 1.5 | 0 |
| 2026-11-17 | Example Fiber | 8.5 | 1.3 | 0 |
| 2026-11-16 | Metro Cable | 9.4 | 1.5 | 0 |
| 2026-11-16 | Example Fiber | 7.5 | 1.2 | 0 |
| 2026-11-15 | Metro Cable | 9.6 | 0.9 | 0 |
| 2026-11-15 | Example Fiber | 8.4 | 1.4 | 0 |
| 2026-11-14 | Metro Cable | 9.2 | 1.5 | 0 |
| 2026-11-14 | Example Fiber | 8.7 | 1.4 | 0 |
| 2026-11-13 | Metro Cable | 10.3 | 1.4 | 0.5 |
| 2026-11-13 | Example Fiber | 8.2 | 1 | 0 |
| 2026-11-12 | Metro Cable | 9.3 | 1.6 | 0 |
| 2026-11-12 | Example Fiber | 8.4 | 1.4 | 0.5 |
| 2026-11-11 | Metro Cable | 10.1 | 1.5 | 0 |
| 2026-11-11 | Example Fiber | 8 | 1.1 | 0.2 |
| 2026-11-10 | Metro Cable | 9.8 | 1.7 | 0.2 |
| 2026-11-10 | Example Fiber | 8.5 | 1.5 | 0 |
| 2026-11-09 | Metro Cable | 9 | 1.3 | 0 |
| 2026-11-09 | Example Fiber | 9.1 | 1.4 | 0.2 |
| 2026-11-08 | Metro Cable | 9.2 | 1.1 | 0 |
| 2026-11-08 | Example Fiber | 9.3 | 1.4 | 0.2 |
| 2026-11-07 | Metro Cable | 9.4 | 1.4 | 0 |
| 2026-11-07 | Example Fiber | 9.5 | 1 | 0 |
| 2026-11-06 | Metro Cable | 10.4 | 1.4 | 0 |
| 2026-11-06 | Example Fiber | 7.6 | 1.6 | 0 |
| 2026-11-05 | Metro Cable | 10.4 | 1.6 | 0 |
| 2026-11-05 | Example Fiber | 8.4 | 1.3 | 0 |
| 2026-11-04 | Metro Cable | 9.8 | 1.6 | 0.2 |
| 2026-11-04 | Example Fiber | 9 | 1 | 0.2 |
| 2026-11-03 | Metro Cable | 10 | 1.8 | 0 |
| 2026-11-03 | Example Fiber | 8.6 | 1.2 | 0 |
| 2026-11-02 | Metro Cable | 9.8 | 1.4 | 0 |
| 2026-11-02 | Example Fiber | 8.1 | 1.5 | 0 |
| 2026-11-01 | Metro Cable | 10.1 | 1.1 | 0 |
| 2026-11-01 | Example Fiber | 8.9 | 1 | 0 |
| 2026-10-31 | Metro Cable | 10 | 1.6 | 0 |
| 2026-10-31 | Example Fiber | 8.9 | 1 | 0 |
| 2026-10-30 | Metro Cable | 9.6 | 1.5 | 0 |
| 2026-10-30 | Example Fiber | 8.8 | 1.6 | 0 |
| 2026-10-29 | Metro Cable | 8.8 | 1.6 | 0.2 |
| 2026-10-29 | Example Fiber | 9.2 | 1.5 | 0 |
| 2026-10-28 | Metro Cable | 10.3 | 1.3 | 0 |
| 2026-10-28 | Example Fiber | 8.1 | 1.7 | 0 |
| 2026-10-27 | Metro Cable | 8.6 | 1.4 | 0 |
| 2026-10-27 | Example Fiber | 7.7 | 1.3 | 0 |
| 2026-10-26 | Metro Cable | 9 | 1.9 | 0.2 |
| 2026-10-26 | Example Fiber | 9 | 1.1 | 0 |
| 2026-10-25 | Metro Cable | 9 | 1.8 | 0.2 |
| 2026-10-25 | Example Fiber | 7.7 | 1.9 | 0 |
| 2026-10-24 | Metro Cable | 9.6 | 1.9 | 0.2 |
| 2026-10-24 | Example Fiber | 8 | 0.7 | 0 |
| 2026-10-23 | Metro Cable | 8.3 | 1.7 | 0 |
| 2026-10-23 | Example Fiber | 9 | 0.9 | 0 |
Tunnel stability – last 7 days
2 tunnels · 2 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 4
| When | Type | What | Detail |
|---|---|---|---|
| Nov 13 3:13 PM | Config | Static route 45 | added: dst 10.200.0.0 255.255.0.0, device to-chicago |
| Oct 30 3:28 PM | Config | Service NL-ERP | added: TCP 8443-8445 |
| Oct 30 1:07 PM | Config | Service NL-ERP | added: TCP 8443-8445 |
| Oct 27 4:08 PM | Config | Firewall policy 24 | added: users → internet, HTTPS and DNS, log all |
New and moved devices – last 30 days 3
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 16 7:04 AM | Device movedAccess point | Device moved 00:11:22:09:00:05 | 10.9.10.25 FG-ATLANTA-SW1 port8 → FG-ATLANTA-SW1 port4 |
| Nov 14 1:50 PM | New deviceAccess point | New device 00:11:22:09:00:06 | 10.9.10.26 FG-ATLANTA-AP7 on FG-ATLANTA-SW2 port4 |
| Nov 10 9:27 AM | Device movedWi-Fi | Device moved d0:43:1e:09:10:04 | 10.9.10.123 FG-ATLANTA-SW1 port8 → FG-ATLANTA-SW1 port4 |
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
- Users affected2
- ●2 APs disconnected
- 2 APs disconnected: FG-ATLANTA-AP15, FG-ATLANTA-AP16
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get wireless-controller wtp-statusWTP: FP231F09150001 wtp-id : FP231F09150001 name : FG-ATLANTA-AP15 connection-state : Disconnected join-time : Thu Nov 12 08:00:00 2026 WTP: FP231F09160001 wtp-id : FP231F09160001 name : FG-ATLANTA-AP16 connection-state : Disconnected join-time : Thu Nov 12 08:00:00 2026How to fix
The access point isn't talking to the FortiGate's wireless controller, so it isn't serving Wi-Fi. Usually power (PoE), cabling, or the AP itself.
- Check PoE on its switch port (FG-ATLANTA-SW5 port5) – if the port shows no power or 100 Mb, check the cable.
- Power-cycle the port (restarts the AP).
- Still down: check it on site (lights), or swap the AP.
# The switch and port below are what the access point ITSELF announced (LLDP) - they were not read from the switch. # Confirm them before resetting power: the Find page, or the first command. diagnose switch-controller switch-info lldp neighbors-summary diagnose switch-controller switch-info poe summary FG-ATLANTA-SW5 diagnose switch-controller switch-info port-stats FG-ATLANTA-SW5 port5 execute switch-controller poe-reset FG-ATLANTA-SW5 port5 get wireless-controller wtp-status - ●DHCP scope filling up
- DHCP filling up: users – 18 of 20 addresses in use (10% free) (estimate: seen at the last collection, plus reservations)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system dhcp serverconfig system dhcp server edit 1 set default-gateway 10.9.10.1 set netmask 255.255.255.0 set interface "users" set dns-server 10.1.30.2 10.1.30.3 set ntp-server 10.1.30.2 10.1.30.3 set domain-name "northline.example.com" set lease-time 28800 end next endHow to fix
Almost every address in this DHCP scope is taken. New or returning devices on that network get no address – they look as if the network is down. The count is an estimate from what was seen at the last collection plus the reservations; leases held by devices that are off make the real picture worse, not better.
- See who holds the leases (below, with an admin account) – look for stale entries and devices that do not belong there.
- Shorten the lease time on networks where devices come and go (guest, Wi-Fi).
- Widen the range if the subnet has room, or move devices to another network.
- Clear leases that are clearly stale.
execute dhcp lease-list users # shorter lease / wider range: show system dhcp server # clear one stale lease: execute dhcp lease-clear <ip> - Redundancy reduced2
- ●traffic one way only
- 1 tunnel(s) carried traffic in one direction only in the last 69 minutes: to-chicago (received 2,462 / sent 0)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get vpn ipsec tunnel summary'to-chicago' 203.0.113.11:0 selectors(total,up): 1/1 rx(pkt,err): 90000/0 tx(pkt,err): 0/0diagnose vpn tunnel listname=to-chicago ver=2 serial=1 203.0.113.19:0->203.0.113.11:0 nexthop=203.0.113.17 tun_id=203.0.113.11 tun_id6=::203.0.113.11 dst_mtu=1500 dpd-link=on weight=1 bound_if=5 lgwy=static/1 tun=intf mode=auto/1 encap=none/552 options[0228]=npu frag-rfc run_state=0 role=primary accept_traffic=1 overlay_id=0 proxyid_num=1 child_num=0 refcnt=5 ilast=0 olast=1 ad=/0 stat: rxp=90000 txp=0 rxb=12780000 txb=0 dpd: mode=on-demand on=1 status=ok idle=20000ms retry=3 count=0 seqno=223 natt: mode=none draft=0 interval=0 remote_port=0 fec: egress=0 ingress=0 proxyid=to-chicago proto=0 sa=1 ref=2 serial=1 auto-negotiate src: 0:0.0.0.0-255.255.255.255:0 dst: 0:0.0.0.0-255.255.255.255:0 SA: ref=3 options=18227 type=00 soft=0 mtu=1438 expire=9387/0B replaywin=2048 seqno=1 esn=0 replaywin_lastseq=00015f90 qat=0 rekey=0 hash_search_len=1 life: type=01 bytes=0/0 timeout=9387/43200 dec: spi=24ac0205 esp=aes key=32 <removed> ah=sha256 key=32 <removed> enc: spi=c242fdcb esp=aes key=32 <removed> ah=sha256 key=32 <removed> dec:pkts/bytes=90000/12780000, enc:pkts/bytes=0/0 npu_flag=03 npu_rgwy=203.0.113.11 npu_lgwy=203.0.113.19 npu_selid=0 dec_npuid=1 enc_npuid=1 ------------------------------------------------------How to fix
These tunnels are up, but traffic only flows one way: this end sends and never receives (or the reverse). That nearly always means the two ends' IPsec aggregates disagree – different mode, different member order, or a member that exists on one end only – so each end picks a different tunnel.
- Compare the aggregate at both ends (the matching 'aggregate' item on this page, if there is one, says which).
- Make both ends use algorithm redundant with members in the same path order.
- Check again: rx and tx should both climb on the same tunnel.
- Also check Best Practices for “VPN allow one way only” and “asymmetric routing with one-way traffic”.
to-chicago: since the last collection received 2,462 / sent 0
# safe to share (no keys): show system ipsec-aggregate diagnose sys ipsec-aggregate list get vpn ipsec tunnel summary # The next commands print LIVE KEYS (tunnel encryption keys, pre-shared keys). Read them on the FortiGate – # never paste their output into a ticket, an email or a chat. diagnose vpn tunnel list name to-chicago - ●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 Interface 10.1.0.1 1 Init/ - 00:00:35 10.254.9.1 to-chicago 10.1.0.1 1 Full/ - 00:00:31 10.254.9.5 to-chicago-bHow 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 - Performance1
- ●1 AP at 100 Mb
- Access point(s) linked below 1 Gb – usually a bad cable or a 2-pair run: FG-ATLANTA-AP1 (100Base-TX on FG-ATLANTA-SW1 port3)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get wireless-controller wtp-statusWTP: FP231F09010001 name : FG-ATLANTA-AP1 sys name : FG-ATLANTA-SW1 port id : port3 MAU oper type : 100Base-TXHow to fix
These APs negotiated 100 Mb instead of 1 Gb, which caps every Wi-Fi client behind them. Usually a damaged cable, a bad keystone/patch, or a run with only two pairs terminated.
- Swap the patch cables at both ends.
- If it stays at 100 Mb, test/re-terminate the cable run.
- Bounce the switch port to renegotiate after a fix.
# The switch and port below are what the access point ITSELF announced (LLDP) - they were not read from the switch. # Confirm them before resetting power: the Find page, or the first command. diagnose switch-controller switch-info lldp neighbors-summary diagnose switch-controller switch-info port-stats FG-ATLANTA-SW1 port3 execute switch-controller poe-reset FG-ATLANTA-SW1 port3 - Configuration3
- ●VPN allow one way only
- 1 IPsec tunnel interface(s) have an accept policy in one direction only: to-chicago (outbound only (LAN → tunnel); policy 9, 11, 12). Without a return allow, replies die on this FortiGate and counters look one-way.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show firewall policyedit "9" edit "11"diagnose vpn tunnel listname=to-chicago ver=2 serial=1 203.0.113.19:0->203.0.113.11:0 nexthop=203.0.113.17 tun_id=203.0.113.11 tun_id6=::203.0.113.11 dst_mtu=1500 dpd-link=on weight=1 bound_if=5 lgwy=static/1 tun=intf mode=auto/1 encap=none/552 options[0228]=npu frag-rfc run_state=0 role=primary accept_traffic=1 overlay_id=0 proxyid_num=1 child_num=0 refcnt=5 ilast=0 olast=1 ad=/0 stat: rxp=90000 txp=0 rxb=12780000 txb=0 dpd: mode=on-demand on=1 status=ok idle=20000ms retry=3 count=0 seqno=223 natt: mode=none draft=0 interval=0 remote_port=0 fec: egress=0 ingress=0 proxyid=to-chicago proto=0 sa=1 ref=2 serial=1 auto-negotiate src: 0:0.0.0.0-255.255.255.255:0 dst: 0:0.0.0.0-255.255.255.255:0 SA: ref=3 options=18227 type=00 soft=0 mtu=1438 expire=9387/0B replaywin=2048 seqno=1 esn=0 replaywin_lastseq=00015f90 qat=0 rekey=0 hash_search_len=1 life: type=01 bytes=0/0 timeout=9387/43200 dec: spi=24ac0205 esp=aes key=32 <removed> ah=sha256 key=32 <removed> enc: spi=c242fdcb esp=aes key=32 <removed> ah=sha256 key=32 <removed> dec:pkts/bytes=90000/12780000, enc:pkts/bytes=0/0 npu_flag=03 npu_rgwy=203.0.113.11 npu_lgwy=203.0.113.19 npu_selid=0 dec_npuid=1 enc_npuid=1 ------------------------------------------------------How to fix
An accept firewall policy uses this IPsec tunnel interface in only one direction. Replies that need the opposite allow are dropped here, which shows up as one-way tunnel counters. Dial-up and DECOM tunnels are not listed.
- Open the listed policy and note its source, destination and services.
- Add a matching accept in the reverse direction (or a zone pair that covers both).
- Do not use `any` for WAN-facing source; keep the path as narrow as the outbound allow.
- Suggested CLI below is a sketch – replace the placeholders before pasting.
# to-chicago: add an accept with srcintf "to-chicago" toward the LAN (mirror the outbound allow) config firewall policy edit 0 set name "return-to-chicago" set srcintf "to-chicago" set dstintf "<lan-or-zone>" set srcaddr "<remote-nets>" set dstaddr "<local-nets>" set action accept set schedule always set service ALL set logtraffic all next end - ●1 stale AP entry
- 1 AP(s) configured on the FortiGate that have never connected: FG-ATLANTA-APNEW
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get wireless-controller wtp-statusWTP: FP231F09900001 wtp-id : FP231F09900001 name : FG-ATLANTA-APNEW connection-state : Disconnected join-time : N/A name: to-chicago name: to-chicago-bHow to fix
These APs are configured on the FortiGate but have never connected. They clutter the wireless controller and hide real problems. Delete the ones that no longer exist (or acknowledge them if they're still to be installed).
- Confirm they aren't APs waiting to be installed.
- Delete them on the FortiGate (below).
config wireless-controller wtp delete "FG-ATLANTA-APNEW" end - ●firmware below baseline
- 1 device(s) below the firmware baseline: FG-ATLANTA-AP1 7.2.2 (baseline 7.4.3)
How to fix
These devices run firmware older than the baseline your security team set (config.json → security → firmware_baseline). Older firmware usually means known, fixed vulnerabilities are still present.
- Check the upgrade path for each model (Fortinet upgrade path tool) and the release notes.
- Plan a maintenance window (maintenance.py add …) and upgrade – FortiGate first, then switches and APs from the FortiGate.
- If a device can't be upgraded (end of support), replace it or record the exception with the security team.
FortiAP FG-ATLANTA-AP1 (FortiAP 231F): 7.2.2 → at least 7.4.3
get system status diagnose switch-controller switch-info status get wireless-controller wtp-status
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 Atlanta floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment22 devices1 with support ended
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-ATLANTA FortiGate · FortiGate 90G | FGDEMO00090001 tag NL-0009 | Atlanta Northline | 2022-10-10 4.1 years old PO PO-55510 · Example Reseller | Standard 2029-10-30 contract NL-SUP-09 warranty 2023-10-10 passed | 2035-06-30 end of order 2030-06-30 | 2028 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-ATLANTA-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF09010001 tag NL-09S01 | Atlanta · Closet 1 · Rack 1 Network team | 2022-02-15 4.8 years old PO PO-56090 · 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-ATLANTA-SW2 FortiSwitch · FortiSwitch 124F-FPOE | S124FF09020001 tag NL-09S02 | Atlanta · Closet 2 · Rack 2 Network team | 2023-02-15 3.8 years old PO PO-56091 · 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-ATLANTA-SW3 FortiSwitch · FortiSwitch 124F-FPOE | S124FF09030001 tag NL-09S03 | Atlanta · Closet 3 · Rack 3 Network team | 2024-02-15 2.8 years old PO PO-56092 · 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-ATLANTA-SW4 FortiSwitch · FortiSwitch 124F-FPOE | S124FF09040001 tag NL-09S04 | Atlanta · Closet 4 · Rack 4 Network team | 2021-02-15 5.8 years old PO PO-56093 · 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-ATLANTA-SW5 FortiSwitch · FortiSwitch 124F-FPOE | S124FF09050001 tag NL-09S05 | Atlanta · Closet 5 · Rack 5 Network team | 2022-02-15 4.8 years old PO PO-56094 · 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-ATLANTA-AP1 FortiAP · FAP231F | FP231F09010001 tag NL-09A01 | Atlanta · Ceiling, zone 1 Network team | 2022-05-10 4.5 years old PO PO-57090 · 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-ATLANTA-AP2 FortiAP · FAP231F | FP231F09020001 tag NL-09A02 | Atlanta · Ceiling, zone 2 Network team | 2023-05-10 3.5 years old PO PO-57091 · 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-ATLANTA-AP3 FortiAP · FAP231F | FP231F09030001 tag NL-09A03 | Atlanta · Ceiling, zone 3 Network team | 2024-05-10 2.5 years old PO PO-57092 · 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-ATLANTA-AP4 FortiAP · FAP231F | FP231F09040001 tag NL-09A04 | Atlanta · Ceiling, zone 4 Network team | 2022-05-10 4.5 years old PO PO-57093 · 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-ATLANTA-AP5 FortiAP · FAP231F | FP231F09050001 tag NL-09A05 | Atlanta · Ceiling, zone 5 Network team | 2023-05-10 3.5 years old PO PO-57094 · 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-ATLANTA-AP6 FortiAP · FAP231F | FP231F09060001 tag NL-09A06 | Atlanta · Ceiling, zone 6 Network team | 2024-05-10 2.5 years old PO PO-57095 · 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-ATLANTA-AP7 FortiAP · FAP231F | FP231F09070001 tag NL-09A07 | Atlanta · Ceiling, zone 7 Network team | 2022-05-10 4.5 years old PO PO-57096 · 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-ATLANTA-AP8 FortiAP · FAP231F | FP231F09080001 tag NL-09A08 | Atlanta · Ceiling, zone 8 Network team | 2023-05-10 3.5 years old PO PO-57097 · 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-ATLANTA-AP9 FortiAP · FAP231F | FP231F09090001 tag NL-09A09 | Atlanta · Ceiling, zone 9 Network team | 2024-05-10 2.5 years old PO PO-57098 · 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-ATLANTA-AP10 FortiAP · FAP231F | FP231F09100001 tag NL-09A10 | Atlanta · Ceiling, zone 10 Network team | 2022-05-10 4.5 years old PO PO-57099 · 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-ATLANTA-AP11 FortiAP · FAP231F | FP231F09110001 tag NL-09A11 | Atlanta · Ceiling, zone 11 Network team | 2023-05-10 3.5 years old PO PO-57100 · 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-ATLANTA-AP12 FortiAP · FAP231F | FP231F09120001 tag NL-09A12 | Atlanta · Ceiling, zone 12 Network team | 2024-05-10 2.5 years old PO PO-57101 · 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-ATLANTA-AP13 FortiAP · FAP231F | FP231F09130001 tag NL-09A13 | Atlanta · Ceiling, zone 13 Network team | 2022-05-10 4.5 years old PO PO-57102 · 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-ATLANTA-AP14 FortiAP · FAP231F | FP231F09140001 tag NL-09A14 | Atlanta · Ceiling, zone 14 Network team | 2023-05-10 3.5 years old PO PO-57103 · 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-ATLANTA-AP15 FortiAP · FAP231F | FP231F09150001 tag NL-09A15 | Atlanta · Ceiling, zone 15 Network team | 2024-05-10 2.5 years old PO PO-57104 · 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-ATLANTA-AP16 FortiAP · FAP231F | FP231F09160001 tag NL-09A16 | Atlanta · Ceiling, zone 16 Network team | 2022-05-10 4.5 years old PO PO-57105 · 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 contracts2 circuits
| Circuit | Bandwidth | Ping | From | Ends | Notice | SLA | |
|---|---|---|---|---|---|---|---|
| Example Fiber Example Fiber · wan1 · NL-091 | 500/500 | 12 ms collector ping | 2025-12-15 | 2028-12-15 give notice within 664 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-092 | 300/30 | 17 ms collector ping | 2026-02-14 | 2029-02-14 give notice within 755 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.9.10.0/24 | 10.9.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Atlanta network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.9.20.0/24 | 10.9.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Atlanta network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.9.30.0/24 | 10.9.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Atlanta network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.9.40.0/24 | 10.9.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Atlanta network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.9.50.0/24 | 10.9.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Atlanta network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.9.90.0/24 | 10.9.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Atlanta 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.