Filter
Top Products
Table 17.3 Node Entry Settings
Setting Keyword Expected Values: Description
Managed server
name
NODE_NAME
Physical server
name
Physical server name that was set when
registering the managed server.
Note
Specify additional entries for any node (server) that may be added in the future (one entry per server).
- Interface Entries (without Redundancy)
The following table explains how to define each interface entry.
Keywords for interface entries should be appended with a number between 0 and 99.
Note
The number appended to each entry's keyword should start with 0 and increase incrementally.
Table 17.4 Interface Entry Settings (without Redundancy)
Setting Keyword Expected Values: Description
Interface name IF_NAME Interface name
Specify the interface name as displayed by
the operating system. (*)
Example
[Windows]
Local area connection 2
[Linux]
eth
X
(where
X
is an integer equal to or
greater than 0)
IP address IF_IPAD
IP address in
xxx.xxx.xxx.xxx
format
-
Subnet mask IF_MASK
Subnet mask in
xxx.xxx.xxx.xxx
format
-
* Note: As Windows allows interface names to be changed, ensure that the names defined here match those displayed in
Windows.
- Interface entries (with redundancy) [Linux]
The following table explains how to define each interface entry.
Keywords for interface entries should be appended with a number between 0 and 99.
This setting uses the "NIC switching mode (Physical IP address takeover function)" of the PRIMECLUSTER Global Link
Services product, which requires a virtual interface set with its own IP address.
Within a same node entry, it is possible to define interface entries both with and without redundancy settings as long as
interface names differ.
Note
The number appended to each entry's keyword (including both entries with and without redundancy settings) should start
with 0 and increase incrementally.
- 138 -