Consistency across sites
Settings that should match · built Sun Nov 22 2026 04:16 PMWhere the same setting appears at every site, the usual value is the one most sites share. Anything else is marked as the odd one out.
What is compared
show is marked (default). Wi-Fi security – each SSID's security mode and PMF. Firmware – the FortiGate version(s) at the site (switches and access points are on the Firmware page). DHCP options – DNS servers, NTP servers and domain name across the site's enabled DHCP servers. OSPF – router-id, areas, networks and interface timers from show router ospf only. Neighbour state is left out. BGP – local AS, router-id and neighbour remote-AS from show router bgp (neighbour state is not read). Policy routes – match and action fields from show router policy. Static default – whether a default is set in show router static, its administrative distance, and how many blackhole routes are defined (not every static route). SD-WAN – member interface names, health-check names/protocol, and service/rule names with strategy (not every match clause). Absent SD-WAN is skipped like empty OSPF. SSL VPN / portals – status, port when present, and tunnel vs web mode per portal (no realm secrets). Automation – stitch names with trigger types and action kinds (no webhook URLs or tokens). Services – custom service name with a compact proto/port fingerprint. A router-id or AS is often unique on purpose, so a fleet of unique values may have no single usual value. A site with nothing in a category is listed under that section and is not counted as odd. A DECOM comment on OSPF or BGP is left out the same way. This page does not change a site's colour.IPsec proposals
IKE version, proposal and DH group on site-to-site tunnels. Each distinct phase-1 profile is a row. Orange marks a value that differs from the usual.
Usual · Atlanta, Azure East, Azure West, Boston, Charlotte, Charlotte OT, Chicago, Dallas, Denver, Detroit, Detroit OT, Houston, Houston OT, Miami, Minneapolis, New York, Philadelphia, Phoenix, Seattle19 sites
| IKE | Proposal | DH | PQ | PPK | P2 |
|---|---|---|---|---|---|
| IKEv2 | aes256-sha256 | 14 | (none) | (none) | (none) |
Odd one out · Los Angeles1 site
| IKE | Proposal | DH | PQ | PPK | P2 |
|---|---|---|---|---|---|
| IKEv2 | aes256-sha256 | 14 | (none) | (none) | (none) |
| IKEv? (default) | aes128-sha1 | 5 | (none) | (none) | (none) |
sites with no site-to-site IPsec (or no output):
Wi-Fi security
Security mode and PMF on each SSID.
Usual · Atlanta, Boston, Charlotte, Chicago, Dallas, Denver, Detroit, Houston, Los Angeles, Miami, New York, Philadelphia, Phoenix, Seattle14 sites
| SSID | Security | PMF |
|---|---|---|
| Northline-Guest | owe | enable |
| Northline-IoT | wpa3-sae-transition | optional |
| Northline | wpa2-only-enterprise | optional |
Odd one out · Charlotte OT, Detroit OT, Houston OT3 sites
| SSID | Security | PMF |
|---|---|---|
| Northline-IoT | wpa3-sae-transition | optional |
| Northline | wpa2-only-enterprise | optional |
Odd one out · Minneapolis1 site
| SSID | Security | PMF |
|---|---|---|
| Northline-Guest | owe | enable |
| Northline-IoT | wpa3-sae-transition | optional |
| Northline | wpa2-only-personal | off |
sites with no SSIDs (or no output): Azure East, Azure West,
Firmware
FortiGate firmware version at each site.
| Sites | FortiGate version | |
|---|---|---|
| Atlanta, Azure East, Azure West, Boston, Charlotte, Charlotte OT, Chicago, Denver, Detroit, Detroit OT, Houston, Houston OT, Los Angeles, Miami, Minneapolis, New York, Philadelphia, Phoenix, Seattle (19) | Usual | 7.4.8 |
| Dallas (1) | Odd one out | 7.2.4 |
sites with no FortiGate version yet:
DHCP options
DNS, NTP and domain name on the FortiGate's DHCP servers.
| Sites | DNS | NTP | Domain | |
|---|---|---|---|---|
| Atlanta, Boston, Charlotte, Charlotte OT, Chicago, Dallas, Denver, Detroit, Detroit OT, Houston, Houston OT, Los Angeles, Minneapolis, New York, Philadelphia, Phoenix, Seattle (17) | Usual | 10.1.30.2, 10.1.30.3 | 10.1.30.2, 10.1.30.3 | northline.example.com |
| Miami (1) | Odd one out | 10.14.10.1, 10.14.20.1, 10.14.30.1, 10.14.40.1, 10.14.50.1, 10.14.90.1 | 10.1.30.2, 10.1.30.3 | northline.example.com |
sites with no DHCP servers (or no output): Azure East, Azure West,
OSPF
Router-id, areas, networks and interface timers. Neighbour state is not compared. A unique router-id is normal and may mean there is no single usual value.
No single usual value – two or more settings are tied for most common, or fewer than two sites share one.
| Sites | Value |
|---|---|
| Chicago (1) | router-id 10.1.0.1 | area 0.0.0.0 | network 10.254.0.0/16 |
| Denver (1) | router-id 10.10.0.1 | area 0.0.0.0 | network 10.254.10.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Seattle (1) | router-id 10.11.0.1 | area 0.0.0.0 | network 10.254.11.0/24 | iface to-chicago on to-chicago |
| New York (1) | router-id 10.12.0.1 | area 0.0.0.0 | network 10.254.12.0/24 | iface to-chicago on to-chicago hello 30 dead 120 |
| Los Angeles (1) | router-id 10.13.0.1 | area 0.0.0.0 | network 10.254.13.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Miami (1) | router-id 10.14.0.1 | area 0.0.0.0 | network 10.254.14.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Boston (1) | router-id 10.15.0.1 | area 0.0.0.0 | network 10.254.15.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Minneapolis (1) | router-id 10.16.0.1 | area 0.0.0.0 | network 10.254.16.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Phoenix (1) | router-id 10.17.0.1 | area 0.0.0.0 | network 10.254.17.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Philadelphia (1) | router-id 10.18.0.1 | area 0.0.0.0 | network 10.254.18.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Azure East (1) | router-id 10.19.0.1 | area 0.0.0.0 | network 10.254.19.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Houston (1) | router-id 10.2.0.1 | area 0.0.0.0 | network 10.254.2.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Azure West (1) | router-id 10.20.0.1 | area 0.0.0.0 | network 10.254.20.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Detroit (1) | router-id 10.4.0.1 | area 0.0.0.0 | network 10.254.4.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Charlotte (1) | router-id 10.6.0.1 | area 0.0.0.0 | network 10.254.6.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Dallas (1) | router-id 10.8.0.1 | area 0.0.0.0 | network 10.254.8.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
| Atlanta (1) | router-id 10.9.0.1 | area 0.0.0.0 | network 10.254.9.0/24 | iface to-chicago on to-chicago | iface to-chicago-b on to-chicago-b |
sites with no OSPF (or marked DECOM): Charlotte OT, Detroit OT, Houston OT
BGP
Local AS, router-id and configured neighbours. Neighbour state is not compared.
No single usual value – two or more settings are tied for most common, or fewer than two sites share one.
| Sites | Value |
|---|---|
| Chicago (1) | as 65000 | router-id 10.1.0.1 | neighbor 10.254.11.2 remote-as 65000 | neighbor 10.254.19.2 remote-as 65019 soft-reconfig enable | neighbor 10.254.19.6 remote-as 65019 soft-reconfig enable | neighbor 10.254.20.2 remote-as 65020 soft-reconfig enable | neighbor 10.254.20.6 remote-as 65020 soft-reconfig enable | neighbor 10.254.8.2 remote-as 65000 | network 10.1.0.0/16 | ebgp-multipath enable | graceful-restart enable |
| Seattle (1) | as 65000 | router-id 10.11.0.1 | neighbor 10.254.11.1 remote-as 65000 |
| Dallas (1) | as 65000 | router-id 10.8.0.1 | neighbor 10.254.8.1 remote-as 65000 |
| Azure East (1) | as 65019 | router-id 10.19.0.1 | neighbor 10.254.19.1 remote-as 65000 | neighbor 10.254.19.5 remote-as 65000 | network 10.19.0.0/16 |
| Azure West (1) | as 65020 | router-id 10.20.0.1 | neighbor 10.254.20.1 remote-as 65000 | neighbor 10.254.20.5 remote-as 65000 | network 10.20.0.0/16 |
sites with no BGP (or marked DECOM): Atlanta, Boston, Charlotte, Charlotte OT, Denver, Detroit, Detroit OT, Houston, Houston OT, Los Angeles, Miami, Minneapolis, New York, Philadelphia, Phoenix
Policy routes
Policy-based routes from the FortiGate configuration.
No single usual value – two or more settings are tied for most common, or fewer than two sites share one.
| Sites | Value |
|---|---|
| Chicago (1) | rule 1 in cameras src 10.1.50.0/255.255.255.0 dst 0.0.0.0/0.0.0.0 gw 198.51.100.9 out wan2 | rule 2 in servers src 10.1.30.40/255.255.255.255 dst 0.0.0.0/0.0.0.0 gw 192.0.2.86 out wan4 proto 6 |
| Dallas (1) | rule 1 in users src 10.8.10.64/255.255.255.192 dst 10.19.0.0/255.255.0.0 gw 10.254.8.1 out to-chicago |
sites with no policy routes: Atlanta, Azure East, Azure West, Boston, Charlotte, Charlotte OT, Denver, Detroit, Detroit OT, Houston, Houston OT, Los Angeles, Miami, Minneapolis, New York, Philadelphia, Phoenix, Seattle
Static default
Default route in static configuration (presence, gateway or device, distance) and blackhole route count.
Every compared site matches: no default in static | blackhole routes 3
Sites: Atlanta, Azure East, Azure West, Boston, Charlotte, Charlotte OT, Chicago, Dallas, Denver, Detroit, Detroit OT, Houston, Houston OT, Los Angeles, Miami, Minneapolis, Philadelphia, Phoenix, Seattle
sites with no static routes configured: , New York
SD-WAN
Member interfaces, health-check names/protocol, and service rule names with strategy.
| Sites | Value | |
|---|---|---|
| Atlanta, Charlotte, Dallas, Denver, Houston, Los Angeles, Miami, Minneapolis, New York, Philadelphia, Phoenix (11) | Usual | members wan1, wan2 · hc Internet/ping · svc Teams-Audio+sla, Teams-Video+sla, Microsoft-Teams+sla, Guest-Internet+load-balance |
| Azure East, Azure West (2) | Odd one out | members wan1, wan2 · hc Internet/ping · svc Branch-backhaul+priority |
| Detroit (1) | Odd one out | members wan1, wan2 · hc Internet/ping · svc Microsoft-Teams+sla, Teams-Audio+sla, Teams-Video+sla, Guest-Internet+load-balance |
| Boston (1) | Odd one out | members wan1, wan2 · hc Internet/ping · svc Teams-Audio+sla, Microsoft-Teams+sla, Guest-Internet+load-balance |
| Seattle (1) | Odd one out | members wan1, wan2 · hc Internet/ping, Monitor/http · svc Teams-Audio+sla, Teams-Video+sla, Microsoft-Teams+sla, Guest-Internet+load-balance |
| Chicago (1) | Odd one out | members wan1, wan2, wan3, wan4 · hc Internet/ping, Starlink/ping · svc Teams-Audio+sla, Teams-Video+sla, Microsoft-Teams+sla, Guest-Internet+load-balance |
sites with no SD-WAN (or no members): Charlotte OT, Detroit OT, Houston OT
SSL VPN / portals
Status, port when present, and tunnel vs web mode per portal. Secrets stay out.
| Sites | Value | |
|---|---|---|
| Atlanta, Azure East, Azure West, Boston, Charlotte, Charlotte OT, Denver, Detroit, Detroit OT, Houston OT, Los Angeles, Miami, Minneapolis, New York, Philadelphia, Phoenix, Seattle (17) | Usual | status disable · port 443 |
| Chicago (1) | Odd one out | status enable · port 10443 · portals IT-Admin:tunnel, no-access:neither, Northline-Staff:tunnel |
| Houston (1) | Odd one out | status enable · port 10443 · portals no-access:neither, Plant-Engineers:tunnel |
| Dallas (1) | Odd one out | status enable · port 443 · portals Warehouse-Vendors:tunnel+web |
sites with no SSL VPN settings (or no output):
Automation
Stitch names with trigger types and action kinds. Webhook URLs and tokens stay out.
| Sites | Value | |
|---|---|---|
| Atlanta, Azure East, Azure West, Boston, Charlotte OT, Denver, Detroit OT, Houston OT, Los Angeles, Miami, Minneapolis, New York, Philadelphia, Phoenix (14) | Usual | License Expired Notification:license-near-expiry/fortiexplorer-notification | Network Down:event-log/email | Northline Config Change:config-change/email | Northline Tunnel Down:event-log/webhook |
| Charlotte, Detroit (2) | Odd one out | License Expired Notification:license-near-expiry/fortiexplorer-notification | Network Down:event-log/email | Northline Config Change:config-change/email | Northline HA Failover:ha-failover/webhook | Northline Tunnel Down:event-log/webhook |
| Chicago (1) | Odd one out | Admin Lockdown on Brute Force:event-log/cli-script | License Expired Notification:license-near-expiry/fortiexplorer-notification | Network Down:event-log/email | Northline Config Change:config-change/email | Northline HA Failover:ha-failover/webhook | Northline Tunnel Down:event-log/webhook | Quarantine Compromised Host:ioc/quarantine |
| Houston (1) | Odd one out | IoT VLAN Shut on IOC:ioc/cli-script | License Expired Notification:license-near-expiry/fortiexplorer-notification | Network Down:event-log/email | Northline Config Change:config-change/email | Northline HA Failover:ha-failover/webhook | Northline Tunnel Down:event-log/webhook |
| Dallas (1) | Odd one out | License Expired Notification:license-near-expiry/fortiexplorer-notification | Network Down:event-log/email | Northline Config Change:config-change/email | Northline Tunnel Down:event-log/webhook | Vendor RDP Open:incoming-webhook/cli-script |
| Seattle (1) | Odd one out | License Expired Notification:license-near-expiry/fortiexplorer-notification | Network Down:event-log/email | Northline Config Change:config-change/email | Northline Tunnel Down:event-log/webhook | Weekly Config Backup:scheduled/cli-script |
sites with no automation stitches (or no output):
Custom services
Custom firewall service name with a compact proto/port fingerprint.
| Sites | Value | |
|---|---|---|
| Boston, Charlotte, Detroit, Miami, New York, Philadelphia (6) | Usual | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | HQ-ERP:TCP/8000-8010 | IPP-Print:TCP/631 | MS-Teams-Media:UDP/3478-3481 | RTP-Voice:UDP/16384-32767 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Atlanta, Denver, Seattle (3) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | FTP-Scanner:TCP/21 | HQ-ERP:TCP/8000-8010 | IPP-Print:TCP/631 | MS-Teams-Media:UDP/3478-3481 | RTP-Voice:UDP/16384-32767 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Houston, Phoenix (2) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | HQ-ERP:TCP/8000-8010 | IPP-Print:TCP/631 | MS-RDP:TCP/3389 | MS-Teams-Media:UDP/3478-3481 | RTP-Voice:UDP/16384-32767 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Charlotte OT, Houston OT (2) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | EtherNet-IP:TCP/44818 UDP/2222 | Modbus-TCP:TCP/502 | VNC-HMI:TCP/5900 |
| Azure East, Azure West (2) | Odd one out | Azure-App-8443:TCP/8443 | HQ-ERP:TCP/8000-8010 |
| Chicago (1) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | FTP-Partner:TCP/21 | HQ-ERP:TCP/8000-8010 | IPP-Print:TCP/631 | MS-RDP:TCP/3389 | MS-Teams-Media:UDP/3478-3481 | Order-Portal-8443:TCP/8443 | RTP-Voice:UDP/16384-32767 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Dallas (1) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | FTP-Scanner:TCP/21 | HQ-ERP:TCP/8000-8020 | IPP-Print:TCP/631 | Legacy-Telnet:TCP/23 | MS-RDP:TCP/3389 | MS-Teams-Media:UDP/3478-3481 | RTP-Voice:UDP/16384-32767 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Minneapolis (1) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | HQ-ERP:TCP/8000-8010 | IPP-Print:TCP/631 | RTP-Voice:UDP/16384-32767 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Los Angeles (1) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | Collector-API:TCP/443 | HQ-ERP:TCP/8000-8010 | IPP-Print:TCP/631 | SIP-Trunk:TCP/5060-5061 UDP/5060-5061 | Zebra-Print:TCP/9100 |
| Detroit OT (1) | Odd one out | Axis-Video:TCP/554 80 | Backup-Veeam:TCP/9392-9401 2500-3300 | EtherNet-IP:TCP/44818 UDP/2222 | Legacy-Telnet:TCP/23 | Modbus-TCP:TCP/502 | VNC-HMI:TCP/5900 |
sites with no custom services (or no output):