IBM Tivoli Storage Manager in a Clustered Environment

442 IBM Tivoli Storage Manager in a Clustered Environment

Once you have installed HACMP, check to make sure you have the required

APAR applied with the instfix command.

Example 8-25 shows the output on a system having APAR IY58496 installed.

Example 8-25 APAR installation check with instfix command.

instfix -ick IY58496

#Keyword:Fileset:ReqLevel:InstLevel:Status:Abstract

IY58496:cluster.es.client.lib:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.0

IY58496:cluster.es.client.rte:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.0

IY58496:cluster.es.client.utils:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.

IY58496:cluster.es.cspoc.cmds:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.0

IY58496:cluster.es.cspoc.rte:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.0

IY58496:cluster.es.server.diag:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.0

IY58496:cluster.es.server.events:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2

IY58496:cluster.es.server.rte:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.0

IY58496:cluster.es.server.utils:5.2.0.1:5.2.0.1:=:Base fixes for hacmp 5.2.

8.7 HACMP configuration

Cluster information will be entered on one node only between synchronizations.

Network adapters configuration

We will now configure our network adapters with the boot addresses, from

Table 8-1 on page 429.

During these steps, we will require an alternative network connection to telnet to

the servers or to login from a local console, as our network connection will be

severed.

1. We use the smitty chinet fast path.

2. Then, on the Available Network Interfaces panel, we select our first

targeted network adapter.

Tip: We suggest choosing a “primary” node and then using this node to enter

all the cluster information. This will help you avoid losing configuration data or

incurring inconsistencies.

Attention: Make a note of the default router address and other routing table

entries. This is due to the ip address changes deleting the routing information,

which will have to be added back later.

Chapter 8. Establishing an HACMP infrastructure on AIX 443

3. We fill in the required fields and press Enter (Figure 8-7).

Figure 8-7 boot address configuration

4. We repeat the above steps for the two adapters of both servers.

8.7.1 Initial configuration of nodes

We will now configure the Cluster Name, Cluster Node Name, and the initial

communication paths between the nodes:

1. On the AIX command line, enter the command smitty hacmp.

2. Within SMIT, select the Extended Configuration option.

3. Next, select the Extended Topology Configuration option.

4. Then, select the Configure an HACMP Cluster option.

5. Lastly, select the Add/Change/Show an HACMP Cluster option.

6. Then we enter our Cluster Name, which is

cl_hacmp01.

7. Press Enter to complete the configuration (Figure 8-8).

444 IBM Tivoli Storage Manager in a Clustered Environment

Figure 8-8 Define cluster example.

8. Then we go back to the Extended Topology Configuration panel (3 layers

back).

9. We select the Configure HACMP Nodes option.

10.Then we select the Add a Node to the HACMP Cluster option.

11.We fill in the Node Name field.

12.For the next field below, we press the F4 key to select from a list of available

communication paths to the node.

13.Press Enter to complete the change (Figure 8-9).

Chapter 8. Establishing an HACMP infrastructure on AIX 445

Figure 8-9 An add cluster node example

14.We now go back thorough the SMIT menus using the F3 key, and then repeat

the process for the second node.

8.7.2 Resource discovery

Now we will use the cluster software discovery function to have HACMP locating

the available hardware resources which are available to the nodes.

1. From the AIX command line, we enter the smitty hacmp command.

2. We select Extended Configuration option.

3. Then, we select the Discover HACMP-related Information from

Configured Nodes option.

8.7.3 Defining HACMP interfaces and devices

The cluster should have more than one network path to avoid a single point of

failure for the high available service.

Network paths configured to the cluster are used for heartbeat also. To improve

HACMP problem determination and fault isolation, we use both IP and non-IP

based networks as heartbeat paths.

Note: The Discover utility runs for few seconds (depending on the

configuration) and ends, showing an OK status.

446 IBM Tivoli Storage Manager in a Clustered Environment

Now we are going to configure planned communication devices and interfaces.

Configuring the non-IP communication devices

We now configure the HACMP discovered serial and disk devices for the cluster

heartbeat using SMIT.

1. Enter the AIX smitty hacmp command.

2. Select the Extended Configuration option.

3. Then, select the Extended Topology Configuration option.

4. Next, select Configure HACMP Communication Interfaces/Devices

option.

5. Select the Discovered option (Figure 8-10).

6. Select the Communications Devices type from the selection options.

7. The screen Select Point-to-Point Pair of Discovered Communication

Devices to Add appears; devices that are already added to the cluster are

filtered from the pick list.

8. Now select both devices for the same network at once and press Enter.

9. We then repeat this process for the second serial network type. In our cluster

we configure two point-to-point network types, rs232 and disk.

Figure 8-10 Configure HACMP Communication Interfaces/Devices panel

Note: Configuring the first network interface or communication device for a

point to point network makes a corresponding cluster network object

configured too.