[c-nsp] asr920 tag translation 1-to-2 unsupported?

[Mike]

Yep - that absolutely works, thank you!



On 4/20/20 6:29 PM, Tan Shao Yi wrote:
> Hi Mike,
>
> Would this work for you?
>
> bridge-domain X
>
> interface A
> service instance 1 ethernet
> encapsulation dot1q 131
> rewrite ingress tag pop 1 symmetric
> bridge-domain X
>
> interface B
> service instance 1 ethernet
> encapsulation dot1q 313 second-dot1q 10
> rewrite ingress tag pop 2 symmetric
> bridge-domain X
>
> Hope this helps.
>
> Regards,
> ShaoYi Tan
>
> On 21/4/20, 3:51 AM, "cisco-nsp on behalf of Mike" <cisco-nsp-bounces at puck.nether.net on behalf of mike+lists at yourtownonline.com> wrote:
>
>     Hello,
>
>         I have an ASR920 and   I am trying to translate input dog1q tag
>     '131' to dual-tagged '313,10'. My intention is to the bridge this over
>     to another port that expects these frames on 313,10. But when I try
>     configuring the translation, I get the following:
>
>     Router(config)#interface gi0/0/0
>     Router(config-if)#service instance 1 ethernet
>     Router(config-if-srv)#encapsulation dot1q 131
>     Router(config-if-srv)#rewrite ingress tag translate 1-to-2 dot1q 313
>     second-dot1q 10 symmetric
>      1_TO_2 not supported on EFP
>      This rewrite ingress on ServInst 1(Gi0/0/0) is not allowed by platform
>     or other components.
>
>
>         Can anyone tell me how to get this done or is this just not possible
>     on asr920?
>
>     _______________________________________________
>     cisco-nsp mailing list  cisco-nsp at puck.nether.net
>     https://puck.nether.net/mailman/listinfo/cisco-nsp
>     archive at http://puck.nether.net/pipermail/cisco-nsp/
>