
FL SWITCH MM HS Virtual Local Area Network (VLAN)
6874_en_16
PHOENIX CONTACT
8-9
1
The infrastructure is also operated in "VLAN Tagging" mode and VLAN 5 is created
based on the relevant devices. Result: high configuration and maintenance costs.
2
GVRP is activated in "VLAN Tagging" mode on all infrastructure components and the
information about the created VLANs is transmitted within the network via switch 1 and
switch 2. Result: bidirectional data exchange is ensured between termination device A
and B.
8.5.1
Dynamic configuration
On the MMS, dynamic VLAN configuration using GVRP can be set for transmission
between infrastructure components. Here, every switch with static or dynamically created
VLANs transmits information within the network via VLAN IDs. The adjacent switches with
activated GVRP then create the same VLANs and add the receiver ports of the GVRP
BPDUs as "tagged" ports. A BPDU receiver then distributes its own BPDUs to all ports via
the dynamically learned VLAN.
Switch configuration
1
All switches must be set to "VLAN Tagging" mode. After saving the configuration, a
restart is required.
2
GVRP must be activated on all switches.
Since termination devices usually do not support VLAN tags, port-specific settings must be
made at the termination device ports for the infrastructure. The switch then adds the
corresponding tags to every data packet received at the relevant port. If a data packet is to
be sent from the termination device port to the termination device, the switch removes the
VLAN tag first.
8.6
VLAN and (R)STP
When using (R)STP and VLAN simultaneously, please note the following:
–
(R)STP is
not
based on VLANs
–
(R)STP creates a loop-free topology in the form of a tree structure
In the event of static VLAN configuration, all possible redundant data paths must be taken
into consideration in the configuration. All possible backbone ports of the network (not the
termination device ports) must be inserted in all available VLANs as "tagged" members.
This ensures that for every possible tree structure that can be generated by (R)STP, every
VLAN can be accessed by every switch.
A typical configuration is illustrated in the following diagram:
RSPSupply - 1-888-532-2706 - www.RSPSupply.com
http://www.RSPSupply.com/p-14178-Phoenix-Contact-2832357-FL-IF-2TX-VS-RJ-D-Media-Module-for-Modular-Switch.aspx