Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1777
  • Last Modified:

Juniper debug settings

Hi,

I need to get some debug logs from a netscreen firewall.
Now this in itself is not really a problem.
However, whenever I set the debug options I want:
debug flow basic
debug ike detail

and I type get debug, I can see both these things are being logged.
But this will only keep logging until the CLI gets disconnected.
If I log back in and type "get debug" nothing is being logged.

Is there a command to ensure it keep logging these things even after you log out of the command line interface?

Thanks,
UM
0
umeex
Asked:
umeex
2 Solutions
 
ujitnosCommented:
0
 
umeexAuthor Commented:
Thanks for this.
The document is actually very useful, but it still does not really help me solve the initial problem.
When I set the debugging options, the system only debugs until the CLI sessin gets terminated.
Is there any way to ensure the debugging just keeps going until I manually stop it or the buffer fills up?
Even if I need to terminate the CLI session?
0
 
ujitnosCommented:
Try "snoop", a kind of debug tool within Netscreen
http://kb.juniper.net/KB5411 
0
Managing Security & Risk at the Speed of Business

Gartner Research VP, Neil McDonald & AlgoSec CTO, Prof. Avishai Wool, discuss the business-driven approach to automated security policy management, its benefits and how to align security policy management with business processes to address today's security challenges.

 
arnoldCommented:
What is the point of running a debug session if you are not there to monitor it?

What you might be looking for is to increase the verbosity of data loged.  You should look at the logging settings on the netscreen. note that this could add to the load.
If you have your netscreen configured with syslog or snmptraps, that is the approach you might want to take.

http://mail.adeptech.com/pipermail/sidewinder/2009-February/002667.html
Check the IKE/RULE policy and check the audit level
Policy --> Rule Elements --> Services --> isakmp
etc.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Arnold is absolutely right. Loosing the debug switches on logout is a feature, because it shall prevent from accidently keeping debugging on when leaving an admin session. Debug switches only make sense when you are there to analyze them near real-time, and usually they are very demanding for the device, so you won't let that run too long.

Snoop might really be an alternative for a longer term, since it can use the buffer circularly, and so you have a descent time slot, with a detail level (by setting the capture size of each packet). Snoop'd packets can be transferred to your PC, and converted for analyzing via WireShark (or any PCap compatible analyzer).

Syslog and SNMPTraps are the way you monitor for long-term.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now