Re: [j-nsp] Need Assistance

Ps.. Should that be a /12 ? On Tue, 7 Nov 2017 at 4:53 pm, sameer mughal wrote: > Hi All, > > Kindly review below routes, can anyone please help me to prefer BGP over > OSPF internal route? > What will be the configuration, please? > > 172.16.0.0/16 *[OSPF/10] 1d

Re: [j-nsp] MPLSoMPLS - horrible?

Hi Dale, This is a pretty key point because it will change the way you would implement it.. I'm looking at building a new 'enterprise' network - an extranet of sorts - *on top of* a NSP's L3VPN service. So they are routing IP? It's all Ethernet. Or are they are switching ethernet? If they are

Re: [j-nsp] MPLSoMPLS - horrible?

Ahh I'm with you. A lot of people do refer to a l2 ethernet service (vpls, pseudowires, LES etc) as L3VPN. when you said that it's all Ethernet, I thought I'd raise it :) On 30 September 2010 12:30, Dale Shaw dale.shaw+j-...@gmail.com wrote: Hi Heath, On Thu, Sep 30, 2010 at 9:14 PM, Heath

Re: [j-nsp] Policy based routing on SRX 210

I'm not sure that this is the only issue, but something I just spotted under pbr_fe-0/0/6_adsl: route 0.0.0.0/24 I would have thought that if it didnt match a route that instance, it would have been dropped. If that is the case, then something else is going wrong beforehand and the traffic isn't

Re: [j-nsp] EX4200 ARP Issue

This morning users started complaining that there ips were flapping, they would work for 5 minutes then stop working for 5 minutes. What seemed to fix this issue was clearing the ARP table. This switch has all customer vlans and routes customer subnets. Did it occur once, or you had to had

Re: [j-nsp] EX4200 Error Log

Has anyone ever seen this in the message logs? Seems to be the exact same time my network started to flap. Sep 27 11:53:47  core1.pit1 fpc0 Resolve request came for an address matching on Wrong nh nh:1890, type:Unicast...?

Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases.

On 23 July 2010 08:03, Pavel Lunin plu...@senetsy.ru wrote: But excuse me. The way we discuss it here reminds me those teenager-style web-forums where they have been talking 'windows-must-die' for last 15 years. Everyone just thinks it's his duty to claim 'junos is so buggy, so buggy! I am

Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases.

Cheers for the insight Pavel - sounds like you have been on this one for a while.. I'm just curious about the cash people actually have to spend on routers/firewalls these days. All the providers (especially small/mid sized ones) I have dealt with are trying to remain competitive in a really

Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases.

Chris I think you've hit the nail on the head here.. In my experience communication from Juniper is, exactly that. Simplex mode only. Any opening up of channels and getting the message from customers and 'partners' back into Juniper is greatly appreciated! Cheers On 22 July 2010 20:59, Chris

Re: [j-nsp] J series users bitten by the massive memory use increase with flow mode add, please file jtac cases.

Just a quick thought... what about renaming the flowd binary..? No I haven't tested it :) On 20 July 2010 23:14, Christopher E. Brown chris.br...@acsalaska.netwrote: I know alot of us here have been bitten by this, and the fact that disabling flow mode and reverting to packet does not

Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases.

: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Heath Jones Sent: 21 July 2010 11:05 To: C... Just a quick thought... what about renaming the flowd binary..? No I haven't tested it :) On 20 J

Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases.

I think you should actually give the renaming of the binary a go. If you rename flowd (or name of process using memory), it wont be found and loaded on next boot. Obviously this is a hack and not what you want to be relying on in a production network, but if it solves the issue then good. That and

Re: [j-nsp] J series users bitten by the massive memory useincrease with flow mode add, please file jtac cases.

What is the process name? I thought on the J series it was the fwdd process or something similar that controlled forwarding. On 21 July 2010 21:52, Christopher E. Brown chris.br...@acsalaska.netwrote: On 7/21/2010 12:48 PM, Heath Jones wrote: I think you should actually give the renaming

Re: [j-nsp] J series users bitten by the massive memory use increase with flow mode add, please file jtac cases.

Chris - Is the current situation: that Juniper have said there is no workaround / configuration change that can be made to stop the allocation of memory for the flow forwarding information? On 20 July 2010 23:14, Christopher E. Brown chris.br...@acsalaska.netwrote: I know alot of us here