Re: [j-nsp] Vccv ping on l2vpns on JuniperM320

2008-07-25 Thread Stacy W. Smith
No config missing. JUNOS software does not support the required VCCV interface parameter sub-TLV in it's PW signaling advertisements. This will be supported in JUNOS 9.2R1. --Stacy On Jul 25, 2008, at 12:21 AM, Dinesh Bhonsle wrote: Hi, I have a l2vpn circuit between Juniper M320 and Al

Re: [j-nsp] Vccv ping on l2vpns on JuniperM320 [ second try]

2008-07-25 Thread Dinesh Bhonsle
Second try . -Original Message- From: Dinesh Bhonsle [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2008 11:22 PM To: 'juniper-nsp@puck.nether.net' Subject: Vccv ping on l2vpns on JuniperM320 Hi, I have a l2vpn circuit between Juniper M320 and Alcatel 7750 box. But Juniper do

Re: [j-nsp] VPLS NSR in 9.1

2008-07-25 Thread Harry Reynolds
Updating list. I believe the issue relates to use of mesh-groups, which are not supported for vpls nsr as of 9.1. I've raised a doc pr (305644) to have the release notes appended. Regards ___ juniper-nsp mailing list juniper-nsp@puck.nether.net http

Re: [j-nsp] VPLS in J series router?

2008-07-25 Thread Eugeniu Patrascu
Rubens Kuhl Jr. wrote: Can I expand the question to what L2 and L3 VPNs methods are supported on all J-series from J2320 to J3650 ? Did a lab a while ago with 2 J4350 as PE routers and L2 and L3 VPNs worked without any problems. The only thing that did not worked very good was BFD with very

Re: [j-nsp] VPLS in J series router?

2008-07-25 Thread Muhammad Asif Rao
vpls is not supported over J series, http://atm.tut.fi/list-archive/juniper-nsp-2005/msg01217.html @$if On Fri, Jul 25, 2008 at 7:18 PM, Rubens Kuhl Jr. <[EMAIL PROTECTED]> wrote: > Can I expand the question to what L2 and L3 VPNs methods are supported > on all J-series from J2320 to J3650 ? > >

Re: [j-nsp] VPLS in J series router?

2008-07-25 Thread Rubens Kuhl Jr.
Can I expand the question to what L2 and L3 VPNs methods are supported on all J-series from J2320 to J3650 ? Rubens On Fri, Jul 25, 2008 at 6:10 AM, Farhan Jaffer <[EMAIL PROTECTED]> wrote: > Hi, > > I need to enable encapsulation vlan-vpls in J6350, but it is not > supported on that platform. I

Re: [j-nsp] load balance traffic

2008-07-25 Thread sunnyday
I don't have it configured but the thing is that I ping at the gateway [EMAIL PROTECTED] run ping 1.1.1.1 source 10.11.11.7 (pp0.0) PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=127 time=42.211 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=127 time=20.205 ms ^C [edit] [

Re: [j-nsp] load balance traffic

2008-07-25 Thread sunnyday
I have logged traffic at the interfaces and found that the router is using the loopback as source address for reaching the gateway When specifying the 2 interfaces the pings work How can I change the default selection of the loopback address? -Original Message- From: [EMAIL PROTECTED] [m

[j-nsp] load balance traffic

2008-07-25 Thread sunnyday
Hello I have a j router with 2 adsl cards they have been assigned ip address from the bras. pp0.0 upup inet 10.11.11.7 --> 1.1.1.1 pp0.1 upup inet 10.11.11.8 --> 1.1.1.1 the problem is that only one adsl card(

[j-nsp] VPLS in J series router?

2008-07-25 Thread Farhan Jaffer
Hi, I need to enable encapsulation vlan-vpls in J6350, but it is not supported on that platform. Is there any alternative method / trick? -FJ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] J-2320 base configuration - gotchas

2008-07-25 Thread Eugeniu Patrascu
Rubens Kuhl Jr. wrote: Hi... I'm sizing a J-2320, and noticed the following RAM and flash defaults: • 256 MB DRAM default, expandable to 1 GB DRAM • 256 MB compact flash default, upgradeable to 1 G What is possible and not with such a configuration, like installing recent JunOS versions, FIB s

Re: [j-nsp] J-2320 base configuration - gotchas

2008-07-25 Thread Lee Hetherington
Hi There, We have 4 of the J2320-JH which come with 1Gb ram as standard but have just upgraded them to 2Gb. We are running BGP with 4 full routing tables on them with no issues what so ever. I think we had something like 500k routes in our table when on 1Gb ram (running somewhere close to 750mb