ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

More documents

Recommendations

Info

Chapter 4 Latest version informationNumberVersion (indetail) Upgraded section CauseThe FTP monitor resource may The FTP monitor executes the next158 3.1.5-1/mistakenly detect a monitor error. command before receiving all3.0.0-1 to 3.1.4-1This problem occurs if the banner responses from the FTP server.message registered in the FTP server orthe message at the time of connection is along character string or spans multiplelines.An unnecessary message about a System A case in which resources are released159 3.1.5-1/Resource Agent background process may in a multi-thread process was not taken3.1.0-1 to 3.1.4-1be output in when a cluster stops. into consideration.This problem occurs if the cluster stops inan environment in which SystemResource Agent is used.If all groups are subject to recovery by a Whether to fail over all the groups was160 3.1.5-1/message receive monitor resource, not properly determined.3.1.0-1 to 3.1.4-1failover may not be performed when anerror is detected.This problem occurs if you use messagereceive monitor resources for linkagewith the server managementinfrastructure or A1080a/A1040a, andthere is a group that did not activate in alocal server.If the process to unmount the mirror disk OS mountpoint information was161 3.1.3-1/resource or hybrid disk resource times already removed even though the3.0.0-1 to 3.1.2-1out, the system may misidentify that the unmount process is still being executed.unmount process is successfullycompleted.This problem occurs if the mirror diskresource or hybrid disk resource unmountprocess takes longer than the unmounttimeout time.Activating/deactivating a volume The vgchange command might fail162 3.1.5-1/manager resource may fail.when the vgs command is executed3.0.0-1 to 3.1.4-1This problem may occur when LVM is while the vgchange command is beingselected as the volume manager type and executed.the vgs command is executed whileactivating/deactivating a volumemanager resource.The mail report function might fail to The domain name of the greeing163 3.1.5-1/send a mail.message retured by the SMTP server is3.0.0-1 to 3.1.4-1This problem occurs when a domain used as the domain of the HELO orname is not included in the greeting EHLO command.message of the destination SMTP server.When the configuration information is This occurred when the configuration164 3.1.7-1/uploaded using the clpcfctrl command, information including interconnect3.1.0-1 to 3.1.6-1an OS memory shortage error might settings having IPs not existing on theoccur although this is not the case. sever is uploaded.The result of virtual machine resource This occurred while virtual machine165 3.1.7-1/activation processing was reflected on the resources were used.3.1.0-1 to 3.1.6-1environment variable CLP_DISK to beused for EXEC resources.104ExpressCluster X 3.1 for Linux Getting Started Guide
System requirements for WebManager MobileNumberVersion (indetail) Upgraded section CauseSometimes recovery action upon monitor This occurred when recovery action by166 3.1.7-1/error could not be executed.another monitor resource on the same3.1.5-1 to 3.1.6-1server was tried for the group andresource for which group stop had beenexecuted as the final action uponmonitor error.In executing the clplogcc command, a log This occurred when a directory in a file167 3.1.7-1/file might not be saved in a directory system other than the ExpressCluster3.1.0-1 to 3.1.6-1specified by the -o option.installation path was specified by the -ooption in executing clplogcc -l.The following alert might be output to the This occurred when a server was168 3.1.7-1/WebManager.stopped and there was no failover3.1.5-1 to 3.1.6-1destination for the failover group thatTYPE:rc, ID:503was running on that server and whenA mismatch in the group failover-md manual failover was configured.status occurs between the servers.The following alert might be output to the This occurred when there were169 3.1.7-1/WebManager.3.1.5-1TYPE:rc, ID:503A mismatch in the group failover-mdstatus occurs between the servers.differences in the startup times betweenthe servers when the cluster started.In Config Mode of the WebManager, the This occurred when the recovery target170 3.1.7-1/final action setting might be changed at was changed on the recovery action tab3.1.0-1 to 3.1.6-1an unintended timing.of monitor resource properties.The same monitor resource might be This occurred on very rare occasions171 3.1.7-1/started redundantly, resulting in when a monitor resource set to Always3.1.0-1 to 3.1.6-1unnecessary recovery action being monitors and a monitor resource set toexecuted.Monitors while activated were startedsimultaneously when the cluster started.The following alerts might be output to This occurred when it took time to stop172 3.1.7-1/the WebManager.a failover group in stopping the cluster.3.1.5-1TYPE:rm, ID:9Detected an error in monitoring.( :TYPE:rm, ID:25Recovery will not be executed since therecoverytarget is not active.On the title line displayed when This occurred when clpmdstat --perf173 3.1.7-1/clpmdstat --perf was executed, "Cur", was executed.3.1.0-1 to 3.1.6-1which indicated the latest value, wasdisplayed in place of "Avg" in theaverage column.Section II Installing ExpressCluster105
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 54 and 55: Chapter 3 Installation requirements
Page 79 and 80: Chapter 4Latest version information
Page 81 and 82: System requirements for WebManager
Page 103: 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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?