Needs attention 1
- Monitoring & housekeeping1
- ▲data 30 h old
- Data is 30 hours old – last successful collection Nov 21, 10:16 AM
How to fix
No successful collection for over a day – everything on this page may be out of date.
- Check the scheduled task ran (Task Scheduler → History of the hourly task).
- Read the latest log in C:\netmap\logs – a failed site's line ends with a diagnosis.
- Run the hourly task now and read the log again (manual runs go through the task – only its account can read the key).
# on NET-DEMO01 (elevated PowerShell): Start-ScheduledTask "Vantage hourly" Get-Content (Get-ChildItem C:\netmap\logs\daily-*.log | Sort-Object LastWriteTime | Select-Object -Last 1) -Encoding UTF8 -Tail 30
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-MIAMI | FortiGate-40F | 7.4.8 | 18% | 50% | 792 | 23% · wan1 | — | Working, needs a look |
Switches11 · 0 need a look · PoE 46 of 370 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-MIAMI-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 46 of 370 W | — | — | 7.4.5 | Working normally |
Access points22 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-MIAMI-AP1 | FP231F | — | — | — | — | FG-MIAMI-SW1 port3 | 7.4.3 | Working normally | |
| FG-MIAMI-AP2 | FP231F | — | — | — | — | FG-MIAMI-SW1 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.14.10.0/24 | 10.14.10.1 | 255.255.255.0 /24 | 10.14.10.20 – 10.14.10.250 231 addresses · 5 in use · lease 8 hours | |
| 20 | voice | 10.14.20.0/24 | 10.14.20.1 | 255.255.255.0 /24 | 10.14.20.20 – 10.14.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.14.30.0/24 | 10.14.30.1 | 255.255.255.0 /24 | 10.14.30.20 – 10.14.30.250 231 addresses · 0 in use · lease 7 days · 3 reserved | |
| 40 | printers | 10.14.40.0/24 | 10.14.40.1 | 255.255.255.0 /24 | 10.14.40.100 – 10.14.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.14.50.0/24 | 10.14.50.1 | 255.255.255.0 /24 | 10.14.50.100 – 10.14.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.14.90.0/24 | 10.14.90.1 | 255.255.255.0 /24 | 10.14.90.100 – 10.14.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.14.0/24 | 10.255.14.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 4 | 3 Computer · 1 Network gear |
| 20 | voice | 2 | 2 Phone (VoIP) |
| 30 | servers | 3 | 2 Storage / server · 1 UPS / power |
| 40 | printers | 1 | 1 Printer |
| 50 | cameras | 1 | 1 Camera |
| 90 | iot | 1 | 1 IoT / industrial (by network) |
| FortiLink | FortiLink | 1 | 1 Network gear |
| 10 | users | 2 | 2 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.
1 switches · 14 ports in use · 14 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 closet1 closet14 of 28 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Miami | Closet 1 FG-MIAMI-SW1 | 14 / 28 (50%) | 10 | 10 | 46 / 370 W (12%) 324 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-MIAMI-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 46 / 370 W · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-MIAMI-AP1 FortiAP | 10 users | 10.14.10.20 · 00:11:22:0e:00:00 | 13.8 W class 4 | |
| port4 | Up | FG-MIAMI-AP2 FortiAP | 10 users | 10.14.10.21 · 00:11:22:0e:00:01 | 13.9 W class 4 | |
| port7 | Up | FILE01 | 30 servers | 10.14.30.2 · f8:bc:12:0b:fd:59 | ||
| port8 | Up | IPERF01 | 30 servers | 10.14.30.3 · f8:bc:12:5e:da:ac | ||
| port9 | Up | UPS-MDF | 30 servers | 10.14.30.4 · 00:c0:b7:33:7d:a7 | ||
| port10 | Up | DOOR-FRONT | 90 iot | 10.14.90.2 · 00:06:8e:08:dd:22 | 4.2 W class 2 | |
| port13 | Up | NL-MIA-PC011 | 10 users | 10.14.10.120 · d0:43:1e:0e:0a:01 | ||
| port14 | Up | NL-MIA-LT012 | 10 users | 10.14.10.121 · d0:43:1e:0e:0a:02 | ||
| port15 | Up | NL-MIA-PC013 | 10 users | 10.14.10.122 · d0:43:1e:0e:0a:03 | ||
| port16 | Up | NL-MIA-PH01 phone | 20 voice | 10.14.20.20 · 00:04:f2:0e:14:01 | 4.8 W class 2 | |
| port17 | Up | NL-MIA-PH02 phone | 20 voice | 10.14.20.21 · 00:04:f2:0e:14:02 | 4.1 W class 2 | |
| port18 | Up | PRN-MIA-01 | 40 printers | 10.14.40.20 · 3c:2a:f4:0e:28:01 | ||
| port19 | Up | CAM-LOBBY-01 | 50 cameras | 10.14.50.20 · 00:40:8c:0e:32:01 | 5.3 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00140001 |
Free ports: port1–2, port5–6, port11–12, port20–23, port25–28
S124FF14010001 · FortiSwitchOS 7.4.5
Address
On-site contacts
- Riley Okonkwo · (214) 555-1014 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 12/30/2021 to 12/30/2026 · 38 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.24 /29
- Gateway
- 203.0.113.4
- Circuit ID
- NL-141
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 12/1/2025 to 12/1/2028 · 740 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.24 /29
- Gateway
- 198.51.100.4
- Circuit ID
- NL-142
- 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.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.10.0/24 | Connected | users local network |
| 10.14.20.0/24 | Connected | voice local network |
| 10.14.30.0/24 | Connected | servers local network |
| 10.14.40.0/24 | Connected | printers local network |
| 10.14.50.0/24 | Connected | cameras local network |
| 10.14.90.0/24 | Connected | iot local network |
| 10.16.0.0/16 | OSPF | to-chicago → Chicago |
| 10.17.0.0/16 | OSPF | to-chicago → Chicago |
| 10.255.14.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.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 | Metro Cable | 9.8 | 1.4 | 0 |
| 2026-11-22 | Example Fiber | 8 | 1.3 | 0 |
| 2026-11-21 | Metro Cable | 9.2 | 1.6 | 0 |
| 2026-11-21 | Example Fiber | 8.8 | 1.4 | 0 |
| 2026-11-20 | Metro Cable | 10.2 | 1.7 | 0 |
| 2026-11-20 | Example Fiber | 8.6 | 1.7 | 0 |
| 2026-11-19 | Metro Cable | 9.4 | 1.2 | 0.2 |
| 2026-11-19 | Example Fiber | 8.8 | 1.5 | 0.2 |
| 2026-11-18 | Metro Cable | 9.4 | 1.9 | 0 |
| 2026-11-18 | Example Fiber | 8.3 | 1.4 | 0 |
| 2026-11-17 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-17 | Example Fiber | 8.3 | 1 | 0 |
| 2026-11-16 | Metro Cable | 10 | 1.4 | 0.5 |
| 2026-11-16 | Example Fiber | 8.8 | 1.2 | 0 |
| 2026-11-15 | Metro Cable | 9.9 | 1.7 | 0 |
| 2026-11-15 | Example Fiber | 8.1 | 1.3 | 0 |
| 2026-11-14 | Metro Cable | 9.8 | 1.6 | 0 |
| 2026-11-14 | Example Fiber | 8 | 0.9 | 0 |
| 2026-11-13 | Metro Cable | 8.6 | 1.6 | 0.2 |
| 2026-11-13 | Example Fiber | 8.7 | 1.7 | 0.2 |
| 2026-11-12 | Metro Cable | 10.2 | 1.1 | 0 |
| 2026-11-12 | Example Fiber | 8.5 | 1.5 | 0 |
| 2026-11-11 | Metro Cable | 9.5 | 1 | 0.2 |
| 2026-11-11 | Example Fiber | 9.1 | 1.5 | 0 |
| 2026-11-10 | Metro Cable | 9.3 | 1.7 | 0.5 |
| 2026-11-10 | Example Fiber | 8.2 | 1 | 0 |
| 2026-11-09 | Metro Cable | 9.6 | 1.4 | 0 |
| 2026-11-09 | Example Fiber | 8.2 | 1.7 | 0 |
| 2026-11-08 | Metro Cable | 9.1 | 1.4 | 0 |
| 2026-11-08 | Example Fiber | 8 | 1.3 | 0 |
| 2026-11-07 | Metro Cable | 9 | 1.1 | 0 |
| 2026-11-07 | Example Fiber | 8.6 | 1.1 | 0.2 |
| 2026-11-06 | Metro Cable | 10.5 | 1.6 | 0.2 |
| 2026-11-06 | Example Fiber | 7.6 | 1.6 | 0 |
| 2026-11-05 | Metro Cable | 10.9 | 1.2 | 0.2 |
| 2026-11-05 | Example Fiber | 8.7 | 1.3 | 0 |
| 2026-11-04 | Metro Cable | 10 | 1.1 | 0 |
| 2026-11-04 | Example Fiber | 8.4 | 1.2 | 0 |
| 2026-11-03 | Metro Cable | 8.4 | 1.4 | 0 |
| 2026-11-03 | Example Fiber | 8.5 | 1.4 | 0 |
| 2026-11-02 | Metro Cable | 8.8 | 1.7 | 0.2 |
| 2026-11-02 | Example Fiber | 8.4 | 1.7 | 0 |
| 2026-11-01 | Metro Cable | 9.1 | 1 | 0 |
| 2026-11-01 | Example Fiber | 9 | 1.7 | 0 |
| 2026-10-31 | Metro Cable | 8.9 | 1.3 | 0 |
| 2026-10-31 | Example Fiber | 8.9 | 1.4 | 0 |
| 2026-10-30 | Metro Cable | 10.1 | 1.8 | 0.2 |
| 2026-10-30 | Example Fiber | 8.5 | 0.9 | 0 |
| 2026-10-29 | Metro Cable | 10.4 | 1.4 | 0 |
| 2026-10-29 | Example Fiber | 7.9 | 1.5 | 0 |
| 2026-10-28 | Metro Cable | 9.6 | 1.3 | 0 |
| 2026-10-28 | Example Fiber | 7.8 | 1.4 | 0 |
| 2026-10-27 | Metro Cable | 9.5 | 1.6 | 0.2 |
| 2026-10-27 | Example Fiber | 8.8 | 1.3 | 0 |
| 2026-10-26 | Metro Cable | 10.3 | 1.5 | 0.2 |
| 2026-10-26 | Example Fiber | 8.8 | 1.2 | 0.2 |
| 2026-10-25 | Metro Cable | 8.6 | 1.8 | 0 |
| 2026-10-25 | Example Fiber | 8.8 | 1 | 0.2 |
| 2026-10-24 | Metro Cable | 8.6 | 1.1 | 0 |
| 2026-10-24 | Example Fiber | 9.1 | 1.2 | 0 |
| 2026-10-23 | Metro Cable | 10.6 | 1.6 | 0 |
| 2026-10-23 | Example Fiber | 8.5 | 1 | 0.2 |
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 17 10:08 AM | Config | Firewall policy 60 | edited: schedule always → business-hours |
| Nov 13 4:11 PM | Config | Interface printers | description: – → Floor 2 printers |
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 17 7:28 AM | Device movedWired | Device moved 00:04:f2:0e:14:02 | 10.14.20.21 FG-MIAMI-SW1 port21 → FG-MIAMI-SW1 port17 |
| Nov 10 7:48 AM | Device movedWired | Device moved d0:43:1e:0e:0a:03 | 10.14.10.122 FG-MIAMI-SW1 port19 → FG-MIAMI-SW1 port15 |
| Oct 28 3:40 PM | Device movedWired | Device moved f8:bc:12:5e:da:ac | 10.14.30.3 FG-MIAMI-SW1 port12 → FG-MIAMI-SW1 port8 |
| Oct 27 4:07 PM | New deviceWired | New device 00:06:8e:08:dd:22 | 10.14.90.2 DOOR-FRONT on FG-MIAMI-SW1 port10 |
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
- ●circuit contract 38 days
- Circuit contract: Example Fiber ends 12/30/2026 (38 days left)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
Library circuits.csvExample Fiber: contract_end 2026-12-30How to fix
The contract for Example Fiber ends on 12/30/2026. Renewing, renegotiating or moving to another provider all take time, and many contracts need written notice well before the end.
- Check the contract for the notice period and whether it renews by itself (the site's Library has the facts on file).
- Decide with the business: renew, renegotiate or replace the circuit.
- When the new term is signed, change the dates in the tag on the FortiGate interface comment (or in the Library's circuits.csv).
- If nothing will be done, acknowledge it in the site file so it stops flagging.
# the tag sits in the comment of the circuit's WAN interface (admin account): show system interface | grep -f CT-ISP config system interface edit "<wan interface>" set description "<what is there now> CT-ISP1-<MMDDYYYY>-<MMDDYYYY>" next end
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 Miami floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment4 devices1 ending soon
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-MIAMI FortiGate · FortiGate 40F | FGDEMO00140001 tag NL-0014 | Miami Northline | 2023-11-18 3.0 years old PO PO-55515 · Example Reseller | Standard 2027-01-13 in 52 days contract NL-SUP-14 warranty 2024-11-18 passed | 2032-09-30 end of order 2027-09-30 | 2029 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-MIAMI-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF14010001 tag NL-14S01 | Miami · Closet 1 · Rack 1 Network team | 2023-02-15 3.8 years old PO PO-56140 · 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-MIAMI-AP1 FortiAP · FAP231F | FP231F14010001 tag NL-14A01 | Miami · Ceiling, zone 1 Network team | 2024-05-10 2.5 years old PO PO-57140 · 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-MIAMI-AP2 FortiAP · FAP231F | FP231F14020001 tag NL-14A02 | Miami · Ceiling, zone 2 Network team | 2022-05-10 4.5 years old PO PO-57141 · 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 circuits1 to look at soon
| Circuit | Bandwidth | Ping | From | Ends | Notice | SLA | |
|---|---|---|---|---|---|---|---|
| Example Fiber Example Fiber · wan1 · NL-141 | 500/500 | 13 ms collector ping | 2021-12-30 | 2026-12-30 in 38 days the notice date has passed (52 days ago) | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-142 | 300/30 | 10 ms collector ping | 2025-12-01 | 2028-12-01 give notice within 680 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.14.10.0/24 | 10.14.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Miami network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.14.20.0/24 | 10.14.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Miami network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.14.30.0/24 | 10.14.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Miami network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.14.40.0/24 | 10.14.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Miami network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.14.50.0/24 | 10.14.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Miami network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.14.90.0/24 | 10.14.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Miami 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.