Displaying Profiler Database Information (Nsm Procedure); Querying The Profiler Database (Nsm Procedure); Purging The Profiler Database (Nsm Procedure) - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING INTRUSION DETECTION PREVENTION DEVICES GUIDE REV 01 Manual

Configuring Intrusion Detection and Prevention Devices Guide

Displaying Profiler Database Information (NSM Procedure)

Purpose
Action
Related
Documentation

Querying the Profiler Database (NSM Procedure)

Purpose
Action
Related
Documentation

Purging the Profiler Database (NSM Procedure)

28
Viewing Profiler Logs (NSM Procedure) on page 20
Data discovered by Profiler is stored in a database located on the NSM GUI server. Use
the steps in this procedure to display information about the Profiler database.
To display Profiler database information:
In the NSM Navigation tree select Investigate > Security Monitor > Profiler.
1.
Click the Show DB Information icon in the upper right corner to view specific details
2.
about the Profiler database, including the database size.
Configuring Profiler Options (NSM Procedure) on page 13
Configuring Profiler Database Preferences (NSM Procedure) on page 26
Querying the Profiler Database (NSM Procedure) on page 28
Data discovered by Profiler is stored in a database located on the NSM GUI server. Use
the steps in this procedure to query the Profiler database.
To query records in the database:
Log into the NSM GUI server as the Postgres SQL user. By default, the Postgres SQL
1.
user is netscreen.
Navigate to the directory where the Profiler DB is located:
2.
Run any Postgres SQL command. For example, you can type the following command:
3.
./psql -d profilerDb
Configuring Profiler Database Preferences (NSM Procedure) on page 26
Configuring Profiler Options (NSM Procedure) on page 13
Displaying Profiler Database Information (NSM Procedure) on page 28
Purging the Profiler Database (NSM Procedure) on page 28
Data discovered by Profiler is stored in a database located on the NSM GUI server. When
the database reaches a maximum size (4 GB by default), it begins purging records (oldest
first) automatically. The Profiler stops purging records when it reaches a certain set
minimum size (3 GB by default).
Use the steps in this procedure to purge the Profiler database, if needed.
/usr/local/nsmpsql/bin
Copyright © 2010, Juniper Networks, Inc.
.