Ejercicios resueltos

To correctly specify the device file names when creating Symmetrix device groups, you need to know how the HP-UX device files map to the R1 and R2 Symmetrix devices. Use the following steps to gather the necessary information.

1. Obtain a list of data for the Symmetrix devices available, using the following command on each node without any options:

# syminq

Sample output from both the R1 and R2 sides is shown in Figure 4-12 and Figure 4-13.

Preparing a Cluster for MetroCluster/SRDF

Figure 4-12 Sample syminq Output from a Node on the R1 Side

Figure 4-13 Sample syminq Output from a Node on the R2 Side

2. You need the following information from these listings for each Symmetrix logical device:

• HP-UX device file name (e.g. /dev/rdsk/c3t3d2).

• device type (R1, R2, BCV, GK, or blank)

• Symmetrix serial number (e.g. 50006161), useful in matching the Device Product

Name Type Vendor ID Rev Ser Num Cap(KB) /dev/rdsk/c0t0d0 R1 EMC Symmetrix 5264 95004160 4418880 /dev/rdsk/c0t0d1 R1 EMC Symmetrix 5264 95005160 4418880 /dev/rdsk/c0t0d2 R2 EMC Symmetrix 5264 95006160 4418880 /dev/rdsk/c0t0d3 R2 EMC Symmetrix 5264 95007160 4418880 /dev/rdsk/c0t1d0 BCV EMC Symmetrix 5264 95024160 4418880 /dev/rdsk/c0t1d1 BCV EMC Symmetrix 5264 95025160 4418880 /dev/rdsk/c0t1d0 GK EMC Symmetrix 5264 95040160 2880 /dev/rdsk/c0t1d1 GK EMC Symmetrix 5264 95041160 2880 /dev/rdsk/c0t1d2 GK EMC Symmetrix 5264 95042160 2880 /dev/rdsk/c1t2d0 R1 EMC Symmetrix 5264 95004320 4418880 /dev/rdsk/c1t2d1 R1 EMC Symmetrix 5264 95005320 4418880 /dev/rdsk/c1t2d2 R2 EMC Symmetrix 5264 95006320 4418880

/dev/rdsk/c4t0d0 R2 EMC Symmetrix 5264 50014321 4418880 /dev/rdsk/c4t0d1 R2 EMC Symmetrix 5264 50015321 4418880 /dev/rdsk/c4t0d2 R1 EMC Symmetrix 5264 50016321 4418880 /dev/rdsk/c4t0d3 R1 EMC Symmetrix 5264 50017321 4418880 /dev/rdsk/c4t1d0 BCV EMC Symmetrix 5264 50034321 4418880 /dev/rdsk/c4t1d1 BCV EMC Symmetrix 5264 50035321 4418880 /dev/rdsk/c4t1d0 GK EMC Symmetrix 5264 50040321 2880 /dev/rdsk/c3t1d1 GK EMC Symmetrix 5264 50041321 2880 /dev/rdsk/c3t1d0 BCV EMC Symmetrix 5264 50030161 4418880 /dev/rdsk/c3t1d1 BCV EMC Symmetrix 5264 50031161 4418880 /dev/rdsk/c3t3d0 R2 EMC Symmetrix 5264 50004161 4418880 /dev/rdsk/c3t3d1 R2 EMC Symmetrix 5264 50005161 4418880 /dev/rdsk/c3t3d2 R1 EMC Symmetrix 5264 50006161 4418880

Device Product

Name Type Vendor ID Rev Ser Num Cap(KB)

Building a Metropolitan Cluster Using MetroCluster/SRDF Preparing a Cluster for MetroCluster/SRDF

HP-UX device names to the actual devices in the Symmetrix configuration downloaded by EMC support staff. This number is further explained in Figure 4-14.

Figure 4-14 Parsing the Symmetrix Serial Number

— The Symmetrix ID is the same as the last two digits of the serial number of the Symmetrix frame, in this example 50.

— The next three hexadecimal digits are the unique Symmetrix device number that is seen in the output of the status

command:

symrdf -g symdevgrpname query

and is used by the MetroCluster with EMC SRDF control script and saved in the file

/etc/cmcluster/package_name/symrdf.out. The contents of this file may be useful for debugging purposes.

— The next three digits indicate the Symmetrix host adapter (SA or FA) and port numbers; this is useful to see multiple host links to the same Symmetrix device. For example, PV links will show up as two HP-UX device file names with the same device number, but with different host adapter and port numbers.

3. Use the symrdf command on each Symmetrix disk array (that is, from both the R1 and the R2 side) to pair the logical device names for the R1 and R2 sides of each SRDF link:

# symrdf list

Sample output is shown in Figure 4-15 and Figure 4-16.

50 006 161 } } }

Symmetrix ID

unique device number host adapter and port numbers

Preparing a Cluster for MetroCluster/SRDF

Figure 4-15 Sample symrdf list Output from R1 Side

Figure 4-16 Sample symrdf list Output from R2 Side

4. Match the logical device numbers in the symrdf listings with the HP-UX device file names in the output from the syminq command to see which devices are seen from each node to make sure that this node can see all necessary devices.

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 the same logical device seen by each node that is connected to the same Symmetrix unit. Record the

STATUS RDF S T A T E S

000 000 R1:1 ?? RW RW SYN DIS OFF 0 0 RW NR Synchronized Local Device View

Sym RDF --- --- --- R1 Ivn R2 Ivn ---Dev RDev Typ:G SA RA LNK Mode Dom ACp Tracks Tracks Dev RDev Pair

MODES

001 001 R1:1 ?? RW RW SYN DIS OFF 0 0 RW NR Synchronized 004 004 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized 005 005 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized 006 006 R2:2 RW WD RW SYN DIS OFF 0 0 WD RW Synchronized 007 007 R2:2 RW WD RW SYN DIS OFF 0 0 WD RW Synchronized 008 008 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized 009 009 R1:1 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized

STATUS RDF S T A T E S

000 000 R2:1 NR WD RW SYN DIS OFF 0 0 NR RW Synchronized Local Device View

Sym RDF --- --- --- R1 Ivn R2 Ivn ---Dev RDev Typ:G SA RA LNK Mode Dom ACp Tracks Tracks Dev RDev Pair

MODES

001 001 R2:1 NR WD RW SYN DIS OFF 0 0 NR RW Synchronized 004 004 R2:1 RW WD RW SYN DIS OFF 0 0 WD RW Synchronized 005 005 R2:1 RW WD RW SYN DIS OFF 0 0 WD RW Synchronized 006 006 R1:2 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized 007 007 R1:2 RW RW RW SYN DIS OFF 0 0 RW WD Synchronized 008 008 R2:1 RW WD RW SYN DIS OFF 0 0 WD RW Synchronized

Building a Metropolitan Cluster Using MetroCluster/SRDF Preparing a Cluster for MetroCluster/SRDF

HP-UX device file names in your table.

Table 4-6 show a partial mapping for a 4 node cluster connected to two Symmetrix arrays (95 and 50). Note that you may have 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 4-6 Symmetrix Device and HP-UX Device Correlation

Symmetrix

Preparing a Cluster for MetroCluster/SRDF

NOTE The Symmetrix device number may be the same or different in each of the Symmetrix units for the same logical device. In other words, the device number for the logical device on the R1 side of the SRDF link may be different from the device number for the logical device on the R2 side of the SRDF link.

The Symmetrix logical device numbers in these examples were

configured to be the same number so that the cluster is easier to manage.

If you are reconfiguring an existing cluster, the

Dev and RDev devices will probably not be the same number.

When you are determining the configuration for the Symmetrix devices for a new installation, it is recommended that you try to use the same Symmetrix device number for the R1 devices and the R2 devices. It is also recommended that the same target and LUN number be configured for all nodes that have access to the same Symmetrix logical device.

Type GK

ID 95 c4t3d2

Dev# 028 c4t3d2

Type BCV n/a n/a

Table 4-6 Symmetrix Device and HP-UX Device Correlation

Symmetrix ID, device #, and type

Node 1 /dev/rdsk device file name

Node 2 /dev/rdsk device file name

Node 3 /dev/rdsk device file name

Nodes 4 /dev/rdsk device file name

Building a Metropolitan Cluster Using MetroCluster/SRDF