...
Attribute | Description | Type | Default | Edit | Note |
BootMode | It is value that indicate whether auto-start or not to been started according to the bootMode value setting when MCCS service starts.. | BOOLEAN | X | ||
ExpirationDate | It shows license MAC of the node. | STRING | |||
HostID | It shows license MAC of the node. | STRING | X | ||
IsolationTestAddressIsolationTestAddresses | It enters the IP address to test Isolation. It is recommended the reliable IP address. | IP ADDRESS | O | ||
LicenseType | It shows license type of the node. | STRING | X | ||
NodeName | It indicated the name of the node. | NAME |
| X | |
NodeState | It indicated the state of the node. | STRING |
| X | |
PrimaryHB | It shows an IP address of the Primary Heartbeat defined in the MCCS server. | IP ADDRESS |
| X | |
PrimaryHBStatus | It indicates state of primary heartbeat | IP ADDRESS | X | ||
SecondaryHB | It shows an IP address of the Secondary Heartbeat defined in the MCCS server. | IP ADDRESS |
| X | |
SecondaryHBStatus | It indicates state of secondary heartbeat | IP ADDRESS | X | ||
StandAlone | It indicates whether standalone mode or not. | BOOLEAN | false | X |
...
MCCS connects nodes as one cluster through heartbeat connection.
Action of the cluster is decided by the state and role of the node, and node states are decided not only by the system state but also the state of heartbeat connection.
Following are node states for Cluster Mode.
Node states of the Cluster Mode
Node states of the Cluster Mode
...
State | Description |
---|---|
EXITED | This is a state where MCCS engine is terminated.. |
INITING | This is a state before configuring the heartbeat after starting the engine. This is initial state before both nodes communicate each other through heartbeat network and collect mutual status of node state after MCCS engine is started. This state is normally changed to the LOCAL_BUILD or REMOTE_BUILD state, but if there is a problem with the configuration or physical environment, it remains in the INITING state, or is automatically terminated to the EXITED state. |
LOCAL_BUILD | When every node in the cluster is in the INITING state, the node with the highest priority at establishing of heartbeat communication is changed to the LOCAL_BUILD state, and the node in this state forms a cluster database from the local configuration file(%MCCS$MCCS_HOME%\HOME/config\/main.json). Only one node within the cluster goes through this state to the RUNNING state, and other nodes undergo the REMOTE_BUILD state that receives information from that node. |
REMOTE_BUILD | When a node in the INITING state detects a node in the RUNNING state through heartbeat communication, it establishes by downloading the configuration |
RUNNING | This is the state when establishing a configuration database through the LOCAL_BUILD or REMOTE_BUILD is completed, and starts agents and group administrators of all the resources defined at this state. |
FAULTED | When all the heartbeats with the node in the RUNNING state are disconnected, the node is FAULTED. |
...
If all of the heartbeat communication is disconnected, both nodes cannot exchange the mutual state.
Service recovery and process are determined by whether the opposite node is declared as a failure, or simply in a state in which the communication paths between nodes are disconnected.
Split Brain
If If the interval of heartbeat network disconnections is greater than the limit set in the cluster attribute, you can suspect instability of the entire heartbeat network instead of node failures.
Thus, it is deemed that the heartbeat node status cannot be trusted and it does not detect system failures but maintains the current status.
When heartbeat communication is restored, the nodes in the clusters will restart the MCCS service and return to the running status.
If not, it will wait until heartbeat communication is restored in INITING state.
...
When a local node cannot communicate to opposite node within a defined timeout and it is not in an isolation state, local node will try to keep its state as RUNNING, and bring ONLINE the services which taken OFFLINE from remote node.
How to Change the Node Name
- In the web console, select the node management view and select the node to change the name for.
[Figure] Node Name Change Selected - Enter the node name to change.
[Figure] New Node Name Input - In the web console's node management view,
you can check the newly changed node name.
CLI Use(mcnode command)
It sends the node commands. You can command to inquire about or change the node attributes, enter the license or download the support file.
Info |
---|
When you install MCCS, the initial user account ID is set to 'admin' and the password is set to 'password'. |
Syntax
Code Block |
---|
mcnode [-u userid -pw password] [-n nodename] [-a attribute] [-l license] [-p download_path] |
...
Option | Description |
-h | Display Help. |
-u | Designate the user account ID. |
-pw | Create Enter user password. |
-n | Designate a node to be accessed to run the command. |
-a | If the [modify] command is used, set the attribute and the attribute values to change. |
-p | Designate the path for downloading the support file. If you do not enter the path, it will be downloaded to 'user.home'. |
-l | Enter the license value to be entered for the designated node. |
...
Code Block |
---|
mcnode -u admin -pw password -modify -n testNodeTestNode-1 -a IsolationTestAddressattribute attribute_value |
license
Enter the license for testNode-1.
Code Block |
---|
mcnode -u admin -pw password -license -n TestNode-1 [ -all ] license_value |
support
Download the support file of testNode-1 to /root/Desktop/mantech.
(If you enter -all, it will create the support file for all the nodes and then download them.)
Code Block |
---|
mcnode -u admin -pw password -supprot [-n TestNode-1 ([ -all) ] -p /root/Desktop/mantech |
...
Show the list of node attributes.
(If you enter nonamenode name, it will only display the attribute values for the node entered.)
Code Block |
---|
mcnode -u admin -pw password -list ([-n nodename)] |