Hi Everyone,

We have carrier AGG's coming into 4948's(Trunk ports), which then connect to 
ME3600's(For L3VPN etc)....We agree on vlans for each customer tail with 
carrier...customers can have multiple vlans(services) over the one "service".

Now I assume the carrier would be doing something like this:

- Carrier AGG port facing us is a QinQ port with vlan 10, connects to 4948 
trunk port with all customer agreed vlans.- Carrier carries our "outer tag" to 
all our customers NTU's (Each having a trunk port back to providers PE, which 
would be a QinQ port, with vlan 10)- We tag vlan 30 for CUST_A on 4948 trunk 
port, and Carrier NTU at CUST_A also tags vlan 30, and the link is made 
(Customer brings up L3, and we do also on ME3600.

Would that be correct?

If so, and we wanted to run multiple vlans to a customer, but without engaging 
Carrier (i.e. QinQinQ), I assume we would need to do something like this:

CUST_A - We would need to have a "device" (eg ME3400) that has QinQ port facing 
customer(Outer tag vlan 11), and customer connects to this with a device(Trunk 
port) tagging the vlans we agree on (Say 100,110)...The ME400 then has a trunk 
port to carrier, only allowing vlan 11(This would be the agreed single service 
vlan ID agreed to with the carrier), and our AGG port to carrier also has vlan 
11 tagged...this is the part where Im not 100% on...can we do "something" on 
the ME3600 to pop the outer tag(vlan 11), and create the Layer3 ints with the 
inner tags(Vlans 100,110)..

Thanks in advance for all comments/suggestions...cheers.




                                          
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to