|
Home > |
|---|
As a general rule, do not adjust timeout settings (either via the interface or in config files) unless instructed to do so by SafeNet Customer support.
Changing some settings can appear to improve performance until a situation is encountered where a process does not have time to complete due to a shortened timeout value.
Making timeouts too long will usually not cause errors, but can cause apparent performance degradation in some situations (HA).
Default settings have been chosen with some care, and should not be modified without good reason and full knowledge of the consequences.
If adjusting the configuration files for any reason:
CAUTION: Never insert TAB characters into the chrystoki.ini
(Windows) or crystoki.conf (UNIX) file.
However, with the above said...
One timeout value that might require change is the ReceiveTimeout value in the "LunaSA Client" section of the configuration file. This timeout value is the period that the SafeNet Network HSM client will wait for a response from the SafeNet Network HSM before determining that the appliance is off-line. The default value of 20 seconds provides a worst-case scenario over a larger WAN, but may be inappropriate for some SafeNet Network HSM deployments (such as SafeNet Enterprise HSMs in an HA configuration) where a quicker determination of the health of the SafeNet Network HSM system is required. This value can be set in the SafeNet Network HSM configuration file as follows:
[LunaSA Client]
:
ReceiveTimeout=<value in milliseconds> //default is 20000 milliseconds
:
LunaSA Client = {:
ReceiveTimeout=<value in milliseconds>;
:
}