Vantage / Monitoring / Status / Monitor
Monitor Every site as a tree: internet, FortiGate, switches, access points, VLANs Green good · yellow something might be wrong · red bad or offline · grey not checked yet. A branch with red or yellow in it opens by itself; everything else starts folded. Devices come from what the FortiGates report (servers, storage, printers, IoT/OT, cameras, UPS, lab) and are pinged, and polled over SNMPv3 when that is on. A device that has not answered for 30 days is taken off the list.
18 red22 yellow532 green
Atlanta 4 red1 yellow57 green Internetbusiest wan1 39% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 12 ms 0% Metro Cable gateway 198.51.100.17 ping 17 ms 0%
FortiGate FG-ATLANTACPU 16% Mem 50% Sessions 5,834 up 195 days Interface IP Ping CPU Mem Worst link Atlanta FortiGate 10.250.0.9 27 ms — — wan2 · 0.0 err/h atlanta FortiGate (users) 10.9.10.1 27 ms — — —
Switches5 Switch Model Firmware State FG-ATLANTA-SW1 FortiSwitch 124F-FPOE 7.4.5 up 79 days FG-ATLANTA-SW2 FortiSwitch 124F-FPOE 7.4.5 up 255 days FG-ATLANTA-SW3 FortiSwitch 124F-FPOE 7.4.5 up 194 days FG-ATLANTA-SW4 FortiSwitch 124F-FPOE 7.4.5 up 220 days FG-ATLANTA-SW5 FortiSwitch 124F-FPOE 7.4.5 up 238 days
Access points17 Access point Model State FG-ATLANTA-AP15 FP231F offline FG-ATLANTA-AP16 FP231F offline FG-ATLANTA-APNEW FP231F offline FG-ATLANTA-AP1 FP231F connected · up 146 days FG-ATLANTA-AP2 FP231F connected · up 76 days FG-ATLANTA-AP3 FP231F connected · up 16 days FG-ATLANTA-AP4 FP231F connected · up 50 days FG-ATLANTA-AP5 FP231F connected · up 71 days FG-ATLANTA-AP6 FP231F connected · up 155 days FG-ATLANTA-AP7 FP231F connected · up 69 days FG-ATLANTA-AP8 FP231F connected · up 139 days FG-ATLANTA-AP9 FP231F connected · up 145 days FG-ATLANTA-AP10 FP231F connected · up 39 days FG-ATLANTA-AP11 FP231F connected · up 140 days FG-ATLANTA-AP12 FP231F connected · up 51 days FG-ATLANTA-AP13 FP231F connected · up 116 days FG-ATLANTA-AP14 FP231F connected · up 101 days
VLANs6 VLAN 10 · users10.9.10.0/24 20 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.9.10.80 10.9.10.80 printer 31 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.81 10.9.10.81 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.82 10.9.10.82 printer 39 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.83 10.9.10.83 printer 28 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.84 10.9.10.84 printer 28 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.85 10.9.10.85 printer 31 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.86 10.9.10.86 printer 23 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.87 10.9.10.87 printer 35 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.88 10.9.10.88 printer 36 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.89 10.9.10.89 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.90 10.9.10.90 printer 19 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.91 10.9.10.91 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.92 10.9.10.92 printer 32 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.93 10.9.10.93 printer 36 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.94 10.9.10.94 printer 42 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.95 10.9.10.95 printer 37 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.96 10.9.10.96 printer 21 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.97 10.9.10.97 printer 18 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.98 10.9.10.98 printer 23 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.9.10.99 10.9.10.99 printer 32 ms — — — Ethernet · 0.0 err/h
VLAN 20 · voice10.9.20.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PAGE-WHSE 10.9.20.2 other 17 ms — — — eth0 · 0.0 err/h
VLAN 30 · servers10.9.30.0/24 7 devicesDevice IP Type Ping CPU Mem Disk Worst link BACKUP01 10.9.30.5 backup no answer since Sun 22 Nov 15:44 · 32 min ago DC01 10.9.30.2 dc 46 ms 3.4% 45.6% 41.1% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.9.30.3 file 31 ms 24.2% 51.2% 44.2% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.9.30.6 file 40 ms 3.8% 15.9% 29.5% ens192 · 0.0 err/h NAS01 10.9.30.7 storage 36 ms 15.1% 38.3% 97.8% eth0 · 0.0 err/h UPS-MDF 10.9.30.8 ups 44 ms — — — LanInterface · 0.0 err/h WMS01 10.9.30.4 file 27 ms 11.4% 53.4% 35.5% vmxnet3 Ethernet Adapter · 0.0 err/h
VLAN 40 · printers10.9.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-ATL-01 10.9.40.20 printer 24 ms — 28.4% — eth0 · 0.0 err/h
VLAN 50 · cameras10.9.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-DOCK-01 10.9.50.20 sensor 22 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.9.90.0/24 5 devicesDevice IP Type Ping CPU Mem Disk Worst link DOCK-ATL-01 10.9.90.30 printer 16 ms — 52.4% — eth0 · 0.0 err/h DOCK-ATL-02 10.9.90.31 printer 28 ms — 22.1% — eth0 · 0.0 err/h DOOR-DOCK1 10.9.90.2 door 18 ms — — — eth0 · 0.0 err/h DOOR-DOCK2 10.9.90.3 door 16 ms — — — eth0 · 0.0 err/h ENV-FREEZER 10.9.90.4 sensor 36 ms — — — eth0 · 0.0 err/h
Charlotte 1 red0 yellow21 green Internetbusiest wan1 39% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 14 ms 0% Metro Cable gateway 198.51.100.17 ping 17 ms 0%
FortiGate FG-CHARLOTTECPU 17% Mem 48% Sessions 4,190 up 159 days Interface IP Ping CPU Mem Worst link Charlotte FortiGate 10.250.0.6 28 ms — — wan1 · 0.0 err/h charlotte FortiGate (users) 10.6.10.1 22 ms — — —
Switches2 Switch Model Firmware State FG-CHARLOTTE-SW1 FortiSwitch 124F-FPOE 7.4.5 up 130 days FG-CHARLOTTE-SW2 FortiSwitch 124F-FPOE 7.4.5 up 209 days
Access points4 Access point Model State FG-CHARLOTTE-AP1 FP231F connected · up 114 days FG-CHARLOTTE-AP2 FP231F connected · up 139 days FG-CHARLOTTE-AP3 FP231F connected · up 151 days FG-CHARLOTTE-AP4 FP231F connected · up 138 days
VLANs6 VLAN 30 · servers10.6.30.0/24 6 devicesDevice IP Type Ping CPU Mem Disk Worst link DC01 10.6.30.2 dc 42 ms 6.8% 72.0% 31.8% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.6.30.3 file 28 ms 16.1% 65.2% 50.9% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.6.30.5 file 20 ms 3.7% 15.8% 23.7% lo · 0.0 err/h MES01 10.6.30.4 file 20 ms 32.6% 66.5% 37.5% vmxnet3 Ethernet Adapter · 0.0 err/h NAS01 10.6.30.6 storage 40 ms 5.6% 36.4% 53.4% eth0 · 0.0 err/h UPS-MDF 10.6.30.7 ups 34 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.6.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-CLT-01 10.6.40.20 printer 37 ms — 47.0% — eth0 · 0.0 err/h
VLAN 50 · cameras10.6.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-DOCK-01 10.6.50.20 sensor 34 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.6.90.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link DOOR-DOCK 10.6.90.2 door 18 ms — — — — DOOR-MDF 10.6.90.3 door 27 ms — — — eth0 · 0.0 err/h ENV-MDF 10.6.90.4 sensor 18 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Dallas 1 red3 yellow76 green Internetbusiest wan1 91% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 15 ms 0% Metro Cable gateway 198.51.100.17 ping 8 ms 0%
FortiGate FG-DALLASCPU 86% Mem 75% Sessions 13,838 up 109 days Interface IP Ping CPU Mem Worst link Dallas FortiGate 10.250.0.8 29 ms — — voice · 0.0 err/h dallas FortiGate (users) 10.8.10.1 21 ms — — —
Switches6 Switch Model Firmware State FG-DALLAS-SW6 — — no answer FG-DALLAS-SW1 FortiSwitch 124F-FPOE 7.0.5 up 64 days FG-DALLAS-SW2 FortiSwitch 124F-FPOE 7.4.5 up 271 days FG-DALLAS-SW3 FortiSwitch 124F-FPOE 7.4.5 up 95 days · port14 108 errors/h FG-DALLAS-SW4 FortiSwitch 124F-FPOE 7.4.5 up 246 days FG-DALLAS-SW5 FortiSwitch 124F-FPOE 7.4.5 up 126 days
Access points20 Access point Model State FG-DALLAS-AP1 FP231F connected · up 70 days FG-DALLAS-AP2 FP231F connected · up 109 days FG-DALLAS-AP3 FP231F connected · up 98 days FG-DALLAS-AP4 FP231F connected · up 46 days FG-DALLAS-AP5 FP231F connected · up 170 days FG-DALLAS-AP6 FP231F connected · up 133 days FG-DALLAS-AP7 FP231F connected · up 14 days FG-DALLAS-AP8 FP231F connected · up 152 days FG-DALLAS-AP9 FP231F connected · up 13 days FG-DALLAS-AP10 FP231F connected · up 159 days FG-DALLAS-AP11 FP231F connected · up 69 days FG-DALLAS-AP12 FP231F connected · up 157 days FG-DALLAS-AP13 FP231F connected · up 47 days FG-DALLAS-AP14 FP231F connected · up 145 days FG-DALLAS-AP15 FP231F connected · up 153 days FG-DALLAS-AP16 FP231F connected · up 20 days FG-DALLAS-AP17 FP231F connected · up 107 days FG-DALLAS-AP18 FP231F connected · up 52 days FG-DALLAS-AP19 FP231F connected · up 148 days FG-DALLAS-AP20 FP231F connected · up 163 days
VLANs6 VLAN 10 · users10.8.10.0/24 24 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.8.10.100 10.8.10.100 printer 44 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.101 10.8.10.101 printer 17 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.102 10.8.10.102 printer 21 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.103 10.8.10.103 printer 28 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.80 10.8.10.80 printer 19 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.81 10.8.10.81 printer 33 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.82 10.8.10.82 printer 23 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.83 10.8.10.83 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.84 10.8.10.84 printer 39 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.85 10.8.10.85 printer 43 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.86 10.8.10.86 printer 45 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.87 10.8.10.87 printer 46 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.88 10.8.10.88 printer 31 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.89 10.8.10.89 printer 22 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.90 10.8.10.90 printer 22 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.91 10.8.10.91 printer 46 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.92 10.8.10.92 printer 30 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.93 10.8.10.93 printer 35 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.94 10.8.10.94 printer 19 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.95 10.8.10.95 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.96 10.8.10.96 printer 33 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.97 10.8.10.97 printer 36 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.98 10.8.10.98 printer 40 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.8.10.99 10.8.10.99 printer 36 ms — — — Ethernet · 0.0 err/h
VLAN 20 · voice10.8.20.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PAGE-WHSE 10.8.20.2 other 30 ms — — — eth0 · 0.0 err/h
VLAN 30 · servers10.8.30.0/24 7 devicesDevice IP Type Ping CPU Mem Disk Worst link BACKUP01 10.8.30.5 backup 20 ms 21.7% 65.6% 34.4% vmxnet3 Ethernet Adapter · 0.0 err/h DC01 10.8.30.2 dc 26 ms 13.1% 64.2% 50.6% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.8.30.3 file 26 ms 93.1% 62.8% 47.0% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.8.30.6 file 44 ms 5.0% 11.0% 22.6% lo · 0.0 err/h NAS01 10.8.30.7 storage 32 ms 11.8% 44.5% 81.7% bond0 · 0.0 err/h UPS-MDF 10.8.30.8 ups 36 ms — — — LanInterface · 0.0 err/h WMS01 10.8.30.4 file 17 ms 29.5% 73.6% 50.8% vmxnet3 Ethernet Adapter · 0.0 err/h
VLAN 40 · printers10.8.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-DAL-01 10.8.40.20 printer 41 ms — 58.4% — eth0 · 0.0 err/h
VLAN 50 · cameras10.8.50.0/24 11 devicesDevice IP Type Ping CPU Mem Disk Worst link CAM-AISLE-02 10.8.50.12 sensor 42 ms — — — eth0 · 0.0 err/h CAM-AISLE-03 10.8.50.16 sensor 31 ms — — — eth0 · 0.0 err/h CAM-DOCK-01 10.8.50.20 sensor 29 ms — — — eth0 · 0.0 err/h CAM-DOCK-02 10.8.50.10 sensor 28 ms — — — eth0 · 0.0 err/h CAM-DOCK-03 10.8.50.14 sensor 37 ms — — — eth0 · 0.0 err/h CAM-DOCK-04 10.8.50.18 sensor 28 ms — — — eth0 · 0.0 err/h CAM-GATE-02 10.8.50.13 sensor 20 ms — — — eth0 · 0.0 err/h CAM-GATE-03 10.8.50.17 sensor 29 ms — — — eth0 · 0.0 err/h CAM-YARD-02 10.8.50.11 sensor 36 ms — — — eth0 · 0.0 err/h CAM-YARD-03 10.8.50.15 sensor 30 ms — — — eth0 · 0.0 err/h CAM-YARD-04 10.8.50.19 sensor 34 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.8.90.0/24 5 devicesDevice IP Type Ping CPU Mem Disk Worst link DOCK-DAL-01 10.8.90.30 printer 25 ms — 31.1% — eth0 · 0.0 err/h DOCK-DAL-02 10.8.90.31 printer 35 ms — 46.3% — eth0 · 0.0 err/h DOOR-DOCK1 10.8.90.2 door 19 ms — — — eth0 · 0.0 err/h DOOR-DOCK2 10.8.90.3 door 22 ms — — — eth0 · 0.0 err/h ENV-FREEZER 10.8.90.4 sensor 18 ms — — — eth0 · 0.0 err/h
Houston OT 1 red0 yellow34 green Internet0 linksLink IP Checked by Latency Loss No internet link found in the collection
FortiGate FG-HOUSTONOTCPU 17% Mem 48% Sessions 1,572 up 232 days Interface IP Ping CPU Mem Worst link Houston OT FortiGate 10.250.0.3 15 ms — — voice · 0.0 err/h houston-ot FortiGate (users) 10.3.10.1 22 ms — — —
Switches4 Switch Model Firmware State FG-HOUSTONOT-SW1 FortiSwitch 124F-FPOE 7.4.5 up 40 days FG-HOUSTONOT-SW2 FortiSwitch 124F-FPOE 7.4.5 up 115 days FG-HOUSTONOT-SW3 FortiSwitch 124F-FPOE 7.4.5 up 37 days FG-HOUSTONOT-SW4 FortiSwitch 124F-FPOE 7.4.5 up 122 days
Access points2 Access point Model State FG-HOUSTONOT-AP1 FP231F connected · up 11 days FG-HOUSTONOT-AP2 FP231F connected · up 145 days
VLANs6 VLAN 10 · users10.3.10.0/24 2 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.3.10.80 10.3.10.80 printer 19 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.3.10.81 10.3.10.81 printer 22 ms — — — Ethernet · 0.0 err/h
VLAN 30 · servers10.3.30.0/24 2 devicesDevice IP Type Ping CPU Mem Disk Worst link HIST01 10.3.30.2 file 40 ms 17.4% 64.9% 52.5% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.3.30.3 file 23 ms 0.5% 17.9% 21.1% ens192 · 0.0 err/h
VLAN 90 · iot10.3.90.0/24 24 devicesDevice IP Type Ping CPU Mem Disk Worst link PLC-LINE2 10.3.90.5 plc no answer since Sun 22 Nov 15:44 · 32 min ago CAM-LINE-01 10.3.90.24 sensor 40 ms — — — eth0 · 0.0 err/h ENV-PANEL 10.3.90.8 sensor 25 ms — — — eth0 · 0.0 err/h HMI-HOU-01 10.3.90.16 ot 27 ms — — — X1 · 0.0 err/h HMI-HOU-02 10.3.90.17 ot 31 ms — — — X1 · 0.0 err/h HMI-HOU-03 10.3.90.18 ot 38 ms — — — X1 · 0.0 err/h HMI-HOU-04 10.3.90.19 ot 21 ms — — — X1 · 0.0 err/h HMI01 10.3.90.2 ot 36 ms — — — X2 · 0.0 err/h HMI02 10.3.90.3 ot 20 ms — — — X2 · 0.0 err/h IoT / industrial 10.3.90.25 10.3.90.25 ot 18 ms — — — eth0 · 0.0 err/h PLC-HOU-01 10.3.90.10 ot 31 ms — — — eth0 · 0.0 err/h PLC-HOU-02 10.3.90.11 ot 45 ms — — — eth0 · 0.0 err/h PLC-HOU-03 10.3.90.12 ot 16 ms — — — eth0 · 0.0 err/h PLC-HOU-04 10.3.90.13 ot 16 ms — — — eth0 · 0.0 err/h PLC-HOU-05 10.3.90.14 ot 29 ms — — — eth0 · 0.0 err/h PLC-HOU-06 10.3.90.15 ot 37 ms — — — eth0 · 0.0 err/h PLC-LINE1 10.3.90.4 plc 35 ms — — — X1 P1 · 0.0 err/h PLC-PACK 10.3.90.6 plc 42 ms — — — X1 P1 · 0.0 err/h UPS-PANEL 10.3.90.9 ups 42 ms — — — LanInterface · 0.0 err/h VFD-CONV1 10.3.90.7 ot 39 ms — — — X1 · 0.0 err/h VFD-HOU-01 10.3.90.20 ot 17 ms — — — X1 · 0.0 err/h VFD-HOU-02 10.3.90.21 ot 42 ms — — — X1 · 0.0 err/h VFD-HOU-03 10.3.90.22 ot 24 ms — — — X1 · 0.0 err/h VFD-HOU-04 10.3.90.23 ot 29 ms — — — X1 · 0.0 err/h
+ 3 VLANs with no monitored devices: 20 voice, 40 printers, 50 cameras
Philadelphia 10 red3 yellow0 green Internet3 linksLink IP Checked by Latency Loss wan1 — SD-WAN down wan2 — SD-WAN down Example Fiber gateway 203.0.113.1 ping no answer since Sun 22 Nov 10:56 · 5 h 20 min ago
FortiGate FortiGate-40FInterface IP Ping CPU Mem Worst link Philadelphia FortiGate 10.250.0.18 no answer since Sun 22 Nov 10:56 · 5 h 20 min ago philadelphia FortiGate (users) 10.18.10.1 no answer since Sun 22 Nov 10:56 · 5 h 20 min ago
Switches1 Switch Model Firmware State FG-PHILADELPH-SW1 FortiSwitch 124F-FPOE 7.4.5 up · SNMP no answer
Access points2 Access point Model State FG-PHILADELPH-AP1 FP231F connected · SNMP no answer FG-PHILADELPH-AP2 FP231F connected · SNMP no answer
VLANs6 VLAN 30 · servers10.18.30.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.18.30.2 file no answer since Sun 22 Nov 10:56 · 5 h 20 min ago IPERF01 10.18.30.3 file no answer since Sun 22 Nov 10:56 · 5 h 20 min ago UPS-MDF 10.18.30.4 ups no answer since Sun 22 Nov 10:56 · 5 h 20 min ago
VLAN 40 · printers10.18.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-PHL-01 10.18.40.20 printer no answer since Sun 22 Nov 10:56 · 5 h 20 min ago
VLAN 50 · cameras10.18.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.18.50.20 sensor no answer since Sun 22 Nov 10:56 · 5 h 20 min ago
VLAN 90 · iot10.18.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.18.90.2 door no answer since Sun 22 Nov 10:56 · 5 h 20 min ago
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Phoenix 1 red0 yellow13 green Internetbusiest wan1 74% 3 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN down Example Fiber gateway 203.0.113.7 ping 16 ms 0%
FortiGate FG-PHOENIXCPU 19% Mem 48% Sessions 811 up 227 days Interface IP Ping CPU Mem Worst link Phoenix FortiGate 10.250.0.17 35 ms — — wan1 · 0.0 err/h phoenix FortiGate (users) 10.17.10.1 39 ms — — —
Switches1 Switch Model Firmware State FG-PHOENIX-SW1 FortiSwitch 124F-FPOE 7.4.5 up 292 days
Access points2 Access point Model State FG-PHOENIX-AP1 FP231F connected · up 114 days FG-PHOENIX-AP2 FP231F connected · up 141 days
VLANs6 VLAN 30 · servers10.17.30.0/24 4 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.17.30.2 file 29 ms 29.5% 70.5% 53.3% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.17.30.3 file 43 ms 8.0% 12.0% 28.5% ens192 · 0.0 err/h NEW-PC 10.17.30.40 storage 27 ms 15.7% 29.9% 57.3% eth1 · 0.0 err/h UPS-MDF 10.17.30.4 ups 29 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.17.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-PHX-01 10.17.40.20 printer 20 ms — 43.5% — eth0 · 0.0 err/h
VLAN 50 · cameras10.17.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.17.50.20 sensor 20 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.17.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.17.90.2 door 44 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Azure East 0 red1 yellow9 green Internetbusiest wan1 39% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Path A gateway 203.0.113.2 ping 7 ms 0% Path B gateway 198.51.100.2 ping 11 ms 0%
FortiGate FG-AZUREEASTCPU 18% Mem 50% Sessions 17,660 up 107 days Interface IP Ping CPU Mem Worst link Azure East FortiGate 10.250.0.19 25 ms — — wan1 · 0.0 err/h
VLANs0 Other networks5 devicesDevice IP Type Ping CPU Mem Disk Worst link AZ-APP01 10.1.30.3 file 46 ms 9.0% 58.5% 47.1% Microsoft Hyper-V Network Adapter · 0.0 err/h AZ-APP02 10.1.30.4 file 22 ms 91.3% 58.3% 65.3% Microsoft Hyper-V Network Adapter · 0.0 err/h AZ-DC01 10.1.30.2 dc 25 ms 4.3% 65.7% 61.1% Microsoft Hyper-V Network Adapter · 0.0 err/h AZ-IPERF01 10.1.30.6 file 18 ms 3.2% 13.1% 23.1% lo · 0.0 err/h AZ-SQL01 10.1.30.5 file 24 ms 23.0% 63.5% 44.5% Microsoft Hyper-V Network Adapter · 0.0 err/h
Boston 0 red6 yellow8 green Internetbusiest wan1 46% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.5 ping 9 ms 0% Metro Cable gateway 198.51.100.5 ping 9 ms 0%
FortiGate FG-BOSTONCPU 18% Mem 48% Sessions 802 up 224 days Interface IP Ping CPU Mem Worst link Boston FortiGate 10.250.0.15 239 ms · 33% lost — — wan1 · 0.0 err/h boston FortiGate (users) 10.15.10.1 292 ms · 33% lost — — —
Switches1 Switch Model Firmware State FG-BOSTON-SW1 FortiSwitch 124F-FPOE 7.4.5 up 130 days
Access points2 Access point Model State FG-BOSTON-AP1 FP231F connected · up 27 days FG-BOSTON-AP2 FP231F connected · up 54 days
VLANs6 VLAN 30 · servers10.15.30.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.15.30.2 file 214 ms · 33% lost 15.4% 73.0% 28.1% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.15.30.3 file 210 ms · 33% lost 7.2% 19.7% 21.5% lo · 0.0 err/h UPS-MDF 10.15.30.4 ups 277 ms · 33% lost — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.15.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-BOS-01 10.15.40.20 printer 294 ms · 33% lost — 34.5% — eth0 · 0.0 err/h
VLAN 50 · cameras10.15.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.15.50.20 sensor 250 ms · 33% lost — — — eth0 · 0.0 err/h
VLAN 90 · iot10.15.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.15.90.2 door 260 ms · 33% lost — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Chicago 0 red3 yellow41 green Internetbusiest wan1 35% 7 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% wan3 — SD-WAN 41 ms 0% Example Fiber gateway 203.0.113.9 ping 8 ms 0% Example Fiber West gateway 192.0.2.86 ping 11 ms 0% Metro Cable gateway 198.51.100.9 ping 6 ms 0% Starlink gateway 192.0.2.9 ping 10 ms 0%
FortiGate FG-CHICAGOCPU 15% Mem 50% Sessions 31,438 up 157 days Interface IP Ping CPU Mem Worst link Chicago FortiGate 10.250.0.1 4 ms — — wan3 · 0.0 err/h chicago FortiGate (users) 10.1.10.1 3 ms — — —
Switches6 Switch Model Firmware State FG-CHICAGO-SW1 FortiSwitch 124F-FPOE 7.4.5 up 190 days FG-CHICAGO-SW2 FortiSwitch 124F-FPOE 7.4.5 up 174 days FG-CHICAGO-SW3 FortiSwitch 124F-FPOE 7.4.5 up 278 days FG-CHICAGO-SW4 FortiSwitch 124F-FPOE 7.4.5 up 48 days FG-CHICAGO-SW5 FortiSwitch 124F-FPOE 7.4.5 up 245 days FG-CHICAGO-SW6 FortiSwitch 124F-FPOE 7.4.5 up 257 days
Access points12 Access point Model State FG-CHICAGO-AP1 FP231F connected · up 64 days FG-CHICAGO-AP2 FP231F connected · up 74 days FG-CHICAGO-AP3 FP231F connected · up 160 days FG-CHICAGO-AP4 FP231F connected · up 48 days FG-CHICAGO-AP5 FP231F connected · up 134 days FG-CHICAGO-AP6 FP231F connected · up 171 days FG-CHICAGO-AP7 FP231F connected · up 21 days FG-CHICAGO-AP8 FP231F connected · up 24 days FG-CHICAGO-AP9 FP231F connected · up 155 days FG-CHICAGO-AP10 FP231F connected · up 24 days FG-CHICAGO-AP11 FP231F connected · up 114 days FG-CHICAGO-AP12 FP231F connected · up 139 days
VLANs6 VLAN 30 · servers10.1.30.0/24 13 devicesDevice IP Type Ping CPU Mem Disk Worst link BACKUP01 10.1.30.9 backup 3 ms 27.8% 59.7% 31.3% vmxnet3 Ethernet Adapter · 0.0 err/h DC01 10.1.30.2 dc 3 ms 5.8% 62.0% 60.1% vmxnet3 Ethernet Adapter · 0.0 err/h DC02 10.1.30.3 dc 3 ms 8.4% 53.7% 50.5% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.1.30.4 file 5 ms 31.2% 71.0% 27.0% vmxnet3 Ethernet Adapter · 0.0 err/h HV01 10.1.30.7 file 4 ms 37.2% 75.9% 59.3% Intel(R) Ethernet Controller X710 for 10 · 0.0 err/h HV02 10.1.30.8 file 2 ms 10.1% 95.6% 59.4% Microsoft Hyper-V Network Adapter · 0.0 err/h IPERF01 10.1.30.10 file 3 ms 5.3% 13.5% 19.0% ens192 · 0.0 err/h NAS01 10.1.30.12 storage 4 ms 12.8% 48.5% 69.3% eth0 · 0.0 err/h PRINT01 10.1.30.6 print 2 ms 12.3% 71.2% 70.0% vmxnet3 Ethernet Adapter · 0.0 err/h SAN01 10.1.30.11 storage 3 ms 9.4% 31.8% 99.5% eth3 · 0.0 err/h SQL01 10.1.30.5 file 3 ms 13.3% 50.0% 96.9% vmxnet3 Ethernet Adapter · 0.0 err/h UPS-IDF2 10.1.30.14 ups 2 ms — — — LanInterface · 0.0 err/h UPS-MDF 10.1.30.13 ups 5 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.1.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-CHI-01 10.1.40.20 printer 3 ms — 46.2% — eth0 · 0.0 err/h
VLAN 50 · cameras10.1.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.1.50.20 sensor 2 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.1.90.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link DOOR-LOBBY 10.1.90.2 door 2 ms — — — eth0 · 0.0 err/h DOOR-MDF 10.1.90.3 door 3 ms — — — eth0 · 0.0 err/h ENV-MDF 10.1.90.4 sensor 4 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Denver 0 red3 yellow51 green Internetbusiest wan1 37% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 280 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 289 ms 0% Metro Cable gateway 198.51.100.17 ping 14 ms 0%
FortiGate FG-DENVERCPU 16% Mem 48% Sessions 5,961 up 186 days Interface IP Ping CPU Mem Worst link Denver FortiGate 10.250.0.10 35 ms — — servers · 0.0 err/h denver FortiGate (users) 10.10.10.1 21 ms — — —
Switches4 Switch Model Firmware State FG-DENVER-SW1 FortiSwitch 124F-FPOE 7.4.5 up 201 days FG-DENVER-SW2 FortiSwitch 124F-FPOE 7.4.5 up 68 days FG-DENVER-SW3 FortiSwitch 124F-FPOE 7.4.5 up 201 days FG-DENVER-SW4 FortiSwitch 124F-FPOE 7.4.5 up 181 days
Access points14 Access point Model State FG-DENVER-AP1 FP231F connected · up 158 days FG-DENVER-AP2 FP231F connected · up 26 days FG-DENVER-AP3 FP231F connected · up 39 days FG-DENVER-AP4 FP231F connected · up 12 days FG-DENVER-AP5 FP231F connected · up 151 days FG-DENVER-AP6 FP231F connected · up 54 days FG-DENVER-AP7 FP231F connected · up 98 days FG-DENVER-AP8 FP231F connected · up 58 days FG-DENVER-AP9 FP231F connected · up 127 days FG-DENVER-AP10 FP231F connected · up 26 days FG-DENVER-AP11 FP231F connected · up 155 days FG-DENVER-AP12 FP231F connected · up 55 days FG-DENVER-AP13 FP231F connected · up 123 days FG-DENVER-AP14 FP231F connected · up 117 days
VLANs6 VLAN 10 · users10.10.10.0/24 16 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.10.10.80 10.10.10.80 printer 28 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.81 10.10.10.81 printer 37 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.82 10.10.10.82 printer 24 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.83 10.10.10.83 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.84 10.10.10.84 printer 42 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.85 10.10.10.85 printer 33 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.86 10.10.10.86 printer 28 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.87 10.10.10.87 printer 34 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.88 10.10.10.88 printer 30 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.89 10.10.10.89 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.90 10.10.10.90 printer 34 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.91 10.10.10.91 printer 27 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.92 10.10.10.92 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.93 10.10.10.93 printer 36 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.94 10.10.10.94 printer 20 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.10.10.95 10.10.10.95 printer 34 ms — — — Ethernet · 0.0 err/h
VLAN 20 · voice10.10.20.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PAGE-WHSE 10.10.20.2 other 30 ms — — — eth0 · 0.0 err/h
VLAN 30 · servers10.10.30.0/24 7 devicesDevice IP Type Ping CPU Mem Disk Worst link BACKUP01 10.10.30.5 backup 44 ms 9.8% 72.5% 64.0% vmxnet3 Ethernet Adapter · 0.0 err/h DC01 10.10.30.2 dc 40 ms 10.5% 52.8% 51.0% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.10.30.3 file 36 ms 25.6% 65.1% 61.8% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.10.30.6 file 40 ms 6.1% 16.9% 16.5% lo · 0.0 err/h NAS01 10.10.30.7 storage 16 ms 13.7% 53.5% 78.5% eth0 · 0.0 err/h UPS-MDF 10.10.30.8 ups 18 ms — — — LanInterface · 0.0 err/h WMS01 10.10.30.4 file 40 ms 28.7% 50.3% 90.7% vmxnet3 Ethernet Adapter · 0.0 err/h
VLAN 40 · printers10.10.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-DEN-01 10.10.40.20 printer 32 ms — 30.8% — eth0 · 0.0 err/h
VLAN 50 · cameras10.10.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-DOCK-01 10.10.50.20 sensor 36 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.10.90.0/24 5 devicesDevice IP Type Ping CPU Mem Disk Worst link DOCK-DEN-01 10.10.90.30 printer 31 ms — 55.7% — eth0 · 0.0 err/h DOCK-DEN-02 10.10.90.31 printer 44 ms — 32.0% — eth0 · 0.0 err/h DOOR-DOCK1 10.10.90.2 door 38 ms — — — eth0 · 0.0 err/h DOOR-DOCK2 10.10.90.3 door 39 ms — — — eth0 · 0.0 err/h ENV-FREEZER 10.10.90.4 sensor 32 ms — — — eth0 · 0.0 err/h
Detroit OT 0 red1 yellow34 green Internet0 linksLink IP Checked by Latency Loss No internet link found in the collection
FortiGate FG-DETROITOTCPU 17% Mem 49% Sessions 1,475 up 201 days Interface IP Ping CPU Mem Worst link Detroit OT FortiGate 10.250.0.5 24 ms — — iot · 0.0 err/h detroit-ot FortiGate (users) 10.5.10.1 42 ms — — —
Switches4 Switch Model Firmware State FG-DETROITOT-SW1 FortiSwitch 124F-FPOE 7.4.5 up 152 days FG-DETROITOT-SW2 FortiSwitch 124F-FPOE 7.4.5 up 47 days FG-DETROITOT-SW3 FortiSwitch 124F-FPOE 7.4.5 up 294 days FG-DETROITOT-SW4 FortiSwitch 124F-FPOE 7.4.5 up 277 days
Access points2 Access point Model State FG-DETROITOT-AP1 FP231F connected · up 116 days FG-DETROITOT-AP2 FP231F connected · up 39 days
VLANs6 VLAN 10 · users10.5.10.0/24 2 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.5.10.80 10.5.10.80 printer 38 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.5.10.81 10.5.10.81 printer 45 ms — — — Ethernet · 0.0 err/h
VLAN 30 · servers10.5.30.0/24 2 devicesDevice IP Type Ping CPU Mem Disk Worst link HIST01 10.5.30.2 file 17 ms 26.9% 52.2% 59.6% vmxnet3 Ethernet Adapter · 48.0 err/h IPERF01 10.5.30.3 file 24 ms 4.0% 21.6% 14.3% lo · 0.0 err/h
VLAN 90 · iot10.5.90.0/24 24 devicesDevice IP Type Ping CPU Mem Disk Worst link CAM-LINE-01 10.5.90.24 sensor 27 ms — — — eth0 · 0.0 err/h ENV-PANEL 10.5.90.8 sensor 17 ms — — — eth0 · 0.0 err/h HMI-DET-01 10.5.90.16 ot 35 ms — — — X2 · 0.0 err/h HMI-DET-02 10.5.90.17 ot 20 ms — — — X1 · 0.0 err/h HMI-DET-03 10.5.90.18 ot 19 ms — — — X1 · 0.0 err/h HMI-DET-04 10.5.90.19 ot 44 ms — — — X1 · 0.0 err/h HMI01 10.5.90.2 ot 29 ms — — — X1 · 0.0 err/h HMI02 10.5.90.3 ot 38 ms — — — X1 · 0.0 err/h IoT / industrial 10.5.90.25 10.5.90.25 ot 25 ms — — — eth0 · 0.0 err/h PLC-DET-01 10.5.90.10 ot 45 ms — — — eth0 · 0.0 err/h PLC-DET-02 10.5.90.11 ot 20 ms — — — eth0 · 0.0 err/h PLC-DET-03 10.5.90.12 ot 37 ms — — — eth0 · 0.0 err/h PLC-DET-04 10.5.90.13 ot 42 ms — — — eth0 · 0.0 err/h PLC-DET-05 10.5.90.14 ot 18 ms — — — eth0 · 0.0 err/h PLC-DET-06 10.5.90.15 ot 38 ms — — — eth0 · 0.0 err/h PLC-LINE1 10.5.90.4 plc 34 ms — — — X1 P1 · 0.0 err/h PLC-LINE2 10.5.90.5 plc 20 ms — — — X1 P1 · 0.0 err/h PLC-PACK 10.5.90.6 plc 20 ms — — — X1 P2 · 0.0 err/h UPS-PANEL 10.5.90.9 ups 30 ms — — — LanInterface · 0.0 err/h VFD-CONV1 10.5.90.7 ot 37 ms — — — X1 · 0.0 err/h VFD-DET-01 10.5.90.20 ot 27 ms — — — X1 · 0.0 err/h VFD-DET-02 10.5.90.21 ot 16 ms — — — X1 · 0.0 err/h VFD-DET-03 10.5.90.22 ot 36 ms — — — X1 · 0.0 err/h VFD-DET-04 10.5.90.23 ot 40 ms — — — X1 · 0.0 err/h
+ 3 VLANs with no monitored devices: 20 voice, 40 printers, 50 cameras
Miami 0 red0 yellow14 green Internetbusiest wan1 23% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.4 ping 13 ms 0% Metro Cable gateway 198.51.100.4 ping 10 ms 0%
FortiGate FG-MIAMICPU 18% Mem 50% Sessions 792 up 86 days Interface IP Ping CPU Mem Worst link Miami FortiGate 10.250.0.14 39 ms — — fortilink · 0.0 err/h miami FortiGate (users) 10.14.10.1 43 ms — — —
Switches1 Switch Model Firmware State FG-MIAMI-SW1 FortiSwitch 124F-FPOE 7.4.5 up 212 days
Access points2 Access point Model State FG-MIAMI-AP1 FP231F connected · up 70 days FG-MIAMI-AP2 FP231F connected · up 88 days
VLANs6 VLAN 30 · servers10.14.30.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.14.30.2 file 20 ms 30.2% 45.7% 46.8% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.14.30.3 file 35 ms 5.4% 19.6% 21.0% ens192 · 0.0 err/h UPS-MDF 10.14.30.4 ups 32 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.14.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-MIA-01 10.14.40.20 printer 28 ms — 59.8% — eth0 · 0.0 err/h
VLAN 50 · cameras10.14.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.14.50.20 sensor 39 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.14.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.14.90.2 door 24 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Seattle 0 red1 yellow44 green Internetbusiest wan1 31% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 15 ms 0% Metro Cable gateway 198.51.100.17 ping 12 ms 0%
FortiGate FG-SEATTLECPU 19% Mem 49% Sessions 6,050 up 171 days Interface IP Ping CPU Mem Worst link Seattle FortiGate 10.250.0.11 24 ms — — wan2 · 0.0 err/h seattle FortiGate (users) 10.11.10.1 19 ms — — —
Switches3 Switch Model Firmware State FG-SEATTLE-SW1 FortiSwitch 124F-FPOE 7.4.5 up 144 days FG-SEATTLE-SW2 FortiSwitch 124F-FPOE 7.4.5 up 38 days FG-SEATTLE-SW3 FortiSwitch 124F-FPOE 7.4.5 up 61 days
Access points10 Access point Model State FG-SEATTLE-AP1 FP231F connected · up 33 days FG-SEATTLE-AP2 FP231F connected · up 108 days FG-SEATTLE-AP3 FP231F connected · up 172 days FG-SEATTLE-AP4 FP231F connected · up 55 days FG-SEATTLE-AP5 FP231F connected · up 75 days FG-SEATTLE-AP6 FP231F connected · up 46 days FG-SEATTLE-AP7 FP231F connected · up 161 days FG-SEATTLE-AP8 FP231F connected · up 41 days FG-SEATTLE-AP9 FP231F connected · up 39 days FG-SEATTLE-AP10 FP231F connected · up 129 days
VLANs6 VLAN 10 · users10.11.10.0/24 12 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.11.10.80 10.11.10.80 printer 26 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.81 10.11.10.81 printer 40 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.82 10.11.10.82 printer 25 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.83 10.11.10.83 printer 17 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.84 10.11.10.84 printer 44 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.85 10.11.10.85 printer 29 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.86 10.11.10.86 printer 18 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.87 10.11.10.87 printer 40 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.88 10.11.10.88 printer 36 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.89 10.11.10.89 printer 16 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.90 10.11.10.90 printer 17 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.11.10.91 10.11.10.91 printer 26 ms — — — Ethernet · 0.0 err/h
VLAN 20 · voice10.11.20.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PAGE-WHSE 10.11.20.2 other 42 ms — — — eth0 · 0.0 err/h
VLAN 30 · servers10.11.30.0/24 7 devicesDevice IP Type Ping CPU Mem Disk Worst link BACKUP01 10.11.30.5 backup 25 ms 10.7% 57.1% 30.9% vmxnet3 Ethernet Adapter · 0.0 err/h DC01 10.11.30.2 dc 35 ms 5.2% 73.6% 52.9% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.11.30.3 file 26 ms 19.1% 71.6% 47.9% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.11.30.6 file 16 ms 5.0% 20.8% 18.3% lo · 0.0 err/h NAS01 10.11.30.7 storage 29 ms 7.4% 50.3% 92.7% eth1 · 0.0 err/h UPS-MDF 10.11.30.8 ups 44 ms — — — LanInterface · 0.0 err/h WMS01 10.11.30.4 file 36 ms 34.9% 47.2% 36.5% vmxnet3 Ethernet Adapter · 0.0 err/h
VLAN 40 · printers10.11.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-SEA-01 10.11.40.20 printer 34 ms — 27.4% — eth0 · 0.0 err/h
VLAN 50 · cameras10.11.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-DOCK-01 10.11.50.20 sensor 29 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.11.90.0/24 5 devicesDevice IP Type Ping CPU Mem Disk Worst link DOCK-SEA-01 10.11.90.30 printer 22 ms — 26.5% — eth0 · 0.0 err/h DOCK-SEA-02 10.11.90.31 printer 37 ms — 23.4% — eth0 · 0.0 err/h DOOR-DOCK1 10.11.90.2 door 41 ms — — — eth0 · 0.0 err/h DOOR-DOCK2 10.11.90.3 door 31 ms — — — eth0 · 0.0 err/h ENV-FREEZER 10.11.90.4 sensor 41 ms — — — eth0 · 0.0 err/h
Azure West 0 red0 yellow10 green Internetbusiest wan1 24% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Path A gateway 203.0.113.3 ping 12 ms 0% Path B gateway 198.51.100.3 ping 11 ms 0%
FortiGate FG-AZUREWESTCPU 18% Mem 50% Sessions 17,700 up 135 days Interface IP Ping CPU Mem Worst link Azure West FortiGate 10.250.0.20 21 ms — — wan1 · 0.0 err/h
VLANs0 Other networks5 devicesDevice IP Type Ping CPU Mem Disk Worst link AZ-APP01 10.1.30.3 file 36 ms 35.2% 72.3% 38.5% Microsoft Hyper-V Network Adapter · 0.0 err/h AZ-APP02 10.1.30.4 file 28 ms 25.0% 55.3% 69.2% Microsoft Hyper-V Network Adapter · 0.0 err/h AZ-DC01 10.1.30.2 dc 27 ms 8.7% 61.3% 52.0% Microsoft Hyper-V Network Adapter · 0.0 err/h AZ-IPERF01 10.1.30.6 file 38 ms 0.9% 23.2% 21.0% lo · 0.0 err/h AZ-SQL01 10.1.30.5 file 21 ms 13.0% 46.1% 61.7% Microsoft Hyper-V Network Adapter · 0.0 err/h
Charlotte OT 0 red0 yellow35 green Internet0 linksLink IP Checked by Latency Loss No internet link found in the collection
FortiGate FG-CHARLOTTEOCPU 17% Mem 49% Sessions 1,636 up 213 days Interface IP Ping CPU Mem Worst link Charlotte OT FortiGate 10.250.0.7 18 ms — — servers · 0.0 err/h charlotte-ot FortiGate (users) 10.7.10.1 19 ms — — —
Switches4 Switch Model Firmware State FG-CHARLOTTEO-SW1 FortiSwitch 124F-FPOE 7.4.5 up 48 days FG-CHARLOTTEO-SW2 FortiSwitch 124F-FPOE 7.4.5 up 263 days FG-CHARLOTTEO-SW3 FortiSwitch 124F-FPOE 7.4.5 up 144 days FG-CHARLOTTEO-SW4 FortiSwitch 124F-FPOE 7.4.5 up 271 days
Access points2 Access point Model State FG-CHARLOTTEO-AP1 FP231F connected · up 35 days FG-CHARLOTTEO-AP2 FP231F connected · up 51 days
VLANs6 VLAN 10 · users10.7.10.0/24 2 devicesDevice IP Type Ping CPU Mem Disk Worst link Label printer / scanner 10.7.10.80 10.7.10.80 printer 39 ms — — — Ethernet · 0.0 err/h Label printer / scanner 10.7.10.81 10.7.10.81 printer 27 ms — — — Ethernet · 0.0 err/h
VLAN 30 · servers10.7.30.0/24 2 devicesDevice IP Type Ping CPU Mem Disk Worst link HIST01 10.7.30.2 file 45 ms 30.2% 54.1% 62.9% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.7.30.3 file 16 ms 9.9% 22.8% 24.7% ens192 · 0.0 err/h
VLAN 90 · iot10.7.90.0/24 24 devicesDevice IP Type Ping CPU Mem Disk Worst link CAM-LINE-01 10.7.90.24 sensor 32 ms — — — eth0 · 0.0 err/h ENV-PANEL 10.7.90.8 sensor 19 ms — — — eth0 · 0.0 err/h HMI-CLT-01 10.7.90.16 ot 24 ms — — — X1 · 0.0 err/h HMI-CLT-02 10.7.90.17 ot 41 ms — — — X1 · 0.0 err/h HMI-CLT-03 10.7.90.18 ot 29 ms — — — X1 · 0.0 err/h HMI-CLT-04 10.7.90.19 ot 38 ms — — — X2 · 0.0 err/h HMI01 10.7.90.2 ot 38 ms — — — X1 · 0.0 err/h HMI02 10.7.90.3 ot 29 ms — — — X1 · 0.0 err/h IoT / industrial 10.7.90.25 10.7.90.25 ot 43 ms — — — eth0 · 0.0 err/h PLC-CLT-01 10.7.90.10 ot 44 ms — — — eth0 · 0.0 err/h PLC-CLT-02 10.7.90.11 ot 21 ms — — — eth0 · 0.0 err/h PLC-CLT-03 10.7.90.12 ot 36 ms — — — eth0 · 0.0 err/h PLC-CLT-04 10.7.90.13 ot 19 ms — — — eth0 · 0.0 err/h PLC-CLT-05 10.7.90.14 ot 29 ms — — — eth0 · 0.0 err/h PLC-CLT-06 10.7.90.15 ot 41 ms — — — eth0 · 0.0 err/h PLC-LINE1 10.7.90.4 plc 40 ms — — — X1 P1 · 0.0 err/h PLC-LINE2 10.7.90.5 plc 18 ms — — — X1 P2 · 0.0 err/h PLC-PACK 10.7.90.6 plc 27 ms — — — X1 P1 · 0.0 err/h UPS-PANEL 10.7.90.9 ups 27 ms — — — LanInterface · 0.0 err/h VFD-CLT-01 10.7.90.20 ot 16 ms — — — X1 · 0.0 err/h VFD-CLT-02 10.7.90.21 ot 27 ms — — — X1 · 0.0 err/h VFD-CLT-03 10.7.90.22 ot 33 ms — — — X1 · 0.0 err/h VFD-CLT-04 10.7.90.23 ot 30 ms — — — X1 · 0.0 err/h VFD-CONV1 10.7.90.7 ot 18 ms — — — X1 · 0.0 err/h
+ 3 VLANs with no monitored devices: 20 voice, 40 printers, 50 cameras
Detroit 0 red0 yellow22 green Internetbusiest wan1 41% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.9 ping 17 ms 0% Metro Cable gateway 198.51.100.9 ping 12 ms 0%
FortiGate FG-DETROITCPU 19% Mem 50% Sessions 4,422 up 97 days Interface IP Ping CPU Mem Worst link Detroit FortiGate 10.250.0.4 22 ms — — iot · 0.0 err/h detroit FortiGate (users) 10.4.10.1 44 ms — — —
Switches2 Switch Model Firmware State FG-DETROIT-SW1 FortiSwitch 124F-FPOE 7.4.5 up 219 days FG-DETROIT-SW2 FortiSwitch 124F-FPOE 7.4.5 up 267 days
Access points4 Access point Model State FG-DETROIT-AP1 FP231F connected · up 159 days FG-DETROIT-AP2 FP231F connected · up 13 days FG-DETROIT-AP3 FP231F connected · up 180 days FG-DETROIT-AP4 FP231F connected · up 14 days
VLANs6 VLAN 30 · servers10.4.30.0/24 6 devicesDevice IP Type Ping CPU Mem Disk Worst link DC01 10.4.30.2 dc 32 ms 5.0% 57.1% 33.7% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.4.30.3 file 34 ms 21.6% 57.3% 36.7% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.4.30.5 file 26 ms 5.6% 19.5% 23.8% ens192 · 0.0 err/h MES01 10.4.30.4 file 25 ms 32.1% 50.6% 50.1% vmxnet3 Ethernet Adapter · 0.0 err/h NAS01 10.4.30.6 storage 25 ms 12.2% 55.7% 54.1% eth0 · 0.0 err/h UPS-MDF 10.4.30.7 ups 38 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.4.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-DET-01 10.4.40.20 printer 42 ms — 34.9% — eth0 · 0.0 err/h
VLAN 50 · cameras10.4.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-DOCK-01 10.4.50.20 sensor 17 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.4.90.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link DOOR-DOCK 10.4.90.2 door 44 ms — — — eth0 · 0.0 err/h DOOR-MDF 10.4.90.3 door 18 ms — — — eth0 · 0.0 err/h ENV-MDF 10.4.90.4 sensor 15 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Houston 0 red0 yellow22 green Internetbusiest wan1 31% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.9 ping 12 ms 0% Metro Cable gateway 198.51.100.9 ping 13 ms 0%
FortiGate FG-HOUSTONCPU 16% Mem 50% Sessions 4,071 up 211 days Interface IP Ping CPU Mem Worst link Houston FortiGate 10.250.0.2 45 ms — — servers · 0.0 err/h houston FortiGate (users) 10.2.10.1 42 ms — — —
Switches2 Switch Model Firmware State FG-HOUB-SW1 FortiSwitch 124F-FPOE 7.4.5 up 294 days FG-HOUB-SW2 FortiSwitch 124F-FPOE 7.4.5 up 34 days
Access points4 Access point Model State FG-HOUB-AP1 FP231F connected · up 21 days FG-HOUB-AP2 FP231F connected · up 60 days FG-HOUB-AP3 FP231F connected · up 113 days FG-HOUB-AP4 FP231F connected · up 164 days
VLANs6 VLAN 30 · servers10.2.30.0/24 6 devicesDevice IP Type Ping CPU Mem Disk Worst link DC01 10.2.30.2 dc 16 ms 9.3% 49.6% 38.3% vmxnet3 Ethernet Adapter · 0.0 err/h FILE01 10.2.30.3 file 31 ms 8.2% 64.0% 34.4% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.2.30.5 file 40 ms 4.6% 19.8% 18.9% lo · 0.0 err/h MES01 10.2.30.4 file 24 ms 11.6% 46.9% 36.4% vmxnet3 Ethernet Adapter · 0.0 err/h NAS01 10.2.30.6 storage 31 ms 7.2% 56.6% 71.3% eth0 · 0.0 err/h UPS-MDF 10.2.30.7 ups 34 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.2.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-HOU-01 10.2.40.20 printer 32 ms — 45.7% — eth0 · 0.0 err/h
VLAN 50 · cameras10.2.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-DOCK-01 10.2.50.20 sensor 42 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.2.90.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link DOOR-DOCK 10.2.90.2 door 36 ms — — — eth0 · 0.0 err/h DOOR-MDF 10.2.90.3 door 38 ms — — — eth0 · 0.0 err/h ENV-MDF 10.2.90.4 sensor 40 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Los Angeles 0 red0 yellow14 green Internetbusiest wan1 29% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 7 ms 0% Metro Cable gateway 198.51.100.17 ping 9 ms 0%
FortiGate FG-LOSANGELESCPU 18% Mem 50% Sessions 751 up 140 days Interface IP Ping CPU Mem Worst link Los Angeles FortiGate 10.250.0.13 36 ms — — wan1 · 0.0 err/h losangeles FortiGate (users) 10.13.10.1 27 ms — — —
Switches1 Switch Model Firmware State FG-LOSANGELES-SW1 FortiSwitch 124F-FPOE 7.4.5 up 177 days
Access points2 Access point Model State FG-LOSANGELES-AP1 FP231F connected · up 39 days FG-LOSANGELES-AP2 FP231F connected · up 17 days
VLANs6 VLAN 30 · servers10.13.30.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.13.30.2 file 33 ms 15.2% 67.6% 65.6% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.13.30.3 file 33 ms 3.5% 22.1% 23.1% lo · 0.0 err/h UPS-MDF 10.13.30.4 ups 42 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.13.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-LAX-01 10.13.40.20 printer 37 ms — 47.2% — eth0 · 0.0 err/h
VLAN 50 · cameras10.13.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.13.50.20 sensor 19 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.13.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.13.90.2 door 27 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Minneapolis 0 red0 yellow13 green Internetbusiest wan1 38% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.6 ping 13 ms 0% Metro Cable gateway 198.51.100.6 ping 14 ms 0%
FortiGate FG-MINNEAPOLICPU 16% Mem 50% Sessions 742 up 195 days Interface IP Ping CPU Mem Worst link Minneapolis FortiGate 10.250.0.16 25 ms — — wan2 · 0.0 err/h minneapolis FortiGate (users) 10.16.10.1 17 ms — — —
Switches1 Switch Model Firmware State FG-MINNEAPOLI-SW1 FortiSwitch 124F-FPOE 7.4.5 up 291 days
Access points1 Access point Model State FG-MINNEAPOLI-AP1 FP231F connected · up 10 days
VLANs6 VLAN 30 · servers10.16.30.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.16.30.2 file 22 ms 26.3% 44.9% 60.1% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.16.30.3 file 38 ms 5.8% 14.0% 28.2% lo · 0.0 err/h UPS-MDF 10.16.30.4 ups 35 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.16.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-MSP-01 10.16.40.20 printer 24 ms — 46.5% — eth0 · 0.0 err/h
VLAN 50 · cameras10.16.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.16.50.20 sensor 36 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.16.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.16.90.2 door 41 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
New York 0 red0 yellow14 green Internetbusiest wan1 41% 4 linksLink IP Checked by Latency Loss wan1 — SD-WAN 8 ms 0% wan2 — SD-WAN 9 ms 0% Example Fiber gateway 203.0.113.17 ping 9 ms 0% Metro Cable gateway 198.51.100.17 ping 12 ms 0%
FortiGate FG-NEWYORKCPU 16% Mem 49% Sessions 704 up 201 days Interface IP Ping CPU Mem Worst link New York FortiGate 10.250.0.12 33 ms — — wan2 · 0.0 err/h newyork FortiGate (users) 10.12.10.1 23 ms — — —
Switches1 Switch Model Firmware State FG-NEWYORK-SW1 FortiSwitch 124F-FPOE 7.4.5 up 134 days
Access points2 Access point Model State FG-NEWYORK-AP1 FP231F connected · up 102 days FG-NEWYORK-AP2 FP231F connected · up 89 days
VLANs6 VLAN 30 · servers10.12.30.0/24 3 devicesDevice IP Type Ping CPU Mem Disk Worst link FILE01 10.12.30.2 file 15 ms 31.3% 64.1% 32.8% vmxnet3 Ethernet Adapter · 0.0 err/h IPERF01 10.12.30.3 file 44 ms 6.1% 12.7% 16.8% ens192 · 0.0 err/h UPS-MDF 10.12.30.4 ups 20 ms — — — LanInterface · 0.0 err/h
VLAN 40 · printers10.12.40.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link PRN-NYC-01 10.12.40.20 printer 16 ms — 49.8% — eth0 · 0.0 err/h
VLAN 50 · cameras10.12.50.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link CAM-LOBBY-01 10.12.50.20 sensor 27 ms — — — eth0 · 0.0 err/h
VLAN 90 · iot10.12.90.0/24 1 deviceDevice IP Type Ping CPU Mem Disk Worst link DOOR-FRONT 10.12.90.2 door 19 ms — — — eth0 · 0.0 err/h
+ 2 VLANs with no monitored devices: 10 users, 20 voice
Vantage demo · last merged Sun Nov 22 2026 04:17 PM CT