0% found this document useful (0 votes)
3 views18 pages

RDR Configuration Guide for StoreWay FDA

This document provides a step-by-step guide for configuring replication (RDR) between StoreWay FDA systems, focusing on efficiency and reliability. It covers both Direct Access (DAS) and Storage Area Network (SAN) configurations applicable to models FDA2400/2500/2800/2900/4900. The guide includes prerequisites, configuration procedures, and best practices for successful implementation.

Uploaded by

billy.laille
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views18 pages

RDR Configuration Guide for StoreWay FDA

This document provides a step-by-step guide for configuring replication (RDR) between StoreWay FDA systems, focusing on efficiency and reliability. It covers both Direct Access (DAS) and Storage Area Network (SAN) configurations applicable to models FDA2400/2500/2800/2900/4900. The guide includes prerequisites, configuration procedures, and best practices for successful implementation.

Uploaded by

billy.laille
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

StoreWay

Bull Storage Solutions

Engineering Document

RDR Configuration Planning Guide


Best Practices

 StoreWay FDA
 RDR
 RDR/CO

Date: Published January 2006


Revision: v2.9/ October 2006
Reference: FDA_RDR_PlanningGuide.doc
[Link]
StoreWay FDA - RDR Configuration Planning Guide V2.9

Note to the reader


This document describes a step by step guideline to configure the replication (RDR) between two StoreWay
FDA systems. The goal is to perform this operation in an efficient and reliable way.

RDR is supported on FDA2400/2500/2800/2900/4900.

We recommend reading carefully the document before doing any configuration.

StoreWay engineering documentation


 StoreWay FDA Installation Planning Guide – Best Practices
 StoreWay FDA RDR Configuration Planning Guide – Best Practices
 StoreWay FDA RAID-6 Technology – Technical Notes
 StoreWay FDA Phoenix Technology – Technical Notes
 StoreWay FDA RDR and RDR/CO Technology – Technical Notes
 OpenSave with StoreWay FDA DSV In SAN Environments – White Paper
 Atempo Time Navigator with StoreWay FDA DSV In SAN Environments – White Paper
 StoreWay FDA RDR, RDR/CO – White Paper
 OpenSave with StoreWay FDA DSV and ARF – Blue Print Document
 StoreWay FDA Replication over SAN Long Distance on Brocade s7500 – Blue Print Document
 SAN Long Distance (Alcatel/Bull project) – Blue Print Document
 StoreWay FDA FDACopyDrive Backup Automation – Blue Print Document
 StoreWay FDA Boot SAN on ESCALA – Best Practices

StoreWay FDA engineering documentation is available on [Link] then


go to \fournisseurs\Disk_Arrays\NEC or to \Bibliotheque\White Papers\FDA

SAN

Bull P&S/SCCPage 2 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Table of Contents
Note to the reader ...................................................................................................................... 2
Summary.................................................................................................................................... 4
Document References................................................................................................................ 4
Intended Audience..................................................................................................................... 4
Introduction ............................................................................................................................... 4
Configuration - DAS/SAN ................................................................................................................ 4
Which FE ports for the replication.................................................................................................. 7
iSM ..................................................................................................................................................... 7
Procedure................................................................................................................................... 8
Overview ............................................................................................................................................ 8
1. Pre-Requisites Check up .............................................................................................................. 8
1.1 Primary Site ............................................................................................................................................. 8
1.2 Secondary Site ......................................................................................................................................... 8
2. Collect Information....................................................................................................................... 8
3. Configure ....................................................................................................................................... 9
3.1 Zoning ..................................................................................................................................................... 9
3.2 Primary Array .......................................................................................................................................... 9
3.3 Secondary Array .................................................................................................................................... 10
3.4 Final Steps ............................................................................................................................................. 12
3.5 Error cases ............................................................................................................................................. 12
Appendix 1 - Best Practices: Choosing the Replication Ports / Zoning................................ 13
Appendix 2 – Primary Site Information table (DAS Configuration) .................................... 14
Appendix 3 – Secondary Site Information table (DAS Configuration) ................................ 15
Appendix 4 – Primary Site Information table (SAN Configuration) .................................... 16
Appendix 5 – Secondary Site Information table (SAN Configuration) ................................ 17

Bull P&S/SCCPage 3 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Summary
The goal of this document is to propose a step by step guideline to configure the replication (RDR) between two
StoreWay FDA systems in order to minimize the configuration steps and save time. Both DAS (Direct Access)
and SAN configurations are covered. This document applies to StoreWay FDA2400/2800/2500/2900/4900.

Document References
 Storage S2x00 Initial Setup Guide (StoreWay User Documentation)

Intended Audience
This procedure is intended for Bull Engineers who develop services in installing and configuring replication
(RDR). The audience should be familiar with Fibre Channel, SAN and DAS concepts and use of iStorage
Manager (iSM), iStorage Navigator (iSN) and FC Switchs tools like Brocade Telnet and WebTools.

Introduction
Configuration - DAS/SAN
In a DAS configuration (Figure -1), the important point is that you cannot interconnect two FC ports (i.e. two
arrays FE ports) in a direct connection if those two FC ports have the same ALPA (Arbitrated Loop Physical
Address). This is the reason why, in a DAS configuration, you must set a different ALPA on each interconnected
ports. Actually, you will configure with iSN (iSN Configuration FC Port Configuration) the Loop ID value
(decimal value of the ALPA) of the port in the Switch column.

Loop ID

To fill up the Site Information tables use either the proposed values or determine the values that fit the best your
configuration. It is recommended to start with low Loop ID values (00, 01, 02 …).
Example 1:
Local Array CONT0 / HP3  Remote Array CONT0 / HP3
Switch = 00 Switch = 01
Local Array CONT1 / HP3  Remote Array CONT1 / HP3
Switch = 00 Switch = 01
Example 2:
Local Array CONT0 / HP3  Remote Array CONT0 / HP3
Switch = 00 Switch = 01
Local Array CONT1 / HP3  Remote Array CONT1 / HP3
Switch = 01 Switch = 00

Bull P&S/SCCPage 4 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

In DAS configuration (Figure - 1) you need also to get prepared to configure the Port ID value for each port.
Once the Switch value settled, convert it to the Port ID. Examples that will cover most of the cases:
• if Switch=00 then ALPA=EF and Port ID=0000EF
• if Switch=01 then ALPA=E8 and Port ID=0000E8
• if Switch=02 then ALPA=E4 and Port ID=0000E4
• if Switch=03 then ALPA=E2 and Port ID=0000E2
For other cases use the conversion table (Table 4.3.1 of Storage S2x00 Initial Setup Guide) to convert Switch
value to ALPA value, then concatenate ALPA to “0000” to make the Port ID value.

Hosts IOs Hosts IOs

CONT0 CONT1 CONT0 CONT1


Port 0 Port 0 Port 0 Port 0

CONT0 CONT0
Port 1 Port 1
Primary Secondary
Array CONT1 CONT1 Array
FDA2400_1 Port 1 Port 1 FDA2400_2

Replication IOs
Primary Site Secondary Site

FC Links ………...:

FDA Subsystems……:

Figure 1 - DAS Configuration

Bull P&S/SCCPage 5 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

In a SAN configuration (Figure - 2), the first important point is that the Fabric will provide the Port ID. So once
the replication port has been connected to the FC Switch, use a Switch tool to check the state of the port and
collect the Port ID). The second important point is that the replication pair ports must be correctly zoned.
Example:
Zone X Local Array CONT0 / HP3  Remote Array CONT0 / HP1
Port ID = 010300 Port ID = 121b00
Zone Y Local Array CONT1 / HP3  Remote Array CONT1 / HP1
Port ID = 020300 Port ID = 131b00

See the Best Practices in Appendix -1.

Hosts IOs Replication IOs Hosts IOs

Fabric MPR MPR Fabric

CONT0 CONT1 HA00/… HA01/…


Port 0-2 Port 0-2 Ports 0-7 Ports 0-7

CONT0 HA0C
Port 3 Port 0
Primary Secondary
Array CONT1 HA0D Array
FDA2800_1 Port 3 Port 0 FDA4900_1

Primary Site Secondary Site


FC Links ……..….:

FDA Subsystems……:

Figure 2 - SAN Configuration

Bull P&S/SCCPage 6 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Which FE ports for the replication


In both type of configuration (DAS or SAN) the choice of the FE (Front End) ports that will be dedicated to the
replication will depend on the model of the StoreWay FDA. To make your choice, refer to the Best Practices in
Appendix -1.
Examples (There should be two ports for the redundancy for the high availability):

StoreWay FDA2400/2500:
Controller 0 / Port 1 aka CONT0 / HP1 aka HD0 / 1
Controller 1 / Port 1 aka CONT1 / HP1 aka HD1 / 1

StoreWay FDA2800/2900:
Controller 0 / Port 3 aka CONT0 / HP3 aka HD0 / 3

Controller 1 / Port 3 aka CONT1 / HP3 aka HD1 / 3

FDA4900 – Cluster 0:
Controller C / Port 0 aka HA0C / HP0 aka HA0C / 00
Controller C / Port 1 aka HA0C / HP1 aka HA0C / 01
……….. ………. …..
Controller C / Port 6 aka HA0C / HP6 aka HA0C / 06
Controller C / Port 7 aka HA0C / HP7 aka HA0C / 07

FDA4900 – Cluster 1 (for the redundancy for the high availability):


Controller D / Port 0 aka HA0D / HP0 aka HA0D / 00
Controller D / Port 1 aka HA0D / HP1 aka HA0D / 01
……….. ………. …..
Controller D / Port 6 aka HA0D / HP6 aka HA0D / 06
Controller D / Port 7 aka HA0D / HP7 aka HA0D / 07

iSM

On the primary site LAN and on the secondary site LAN there should be an iSM (iStorage Manager) Server to
manage the StoreWay arrays. The fact that the LAN of the primary site and the LAN of the secondary site may
not be interconnected (e.g. due to the long distance) will not cause a problem for the replication because the
information about the volumes involved in the replication is transmitted between the arrays thru the FC links and
then between the local array and the local iSM Server thru the local LAN.
In this case:
• Each local iSM Servers will be used for the local administration (Pool, LD, License, LD Set, Snapshots,
Clones …) and monitoring.
• The iSM Server on the primary site will be used to start the Replication menu and run the Pair Setting
and Volume Operation. Of course the iSM Server on the secondary site can play the same role as the
primary array.

Bull P&S/SCCPage 7 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Procedure
Overview
The procedure includes the use of Site Information Tables (Appendix 2/3/4/5) that you will fill up progressively
and then use as an input for configuring.
 Read carefully the introduction chapter,
 Printout as many Site Information Tables that are necessary.
Then start a 3 steps procedure:
1. Proceed to the check up of the pre-requisites. During this step start to fill up the Tables.
2. Prepare the configuration by collecting information and finish to fill up the Tables.
3. Configure and check the configuration.

In case of long distance between the sites, once step “2” is completed, exchange with your correspondent the
Table information and synchronize by telephone the execution of step “3”.

1. Pre-Requisites Check up
Check the following items before configuring the replication between two FDA systems. During this step start
filling up the site tables but do not configure the array.

1.1 Primary Site


 Array is powered-on and has a LAN connection.
o Fill up: Model, Nickname and IP address (item 3).
 SAN configuration: array is connected to a FC Switch and the FC link is established.
Or
 DAS configuration: array is directly connected to another array and the FC link is established.
 Array is manageable with iSN.
 Array is manageable with iSM.
o Fill up: SAA (item 4). Do: iSM select array  right click on properties.
 Array has its RDR license unlocked (same license on both systems is highly recommended).
 Array has the necessary available ports for the replication FC links. There should be two ports for the
redundancy for the high availability.

1.2 Secondary Site


 Array is powered-on and has a LAN connection.
o Fill up: Model, Nickname and IP address (item 3).
 SAN configuration: array is connected to a FC Switch and the FC link is established.
Or
 DAS configuration: array is directly connected to another array and the FC link is established.
 Array is manageable with iSN.
 Array is manageable with iSM.
o Fill up: SAA (item 4). Do: iSM select array  right click on properties.
 Array has its RDR license unlocked (same license on both systems is highly preferable).
 Array has the necessary available ports for the replication FC links. There should be two ports for the
redundancy for the high availability.

2. Collect Information
During this step finish filling up the site tables but don’t configure the array.
 Primary Site: Fill up the Site Information table with the information concerning the Primary array
(items 4 to 17).
 Secondary Site: Fill up the Site Information table with the information concerning the Secondary array
(items 4 to 17).
In the eventuality of a primary array connected to 2 secondary arrays use 2 data sheets, one per remote array.
 Collect the WWPN of all the replication ports that must paired in a single zone (see also Appendix.1)

Bull P&S/SCCPage 8 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9
3. Configure
3.1 Zoning
Zone (WWPN, single initiator zoning) the pair of replication ports in a single zone (see also Appendix.1).

Repeat the operation for each pair of replication ports.

3.2 Primary Array


Note: don’t forget to validate each step by a click on the SET button.

 Check or Configure items 7 and 13 (iSN  Configuration / Port Configuration). Click on SET.
 Configure items 8, 9 10, 11 and 14, 15, 16, 17 (iSN  Configuration / FC Port Configuration). Click
on SET.
 Go to iSN  Panel. If the replication ports are checked then remove the check of those ports, wait for
at least 5 seconds, check again the ports and click on SET. Otherwise check the ports and click on SET.
Note: for the next steps additional explanation can be found in the step “4” of the chapter 4-3-4-2 of the
Storage S2x00 Initial Setup Guide.
 Go to iSN  Solution / RDR Configuration
 Click on HDPC
 In “Valid Subsystem Link Number” enter the number (how many) of (in French “le nombre de”)
remote arrays (Item “4”) and click on SET.
 For each remote array: “Subsystem Link Information Number” is the number of the (in French “le
numéro du”) path to the remote array.
 Enter “0” if there is only one remote array. Click on SET.
Otherwise enter “0” for the 1st array and “1” for the second array and Click on SET.
 Enter the SAA of the remote array (Item “3”).
 “Valid Path Information Number” is the Number of paths (or FC Links) to the remote array (Item
“5”). Enter this value.
 “Path Information Format Code” is fixed to “01”. Check that “01” appears.
 Click on SET
 You should see as many columns as there are paths to the remote array.

Example of what you may see on a FDA2400/2800/2500/2900 before doing the configuration for 2
paths:

Example of what you may see on a FDA4900 before doing the configuration for 2 paths:

Bull P&S/SCCPage 9 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

 Now for each Path Information (“0” then “1” …) check and configure:
 Director Number is set to HD0 or HA00 (or HD1or HA01 …). This is the local Controller
number.
 Port Number is set to the values as in Item “6” or “12” (This is the local Port number).
 Transfer Rate (normally “00” or “0” on FDA4900). Caution: The Transfer Rate should not
have a number that exceeds the network bandwidth. If nothing is set, IO timeout may occur due
to too much load weigh on the storage and the network. Check the bandwidth of the network.
 N_Port Identifier Lock is normally set to “L” for merged SANs or DAS configurations (“U”
when the link goes thru Routed SANs). Lock acts as a security, disrupting the link in case of
unwillingly unplugging the FC cable. Unintentional port pair coupling can be circumvented by
this option.
 N_Port Identifier (This is the Port ID as in Items “11” and “17” if SAN or Items “10” and
“16” if DAS). Caution: this is the Port ID of the remote Port.
 Click on SET.

Example of what you may see on a FDA2400/2800/2500/2900 after doing the configuration for 2
paths:

 Click on PCHD if FDA2xxx or on PC HA if FDA4900 (it saves you work by
uploading the configuration to the controller)

3.3 Secondary Array


Note: don’t forget to validate each step by a click on the SET button.

 Check or Configure items 7 and 13 (iSN  Configuration / Port Configuration). Click on SET.
 Configure items 8, 9 10, 11 and 14, 15, 16, 17 (iSN  Configuration / FC Port Configuration). Click
on SET.
 Go to iSN  Panel. If the replication ports are checked then remove the check of those ports, wait for
at least 5 seconds, check again the ports and click on SET. Otherwise check the ports and click on SET.
Note: for the next steps additional explanation can be found in the step “4” of the chapter 4-3-4-2 of the
Storage S2x00 Initial Setup Guide.
 Go to iSN  Solution / RDR Configuration
 Click on HDPC
 In “Valid Subsystem Link Number” enter the number (how many) of (in French “le nombre de”)
remote arrays (Item “4”) and click on SET.
 For each remote array: “Subsystem Link Information Number” is the number of the (in French “le
numéro du”) path to the remote array.
 Enter “0” if there is only one remote array. Click on SET.
Otherwise enter “0” for the 1st array and “1” for the second array and Click on SET.
 Enter the SAA of the remote array (Item “3”).
 “Valid Path Information Number” is the Number of paths (or FC Links) to the remote array (Item
“5”). Enter this value.
 “Path Information Format Code” is fixed to “01”. Check that “01” appears.

Bull P&S/SCCPage 10 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9
 Click on SET

 You should see as many columns as there are paths to the remote array.

Example of what you may see on a FDA2400/2800/2500/2900 before doing the configuration for 2
paths:

Example of what you may see on a FDA4900 before doing the configuration for 2 paths:

 Now for each Path Information (“0” then “1” …) check and configure:
 Director Number is set to HD0 or HA00 (or HD1or HA01 …). This is the local Controller
number.
 Port Number is set to the values as in Item “6” or “12” (This is the local Port number).
 Transfer Rate (normally “00” or “0” on FDA4900). Caution: The Transfer Rate should not
have a number that exceeds the network bandwidth. If nothing is set, IO timeout may occur due
to too much load weigh on the storage and the network. Check the bandwidth of the network.
 N_Port Identifier Lock is normally set to “L” for merged SANs or DAS configurations (“U”
when the link goes thru Routed SANs). Lock acts as a security, disrupting the link in case of
unwillingly unplugging the FC cable. Unintentional port pair coupling can be circumvented by
this option.
 N_Port Identifier (This is the Port ID as in Items “11” and “17” if SAN or Items “10” and
“16” if DAS). Caution: this is the Port ID of the remote Port.
 Click on SET.

 Click on PCHD if FDA2xxx or on PC HA if FDA4900 (it saves you work by
uploading the configuration to the controller)

Bull P&S/SCCPage 11 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

3.4 Final Steps

Final steps for last checking:

 On the Primary array do iSN  Solution  RDR. Click on HDPC. Check that “12.1 State” is
Online. If this is not the case, review the configuration, Click on PCHD, Click “RD Link” to Online
and then Click on HDPC.
 On the Secondary array do iSN  Solution  RDR. Click on HDPC. Check that “12.1 State” is
Online. If this is not the case, review the configuration, Click on PCHD, Click “RD Link” to Online
and then Click on HDPC.
 On iSM, click on the Replication button. Select the local array (left hand) and check the replication
state in the right hand part, in the Replication and LINK Information tabs.
 In case the Consistency Option is required (RDR/CO, Atomic Groups):
o Check in iSM that the “RDR/DR” license is set.
o Configure the options in iSN: iSN  Solution  Disaster recovery
Example:
Click on HDPC if FDA2xxx or on HAPC if FDA4900

AT Group to use 4:16MB


Equipments uses 1:16MB

Click on PCHD if FDA2xxx or on PCHA if FDA4900

3.5 Error cases


General cases when the link in iSM  Replication  Replication and LINK Information remains in “Offline”
state (link status button grey colour instead of green):
1. The zoning is not ok  double check zoning
2. The port may not be check in (iSM  Panel)

Examples of error codes under iSN:


1. Error “ASC/ASCQ CODE=2000”
a. This is in general an invalid operation, meaning that the operation is performed in an incorrect
or invalid context. Example, the RDR license has not been unlocked.
2. Error “ASC/ASCQ CODE=F2F0”
a. This is in general a problem in the iSN configuration setting: invalid parameter, invalid value
or invalid sequence.
3. Error “ASC/ASCQ CODE=F262”
a. This is in general a wrong or a missing zoning configuration.

Check again the pre-requisites in the Procedure chapter.

Bull P&S/SCCPage 12 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Appendix 1 - Best Practices: Choosing the Replication


Ports / Zoning
 Make the choice of the FE (Front End) ports for the replication.
o FDA2400/2500 - Two FE ports per controller:
Hosts: Port 0 of CONT0 and Port 0 of CONT1
Replication: Port 1 of CONT0 and Port 1 of CONT1 (redundancy for the high
availability)

o FDA2800/2900 - Four FE ports per controller:


 One remote array
To Hosts:
Port 0 of CONT0 and Port 0 of CONT1
Port 1 of CONT0 and Port 1 of CONT1
Port 2 of CONT0 and Port 2 of CONT1
To the peer Array (Replication):
Port 3 of CONT0 and Port 3 of CONT1 (redundancy for the high availability)

 Two remote arrays


To Hosts:
Port 0 of CONT0 and Port 0 of CONT1
Port 1 of CONT0 and Port 1 of CONT1
To the 1st peers Array (Replication):
Port 3 of CONT0 and Port 3 of CONT1 (redundancy for the high availability)
To the 2nd peers Array (Replication):
Port 2 of CONT0 and Port 2 of CONT1 (redundancy for the high availability)

o FDA4900 - Eight FE ports per controller:


To Hosts:
Ports 0-7 of HA00, Ports 0-7 of HA01,
Ports 0-7 of HA02, Ports 0-7 of HA03,
…..
To the peer Array (Replication):
Port 0-7 of HA0C and Port 3 of Port 0-7 of HA0D (redundancy for the high
availability)

 Zone the FDA FE ports involved in the replication.


o Single initiator zoning:
That means that each zone contains two “Port_Name”, the “Port_Name” of the initiator and
the “Port_Name” of the target, knowing that each one its turn will be initiator and target.
For example “local FDA CONT0 Port 3” in a zone with “remote FDA CONT0 Port 3” and
“local FDA CONT1 Port 3” in a zone with “remote FDA CONT1 Port 3”.
o Zoning using the WWN:
Use the WWPN (the WWN of the “Port_Name”) of the devices as each WWPN is unique.
o Use of Aliases:
Use systematically an alias for each FDA FE Port in order to modify only the content of the
alias in case of modification of the configuration.

Bull P&S/SCCPage 13 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Appendix 2 – Primary Site Information table (DAS


Configuration)
Primary Site Name: ________
Cfg
Item Parameter Value to Collect or Configure Tool Comment
Array Model …
Array Nickname … iSM cut&paste from iSM
1 IP address of CONT0 … iSN
2 IP address of CONT1 … iSN If any
SAA (Subsystem Right click on Array
3 Absolute Address) … iSM Properties
cut&paste from iSM

4 Number of Remote arrays … 1 or 2


For one Remote array: 2 remote arrays  2
data sheets
Name of the Remote array …
Number of paths (or FC 1 or 2 (or more)
5 Links) to the remote array …

1st Path information:


“Subsystem Link Information Number” = 0
CONT0 (or HD0) Controller 0
6 Local Port (or HPx) … FE Port #: 3, 2, 1
7 Host Type 00:Default (1) iSN Config/Port Config
8 Link Attach 2:Only FC-AL (1) iSN Config/FC Port Config
(1)
9 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Config/FC Port Config
10 Switch (or FC Loop ID) Switch=00 (2)/ALPA=EF / Port ID=0000EF iSN
Switch=00, 01, 02 …..
Config/FC Port Config
11 Data Rate (or FC speed) .. [Mbps] iSN

2nd Path information:


“Subsystem Link Information Number” = 1
CONT1 (or HD1) Controller 1
12 Local Port (or HPx) … FE Port #: 3, 2, 1
13 Host Type 00:Default (1) iSN Config/Port Config
14 Link Attach 2:Only FC-AL (1) iSN Config/FC Port Config
(1)
15 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Config/FC Port Config
16 Switch (or FC Loop ID) Switch=00 (2)/ALPA=EF / Port ID=0000EF iSN
Switch=00, 01, 02 …..
17 Data Rate (or FC speed) .. [Mbps] iSN Config/FC Port Config

(1) Fixed values.


(2) Proposed value. See also the notes about the correspondence between Switch, ALPA and Port ID.

Bull P&S/SCCPage 14 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Appendix 3 – Secondary Site Information table (DAS


Configuration)
Secondary Site Name: ________
Cfg
Item Parameter Value to Collect or Configure Tool Comment
Array Model …
Array Nickname … iSM cut&paste from iSM
1 IP address of CONT0 … iSN
2 IP address of CONT1 … iSN If any
SAA (Subsystem Right click on Array
3 Absolute Address) … iSM Properties
cut&paste from iSM

4 Number of Remote arrays … 1 or 2


For one Remote array: 2 remote arrays  2
data sheets
Name of the Remote array …
Number of paths (or FC 1 or 2 (or more)
5 …
Links) to the remote array

1st Path information: “Subsystem Link Information Number” = 0


CONT0 (or HD0) Controller 0
6 Local Port (or HPx) … FE Port #: 3, 2, 1
7 Host Type 00:Default (1) iSN Config/Port Config
8 Link Attach 2:Only FC-AL (1) iSN Config/FC Port Config
(1)
9 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Config/FC Port Config
10 Switch (or FC Loop ID) Switch=01 (2)/ALPA=E8 / Port ID=0000E8 iSN
Switch=00, 01, 02 …..
Config/FC Port Config
11 Data Rate (or FC speed) .. [Mbps] iSN

2nd Path information: “Subsystem Link Information Number” = 1


CONT1 (or HD1) Controller 1
12 Local Port (or HPx) … FE Port #: 3, 2, 1
13 Host Type 00:Default (1) iSN Config/Port Config
14 Link Attach 2:Only FC-AL (1) iSN Config/FC Port Config
(1)
15 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Config/FC Port Config
16 Switch (or FC Loop ID) Switch=01 (2)/ ALPA=E8 / Port ID=0000E8 iSN
Switch=00, 01, 02 …..
17 Data Rate (or FC speed) .. [Mbps] iSN Config/FC Port Config

(1) Fixed values.


(2) Proposed value. See also the notes about the correspondence between Switch, ALPA and Port ID.

Bull P&S/SCCPage 15 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Appendix 4 – Primary Site Information table (SAN


Configuration)
Primary Site Name: ________
Cfg
Item Parameter Value to Collect or Configure Tool Comment
Array Model …
Array Nickname … iSM cut&paste from iSM
1 IP address of CONT0 … iSN
2 IP address of CONT1 … iSN If any
SAA (Subsystem Absolute Right click on Array
3 Address) … iSM Properties
cut&paste from iSM

4 Number of Remote arrays … 1 or 2


For one Remote array: 2 remote arrays  2
data sheets
Name of the Remote array …
Number of paths (or FC 1 or 2 (or more)
5 …
Links) to the remote array

1st Path information: “Subsystem Link Information Number” = 0


CONT0 (or HD0) Controller 0
6 Local Port (or HPx) … FE Port #: 3, 2, 1
7 Host Type 00:Default (1) iSN Config/Port Config
8 Link Attach 3:Only Fabric (1) iSN Config/FC Port Config
(1)
9 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Switch (or FC Loop ID) Not applicable
10 Data Rate (or FC speed) .. [Mbps] iSN Config/FC Port Config
11 Port_ID (2) 3bytes Fabric address
0x .. .. .. Switch

2nd Path information: “Subsystem Link Information Number” = 1


CONT1 (or HD1) Controller 1
12 Local Port (or HPx) … FE Port #: 3, 2, 1
13 Host Type 00:Default (1) iSN Config/Port Config
14 Link Attach 3:Only Fabric (1) iSN Config/FC Port Config
(1)
15 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Switch (or FC Loop ID) Not applicable
16 Data Rate (or FC speed) .. [Mbps] iSN Config/FC Port Config
17 Port_ID (2) 3bytes Fabric address
0x .. .. .. Switch

(1) Fixed values.


(2) Use Switch tools (Telnet, WebTools) to collect this information.

Bull P&S/SCCPage 16 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

Appendix 5 – Secondary Site Information table (SAN


Configuration)
Secondary Site Name: ________
Cfg
Item Parameter Value to Collect or Configure Tool Comment
Array Model …
Array Nickname … iSM cut&paste from iSM
1 IP address of CONT0 … iSN
2 IP address of CONT1 … iSN If any
SAA (Subsystem Absolute Right click on Array
3 Address) … iSM Properties
cut&paste from iSM

4 Number of Remote arrays … 1 or 2


For one Remote array: 2 remote arrays  2
data sheets
Name of the Remote array …
Number of paths (or FC 1 or 2 (or more)
5 …
Links) to the remote array

1st Path information: “Subsystem Link Information Number” = 0


CONT0 (or HD0) Controller 0
6 Local Port (or HPx) … FE Port #: 3, 2, 1
7 Host Type 00:Default (1) iSN Config/Port Config
8 Link Attach 3:Only Fabric (1) iSN Config/FC Port Config
(1)
9 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Switch (or FC Loop ID) Not applicable
10 Data Rate (or FC speed) .. [Mbps] iSN Config/FC Port Config
11 Port_ID (2) 3bytes Fabric address
0x .. .. .. Switch

2nd Path information: “Subsystem Link Information Number” = 1


CONT1 (or HD1) Controller 1
12 Local Port (or HPx) … FE Port #: 3, 2, 1
13 Host Type 00:Default (1) iSN Config/Port Config
14 Link Attach 3:Only Fabric (1) iSN Config/FC Port Config
(1)
15 Mode 0040 (or 2:RD Port for FDA4900) iSN Config/FC Port Config
Switch (or FC Loop ID) Not applicable
16 Data Rate (or FC speed) .. [Mbps] iSN Config/FC Port Config
17 Port_ID (2) 3bytes Fabric address
0x .. .. .. Switch

(1) Fixed values.


(2) Use Switch tools (Telnet, WebTools) to collect this information

Bull P&S/SCCPage 17 of 18 October 2006


StoreWay FDA - RDR Configuration Planning Guide V2.9

This page is intentionally left blank.

Bull P&S/SCCPage 18 of 18 October 2006

You might also like