1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 1 /10

1 Gbit/sec to 2 and 4 Gbit/sec

SAN Migration Flow Chart

Audience: Brocade partners with many OEMs and resellers who supply switches and
directors to end users. Many of these partners provide direct support for the switches and
directors they sell. In some cases, the migration processes supported by Brocade Partners
will differ from the guidelines Brocade presents in this document. Please work with your
support provider to determine the appropriate migrations steps for your SAN.

THE INFORMATION PROVIDED IS PROVIDED ON AN "AS-IS" BASIS AND

IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. THE
FOLLOWING INFORMATION DOES NOT MODIFY ANY WARRANTIES,
REPRESENTATIONS OR OBLIGATIONS IN ANY WRITTEN AGREEMENT
WITH BROCADE. ACCORDINGLY, PROVISION BY BROCADE OF THE
INFORMATION IN THIS DOCUMENT SHALL CREATE NO ADDITIONAL
WARRANTIES, LIABILITIES, OR OBLIGATIONS OF ANY KIND AND
BROCADE ASSUMES NO LIABILITY RELATED TO THE FOLLOWING
INFORMATION. COMMERCIAL ASPECTS OF SUPPORT AND THE
CUSTOMER RELATIONSHIP ARE COVERED BY FORMAL CONTRACTS.

© 2005 Brocade Communications Systems, Inc. All Rights Reserved. 03/05

Brocade, the Brocade B weave logo, Fabric OS, Secure Fabric OS, and SilkWorm are registered
trademarks of Brocade Communications Systems, Inc., in the United States and/or in other
countries. FICON is a registered trademark of IBM Corporation in the U.S. and other countries. All
other brands, products, or service names are or may be trademarks or service marks of, and are
used to identify, products or services of their respective owners.

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 2 /10

SAN Migration
PROCESS OVERVIEW

ƒ SAN Architecture
Assess the SAN ƒ Logistics- Rack space. Power and Cable
targeted for
ƒ Host rebooting consideration
migration
ƒ Existing Switch configuration

Choose the right

migration Strategy ƒ Online or offline Migration
to match
expectations

Develop a plan ƒ Single Fabric Online Migration

based on the type ƒ Offline Fabric Migration
of migration ƒ Redundant Fabric Migration

No Is the plan ƒ Schedule upgrade time

acceptable?

yes

ƒ Prepare SAN to perform one or more of

Perform the the following steps if required.
necessary ƒ Fabric OS upgrade
migration
pre-requisites
ƒ Core PID Format Update
ƒ Persistent binding PID method
ƒ Host reboot

ƒ 2/4 Gbit/sec switch preparation and

Migrate the
switches Migration
ƒ Zoning configuration update

ƒ Verify the functionality of the new

2/4 Gbit/sec SAN
ƒ No fabric segmentation
Validate 2/4 Gbit ƒ Zoning verification
SAN
ƒ Successful login of all attached devices
ƒ Host access to the device

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 3 /10

Fabric Assessment

Existing Fabric Existing Fabric Host Reboot Logistics New 2/4 Gbit/sec
Switch Switch

Is there Is host Replacing

any topology Is Core
hba config.file Enough rack or adding a
change PID change
changes? (PID space ? 2/4Gbit/sec
planned ? required?
bindings) switch?

Is auto-
Any plan Name, IP
negotiation Is FOS
to upgrade Enough Domain. setup
sufficient ? upgrade
HBA to power? consideration
required?
2/4Gbit/sec?

What is
Any other Is Host
trunking Necessary
configuration, reboot
strategy ? cables
parameters acceptable if
ready?
update? required? = Critical items

What is the
zone import
strategy to the
2/4 Gbit fabric?

This section details the various aspects of a Migration that

need to be considered when developing a Migration strategy

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 4 /10

Migration Strategy

Is
Redundant No Is Host reboot No there a window No
Fabric ? allowed? for SAN
downtime?

yes yes yes

Configured
No Is Core PID
No redundant
format already
paths for all
updated?
devices?

yes yes

Is the
Is multi-pathing No Fabric OS
No
software used for already
all devices ? updated ?

yes
yes
Is multi-
No
Is path software
No performance used for all
degradation devices ?
acceptable ?
yes
yes
No Is the fabric
Are both resilient ?
No redundant I/O
paths open to all
devices? yes
Is
yes performance
No
degradation
Is acceptable?
downtime for a Follow the steps for
single path Redundant Fabric
device Migration yes
acceptable?
Are
No frequent fabric
Follow the steps for an No
interruptions
Offline Fabric Migration
acceptable?

yes

Follow the steps for

Online Migration

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 5 /10

Offline Fabric
Migration Offline Fabric Migration Procedure

Schedule a time to
bring the fabric offline.

Planning No
Incremental
The fabric remains segmented Migration?
unless the Core PID Format is
The fabric stays down until all switches
changed on all switches in the yes are migrated. No Core PID Format change
existing fabric
is required.

Is Core
Follow the Core No PID Format
PID Update
already
Procedure
set ?

yes

Prepare 2/4 Gbit/sec

switch parameters ,
set Domain ID

Import the zoning configuration to at least one switch when

Import/Update the fabric is replaced with new switches. The zone
Zoning configuratiuon is propagated to all adjecent switches during
an incremental upgrade.

Move the host and

Is Host storage cable
HBA Persistent No connections to the
bindings method corresponding
by PID ? 2/4 Gbit/sec switch
ports

yes

Follow the PID

Persistent binding Validate the fabric.
procedure

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 6 /10

Single Fabric Online Migration Procedure

Single Fabric Online

Migration

Select a Switch that

needs to be replaced.
one

Does this
No switch have an
active I/O path
open?

yes

Failover to alternate
open path on other
switch(s).

WARNING : This strategy assumes an

incremental switch replacement. Make sure
all devices have an alternate open path
before disabling the existing switch.
Disabling or enabling a switch can cause
Prepare the fabric segmentation and a fabric build. I/O
new switch may pause for the duration of these events.
parameters, set
Domain ID

Move all device

connections to the
new switch

Failback and restore

the path on the new
switch if necessary

All existing fabric

switches have No
been replaced?

yes

Validate the new

fabric

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 7 /10

Redundant Fabric
Online Migration

Ensure from
multi-pathing software,
that all paths are open to Are both
all devices that must No redundant I/O
remain online during the paths open to all
migration devices?

yes
Prepare devices with a
single path for
downtime

Select a fabric for

migration. Redirect all
active I/Os from this
fabric to an alternate
open fabric

Follow the steps for

Offline Fabric Migration

Restore the I/O paths

on the upgraded
2/4 Gbit/sec fabric

Are all fabrics No

migrated to
2/4 Gbit/sec ?

yes

Verify all fabrics

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 8 /10

Core PID Update Procedure

No * Switch FOS
< 2.4.1a or
3.0.1c ?

yes
Optional step
( Strongly recommend
to upgrade to latest Disable switch and
acceptable FOS level) upgrade to the latest
Fabric OS
on all existing fabric
switches

Disable the switch and

set the
Core PID format to 1
on all switches

Enable switches and

verify the fabric
( No segmentation)

Return

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 9 /10

PID Persistent Binding

Procedure

Host HBA
No config.file update &
reboot
allowed ?

yes

Move storage port Move host and storage

cable connections to cable connections to
corresponding 2/4 Gbit corresponding 2/4Gbit
switch port #+16 switch port #

If zoning by PID , make

appropriate zone Update HBA config file
changes to reflect the with new PID and
correct storage port reboot the host
number .

Validate the fabric

( No segmentation)

Return

V1.3
1 Gbit/sec to 2 and 4 Gbit/sec SAN Migration Page 10 /10

2/4 Gbit Switch

Paramaters & Domain
ID Set Procedure

No
Replacing an
existing switch ?

When adding a new yes

switch
set the unique Set the matching
Domain ID, switch Domain ID , switch
name. name, IP address and
configuration file
settings

Clear the zone

configuration on the
2/4 Gbit switch

Disable the switch

being replaced and
Migrate to the
2/4 Gbit switch

All existing
switches replaced No
for
Non-incremental
Migration?

yes

Return

V1.3