[c-nsp] QinQ question

[CiscoNSP_list CiscoNSP_list]

Thanks Iftikhar.


For our smaller POPs (Where we only have Single switch stack, and single router(with cold spare)), we would need to install another switch with QinQ port connecting to our router(with dot1q subints), and then trunk port(Allowing our outer tag only) to providers QinQ port?



Subject: RE: [c-nsp] QinQ question
Date: Tue, 20 Nov 2012 11:52:13 +0000
From: Iftikhar.Mehar at redstone.com
To: cisconsp_list at hotmail.com; cisco-nsp at puck.nether.net

Hi, Service Provider port will be QinQ and your port facing provider’s QinQ port will always remain as trunk port. Same would apply to you and your customer when you provide QinQ to your customers, the only difference would be that you will be the service provider (your port will be QinQ) for your customer (customer port normal trunk). Note: You and your service provider will have to allow enough MTU size to accommodate extra 802.1q headers as each time you apply QinQ it increases the size of a frame. I think 802.1q header size is 4 bytes. Regards From: CiscoNSP_list CiscoNSP_list [mailto:cisconsp_list at hotmail.com] 
Sent: 20 November 2012 05:59
To: Iftikhar Mehar; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] QinQ question   > That's right, using QinQ the provider will tag all frames (customer's
> various VLAN ID frames) using the same VLAN ID at all edges.


Thanks Iftikhar - The provider also offers a service where we do the QinQ(we control all client(tails) vlans)....would we configure the Agg port connecting to the provider as QinQ, or would this remain a trunk and we would have a QinQ port "behind" this....and then on customer site, we would need to install a switch with QinQ port facing CE WAN(And customer would tag vlans), and we would have a trunk allowing that vlan to providers NTU?

Cheers.

  Click here to report this email as spam.


DISCLAIMER:
This message is intended only for the use of the person(s) ("the intended recipient(s)") to whom it is addressed. 
It may contain information which is privileged, proprietary and/or confidential within the meaning of applicable law. 
If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this message (including any attachments) is strictly prohibited. 
If you have received this message in error, please contact the sender of this message as soon as possible. 
The views or opinions expressed in this message are those of the author and may not necessarily be the views held by Maxima Holdings plc.
Maxima Holdings plc trading as Redstone. Registered office: Cotswold Court, Lansdown Road, Cheltenham, Glos, GL50 2JA. Registered in England. 5043538. VAT Number - 728778184
This message has been scanned for malware by Websense. www.websense.com