ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

System requirements for WebManager MobileNumber111112113114115116117Version (indetail) Upgraded section CauseIt took extra five seconds to perform a A final retry entered in unnecessaryfinal retry upon a group resource sleep state (five seconds) when anactivation/deactivation error. activation or deactivation retry was3.1.3-1/This occurred upon a group resource performed upon a group resource3.0.0-1 to 3.1.1-1activation/deactivation error when it activation/deactivation error.was set to retry activate or deactivatethe group resource.When a network used by mirror disk When an attempt was made to bindconnect was brought down by a a socket in a sending process bycommand such as ifdown, mirror ICMP, the socket was connectedrecovery might be executed without checking the return value.3.1.3-1/ repeatedly.3.0.0-1 to 3.1.1-1 This occurred when there was a pathto a remote server other than mirrorconnect and a network used by mirrordisk connect was brought down byifdown.A message receive monitor error A monitor process was notmight be detected when the cluster generated when the cluster waswas being stopped.being stopped, and the stopping3.1.3-1/This might occur when a message process was always assumed to be3.0.0-1 to 3.1.1-1receive monitor was monitored when completed successfully. In such athe cluster was being stopped. case, it was checked whether amonitor process existed or not.Changes were supposed to be When the Forced Stop andreflected to the forced stop function Chassis Identify are disabledsettings by uploading, but could not (OFF), the setting information wasbe reflected.not acquired in the process to3.1.3-1/This occurred when Forced Stop acquire.3.0.0-1 to 3.1.1-1was changed to enable (ON) after thecluster was started with Forced Stopand Chassis Identify disabled(OFF).When collecting logs, a rotated syslog The name of the rotated messagesfile might not be collected.file did not comply with the changed3.1.3-1/This occurred when logs were naming rule.3.0.2-1 to 3.1.1-1collected in RHEL6 or laterenvironments.Stopping the cluster might not be A termination process was missingcompleted.in the process to check a thread3.1.3-1/This might infrequently occur when a termination request.3.0.0-1 to 3.1.1-1message receive monitor resourcewas set.33 or more destinations to which a The control processing of the AddSNMP trap was sent could be set. button on the SNMP trap sending3.1.3-1/ This occurred when the SNMP trap destination settings screen was3.1.0-1 to 3.1.1-1 sending destination settings screen inadequate.was started again after 32destinations had been set.Section II Installing ExpressCluster97