SRX Services Gateway
SRX Services Gateway

Conflict between debug and traceoptions

12.16.10   |  
‎12-16-2010 04:43 AM

I was investigating an issue between 2 endpoints on an IPSec VPN connection so I set

request security ike debug-enable level 15

 

and then when I was finished ran

request security ike debug-disable

 

This stopped everything that was previously logged under traceoptions

traceoptions {
    file ike size 1m files 10;
    flag policy-manager;
}

 

I don't know how to make things to back to how they were before and would really like it if someone could help me out.

Thanks,

Mark

3 REPLIES
SRX Services Gateway
Solution
Accepted by topic author mmcgilly
‎08-26-2015 01:27 AM

Re: Conflict between debug and traceoptions

12.16.10   |  
‎12-16-2010 06:47 AM

Try running a "commit full" and see if it restarts the traceoptions.

 

Ben

SRX Services Gateway

Re: Conflict between debug and traceoptions

[ Edited ]
12.16.10   |  
‎12-16-2010 07:28 AM

Depending on config size, level 15 and commit fulls are probably not the best of the best...  Can cause some SERIOUS issues if you have LARGE configs, or LOTS of ike gateways...

 

Control / Forwarding link between the two can get saturated with data...

 

RKIM could explain it better ;o)

 

 

Highlighted
SRX Services Gateway

Re: Conflict between debug and traceoptions

12.17.10   |  
‎12-17-2010 05:23 AM

Thanks for the replies my logging is back to normal now.

 

I had this problem on a SRX210 with only 15 VPNs so I don't think the amount of data is a problem. I do plan on having a lot more VPNs soon so this is something to look out for. Thanks for the heads up.