ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

Chapter 4 Latest version informationCorrected informationModification has been performed on the following minor versions.NumberVersion (indetail) Upgraded section Cause1 3.0.1-1/3.0.0-1A problem that a cluster cannot start Error in the license managementup with VM license has been fixed. tableThe final action upon group resource2 3.0.2-1or monitor resource failure was/3.0.0-1 to 3.0.1-1displayed as a final action upon The terms have not been unifiedcluster service failure for Builder, and among the functions.a final action upon cluster daemonfailure for WebManager.3.0.2-1Specifying exclusive attributes from3In Builder, an exclusive attribute/3.0.0-1 to 3.0.1-1 the properties was not prohibited.could be specified from the virtual(In the case of the wizard, this hasmachine properties.been prohibited.)3.0.2-1 In an environment where XenServer4/3.0.0-1 to 3.0.1-1 could not be used, the VM monitorA NULL pointer was issued in theabnormally terminated (core dump)VM monitor initialization.when the XenServer VM monitor wasset up.3.0.2-1 When connecting to WebManager by5WebManager was not taken into/3.0.0-1 to 3.0.1-1 using FIP, and adding the settings,consideration for the process tothe notes on connecting by usingevaluate connection using FIP.FIPs were not displayed.3.0.2-1Script execution and group failover6/3.0.0-1 to 3.0.1-1 When using the clprexec were not taken into consideration forcommand, Unknown request was the process to create a characteroutput to syslog and the alert log. string output to syslog and the alertlog.3.0.2-1Since the NP status was not7891011In WebManager, the pingnp status of/3.0.0-1 to 3.0.1-1 initialized, it is assumed as anthe stopped server was displayed asnormal.undefined value if no informationwas obtained.3.0.2-1 When changing the settings on theThere was no consideration for the/3.0.0-1 to 3.0.1-1 monitor resource properties dialogdecision process.box, Apply could not be clicked.3.0.2-1 On the Builder Interconnect Setting/3.0.0-1 to 3.0.1-1 window, when attempting to deleteThere was no consideration forinter connect settings by selecting allselecting multiple interconnects.settings, only some settings weredeleted.3.0.2-1The timing to release the MutexThe system abnormally terminated/3.0.0-1 to 3.0.1-1 resource, which was used by thewhen the WebManager service wasrealtime update thread, was notstopped.correct.3.0.2-1 The alert synchronization service/3.0.0-1 to 3.0.1-1 abnormally terminated when There was an error in the process torestarting the server after changing its obtain the server list.name.86ExpressCluster X 3.1 for Linux Getting Started Guide