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-CHARLOTTE | FortiGate-120G | 7.4.8 | 17% | 48% | 4,190 | 39% · wan1 | — | Working normally |
Switches22 · 0 need a look · PoE 73 of 740 W
| Switch | Model | Ports up | PoE | Port errors | Uplink | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|
| FG-CHARLOTTE-SW1 | FortiSwitch 124F-FPOE | 11 / 28 | 40 of 370 W | — | FG-CHARLOTTE-SW2 port28 (port25) | 7.4.5 | Working normally | |
| FG-CHARLOTTE-SW2 | FortiSwitch 124F-FPOE | 12 / 28 | 33 of 370 W | — | FG-CHARLOTTE-SW1 port25 (port28) | 7.4.5 | Working normally |
Access points44 · 0 down · 0 clients
| Access point | Model | Clients | 2.4 GHz | 5 GHz | Weakest client | Wired to | Firmware | In plain words | |
|---|---|---|---|---|---|---|---|---|---|
| FG-CHARLOTTE-AP1 | FP231F | — | — | — | — | FG-CHARLOTTE-SW1 port3 | 7.4.3 | Working normally | |
| FG-CHARLOTTE-AP2 | FP231F | — | — | — | — | FG-CHARLOTTE-SW2 port3 | 7.4.3 | Working normally | |
| FG-CHARLOTTE-AP3 | FP231F | — | — | — | — | FG-CHARLOTTE-SW1 port4 | 7.4.3 | Working normally | |
| FG-CHARLOTTE-AP4 | FP231F | — | — | — | — | FG-CHARLOTTE-SW2 port4 | 7.4.3 | Working normally |
| VLAN | Name | Subnet | Gateway (FortiGate) | Mask | DHCP | Notes |
|---|---|---|---|---|---|---|
| 10 | users | 10.6.10.0/24 | 10.6.10.1 | 255.255.255.0 /24 | 10.6.10.20 – 10.6.10.250 231 addresses · 7 in use · lease 8 hours | |
| 20 | voice | 10.6.20.0/24 | 10.6.20.1 | 255.255.255.0 /24 | 10.6.20.20 – 10.6.20.250 231 addresses · 2 in use · lease 8 hours | |
| 30 | servers | 10.6.30.0/24 | 10.6.30.1 | 255.255.255.0 /24 | 10.6.30.20 – 10.6.30.250 231 addresses · 0 in use · lease 7 days · 6 reserved | |
| 40 | printers | 10.6.40.0/24 | 10.6.40.1 | 255.255.255.0 /24 | 10.6.40.100 – 10.6.40.199 100 addresses · 0 in use · lease 7 days · 1 reserved | |
| 50 | cameras | 10.6.50.0/24 | 10.6.50.1 | 255.255.255.0 /24 | 10.6.50.100 – 10.6.50.199 100 addresses · 0 in use · lease 7 days | |
| 90 | iot | 10.6.90.0/24 | 10.6.90.1 | 255.255.255.0 /24 | 10.6.90.100 – 10.6.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.6.0/24 | 10.255.6.1 |
Devices by network
| VLAN | Network | Devices | Types |
|---|---|---|---|
| 10 | users | 4 | 3 Computer · 1 Network gear |
| 20 | voice | 2 | 2 Phone (VoIP) |
| 30 | servers | 6 | 5 Storage / server · 1 UPS / power |
| 40 | printers | 1 | 1 Printer |
| 50 | cameras | 1 | 1 Camera |
| 90 | iot | 3 | 2 IoT / industrial (by network) · 1 IoT / industrial |
| FortiLink | FortiLink | 2 | 2 Network gear |
| 10 | users | 4 | 4 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.
2 switches · 23 ports in use · 33 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 closet2 closets23 of 56 ports in use
| Building | Closet | Ports in use | Free access ports | Free PoE | PoE used / budget | |
|---|---|---|---|---|---|---|
| Charlotte | Closet 1 FG-CHARLOTTE-SW1 | 11 / 28 (39%) | 14 | 14 | 40 / 370 W (11%) 330 W headroom | |
| Charlotte | Closet 2 FG-CHARLOTTE-SW2 | 12 / 28 (43%) | 13 | 13 | 33 / 370 W (9%) 337 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-CHARLOTTE-SW1 FortiSwitch 124F-FPOE · Closet 111 in use · 17 free · PoE 40 / 370 W · 1 fiber port · 45 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHARLOTTE-AP1 FortiAP | 10 users | 10.6.10.20 · 00:11:22:06:00:00 | 12.8 W class 4 | |
| port4 | Up | FG-CHARLOTTE-AP3 FortiAP | 10 users | 10.6.10.22 · 00:11:22:06:00:02 | 12.8 W class 4 | |
| port13 | Up | NL-CLT-PC011 | 10 users | 10.6.10.120 · d0:43:1e:06:0a:01 | ||
| port14 | Up | NL-CLT-LT012 | 10 users | 10.6.10.121 · d0:43:1e:06:0a:02 | ||
| port15 | Up | NL-CLT-PC013 | 10 users | 10.6.10.122 · d0:43:1e:06:0a:03 | ||
| port16 | Up | NL-CLT-PH01 phone | 20 voice | 10.6.20.20 · 00:04:f2:06:14:01 | 3.2 W class 2 | |
| port17 | Up | NL-CLT-PH02 phone | 20 voice | 10.6.20.21 · 00:04:f2:06:14:02 | 4.7 W class 2 | |
| port18 | Up | PRN-CLT-01 | 40 printers | 10.6.40.20 · 3c:2a:f4:06:28:01 | ||
| port19 | Up | CAM-DOCK-01 | 50 cameras | 10.6.50.20 · 00:40:8c:06:32:01 | 7.0 W class 3 | |
| port24 | Up | FortiGate · FortiLink trunk FGDEMO00060001 | ||||
| port25 | Up | ↔ FG-CHARLOTTE-SW2 port28 trunk S124FF06020001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–12, port20–23, port26–28
S124FF06010001 · FortiSwitchOS 7.4.5
FG-CHARLOTTE-SW2 FortiSwitch 124F-FPOE · Closet 212 in use · 16 free · PoE 33 / 370 W · 1 fiber port · 40 °C
Blink lights
| Port | Link | Connected to | VLAN | Address | PoE | Media (SFP) |
|---|---|---|---|---|---|---|
| port3 | Up | FG-CHARLOTTE-AP2 FortiAP | 10 users | 10.6.10.21 · 00:11:22:06:00:01 | 10.6 W class 4 | |
| port4 | Up | FG-CHARLOTTE-AP4 FortiAP | 10 users | 10.6.10.23 · 00:11:22:06:00:03 | 11.8 W class 4 | |
| port7 | Up | DC01 | 30 servers | 10.6.30.2 · f8:bc:12:fe:e7:01 | ||
| port8 | Up | FILE01 | 30 servers | 10.6.30.3 · f8:bc:12:46:45:95 | ||
| port9 | Up | MES01 | 30 servers | 10.6.30.4 · f8:bc:12:75:18:23 | ||
| port10 | Up | IPERF01 | 30 servers | 10.6.30.5 · f8:bc:12:af:45:3c | ||
| port11 | Up | NAS01 | 30 servers | 10.6.30.6 · 00:11:32:1a:8f:57 | ||
| port12 | Up | UPS-MDF | 30 servers | 10.6.30.7 · 00:c0:b7:61:5c:18 | ||
| port13 | Up | DOOR-DOCK | 90 iot | 10.6.90.2 · 00:06:8e:9c:58:07 | 4.2 W class 2 | |
| port14 | Up | DOOR-MDF | 90 iot | 10.6.90.3 · 00:06:8e:76:32:9f | 4.2 W class 2 | |
| port15 | Up | ENV-MDF | 90 iot | 10.6.90.4 · b8:27:eb:61:f3:a8 | 1.9 W class 1 | |
| port28 | Up | ↔ FG-CHARLOTTE-SW1 port25 trunk S124FF06010001-0 | Fiber 10G-SR |
Free ports: port1–2, port5–6, port16–27
S124FF06020001 · FortiSwitchOS 7.4.5
On-site contacts
- Avery Chen · (206) 555-1006 (Site contact)
Outages & status
Notes
- Made-up site. Northline is not a real company.
Contract 10/31/2024 to 10/31/2027 · 343 days left · from the Library
Provider status: Example Fiber ↗ · all on Service status
- FortiGate WAN IP
- 203.0.113.16 /29
- Gateway
- 203.0.113.17
- Circuit ID
- NL-061
- Bandwidth
- 500 / 500 Mbps
- Support #
- 800-555-0199
Contract ISP2 · 2/4/2024 to 2/4/2027 · 74 days left
Provider status: Metro Cable ↗ · all on Service status
- FortiGate WAN IP
- 198.51.100.16 /29
- Gateway
- 198.51.100.17
- Circuit ID
- NL-062
- Bandwidth
- 300 / 30 Mbps
- Support #
- 800-555-0199
Configuration summary4 static routes · OSPF configured
From show router static, show router bgp, show router policy and show router ospf at the last collection. Counts only — see Consistency to compare across sites.
| Network | Type | Next hop |
|---|---|---|
| 0.0.0.0/0 | Static | wan1 internet wan2 internet · equal cost |
| 10.0.0.0/8 | Static | blackhole (dropped) |
| 10.1.0.0/16 | 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.10.0/24 | Connected | users local network |
| 10.6.20.0/24 | Connected | voice local network |
| 10.6.30.0/24 | Connected | servers local network |
| 10.6.40.0/24 | Connected | printers local network |
| 10.6.50.0/24 | Connected | cameras local network |
| 10.6.90.0/24 | Connected | iot local network |
| 10.7.0.0/16 | Static | to-charlotte-ot → Charlotte OT |
| 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.255.6.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.16/29 | Connected | wan2 local network |
| 203.0.113.16/29 | Connected | wan1 local network |
From get router info routing-table all at the last collection. A tunnel or IPsec aggregate is named with the site it leads to. Want the full path to a device? Use Find → tick two devices → Build path.
Status – last 30 days
WAN quality
Show as table (daily median)
| Day | Circuit | Latency ms | Jitter ms | Loss % |
|---|---|---|---|---|
| 2026-11-22 | Metro Cable | 9 | 1.3 | 0 |
| 2026-11-22 | Example Fiber | 8 | 1.3 | 0 |
| 2026-11-21 | Metro Cable | 9.5 | 1.6 | 0.2 |
| 2026-11-21 | Example Fiber | 8.4 | 1.1 | 0 |
| 2026-11-20 | Metro Cable | 10.3 | 1.5 | 0.2 |
| 2026-11-20 | Example Fiber | 7.7 | 1.8 | 0 |
| 2026-11-19 | Metro Cable | 10.3 | 1.2 | 0 |
| 2026-11-19 | Example Fiber | 9.1 | 2 | 0 |
| 2026-11-18 | Metro Cable | 9.7 | 1.2 | 0 |
| 2026-11-18 | Example Fiber | 7.9 | 1.4 | 0.2 |
| 2026-11-17 | Metro Cable | 10.1 | 1.4 | 0.2 |
| 2026-11-17 | Example Fiber | 8.3 | 1.6 | 0.2 |
| 2026-11-16 | Metro Cable | 10.5 | 1.2 | 0.2 |
| 2026-11-16 | Example Fiber | 8.5 | 1.4 | 0 |
| 2026-11-15 | Metro Cable | 9.7 | 1.5 | 0 |
| 2026-11-15 | Example Fiber | 8.8 | 1.1 | 0.2 |
| 2026-11-14 | Metro Cable | 8.5 | 1.1 | 0.2 |
| 2026-11-14 | Example Fiber | 8.5 | 1.2 | 0 |
| 2026-11-13 | Metro Cable | 10 | 1.2 | 0 |
| 2026-11-13 | Example Fiber | 7.8 | 1.4 | 0 |
| 2026-11-12 | Metro Cable | 9.5 | 1.4 | 0 |
| 2026-11-12 | Example Fiber | 8.5 | 1.8 | 0.2 |
| 2026-11-11 | Metro Cable | 8.4 | 1.8 | 0.2 |
| 2026-11-11 | Example Fiber | 8.4 | 1.2 | 0 |
| 2026-11-10 | Metro Cable | 10.2 | 1.7 | 0 |
| 2026-11-10 | Example Fiber | 8.6 | 1.5 | 0.2 |
| 2026-11-09 | Metro Cable | 9.1 | 1.3 | 0 |
| 2026-11-09 | Example Fiber | 9 | 1.4 | 0 |
| 2026-11-08 | Metro Cable | 9.3 | 1.4 | 0 |
| 2026-11-08 | Example Fiber | 8.9 | 1.3 | 0.2 |
| 2026-11-07 | Metro Cable | 9.7 | 1.5 | 0 |
| 2026-11-07 | Example Fiber | 9 | 1 | 0 |
| 2026-11-06 | Metro Cable | 9 | 1.2 | 0.2 |
| 2026-11-06 | Example Fiber | 8.1 | 1.4 | 0 |
| 2026-11-05 | Metro Cable | 9.4 | 1.8 | 0.2 |
| 2026-11-05 | Example Fiber | 8.9 | 1.5 | 0 |
| 2026-11-04 | Metro Cable | 8.3 | 1.8 | 0 |
| 2026-11-04 | Example Fiber | 9.1 | 1.5 | 0 |
| 2026-11-03 | Metro Cable | 8.9 | 1.5 | 0.2 |
| 2026-11-03 | Example Fiber | 8.7 | 1.3 | 0.5 |
| 2026-11-02 | Metro Cable | 10 | 1.3 | 0 |
| 2026-11-02 | Example Fiber | 8.5 | 1.4 | 0.2 |
| 2026-11-01 | Metro Cable | 9.6 | 1.4 | 0.2 |
| 2026-11-01 | Example Fiber | 8.6 | 1 | 0.2 |
| 2026-10-31 | Metro Cable | 10 | 1.2 | 0 |
| 2026-10-31 | Example Fiber | 7.9 | 1.4 | 0 |
| 2026-10-30 | Metro Cable | 9.3 | 1.1 | 0 |
| 2026-10-30 | Example Fiber | 8.4 | 1.3 | 0 |
| 2026-10-29 | Metro Cable | 10.3 | 1.3 | 0.2 |
| 2026-10-29 | Example Fiber | 7.5 | 1.6 | 0.5 |
| 2026-10-28 | Metro Cable | 9.2 | 1.5 | 0 |
| 2026-10-28 | Example Fiber | 9.5 | 0.9 | 0 |
| 2026-10-27 | Metro Cable | 10.6 | 1.6 | 0 |
| 2026-10-27 | Example Fiber | 9.2 | 1.1 | 0 |
| 2026-10-26 | Metro Cable | 9.3 | 1.2 | 0.2 |
| 2026-10-26 | Example Fiber | 8.9 | 1.8 | 0.2 |
| 2026-10-25 | Metro Cable | 10.2 | 1.5 | 0 |
| 2026-10-25 | Example Fiber | 9 | 1.4 | 0 |
| 2026-10-24 | Metro Cable | 9.1 | 1.1 | 0.5 |
| 2026-10-24 | Example Fiber | 8.1 | 1.7 | 0 |
| 2026-10-23 | Metro Cable | 9.3 | 1.5 | 0 |
| 2026-10-23 | Example Fiber | 8.2 | 0.8 | 0 |
Tunnel stability – last 7 days
3 tunnels · 3 up on every run in the last 7 days.
Configuration & routing changes – last 30 days 5
| When | Type | What | Detail |
|---|---|---|---|
| Nov 14 9:04 PM | Config | Address srv-backup-54 | added: subnet 10.15.30.54 255.255.255.255 |
| Nov 12 9:28 PM | Config | Static route 22 | added: dst 10.200.0.0 255.255.0.0, device to-chicago |
| Nov 8 4:22 PM | Routing | Route 10.15.60.0/24 | added via to-chicago (OSPF) |
| Oct 28 9:38 AM | Config | Address srv-backup-35 | added: subnet 10.15.30.35 255.255.255.255 |
| Oct 28 9:28 AM | Config | Address srv-backup-30 | added: subnet 10.15.30.30 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 20 10:41 AM | New deviceAccess point | New device 00:11:22:06:00:00 | 10.6.10.20 FG-CHARLOTTE-AP1 on FG-CHARLOTTE-SW1 port3 |
| Nov 14 3:45 PM | Device movedWired | Device moved f8:bc:12:75:18:23 | 10.6.30.4 FG-CHARLOTTE-SW2 port13 → FG-CHARLOTTE-SW2 port9 |
| Oct 28 2:32 PM | New deviceAccess point | New device 00:11:22:06:00:02 | 10.6.10.22 FG-CHARLOTTE-AP3 on FG-CHARLOTTE-SW1 port4 |
Worth fixing when there's time. Security items are listed first and marked in red. Open is the default. A muted, hidden, accepted or won't-fix note stays here and does not change the colour.
How this works
- Redundancy reduced1
- ●HA partner missing
- HA: only 1 of 2 FortiGates in the cluster – no failover (WARNING: FGDEMO00060002 is lost @ 2026/11/10 22:14:05)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
get system ha statusHA Health Status: WARNING: FGDEMO00060002 is lost @ 2026/11/10 22:14:05How to fix
Only one FortiGate is in the cluster, so there is no failover if it dies.
- Check the second unit is powered on.
- Check the HA heartbeat cable/port on both units.
- Confirm both units have the same HA group name, group ID and password.
get system ha status diagnose sys ha history read - Monitoring & housekeeping1
- ●circuit contract 74 days
- Circuit contract: Metro Cable (ISP2) ends 2/4/2027 (74 days left)
Evidence
Exact lines from the FortiGate output collected for this site – check them against the live device.
show system interfacewan2: CT-ISP2-02042024-02042027How to fix
The contract for Metro Cable (ISP2) ends on 2/4/2027. Renewing, renegotiating or moving to another provider all take time, and many contracts need written notice well before the end.
- Check the contract for the notice period and whether it renews by itself (the site's Library has the facts on file).
- Decide with the business: renew, renegotiate or replace the circuit.
- When the new term is signed, change the dates in the tag on the FortiGate interface comment.
- If nothing will be done, acknowledge it in the site file so it stops flagging.
# the tag sits in the comment of the circuit's WAN interface (admin account): show system interface | grep -f CT-ISP config system interface edit "<wan interface>" set description "<what is there now> CT-ISP1-<MMDDYYYY>-<MMDDYYYY>" next 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 Charlotte floor plan ↗ files.example.com – Made-up floor plan.
The site1 fact
Equipment7 devices
| Device | Serial | Where | Bought | Support until | End of support | Replace | |
|---|---|---|---|---|---|---|---|
| FG-CHARLOTTE FortiGate · FortiGate 120G | FGDEMO00060001 tag NL-0006 | Charlotte Northline | 2023-07-16 3.4 years old PO PO-55507 · Example Reseller | Premium 2029-01-12 contract NL-SUP-06 warranty 2024-07-16 passed | 2035-09-30 end of order 2030-09-30 | 2029 spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHARLOTTE-SW1 FortiSwitch · FortiSwitch 124F-FPOE | S124FF06010001 tag NL-06S01 | Charlotte · Closet 1 · Rack 1 Network team | 2023-02-15 3.8 years old PO PO-56060 · 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-CHARLOTTE-SW2 FortiSwitch · FortiSwitch 124F-FPOE | S124FF06020001 tag NL-06S02 | Charlotte · Closet 2 · Rack 2 Network team | 2024-02-15 2.8 years old PO PO-56061 · Example Reseller | Standard 2029-03-01 contract NL-FSW warranty 2029-03-01 | 2033-03-31 end of order 2028-03-31 | 2030 → FortiSwitch 124G-FPOE spare: 0 | sourcehttps://files.example.com/northline/assets Made-up asset row. |
| FG-CHARLOTTE-AP1 FortiAP · FAP231F | FP231F06010001 tag NL-06A01 | Charlotte · Ceiling, zone 1 Network team | 2022-05-10 4.5 years old PO PO-57060 · 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-CHARLOTTE-AP2 FortiAP · FAP231F | FP231F06020001 tag NL-06A02 | Charlotte · Ceiling, zone 2 Network team | 2023-05-10 3.5 years old PO PO-57061 · 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. |
| FG-CHARLOTTE-AP3 FortiAP · FAP231F | FP231F06030001 tag NL-06A03 | Charlotte · Ceiling, zone 3 Network team | 2024-05-10 2.5 years old PO PO-57062 · 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-CHARLOTTE-AP4 FortiAP · FAP231F | FP231F06040001 tag NL-06A04 | Charlotte · Ceiling, zone 4 Network team | 2022-05-10 4.5 years old PO PO-57063 · 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 circuits1 to look at soon
| Circuit | Bandwidth | Ping | From | Ends | Notice | SLA | |
|---|---|---|---|---|---|---|---|
| Example Fiber Example Fiber · wan1 · NL-061 | 500/500 | 14 ms collector ping | 2024-10-31 | 2027-10-31 give notice within 253 days | 90 days renews by itself: no | 99.9 Made-up circuit. | |
| Metro Cable Metro Cable · wan2 · NL-062 | 300/30 | 17 ms collector ping | 2024-02-04 | 2027-02-04 in 74 days give notice within 14 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.6.10.0/24 | 10.6.10.1 | Staff laptops and desktops IT service desk | 10-49 printers and kiosks Made-up Charlotte network. | sourcehttps://files.example.com/northline/networks |
| 20 | voice | 10.6.20.0/24 | 10.6.20.1 | Teams phones and room systems Unified communications | 10-29 conference rooms Made-up Charlotte network. | sourcehttps://files.example.com/northline/networks |
| 30 | servers | 10.6.30.0/24 | 10.6.30.1 | Site servers and storage Infrastructure | 10-40 fixed servers Made-up Charlotte network. | sourcehttps://files.example.com/northline/networks |
| 40 | printers | 10.6.40.0/24 | 10.6.40.1 | Printers and copiers IT service desk | 10-60 all reserved Made-up Charlotte network. | sourcehttps://files.example.com/northline/networks |
| 50 | cameras | 10.6.50.0/24 | 10.6.50.1 | Security cameras and NVR Facilities security | 10-99 all reserved Made-up Charlotte network. | sourcehttps://files.example.com/northline/networks |
| 90 | iot | 10.6.90.0/24 | 10.6.90.1 | Building sensors and door controllers Facilities | 10-50 controllers Made-up Charlotte 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.