[f-nsp] VPLS and Q-in-Q
spenserhuang at aptg.com.tw
spenserhuang at aptg.com.tw
Tue Dec 23 21:04:34 EST 2008
Dear Lazuardi:
The following are the sample configuration you have asked.
Let's say the inner voice vlan id is 101, inner data vlan id is 102, the outter q-in-q vlan id is 901.
You will find that the vlan id 101 & 102 didn't use in those device. This because that the vlan id 101 & 102 are looked as payload. The QoS setting of vlan id 101 and 102 will follow the vlan id 901. You may use 'aggregtaed-vlan-copy-cos' or 'qos decode-cvlan-pcp' command to have MLX copy the inner vlan qos to outter vlan. However, FESX didn't support this feature.
Regards,
Spenser.
-----------------------------------------------------------------------------------------------------
For FESX-A
jumbo
aggregated-vlan
tag-type 9100 ethernet 13 to 24(the ports to connect Q-in-Q customers)
vlan 901
untag e 13(the ports to connect Q-in-Q customer)
tag 1 (uplink port)
-----------------------------------------------------------------------------------------------------
For FESX-B
jumbo
aggregated-vlan
tag-type 9100 ethernet 13 to 24(the ports to connect Q-in-Q customers)
vlan 901
untag e 13(the port to connect Q-in-Q customer)
tag 1 (uplink port)
-----------------------------------------------------------------------------------------------------
For MLX
default-max-frame-size 9216
tag-type 9100 e 3/1(the port connect to Node C cutomer)
vpls Q-in-Q-test 901 cos 1(cos 0-7 is optional)
vlan 901
tag e 3/2(the port connect to FESX-A & FESX-B)
untag e 3/1(the port connect to Node C cutomer)
------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20081224/69b45d90/attachment.html>
More information about the foundry-nsp
mailing list