I know that there are a number of hardware limitations when it comes to L2VPN configurations on the SIPs, so it's probably safe to assume that it's not supported.
On Tue, Apr 22, 2014 at 9:14 AM, Raheel Muhammad <[email protected]>wrote: > Yup xconnect worked under service instance. > On 22 Apr 2014 16:10, "Pete Lumbis" <[email protected]> wrote: > >> It's possible that Q-inQ mapping isn't supported but EVC style is. If you >> move it to EVC for the xconnect does it work? >> >> >> On Tue, Apr 22, 2014 at 8:42 AM, Raheel Muhammad < >> [email protected]> wrote: >> >>> Hi, >>> >>> It works and why i wanted to do it is we already have lot of customers >>> configured as sub interfaces and this interface is the only option to >>> configure service instance and i was getting error on sub interface when i >>> was configuring xconnect on a QinQ sub interface. >>> >>> Thanks >>> >>> >>> On Tue, Apr 22, 2014 at 3:37 PM, Pete Lumbis <[email protected]> wrote: >>> >>>> Probably not, but I'd ask why? EVC does the same thing as subs but with >>>> more flexibility? >>>> >>>> >>>> >>>> On Tue, Apr 22, 2014 at 4:28 AM, Raheel Muhammad < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> Might be a stupid question but have never done it, can we mix up >>>>> service >>>>> instance and sub interface configuration on the same main interface. >>>>> >>>>> I am using SPA-5X1GE-V2 on 7600. >>>>> >>>>> Thanks >>>>> Raheel Muhammad >>>>> _______________________________________________ >>>>> cisco-nsp mailing list [email protected] >>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp >>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/ >>>>> >>>> >>>> >>> >> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
