Juniper NETWORK AND SECURITY MANAGER 2010.4 - REV1, Руководство по установке, Страница: 199 / 244

5.
Edit the value (in megabytes) for the storageManager.minimumFreeSpace parameter.
This parameter indicates that 1000 MB of disk space need to be free if the GUI Server
starts to purge log records after crossing storageManager.threshold.
6.
Edit the value (in megabytes) for the storageManager.alert parameter. This parameter
sets the minimum threshold for available disk space at which the GUI Server sends
you an e-mail alert. By default, the GUI Server sends an e-mail alert when disk space
reaches 1000 MB.
NOTE: Use the Server Manager node in the UI to configure e-mail
notification. Refer to the Network and Security Manager Administration
Guide for more information.
7.
Configure the minimum i-node threshold by editing the storageManager.inodeThres
variable.
8.
Save the file.
9.
Restart the GUI Server.
Configuring Connection Timing
To configure connection timing with the managed devices in your network:
1.
Edit the Device Server configuration file (called devSvr.cfg).
2.
Edit the time value (in thousandths of a second) for the
devSvrDirectiveHandler.fastCli.timeout parameter to change the way the Device
Server controls connection timing with managed security devices running ScreenOS.
The devSvrDirectiveHandler.fastCli.timeout parameter determines the amount of
time that the Device Server waits for a CLI response from a security device running
ScreenOS before it disconnects the connection. By default, the Device Server waits
40 seconds before disconnecting the connection.
3.
Save the file.
4.
Restart the Device Server.
Setting Core File Naming on Solaris
If you are running the management system on Solaris, you can configure the file naming
used for core files to indicate the executable file and process ID generating the core file.
This procedure also ensures that Solaris does not overwrite the names of multiple core
files.
To set core file naming on Solaris:
1.
Log into the GUI Server computer as root.
2.
Run the following command:
coreadm -i core.%f.%p
3.
Restart the server.
177 Copyright © 2010, Juniper Networks, Inc.
Chapter 8: Maintaining NSM