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-HOUSTON | FortiGate-120G | 7.4.8 | 16% | 50% | 4,071 | 31% · wan1 | — | Working normally |
Switches22 · 0 need a look · PoE 69 of 740 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-HOUB-SW1 | FortiSwitch 124F-FPOE | 11 / 28 | 38 of 370 W | — | FG-HOUB-SW2 port28 (port25) | 7.4.5 | Working normally | |
| FG-HOUB-SW2 | FortiSwitch 124F-FPOE | 12 / 28 | 31 of 370 W | — | FG-HOUB-SW1 port25 (port28) | 7.4.5 | Working normally |
Access points44 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-HOUB-AP1 | FP231F | — | — | — | — | FG-HOUB-SW1 port3 | 7.4.3 | Working normally | |
| FG-HOUB-AP2 | FP231F | — | — | — | — | FG-HOUB-SW2 port3 | 7.4.3 | Working normally | |
| FG-HOUB-AP3 | FP231F | — | — | — | — | FG-HOUB-SW1 port4 | 7.4.3 | Working normally | |
| FG-HOUB-AP4 | FP231F | — | — | — | — | FG-HOUB-SW2 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.2.10.0/24 | 10.2.10.1 | 255.255.255.0 /24 | 10.2.10.20 – 10.2.10.250 231 addresses · 7 in use · lease 8 hours | |
| 20 | voice | 10.2.20.0/24 | 10.2.20.1 | 255.255.255.0 /24 | 10.2.20.20 – 10.2.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.2.30.0/24 | 10.2.30.1 | 255.255.255.0 /24 | 10.2.30.20 – 10.2.30.250 231 addresses · 0 in use · lease 7 days · 6 reserved | |
| 40 | printers | 10.2.40.0/24 | 10.2.40.1 | 255.255.255.0 /24 | 10.2.40.100 – 10.2.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.2.50.0/24 | 10.2.50.1 | 255.255.255.0 /24 | 10.2.50.100 – 10.2.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.2.90.0/24 | 10.2.90.1 | 255.255.255.0 /24 | 10.2.90.100 – 10.2.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.2.0/24 | 10.255.2.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 4 | 3 Computer · 1 Network gear |
| 20 | voice | 2 | 2 Phone (VoIP) |
| 30 | servers | 6 | 5 Storage / server · 1 UPS / power |
| 40 | printers | 1 | 1 Printer |
| 50 | cameras | 1 | 1 Camera |
| 90 | iot | 3 | 2 IoT / industrial (by network) · 1 IoT / industrial |
| FortiLink | FortiLink | 2 | 2 Network gear |
| 10 | users | 4 | 4 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.
2 switches · 24 ports in use · 32 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 closet2 closets24 of 56 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Houston | Closet 1 FG-HOUB-SW1 | 12 / 28 (43%) | 15 | 15 | 38 / 370 W (10%) 332 W headroom | |
| Houston | Closet 2 FG-HOUB-SW2 | 12 / 28 (43%) | 13 | 13 | 31 / 370 W (8%) 339 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-HOUB-SW1 FortiSwitch 124F-FPOE · Closet 112 in use · 16 free · PoE 38 / 370 W · 3 fiber ports · 38 °C
Uplink trunk member(s) not active: port28 (FGDEMO00020001)
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-HOUB-AP1 FortiAP | 10 users | 10.2.10.20 · 00:11:22:02:00:00 | 9.9 W class 4 | |
| port4 | Up | FG-HOUB-AP3 FortiAP | 10 users | 10.2.10.22 · 00:11:22:02:00:02 | 11.4 W class 4 | |
| port13 | Up | NL-HOU-PC011 | 10 users | 10.2.10.120 · d0:43:1e:02:0a:01 | ||
| port14 | Up | NL-HOU-LT012 | 10 users | 10.2.10.121 · d0:43:1e:02:0a:02 | ||
| port15 | Up | NL-HOU-PC013 | 10 users | 10.2.10.122 · d0:43:1e:02:0a:03 | ||
| port16 | Up | NL-HOU-PH01 phone | 20 voice | 10.2.20.20 · 00:04:f2:02:14:01 | 4.7 W class 2 | |
| port17 | Up | NL-HOU-PH02 phone | 20 voice | 10.2.20.21 · 00:04:f2:02:14:02 | 4.5 W class 2 | |
| port18 | Up | PRN-HOU-01 | 40 printers | 10.2.40.20 · 3c:2a:f4:02:28:01 | ||
| port19 | Up | CAM-DOCK-01 | 50 cameras | 10.2.50.20 · 00:40:8c:02:32:01 | 7.7 W class 3 | |
| port25 | Up | ↔ FG-HOUB-SW2 port28 trunk S124FF02020001-0 | Fiber 10G-SR | |||
| port27 | Up | FortiGate · FortiLink trunk FGDEMO00020001 · port28 not active | Fiber 10G-SR | |||
| port28 | Down | FortiGate · FortiLink trunk FGDEMO00020001 · port28 not active | Fiber 10G-SR no light (LOS) |
Free ports: port1–2, port5–12, port20–24, port26
S124FF02010001 · FortiSwitchOS 7.4.5
FG-HOUB-SW2 FortiSwitch 124F-FPOE · Closet 212 in use · 16 free · PoE 31 / 370 W · 1 fiber port · 44 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-HOUB-AP2 FortiAP | 10 users | 10.2.10.21 · 00:11:22:02:00:01 | 10.3 W class 4 | |
| port4 | Up | FG-HOUB-AP4 FortiAP | 10 users | 10.2.10.23 · 00:11:22:02:00:03 | 10.4 W class 4 | |
| port7 | Up | DC01 | 30 servers | 10.2.30.2 · f8:bc:12:6b:0d:a9 | ||
| port8 | Up | FILE01 | 30 servers | 10.2.30.3 · f8:bc:12:5c:a1:e8 | ||
| port9 | Up | MES01 | 30 servers | 10.2.30.4 · f8:bc:12:e0:2b:8f | ||
| port10 | Up | IPERF01 | 30 servers | 10.2.30.5 · f8:bc:12:31:e3:18 | ||
| port11 | Up | NAS01 | 30 servers | 10.2.30.6 · 00:11:32:3c:9c:ab | ||
| port12 | Up | UPS-MDF | 30 servers | 10.2.30.7 · 00:c0:b7:67:b0:6f | ||
| port13 | Up | DOOR-DOCK | 90 iot | 10.2.90.2 · 00:06:8e:2c:53:48 | 4.2 W class 2 | |
| port14 | Up | DOOR-MDF | 90 iot | 10.2.90.3 · 00:06:8e:ef:5f:c2 | 4.2 W class 2 | |
| port15 | Up | ENV-MDF | 90 iot | 10.2.90.4 · b8:27:eb:b3:34:52 | 1.9 W class 1 | |
| port28 | Up | ↔ FG-HOUB-SW1 port25 trunk S124FF02010001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–6, port16–27
S124FF02020001 · FortiSwitchOS 7.4.5
On-site contacts
- Riley Okonkwo · (202) 555-1002 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 5/30/2023 to 5/30/2028 · 555 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.12 /29
- Gateway
- 203.0.113.9
- Circuit ID
- NL-021
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 7/30/2025 to 7/30/2028 · 616 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.12 /29
- Gateway
- 198.51.100.9
- Circuit ID
- NL-022
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary4 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.10.0/24 | Connected | users local network |
| 10.2.20.0/24 | Connected | voice local network |
| 10.2.30.0/24 | Connected | servers local network |
| 10.2.40.0/24 | Connected | printers local network |
| 10.2.50.0/24 | Connected | cameras local network |
| 10.2.90.0/24 | Connected | iot local network |
| 10.3.0.0/16 | Static | to-houston-ot → Houston OT |
| 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.255.2.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.8/29 | Connected | wan2 local network |
| 203.0.113.8/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.5 | 0 |
| 2026-11-22 | Example Fiber | 8.4 | 1.4 | 0 |
| 2026-11-21 | Metro Cable | 9.4 | 1.5 | 0 |
| 2026-11-21 | Example Fiber | 8.3 | 1.4 | 0 |
| 2026-11-20 | Metro Cable | 9.2 | 1.7 | 0 |
| 2026-11-20 | Example Fiber | 8.1 | 1.8 | 0 |
| 2026-11-19 | Metro Cable | 9.5 | 1.5 | 0 |
| 2026-11-19 | Example Fiber | 8.9 | 1.3 | 0 |
| 2026-11-18 | Metro Cable | 9.5 | 1.7 | 0 |
| 2026-11-18 | Example Fiber | 9.1 | 1.7 | 0.5 |
| 2026-11-17 | Metro Cable | 9.8 | 0.9 | 0.2 |
| 2026-11-17 | Example Fiber | 8.8 | 1.4 | 0 |
| 2026-11-16 | Metro Cable | 10.1 | 1.6 | 0 |
| 2026-11-16 | Example Fiber | 8.3 | 1.3 | 0 |
| 2026-11-15 | Metro Cable | 9.9 | 1 | 0 |
| 2026-11-15 | Example Fiber | 8.6 | 1.9 | 0.2 |
| 2026-11-14 | Metro Cable | 8.9 | 1.6 | 0.5 |
| 2026-11-14 | Example Fiber | 9.4 | 1.1 | 0.2 |
| 2026-11-13 | Metro Cable | 9.8 | 1.4 | 0 |
| 2026-11-13 | Example Fiber | 9 | 1.6 | 0.5 |
| 2026-11-12 | Metro Cable | 9.4 | 1.5 | 0 |
| 2026-11-12 | Example Fiber | 8.7 | 1.1 | 0 |
| 2026-11-11 | Metro Cable | 10.2 | 1.1 | 0 |
| 2026-11-11 | Example Fiber | 7.8 | 1.3 | 0.2 |
| 2026-11-10 | Metro Cable | 10.3 | 1.6 | 0.2 |
| 2026-11-10 | Example Fiber | 8.6 | 1.4 | 0.2 |
| 2026-11-09 | Metro Cable | 10.1 | 1.3 | 0 |
| 2026-11-09 | Example Fiber | 7.5 | 1.4 | 0 |
| 2026-11-08 | Metro Cable | 9 | 0.6 | 0.2 |
| 2026-11-08 | Example Fiber | 9.9 | 1.2 | 0 |
| 2026-11-07 | Metro Cable | 9.7 | 0.9 | 0 |
| 2026-11-07 | Example Fiber | 8.5 | 1.4 | 0 |
| 2026-11-06 | Metro Cable | 10.1 | 1.8 | 0 |
| 2026-11-06 | Example Fiber | 8.4 | 1.4 | 0 |
| 2026-11-05 | Metro Cable | 10.8 | 0.8 | 0 |
| 2026-11-05 | Example Fiber | 7.7 | 0.9 | 0 |
| 2026-11-04 | Metro Cable | 9.3 | 1.9 | 0.2 |
| 2026-11-04 | Example Fiber | 8 | 1.3 | 0 |
| 2026-11-03 | Metro Cable | 9.8 | 1.7 | 0 |
| 2026-11-03 | Example Fiber | 8.6 | 1.1 | 0 |
| 2026-11-02 | Metro Cable | 10.2 | 1.5 | 0.2 |
| 2026-11-02 | Example Fiber | 9 | 1.3 | 0.2 |
| 2026-11-01 | Metro Cable | 9.5 | 1 | 0 |
| 2026-11-01 | Example Fiber | 7.7 | 1.2 | 0 |
| 2026-10-31 | Metro Cable | 10.1 | 1.5 | 0 |
| 2026-10-31 | Example Fiber | 8.3 | 1.7 | 0.2 |
| 2026-10-30 | Metro Cable | 9.5 | 1.3 | 0 |
| 2026-10-30 | Example Fiber | 8.8 | 1.3 | 0 |
| 2026-10-29 | Metro Cable | 9.4 | 2.1 | 0.5 |
| 2026-10-29 | Example Fiber | 8.8 | 1.2 | 0 |
| 2026-10-28 | Metro Cable | 9.3 | 1.2 | 0 |
| 2026-10-28 | Example Fiber | 8.1 | 1.5 | 0 |
| 2026-10-27 | Metro Cable | 9.5 | 1 | 0 |
| 2026-10-27 | Example Fiber | 9.1 | 1.1 | 0 |
| 2026-10-26 | Metro Cable | 9.6 | 1.3 | 0.2 |
| 2026-10-26 | Example Fiber | 9 | 1.1 | 0.2 |
| 2026-10-25 | Metro Cable | 9.9 | 1 | 0 |
| 2026-10-25 | Example Fiber | 7.8 | 1.7 | 0 |
| 2026-10-24 | Metro Cable | 8.7 | 1.7 | 0 |
| 2026-10-24 | Example Fiber | 8.4 | 1.7 | 0 |
| 2026-10-23 | Metro Cable | 9.6 | 1.9 | 0 |
| 2026-10-23 | Example Fiber | 7.3 | 1.5 | 0 |
Tunnel stability – last 7 days
3 tunnels · 3 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 5
| When | Type | What | Detail |
|---|---|---|---|
| Nov 20 9:37 PM | Config | Admin netops-58 | trusthost1: 0.0.0.0 0.0.0.0 → 10.1.30.0 255.255.255.0 |
| Nov 13 10:35 AM | Config | Firewall policy 45 | edited: schedule always → business-hours |
| Nov 9 7:33 AM | Config | Interface printers | description: – → Floor 2 printers |
| Nov 6 7:46 AM | Config | Service NL-ERP | added: TCP 8443-8445 |
| Oct 28 3:25 PM | Config | Address srv-backup-43 | added: subnet 10.7.30.43 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 9 7:06 AM | New deviceWired | New device 00:11:32:3c:9c:ab | 10.2.30.6 NAS01 on FG-HOUB-SW2 port11 |
| Nov 5 8:00 AM | New deviceWired | New device d0:43:1e:02:0a:01 | 10.2.10.120 NL-HOU-PC011 on FG-HOUB-SW1 port13 |
| Oct 26 5:24 PM | Device movedWired | Device moved 00:04:f2:02:14:01 | 10.2.20.20 FG-HOUB-SW1 port20 → FG-HOUB-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 reduced4
- ●HA out of sync
Mismatched checksum parts (all, root):
- all
- FGDEMO00020001=76 09 b4 06 79 89 51 ac ba b2 04 3f 3f 63 47 e5
- FGDEMO00020002=20 bd d4 fc 9f e4 08 40 a0 a2 1e 64 d5 73 5b d1
- root
- FGDEMO00020001=9a 7d 73 f9 8c df 1c 77 da 5e af 60 27 f6 ad 9e
- FGDEMO00020002=00 2b 13 8f 98 3b 24 7a 6b 91 35 05 a6 ff e2 2c
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get system ha statusConfiguration Status: FGDEMO00020001(updated 2 seconds ago): in-sync FGDEMO00020002(updated 3 seconds ago): out-of-syncdiagnose sys ha checksum clusterpart FGDEMO00020001 FGDEMO00020002 ------------------------------------------------ all 76 09 b4 06 79 8 20 bd d4 fc 9f e root 9a 7d 73 f9 8c d 00 2b 13 8f 98 3How to fix
The two FortiGates in the HA cluster have different configurations. If the primary fails, the secondary takes over with the wrong settings. A firmware mismatch between the units also causes this.
- Compare the checksums – the module that differs shows where.
- Make sure both units run the same firmware.
- Force a sync from the primary, wait a minute, and check again.
Differs in: all, root – all = the overall checksum (follows the others); root = the root VDOM (firewall policies, addresses, routes, VPNs, SD-WAN). 'diagnose sys ha checksum show <part>' on both units lists a checksum per table – the table whose checksum differs is the object to compare.
Mismatched parts only (matching parts omitted): part FGDEMO00020001 FGDEMO00020002 ------------------------------------------------all 76 09 b4 06 79 8 20 bd d4 fc 9f e root 9a 7d 73 f9 8c d 00 2b 13 8f 98 3diagnose sys ha checksum cluster diagnose sys ha checksum show root diagnose sys ha checksum recalculate get system ha status # still out of sync – force it from the secondary: execute ha manage <index> <admin> execute ha synchronize start # firmware on the secondary: get system status - all
- ●FortiLink link down
- FortiLink fortilink: 1 of 2 links down (port x2) – the switches are running on port x1 only
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system interfaceconfig system interface edit "fortilink" set fortilink enable set type aggregate set member "x1" "x2" next endget system interface physical==[x1] status: up speed: 10000Mbps (Duplex: full) ==[x2] status: down speed: n/aHow to fix
The FortiGate reaches its switches over the fortilink aggregate. One member is down, so every switch, AP and wired device at the site now depends on a single cable/SFP – lose it and the whole LAN is cut off.
- x2 is disabled in the config – enable it (below) if it should be in use.
- Check the cable/fiber and the SFP on both ends (FortiGate port and the core switch's FortiLink port).
- Look at the transceiver readings – a dead or wrong-type SFP shows here.
- If the second link was never cabled, either cable it or remove it from the aggregate so it stops showing.
get system interface physical x2 get system interface transceiver diagnose netlink aggregate name fortilink # re-enable: config system interface edit "x2" set status up next end - ●HA single heartbeat
- HA has 1 heartbeat device(s) (ha1) – a second hbdev keeps the cluster from splitting when one HA cable fails.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system haconfig system ha set mode a-p set hbdev "ha1" 50 set monitor "wan1" "wan2" "x1" "x2" endHow to fix
HA needs two heartbeat links so a single cable or port failure does not split the cluster (both units thinking they are primary).
- Add a second dedicated HA port (or a monitored VLAN) as hbdev.
- Use separate physical paths where you can.
- After the change, confirm both units list the same hbdev ports.
show system ha config system ha set hbdev ha1 50 end - ●trunk member not active
Switch trunk member(s) not active – LACP redundancy is reduced.
- FG-HOUB-SW1 trunk FGDEMO00020001: port28 not active (still up: port27)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
diagnose switch-controller switch-info trunk statusFG-HOUB-SW1 trunk FGDEMO00020001: port28 not active (still up: port27)How to fix
A FortiSwitch trunk (LACP) with a member not active has lost a redundant path. Spanning or failover still works on the remaining members, but one more failure cuts the link.
- Check the cable/SFP and the far-end port for each inactive member.
- Confirm LACP mode matches at both ends (active/passive).
- If the port was retired, remove it from the trunk so it stops showing.
FG-HOUB-SW1 FGDEMO00020001: down port28
diagnose switch-controller switch-info trunk status <switch> - Performance1
- ●2 optics to check
- FortiGate x2: Rx power ALARM (-40.0), Tx power ALARM (-40.0), temperature ALARM (73.5), Tx bias ALARM (0.0); FG-HOUB-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 summaryInterface x1 - SFP/SFP+, 10GBASE-SR Vendor Name : FORTINET Part No. : FN-TRAN-SFP+SR Serial No. : NLFG97537 Interface x2 - SFP/SFP+, 10GBASE-SR Vendor Name : FORTINET Part No. : FN-TRAN-SFP+SR Serial No. : NLFG33433 Optical Temperature Voltage Tx Bias Tx Power Rx Power Interface (Celsius) (Volts) (mA) (dBm) (dBm) ------------ --------------- ------------- ------------- ------------- ------------- x1 41.3 3.31 6.10 -2.62 -3.48 x2 73.5 ++ 3.27 0.00 -- -40.00 -- -40.00 -- ++ : high alarm, + : high warning, - : low warning, -- : low alarm, ? : suspect. FG-HOUB-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.
FortiGate x2
FG-HOUB-SW1 port28get system interface transceiver diagnose switch-controller switch-info modules summary <switch> diagnose switch-controller switch-info modules detail <switch> <port> - Monitoring & housekeeping2
- ●collected from the secondary
- The collector is logged in to the secondary HA unit (FG-HOUB). Tunnel, routing and aggregate state on this page is that unit's – not what carries the traffic. Primary: FG-HOUSTON
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get system statusHostname: FG-HOUB Current HA mode: a-p, backupHow to fix
In a FortiGate HA pair one unit forwards the traffic (the primary). Tunnels, routes and aggregates are live there; the secondary's copies can look different, and troubleshooting from it gives wrong answers.
- Point the collector at the address that follows the primary, not at this unit's own management address (config.json → sites → host).
- When you work on the cluster by hand, check which unit you are on first (below).
get system status | grep -i 'HA mode' get system ha status - ●Certificate 57 days
- Certificate: Houston-MES expires in 57 days (Jan 18 2027)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get vpn certificate local detailsHouston-MES: 2027-01-18How to fix
The certificate 'Houston-MES' on this FortiGate expires 2027-01-18. Anything using it – SSL VPN, the admin GUI, an IPsec tunnel with certificate authentication – fails after that date.
- Find what uses it (below).
- Issue a new certificate from your CA, import it on the FortiGate.
- Point the services at the new certificate, then delete the old one.
get vpn certificate local details Houston-MES show vpn ssl settings show system global | grep -f cert show vpn ipsec phase1-interface | grep -f certificate
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 Houston floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment7 devices
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-HOUB FortiGate · FortiGate 120G | FGDEMO00020001 tag NL-0002 | Houston Northline | 2023-11-15 3.0 years old PO PO-55503 · Example Reseller | Premium 2027-12-21 contract NL-SUP-02 warranty 2024-11-15 passed | 2035-09-30 end of order 2030-09-30 | 2029 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-HOUB-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF02010001 tag NL-02S01 | Houston · Closet 1 · Rack 1 Network team | 2023-02-15 3.8 years old PO PO-56020 · 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-HOUB-SW2 FortiSwitch · FortiSwitch 124F-FPOE | S124FF02020001 tag NL-02S02 | Houston · Closet 2 · Rack 2 Network team | 2024-02-15 2.8 years old PO PO-56021 · 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-HOUB-AP1 FortiAP · FAP231F | FP231F02010001 tag NL-02A01 | Houston · Ceiling, zone 1 Network team | 2024-05-10 2.5 years old PO PO-57020 · 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-HOUB-AP2 FortiAP · FAP231F | FP231F02020001 tag NL-02A02 | Houston · Ceiling, zone 2 Network team | 2022-05-10 4.5 years old PO PO-57021 · 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-HOUB-AP3 FortiAP · FAP231F | FP231F02030001 tag NL-02A03 | Houston · Ceiling, zone 3 Network team | 2023-05-10 3.5 years old PO PO-57022 · 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-HOUB-AP4 FortiAP · FAP231F | FP231F02040001 tag NL-02A04 | Houston · Ceiling, zone 4 Network team | 2024-05-10 2.5 years old PO PO-57023 · 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-021 | 500/500 | 12 ms collector ping | 2023-05-30 | 2028-05-30 give notice within 465 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-022 | 300/30 | 13 ms collector ping | 2025-07-30 | 2028-07-30 give notice within 556 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.2.10.0/24 | 10.2.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Houston network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.2.20.0/24 | 10.2.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Houston network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.2.30.0/24 | 10.2.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Houston network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.2.40.0/24 | 10.2.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Houston network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.2.50.0/24 | 10.2.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Houston network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.2.90.0/24 | 10.2.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Houston 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.