Needs attention 1
- Performance1
- ▲Example Fiber gateway slow ping
- Collector ping to Example Fiber gateway (203.0.113.17): 289 ms, 0% loss
How to fix
The collector can ping Example Fiber gateway, but latency or loss is high.
- Confirm the address still answers from the collector (ping).
- Check routing and firewall policy between the collector and the target.
- If this is an ISP gateway, check the circuit on Circuits & contacts.
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-DENVER | FortiGate-90G | 7.4.8 | 16% | 48% | 5,961 | 37% · wan1 | — | Working, needs a look |
Switches44 · 0 need a look · PoE 197 of 1480 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-DENVER-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 64 of 370 W | — | FG-DENVER-SW2 port28 (port25) | 7.4.5 | Working normally | |
| FG-DENVER-SW2 | FortiSwitch 124F-FPOE | 13 / 28 | 47 of 370 W | — | FG-DENVER-SW4 port28 (port25) | 7.4.5 | Working normally | |
| FG-DENVER-SW3 | FortiSwitch 124F-FPOE | 6 / 28 | 33 of 370 W | — | FG-DENVER-SW1 port26 (port28) | 7.4.5 | Working normally | |
| FG-DENVER-SW4 | FortiSwitch 124F-FPOE | 8 / 28 | 52 of 370 W | — | FG-DENVER-SW2 port25 (port28) | 7.4.5 | Working normally |
Access points1414 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-DENVER-AP1 | FP231F | — | — | — | — | FG-DENVER-SW1 port3 | 7.4.3 | Working normally | |
| FG-DENVER-AP10 | FP231F | — | — | — | — | FG-DENVER-SW2 port5 | 7.4.3 | Working normally | |
| FG-DENVER-AP11 | FP231F | — | — | — | — | FG-DENVER-SW3 port5 | 7.4.3 | Working normally | |
| FG-DENVER-AP12 | FP231F | — | — | — | — | FG-DENVER-SW4 port5 | 7.4.3 | Working normally | |
| FG-DENVER-AP13 | FP231F | — | — | — | — | FG-DENVER-SW1 port6 | 7.4.3 | Working normally | |
| FG-DENVER-AP14 | FP231F | — | — | — | — | FG-DENVER-SW2 port6 | 7.4.3 | Working normally | |
| FG-DENVER-AP2 | FP231F | — | — | — | — | FG-DENVER-SW2 port3 | 7.4.3 | Working normally | |
| FG-DENVER-AP3 | FP231F | — | — | — | — | FG-DENVER-SW3 port3 | 7.4.3 | Working normally | |
| FG-DENVER-AP4 | FP231F | — | — | — | — | FG-DENVER-SW4 port3 | 7.4.3 | Working normally | |
| FG-DENVER-AP5 | FP231F | — | — | — | — | FG-DENVER-SW1 port4 | 7.4.3 | Working normally | |
| FG-DENVER-AP6 | FP231F | — | — | — | — | FG-DENVER-SW2 port4 | 7.4.3 | Working normally | |
| FG-DENVER-AP7 | FP231F | — | — | — | — | FG-DENVER-SW3 port4 | 7.4.3 | Working normally | |
| FG-DENVER-AP8 | FP231F | — | — | — | — | FG-DENVER-SW4 port4 | 7.4.3 | Working normally | |
| FG-DENVER-AP9 | FP231F | — | — | — | — | FG-DENVER-SW1 port5 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.10.10.0/24 | 10.10.10.1 | 255.255.255.0 /24 | 10.10.10.20 – 10.10.10.250 231 addresses · 33 in use · lease 8 hours | |
| 20 | voice | 10.10.20.0/24 | 10.10.20.1 | 255.255.255.0 /24 | 10.10.20.20 – 10.10.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.10.30.0/24 | 10.10.30.1 | 255.255.255.0 /24 | 10.10.30.20 – 10.10.30.250 231 addresses · 0 in use · lease 7 days · 7 reserved | |
| 40 | printers | 10.10.40.0/24 | 10.10.40.1 | 255.255.255.0 /24 | 10.10.40.100 – 10.10.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.10.50.0/24 | 10.10.50.1 | 255.255.255.0 /24 | 10.10.50.20 – 10.10.50.250 231 addresses · 1 in use · lease 7 days | |
| 90 | iot | 10.10.90.0/24 | 10.10.90.1 | 255.255.255.0 /24 | 10.10.90.100 – 10.10.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.10.0/24 | 10.255.10.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 20 | 16 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 | 4 | 4 Network gear |
| 10 | users | 14 | 14 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.
4 switches · 41 ports in use · 71 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 closet4 closets41 of 112 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Denver | Closet 1 FG-DENVER-SW1 | 14 / 28 (50%) | 12 | 12 | 64 / 370 W (17%) 306 W headroom | |
| Denver | Closet 2 FG-DENVER-SW2 | 13 / 28 (46%) | 13 | 13 | 47 / 370 W (13%) 323 W headroom | |
| Denver | Closet 3 FG-DENVER-SW3 | 6 / 28 (21%) | 19 | 19 | 33 / 370 W (9%) 337 W headroom | |
| Denver | Closet 4 FG-DENVER-SW4 | 8 / 28 (29%) | 17 | 17 | 52 / 370 W (14%) 318 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-DENVER-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 64 / 370 W · 3 fiber ports · 40 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-DENVER-AP1 FortiAP | 10 users | 10.10.10.20 · 00:11:22:0a:00:00 2 Wi-Fi clients list | 13.5 W class 4 | |
| port4 | Up | FG-DENVER-AP5 FortiAP | 10 users | 10.10.10.24 · 00:11:22:0a:00:04 1 Wi-Fi client list | 10.2 W class 4 | |
| port5 | Up | FG-DENVER-AP9 FortiAP | 10 users | 10.10.10.28 · 00:11:22:0a:00:08 1 Wi-Fi client list | 13.3 W class 4 | |
| port6 | Up | FG-DENVER-AP13 FortiAP | 10 users | 10.10.10.32 · 00:11:22:0a:00:0c 1 Wi-Fi client list | 13.1 W class 4 | |
| port13 | Up | NL-DEN-PC011 | 10 users | 10.10.10.120 · d0:43:1e:0a:0a:01 | ||
| port14 | Up | NL-DEN-LT012 | 10 users | 10.10.10.121 · d0:43:1e:0a:0a:02 | ||
| port15 | Up | NL-DEN-PC013 | 10 users | 10.10.10.122 · d0:43:1e:0a:0a:03 | ||
| port16 | Up | NL-DEN-PH01 phone | 20 voice | 10.10.20.20 · 00:04:f2:0a:14:01 | 4.5 W class 2 | |
| port17 | Up | NL-DEN-PH02 phone | 20 voice | 10.10.20.21 · 00:04:f2:0a:14:02 | 3.8 W class 2 | |
| port18 | Up | PRN-DEN-01 | 40 printers | 10.10.40.20 · 3c:2a:f4:0a:28:01 | ||
| port19 | Up | CAM-DOCK-01 | 50 cameras | 10.10.50.20 · 00:40:8c:0a:32:01 | 5.7 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00100001 | ||||
| port25 | Up | ↔ FG-DENVER-SW2 port28 trunk S124FF10020001-0 | Fiber 10G-SR | |||
| port26 | Up | ↔ FG-DENVER-SW3 port28 trunk S124FF10030001-0 | Fiber 10G-SR |
Free ports: port1–2, port7–12, port20–23, port27–28
Optics with no link: port28 (10G-SR, no light)
S124FF10010001 · FortiSwitchOS 7.4.5
FG-DENVER-SW2 FortiSwitch 124F-FPOE · Closet 213 in use · 15 free · PoE 47 / 370 W · 2 fiber ports · 44 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-DENVER-AP2 FortiAP | 10 users | 10.10.10.21 · 00:11:22:0a:00:01 2 Wi-Fi clients list | 12.1 W class 4 | |
| port4 | Up | FG-DENVER-AP6 FortiAP | 10 users | 10.10.10.25 · 00:11:22:0a:00:05 1 Wi-Fi client list | 11.9 W class 4 | |
| port5 | Up | FG-DENVER-AP10 FortiAP | 10 users | 10.10.10.29 · 00:11:22:0a:00:09 1 Wi-Fi client list | 11.8 W class 4 | |
| port6 | Up | FG-DENVER-AP14 FortiAP | 10 users | 10.10.10.33 · 00:11:22:0a:00:0d 1 Wi-Fi client list | 11.3 W class 4 | |
| port7 | Up | DC01 | 30 servers | 10.10.30.2 · f8:bc:12:82:cc:de | ||
| port8 | Up | FILE01 | 30 servers | 10.10.30.3 · f8:bc:12:2e:c8:39 | ||
| port9 | Up | WMS01 | 30 servers | 10.10.30.4 · f8:bc:12:58:43:54 | ||
| port10 | Up | BACKUP01 | 30 servers | 10.10.30.5 · c4:cb:e1:74:eb:75 | ||
| port11 | Up | IPERF01 | 30 servers | 10.10.30.6 · f8:bc:12:12:f1:24 | ||
| port12 | Up | NAS01 | 30 servers | 10.10.30.7 · 00:11:32:b0:fe:ed | ||
| port13 | Up | UPS-MDF | 30 servers | 10.10.30.8 · 00:c0:b7:80:21:d0 | ||
| port25 | Up | ↔ FG-DENVER-SW4 port28 trunk S124FF10040001-0 | Fiber 10G-LR | |||
| port28 | Up | ↔ FG-DENVER-SW1 port25 trunk S124FF10010001-0 | Fiber 10G-SR |
Free ports: port1–2, port14–24, port26–27
S124FF10020001 · FortiSwitchOS 7.4.5
FG-DENVER-SW3 FortiSwitch 124F-FPOE · Closet 36 in use · 22 free · PoE 33 / 370 W · 1 fiber port · 42 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-DENVER-AP3 FortiAP | 10 users | 10.10.10.22 · 00:11:22:0a:00:02 1 Wi-Fi client list | 13.2 W class 4 | |
| port4 | Up | FG-DENVER-AP7 FortiAP | 10 users | 10.10.10.26 · 00:11:22:0a:00:06 1 Wi-Fi client list | 9.9 W class 4 | |
| port5 | Up | FG-DENVER-AP11 FortiAP | 10 users | 10.10.10.30 · 00:11:22:0a:00:0a 1 Wi-Fi client list | 10.2 W class 4 | |
| port14 | Up | DOCK-DEN-01 | 90 iot | 10.10.90.30 · 00:07:4d:47:25:6d | ||
| port15 | Up | DOCK-DEN-02 | 90 iot | 10.10.90.31 · 00:07:4d:be:39:c7 | ||
| port28 | Up | ↔ FG-DENVER-SW1 port26 trunk S124FF10010001-0 | Fiber 10G-SR |
Free ports: port1–2, port6–13, port16–27
S124FF10030001 · FortiSwitchOS 7.4.5
FG-DENVER-SW4 FortiSwitch 124F-FPOE · Closet 48 in use · 20 free · PoE 52 / 370 W · 1 fiber port · 39 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-DENVER-AP4 FortiAP | 10 users | 10.10.10.23 · 00:11:22:0a:00:03 1 Wi-Fi client list | 11.3 W class 4 | |
| port4 | Up | FG-DENVER-AP8 FortiAP | 10 users | 10.10.10.27 · 00:11:22:0a:00:07 1 Wi-Fi client list | 10.2 W class 4 | |
| port5 | Up | FG-DENVER-AP12 FortiAP | 10 users | 10.10.10.31 · 00:11:22:0a:00:0b 1 Wi-Fi client list | 13.9 W class 4 | |
| port7 | Up | PAGE-WHSE | 20 voice | 10.10.20.2 · 00:22:ee:2b:19:0d | 6.4 W class 3 | |
| port9 | Up | DOOR-DOCK1 | 90 iot | 10.10.90.2 · 00:06:8e:4c:e5:8f | 4.2 W class 2 | |
| port10 | Up | DOOR-DOCK2 | 90 iot | 10.10.90.3 · 00:06:8e:02:7f:fc | 4.2 W class 2 | |
| port11 | Up | ENV-FREEZER | 90 iot | 10.10.90.4 · b8:27:eb:0e:7c:54 | 1.9 W class 1 | |
| port28 | Up | ↔ FG-DENVER-SW2 port25 trunk S124FF10020001-0 | Fiber 10G-LR |
Free ports: port1–2, port6, port8, port12–27
S124FF10040001 · FortiSwitchOS 7.4.5
Address
On-site contacts
- Chris Nguyen · (210) 555-1010 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 5/1/2026 to 5/1/2029 · 891 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.20 /29
- Gateway
- 203.0.113.17
- Circuit ID
- NL-101
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 7/1/2024 to 7/1/2029 · 952 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.20 /29
- Gateway
- 198.51.100.17
- Circuit ID
- NL-102
- 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 → 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.10.0/24 | Connected | users local network |
| 10.10.20.0/24 | Connected | voice local network |
| 10.10.30.0/24 | Connected | servers local network |
| 10.10.40.0/24 | Connected | printers local network |
| 10.10.50.0/24 | Connected | cameras local network |
| 10.10.90.0/24 | Connected | iot local network |
| 10.11.0.0/16 | OSPF | to-chicago → Chicago |
| 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.255.10.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.2 | 1.2 | 0 |
| 2026-11-22 | Example Fiber | 285.7 | 1.1 | 0 |
| 2026-11-21 | Metro Cable | 8.8 | 1.3 | 0 |
| 2026-11-21 | Example Fiber | 328.5 | 0.8 | 0 |
| 2026-11-20 | Metro Cable | 9 | 1.6 | 0 |
| 2026-11-20 | Example Fiber | 302 | 1.3 | 0 |
| 2026-11-19 | Metro Cable | 9.7 | 1.6 | 0 |
| 2026-11-19 | Example Fiber | 326.5 | 1.3 | 0 |
| 2026-11-18 | Metro Cable | 10 | 1.8 | 0 |
| 2026-11-18 | Example Fiber | 300.8 | 1.6 | 0.2 |
| 2026-11-17 | Metro Cable | 9.5 | 1.2 | 0.5 |
| 2026-11-17 | Example Fiber | 306.1 | 1.6 | 0 |
| 2026-11-16 | Metro Cable | 10.2 | 1.7 | 0.5 |
| 2026-11-16 | Example Fiber | 321.2 | 1.4 | 0.2 |
| 2026-11-15 | Metro Cable | 9.9 | 1.3 | 0.2 |
| 2026-11-15 | Example Fiber | 323.7 | 1.1 | 0 |
| 2026-11-14 | Metro Cable | 10.8 | 1.2 | 0.2 |
| 2026-11-14 | Example Fiber | 310.3 | 0.9 | 0 |
| 2026-11-13 | Metro Cable | 10.2 | 1 | 0 |
| 2026-11-13 | Example Fiber | 330.6 | 1.7 | 0 |
| 2026-11-12 | Metro Cable | 10.3 | 1.5 | 0 |
| 2026-11-12 | Example Fiber | 282.9 | 1.5 | 0 |
| 2026-11-11 | Metro Cable | 9.6 | 1.9 | 0 |
| 2026-11-11 | Example Fiber | 318.1 | 1.4 | 0 |
| 2026-11-10 | Metro Cable | 9.6 | 1.1 | 0 |
| 2026-11-10 | Example Fiber | 308.2 | 1.2 | 0 |
| 2026-11-09 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-09 | Example Fiber | 296.6 | 1.5 | 0 |
| 2026-11-08 | Metro Cable | 10.1 | 0.7 | 0.2 |
| 2026-11-08 | Example Fiber | 263.5 | 1.7 | 0.2 |
| 2026-11-07 | Metro Cable | 8.8 | 1.3 | 0 |
| 2026-11-07 | Example Fiber | 303.9 | 1.3 | 0 |
| 2026-11-06 | Metro Cable | 10.2 | 1.4 | 0 |
| 2026-11-06 | Example Fiber | 281.7 | 1.3 | 0.2 |
| 2026-11-05 | Metro Cable | 9.3 | 1.2 | 0 |
| 2026-11-05 | Example Fiber | 285.1 | 1.7 | 0 |
| 2026-11-04 | Metro Cable | 8.9 | 1.8 | 0 |
| 2026-11-04 | Example Fiber | 322.1 | 1.3 | 0 |
| 2026-11-03 | Metro Cable | 9.8 | 1.2 | 0 |
| 2026-11-03 | Example Fiber | 329.9 | 1.4 | 0 |
| 2026-11-02 | Metro Cable | 9.5 | 1.3 | 0 |
| 2026-11-02 | Example Fiber | 313.1 | 1.9 | 0 |
| 2026-11-01 | Metro Cable | 9.7 | 1.2 | 0 |
| 2026-11-01 | Example Fiber | 292.4 | 1.8 | 0.2 |
| 2026-10-31 | Metro Cable | 9.5 | 1.5 | 0.2 |
| 2026-10-31 | Example Fiber | 301.7 | 1.3 | 0 |
| 2026-10-30 | Metro Cable | 9.8 | 1.7 | 0 |
| 2026-10-30 | Example Fiber | 294 | 1.6 | 0 |
| 2026-10-29 | Metro Cable | 9.3 | 1 | 0.2 |
| 2026-10-29 | Example Fiber | 322.4 | 1.1 | 0.2 |
| 2026-10-28 | Metro Cable | 9.6 | 1.5 | 0 |
| 2026-10-28 | Example Fiber | 287.2 | 1 | 0 |
| 2026-10-27 | Metro Cable | 9.5 | 1.2 | 0 |
| 2026-10-27 | Example Fiber | 285.5 | 1.2 | 0.2 |
| 2026-10-26 | Metro Cable | 9.5 | 1.8 | 0 |
| 2026-10-26 | Example Fiber | 290.1 | 1.5 | 0 |
| 2026-10-25 | Metro Cable | 9.9 | 1.1 | 0.2 |
| 2026-10-25 | Example Fiber | 296.1 | 1.7 | 0.2 |
| 2026-10-24 | Metro Cable | 9 | 1.6 | 0 |
| 2026-10-24 | Example Fiber | 283.4 | 0.8 | 0 |
| 2026-10-23 | Metro Cable | 10.6 | 1.6 | 0 |
| 2026-10-23 | Example Fiber | 308.3 | 1.2 | 0 |
Tunnel stability – last 7 days
2 tunnels · 2 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 3
| When | Type | What | Detail |
|---|---|---|---|
| Nov 12 10:33 AM | Config | Service NL-ERP | added: TCP 8443-8445 |
| Nov 10 1:27 PM | Config | Service NL-ERP | added: TCP 8443-8445 |
| Oct 29 10:27 AM | Config | Static route 49 | added: dst 10.200.0.0 255.255.0.0, device to-chicago |
New and moved devices – last 30 days 2
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 19 4:49 PM | Device movedWi-Fi | Device moved 90:75:de:0a:aa:01 | 10.10.10.80 FG-DENVER-SW1 port7 → FG-DENVER-SW1 port3 |
| Oct 25 8:27 AM | New deviceWired | New device 00:04:f2:0a:14:01 | 10.10.20.20 NL-DEN-PH01 on FG-DENVER-SW1 port16 |
Worth fixing when there's time. Security items are listed first and marked in red. Open is the default. A muted, hidden, accepted or won't-fix note stays here and does not change the colour.
How this works
- Redundancy reduced1
- ●IPsec errors climbing
- 1 tunnel(s) with IPsec errors climbing since the last comparison: to-chicago (rx 41 / tx 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): 61080/41 tx(pkt,err): 63800/0How to fix
IPsec error counters on these tunnels have climbed since the last comparison. These are the tunnel's own drop counts, not WAN health-check loss.
- Check the tunnel from both ends (below).
- A selector 2/1 often means one phase 2 is down – enable auto-negotiate, or the two ends' selectors disagree.
- Errors climbing: look at the phase-2 proposal and whether anti-replay is dropping because return traffic arrives on a different member.
to-chicago: selectors 1/1, errors +rx 41 / +tx 0
# safe to share (no keys): get vpn ipsec tunnel summary show vpn ipsec phase2-interface # 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 - Performance2
- ●Example Fiber slow
- WAN Example Fiber (wan1) is slow on 1 of 1 health checks – worst: 280 ms, 1 ms jitter, 0% loss (Internet)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
diagnose sys sdwan health-checkHealth Check(Internet): Seq(1 wan1): state(alive), packet-loss(0.000%) latency(280.000), jitter(1.000), mos(4.300), bandwidth-up(400000), bandwidth-dw(400000), bandwidth-bi(800000) sla_map=0x0How to fix
The Example Fiber connection is up but over its limits (latency 150 ms, jitter 30 ms, loss 2%). Calls and remote desktops suffer first.
- Check whether the link is simply full (bandwidth use on the port).
- If it persists and the link isn't full, open a ticket with the ISP.
- Cellular / satellite links have looser limits; to tune them, set "sla" on that ISP in the site file.
diagnose sys sdwan health-check diagnose netlink interface list wan1 - ●1 optic to check
- FG-DENVER-SW1 port28: 10G-Base-SR INSERT, receive LOS – remove the optic if the port is unused
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get system interface transceiver / modules summaryFG-DENVER-SW1 port28: 10G-Base-SR INSERT, receive LOS – remove the optic if the port is unusedHow 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.
FG-DENVER-SW1 port28
get system interface transceiver diagnose switch-controller switch-info modules summary <switch> diagnose switch-controller switch-info modules detail <switch> <port> - Monitoring & housekeeping1
- ●collector
- 1 collector command(s) failed: get router info ospf neighbor
How to fix
Some read-only commands failed on this FortiGate, so parts of the page may be missing. Usually a command that doesn't exist on this model/firmware, or isn't allowed for the netmap account.
- Look at the failed commands below; run one by hand as netmap to see the error.
- If it doesn't apply to this model, it can be skipped – send the error to whoever maintains Vantage.
get router info ospf neighbor
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 Denver 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-DENVER FortiGate · FortiGate 90G | FGDEMO00100001 tag NL-0010 | Denver Northline | 2023-03-17 3.7 years old PO PO-55511 · Example Reseller | Standard 2027-08-19 contract NL-SUP-10 warranty 2024-03-17 passed | 2035-06-30 end of order 2030-06-30 | 2029 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-DENVER-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF10010001 tag NL-10S01 | Denver · Closet 1 · Rack 1 Network team | 2023-02-15 3.8 years old PO PO-56100 · 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: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-DENVER-SW2 FortiSwitch · FortiSwitch 124F-FPOE | S124FF10020001 tag NL-10S02 | Denver · Closet 2 · Rack 2 Network team | 2024-02-15 2.8 years old PO PO-56101 · 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-DENVER-SW3 FortiSwitch · FortiSwitch 124F-FPOE | S124FF10030001 tag NL-10S03 | Denver · Closet 3 · Rack 3 Network team | 2021-02-15 5.8 years old PO PO-56102 · 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-DENVER-SW4 FortiSwitch · FortiSwitch 124F-FPOE | S124FF10040001 tag NL-10S04 | Denver · Closet 4 · Rack 4 Network team | 2022-02-15 4.8 years old PO PO-56103 · 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-DENVER-AP1 FortiAP · FAP231F | FP231F10010001 tag NL-10A01 | Denver · Ceiling, zone 1 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-DENVER-AP2 FortiAP · FAP231F | FP231F10020001 tag NL-10A02 | Denver · Ceiling, zone 2 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-DENVER-AP3 FortiAP · FAP231F | FP231F10030001 tag NL-10A03 | Denver · Ceiling, zone 3 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-DENVER-AP4 FortiAP · FAP231F | FP231F10040001 tag NL-10A04 | Denver · Ceiling, zone 4 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-DENVER-AP5 FortiAP · FAP231F | FP231F10050001 tag NL-10A05 | Denver · Ceiling, zone 5 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-DENVER-AP6 FortiAP · FAP231F | FP231F10060001 tag NL-10A06 | Denver · Ceiling, zone 6 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. |
| FG-DENVER-AP7 FortiAP · FAP231F | FP231F10070001 tag NL-10A07 | Denver · Ceiling, zone 7 Network team | 2023-05-10 3.5 years old PO PO-57106 · 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-DENVER-AP8 FortiAP · FAP231F | FP231F10080001 tag NL-10A08 | Denver · Ceiling, zone 8 Network team | 2024-05-10 2.5 years old PO PO-57107 · 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-DENVER-AP9 FortiAP · FAP231F | FP231F10090001 tag NL-10A09 | Denver · Ceiling, zone 9 Network team | 2022-05-10 4.5 years old PO PO-57108 · 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-DENVER-AP10 FortiAP · FAP231F | FP231F10100001 tag NL-10A10 | Denver · Ceiling, zone 10 Network team | 2023-05-10 3.5 years old PO PO-57109 · 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-DENVER-AP11 FortiAP · FAP231F | FP231F10110001 tag NL-10A11 | Denver · Ceiling, zone 11 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-DENVER-AP12 FortiAP · FAP231F | FP231F10120001 tag NL-10A12 | Denver · Ceiling, zone 12 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-DENVER-AP13 FortiAP · FAP231F | FP231F10130001 tag NL-10A13 | Denver · Ceiling, zone 13 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-DENVER-AP14 FortiAP · FAP231F | FP231F10140001 tag NL-10A14 | Denver · Ceiling, zone 14 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. |
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-101 | 500/500 | 289 ms collector ping | 2026-05-01 | 2029-05-01 give notice within 801 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-102 | 300/30 | 14 ms collector ping | 2024-07-01 | 2029-07-01 give notice within 892 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.10.10.0/24 | 10.10.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Denver network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.10.20.0/24 | 10.10.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Denver network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.10.30.0/24 | 10.10.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Denver network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.10.40.0/24 | 10.10.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Denver network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.10.50.0/24 | 10.10.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Denver network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.10.90.0/24 | 10.10.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Denver 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.