What is a VLAN; what is a VLAN interface for in TR7?
Short answer
VLAN (Virtual LAN) refers to logical L2 networks that are separated from one another with an IEEE 802.1Q tag on a single physical connection; each VLAN is a separate broadcast domain and is identified by a 12-bit VLAN ID. In TR7, a VLAN interface is created on a parent interface (Master Interface: ETH, Bond or LACP) by selecting Type = VLAN in the Add Interface form on the Network → Interfaces screen. VLAN ID is in the range 2–4094, its default value is 2, and it cannot be repeated on the same parent interface. With the IPs added to the VLAN interface, TR7 owns addresses in more than one network over a single cable and can publish vServices or reach Backend Services in those networks. For this, the switch port must carry the related VLANs tagged (trunk).
Where It Is Used in TR7
| Where | Field / label | What for |
|---|---|---|
| Network → Interfaces → Actions → Add Interface | Type = VLAN, VLAN ID, Interface Name, Master Interface, Route Table (if there is more than one route table) | Creating a tagged logical interface on a parent interface |
| VLAN interface → Add IP | Add IP form | Owning an address in the subnet of the VLAN |
| Network → Interfaces list and Network Topology view | Type column VLAN; the topology shows its relationship with the parent interface (Network topology view) | Seeing which VLAN is on which parent interface |
| WEB-CLI | network interface add (type vlan, vlanId, vlanMasterId) (network interface) | Creating the VLAN interface from the command line |
- The order of steps for opening a vService in a different VLAN: What do I need to do on the network side first to open a vService on an IP in a different subnet / VLAN?
VLAN Rules in TR7
- Parent interface: It can be only ETH, Bond or LACP; an interface that is a Bond/LACP member cannot be selected as the parent interface.
- VLAN ID: An integer between 2 and 4094; outside the range, the
VLAN ID must be in range 2-4094warning is given. The same VLAN ID cannot be defined a second time on the same parent interface; the same VLAN ID can be used on different parent interfaces. - Editing: If the VLAN ID, the parent interface, the name or the route table is changed, the VLAN interface is deleted and recreated in the system; the connection is interrupted briefly (System behavior after saving).
- Cluster: The interface definition is common to the two devices and is also created on the peer device with the default auto-sync.
Common Misconceptions
- "A separate physical port is required for each VLAN." VLANs share the same physical connection with tags; it is sufficient for the switch port to carry the VLANs tagged.
- "VLAN ID 1 can be used in TR7." The VLAN ID field accepts the range 2–4094.
- "A VLAN joins networks in different locations." A VLAN divides the same L2 infrastructure; extending an L2 segment over an L3 network is the job of VXLAN (What is VXLAN; how does it differ from VLAN?).
How it is done in the documentation
