Page 56 / 91 Scroll up to view Page 51 - 55
56
Scenario V:
In this scenario, the WLAN Residential Gateway supports VoIP, IPTV application and
internet access. As illustrated in Figure 6, IPTV applications are connected to Port 1 (P1)
and Port 2 (P2); VoIP application is connected to Port 3 (P3) and one PC device is
connected to Port 4 (P4) to access the internet. If you would like the WLAN Residential
Gateway to control how much traffic gets forwarded for VoIP application (Port 5060) and
Internet access (Port 80) as wished (12Mbps for VoIP, 4Mbps for Internet), you can follow
the suggested setup steps below.
Step 1. Set Up NAT/Bridge Mode
In the scenario provided,
Mode 2: 3 WAN & 2 LAN
can be selected to group the WAN port,
Port 1 & 2 to Bridge Mode and Port 3 & 4 to NAT Mode.
Page 57 / 91
57
Step 2. Set Up Egress QoS Control
Egress QoS Control provides five bandwidth modes for users to set up the required
bandwidth based on the actual networking environment. In this scenario, the bandwidth
mode
By Application
can be used to prioritize the egress bandwidth to 12Mbps for VoIP
application and 4Mpbs for Internet access.
Select
By Application
:
Set up rule No.1for limiting VoIP Port 5000~5009 bandwidth.
-
Select
Destination or Source
. This means that both Destination Address and Source
Address with the specified port number will follow the bandwidth setting.
-
Set Port Start to 5000 and Port End to 5009.
-
Select Q3 (highest priority).
Set up rule No.2 for limiting Http Port 80 bandwidth.
-
Select
Destination or Source
. This means that both Destination Address and Source
Address with the specified port number will follow the bandwidth setting.
-
Set Port Start and Port End to 80.
-
Select Q2.
Page 58 / 91
58
Set up rule No.3 for limiting Https Port 443 bandwidth.
-
Select
Destination or Source
. This means that both Destination Address and Source
Address with the specified port number will follow the bandwidth setting.
-
Set Port Start and Port End to 443.
-
Select Q2.
Set Queue 2
s reserved bandwidth to 4096K.
Set Queue 3
s reserved bandwidth to 12288K.
2.6.6 Configure Q-in-Q
The IEEE 802.1Q double tagging VLAN is also referred to Q-in-Q or VLAN stacking (IEEE
802.1ad). Its purpose is to expand the 802.1q VLAN space by tagging the inner tagged
packets. In this way, a “double
-
tagged” frame is created
so as to separate customer traffic
within a service provider network. As shown below in
Double-Tagged Frame
illustration, an
outer tag is added between source destination and inner tag
at the provider network’s edge.
This can support C-VLAN (Customer VLAN) over Metro Area Networks and ensure
complete separation between traffic from different user groups. Moreover, the addition of
double-tagged space increases the number of available VLAN tags which allow service
providers to use a single SP-VLAN (Service Provider VLAN) tag per customer over the
Metro Ethernet network.
Preamble
SFD
D
A
S
A
Type/LEN
PAYLOAD
FCS
Original frame
Preamble
SFD
D
A
S
A
TAG
TCI/P/C/VID
Type/LEN
PAYLOAD
FCS
802.1q
Frame
Preamble
SFD
D
A
S
A
Outer Tag
or SP-Tag
Inner Tag
or C-Tag
TCI/P/C/VID
Type/LEN
PAYLOAD
FCS
Double-
tagged
Frame
Double-Tagged Frame
As shown below in
Q-in-Q Example
illustration, Headquarter A wants to communicate with
Branch 1 that is 1000 mile away. One common thing about these two locations is that they
have the same VLAN ID of 20, called C-VLAN (Customer VLAN). Since customer traffic will
be routed to service provider
s backbone, there is a possibility that traffic might be forwarded
insecurely, for example due to the same VLAN ID used. Therefore, in order to get the
information from Headquarter to Branch 1, the easiest way for the carrier to ensure security
Page 59 / 91
59
to customers is to encapsulate the original VLAN with a second VLAN ID of 100. This
second VLAN ID is known as SP-VLAN (Service Provider VLAN) that is added as data
enters the service provider
s network and then removed as data exits. Eventually, with the
help of SP-Tag, the information sent from Headquarter to Branch 1 can be delivered with
customers
VLANs intact and securely.
Q-in-Q Example
Q-in-Q Setup Steps:
Step 1. Set up Bridge/NAT Mode
Q-in-Q only works in ports that belong to Bridge Mode. Before going any further, please
make sure that the appropriate mode is selected.
Please make sure that packets received from Bridged ports already carry a tag (C-tag).
In this way, a second tag (SP-tag) can be added.
Page 60 / 91
60
Step 2. Enable Ingress Double Tag
Enable Ingress Double Tag on Bridged ports that you would like to add an additional tag
(SP-tag).
Step 3. Set up PVID
Set up a PVID. When packets received with a tag, the PVID will be added. In this example,
PVID 100 will be added (Inner tag+ PVID 100).
Step 4. Set up Egress Forwarding Table
Set up VID 100
s Egress Forwarding Table. WAN port must set to
T
(Tagged) to enable
the Gateway to deliver double-tagged packets. If
U
is assigned to WAN port, PVID will be
removed; therefore, packets with one tag are forwarded.

Rate

3.5 / 5 based on 2 votes.

Popular CTSystems Models

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top