Re: [j-nsp] Subject: Olive and l2circuit

As to my understanding l2circuit just needs encap vlan-ccc on em...i can unicast the configs. As suggested earlier TCC/l2vpn/Vpls doesn't work. On Fri, May 29, 2009 at 8:27 AM, Truman Boyes tru...@suspicious.org wrote: fxp or em interfaces do not support family ccc or tcc. On 29/05/2009,

Re: [j-nsp] Olive and l2circuit

As far as l2ckt(ldp) is concerned it supports both vlan-ccc on em/fxp and works pretty well. L2vpn doesn't work as em/fxp isn't supported in the l2vpn routing-instance. On Thu, May 28, 2009 at 5:42 PM, Danny Vernals danny.vern...@gmail.comwrote: On Wed, May 27, 2009 at 4:30 PM, Harry Reynolds

[j-nsp] InterOP L2circuit(martini) support for interworking ethernet vc-type 5

Hello, Does JunOS 8.4 have support for interworking ethernet on l2circuit ? We have seen that l2circuit comes up if we set interworking as ip on C and encap frame-relay-tcc on J for FR to Eth Vlan ckt. But if we change the interworking as ethernet on C,we get error message as 'vc-type mismatch).

[j-nsp] Indirect next Hop

Hello, Can anyone explain Indirect Next Hop(JunOS 8.2) and how does it improve bgp convergence. Thanks ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Vpls-ldp signaling

Thanks Steinar. That clears it up. I wonder why Juniper has mentioned Ldp based signaling for Vpls in 7.6Release Notes. Probably they need to remove it from 7.6 release notes as they don't support it to avoid unnecessary confusion. On 3/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: