8.5.100.21
Configuration Server 8.5.x Release Notes
| Release Date
|
Release Type
|
Restrictions
|
AIX
|
Linux
|
Solaris
|
Windows
|
| 08/05/16
|
General
|
|
X
|
X
|
X
|
X
|
What's New
This release contains the following new feature or enhancements:
- Improved migration of HA Configuration Servers: You can now allow an upgraded version of Configuration Server to run alongside its HA partner that is not upgraded, for a brief period of time. This provides for a more streamlined migration procedure, with less downtime for clients.
As part of this new functionality, the following new Configuration Server Log Events are used to track the procedure:
- 21-21270 [+] show details
| Level
|
Standard
|
| Text
|
Configuration Server ready to accept client connections.
|
| Attributes
|
None
|
| Description
|
Reports that Configuration Server has completed initialization/switchover and opened its ports for clients. There still might be initialization steps to complete if event 21-21271 is not generated immediately after this message.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- 21-21271 [+] show details
| Level
|
Standard
|
| Text
|
Master Configuration Server is fully operational in primary mode
|
| Attributes
|
None
|
| Description
|
Reports that Configuration Server is fully initialized, and is in fully writable primary master server mode for the Configuration Database.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- 21-21272
[+] show details
| Level
|
Standard
|
| Text
|
Master Configuration Server is fully synchronized in backup mode
|
| Attributes
|
None
|
| Description
|
Reports that Configuration Server is fully initialized as the backup server of the currently running primary server. You can only switch over this server to primary mode after this message is generated.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- 21-21273
[+] show details
| Level
|
Standard
|
| Text
|
Proxy Configuration Server is fully synchronized with master server
|
| Attributes
|
None
|
| Description
|
Reports that Configuration Server in proxy mode is fully operational. If server is in primary mode, it is confirmed with this message. If server is in backup mode, you are free to switch over to primary mode at any time after this message is generated.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- 21-25300
[+] show details
| Level
|
Standard
|
| Text
|
Backup Server ignored because server is starting in upgrade mode [1]
|
| Attributes
|
[1]
Type of upgrade mode. Currently, only one upgrade mode is available: 1 (simple).
|
| Description
|
The master Configuration Server is in upgrade mode, and is starting in backup mode. The backup Configuration Server will switch to primary mode and will be ignored by the primary Configuration Server until the upgrade operation is completed.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- 21-25301
[+] show details
| Level
|
Standard
|
| Text
|
Configuration Server entered upgrade mode. Backup Server ignored because of incompatible schema [<schema>]
|
| Attributes
|
<schema>
Configuration Database schema
|
| Description
|
The master Configuration Server has detected an older primary Configuration Server and is initializing as the primary server. The older primary Configuration Server will switch over to backup mode and be ignored by the newer primary Configuration Server until the upgrade operation is completed.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- 21-25302
[+] show details
| Level
|
Standard
|
| Text
|
Configuration Server ignored switchover request because another upgrade/switchover already in progress
|
| Attributes
|
None
|
| Description
|
Reports Configuration Server ignored a switchover request from Solution Control Server, most likely because Configuration Server is in upgrade mode. During upgrade, Solution Control Server detects the presence of two primary Configuration Servers and tries to force the new server (in upgrade mode) into backup mode, but the new instance refuses these requests and continues to initialize. This is normal situation during upgrade. You might observe this log event reported several times by Configuration Server in upgrade mode; this is not considered an error in this situation.
|
| Alarm Advisory
|
None
|
| Action
|
Take the appropriate action according to step 7 of Upgrading an HA Pair of Configuration Servers.
|
- Support for IBM DB2 10.5 database. See the Supported Operating Environment: Framework page for more detailed information and a list of all supported databases.
- Support for the VMware ESXi 6 virtualization environment. See the Supported Operating Environment: Framework page for more detailed information and a list of all supported virtual machines.
Resolved Issues
This release contains the following resolved issue:
Configuration Server no longer attempts to store the DBMS access password, as read from the startup configuration file, back into the Configuration Database after successfully connecting to the database. Previously, the Configuration Server Application object sometimes attempted to populate its own password option with that value. If the password had already been encrypted in the configuration file, Configuration Server sometimes failed to encrypt it again, logged ERROR: invalid byte sequence for encoding "UTF8", and remained in Read Only mode until it was restarted. (MFWK-17339)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.100.21.
Supported Languages
See Release 8.5.1 Translation Support.
