Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Cascading Failover in a Continental Cluster
Data Storage Setup
Chapter 8368
connection upon failure of all links. This is required so the user
would have time to split the BCV/R1 devices in the secondary
Symmetrix from the mirror group before re-establishing the SRDF
volume pairs between the primary Symmetrix and the secondary
Symmetrix upon link recovery.
2. Ensure that the Symmetrix ICDAs are correctly cabled to each host
system in the cluster that will run packages whose data reside on the
Symmetrix.
3. Install the SymCLI software on each host system that has data
residing on the Symmetrix. Using Figure 8-3, the SymCLI software
is installed on hosts clear, erie, newyork, seattle, atlanta and
sanfran.
4. Create or rebuild the SymCLI database on each system with the
most current information. Use the command:
# symcfg discover
5. Get a list of data for the Symmetrix devices visible to the host. Use
the command:
# syminq -sym
to get a list that includes the following data for each Symmetrix
logical device:
• HP-UX special device filename
Device type (R1, R2, BCV or blank)
Symmetrix serial number
Gatekeeper devices are usually of size 2880. The Symmetrix device
serial number is useful in matching the devices to the actual devices
in the Symmetrix configuration (downloaded by EMC):
• The first two digits equal the last two digits of the serial number
of the Symmetrix frame. The first two digits equal the last two
digits of the serial number of the Symmetrix frame.
• The next three hexadecimal digits equal the Symmetrix device
number that is seen in the output of the following command:
# symdev list