Juniper NETWORK AND SECURITY MANAGER 2010.4 - REV1, Installation Manual

Page: 227 / 244

Table 29: Audit Log Details
Audit Log Detail ON Audit Log Detail OFF Operation
40 KB 408 bytes Update Device 10K
60 KB 408 bytes Update Device 30K
240 KB 456 bytes Update Device 300K
5 KB 6K Add Device
180 bytes 540 bytes Login in/out
.01 MB 144 bytes Save Policy 25 rules
0.5 MB 192 bytes Save Policy 100 rules
0.75 MB 1536 bytes Save Policy 250 rules
5 MB 3072 bytes Save Policy 1000 rules
15 MB 6144 bytes Save Policy 5000 rules
For example, consider a system with 100 devices, with 10 KB configuration size per device,
and 1000 rules, and this system has 100 device updates and 5 policies saves.
• With detailed audit logging enabled, the audit log will use:
100 * 40 KB + 5 * 5 MB = 29 MB of disk space
•
With the audit log details turned off, the audit log uses only:
100 * 408 bytes+ 5 * 1 KB = 45 KB of disk space.
The GUI Server also requires 2 GB for the database transaction log.
Error Log
The /var/netscreen/GuiSvr/errorLog directory keeps error log files ( guidaemon.0 ). It stores
up to 25 files before the oldest log files are overwritten. Each day's file may be up to 5
MB in size. Based on these default settings, error logs can consume up to 125 MB (or 250
MB if the GUI Server and the Device Server are on the same server).
Device Configuration Database
The size of the Device Configuration database depends on the number of devices and
types of configuration used. For every 1 MB of aggregate device configuration, NSM needs
up to 200 MB of disk space.
For example, 100 devices with 10 KB configuration may need:
(10 KB * 100) * 200 = 200 MB of disk space.
205 Copyright © 2010, Juniper Networks, Inc.
Appendix B: Hardware Recommendations