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-LOSANGELES | FortiGate-40F | 7.4.8 | 18% | 50% | 751 | 29% · wan1 | — | Working normally |
Switches11 · 0 need a look · PoE 41 of 370 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-LOSANGELES-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 41 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-LOSANGELES-AP1 | FP231F | — | — | — | — | FG-LOSANGELES-SW1 port3 | 7.4.3 | Working normally | |
| FG-LOSANGELES-AP2 | FP231F | — | — | — | — | FG-LOSANGELES-SW1 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.13.10.0/24 | 10.13.10.1 | 255.255.255.0 /24 | 10.13.10.20 – 10.13.10.250 231 addresses · 5 in use · lease 8 hours | |
| 20 | voice | 10.13.20.0/24 | 10.13.20.1 | 255.255.255.0 /24 | 10.13.20.20 – 10.13.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.13.30.0/24 | 10.13.30.1 | 255.255.255.0 /24 | 10.13.30.20 – 10.13.30.250 231 addresses · 0 in use · lease 7 days · 3 reserved | |
| 40 | printers | 10.13.40.0/24 | 10.13.40.1 | 255.255.255.0 /24 | 10.13.40.100 – 10.13.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.13.50.0/24 | 10.13.50.1 | 255.255.255.0 /24 | 10.13.50.100 – 10.13.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.13.90.0/24 | 10.13.90.1 | 255.255.255.0 /24 | 10.13.90.100 – 10.13.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.13.0/24 | 10.255.13.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 | |
|---|---|---|---|---|---|---|
| Los Angeles | Closet 1 FG-LOSANGELES-SW1 | 14 / 28 (50%) | 10 | 10 | 41 / 370 W (11%) 329 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-LOSANGELES-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 41 / 370 W · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-LOSANGELES-AP1 FortiAP | 10 users | 10.13.10.20 · 00:11:22:0d:00:00 | 10.5 W class 4 | |
| port4 | Up | FG-LOSANGELES-AP2 FortiAP | 10 users | 10.13.10.21 · 00:11:22:0d:00:01 | 12.1 W class 4 | |
| port7 | Up | FILE01 | 30 servers | 10.13.30.2 · f8:bc:12:2f:37:13 | ||
| port8 | Up | IPERF01 | 30 servers | 10.13.30.3 · f8:bc:12:16:6d:74 | ||
| port9 | Up | UPS-MDF | 30 servers | 10.13.30.4 · 00:c0:b7:b6:5e:15 | ||
| port10 | Up | DOOR-FRONT | 90 iot | 10.13.90.2 · 00:06:8e:9c:1f:9c | 4.2 W class 2 | |
| port13 | Up | NL-LAX-PC011 | 10 users | 10.13.10.120 · d0:43:1e:0d:0a:01 | ||
| port14 | Up | NL-LAX-LT012 | 10 users | 10.13.10.121 · d0:43:1e:0d:0a:02 | ||
| port15 | Up | NL-LAX-PC013 | 10 users | 10.13.10.122 · d0:43:1e:0d:0a:03 | ||
| port16 | Up | NL-LAX-PH01 phone | 20 voice | 10.13.20.20 · 00:04:f2:0d:14:01 | 4.6 W class 2 | |
| port17 | Up | NL-LAX-PH02 phone | 20 voice | 10.13.20.21 · 00:04:f2:0d:14:02 | 4.0 W class 2 | |
| port18 | Up | PRN-LAX-01 | 40 printers | 10.13.40.20 · 3c:2a:f4:0d:28:01 | ||
| port19 | Up | CAM-LOBBY-01 | 50 cameras | 10.13.50.20 · 00:40:8c:0d:32:01 | 5.8 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00130001 |
Free ports: port1–2, port5–6, port11–12, port20–23, port25–28
S124FF13010001 · FortiSwitchOS 7.4.5
On-site contacts
- Jordan Hale · (213) 555-1013 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 5/17/2025 to 5/17/2028 · 542 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.23 /29
- Gateway
- 203.0.113.17
- Circuit ID
- NL-131
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 7/17/2023 to 7/17/2028 · 603 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.23 /29
- Gateway
- 198.51.100.17
- Circuit ID
- NL-132
- 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.10.0/24 | Connected | users local network |
| 10.13.20.0/24 | Connected | voice local network |
| 10.13.30.0/24 | Connected | servers local network |
| 10.13.40.0/24 | Connected | printers local network |
| 10.13.50.0/24 | Connected | cameras local network |
| 10.13.90.0/24 | Connected | iot local network |
| 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.13.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 | 1 | 0 |
| 2026-11-22 | Example Fiber | 8.6 | 1 | 0 |
| 2026-11-21 | Metro Cable | 9.4 | 1.4 | 0.2 |
| 2026-11-21 | Example Fiber | 8.2 | 0.6 | 0 |
| 2026-11-20 | Metro Cable | 8.8 | 1 | 0.2 |
| 2026-11-20 | Example Fiber | 8.4 | 1.4 | 0.2 |
| 2026-11-19 | Metro Cable | 9.7 | 1.6 | 0 |
| 2026-11-19 | Example Fiber | 8.4 | 1.1 | 0 |
| 2026-11-18 | Metro Cable | 10.2 | 1.2 | 0 |
| 2026-11-18 | Example Fiber | 9.1 | 1.3 | 0 |
| 2026-11-17 | Metro Cable | 9.5 | 1.5 | 0 |
| 2026-11-17 | Example Fiber | 8.7 | 1.5 | 0 |
| 2026-11-16 | Metro Cable | 9.4 | 1.7 | 0 |
| 2026-11-16 | Example Fiber | 8.7 | 1.3 | 0.2 |
| 2026-11-15 | Metro Cable | 10.2 | 1.2 | 0 |
| 2026-11-15 | Example Fiber | 7.5 | 1.8 | 0.2 |
| 2026-11-14 | Metro Cable | 9.5 | 1.1 | 0 |
| 2026-11-14 | Example Fiber | 8.2 | 1.5 | 0.2 |
| 2026-11-13 | Metro Cable | 10 | 1.3 | 0 |
| 2026-11-13 | Example Fiber | 9.3 | 1.3 | 0 |
| 2026-11-12 | Metro Cable | 9.2 | 1.3 | 0 |
| 2026-11-12 | Example Fiber | 8.2 | 1.6 | 0 |
| 2026-11-11 | Metro Cable | 9.6 | 1.1 | 0 |
| 2026-11-11 | Example Fiber | 8 | 1.9 | 0 |
| 2026-11-10 | Metro Cable | 10 | 1.7 | 0 |
| 2026-11-10 | Example Fiber | 8.7 | 1.5 | 0 |
| 2026-11-09 | Metro Cable | 10.2 | 1.4 | 0 |
| 2026-11-09 | Example Fiber | 7.4 | 1.3 | 0 |
| 2026-11-08 | Metro Cable | 9.5 | 1.7 | 0.5 |
| 2026-11-08 | Example Fiber | 7.5 | 1.3 | 0 |
| 2026-11-07 | Metro Cable | 8.2 | 0.9 | 0.2 |
| 2026-11-07 | Example Fiber | 9.3 | 1.6 | 0 |
| 2026-11-06 | Metro Cable | 9.4 | 0.9 | 0.2 |
| 2026-11-06 | Example Fiber | 8.7 | 1.2 | 0.2 |
| 2026-11-05 | Metro Cable | 10 | 1.1 | 0 |
| 2026-11-05 | Example Fiber | 8.5 | 1.7 | 0.2 |
| 2026-11-04 | Metro Cable | 9.2 | 1.9 | 0.5 |
| 2026-11-04 | Example Fiber | 8 | 1.3 | 0 |
| 2026-11-03 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-03 | Example Fiber | 9.4 | 1.3 | 0 |
| 2026-11-02 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-02 | Example Fiber | 9.7 | 1.3 | 0 |
| 2026-11-01 | Metro Cable | 8.4 | 1.5 | 0.5 |
| 2026-11-01 | Example Fiber | 8.6 | 1.7 | 0 |
| 2026-10-31 | Metro Cable | 9.5 | 1.2 | 0 |
| 2026-10-31 | Example Fiber | 8.2 | 1.6 | 0.2 |
| 2026-10-30 | Metro Cable | 9.1 | 1.4 | 0.2 |
| 2026-10-30 | Example Fiber | 7.7 | 1.8 | 0 |
| 2026-10-29 | Metro Cable | 9.5 | 1.3 | 0.2 |
| 2026-10-29 | Example Fiber | 8.5 | 0.9 | 0.2 |
| 2026-10-28 | Metro Cable | 9.7 | 1 | 0 |
| 2026-10-28 | Example Fiber | 8.6 | 1.2 | 0.2 |
| 2026-10-27 | Metro Cable | 9.5 | 1.2 | 0.2 |
| 2026-10-27 | Example Fiber | 9.1 | 1.7 | 0 |
| 2026-10-26 | Metro Cable | 10.7 | 1.6 | 0 |
| 2026-10-26 | Example Fiber | 9 | 1.9 | 0 |
| 2026-10-25 | Metro Cable | 9.8 | 1.7 | 0.2 |
| 2026-10-25 | Example Fiber | 7.9 | 1.4 | 0 |
| 2026-10-24 | Metro Cable | 10.3 | 1.4 | 0 |
| 2026-10-24 | Example Fiber | 8.9 | 1.5 | 0 |
| 2026-10-23 | Metro Cable | 10.2 | 0.8 | 0 |
| 2026-10-23 | Example Fiber | 8.8 | 1.8 | 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 13 1:29 PM | Config | Static route 10 | added: dst 10.200.0.0 255.255.0.0, device to-chicago |
| Nov 11 3:56 PM | Config | Interface printers | description: – → Floor 2 printers |
| Nov 2 7:05 AM | Config | Address srv-backup-39 | added: subnet 10.16.30.39 255.255.255.255 |
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 19 10:42 AM | New deviceWired | New device d0:43:1e:0d:0a:03 | 10.13.10.122 NL-LAX-PC013 on FG-LOSANGELES-SW1 port15 |
| Nov 5 1:27 PM | New deviceWired | New device 00:04:f2:0d:14:02 | 10.13.20.21 NL-LAX-PH02 on FG-LOSANGELES-SW1 port17 |
| Nov 3 9:02 AM | New deviceWired | New device 00:40:8c:0d:32:01 | 10.13.50.20 CAM-LOBBY-01 on FG-LOSANGELES-SW1 port19 |
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
- Configuration2
- ●weak IPsec settings
- 1 tunnel(s) with legacy crypto: to-chicago (IKEv1, SHA1/MD5/3DES offered, DH 5)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show vpn ipsec phase1-interface (no 'set ike-version 2' line = IKEv1)config vpn ipsec phase1-interface edit "to-chicago" set remote-gw 203.0.113.11 set proposal aes128-sha1 set dhgrp 5 next endHow to fix
These tunnels use legacy crypto: IKEv1, SHA1/MD5/3DES proposals, or Diffie-Hellman groups below 14. They work, but they're weaker and IKEv1 is being phased out. Change both ends together in a maintenance window – a mismatch takes the tunnel down.
- Pick one tunnel pair and change both ends at the same time.
- Use IKEv2, aes256-sha256 / aes256gcm, DH 19/20/21 (keep 14 only if a peer needs it).
- Check it re-establishes, then move on to the next pair.
to-chicago: IKEv1, SHA1/MD5/3DES offered, DH 5
config vpn ipsec phase1-interface edit "<tunnel>" set ike-version 2 set proposal aes256-sha256 aes256gcm-prfsha384 set dhgrp 21 20 19 next end - ●IPsec settings differ at the two ends
- Chicago's to-losangeles ↔ Los Angeles's to-chicago: phase 1 ike-version: 2 vs (default); phase 1 proposal: aes256-sha256 vs aes128-sha1; phase 1 dhgrp: 14 vs 5
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show vpn ipsec phase1-interfaceconfig vpn ipsec phase1-interface edit "to-losangeles" set remote-gw 203.0.113.23 set ike-version 2 set proposal aes256-sha256 set dhgrp 14 next end config vpn ipsec phase1-interface edit "to-chicago" set remote-gw 203.0.113.11 set proposal aes128-sha1 set dhgrp 5 next endHow to fix
The two ends of this path disagree on phase 1 or phase 2 (IKE version, proposal, DH group, dead-peer detection, key life, auto-negotiate, or the phase-2 selectors). `show` omits a setting left at the FortiOS default; a named selector cannot be expanded to its subnets here. A value written on one end and absent on the other is still a mismatch. When the tunnel is one-way and the aggregates already agree, this is the next place to look.
- Compare the settings below at both ends.
- Change both ends together in a maintenance window – a mismatch takes the tunnel down.
- Named address objects are not collected; check those by hand if a selector is a name on one end.
# this end: show vpn ipsec phase1-interface | grep -f to-chicago show vpn ipsec phase2-interface | grep -f to-chicago # on Chicago: show vpn ipsec phase1-interface | grep -f to-losangeles show vpn ipsec phase2-interface | grep -f to-losangeles
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 Los Angeles floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment4 devices
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-LOSANGELES FortiGate · FortiGate 40F | FGDEMO00130001 tag NL-0013 | Los Angeles Northline | 2022-06-11 4.4 years old PO PO-55514 · Example Reseller | Standard 2028-06-05 contract NL-SUP-13 warranty 2023-06-11 passed | 2032-09-30 end of order 2027-09-30 | 2028 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-LOSANGELES-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF13010001 tag NL-13S01 | Los Angeles · Closet 1 · Rack 1 Network team | 2022-02-15 4.8 years old PO PO-56130 · 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-LOSANGELES-AP1 FortiAP · FAP231F | FP231F13010001 tag NL-13A01 | Los Angeles · Ceiling, zone 1 Network team | 2023-05-10 3.5 years old PO PO-57130 · 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-LOSANGELES-AP2 FortiAP · FAP231F | FP231F13020001 tag NL-13A02 | Los Angeles · Ceiling, zone 2 Network team | 2024-05-10 2.5 years old PO PO-57131 · 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-131 | 500/500 | 7 ms collector ping | 2025-05-17 | 2028-05-17 give notice within 452 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-132 | 300/30 | 9 ms collector ping | 2023-07-17 | 2028-07-17 give notice within 543 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.13.10.0/24 | 10.13.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Los Angeles network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.13.20.0/24 | 10.13.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Los Angeles network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.13.30.0/24 | 10.13.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Los Angeles network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.13.40.0/24 | 10.13.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Los Angeles network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.13.50.0/24 | 10.13.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Los Angeles network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.13.90.0/24 | 10.13.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Los Angeles 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.