IBM eServer Cluster 1600 Managed by PSSP 3.5: What's New

146 IBM ^ Cluster 1600 Managed by PSSP 3.5: What’s New

For more information, refer to 6.3.2, “Migrating PSSP 3.1.1 and AIX 4.3.3 to

PSSP 3.5 and AIX 5.1” on page 136, where we migrated the system first to an

intermediate level and then to the latest AIX and PSSP levels.

6.3.4 Migrating PSSP 3.4 and AIX 5.1F to PSSP 3.5 and AIX 5.1F

This scenario is described in 6.3.3, “Migrating PSSP 3.4 and AIX 4.3.3 to PSSP

3.5 and AIX 5.1” on page 145.

6.4 Integration of SP-attached servers

In this section, we discuss, step-by-step, the integration of external nodes

(SP-attached servers) to our Cluster 1600. The hardmon daemon uses different

protocols for each kind of SP-attached server. The names of the protocols are

shown in Table 6-4.

Table 6-4 Hardware protocols for available Cluster 1600 nodes

Hardware protocol information:

򐂰 In the case of an Enterprise Server (S70, S7A, S80, p680) that uses SAMI,

the hardmon daemon on the CWS does not have a direct connection to the

node and frame supervisor card installed in the external system. The

connection is made through another daemon running on the CWS for every

attached server.

򐂰 The IBM ^ pSeries 660 servers have an SP Attachment adapter card

that is used to communicate with the CWS over a serial line using the CSP

protocol. For these servers, no other daemon is necessary to translate the

communication protocol for hardmon.

Migrate PSSP 3.5 on

nodes

Migrate PSSP 3.5 on

nodes

Route 1 Route 2 Route 3

Protocol name Servers

SP SP nodes

SAMI RS/6000 S70, S7A, and S80 or IBM

^ pSeries 680 servers

CSP RS/6000 H80, M80, and IBM

^ pSeries 660 servers (6H0,

6H1, and 6M1)

HMC IBM

^ pSeries 630, 670, and 690 servers

Chapter 6. Coexistence, migration, and integration 147

򐂰 There is one additional daemon running for each HMC server on the CWS to

provide communication between the hardmon daemon and the HMC server

using the HMC protocol.

The protocol name can be found for every frame by running the

splstdata -f

command, as shown in Example 6-17.

Example 6-17 SDR frame information

sp4en0:/

root $ splstdata -f

List Frame Database Information

frame# tty s1_tty frame_type hardware_protocol control_ipaddrs domain_name

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

1 /dev/tty0 "" switch SP "" ""

2 /dev/tty1 "" noswitch SP "" ""

3 /dev/tty2 "" "" CSP "" ""

4 "" "" "" HMC 192.168.4.251 Enterprise

5 /dev/tty3 /dev/tty4 "" SAMI "" ""

The data flow of the hardware control subsystem is shown in Figure 6-2.

Figure 6-2 Hardware control

s70d

Node

Supervisor Cards

S7X/S80/pSeries680

SAMI

RS-232

RS-232

s1_tty

hardmon

perspectives

hmmon hmcmdsspmon

Frame Supervisor Cable

RS-232

s1term

nodecond

SDR

/spdata/sys1/spmon/hmacls

/spdata/sys1/spmon/hmthresholds

splogd

/var/adm/SPlogs/SPdaemon.log

setup_logd

/spdata/sys1/spmon/hwevents

Frame

Supervisor Card

SP

errdemon

hmadm

state handlers

M80/H80/pseries660

pSeries 690/670

hcmd

HMC

CIM Server

HMC

RS-232

Trusted Ethernet

CSP

RS-232