HP Serviceguard Metrocluster with EMC SRDF for Linux B.01.00.00

----------------------------------------------------------------------------
STATUS MODES RDF S T A T E S
Sym RDF --------- ----- R1 Inv R2 Inv ----------------------
Dev RDev Typ:G SA RA LNK MDATE Tracks Tracks Dev RDev Pair
---- ---- -------- --------- ----- ------- ------- --- ---- -------------
034E 80B2 R2:2 RW WD RW S..2. 0 0 WD RW Synchronized
034F 80B3 R2:2 RW WD RW S..2. 0 0 WD RW Synchronized
0350 80B4 R2:2 RW WD RW S..2. 0 0 WD RW Synchronized
0351 80B5 R2:2 RW WD RW S..2. 0 0 WD RW Synchronized
0352 80B6 R2:2 RW WD RW S..2. 0 0 WD RW Synchronized
0353 80B7 R2:2 RW WD RW S..2. 0 0 WD RW Synchronized
4. Match the logical device numbers in the symrdf listings with the disk names in the output
from the sympd list command.
Use the Symmetrix ID to determine which Symmetrix array is connected to the node. Then use
the Symmetrix device number to determine which devices are in the same logical device seen
by each node that is connected to the same Symmetrix unit. Record the disk names in your
table.
Table 1 shows a partial mapping for a 4 node cluster connected to two Symmetrix arrays (95
and 50). There may be many R1 and R2 devices and many gatekeepers for each package,
so this table will be much larger for most clusters. Also, with M by N configurations, the number
of devices increases according to the number of Symmetrix frames.
Table 1 Mapping for a 4 node Cluster connected to 2 Symmetrix arrays
Nodes 4 /dev/sd* disk
name
Node 3 /dev/sd*
disk name
Node 2 /dev/sd*
disk name
Node 1 /dev/sd*
disk name
Symmetrix ID,
device #, and type
sda95ID
sdc005Dev#
R1Type
sdb50ID
sdd014Dev#
R2Type
sdb95ID
sdd00ADev#
R2Type
sda50ID
sdb012Dev#
R1Type
sdc95ID
sda040Dev#
GKType
sdc50ID
sde041Dev#
GKType
sdd95ID
sdb028Dev#
n/an/aBCVType
Determining Symmetrix device names on each node 11