On the port at Switch A facing customer the port is configured for qinq vlan X and also l2protocol tunnel enabled (stp, vpt, cdp) Switch A port toward Core switches is configured as Trunk allowing the vlan X. At ME3600 (facing Core switches) is configured service instance with xconnect (IP of ME3600 -2) encapsulation default and also l2protocol tunnel enabled. Also the same thing at ME3600 at port facing the switch B is configured service instance encapsulation default, xconnect ip of ME36001 and also l2protocol tunnel enabled
Switch B port toward Customer is configured as qinq vlan x and also l2protocol tunnel enabled (stp, vtp, cdp)
So the question is, will the BPDU of Customer network (or VTP) will interfere with BPDU (or VTP of Core switches, switch A and SwitchB). How the packet from customer (qinq and l2pt enabled) will be handled at ME3600 with service instance (encapsulation default and l2 protocol tunnel enabled)
if an ISP has configured service instance with l2protocol tunnel and encapsulation default, I as a customer can i send packet qinq vlan X with l2protocol tunnel enabled across ISP's Tunnel. How this packets will be handled by ME3600-s
The xconnect on a service instance will suck up all VLANS (encapsulation default syntax used) except your PDU's like BPDUS,CDP, ect unless specified
Service instance encapsulation dot1q, is a match criteria only. The rewrite funcion dictates what is done with the tag. If you leave it off "rewrite ingress tag" then I believe the whole frame is encapsulated. If it goes on, then if you are doing qinq, use rewrite ingress tag pop 2, as you encapsulation will be matching 2 tags.
But you still have to add the keyword for encapsulating PDU's
Will the bpdu from customer network (whitch are encapsulated with known multicast from l2protocol tunnel at edge switch) arrive at the other end at customer (edge switch Switch B which is also configured with l2 protocol tunnel qinq) intact or the configuration made at Switch ME3600 will mess the thing up, because we have configured also l2 protocol tunnel at ME3600 for bpdu of service provider
Not 100% sure what you mean by conflict with the SP BPDU, as PE-PE is usually MPLS. So if you had an xconnect a the edge UNI, facing customer A, sending acccross the SP Core to Cust B, if the SP on the service-instance allows the flooding/sending of BPDU, I can't see where the confilict would arise in the SP Core? The rewrite action happens symetrically so on egress and ingress, the L2 VLAN ID is stripped on ingress and re-inserted on egress, with a value stipulated by the encapslulation command. BPDU's are treated as such:
I would say on the service instance set encapsulation default, and perform no tag rewrite, just send it though fully tagged.
If I had the equiptment I would lab up, tagging the native vlan on the Cusctomer switch as well, and monitor the results. Its quite hard to say for sure, purely from a theoretical perspective if the above would actully produce your expected results.
But if i use the option l2protocol forward at ME3600 and l2protocol tunnel at the port facing the customer, should there be any problem? Will BPDU of customer will arrive intact at the other side? IN this case is necessary the native vlan tag at customer switch?
The Cisco EPN system incorporates a network architecture designed to consolidate multiples services on a single Multiprotocol Label Switching (MPLS) transport network. This network is designed primarily based on Application Engineered...
Internet security is important with the increasing attacks that are happening every day. Many internet and browsing security solutions exist, but some are not very easy to use or maybe the question is how can I enable them?
Cisco Software Manager Server
This document describes the programmatic interfaces, RESTful APIs, which are supported by Cisco Software Manager Server (CSM Server).
CSM Server supports a set of finite RESTful APIs. The fir...