[j-nsp] l2circuit between vlan-ccc and ethernet-ccc

[Rafal Szarecki (WA/EPO)]

TCC will work for IP payload only. This is not pseudowire....

Rafal

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Doug Marschke
> Sent: Friday, October 28, 2005 11:23 PM
> To: sthaug at nethelp.no; ras at e-gerbil.net
> Cc: juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] l2circuit between vlan-ccc and ethernet-ccc
> 
> 
> Check out family tcc on the interfaces.
> 
> Doug
> 
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> sthaug at nethelp.no
> Sent: Friday, October 28, 2005 1:01 PM
> To: ras at e-gerbil.net
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] l2circuit between vlan-ccc and ethernet-ccc
> 
> > How the heck do you set up an l2circuit between a vlan-ccc 
> interface (.1q 
> > tagged on the handoff) on one end, and a ethernet-ccc 
> handoff (not .1q 
> > tagged) on the other end? If you just configure it like 
> normal you get 
> > EM/encapsulation mismatch on the l2circuit, but since the 
> .1q tag is not 
> > included in the actual payload put on the LSP, they should 
> actually be the
> 
> > same packet internally yes?
> 
> Um, why do you think the .1q tag is not put on the LSP for 
> the vlan-ccc
> interface? As far as I know it is.
> 
> You may be able to get around this by using a vlan-map with 
> an explicit
> pop/push operation (haven't tried it though).
> 
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>