Solution Control Server 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
Secure Network Logging Deployment Procedure
This release includes only resolved issues.
This release contains the following resolved issues:
SCS now deletes the user's object when the user is disconnected from SCS to prevent corrupting the memory and allocating more memory at reconnection. Then it generates the alarm for log event 10401, if one is configured. Previously in this scenario, SCS did not delete the object, generated the alarm if configured, and then terminated unexpectedly. (MFWK-17951)
The mlcmd help file now indicates that the minimum value for the -timeout parameter is 10 seconds; any value below that is ignored and the default value (60 seconds) is used instead. This was not documented previously. (MFWK-17922)
A simple TLS connection can now be established between Local Control Agent (LCA) and Solution Control Server (SCS), in auto upgrade mode, on Linux, with the following information provided on the SCS client side:
- On Windows, no certificate information is provided.
- On Linux, only the trusted-ca is provided.
Previously, you had to provide the certificate information on Windows and certificate, certificate key, and trusted-ca on Linux for the SCS client side, even for a simple TLS connection.
No special procedure is required to upgrade to release 220.127.116.11.