Exposed to the internet
- Admin login reachable from the internet – wan1 answers https, ssh
- Risky service exposed – RDP, port forward rdp-jump (203.0.113.27 tcp 3389 → 10.17.30.40)
Needs attention 1
- Redundancy reduced1
- ▲Metro Cable down
- WAN Metro Cable (wan2) is down
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
diagnose sys sdwan health-checkHealth Check(Internet): Seq(2 wan2): state(dead), packet-loss(0.000%) latency(9.000), jitter(1.000), mos(4.300), bandwidth-up(400000), bandwidth-dw(400000), bandwidth-bi(800000) sla_map=0x0How to fix
The Metro Cable connection is down. Traffic has failed over to the other connection(s), so users are probably fine, but there is no backup right now.
- Check the ISP modem/ONT has power and normal lights (on-site contact – see Circuits & contacts).
- Check the FortiGate port is up and has an address.
- If the line is dead, call the ISP – circuit, account and support numbers are on the Circuits & contacts tab.
get system interface physical wan2 diagnose sys sdwan health-check
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-PHOENIX | FortiGate-40F | 7.4.8 | 19% | 48% | 811 | 74% · wan1 | — | Working, needs a look |
Switches11 · 0 need a look · PoE 43 of 370 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-PHOENIX-SW1 | FortiSwitch 124F-FPOE | 15 / 28 | 43 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-PHOENIX-AP1 | FP231F | — | — | — | — | FG-PHOENIX-SW1 port3 | 7.4.3 | Working normally | |
| FG-PHOENIX-AP2 | FP231F | — | — | — | — | FG-PHOENIX-SW1 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.17.10.0/24 | 10.17.10.1 | 255.255.255.0 /24 | 10.17.10.20 – 10.17.10.250 231 addresses · 5 in use · lease 8 hours | |
| 20 | voice | 10.17.20.0/24 | 10.17.20.1 | 255.255.255.0 /24 | 10.17.20.20 – 10.17.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.17.30.0/24 | 10.17.30.1 | 255.255.255.0 /24 | 10.17.30.20 – 10.17.30.250 231 addresses · 1 in use · lease 7 days · 3 reserved | |
| 40 | printers | 10.17.40.0/24 | 10.17.40.1 | 255.255.255.0 /24 | 10.17.40.100 – 10.17.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.17.50.0/24 | 10.17.50.1 | 255.255.255.0 /24 | 10.17.50.100 – 10.17.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.17.90.0/24 | 10.17.90.1 | 255.255.255.0 /24 | 10.17.90.100 – 10.17.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.17.0/24 | 10.255.17.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 4 | 3 Computer · 1 Network gear |
| 20 | voice | 2 | 2 Phone (VoIP) |
| 30 | servers | 4 | 3 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 · 15 ports in use · 13 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 closet15 of 28 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Phoenix | Closet 1 FG-PHOENIX-SW1 | 15 / 28 (54%) | 9 | 9 | 43 / 370 W (12%) 327 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-PHOENIX-SW1 FortiSwitch 124F-FPOE · Closet 115 in use · 13 free · PoE 43 / 370 W · 39 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-PHOENIX-AP1 FortiAP | 10 users | 10.17.10.20 · 00:11:22:11:00:00 | 11.3 W class 4 | |
| port4 | Up | FG-PHOENIX-AP2 FortiAP | 10 users | 10.17.10.21 · 00:11:22:11:00:01 | 12.9 W class 4 | |
| port7 | Up | FILE01 | 30 servers | 10.17.30.2 · f8:bc:12:15:24:92 | ||
| port8 | Up | IPERF01 | 30 servers | 10.17.30.3 · f8:bc:12:ca:5d:9f | ||
| port9 | Up | UPS-MDF | 30 servers | 10.17.30.4 · 00:c0:b7:71:7c:67 | ||
| port10 | Up | DOOR-FRONT | 90 iot | 10.17.90.2 · 00:06:8e:91:04:2d | 4.2 W class 2 | |
| port13 | Up | NL-PHX-PC011 | 10 users | 10.17.10.120 · d0:43:1e:11:0a:01 | ||
| port14 | Up | NL-PHX-LT012 | 10 users | 10.17.10.121 · d0:43:1e:11:0a:02 | ||
| port15 | Up | NL-PHX-PC013 | 10 users | 10.17.10.122 · d0:43:1e:11:0a:03 | ||
| port16 | Up | NL-PHX-PH01 phone | 20 voice | 10.17.20.20 · 00:04:f2:11:14:01 | 4.3 W class 2 | |
| port17 | Up | NL-PHX-PH02 phone | 20 voice | 10.17.20.21 · 00:04:f2:11:14:02 | 3.7 W class 2 | |
| port18 | Up | PRN-PHX-01 | 40 printers | 10.17.40.20 · 3c:2a:f4:11:28:01 | ||
| port19 | Up | CAM-LOBBY-01 | 50 cameras | 10.17.50.20 · 00:40:8c:11:32:01 | 6.7 W class 3 | |
| port21 | Up | NEW-PC | 30 servers | 10.17.30.40 · d0:43:1e:11:30:28 | ||
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00170001 |
Free ports: port1–2, port5–6, port11–12, port20, port22–23, port25–28
S124FF17010001 · FortiSwitchOS 7.4.5
On-site contacts
- Morgan Ellis · (217) 555-1017 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 10/18/2022 to 10/18/2027 · 330 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.27 /29
- Gateway
- 203.0.113.7
- Circuit ID
- NL-171
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 12/18/2024 to 12/18/2027 · 391 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.27 /29
- Circuit ID
- NL-172
- 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.10.0/24 | Connected | users local network |
| 10.17.20.0/24 | Connected | voice local network |
| 10.17.30.0/24 | Connected | servers local network |
| 10.17.40.0/24 | Connected | printers local network |
| 10.17.50.0/24 | Connected | cameras local network |
| 10.17.90.0/24 | Connected | iot local network |
| 10.255.17.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 | 8.2 | 1.3 | 0 |
| 2026-11-22 | Example Fiber | 8.8 | 1 | 0 |
| 2026-11-21 | Metro Cable | 9.3 | 1.8 | 0.2 |
| 2026-11-21 | Example Fiber | 8.4 | 1.3 | 0 |
| 2026-11-20 | Metro Cable | 8.8 | 1 | 0 |
| 2026-11-20 | Example Fiber | 8.7 | 1.3 | 0 |
| 2026-11-19 | Metro Cable | 9 | 1.3 | 0.2 |
| 2026-11-19 | Example Fiber | 8.5 | 1.5 | 0.2 |
| 2026-11-18 | Metro Cable | 9 | 1.4 | 0 |
| 2026-11-18 | Example Fiber | 7.9 | 2 | 0.2 |
| 2026-11-17 | Metro Cable | 9.2 | 1.7 | 0 |
| 2026-11-17 | Example Fiber | 8.8 | 1 | 0 |
| 2026-11-16 | Metro Cable | 8.1 | 1.8 | 0.2 |
| 2026-11-16 | Example Fiber | 8.7 | 1.4 | 0.2 |
| 2026-11-15 | Metro Cable | 8.9 | 1.4 | 0.2 |
| 2026-11-15 | Example Fiber | 8.9 | 1.7 | 0.2 |
| 2026-11-14 | Metro Cable | 8.5 | 1.3 | 0 |
| 2026-11-14 | Example Fiber | 7.9 | 1.4 | 0.2 |
| 2026-11-13 | Metro Cable | 8 | 1.6 | 0.2 |
| 2026-11-13 | Example Fiber | 8.9 | 1.2 | 0.2 |
| 2026-11-12 | Metro Cable | 8.7 | 1.6 | 0 |
| 2026-11-12 | Example Fiber | 9.4 | 0.9 | 0 |
| 2026-11-11 | Metro Cable | 8.1 | 1 | 0 |
| 2026-11-11 | Example Fiber | 8.5 | 1.4 | 0 |
| 2026-11-10 | Metro Cable | 7.7 | 0.8 | 0 |
| 2026-11-10 | Example Fiber | 7.7 | 0.9 | 0 |
| 2026-11-09 | Metro Cable | 8.1 | 1.7 | 0.2 |
| 2026-11-09 | Example Fiber | 8.6 | 1.8 | 0 |
| 2026-11-08 | Metro Cable | 9.4 | 1.7 | 0 |
| 2026-11-08 | Example Fiber | 8.5 | 1.1 | 0 |
| 2026-11-07 | Metro Cable | 8.2 | 1.5 | 0 |
| 2026-11-07 | Example Fiber | 9.3 | 1.2 | 0.2 |
| 2026-11-06 | Metro Cable | 7.8 | 1.2 | 0 |
| 2026-11-06 | Example Fiber | 8.3 | 1.7 | 0 |
| 2026-11-05 | Metro Cable | 8.8 | 1.5 | 0 |
| 2026-11-05 | Example Fiber | 8.4 | 1.1 | 0 |
| 2026-11-04 | Metro Cable | 9.3 | 1 | 0.2 |
| 2026-11-04 | Example Fiber | 8.2 | 1.3 | 0 |
| 2026-11-03 | Metro Cable | 7.9 | 1.2 | 0 |
| 2026-11-03 | Example Fiber | 9.6 | 1.5 | 0 |
| 2026-11-02 | Metro Cable | 8.8 | 1.7 | 0 |
| 2026-11-02 | Example Fiber | 8.5 | 1.8 | 0 |
| 2026-11-01 | Metro Cable | 9.2 | 1.6 | 0 |
| 2026-11-01 | Example Fiber | 7.7 | 1.5 | 0.2 |
| 2026-10-31 | Metro Cable | 8.3 | 1 | 0 |
| 2026-10-31 | Example Fiber | 8.2 | 0.9 | 0.2 |
| 2026-10-30 | Metro Cable | 9.2 | 0.9 | 0 |
| 2026-10-30 | Example Fiber | 7.8 | 1.3 | 0.2 |
| 2026-10-29 | Metro Cable | 8.8 | 0.9 | 0.2 |
| 2026-10-29 | Example Fiber | 8.1 | 1.9 | 0 |
| 2026-10-28 | Metro Cable | 8 | 1.4 | 0 |
| 2026-10-28 | Example Fiber | 7.9 | 1.1 | 0.2 |
| 2026-10-27 | Metro Cable | 7.8 | 1.9 | 0.2 |
| 2026-10-27 | Example Fiber | 8.9 | 2 | 0 |
| 2026-10-26 | Metro Cable | 8.8 | 1.4 | 0 |
| 2026-10-26 | Example Fiber | 8.2 | 1.2 | 0 |
| 2026-10-25 | Metro Cable | 9.5 | 1.5 | 0.2 |
| 2026-10-25 | Example Fiber | 9.3 | 1.7 | 0 |
| 2026-10-24 | Metro Cable | 8.7 | 1.7 | 0 |
| 2026-10-24 | Example Fiber | 8.6 | 1 | 0 |
| 2026-10-23 | Metro Cable | 8.7 | 1.4 | 0 |
| 2026-10-23 | Example Fiber | 7.3 | 1.6 | 0 |
Tunnel stability – last 7 days
2 tunnels · 2 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 6
| When | Type | What | Detail |
|---|---|---|---|
| Nov 22 4:15 PM | ConfigSecurity | Interface wan1 | allowaccess: ping → ping https ssh Admin access (https/ssh) switched on for wan1, which has the public address 203.0.113.27 |
| Nov 22 4:15 PM | ConfigSecurity | Port forward (VIP) rdp-jump | added: extip 203.0.113.27, mappedip 10.17.30.40, extport 3389 New port forward 'rdp-jump': 203.0.113.27:3389 → 10.17.30.40:3389 on wan1 |
| Nov 22 4:15 PM | ConfigSecurity | Firewall policy 12 | added: action accept, srcaddr all, dstaddr rdp-jump New firewall policy 'RDP-Jump-In': accept srcaddr all → dstaddr rdp-jump |
| Nov 13 4:18 PM | Config | Service NL-ERP | added: TCP 8443-8445 |
| Nov 9 9:29 AM | Routing | Route 10.4.60.0/24 | added via to-chicago (OSPF) |
| Oct 24 1:03 PM | Config | Address srv-backup-12 | added: subnet 10.4.30.12 255.255.255.255 |
New and moved devices – last 30 days 3
Devices seen on a switch port for the first time, or on a different port – marked Wired, or Wi-Fi when the port is an access point's (the access point is named). A move from one access point to another is listed as a Wi-Fi roam. Devices on Wi-Fi networks that are tunnelled to the FortiGate never appear on a switch port and are not listed here. Private (randomised) MAC addresses are left out.
| When | Type | What | Detail |
|---|---|---|---|
| Nov 22 4:15 PM | New deviceWiredSecurity | New device d0:43:1e:11:30:28 | 10.17.30.40 NEW-PC on FG-PHOENIX-SW1 port21 · VLAN 30 servers · wired Device not seen before on watched VLAN 30 (servers): d0:43:1e:11:30:28 10.17.30.40 on FG-PHOENIX-SW1 port21 |
| Oct 30 3:54 PM | New deviceWired | New device d0:43:1e:11:30:28 | 10.17.30.40 NEW-PC on FG-PHOENIX-SW1 port21 |
| Oct 27 11:11 AM | New deviceWired | New device 00:40:8c:11:32:01 | 10.17.50.20 CAM-LOBBY-01 on FG-PHOENIX-SW1 port19 |
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
- Security exposure3
- ●admin open to internet
- Admin login reachable on a public address: wan1 203.0.113.27 (static) allows https/ssh
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system interfaceconfig system interface edit "wan1" set ip 203.0.113.27 255.255.255.248 set allowaccess ping https ssh set role wan next endHow to fix
This interface has a public IP address and allows admin access, so the FortiGate's login is reachable from the internet (the Evidence shows the address and the allowaccess line). Trusted hosts limit who can log in, but the login page is still exposed to scanning and to any future vulnerability in it. Manage over the VPN / internal interfaces instead.
- Confirm nobody manages this FortiGate through these interfaces (check with the team first).
- Set allowaccess to the remaining services only (below keeps everything else as it is).
config system interface edit "wan1" set allowaccess ping next end - ●risky service exposed
- 1 port forward(s) put RDP on a public address: rdp-jump (203.0.113.27 tcp 3389 → 10.17.30.40) – reachable from the internet if a firewall policy allows it
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show firewall vipconfig firewall vip edit "rdp-jump" set extip 203.0.113.27 set mappedip "10.17.30.40" set extintf "wan1" set portforward enable set extport 3389 set mappedport 3389 next endHow to fix
These port forwards publish an internal server's management or file-sharing service on a public address. RDP, SSH, SMB and database ports are the most scanned and brute-forced services on the internet.
- Check which firewall policy uses each one (below) and who its source is.
- Not needed: delete the policy, then the VIP.
- Needed: limit the source (set src-filter, or a source address group in the policy) – or use the VPN instead.
- Cameras / DVRs: use the vendor's cloud relay or the VPN rather than an open port.
rdp-jump: 203.0.113.27 tcp 3389 → 10.17.30.40
show firewall policy | grep -f "rdp-jump" config firewall vip edit "rdp-jump" set src-filter <allowed public IPs> next end - ●known-bad addresses not blocked
- No firewall policy drops FortiGuard's known-bad addresses (Malicious servers, Botnet C&C) for traffic going out to them. SD-WAN is on: a policy names the zone (virtual-wan-link), not its member ports.
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show firewall policyset internet-service-src enable set internet-service-src-name "Malicious-Malicious.Server" "Botnet-C&C.Server" "Tor-Exit.Node"How to fix
FortiGuard already knows the addresses of malicious servers, botnet controllers and Tor exit nodes (the Internet Service Database, part of the FortiGuard subscription). A deny policy that uses them stops known-bad traffic at the edge – the FortiGate does the blocking; Vantage only reads the configuration. The policy only works above the allow policies: FortiGate uses the first policy that matches. SD-WAN is on, so the policies name the SD-WAN zone (virtual-wan-link: wan1, wan2). A member port cannot be used in a policy on its own.
- Check the Internet Service names on this firmware (first line below) and adjust them if they differ.
- Block-known-bad-out is added as policy 13, the next free number. The move line puts it above allow policy 2, the first one that lets internet traffic through.
- Paste the commands in a change window. The last lines show each policy, so you can see it took.
- Watch the logs for a day: if something you need is blocked, find out why before making an exception.
- Blocking another way (an external threat feed, or upstream)? Acknowledge this note in the site file ("acknowledged": {"badip_block": {"fortiguard-block": "why"}}).
Caution: a deny policy placed above your allow policies can stop traffic you need if FortiGuard lists an address you use. Use a change window and keep console or out-of-band access.
# The names differ between firmware versions - check them first: show firewall internet-service-name | grep -i -e malicious -e botnet -e tor config firewall policy edit 13 set name "Block-known-bad-out" set srcintf "any" set dstintf "virtual-wan-link" set srcaddr "all" set internet-service enable set internet-service-name "Malicious-Malicious.Server" "Botnet-C&C.Server" set action deny set schedule "always" set logtraffic all next move 13 before 2 end # check the result: show firewall policy 13
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 Phoenix floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment4 devices1 ending soon
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-PHOENIX FortiGate · FortiGate 40F | FGDEMO00170001 tag NL-0017 | Phoenix Northline | 2022-02-12 4.8 years old PO PO-55518 · Example Reseller | Standard 2027-02-01 in 71 days contract NL-SUP-17 warranty 2023-02-12 passed | 2032-09-30 end of order 2027-09-30 | 2028 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-PHOENIX-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF17010001 tag NL-17S01 | Phoenix · Closet 1 · Rack 1 Network team | 2022-02-15 4.8 years old PO PO-56170 · Example Reseller | Standard 2027-03-01 contract NL-FSW warranty 2027-03-01 | 2033-03-31 end of order 2028-03-31 | 2028 → FortiSwitch 124G-FPOE spare: 1 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-PHOENIX-AP1 FortiAP · FAP231F | FP231F17010001 tag NL-17A01 | Phoenix · Ceiling, zone 1 Network team | 2024-05-10 2.5 years old PO PO-57170 · Example Reseller | Standard 2029-06-01 contract NL-FAP warranty 2029-06-01 | 2033-06-30 end of order 2028-06-30 | 2030 → FortiAP 431G spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-PHOENIX-AP2 FortiAP · FAP231F | FP231F17020001 tag NL-17A02 | Phoenix · Ceiling, zone 2 Network team | 2022-05-10 4.5 years old PO PO-57171 · 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. |
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-171 | 500/500 | 16 ms collector ping | 2022-10-18 | 2027-10-18 give notice within 240 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-172 | 300/30 | – | 2024-12-18 | 2027-12-18 give notice within 331 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.17.10.0/24 | 10.17.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Phoenix network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.17.20.0/24 | 10.17.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Phoenix network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.17.30.0/24 | 10.17.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Phoenix network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.17.40.0/24 | 10.17.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Phoenix network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.17.50.0/24 | 10.17.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Phoenix network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.17.90.0/24 | 10.17.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Phoenix 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.