What is a VLAN?
A VLAN (Virtual LAN) splits one physical network into several logical networks. Two devices on the same switch cannot reach each other directly if they sit in different VLANs.
In practice this means you can separate guest Wi-Fi from payment terminals without pulling a second cable.
- 1
One physical switch
- 2
VLAN 10 — office
- 3
VLAN 20 — checkout / payment
- 4
VLAN 30 — guest Wi-Fi
- 5
Traffic between them passes through routing
A device in one VLAN only reaches another if routing and rules allow it.
Access ports and trunk ports
An access port belongs to a single VLAN and the device behind it knows nothing about VLANs. A trunk port carries traffic for several VLANs with tags, usually between switches or up to access points.
Most field faults come from this distinction: an access port assigned to the wrong VLAN leaves the device without an address, or on the wrong network.
- Device links up but gets no IP: the port may be in the wrong VLAN
- Access point fails on some SSIDs: the VLAN is not allowed on the trunk
- Identical setups behave differently per site: VLAN numbering is inconsistent
Why separate at all?
Separation buys three concrete things. Security: a guest device cannot reach a checkout terminal. Stability: broadcast traffic in one segment does not slow the whole network. Diagnosis: a fault stays inside one segment and is faster to find.
The cost is that access between VLANs has to be defined deliberately — including the monitoring traffic itself.
VLANs from a monitoring point of view
Monitoring only sees the segments it can reach. A check run from a point with no access to the checkout VLAN will always report those devices as unreachable — that is a false positive, not an outage.
In Sentry, checks run over segments where access is defined; where a segment cannot be reached, the state is stated plainly instead of producing a result. Network configuration, creating VLANs and writing rules are out of scope.