Operation and Maintenance Manual

MultiHaul™ Installation, Operation and Maintenance Manual
Page 70
• VLAN Translation
For cases where you want to translate incoming VLAN to another VLAN.
In this example Bridge #2 will be used to translate incoming traffic with C-VLAN 100
from port eth1 and transmitted with C-VLAN 200 over port eth2 (and vice-versa).
Bridge #1 will implement transparent bridge on all other ports (transparent bridge
between all ports but eth1 and eth2).
• Isolation Traffic of One TU from Other TUs
For cases where you would like to separate the traffic of different terminal units using
VLANs as services in your network are tagged, per user, with different VLANs.
To achieve this goal, a VLAN and a dedicated bridge is configured. Such VLAN will
continue to the network and should be terminated/manipulated by customer’s network
switches/routers.
In this example management is carried throughout the network over C-VLAN 4000. TUs
1 to 8 will be tagged with VLAN 11 to 18 respectively. End user’s traffic at each TU will
remain untagged.
On the BU side, Bridge #1 will be used for management coming from port eth1 over C-
VLAN 4000 and will egress with this VLAN to all terminal units and the host.
A separate bridge (Bridges #2 to 9) will be defined to carry VLANs 11 to 18 to the
respective terminal units. The reason separate bridge is defined for each VLAN is to
assure separation between traffic coming from different TUs.
On the terminal unit side, two bridges will be used. Bridge #1 to carry management over
C-VLAN 4000. Bridge #2 will be used to tag all other traffic coming on port eth1 on the
relevant C-VLAN (C-VLAN 11 for TU 1, up to C-VLAN 18 to TU 8).
Note:
Remember that you can also achieve this goal by enabling the “Terminal Units
Isolation” to separate (isolate) traffic coming from different terminal units.
If enables, “Terminal Units Isolation” overrides any bridge configuration.