Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1 Instrukcja Użytkownika Pobierz pdf (Strona 9)

The ﬁrst cluster node is conﬁgured. Before continuing, invoke ccontrol list or ccontrol all

at a shell prompt to gather the information necessary for conﬁguring the second node.

3 Configuring the Second Node

Use the service relocate command of cluadmin to move the services (the storage you deﬁned)

to the other cluster node.

Deﬁne the Caché instances on this node in one of two ways:

• Run the installation procedure again and give the same instance name you used on the

other node. Install into the same directory.

This is the best option if you are conﬁguring a Web server for use with Caché, because

the Web server conﬁguration is “local” to each node. Reinstalling Caché does not affect

the changes you made to the conﬁguration (cache.cpf) ﬁle.

• If you do not need Caché to conﬁgure the Web server on the other node, register the

Caché instances on the local node using the ccontrol create command:

ccontrol create $cfgname directory=$tgtdir versionid=$ver

For example, if ccontrol all on the ﬁrst node displays:

Configuration Version ID Port Directory

--------------- ---------------- ----- ----------

dn CACHEHA1 5.1.0.900 1973 /store1/c51ha

db CACHEHA2 5.1.0.900 1972 /store2/c51ha2

Run:

ccontrol create cacheha1 directory=”/store1/c51ha” versionid=”5.1.0.900”

ccontrol create cacheha2 directory=”/store2/c51ha2” versionid=”5.1.0.900”

Use ccontrol start to start the instances and verify that they work, shut them down with

ccontrol stop.

4 Adding Caché to the Cluster Services

The scripts necessary to start and stop Caché as part of service failover do not ship with

Caché. An example of the main script is included in the Caché Initialization File for Linux

Caché ECP Clusters on Red Hat Enterprise Linux 5

Configuring the Second Node

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Brak uwag

Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1 Instrukcja Użytkownika Strona 9