Operating System Software Owner manual

Local Setup
(not connected to the FC
SAN)
SystemASystemBTarget system
RCFC links
•• Node WWN:
2FF70002AC0000C3
Node WWN:
2FF70002AC000060
• •Node 0 WWN:
20110002AC000060
Node 0 WWN:
20210002AC0000C3
•• Node 1 WWN:
21210002AC0000C3
Node 1 WWN:
21320002AC000060
SynchronousMode
Backup system 2 (SystemC) is located far from the primary system and backup system 1, and
therefore must use an IP network.
• An IP network connects all systems. (The two backup systems use the IP network to share a
standby link for failover and recovery purposes.)
• Replication between SystemA and SystemC is in asynchronous periodic mode.
Local + Remote Setup
Example backup system 2Example backup system 1Example primary system
SystemCSystemBSystemASystem name
SystemASystemASystemBTarget system 1
RCIP links for target system
1
• Node 2 IP address
10.100.33.96
• Node 2 IP address
10.100.33.96
• Node 2 IP address:
10.100.33.195
• ••Node 3 IP address:
10.101.33.195
Node 3 IP address
10.101.33.96
Node 3 IP address
10.101.33.96
SystemBSystemCSystemCTarget system 2
RCIP links for target system
2
• Node 2 IP address:
10.100.33.195
• Node 2 IP address:
10.100.33.63
• Node 2 IP address:
10.100.33.63
• ••Node 3 IP address:
10.101.33.63
Node 3 IP address:
10.101.33.195
Node 3 IP address:
10.101.33.63
Asynchronous periodic —>
SystemA
Asynchronous periodic —>
SystemC
Mode
Verifying Connectivity between Systems
Verify the connectivity for each Remote Copy pair you are configuring.
• RCIP Remote Copy pairs:
# controlport rcip ping <IP_address> <N:S:P>
• RCFC Remote Copy pairs:
# showrctransport -rcfc
For more information, see “Verifying the Servers Are Connected” (page 35).
58 Setting Up Synchronous Long Distance Remote Copy