This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
storage:svc_ip_quorum [2022/02/26 15:04] manu |
storage:svc_ip_quorum [2025/03/06 13:40] (current) manu [SETUP SAN/SVC QUORUM IP on Windows] |
||
---|---|---|---|
Line 17: | Line 17: | ||
You will download a package called **ip_quorum.jar** | You will download a package called **ip_quorum.jar** | ||
+ | |||
+ | |||
+ | **Port 1260** can be used by the IP quorum application to communicate from the server to all nodes or node canisters. The maximum round-trip delay must not exceed 80ms (milliseconds), which means 40ms in each direction. | ||
+ | |||
+ | ===== Cluster behavior, quorum settings ===== | ||
+ | |||
+ | <cli prompt='>'> | ||
+ | > chsystem -quorummode standard | preferred | winner | ||
+ | </cli> | ||
+ | |||
+ | (Optional) Specifies the mode that quorum uses for tie-breaking. The valid values are standard (default), preferred, or winner. | ||
+ | * **quorumsite site_id | site_name** | ||
+ | (Required) Specifies the site ID or name that quorum uses for tie-breaking when -quorummode is set to preferred or winner. (give 3 seconds for prefer site to lock quorum) | ||
+ | * quorumlease short | long | ||
+ | (Optional) Specifies the mode that quorum uses for tie-breaking. The valid values are short (default) or long. | ||
+ | |||
+ | <color #ed1c24>Who wins if standard or winner is selected ? Depends on IP network to lock on IP quorum, depends on latency...</color> | ||
===== On linux ===== | ===== On linux ===== | ||
Line 107: | Line 124: | ||
# Error Type = none # System Version = 8.2.1.10 (build 147.19.2003130616000) | # Error Type = none # System Version = 8.2.1.10 (build 147.19.2003130616000) | ||
</code> | </code> | ||
+ | |||
+ | ===== On Windows ===== | ||
+ | |||
+ | You have to create a service | ||
+ | |||
+ | ====== SVC IP quorum ====== | ||
+ | |||
+ | **Each time the SVC is upgarded you have to refresh the jar file, download it directly from SVC interface** | ||
+ | |||
+ | Once started, the IP quorum will automaticaly register on SVC | ||
+ | |||
+ | The IP quorum is a jar file that have to be run as a service (persistent), so you can install it on Windows, Linux, AIX... | ||
+ | |||
+ | https://github.com/winsw/winsw | ||
+ | |||
+ | |||
+ | ===== SETUP SAN/SVC QUORUM IP on Windows ===== | ||
+ | |||
+ | **Service creation** | ||
+ | |||
+ | Friday 4 February 2022 | ||
+ | 08:19 | ||
+ | SETUP STEPS: | ||
+ | |||
+ | 1. Install Java stack on Server JRE 8u111x64 | ||
+ | |||
+ | 2. Run install.bat in AdFrom ministrator CMD | ||
+ | |||
+ | a. Installation takes place in c:\program files\Java | ||
+ | |||
+ | b. Executable are below c:\program files\java\jre8\bin | ||
+ | |||
+ | 3. Using c:\program files\java as execution folder for the san quorum IP | ||
+ | |||
+ | a. Copy the latest ip_quorum.jar in that location | ||
+ | |||
+ | b. Download the service wrapper from https://repo.jenkins-ci.org/releases/com/sun/winsw/winsw/2.9.0/ (winsw-2.9.0-bin.exe (Project page https://github.com/winsw/winsw) | ||
+ | |||
+ | c. Copy the executable inside the same folder as the ip_quorum.jar | ||
+ | |||
+ | 4. Preparation for creation of the service: | ||
+ | |||
+ | a. Rename the winsw-2.9.0-bin.exe to the same name as the desired service name in our case to: sanquorum.exe | ||
+ | |||
+ | b. Create a wrapper xml for the service which needs to be names sanquorum.xml | ||
+ | |||
+ | c. Content is described on the github site. | ||
+ | |||
+ | d. Here is our content: | ||
+ | <code> | ||
+ | <service> | ||
+ | <id>sanquorum</id> | ||
+ | <name>SANQUORUM</name> | ||
+ | <description>This service runs the SAN Quorum Java script.</description> | ||
+ | <env name="SANQUORUM_HOME" value="%BASE%"/> | ||
+ | <executable>"%BASE%/jre8/bin/java"</executable> | ||
+ | <arguments>-jar "%BASE%\ip_quorum.jar"</arguments> | ||
+ | <log mode="roll"></log> | ||
+ | </service> | ||
+ | </code> | ||
+ | |||
+ | 5. Install the service: | ||
+ | |||
+ | a. From an ADMINISTRATOR cmd navigate to c:\program files\java | ||
+ | |||
+ | b. Run "sanquorum.exe install sanquorum.xml" | ||
+ | |||
+ | c. The service is then created | ||
+ | |||
+ | 6. Start the service: | ||
+ | |||
+ | a. Run "sanquorum.exe start sanquorum.xml or got to the services console on the server and start the service | ||
+ | |||
+ | 7. Check status: | ||
+ | |||
+ | a. Look into the services console or run sanquorum.exe status mysanquorum.xml | ||
+ | |||
+ | b. There are also various which are created once the service connects properly to the svc/san in the same Java folder | ||
+ | |||
+ |