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-AZUREEAST | FortiGate-VM64-AZURE | 7.4.8 | 18% | 50% | 17,660 | 39% · wan1 | — | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| No VLAN interfaces. | ||||||
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| management | management | 1 | 1 Network gear |
| port2 | port2 | 5 | 5 Computer |
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.
On-site contacts
- Jordan Hale · (219) 555-1019 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 7/18/2025 to 7/18/2028 · 604 days left · from the Library
- FortiGate WAN IP
- 203.0.113.29 /29
- Gateway
- 203.0.113.2
- Circuit ID
- NL-191
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 9/17/2023 to 9/17/2028 · 665 days left
- FortiGate WAN IP
- 198.51.100.29 /29
- Gateway
- 198.51.100.2
- Circuit ID
- NL-192
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary4 static routes · BGP · 2 neighbours · 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 | BGP | to-chicago → Chicago |
| 10.2.0.0/16 | OSPF | to-chicago → Chicago |
| 10.3.0.0/16 | OSPF | to-chicago → Chicago |
| 10.4.0.0/16 | OSPF | to-chicago → Chicago |
| 10.5.0.0/16 | OSPF | to-chicago → Chicago |
| 10.6.0.0/16 | OSPF | to-chicago → Chicago |
| 10.7.0.0/16 | OSPF | to-chicago → Chicago |
| 10.8.0.0/16 | OSPF | to-chicago → Chicago |
| 10.9.0.0/16 | OSPF | to-chicago → Chicago |
| 10.10.0.0/16 | OSPF | to-chicago → Chicago |
| 10.11.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.19.0.0/16 | Static | port2 |
| 10.19.1.0/24 | Connected | port2 local network |
| 172.16.0.0/12 | Static | blackhole (dropped) |
| 192.168.0.0/16 | Static | blackhole (dropped) |
| 198.51.100.24/29 | Connected | wan2 local network |
| 203.0.113.24/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 | Path B | 9.3 | 1.3 | 0 |
| 2026-11-22 | Path A | 8.4 | 1 | 0.2 |
| 2026-11-21 | Path B | 9.4 | 1.7 | 0 |
| 2026-11-21 | Path A | 9.4 | 1.5 | 0.2 |
| 2026-11-20 | Path B | 9 | 1.1 | 0 |
| 2026-11-20 | Path A | 8.4 | 0.7 | 0.2 |
| 2026-11-19 | Path B | 9.7 | 1.4 | 0 |
| 2026-11-19 | Path A | 8.9 | 1.6 | 0 |
| 2026-11-18 | Path B | 10.2 | 1.6 | 0 |
| 2026-11-18 | Path A | 8.9 | 1 | 0 |
| 2026-11-17 | Path B | 10.1 | 1.7 | 0.2 |
| 2026-11-17 | Path A | 9.3 | 1.6 | 0 |
| 2026-11-16 | Path B | 10.2 | 1.5 | 0 |
| 2026-11-16 | Path A | 8.1 | 1.2 | 0.2 |
| 2026-11-15 | Path B | 9.2 | 1.3 | 0 |
| 2026-11-15 | Path A | 9 | 1.1 | 0 |
| 2026-11-14 | Path B | 9.8 | 1.6 | 0.2 |
| 2026-11-14 | Path A | 9.2 | 1.5 | 0 |
| 2026-11-13 | Path B | 10 | 1.4 | 0 |
| 2026-11-13 | Path A | 8 | 1.5 | 0.2 |
| 2026-11-12 | Path B | 9.7 | 0.8 | 0 |
| 2026-11-12 | Path A | 9.1 | 1 | 0 |
| 2026-11-11 | Path B | 8.9 | 1.7 | 0.2 |
| 2026-11-11 | Path A | 8.9 | 1.9 | 0 |
| 2026-11-10 | Path B | 10.3 | 1.4 | 0 |
| 2026-11-10 | Path A | 8.2 | 2.1 | 0 |
| 2026-11-09 | Path B | 9.6 | 1.7 | 0 |
| 2026-11-09 | Path A | 8.7 | 1.6 | 0 |
| 2026-11-08 | Path B | 9.3 | 1.9 | 0.2 |
| 2026-11-08 | Path A | 9.3 | 1.7 | 0 |
| 2026-11-07 | Path B | 10 | 1.3 | 0 |
| 2026-11-07 | Path A | 8.3 | 1.8 | 0 |
| 2026-11-06 | Path B | 10.4 | 1.4 | 0 |
| 2026-11-06 | Path A | 9.3 | 1.3 | 0.2 |
| 2026-11-05 | Path B | 10.7 | 1.4 | 0 |
| 2026-11-05 | Path A | 8.9 | 1.4 | 0.5 |
| 2026-11-04 | Path B | 9.9 | 1.1 | 0 |
| 2026-11-04 | Path A | 8.5 | 1.8 | 0 |
| 2026-11-03 | Path B | 9.6 | 1.8 | 0 |
| 2026-11-03 | Path A | 8.1 | 1.4 | 0 |
| 2026-11-02 | Path B | 9.8 | 1.4 | 0 |
| 2026-11-02 | Path A | 8.8 | 0.8 | 0.2 |
| 2026-11-01 | Path B | 8.5 | 1.1 | 0 |
| 2026-11-01 | Path A | 9.2 | 0.9 | 0 |
| 2026-10-31 | Path B | 9.3 | 1.1 | 0 |
| 2026-10-31 | Path A | 9 | 1.9 | 0 |
| 2026-10-30 | Path B | 10.5 | 1.6 | 0 |
| 2026-10-30 | Path A | 8.9 | 1.4 | 0 |
| 2026-10-29 | Path B | 9.9 | 1.5 | 0.2 |
| 2026-10-29 | Path A | 8.6 | 1.2 | 0 |
| 2026-10-28 | Path B | 9.9 | 1.2 | 0.2 |
| 2026-10-28 | Path A | 8.4 | 1.4 | 0 |
| 2026-10-27 | Path B | 10.6 | 1.2 | 0.2 |
| 2026-10-27 | Path A | 9.4 | 1.7 | 0 |
| 2026-10-26 | Path B | 10.7 | 1.4 | 0 |
| 2026-10-26 | Path A | 8.9 | 1.4 | 0 |
| 2026-10-25 | Path B | 8.8 | 1.4 | 0 |
| 2026-10-25 | Path A | 8.1 | 1.7 | 0 |
| 2026-10-24 | Path B | 10.3 | 1.9 | 0 |
| 2026-10-24 | Path A | 9.4 | 1.2 | 0 |
| 2026-10-23 | Path B | 9.5 | 0.7 | 0.2 |
| 2026-10-23 | Path A | 9.3 | 1.4 | 0 |
Tunnel stability – last 7 days
2 tunnels · 2 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 2
| When | Type | What | Detail |
|---|---|---|---|
| Nov 5 4:43 PM | Config | Firewall policy 55 | added: users → internet, HTTPS and DNS, log all |
| Nov 2 1:41 PM | Config | Firewall policy 24 | added: users → internet, HTTPS and DNS, log all |
New and moved devices – last 30 days 0
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.
Nothing recorded yet.
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
- Monitoring & housekeeping1
- ●Licence 3 days
- Licence: FortiGate-VM licence expires in 3 days (Nov 25 2026)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get system statusFortiGate-VM licence: 2026-11-25How to fix
The FortiGate-VM licence expires 2026-11-25 – after that the VM stops passing traffic.
- 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 Azure East floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment1 device
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-AZUREEAST FortiGate · FortiGate VM AZURE | FGDEMO00190001 tag NL-0019 | Virginia Northline | 2024-12-26 1.9 years old PO PO-55520 · Example Reseller | Standard 2027-07-23 contract NL-SUP-19 warranty 2025-12-26 passed | 2029-06-01 | 2030 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 | |
|---|---|---|---|---|---|---|---|
| Path A Path A · wan1 · NL-191 | 500/500 | 7 ms collector ping | 2025-07-18 | 2028-07-18 give notice within 514 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Path B Path B · wan2 · NL-192 | 300/30 | 11 ms collector ping | 2023-09-17 | 2028-09-17 give notice within 605 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.
Documents0 documents
The demo shows Service desk articles only.
For every site0 documents
The demo shows Service desk articles only.