chaunceyschwartz simplified integration multi vendor

8/13/2019 ChaunceySchwartz Simplified Integration Multi Vendor

http://slidepdf.com/reader/full/chaunceyschwartz-simplified-integration-multi-vendor 1/27

Simplified Integration & Management in

Multi-Vendor SANs

Chauncey Schwartz

Senior Technical Marketing Manager

QLogic



Simplified Integration & Management in Multi-Vendor SANs© 2012 Storage Networking Industry Association. All Rights Reserved.

22

SNIA Legal Notice

The material contained in this tutorial is copyrighted by the SNIA unless otherwisenoted.

Member companies and individual members may use this material in presentationsand literature under the following conditions:

Any slide or slides used must be reproduced in their entirety withoutmodification

The SNIA must be acknowledged as the source of any material used in thebody of any document containing material from these presentations.

This presentation is a project of the SNIA Education Committee.

Neither the author nor the presenter is an attorney and nothing in thispresentation is intended to be, or should be construed as legal advice or an opinionof counsel. If you need legal advice or a legal opinion please contact your attorney.

The information presented herein represents the author's personal opinion andcurrent understanding of the relevant issues involved. The author, the presenter,and the SNIA do not assume any responsibility or liability for damages arising out ofany reliance on or use of this information.NO WARRANTIES, EXPRESS OR IMPLIED. USE AT YOUR OWN RISK.




33

Abstract

Simplified Integration & Management in Multi-Vender

SANsSituation: Rapidly increasing requirements for storage,IT initiatives driving virtualization across all aspects ofthe infrastructure, cloud-enabling the environmentProblem Statement: Data Center Managers face afundamental task in figuring out how to integrate SANenvironments over multi-vender and multi-protocolinfrastructures.

Resolution: This session will review methods toconnect together multi-vendor SANs without loosingmanagement function and cost while increasing multi-vender interoperability.




44

Learning Objectives

Learning Objective 1: Become familiarwith the terminology relating toTransparent SAN technologies

Learning Objective 2: Understand the solution setsand challenges inherent in integrating a multi-venderSAN infrastructure

Learning Objective 3: Evaluate the potential solutionsfor integrating multi-protocol and multi-vender SANinfrastructures




Agenda

Connections and PortOverview

Issues and Responses

Virtualization

Blade Enclosures

Potential Use Cases

Sample Setup of Virtual

Switch

5



Connections and Port Overview




F_Port

N_Port

E_Port

N_Port

N_Port N_Port

F_PortE_Port

Inter-Switch Link

Traditional Interconnect Port Types

TraditionalF_Port

N_Port

E_Port

Relationship1:1

1 N_Port =

1 WWN



Issues and Responses




The Issue Part 1 – Virtualization

1:1 relationship becomesinadequate

Need a method to develop

a many virtual to one

physical port relationship

N_Port ID Virtualization

(NPIV)

NPIV allows a single physicalN_Port to register multiple

World Wide Port Names

(WWPNs) and V-N_Port

identification numbers.9

N_Port

The Issue

VM1

VM2

VMn

1 ID

WWWN1

V-N_Port

The Answer Part 1

VM1

VM2

VMnn IDs

WWWN1

WWWN2

WWWNn




The Issue Part 2 – Blade Servers

Blade servers increase server density resulting in theneed for switch port aggregation capability

Blade switch module to consolidate blade servers to

external SAN switches (top of rack role)

Concern for domain ID limit of 239

10

Blades

Many

HBA

Ports

F _P or t s

E_Port

Domain ID Domain ID




The Answer Part 2 – Switch

Virtualization

Extend the idea of NPIV to the fabric (F_Port level)

Multiple approaches to switch NPIV were developedBrocade’s access gateway

Cisco’s N_Port virtualization

QLogic’s transparent routing

Transparent switch for blade server racks (all FC switch vendors)

11

F_PortDomain ID

N_Port

Existing

SAN

F_Port

F_Port

N_Port

N_Port

Transparent Architecture

Domain ID

Existing

SAN

F_Port

N_Port

N_Port

Looks like this to Existing SANManage End Points As Normal




Considerations for NPIV on Switch

Address potential domain ID limit

(239)Multi-vendor fabric without loss of

management or function

Manage end points as normal

Support both new SAN management

and transparent integration to

existing SAN

Granularity strategy – per port orwhole switch transparent

Cost effective transition to new

technologies12

Ch t i ti f T t Bl d




Characteristic of Transparent Blade

Switch

SAN connectivity as a N_Port

Does not have constraints of FC switchDoman proliferation

Interoperability – avoids reduced feature set likely required in

multivendor networks

All ports are transparent to fabricMany to one multiplexing

All or none approach

13

Blades

Many

HBA

Ports

F _P or t s

N_Port

Ch t i ti f E t l Vi t l




Characteristic of External Virtual

Switches

SAN connectivity as a N_PortDoes not have constraints of FC switch

Doman proliferation

Interoperability – avoids reduced feature set likely required in

multivendor networks

Granularity varies by vendor

All or none

Port level

14




External Virtual Switch Granularity

All ports or none approach

Reduces domain ID consumptionLocal communication requires hairpin through fabric

Port level approach

Reduces domain ID consumption

Flexible use of other ports

15

F_PortF_Port

Domain ID

N_Port




Benefits of Virtualizing The Switch

Reduce number of domain-id’sneeded (max 239)

Provide heterogeneous multi-vendor switch fabrics

without loss of management or function

More interoperable than switch-to-switch functions

Simplify connection of blade servers to external

fabrics

A NPIV transparent switch is less expensive than a

full-function switch

Manage end points as normal16



Virtual Switch Possible Use Cases




Use Case 1: Migrate to the latest technology

Upgrade legacy 2 Gbps and 4 Gbps SANsNPIV and Virtual Switch for heterogeneous SAN attach

Keep existing services running while bringing new systems online

Ability to share resources across SANs without disruption improves cost-effectiveness

8GbpsSAN

Servers

(HBAs)

ActiveLegacy

SAN

Array

Servers (HBAs)

ArrayVirtual Switch

between SANs

New

switch(s)

Existing

switch(s)

18

Domain ID

Existing

SAN

F_Port

N_Port

N_Port

Looks like this to Existing SAN




Use Case 2: Backup SAN uti lizing TR

Virtual

switch(s)

Backup SAN

BackupServers

Primary DataCenter

Virtual Switch

to Backup

SAN

Backup

storage

Arrays

Servers

(HBAs)

Arrays

Existing

fabric

SAN accessed for dedicated and secure backup

No disruption to existing fabric or LAN

Improved fault tolerance

19




QLogicswitch(s)

Departmental SAN

Arrays

Primary Data Center

Virtual Switch

to

Corporate

SAN

Servers(HBAs)

Storage

Arrays (New Finance SAN)

Use Case 3: Departmental build-out

Brocade orCisco

fabric

(Existing fabrics)

Build and manage a new

departmental fabric inexpensively

Seamless, non-disruptive connection to existing

fabrics.

Simplify server upgrades and replacement.

20



Sample Setup of Virtual Switch



1 S t th QL i t t t “ TR”




SB5800 TR port #3

Brocade name server

1. Set the QLogic port type to “ TR”

(QuickTools or CLI)

Port is displayed as

TR_port.

N

QLogic TR_port logs in

as an “N_port” on the

Brocade switch and is

displayed in the Brocade

name server.

Sharing will not yet

occur – devices must be

mapped.

“I see a

new

N_port”

23

2 Map Devices (4 clicks in




2. Map Devices (4 clicks inTR Mapping Manager)

(1, 2) Select storage or

server devices from the

QLogic and Brocade fabrics

that you wish to share.

(3) Select a configured TRport for those devices to

use.

(4) Click OK.

Devices

attached

to QLogic

switch

Devices on

Brocade

fabric

Avai lable

TR ports

on QLogic

switch

12

3

4

24




3. Zoning method for both fabrics

Brocade

Zones must also be created on

the remote fabric before

devices can communicate.

Inter-fabric zones are

automatically created on theQLogic switch.

Wizard generates zoning

commands for the remote

fabric which can be easily

copied/pasted directly into theremote fabric management

tools.

25



Discussion and Questions



Simplified Integration & Management in Multi-Vendor SANs© 2012 Storage Networking Industry Association All Rights Reserved

2727

Attribution & Feedback

Please send any questions or comments regarding this SNIA Tutorial to

[email protected]

The SNIA Education Committee would like to thank the

following individuals for their contributions to this Tutorial.

Authorship History

Chauncey Schwartz, QLogic 08/23/2012:

Updates:

Additional Contributors

Marty Holmes, QLogic

mailto:[email protected]

mailto:[email protected]

chaunceyschwartz simplified integration multi vendor

Documents