Needs attention 15
- Users affected13
- ✕unreachable
- Collection failing since Nov 22, 11:16 AM (4 attempts): timed out – showing data from Nov 20, 2:16 PM
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
collectortimed out · TCP 22: no answer on port 22How to fix
No other site has a tunnel up to Philadelphia (2 configured) – the site may really be down.The collector couldn't log in to this FortiGate this time (timed out), so the page shows the last good data. It has failed 4 times in a row since Nov 22, 11:16 AM.
- Check the site is up some other way.
- From NET-DEMO01: test the path (below).
- Read the FortiGate's event log for the login.
# on NET-DEMO01 (PowerShell): Test-NetConnection 10.250.0.18 -Port 22 # on the FortiGate (your admin account) – why it refused the login: execute log filter category event execute log filter field user netmap execute log display # --- on Philadelphia's FortiGate. Safe to share – no keys: get router info routing-table details 10.250.0.5 diagnose sniffer packet any 'host 10.250.0.5 and port 22' 4 20 # nothing arrives -> the request never left the far end on a tunnel that reaches this site # arrives, no reply leaves -> this FortiGate ignores it: policy, or the source is no longer the trusted host # reply leaves elsewhere -> the return route is wrong here # 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. # diagnose vpn tunnel list · diagnose vpn ike gateway list · show vpn ipsec phase1-interface - ▲FG-PHILADELPH-SW1 unreachable
- Collector ping to FG-PHILADELPH-SW1 (10.255.18.10) failed: no reply
How to fix
The collector cannot ping FG-PHILADELPH-SW1 (10.255.18.10). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲Philadelphia FortiGate unreachable
- Collector ping to Philadelphia FortiGate (10.250.0.18) failed: no reply
How to fix
The collector cannot ping Philadelphia FortiGate (10.250.0.18). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia FortiGate (users) unreachable
- Collector ping to philadelphia FortiGate (users) (10.18.10.1) failed: no reply
How to fix
The collector cannot ping philadelphia FortiGate (users) (10.18.10.1). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia servers gateway unreachable
- Collector ping to philadelphia servers gateway (10.18.30.1) failed: no reply
How to fix
The collector cannot ping philadelphia servers gateway (10.18.30.1). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia printers gateway unreachable
- Collector ping to philadelphia printers gateway (10.18.40.1) failed: no reply
How to fix
The collector cannot ping philadelphia printers gateway (10.18.40.1). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia cameras gateway unreachable
- Collector ping to philadelphia cameras gateway (10.18.50.1) failed: no reply
How to fix
The collector cannot ping philadelphia cameras gateway (10.18.50.1). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia iot gateway unreachable
- Collector ping to philadelphia iot gateway (10.18.90.1) failed: no reply
How to fix
The collector cannot ping philadelphia iot gateway (10.18.90.1). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia FortiLink unreachable
- Collector ping to philadelphia FortiLink (10.255.18.1) failed: no reply
How to fix
The collector cannot ping philadelphia FortiLink (10.255.18.1). A critical internal address is unreachable from the Vantage server.
- 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-PHILADELPH-AP1 unreachable
- Collector ping to FG-PHILADELPH-AP1 (10.18.10.20) failed: no reply
How to fix
The collector cannot ping FG-PHILADELPH-AP1 (10.18.10.20). A critical internal address is unreachable from the Vantage server.
- 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-PHILADELPH-AP2 unreachable
- Collector ping to FG-PHILADELPH-AP2 (10.18.10.21) failed: no reply
How to fix
The collector cannot ping FG-PHILADELPH-AP2 (10.18.10.21). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia DNS 10.1.30.2 unreachable
- Collector ping to philadelphia DNS 10.1.30.2 (10.1.30.2) failed: no reply
How to fix
The collector cannot ping philadelphia DNS 10.1.30.2 (10.1.30.2). A critical internal address is unreachable from the Vantage server.
- 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.
- ▲philadelphia DNS 10.1.30.3 unreachable
- Collector ping to philadelphia DNS 10.1.30.3 (10.1.30.3) failed: no reply
How to fix
The collector cannot ping philadelphia DNS 10.1.30.3 (10.1.30.3). A critical internal address is unreachable from the Vantage server.
- 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.
- Redundancy reduced1
- ▲Example Fiber gateway unreachable
- Collector ping to Example Fiber gateway (203.0.113.1) failed: no reply
How to fix
The collector cannot ping Example Fiber gateway (203.0.113.1). An ISP gateway or external service is unreachable from the Vantage server.
- 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.
- Monitoring & housekeeping1
- ✕data 50 h old
- Data is 50 hours old – last successful collection Nov 20, 2:16 PM
How to fix
No successful collection for over a day – everything on this page may be out of date.
- Check the scheduled task ran (Task Scheduler → History of the hourly task).
- Read the latest log in C:\netmap\logs – a failed site's line ends with a diagnosis.
- Run the hourly task now and read the log again (manual runs go through the task – only its account can read the key).
# on NET-DEMO01 (elevated PowerShell): Start-ScheduledTask "Vantage hourly" Get-Content (Get-ChildItem C:\netmap\logs\daily-*.log | Sort-Object LastWriteTime | Select-Object -Last 1) -Encoding UTF8 -Tail 30
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 | |
|---|---|---|---|---|---|---|---|---|---|---|
| Philadelphia | FortiGate-40F | 7.4.8 | — | — | — | — | — | — | Not working |
Switches11 · 0 need a look · PoE 46 of 370 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-PHILADELPH-SW1 | FortiSwitch 124F-FPOE | 14 / 28 | 46 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-PHILADELPH-AP1 | FP231F | — | — | — | — | FG-PHILADELPH-SW1 port3 | 7.4.3 | Working normally | |
| FG-PHILADELPH-AP2 | FP231F | — | — | — | — | FG-PHILADELPH-SW1 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.18.10.0/24 | 10.18.10.1 | 255.255.255.0 /24 | 10.18.10.20 – 10.18.10.250 231 addresses · 5 in use · lease 8 hours | |
| 20 | voice | 10.18.20.0/24 | 10.18.20.1 | 255.255.255.0 /24 | 10.18.20.20 – 10.18.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.18.30.0/24 | 10.18.30.1 | 255.255.255.0 /24 | 10.18.30.20 – 10.18.30.250 231 addresses · 0 in use · lease 7 days · 3 reserved | |
| 40 | printers | 10.18.40.0/24 | 10.18.40.1 | 255.255.255.0 /24 | 10.18.40.100 – 10.18.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.18.50.0/24 | 10.18.50.1 | 255.255.255.0 /24 | 10.18.50.100 – 10.18.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.18.90.0/24 | 10.18.90.1 | 255.255.255.0 /24 | 10.18.90.100 – 10.18.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.18.0/24 | 10.255.18.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 | |
|---|---|---|---|---|---|---|
| Philadelphia | Closet 1 FG-PHILADELPH-SW1 | 14 / 28 (50%) | 10 | 10 | 46 / 370 W (12%) 324 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-PHILADELPH-SW1 FortiSwitch 124F-FPOE · Closet 114 in use · 14 free · PoE 46 / 370 W · 40 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-PHILADELPH-AP1 FortiAP | 10 users | 10.18.10.20 · 00:11:22:12:00:00 | 13.7 W class 4 | |
| port4 | Up | FG-PHILADELPH-AP2 FortiAP | 10 users | 10.18.10.21 · 00:11:22:12:00:01 | 14.2 W class 4 | |
| port7 | Up | FILE01 | 30 servers | 10.18.30.2 · f8:bc:12:af:32:ba | ||
| port8 | Up | IPERF01 | 30 servers | 10.18.30.3 · f8:bc:12:7c:54:e4 | ||
| port9 | Up | UPS-MDF | 30 servers | 10.18.30.4 · 00:c0:b7:7d:1f:c4 | ||
| port10 | Up | DOOR-FRONT | 90 iot | 10.18.90.2 · 00:06:8e:ea:c4:62 | 4.2 W class 2 | |
| port13 | Up | NL-PHL-PC011 | 10 users | 10.18.10.120 · d0:43:1e:12:0a:01 | ||
| port14 | Up | NL-PHL-LT012 | 10 users | 10.18.10.121 · d0:43:1e:12:0a:02 | ||
| port15 | Up | NL-PHL-PC013 | 10 users | 10.18.10.122 · d0:43:1e:12:0a:03 | ||
| port16 | Up | NL-PHL-PH01 phone | 20 voice | 10.18.20.20 · 00:04:f2:12:14:01 | 3.6 W class 2 | |
| port17 | Up | NL-PHL-PH02 phone | 20 voice | 10.18.20.21 · 00:04:f2:12:14:02 | 3.2 W class 2 | |
| port18 | Up | PRN-PHL-01 | 40 printers | 10.18.40.20 · 3c:2a:f4:12:28:01 | ||
| port19 | Up | CAM-LOBBY-01 | 50 cameras | 10.18.50.20 · 00:40:8c:12:32:01 | 7.1 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00180001 |
Free ports: port1–2, port5–6, port11–12, port20–23, port25–28
S124FF18010001 · FortiSwitchOS 7.4.5
On-site contacts
- Avery Chen · (218) 555-1018 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 3/3/2025 to 3/3/2028 · 467 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.28 /29
- Gateway
- 203.0.113.1
- Circuit ID
- NL-181
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 5/3/2025 to 5/3/2028 · 528 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.28 /29
- Circuit ID
- NL-182
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary3 static routes · OSPF configured
From show router static, show router bgp, show router policy and show router ospf at the last collection. Counts only — see Consistency to compare across sites.
| Network | Type | Next hop |
|---|---|---|
| 0.0.0.0/0 | Static | wan1 internet |
| 10.0.0.0/8 | Static | blackhole (dropped) |
| 10.1.0.0/16 | OSPF | to-chicago → Chicago |
| 10.2.0.0/16 | OSPF | to-chicago → Chicago |
| 10.3.0.0/16 | OSPF | to-chicago → Chicago |
| 10.4.0.0/16 | OSPF | to-chicago → Chicago |
| 10.5.0.0/16 | OSPF | to-chicago → Chicago |
| 10.6.0.0/16 | OSPF | to-chicago → Chicago |
| 10.7.0.0/16 | OSPF | to-chicago → Chicago |
| 10.8.0.0/16 | OSPF | to-chicago → Chicago |
| 10.9.0.0/16 | OSPF | to-chicago → Chicago |
| 10.10.0.0/16 | OSPF | to-chicago → Chicago |
| 10.11.0.0/16 | OSPF | to-chicago → Chicago |
| 10.12.0.0/16 | OSPF | to-chicago → Chicago |
| 10.13.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.18.10.0/24 | Connected | users local network |
| 10.18.20.0/24 | Connected | voice local network |
| 10.18.30.0/24 | Connected | servers local network |
| 10.18.40.0/24 | Connected | printers local network |
| 10.18.50.0/24 | Connected | cameras local network |
| 10.18.90.0/24 | Connected | iot local network |
| 10.255.18.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 % |
|---|
Tunnel stability – last 7 days
2 tunnels · 2 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 4
| When | Type | What | Detail |
|---|---|---|---|
| Nov 18 9:09 AM | Config | DHCP server 1 | dns-server1: 10.1.30.11 → 10.1.30.12 |
| Nov 7 9:53 AM | Config | Static route 34 | added: dst 10.200.0.0 255.255.0.0, device to-chicago |
| Nov 1 3:08 PM | Config | Admin netops-17 | trusthost1: 0.0.0.0 0.0.0.0 → 10.1.30.0 255.255.255.0 |
| Oct 26 1:16 PM | Routing | Route 10.12.60.0/24 | added via to-chicago (OSPF) |
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 9 11:12 AM | Device movedWired | Device moved d0:43:1e:12:0a:03 | 10.18.10.122 FG-PHILADELPH-SW1 port19 → FG-PHILADELPH-SW1 port15 |
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
- Monitoring & housekeeping1
- ●health check
- SD-WAN health check 'Internet' can't reach its target on any WAN – check its server setting
How to fix
The SD-WAN health check 'Internet' probes 198.51.100.53 203.0.113.53 over the internet links, and that address doesn't answer on any of them. A private (10.x) address can only be reached over a tunnel, so this check can never pass. Any SD-WAN rule using it is effectively switched off.
- If nothing depends on it: delete the SD-WAN rule that uses it, then the health check.
- If it's meant to watch a server across the VPN: make the IPsec tunnels its members instead of the WANs.
show system sdwan config system sdwan config health-check delete "Internet" end end
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 Philadelphia 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-PHILADELPH FortiGate · FortiGate 40F | FGDEMO00180001 tag NL-0018 | Philadelphia Northline | 2023-07-19 3.3 years old PO PO-55519 · Example Reseller | Standard 2029-10-03 contract NL-SUP-18 warranty 2024-07-19 passed | 2032-09-30 end of order 2027-09-30 | 2029 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-PHILADELPH-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF18010001 tag NL-18S01 | Philadelphia · Closet 1 · Rack 1 Network team | 2023-02-15 3.8 years old PO PO-56180 · 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-PHILADELPH-AP1 FortiAP · FAP231F | FP231F18010001 tag NL-18A01 | Philadelphia · Ceiling, zone 1 Network team | 2022-05-10 4.5 years old PO PO-57180 · 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-PHILADELPH-AP2 FortiAP · FAP231F | FP231F18020001 tag NL-18A02 | Philadelphia · Ceiling, zone 2 Network team | 2023-05-10 3.5 years old PO PO-57181 · 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-181 | 500/500 | no reply collector ping | 2025-03-03 | 2028-03-03 give notice within 377 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-182 | 300/30 | – | 2025-05-03 | 2028-05-03 give notice within 468 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.18.10.0/24 | 10.18.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Philadelphia network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.18.20.0/24 | 10.18.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Philadelphia network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.18.30.0/24 | 10.18.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Philadelphia network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.18.40.0/24 | 10.18.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Philadelphia network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.18.50.0/24 | 10.18.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Philadelphia network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.18.90.0/24 | 10.18.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Philadelphia 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.