xmin0s at gmail
May 5, 2012, 7:18 AM
Post #5 of 6
(599 views)
Permalink
|
Gotta love those proteus guys. Doing a write up on this so I don't have to :)
http://www.proteus.net/sites/default/files/how_to_disable_idp_in_an_srx_0.pdf
I'm pretty sure you need to either kill the process or bounce the box
for it to "officially" take effect as the memory is allocated/consumed
upon start up.
Hope this helps,
-Tim Eberhard
On Sat, May 5, 2012 at 7:51 AM, David Klein <davidklein [at] dhk> wrote:
> How do you disable IDP and UTM?
>
> Thanks...
>
> -David Klein
>
> -----Original Message-----
> From: juniper-nsp-bounces [at] puck
> [mailto:juniper-nsp-bounces [at] puck] On Behalf Of Tim Eberhard
> Sent: Friday, May 04, 2012 9:13 PM
> To: Maciej Jan Broniarz
> Cc: juniper-nsp [at] puck
> Subject: Re: [j-nsp] problems with srx240
>
> If I recall correctly, I looked into this previously and found that this was
> due to idp being enabled (which it is by default) but not being used by
> policy. I want to say the fix to stop these non-impacting albeit annoying
> log messages is to just disable IDP all together.
>
> Hope that helps,
> -Tim Eberhard
>
> On Fri, May 4, 2012 at 5:38 PM, Maciej Jan Broniarz <gausus [at] gausus>
> wrote:
>> Hi,
>>
>> My SRX240 box started showing the following error in the logs:
>>
>> May 5 00:36:08 srx240-lab srx240-lab Frame 00: sp = 0x49202a58, pc =
>> 0x08020254 May 5 00:36:08 srx240-lab srx240-lab Frame 01: sp =
>> 0x49202b00, pc = 0x0800c1fc May 5 00:36:08 srx240-lab srx240-lab
>> Frame 02: sp = 0x49202b70, pc = 0x0800d300 May 5 00:36:08 srx240-lab
>> srx240-lab Frame 03: sp = 0x49202b90, pc = 0x082cb550 May 5 00:36:08
>> srx240-lab srx240-lab Frame 04: sp = 0x49202be8, pc = 0x080198c0 May
>> 5 00:36:08 srx240-lab srx240-lab Frame 05: sp = 0x49202c10, pc =
>> 0x080198c0 May 5 00:36:08 srx240-lab srx240-lab Frame 06: sp =
>> 0x49202c38, pc = 0x080198c0 May 5 00:36:08 srx240-lab srx240-lab
>> Frame 07: sp = 0x49202c60, pc = 0x08019a2c May 5 00:36:08 srx240-lab
>> srx240-lab Frame 08: sp = 0x49202c98, pc = 0x0801fc34 May 5 00:36:08
>> srx240-lab srx240-lab Frame 09: sp = 0x49202cc0, pc = 0x09dc54c8 May
>> 5 00:36:18 srx240-lab srx240-lab SCHED: Thread 14 (Forwarding Thread)
>> ran for 1572 ms without yielding May 5 00:36:18 srx240-lab
>> srx240-lab Scheduler Oinker May 5 00:36:18 srx240-lab srx240-lab
>> Frame 00: sp = 0x491b8c68, pc = 0x08020254 May 5 00:36:18 srx240-lab
>> srx240-lab Frame 01: sp = 0x491b8d10, pc = 0x0800c1fc May 5 00:36:18
>> srx240-lab srx240-lab Frame 02: sp = 0x491b8d80, pc = 0x088b3c8c May
>> 5 00:36:18 srx240-lab srx240-lab Frame 03: sp = 0x491b8dd0, pc =
>> 0x088b76d0 May 5 00:36:18 srx240-lab srx240-lab Frame 04: sp =
>> 0x491b8e50, pc = 0x0801fc34 May 5 00:36:18 srx240-lab srx240-lab
>> Frame 05: sp = 0x491b8e78, pc = 0x09dc54c8
>>
>> The box isn't heavy loaded - just about 1-2megs of trafiic per sec.
>>
>> What might be the problem here?
>>
>> All best,
>> mjb
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp [at] puck
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp [at] puck
https://puck.nether.net/mailman/listinfo/juniper-nsp
|
