HP StorageWorks Clustered File System 3.1.1 for Linux Installation Guide (May 2006)

Chapter 4: Install HP Clustered File System 28
2. Remote Management Controller ID. Specify how Clustered File
System should identify the Remote Management Controller iLO
associated with each server. Use one of the following methods.
– Select “Cluster-wide Pattern” and then specify the common
naming scheme that you are using for the Remote Management
Controllers (either a hostname suffix or an IP address delta).
– Enter the hostname or IP address for the Remote Management
Controller associated with this cluster server. (If you unchecked
“Vendor and type selection apply to all controllers for the cluster,”
you will need to use this method.)
Hostname Suffix. Specify the common suffix to append to each server
name to determine the associated Remote Management Controller
name. For example, if your server names are server1 and server2 and
their Remote Management Controllers are server1-iLO and server2-
iLO, enter -iLO as the suffix.
IP Delta. Specify the delta to add to each server’s IP address to
determine the IP addresses of the associated Remote Management
Controllers. For example, if your servers are 1.255.200.12 and
1.255.200.15 and their Remote Management Controllers are
1.255.201.112 and 1.255.201.115, enter 0.0.1.100 as the delta.
Hostname/IP Address. Specify either the hostname or IP address for
the Remote Management Controller associated with the server to
which you are connected.
3. Fencing Action. When a server needs to be restricted from the SAN,
Clustered File System can either power-cycle the server or shut it
down. Select the method that you want to use.
4. Remote Management Controller iLO Access. Clustered File System
needs to log into a user account on the Remote Management
Controller in order to fence the server. Specify the user name and
password for the account that you want Clustered File System to use.
The account must currently exist on the Remote Management
Controller.
If all servers in the cluster will not be sharing the same login account,
remove the checkmark from “Login shared by all nodes of cluster.”