ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

More documents

Recommendations

Info

Chapter 5 Notes and RestrictionsService startup timeAs long as the system shutdown is executed by WebManger or clpstdn command, there isno problem even if the services is terminated in the wrong order. But, any other problem maynot be happened by wrong order termination.ExpressCluster services might take a while to start up, depending on the wait processing at startup. clusterpro_evtServers other than the master server wait up to two minutes for configuration data to bedownloaded from the master server. Downloading usually finishes within several seconds ifthe master server is already operating. The master server does not have this wait process. clusterpro_trnThere is no wait process. This process usually finishes within several seconds. clusterpro_mdThis service starts up only when the mirror or hybrid disk resources exist. The system waitsup to one minute for the mirror agent to normally start up. This process usually finisheswithin several seconds. clusterproAlthough there is no wait process, ExpressCluster might take several tens of seconds to startup. This process usually finishes within several seconds. clusterpro_webmgrThere is no wait process. This process usually finishes within several seconds. clusterpro_alertsyncThere is no wait process. This process usually finishes within several seconds.In addition, the system waits for cluster activation synchronization after the ExpressClusterdaemon is started. By default, this wait time is five minutes.For details, see Chapter 10, “The system maintenance information” in the Reference Guide.Scripts in EXEC resourcesEXEC resource scripts of group resources stored in the following location./opt/nec/clusterpro/scripts/group-name/resource-name/The following cases, old EXEC resource scripts are not deleted automatically.• When the EXEC resource is deleted or renamed• When a group that belongs to the EXEC resource is deleted or renamedOld EXEC resource scripts can be deleted when unnecessary.Monitor resources that monitoring timing is “Active”When monitor resources that monitoring timing is “Active” have suspended and resumed, thefollowing restriction apply: In case stopping target resource after suspending monitor resource, monitor resourcebecomes suspended. As a result, monitoring restart cannot be executed.In case stopping or starting target resource after suspending monitor resource, monitoring bymonitor resource starts when target resource starts.146ExpressCluster X 3.1 for Linux Getting Started Guide
After start operating ExpressClusterNotes on the WebManagerThe information displayed on the WebManager does not necessarily show the latest status. Ifyou want to get the latest information, click the Reload button.If the problems such as server shutdown occur while the WebManager is getting theinformation, acquiring information may fail and a part of object may not be displayedcorrectly. Wait for the next automatic update or click the Reload button to reacquire thelatest information.When using a browser on Linux, a dialog box may be displayed behind the window managersdepending on the combination of the managers. Change the window by pressing the ALT +TAB keys.Collecting logs of ExpressCluster cannot be executed from two or more WebManagersimultaneously.If the WebManager is operated in the state that it cannot communicate with the connectiondestination, it may take a while until the control returns.If you move the cursor out of the browser in the state that the mouse pointer is displayed as awristwatch or hourglass, the cursor may be back to an arrow.When going through the proxy server, make the settings for the proxy server be able to relaythe port number of the WebManager.When going through the reverse proxy server, the WebManager will not operate properly.When updating ExpressCluster, close all running browsers. Clear the Java cache (notbrowser cache) and open browsers.When updating Java, close all running browsers. Clear the Java cache (not browser cache)and open browsersNotes on the Builder (Config mode of Cluster Manager)ExpressCluster does not have the compatibility of the cluster configuration data with thefollowing products.• Builder for Linux other than ExpressCluster X 3.1 for LinuxCluster configuration data created using a later version of this product cannot be used withthis product.Cluster configuration data of ExpressCluster X1.0/2.0/2.1/3.0/3.1 for Linux can be used withthis product.You can use such data by clicking Import from the File menu in the Builder.Closing the Web browser (by clicking Exit from the menu), the dialog box to confirm to saveis displayed.When you continue to edit, click the Cancel button.Section II Installing ExpressCluster147
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:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 79 and 80:
Chapter 4Latest version information
Page 81 and 82:
System requirements for WebManager
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96: 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 145: 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?