cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
293
Views
0
Helpful
2
Replies
Highlighted
Beginner

ASR9k L2VPN attachment circuit into switch (untagged frame)

Hi guys,

I'm trying to look at the best solution for creating a pseudo-wire on an ASR9k and extending the attachment circuit into either a 6500 or Nexus 6001 switch.

The attachment circuit needs to be untagged so the customer can push whatever VLAN they want onto their frames. The scenario I'm looking at would involve either a Nexus 6001 or 6500 which would sit downstream of the PE and provide the physical presentation to the customer.

I've thought of an EVC using a Dot1q tunnel with each customer associated with an S-tag on the PE and switch, but haven't tested this. Another way might be to use a bridge-domain to link two interfaces together on the PE, but this would still potentially require Q-in-Q to isolate each customer and allow each customer to push whatever C-tags they want onto the frames.

Any help on this would be much appreciated!

Steve

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

the best way to me, and i've

the best way to me, and i've tested this, would be:

 

 

customer--(dot1q)--qinq/tunnel----6500----(AC)---(dot1q-SVLAN)ASR9k(mpls)

 

 

that way you can provide vlan transparency without having to re-provision each customer.

View solution in original post

2 REPLIES 2
Highlighted

the best way to me, and i've

the best way to me, and i've tested this, would be:

 

 

customer--(dot1q)--qinq/tunnel----6500----(AC)---(dot1q-SVLAN)ASR9k(mpls)

 

 

that way you can provide vlan transparency without having to re-provision each customer.

View solution in original post

Highlighted

the best way to me, and i've

the best way to me, and i've tested this, would be:

 

 

customer--(dot1q)--qinq/tunnel----6500----(AC)---(dot1q-SVLAN)ASR9k(mpls)

 

 

that way you can provide vlan transparency without having to re-provision each customer.

CreatePlease to create content