ExpressCluster X 3.1 for Linux Getting Started Guide - Nec
ExpressCluster X 3.1 for Linux Getting Started Guide - Nec
ExpressCluster X 3.1 for Linux Getting Started Guide - Nec
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 2 Using <strong>ExpressCluster</strong>Detectable and non-detectable errors by application monitoringMonitoring conditions: Termination of applications with errors, continuous resource errors, anddisconnection of a path to the network devices.Example of errors that can be monitored: Abnormal termination of an application Failure to access the shared disk (such as HBA 1 failure) Public LAN NIC problemExample of errors that cannot be monitored: Application stalling and resulting in error. <strong>ExpressCluster</strong> cannot monitor applicationstalling and error results. However, it is possible to per<strong>for</strong>m failover by creating a programthat monitors applications and terminates itself when an error is detected, starting theprogram using the exec resource, and monitoring application using the PID monitor resource.1 HBA is an abbreviation <strong>for</strong> host bus adapter. This adapter is not <strong>for</strong> the shared disk, but <strong>for</strong> the server.<strong>ExpressCluster</strong> X <strong>3.1</strong> <strong>for</strong> <strong>Linux</strong> <strong>Getting</strong> <strong>Started</strong> <strong>Guide</strong>34
Change language