ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

System requirements for WebManager MobileNumber12131415161718192021222324Version (indetail) Upgraded section Cause3.0.2-1 When mdw was timed out or forcibly There was no timing to release the/3.0.0-1 to 3.0.1-1 killed, the OS resources were leaked. obtained semaphore.3.0.2-1 When it was specified that the initial When a user did not execute the/3.0.0-1 to 3.0.1-1 mirror construction was not executed, initial mirror constructionresynchronization did not become intentionally, the flag to guaranteeenabled until full synchronization was the consistency of the disk contentsperformed.was not established.3.0.2-1This occurred when returning to the/3.0.0-1 to 3.0.1-1 When a cluster name was changed in cluster name change screen afterthe Cluster Generation Wizard, the the cluster name was changed inname was reset to a default name. the Cluster Generation Wizard andthe next step was selected.3.0.2-1 the recovery action was not executed The process to decide whether to/3.0.0-1 to 3.0.1-1 even if a volmgrw monitor error was execute the recovery action was notdetected.correct.3.0.2-1 The timeout for the volmgr resource The formula to calculate the time out/3.0.0-1 to 3.0.1-1 could not be correctly specified. was not correct.3.0.2-1 When a keyword over 256 characters/3.0.0-1 to 3.0.1-1 was specified, linkage with external The size of the buffer to save themonitoring was not started even if the keyword was insufficient.mnw monitor was set.3.0.2-1The check process of shutdownWhen disabling shutdown monitoring,/3.0.0-1 to 3.0.1-1 monitoring was executed by theuser space monitoring could not beinitialization process of user spacestarted.monitoring.3.0.2-1 The timeout for shutdown monitoring The heartbeat timeout was specified/3.0.0-1 to 3.0.1-1 could not be changed.to use at any time.3.0.3-1 In config mode, non-numeric data There was an error in the design of/3.0.0-1 to 3.0.2-1 (alphabetic characters and symbols) the Builder input control.could be incorrectly entered for WaitTime When External MigrationOccurs for VM monitor resources.3.0.3-1 The method designed for applying a Because the server ID of the server/3.0.0-1 to 3.0.2-1 change in the server priority involved used to activate the groupsuspending and resuming the cluster resources was stored in the sharedand then restarting WebManager. memory, the information on thatHowever, it actually requires the server became inconsistent whenstopping and starting of the cluster the server ID was changed.and then restarting WebManager.3.0.3-1 When "0" was specified as the There was an error in the design of/3.0.0-1 to 3.0.2-1 timeout period for EXEC resources, the Builder input control.the activation of EXEC resourcesfailed and emergency shutdown wasperformed.3.0.3-1 In a specific environment, pressing The error was caused by a problem/3.0.0-1 to 3.0.2-1 the Add Server button in the Cluster with JRE.Generation Wizard of the Buildercaused an application error.3.0.3-1 When a hybrid configuration was There was a problem in the logic/3.0.0-1 to 3.0.2-1 used, the mirror agent sometimes used for searching server groups.failed to start.Section II Installing ExpressCluster87