Brksan 1011 PDF

BRKSAN-1011
1-2-3 of SAN Migration
Bhavin Yadav, Technical Marketing Engineer

Cisco Data Center - Storage Area Networking
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#BRKSAN-1011
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Agenda
• Why Migrate?
• Migration Lifecycle
• Preparation, Planning, Design,
Licensing
• Interoperability Modes
• Migration Approach
• Configuration Migration
• Recap
• Additional Resources
Why Migration
• New Technology introduction
• SAN Consolidation
• New Vendor Introduction (Cisco MDS)
Migration: Adding New Technology
• New Technology:
• Low Latency All Flash Arrays (AFAs, NVMe)
• High performing applications
• High speed servers (16/32G)
• Possible Side Affects:

• Slow Drain
• Bandwidth Bottlenecks
• Mixed speed flows
HR SAN Marketing SAN Cisco Live SAN
Migration: SAN Consolidation

• Business Decisions:
• Reduced Operational cost
• Less  Power, Rack space, Higher Redundancy
• Improved scalability
• Better Performance
• Simplified Management
• Multiple logical fabrics (VSANs) over a

single physical SAN
BRKSAN-1011 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
New Vendor Introduction
(Cisco MDS)
• Issues:
• Vendor specific features and implementations
• Interoperability / Compatibility
• Results:
• Locked into a single vendor
• Forced to use legacy products
• Higher downtime, unexpected issues
• Future scalability issues
Migration Lifecycle
Pre-Migration Check List
• Verify multi-path redundancy for hosts and servers
• Use DCNM host path redundancy check feature
• Update HBA drivers and the switch firmware to match the latest device
interoperability matrix
• Interoperability Matrix for Cisco Nexus and MDS 9000 Products
• Collect domain IDs of all existing switches
• Including the FCID of the storage ports in use by AIX and HP-UX hosts
• Determine Zoning migration method
• Rip and Replace / Cap-N-Grow / Interop mode
Migration Preparation
• Inventory
• Compatibility
• Upgrade
• SAN Assessment
• Application Validation
Planning and Design
• Physical planning (*important*)
• Architectural Planning (Design)
• Software Interoperability Planning
• Licensing
Implementation
• Configuration Migration
• Switch configuration
• Services configuration
• Redundancy Configuration
Operate and Optimize… a continuous cycle
• Check application performance
• Match SLAs
• Optimizing and Monitoring using DCNM-SAN
• DCNM-SAN Health report
• Verify connectivity and redundancy
• Summary Dashboard
• SAN Discovery and Topology Mapping
• Inventory Management
• Inventory, configuration, and status
• Configuration backup
Migration Toolbox
Data Center Network Manager (DCNM)
Zone Migration Wizard
Cisco DCNM Zone Migration Wizard
• Login to DCNM as admin / equivalent rights
• Launch DCNM SAN client
Cisco DCNM Zone Migration wizard (contd…)
• Launch Zone Migration Wizard
• Perform 5-step migration process
What to Migrate?
• Configuration contains
• Management IP, Logs, Alerts, Error dumps, SNMP/Call Home alerts
• Fabric, Interface/Port, Trunk configuration
• Device Aliases, Zoning information, Domains
• Unique configuration
• Management IP, Alerts, SNMP strings, Call Home, etc.
• Most important and common
• Zoning information (~70% of configuration)
BRKSAN-1011 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Data Center Network Manager
Quick Overview
DCNM 10 Summary Dashboards
o Customizable
Layout with 16
different Dashlets
o Add and remove
Dashlets for a
custom view
o Auto Save your
custom layout
o Focus on what
matters in your
environment
Switch Health Score
Policy Based
configurable health score
See Health trend over

time
Quickly Navigate to
review warnings
See Health status on

Topology map
Migration Approach
Option 1: Rip and Replace
DCNM
• Remove the existing switches (Rip) MDS 1 Fabric A
and Install new MDS switches
(Replace)
• One fabric at a time, allows phased
Host
migration
Storage
Switch 1
• SAN functions on one fabric during
Migration
• After first MDS fabric is operational,
other non-MDS fabric is replaced Switch 2
with MDS using the same process
Fabric B
MDS 2
Pros and Cons of Rip and Replace
Pros Cons
• Less Risks • Need Multiple vendor expertise
• Quick Migration • Multipath is must
• No Interop mode needed
• Minimal downtime
• Safer rollback, if needed
Option 2: Cap and Grow Existing SAN
Existing Array
• Migrate the MDS switches in

parallel with the existing SAN Switch 1 Switch 2
infrastructure
• All New storage and hosts are
connected to the new MDS
switches Host
DCNM
• Migrate storage and hosts from New SAN
existing switches to the MDS MDS A

infrastructure in stages MDS B
New Array
New Host
Pros and Cons of Cap and Grow
• Pros • Cons
• Allows phased migration • Multiple vendor SAN exists for longer
• Preferred for Green Field install base time
• Pay as you go model • Two parallel infrastructures could be
running during migration
• SAN administrators have time to learn
new environment • May need additional hardware
interfaces
Option 3: Interop Migration
• Introducing the MDS switch in non-MDS fabric
• Cisco MDS can interoperate
• With Brocade and McDATA switches
• Expands scalability and functionality
Interoperate with non-Cisco FC Switches
Storage
• MDS switches are connected and
configured to the existing fabric Fabric A Fabric B
• Appropriate interop mode is set

MDS A
MDS B
• The third party switches are then
connected to the MDS switches
Switch 1
DCNM Switch 2
• Gradually move hosts/storage
connection from the third party
switches to the MDS fabric; one at a
time
Host
Pros and Cons of Interop Mode
• Pros • Cons
• Allows immediate port expansion • Multi-vendor switches interacting in
• MDS interop VSANs and non-interop the same fabric
VSANs can be concurrently used in • Firmware upgrade/downgrade on the
the same fabric 3rd party switches may be required
• Minimal or No down time • Some features may be limited or not
• Migrate at your pace supported in certain interop modes on
non-Cisco products
Note: Interoperability mode requires that Cisco MDS and Brocade switches are using one of the verified
version on the Cisco supported interoperability matrix:
Interoperability Matrix for Cisco Nexus and MDS 9000 Products
Interop mode migration steps
• Installation - (Preconfiguration - Management IP, SW Image, etc.)
• Configuration - Connect ISL between Brocade and MDS
• Verification - Verify configuration on MDS
• Validation – New config changes
• Verification – Migration of hosts and storage ports
• Finish – Convert interop VSAN to Default VSAN
Resources
• Interoperability Guide:
• http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/interoperability/matr
ix/intmatrx.html
• Storage Interoperability Matrix
• Fabric Services Interoperability Matrix
• Switch Interoperability Matrix
Switch Interoperability Matrix
• Verification: ASIC based interoperability
• The Condor (4 Gbps) ASIC : Brocade 48000
• The Condor 2 (8 Gbps) ASIC : Brocade 5100, DCX and DCX-4S Backbones
• The Condor 3 (10 and 16 Gbps) ASIC : Brocade 6510, DCX8510-4 and DCX8510-8
• The GoldenEye 2 : Brocade 300 (One ASIC) and 5300
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx/Matrix5.html)
Interoperability Challenges
Interoperability Challenges
• NCITS FC-SW-2 (T11) standard
• Partially followed
• Proprietary features
• Different switch vendors
• Different interpretations
• Result
• Interoperability Issues
Brocade Switch Modes
• Native Switch mode (Cisco MDS NPIV equivalent):
• Switch is part of the fabric
• Requires more physical ports
• Consumes fabric resources
• Can connect to FOS fabric only
• Access Gateway mode (Cisco MDS NPV equivalent):

• Reduces number of switches / physical ports requirement
• You can connect to a Fabric OS, M-EOS, or Cisco-based fabric
• No Interop Mode
MDS interoperability modes
• Cisco supports interoperability with other vendors
• MDS Native Mode (Default mode of all VSAN)
• Four different modes of interoperability
• Interop Mode 1 (all vendor switches need to be configured for their respective standards
based interop modes)
• Interop mode 2 (Brocade switches operating in Core PID 0)
• Interop mode 3 (Brocade switches operating in Core PID 1)
• Interop mode 4 (McDATA switches)
• Interoperability mode is per VSAN

• Different VSANs can operate simultaneously in different interop modes
Native MDS Mode
• No Interop settings required
on MDS
• MDS native mode is FC standard
compliant
• Ensures integration of blade servers
with embedded FC interconnect
• Limited support for Advanced
features (with non-cisco hardware)
• Trunking, Port Channels and VSAN
• Only the active zone set is
distributed
Interoperability Mode 1
• Interoperates with Brocade (Access Gateway mode) and McDATA switches
(Open Fabric mode)
• Domain IDs are restricted to the 97 to 127 range
• Operate with full functionality in other non-interop mode VSANs
• Only the active zone set is distributed
• Interoperates with Brocade native
mode
• Enables the MDS 9000 switch to
interoperate with Brocade switches in
native mode and core PID 0
• Some configuration changes may be
needed (VC_RDY disable) on the
Brocade switches
• No need to change the Brocade
switches
• Interoperates with Brocade native mode
• Enables the MDS switch to interoperate with Brocade switches in native mode
and Core PID 1 (i.e. Brocade switches with more than 16 ports)
• Some configuration changes (VC_RDY disable) may be needed on the
Brocade switches.
• No need to change the Brocade switches
• Supports all McDATA platforms operating in ‘McDATA Native Mode’
• MDS switches can be added to a McDATA without disruption
• Allowed domain range is 1–32
• FCID allocated will have domain identifier equal to base domain ID + 96
• This mode requires manually setting the VSAN WWN
• Only pWWN based zones are supported
• Default zone policy is distributed in the fabric
• IVR allocated virtual domain will always be from 1 to 31, but FCIDs will start
from 97-127
Cisco Compatible Interoperability modes
Cisco Interop Brocade Native Brocade AG McDATA McDATA OpenFabric
Mode Mode Mode Native Mode Mode
Native    
Mode 1    
Mode 2  (PID 0)   
Mode 3  (PID 1)   
Mode 4    
Limitations, Precautions, Verifications
• Enabling interop mode requires #switchdisable

• Domain ID change: Switch goes off line
• Select Principal switch to assign a domain ID
(Except in AIX/HP-UX network)
• Preferably configure a Static Domain ID
• Some configuration changes (VC_RDY disable)
may be needed on the Brocade switches.
Limitations, Precautions, Verifications
• Disabled features by Brocade in Interop mode

• Port zoning, Trunking, Fabric Assist, Secure Fabric
OS, and virtual flow control
• Set FC timers to default values and Use
enhanced device aliases
• Zoning changes should be activated from Cisco
MDS Switches
Summary
Summary
• SAN Migration is a multi-stage project
• preparation, planning, design, implementation phases
• Different migration strategies
• Rip & Replace
• Cap-N-Grow
• Interoperability Mode
• Various interoperability modes on MDS

• Interop Mode 1
• Interop mode 2 (Brocade Core PID 0)
• Interop mode 3 (Brocade Core PID 1)
• Interop mode 4 (McDATA switches)
Get ready for the NextGen SAN (What’s In It For ME !!!)
Business Reasons Technical Reasons
a. Scalable Infrastructure a. Inline Analytics
b. Improved Performance b. Proven Architecture
c. Future Investment Protect c. Any  Any interoperability
d. Multi-protocol Flexibility d. Built-in Redundancy
e. Simplified Management e. Programmability support
References
• Whitepapers:
• Transparently Migrate a SAN from a Heterogeneous Environment to a Cisco MDS 9000
Family SAN
• Cisco MDS Family Switch-to-Switch Interoperability Configuration Guide
• Cisco Data Center Interoperability Support Matrix
• Cisco DCNM Fundamentals Guide, Release 10.2(x)
• Interoperability Guide:
• Storage Interoperability Matrix
• Fabric Services Interoperability Matrix
• Switch Interoperability Matrix
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#BRKSAN-1011
• Please complete your Online Complete Your Online
Session Evaluations after each
session
Session Evaluation
• Complete 4 Session Evaluations
& the Overall Conference
Evaluation (available from
Thursday) to receive your Cisco
Live T-shirt
• All surveys can be completed via
the Cisco Live Mobile App or the
Communication Stations
Don’t forget: Cisco Live sessions will be available
for viewing on-demand after the event at
www.ciscolive.com/global/on-demand-library/.
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Tech Circle
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you
Additional Resources
Additional Resources: MDS
• Cisco MDS 9700 Series Datasheets
• Cisco MDS 9718 Multilayer Director
• Compare MDS 9700 models

• White papers
• Release Notes
• Configuration Guides
• Install and Upgrade Guides
Additional Resources: MDS
• Whitepapers:
• http://www.cisco.com/c/en/us/products/storage-networking/mds-9700-series-multilayer-
directors/white-paper-listing.html
• Interoperability and Compatibility Guides:
• Hardware and Software compatibility guide with other vendors
• Configuration Guides:
• http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-
software/tsd-products-support-configure.html

Brksan 1011 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brksan 1011 PDF

Uploaded by

Copyright:

Available Formats

BRKSAN-1011

1-2-3 of SAN Migration

Bhavin Yadav, Technical Marketing Engineer

• Possible Side Affects:

Migration: SAN Consolidation

• Multiple logical fabrics (VSANs) over a

• Launch DCNM SAN client

See Health trend over

See Health status on

with MDS using the same process

• Migrate the MDS switches in

existing switches to the MDS MDS A

• Appropriate interop mode is set

• Access Gateway mode (Cisco MDS NPV equivalent):

• Interoperability mode is per VSAN

• Enabling interop mode requires #switchdisable

• Disabled features by Brocade in Interop mode

• Various interoperability modes on MDS

• Compare MDS 9700 models

You might also like