Purging The Database; Recommended Profiler Options - Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1 Administration Manual

Network and Security Manager Administration Guide
Table 88: Detailed Network Information Data (continued)
Column Description
Peers Details about how the selected host IP communicates with other hosts,
including:
Source IP address of peer traffic
Destination IP of peer traffic
Hits (number of times the source IP communicated with the destination
IP)
First Access date and time that IDP first recorded the peer traffic
Last Access date and time that IDP last recorded the peer traffic
If the source IP is the selected interface, you can use the destination IP
address to identify all the hosts that the interface sent traffic to, both
internal and external, as well as the number of times traffic was sent.
Summary Lists all the details of the other View box selections in HTML format.

Recommended Profiler Options

716

Purging the Database

When the Profiler DB reaches a maximum size (4 GB by default), it begins purging records
(oldest first) automatically. The Profiler DB stops purging records when it reaches a
certain set minimum size (3 GB by default). You can use the Profiler settings in the Tools
preferences menu to change these parameters.
To manually purge the Profiler DB of all records, click Clear All DB. This operation can
take up to one minute. During this time, a message appears on all other connected UIs
indicating that a Clear All DB operation is in progress. After the data clears, you can click
on the Refresh icon to get new data.
NOTE: The Clear All DB option is not supported for Application Profiler views. Application
Profiler data is purged every 1–24 hours, depending on the value configured for the AVT
View Settings from Preferences >Profiler Settings in the Tools menu.
NOTE: NSM supports purging all records for the entire Profiler DB (all subdomains) but
does not support purging records for specific subdomains. Consequently, an IDP
administrator cannot delete Profiler DB records for a subdomain. Only the NSM super
administrator can delete records for the Profiler DB, and all records for all the
subdomains are purged.
The following are recommended for using the Profiler:
Configuring a Network Baseline on page 717
Keeping Your Network Current on page 717
Proactively Updating Your Network on page 718
Copyright © 2010, Juniper Networks, Inc.