| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Node Attribute
Node attribute can be identified from NodeAttributes view of MCCS console.
From the node management view of MCCS console, select node, then select the ‘Node Attributes’ tab located on right top of detailed information panel.
The values of gray colored are for read only. They just contain and show the information of node state. The values of white colored are configurable by user definition. Below is description of some of them.
[Figure] Node Attribute View
...
Attribute | Description | Type | Default | Edit | Note |
| BootMode | It is value that indicate whether auto-start or not 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 | ||
| IsolationTestAddress | 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
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.
...
| 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_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. |
...
Following is the process of the change of the node state of MCCS.
[Figure] MCCS Action step according to Node State
...
Heartbeat has the vital role of synchronizing the state and determining the failure state between nodes.
Therefore, when the system is being operated, it must be redundant to guarantee a state of being available for communication at all times.
Also, to determine the isolation of the network, one of the heartbeat networks must be established as a network available for communication with the service network or nodes other than the cluster node.
...
When all the heartbeat communication is disconnected for a certain amount of time, the node is declared to be in failure state.
The final decision on the discontinuance of heartbeat communication is made by the ICMP test.
When both nodes cannot communicate with each each other within a defined amount of time, MCCS define the state as split, isolation and remote node fault.
...
Before declaring the opposite node as a failure even when all the heartbeats are disconnected within a certain time period, MCCS check the local node is disconnected from the whole network.
If the node can communicate to authorized network points such as gateway or DNS server, the local node is not disconnected, and it can be concluded that the opposite node is in a failure state and will not try to recover.
It that is not the case, it can be considered as isolation state.
Since standby node considers local node has a failure while local is trying to recover the service, service on local node needs to be terminated as soon as possible.
...
| Code Block |
|---|
mcnode [-u userid -pw password] [-n nodename] [-a attribute] [-l license] [-p download_path] |
Options
| 옵션 | 설명 |
-h | 도움말을 출력합니다. |
| -u | 사용자 계정을 지정합니다. |
| -pw | 사용자 Password를 지정합니다. |
-n | 명령을 실행하기 위해 접근할 노드를 지정합니다. |
-a | [modify] 명령일 경우 변경할 속성과 속성값을 지정합니다. |
-p | 서포트 파일 다운 받을 경로를 지정합니다. path 지정 생략시 user.home으로 다운로드 됩니다. |
| -l | 지정한 노드의 입력할 라이선스 값을 지정합니다. |
...