Use the same steps used to define the primary nodes, but supply information specific to the secondary node.
Select Tasks from fstask
Select Nodes from the pull-down menu. and fill in the following fields:
Field |
Sample Values |
Description |
|---|---|---|
Hostname |
mizzen |
The value returned by hostname(1). |
Logical Name |
mizzen |
The same value as Hostname. |
Network |
130.215.121.114 |
The IP address or the hostname of the private network. |
Messages to Accept |
Heartbeat and Control |
Set to enabled after serial reset cables are connected to this node. |
Select Add.
Field |
Sample values |
Description |
|---|---|---|
Network |
10.22.110.133 |
Network address |
Message to Accept |
Heartbeat and Control |
Set to enabled after serial reset cables are connected to this node. |
Select Add
Field |
Sample value |
Description |
|---|---|---|
Node ID |
2 |
(Optional) An integer in the range 1– 32767 that is unique among the nodes in the pool. If you do not specify a number, FailSafe calculates an ID for you. |
Partition ID |
Unset |
(Optional) An integer between 1–32767 that is unique among the nodes in the pool. If you do not specify a number, FailSafe calculates an ID for you. |
Set Reset Parameters |
Check |
A special hardware port on a node that provides a way to power-cycle or reset the node remote. |
Select Next.
Select the Set Reset Parameters box. The following fields are enabled:
Field |
Sample value |
Description |
|---|---|---|
This Node |
N/A |
Information line |
Port Type |
MSC |
Depending on the system controller, the values be L1, L2, MSC, or MMSC. |
Port Password |
Unset |
The system controller password for privileged commands, not the node’s root password. |
Temporarily Disable Port |
Unchecked |
If checked, FailSafe cannot reset the node. |
Owner (name of node that sends reset command) |
N/A |
Information line |
Logical Name |
spinnaker |
Name of the node that sends the remote reset command. |
TTY Device |
/dev/ttyd2 |
Name of the terminal port (TTY) on the owner node to which the system controller is connected. |
From the command line, enter the following:
cluster_mgr –f sec_node_def
