Table of Contents
Advertisement
9. If needed, you may also create a private resource that you can create that becomes a
subordinate resource by clicking on the Attach a new Private Resource to the Selection
button. The process is the same as creating a shared resource described in
"Adding Cluster
Resources". The private resource will appear as a child to the shared
resource to which you associated with the shared resource. Click the triangle icon next to the
shared resource to display any private resources associated.
10. W hen finished, click OK.
11. C hoose File => Save to save the changes to the cluster configuration.
Note
To verify the existence of the IP service resource used in a cluster service, you
must use the
output shows the
cluster service:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1356 qdisc pfifo_fast qlen 1000
link/ether 00:05:5d:9a:d8:91 brd ff:ff:ff:ff:ff:ff
inet 10.11.4.31/22 brd 10.11.7.255 scope global eth0
inet6 fe80::205:5dff:fe9a:d891/64 scope link
inet 10.11.4.240/22 scope global secondary eth0
valid_lft forever preferred_lft forever
9. Propagating The Configuration File: New Cluster
For newly defined clusters, you must propagate the configuration file to the cluster nodes as
follows:
1. Log in to the node where you created the configuration file.
2. Using the
command, copy the
scp
cluster.
Note
/sbin/ip addr list
/sbin/ip addr list
/etc/cluster/cluster.conf
Propagating The Configuration File: New
command on a cluster node. The following
command executed on a node running a
file to all nodes in the
Section 7,
77
Advertisement
Table of Contents
