Needs attention 13
- Redundancy reduced1
- ▲most tunnels down
- 2 of 3 IPsec tunnels are down: to-chicago, to-chicago-b
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/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-chicago-b' 198.51.100.11:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0How to fix
Some IPsec tunnels to other sites are down. If the aggregate's other member is up, traffic still flows – this is lost redundancy, not an outage. Backup tunnels whose phase 2 isn't set to auto-negotiate stay down until traffic needs them, so they look down here.
- Check the tunnel from this end (and the other site's end) – the WAN page's Tunnel paths tab shows both.
- For backup tunnels, enable auto-negotiate on their phase 2 (below) so they stay up.
- Tunnels that point at the wrong IP or a site that no longer exists: fix the remote gateway, or delete them.
to-chicago → 203.0.113.11
to-chicago-b → 198.51.100.11get vpn ipsec tunnel summary diagnose vpn tunnel list name to-chicago diagnose vpn tunnel list name to-chicago-b - Performance12
- ▲FG-BOSTON-SW1 slow ping
- Collector ping to FG-BOSTON-SW1 (10.255.15.10): 263 ms, 33% loss
How to fix
The collector can ping FG-BOSTON-SW1, 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.
- ▲Boston FortiGate slow ping
- Collector ping to Boston FortiGate (10.250.0.15): 239 ms, 33% loss
How to fix
The collector can ping Boston FortiGate, 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.
- ▲boston FortiGate (users) slow ping
- Collector ping to boston FortiGate (users) (10.15.10.1): 292 ms, 33% loss
How to fix
The collector can ping boston FortiGate (users), 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.
- ▲boston servers gateway slow ping
- Collector ping to boston servers gateway (10.15.30.1): 211 ms, 33% loss
How to fix
The collector can ping boston servers 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.
- ▲boston printers gateway slow ping
- Collector ping to boston printers gateway (10.15.40.1): 260 ms, 0% loss
How to fix
The collector can ping boston printers 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.
- ▲boston cameras gateway slow ping
- Collector ping to boston cameras gateway (10.15.50.1): 270 ms, 33% loss
How to fix
The collector can ping boston cameras 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.
- ▲boston iot gateway slow ping
- Collector ping to boston iot gateway (10.15.90.1): 263 ms, 33% loss
How to fix
The collector can ping boston iot 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.
- ▲boston FortiLink slow ping
- Collector ping to boston FortiLink (10.255.15.1): 284 ms, 33% loss
How to fix
The collector can ping boston FortiLink, 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.
- ▲FG-BOSTON-AP1 slow ping
- Collector ping to FG-BOSTON-AP1 (10.15.10.20): 229 ms, 33% loss
How to fix
The collector can ping FG-BOSTON-AP1, 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.
- ▲FG-BOSTON-AP2 slow ping
- Collector ping to FG-BOSTON-AP2 (10.15.10.21): 275 ms, 33% loss
How to fix
The collector can ping FG-BOSTON-AP2, 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.
- ▲boston DNS 10.1.30.2 slow ping
- Collector ping to boston DNS 10.1.30.2 (10.1.30.2): 272 ms, 0% loss
How to fix
The collector can ping boston DNS 10.1.30.2, 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.
- ▲boston DNS 10.1.30.3 slow ping
- Collector ping to boston DNS 10.1.30.3 (10.1.30.3): 263 ms, 33% loss
How to fix
The collector can ping boston DNS 10.1.30.3, 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-BOSTON | FortiGate-40F | 7.4.8 | 18% | 48% | 802 | 46% · wan1 | — | Working, needs a look |
Switches11 · 0 need a look · PoE 44 of 370 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-BOSTON-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 44 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-BOSTON-AP1 | FP231F | — | — | — | — | FG-BOSTON-SW1 port3 | 7.4.3 | Working normally | |
| FG-BOSTON-AP2 | FP231F | — | — | — | — | FG-BOSTON-SW1 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.15.10.0/24 | 10.15.10.1 | 255.255.255.0 /24 | 10.15.10.20 – 10.15.10.250 231 addresses · 5 in use · lease 8 hours | |
| 20 | voice | 10.15.20.0/24 | 10.15.20.1 | 255.255.255.0 /24 | 10.15.20.20 – 10.15.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.15.30.0/24 | 10.15.30.1 | 255.255.255.0 /24 | 10.15.30.20 – 10.15.30.250 231 addresses · 0 in use · lease 7 days · 3 reserved | |
| 40 | printers | 10.15.40.0/24 | 10.15.40.1 | 255.255.255.0 /24 | 10.15.40.100 – 10.15.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.15.50.0/24 | 10.15.50.1 | 255.255.255.0 /24 | 10.15.50.100 – 10.15.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.15.90.0/24 | 10.15.90.1 | 255.255.255.0 /24 | 10.15.90.100 – 10.15.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.15.0/24 | 10.255.15.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 | |
|---|---|---|---|---|---|---|
| Boston | Closet 1 FG-BOSTON-SW1 | 14 / 28 (50%) | 10 | 10 | 44 / 370 W (12%) 326 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-BOSTON-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 44 / 370 W · 38 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-BOSTON-AP1 FortiAP | 10 users | 10.15.10.20 · 00:11:22:0f:00:00 | 12.6 W class 4 | |
| port4 | Up | FG-BOSTON-AP2 FortiAP | 10 users | 10.15.10.21 · 00:11:22:0f:00:01 | 12.8 W class 4 | |
| port7 | Up | FILE01 | 30 servers | 10.15.30.2 · f8:bc:12:2b:44:c8 | ||
| port8 | Up | IPERF01 | 30 servers | 10.15.30.3 · f8:bc:12:e9:d4:f5 | ||
| port9 | Up | UPS-MDF | 30 servers | 10.15.30.4 · 00:c0:b7:29:ed:15 | ||
| port10 | Up | DOOR-FRONT | 90 iot | 10.15.90.2 · 00:06:8e:1f:2d:83 | 4.2 W class 2 | |
| port13 | Up | NL-BOS-PC011 | 10 users | 10.15.10.120 · d0:43:1e:0f:0a:01 | ||
| port14 | Up | NL-BOS-LT012 | 10 users | 10.15.10.121 · d0:43:1e:0f:0a:02 | ||
| port15 | Up | NL-BOS-PC013 | 10 users | 10.15.10.122 · d0:43:1e:0f:0a:03 | ||
| port16 | Up | NL-BOS-PH01 phone | 20 voice | 10.15.20.20 · 00:04:f2:0f:14:01 | 3.6 W class 2 | |
| port17 | Up | NL-BOS-PH02 phone | 20 voice | 10.15.20.21 · 00:04:f2:0f:14:02 | 3.8 W class 2 | |
| port18 | Up | PRN-BOS-01 | 40 printers | 10.15.40.20 · 3c:2a:f4:0f:28:01 | ||
| port19 | Up | CAM-LOBBY-01 | 50 cameras | 10.15.50.20 · 00:40:8c:0f:32:01 | 7.2 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00150001 |
Free ports: port1–2, port5–6, port11–12, port20–23, port25–28
S124FF15010001 · FortiSwitchOS 7.4.5
Address
On-site contacts
- Samira Patel · (215) 555-1015 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 2/15/2026 to 2/15/2029 · 816 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.25 /29
- Gateway
- 203.0.113.5
- Circuit ID
- NL-151
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 4/17/2026 to 4/17/2029 · 877 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.25 /29
- Gateway
- 198.51.100.5
- Circuit ID
- NL-152
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary5 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 | Static | chicago |
| 10.8.0.0/16 | Static | to-dallas → Dallas |
| 10.15.10.0/24 | Connected | users local network |
| 10.15.20.0/24 | Connected | voice local network |
| 10.15.30.0/24 | Connected | servers local network |
| 10.15.40.0/24 | Connected | printers local network |
| 10.15.50.0/24 | Connected | cameras local network |
| 10.15.90.0/24 | Connected | iot local network |
| 10.255.15.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 | 1.1 | 0 |
| 2026-11-22 | Example Fiber | 8.5 | 1.8 | 0 |
| 2026-11-21 | Metro Cable | 10.5 | 1.7 | 0 |
| 2026-11-21 | Example Fiber | 8.3 | 0.9 | 0 |
| 2026-11-20 | Metro Cable | 9.6 | 1.5 | 0 |
| 2026-11-20 | Example Fiber | 8.7 | 1.5 | 0 |
| 2026-11-19 | Metro Cable | 9.1 | 1.7 | 0 |
| 2026-11-19 | Example Fiber | 9 | 1.2 | 0.5 |
| 2026-11-18 | Metro Cable | 10.3 | 1 | 0 |
| 2026-11-18 | Example Fiber | 9.2 | 1.2 | 0 |
| 2026-11-17 | Metro Cable | 9.3 | 1.1 | 0.2 |
| 2026-11-17 | Example Fiber | 7.8 | 2 | 0 |
| 2026-11-16 | Metro Cable | 9.6 | 1.3 | 0.2 |
| 2026-11-16 | Example Fiber | 8.7 | 1.2 | 0.2 |
| 2026-11-15 | Metro Cable | 8.4 | 1.4 | 0 |
| 2026-11-15 | Example Fiber | 8.1 | 1.7 | 0 |
| 2026-11-14 | Metro Cable | 10.6 | 1.5 | 0.2 |
| 2026-11-14 | Example Fiber | 9.5 | 1.7 | 0 |
| 2026-11-13 | Metro Cable | 9.6 | 1.5 | 0 |
| 2026-11-13 | Example Fiber | 7.1 | 1.6 | 0 |
| 2026-11-12 | Metro Cable | 10.2 | 1.6 | 0.2 |
| 2026-11-12 | Example Fiber | 7.8 | 1.6 | 0 |
| 2026-11-11 | Metro Cable | 10.3 | 1.4 | 0 |
| 2026-11-11 | Example Fiber | 9.1 | 1.2 | 0 |
| 2026-11-10 | Metro Cable | 8.8 | 1.1 | 0 |
| 2026-11-10 | Example Fiber | 7.8 | 1.9 | 0 |
| 2026-11-09 | Metro Cable | 10.6 | 1.9 | 0 |
| 2026-11-09 | Example Fiber | 7.5 | 1.4 | 0 |
| 2026-11-08 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-08 | Example Fiber | 9.1 | 1.2 | 0 |
| 2026-11-07 | Metro Cable | 10.8 | 1.6 | 0.5 |
| 2026-11-07 | Example Fiber | 8.7 | 1.1 | 0 |
| 2026-11-06 | Metro Cable | 9 | 1.5 | 0 |
| 2026-11-06 | Example Fiber | 8.5 | 1.1 | 0.2 |
| 2026-11-05 | Metro Cable | 9 | 1 | 0 |
| 2026-11-05 | Example Fiber | 8.8 | 1.1 | 0.2 |
| 2026-11-04 | Metro Cable | 8.7 | 1.5 | 0 |
| 2026-11-04 | Example Fiber | 9.3 | 1.7 | 0.2 |
| 2026-11-03 | Metro Cable | 9.2 | 1.3 | 0 |
| 2026-11-03 | Example Fiber | 8.2 | 1.8 | 0 |
| 2026-11-02 | Metro Cable | 9.8 | 1.4 | 0 |
| 2026-11-02 | Example Fiber | 8.1 | 1.5 | 0 |
| 2026-11-01 | Metro Cable | 9.8 | 1.7 | 0.2 |
| 2026-11-01 | Example Fiber | 8.7 | 1.7 | 0 |
| 2026-10-31 | Metro Cable | 10.7 | 1.5 | 0 |
| 2026-10-31 | Example Fiber | 9.1 | 1.2 | 0.2 |
| 2026-10-30 | Metro Cable | 9.7 | 1.9 | 0.2 |
| 2026-10-30 | Example Fiber | 8.3 | 1.1 | 0.2 |
| 2026-10-29 | Metro Cable | 9.9 | 1.3 | 0.2 |
| 2026-10-29 | Example Fiber | 8.3 | 1.5 | 0.2 |
| 2026-10-28 | Metro Cable | 10.3 | 1.9 | 0 |
| 2026-10-28 | Example Fiber | 8.1 | 1.5 | 0.2 |
| 2026-10-27 | Metro Cable | 9.4 | 1.2 | 0 |
| 2026-10-27 | Example Fiber | 9.2 | 1.8 | 0 |
| 2026-10-26 | Metro Cable | 9 | 0.8 | 0.2 |
| 2026-10-26 | Example Fiber | 9.2 | 1.8 | 0 |
| 2026-10-25 | Metro Cable | 10.3 | 1.5 | 0.2 |
| 2026-10-25 | Example Fiber | 9.2 | 1.8 | 0 |
| 2026-10-24 | Metro Cable | 10.4 | 1.7 | 0.2 |
| 2026-10-24 | Example Fiber | 8.8 | 1.5 | 0.2 |
| 2026-10-23 | Metro Cable | 8.4 | 1 | 0 |
| 2026-10-23 | Example Fiber | 9.6 | 0.9 | 0 |
Tunnel stability – last 7 days
3 tunnels · 1 up on every run in the last 7 days.
| Tunnel | Times it went down | Up |
|---|---|---|
| to-chicago | 1 | 65% |
| to-chicago-b | 1 | 65% |
Configuration & routing changes – last 30 days 5
| When | Type | What | Detail |
|---|---|---|---|
| Nov 15 7:47 AM | Config | Interface printers | description: – → Floor 2 printers |
| Nov 15 7:08 AM | Config | Firewall policy 48 | edited: schedule always → business-hours |
| Nov 12 9:16 AM | Config | Admin netops-10 | trusthost1: 0.0.0.0 0.0.0.0 → 10.1.30.0 255.255.255.0 |
| Nov 9 10:39 AM | Routing | Route 10.1.60.0/24 | added via to-chicago (OSPF) |
| Nov 9 7:57 AM | Config | Firewall policy 18 | edited: schedule always → business-hours |
New and moved devices – last 30 days 1
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 11:11 AM | New deviceWired | New device 00:06:8e:1f:2d:83 | 10.15.90.2 DOOR-FRONT on FG-BOSTON-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
- Redundancy reduced2
- ●no tunnel to Chicago
- No working IPsec tunnel to Chicago – every tunnel to that site is down
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/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-chicago-b' 198.51.100.11:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0How to fix
Some IPsec tunnels to other sites are down. If the aggregate's other member is up, traffic still flows – this is lost redundancy, not an outage. Backup tunnels whose phase 2 isn't set to auto-negotiate stay down until traffic needs them, so they look down here.
- Check the tunnel from this end (and the other site's end) – the WAN page's Tunnel paths tab shows both.
- For backup tunnels, enable auto-negotiate on their phase 2 (below) so they stay up.
- Tunnels that point at the wrong IP or a site that no longer exists: fix the remote gateway, or delete them.
to-chicago → 203.0.113.11
to-chicago-b → 198.51.100.11get vpn ipsec tunnel summary diagnose vpn tunnel list name to-chicago diagnose vpn tunnel list name to-chicago-b - ●preferred tunnel down
- IPsec aggregate chicago: its first member to-chicago is down (dialling 203.0.113.11) – traffic is on to-dallas
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system ipsec-aggregateconfig system ipsec-aggregate edit "chicago" set member "to-chicago" "to-dallas" set algorithm redundant next endget vpn ipsec tunnel summary'to-chicago' 203.0.113.11:0 selectors(total,up): 1/0 rx(pkt,err): 0/0 tx(pkt,err): 0/0 'to-dallas' 203.0.113.18:0 selectors(total,up): 1/1 rx(pkt,err): 66620/0 tx(pkt,err): 69134/0show vpn ipsec phase1-interfaceconfig vpn ipsec phase1-interface edit "to-chicago" set interface "wan1" set remote-gw 203.0.113.11 set ike-version 2 next endHow to fix
'redundant' sends everything over the first member that is up. The first member here is down, so this site is on its backup path to the far end – and if that path fails too, there is nothing left.
- Why is it down? Check the address it dials is still the far end's (an 'unknown address' item on this page means it is not).
- If that circuit is gone for good, take the tunnel out of the aggregate at BOTH ends, so the working tunnel is first.
- After changing an aggregate: renegotiate its tunnels and check the running aggregate.
# on the PRIMARY unit (get system status | grep -i 'HA mode') # safe to share (no keys): get vpn ipsec tunnel summary diagnose sys ipsec-aggregate list # 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. - Configuration2
- ●aggregate-member flag
- in an aggregate with aggregate-member disabled: to-chicago (chicago); to-dallas (chicago)
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-chicago" set interface "wan1" set remote-gw 203.0.113.11 next end config vpn ipsec phase1-interface edit "to-dallas" set interface "wan1" set remote-gw 203.0.113.18 next endshow system ipsec-aggregateconfig system ipsec-aggregate edit "chicago" set member "to-chicago" "to-dallas" set algorithm redundant next endHow to fix
A tunnel listed in an IPsec aggregate should have aggregate-member enable; a tunnel with that flag and no aggregate is left out of the bundle. Either way the FortiGate may send on a member the other end does not expect.
- Enable aggregate-member on every tunnel that is in an aggregate.
- Clear the flag on a tunnel that is not in any aggregate, or add it to the aggregate at both ends.
config vpn ipsec phase1-interface edit "to-chicago" set aggregate-member enable next edit "to-dallas" set aggregate-member enable next end show system ipsec-aggregate - ●aggregate not paired
- IPsec aggregate chicago: members do not all end at one known site, so the order, mode and missing-member checks did not run (peers: Chicago, Dallas)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system ipsec-aggregateconfig system ipsec-aggregate edit "chicago" set member "to-chicago" "to-dallas" set algorithm redundant next endHow to fix
The both-ends checks (order, mode, missing member) only run when every member of an aggregate ends at one known site. When they do not, or when both members leave on the same local WAN, those checks are skipped or treat the members as two paths by the far circuit – this note says so.
- If the members should all go to one site, fix the remote gateways so they map.
- If two members share a WAN on purpose, the path order is still by the far end's circuit.
# safe to share (no keys): show system ipsec-aggregate show vpn ipsec phase1-interface get vpn ipsec tunnel summary
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 Boston 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-BOSTON FortiGate · FortiGate 40F | FGDEMO00150001 tag NL-0015 | Boston Northline | 2024-04-25 2.6 years old PO PO-55516 · Example Reseller | Standard 2028-12-16 contract NL-SUP-15 warranty 2025-04-25 passed | 2032-09-30 end of order 2027-09-30 | 2030 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-BOSTON-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF15010001 tag NL-15S01 | Boston · Closet 1 · Rack 1 Network team | 2024-02-15 2.8 years old PO PO-56150 · 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: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-BOSTON-AP1 FortiAP · FAP231F | FP231F15010001 tag NL-15A01 | Boston · Ceiling, zone 1 Network team | 2022-05-10 4.5 years old PO PO-57150 · 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-BOSTON-AP2 FortiAP · FAP231F | FP231F15020001 tag NL-15A02 | Boston · Ceiling, zone 2 Network team | 2023-05-10 3.5 years old PO PO-57151 · 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. |
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-151 | 500/500 | 9 ms collector ping | 2026-02-15 | 2029-02-15 give notice within 726 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-152 | 300/30 | 9 ms collector ping | 2026-04-17 | 2029-04-17 give notice within 817 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.15.10.0/24 | 10.15.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Boston network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.15.20.0/24 | 10.15.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Boston network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.15.30.0/24 | 10.15.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Boston network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.15.40.0/24 | 10.15.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Boston network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.15.50.0/24 | 10.15.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Boston network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.15.90.0/24 | 10.15.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Boston 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.