Configuration Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
When the backup master Configuration Server reconnects to the primary server after being frequently disconnected (because of expiry of the ADDP timeout) while loading history records, the backup server now loads and synchronizes the history data and opens the management port. Previously in this scenario, the backup Configuration Server did not load the history records, so they were not re-synchronized. (MFWK-19066, MFWK-18941)
Virtual Agent Group (VAG) members are now updated after a switchover between primary and backup Configuration Server. Previously in this scenario, VAG members were not updated and the contents of the group remained static. This problem first occurred in Configuration Server 220.127.116.11. (MFWK-19052)
The primary master Configuration Server no longer terminates when synchronizing data with the backup master Configuration Server shortly after the connection between them is restored. Previously in this scenario, the primary master Configuration Server tried to access memory beyond the allocated buffer space, causing the server to terminate unexpectedly. (MFWK-18955)
When using RADIUS external authentication, Configuration Server no longer terminates unexpectedly when the attributes of the user's Reply Message or the State attribute string contain more than 128 characters. Now, any additional characters (past the 128th character) are truncated by Configuration Server. (MFWK-18654)
Configuration Server now generates 21-22172 Master Configuration Server is fully synchronized in backup mode when it has properly synchronized the History Log with its HA peer server. Previously, this log event was not generated when LCA performed the switchover on a concurrent start. (MFWK-17669)
No special procedure is required to upgrade to release 18.104.22.168.