ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

More documents

Recommendations

Info

Chapter 4 Latest version informationNumber2526272829Version (indetail) Upgraded section Cause3.0.3-1 When "0" was specified for the/3.0.0-1 to 3.0.2-1 Server Sync Wait Time, the mainprocess of the cluster sometimesfailed to start.3.0.3-1 When an attempt was made to/3.0.0-1 to 3.0.2-1 perform failover between absoluteexclusion groups upon the group status.occurrence of multiple and concurrentmonitor errors, both systems weresometimes activated.When "0" (minutes) was specifiedfor the Server Sync Wait Time, thevalue of the startup wait timeoutbecame identical to that of the HBtransmission start timeout.Therefore, the startup waitprocessing was not performedappropriately because of the timingof the processing.There was an error in the design ofthe value that was returned as the3.0.3-1 The setting for forced FIP activation The setting was overwritten with/3.0.0-1 to 3.0.2-1 was ignored.another setting in theimplementation.3.0.3-1 The units of the time values to be The output conversion method was/3.0.0-1 to 3.0.2-1 displayed in the alert (syslog) for incorrect.delay warning in the user spacemonitor resources were incorrect,and the values to be displayed inunits of tick count were displayed inunits of seconds.3.0.3-1 When the size of an alert message The size of the alert message buffer/3.0.0-1 to 3.0.2-1 exceeded 512 bytes, the alert was insufficient.daemon terminated abnormally.8830 3.0.3-1/ 3.0.2-1313233343.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-1WebManager could not be normally When terminating WebManager,terminated by selecting Exit from the the termination process of ConfigFile menu.Mode (Builder) is inadequate.Uploading is unavailable if the cluster When checking processes whilehas been suspended and a uploading, a cluster configurationtemporary suspension of a monitored file only judged whether the statusresource modified a necessary of monitor resources wasconfigurationsuspended.Sometimes unnecessary logs were After the failover destination serveroutput when an attempt was made to was decided in the first monitor errorperform failover between absolute processing, in the next monitor errorexclusion groups upon the processing, a different server wasoccurrence of multiple and concurrent decided for the failover destinationmonitor errors.server because it was determinedthat absolute exclusion groups wererunning on that server.When waiting to start monitoring a The processing for the monitor startresident monitor resource, the wait time was invalid.timeout time rather than the start waittime is referenced.An error occurred when collecting There were faults in the processinglogs, delivering settings information, that determines whether the actionor during other activities, but the was successful or nor.process appears to have terminatednormally.ExpressCluster X 3.1 for Linux Getting Started Guide
System requirements for WebManager MobileNumber3536373839404142434445Version (indetail) Upgraded section Cause3.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-1When adding a server to a mirror When confirming settings whileenvironment, suspending the cluster adding a server, it was not checkedand mirror agent is required to apply whether mirror disk connect hasthe new settings, but been set.suspend/resume is displayed.When a standby mirror agent is A buffer is released if receiving datasuspended during mirror recovery, failed, but a NULL pointer wasretrieving the recovery data may fail, issued when trying to receive thegenerating OOPS.next data.OOPS occurred sometimes in the Mirror driver functions whichdriver termination processing when process the completion notificationthe standby server mirror agent was for processing writing to datastopped during mirror recovery. partitions do not exist in the memorywhen rmmod mirror drivers are nolonger present after a request towrite mirror recovery data to a datapartition.The OS sometimes freezes when the Interruptible sleep occurred whileactive server mirror agent is stopped waiting for the recovery data read toduring mirror recoveryfinish, that sleep was interruptedduring shutdown, and the CPUusage for the thread waiting for readto finish increased.Multiple syslog messages may mix The functions for mirror driverand be output from the mirror driver syslog output uses the same bufferso that the same message is output without exclusion.twice at times such as servershutdown when mirror driver syslogoutput frequency is high.When the IP address for integrated The names of previous setting itemsWebManager was not specified, error were not updated.messages output due to failures toconnect to clusters were invalid.Sometimes core dump occurred while Illegal memory access occurredstopping a cluster service when max when a log was output after logreboot count limitation was set. library termination processingduring termination processing.When a destination server was down No failover policy check processwhile moving a group, sometimes the existed in the recovery processinggroup was moved to a server which associated with the server beingwas not included in the failover policy. down at the destination.Server down notification settings Cluster configuration informationwere changed and uploaded, but the was not reloaded upon termination.changes were not applied.A minor memory leak occurred when Thread information was notperforming a group or resource discarded after the threadoperation.terminated.When a script execution process Sometimes waitpid() wastimes out before the final operation executed before a process wasruns and is force killed, sometimes a terminated by SIGKILL.zombie process was generated.Section II Installing ExpressCluster89
Page 1 and 2:
ExpressCluster ® X 3.1 for LinuxGe
Page 3:
© Copyright NEC Corporation 2011.
Page 6 and 7:
Section II Installing ExpressCluste
Page 8 and 9:
Shutdown and reboot of individual s
Page 10 and 11:
ExpressCluster X Documentation SetT
Page 12 and 13:
Contacting NECFor the latest produc
Page 15 and 16:
Chapter 1What is a cluster system?T
Page 17 and 18:
High Availability (HA) clusterShare
Page 19:
High Availability (HA) clusterData
Page 22 and 23:
Chapter 1 What is a cluster system?
Page 24 and 25:
Page 26 and 27:
Page 29 and 30:
Chapter 2Using ExpressClusterThis c
Page 31 and 32:
Software configuration of ExpressCl
Page 33 and 34:
Software configuration of ExpressCl
Page 35 and 36:
Network partition resolutionNetwork
Page 37 and 38: Failover mechanismFailover resource
Page 39 and 40: Failover mechanismDifferent Applica
Page 41 and 42: Failover mechanismHardware configur
Page 43 and 44: Failover mechanismWhat is cluster o
Page 45 and 46: What is a resource?NAS resource (na
Page 47 and 48: What is a resource?Websphere monito
Page 49: Section IIInstallingExpressClusterT
Page 52 and 53: Chapter 3 Installation requirements
Page 79 and 80: Chapter 4Latest version information
Page 81 and 82: System requirements for WebManager
Page 87: System requirements for WebManager
Page 107 and 108: Chapter 5Notes and RestrictionsThis
Page 109 and 110: Designing a system configurationHar
Page 111 and 112: Designing a system configurationHar
Page 113 and 114: Designing a system configurationNet
Page 115 and 116: Designing a system configuration4.
Page 117 and 118: Designing a system configurationThe
Page 119 and 120: Installing operating systemIt is po
Page 121 and 122: Installing operating systemsoftdogT
Page 123 and 124: Before installing ExpressClusterSer
Page 125 and 126: Before installing ExpressClusterCha
Page 127 and 128: Before installing ExpressClusterUse
Page 129 and 130: Notes when creating ExpressCluster
Page 137 and 138: After start operating ExpressCluste
Page 139 and 140:
After start operating ExpressCluste
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151:
Updating ExpressClusterUpdating Exp
Page 154 and 155:
Chapter 6 Upgrading ExpressClusterH
Page 157:
Appendix• Appendix A Glossary•
Page 160 and 161:
Appendix A GlossaryNodeHeartbeatPub
Page 162:
Appendix B Indexmonitorable and non
show all

ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

Create successful ePaper yourself

Delete template?

Save as template?