Configuring a Dual Fabric SAN Environment

Similar documents
IVR Zones and Zonesets

Inter-VSAN Routing Configuration

CCIE Data Center Storage Networking. Fibre Channel Switching Configuration. Nexus 5500UP FC Initialization Allocate interfaces as type FC

Configuring Fibre Channel Interfaces

Interoperability Limitations

Configuring VSANs and Interfaces

Configuring Fabric Configuration Server

Configuring PortChannels

Troubleshooting Distributed Device Alias Services

Troubleshooting Zones and Zone Sets

Configuring FCoE NPV. Information About FCoE NPV. This chapter contains the following sections:

Managing Zones and Zone Sets

Getting Started. Enabling SSH

Configuring and Managing Zones

Implementing Smart Zoning On IBM Cisco SANs

P Commands. Send documentation comments to CHAPTER

Cisco MDS 9000 Family Blade Switch Solutions Guide

Advanced Fibre Channel Features

Configuring and Managing Zones

FCoE Configuration Between VIC Adapter on UCS Rack Server and Nexus 5500 Switch

Configuring and Managing Zones

MDS 9020 Switch Interoperability

Large SAN Design Best Practices Using Cisco MDS 9700 and MDS 9500 Multilayer Directors

MDS to MDS Basic Configuration with FCIP

Nexus 5000 NPIV FCoE with FCoE NPV Attached UCS Configuration Example

Fibre Channel Gateway Overview

Interoperability Guidelines for Non-Cisco Switches

Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x

Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide

MDS 9000 Core with Brocade 3900/12000 Edge Topology

IBM Europe Announcement ZG , dated February 13, 2007

FCoE Cookbook for HP Virtual Connect

Tech Note on Priority Transmit B2B Credits in MDS Switches

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(4c)

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Release 5.0(1a)

Configuring SAN Port Channel

Fabric Manager Client

Configuring Fabric Congestion Control and QoS

Dell Networking MXL and PowerEdge I/O Aggregator with Cisco Nexus 5000 series fabric mode Config Sheets

Designing and Deploying a Cisco Unified Computing System SAN Using Cisco MDS 9000 Family Switches

Troubleshooting N-Port Virtualization

Symbols. Numerics INDEX

F port channel trunk from MDS 9148 (NPV) to MDS 9509 (NPIV) Configuration Example

Configuring Microsoft Windows XP iscsi Host to MDS/IPS 8

CCIE Data Center Storage Networking. Fibre Channel Switching

Using the Cisco NX-OS Setup Utility

Storage Networking Cisco MDS 9148 Beta Testing

Using the Cisco NX-OS Setup Utility

Managing FLOGI, Name Server, FDMI, and RSCN Databases

Configuring Users and Common Roles

Cisco MDS 9000 Family NX-OS Licensing Guide, Release 6.x

Scheduling Maintenance Jobs

Configuring Zones and Zone Sets

Troubleshooting Your Fabric

This appendix covers the following topics: Understanding the Concepts of Storage Networking Understanding the Storage Networking Protocols

Configuring Fabric Congestion Control and QoS

Cisco MDS 9000 Family SAN Volume Controller Configuration Guide. Cisco MDS SAN-OS Release 1.3 September, 2004

PracticeTorrent. Latest study torrent with verified answers will facilitate your actual test

Cisco MDS NX-OS Release 6.2Configuration Limits 2

Configuring the Fibre Channel Gateway

IBM To Resell Cisco Systems MDS 9000 Multilayer Switch and Director Family of Intelligent Storage Networking Products

Cisco I/O Accelerator Deployment Guide

Cisco MDS 9000 Series NX-OS Interfaces Configuration Guide

MDS 9000 Switch and McData Dual Core Topology (Interop Mode 1)

F Commands CHAPTER. Send documentation comments to

University of Jordan Faculty of Engineering & Technology Computer Engineering Department Advance Networks Laboratory Exp.4 Inter-VLAN Routing

Intermixing Best Practices

vsphere 6.0 with HP ProLiant Gen9 Servers, OneView, 3PAR, Cisco Nexus 5600 and Brocade 6510 Deployment Guide

Cisco Nexus B22HP. Design and Deployment Guide. September, For further information, questions and comments please contact

zseries FICON and FCP Fabrics -

Deploying IP Storage Solutions with the Cisco MDS 9000

Managing FLOGI, Name Server, FDMI, and RSCN Databases, page 1

UCS Direct Attached Storage and FC Zoning Configuration Example

Dell Networking MXL / PowerEdge I/O Aggregator with Cisco Nexus 5000 series NPV mode and Cisco MDS 9100 fabric switch Config Sheets

Configuring Fabric Congestion Control and QoS

Cisco Nexus B22 Blade Fabric Extender for IBM

Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide

Cisco Nexus 5600 Series NX-OS SAN Switching Configuration Guide, Release 7.x

QUESTION: 1 You have been asked to establish a design that will allow your company to migrate from a WAN service to a Layer 3 VPN service. In your des

Cisco Nexus 9000 Series NX-OS FC NPV Configuration Guide, Release 9.x

This section contains context-sensitive Online Help content for the Web Client > Monitor tab.

Cisco MDS 9000 Family CIM Server Support

Direct Attached Storage

Flash Devices in the Cisco MDS 9000 Supervisor Module. External CompactFlash in the Cisco MDS 9000 Supervisor Module.

Use Case: Three-Tier Application with Transit Topology

Product Overview. Send documentation comments to CHAPTER

Cisco Cisco ADVDESIGN. Download Full Version :

Configuring Q-in-Q VLAN Tunnels

Configuring Cisco Unified FEX Nexus 2348UPQ with Fiber Channel Interfaces

Cisco Nexus 5000 Series NX-OS SAN Switching Configuration Guide

iscsi High Availability Design using the MDS 9000 Family of Multilayer Switches


P Commands. Cisco MDS 9000 Series Command Reference 1

Implementing the ERSPAN Analytics Feature on Cisco Nexus 6000 Series and 5600 Platform Switches

UCS Engineering Details for the SAN Administrator

Vendor: Cisco. Exam Code: Exam Name: Introducing Cisco Data Center Technologies. Version: Demo

VPLEX Networking. Implementation Planning and Best Practices

I Commands. I Commands 1

Storage Media Encryption Overview

Troubleshooting Cisco Data Center Unified Fabric

Transcription:

CHAPTER 10 Dual fabric SAN environments are an important configuration requirement. You can use CSM modules in combination with the Inter-VSAN Routing (IVR) feature to operate across two isolated fabrics. This chapter includes the following sections: Overview, page 10-2 Basic SVC Requirements, page 10-2 Dual Fabric Prerequisites, page 10-2 Sample Configuration, page 10-2 10-1

Overview Chapter 10 Overview Redundant isolated fabrics (fabrics without an ISL connecting them) are used to ensure that disruptions in one fabric do not affect the other. Hosts and disk subsystems in such an environment can be configured to ensure that at least one port remains attached to each fabric. Basic SVC Requirements SVC has the following requirements: All SVC nodes must be able to communicate with each other in the management VSAN. All SVC nodes must be able to use the same preferred target controller port for a given Mdisk. In a redundant, dual fabric configuration, the Cisco MDS Inter-VSAN Routing (IVR) feature must be used in order to satisfy these basic SVC requirements. IVR provides the same benefit of keeping the two fabrics separate while providing the connectivity required to implement SVC. Refer to Cisco MDS 9000 Family Configuration Guide for more information on IVR. Dual Fabric Prerequisites To configure a dual fabric SAN environment using IVR and SVC, verify the following requirements: Every VSAN must be assigned a unique number. This number should not be used for any other VSAN in both fabrics. This ensures that the IVR VSAN is not carried across any other non-dedicated dual-fabric E port. The same IVR configuration must be configured in each switch in each fabric. The default zone in the transit VSAN should be set to deny. The transit VSAN must only be dedicated for the dual fabric purpose. New interfaces should not be added to this VSAN once the configuration is implemented. Trunk Mode must be enabled for the transit VSAN. Route advertisement must be disabled for the transit VSAN. The Domain ID for the transit VSAN must be static and domain merges must be disabled on this VSAN. Topology discovery must be disabled for the transit VSAN. Sample Configuration Figure 10-1 displays a dual fabric SAN environment example used in this configuration. The procedure to configure this sample scenario is provided after the illustration. 10-2

Chapter 10 Sample Configuration Figure 10-1 Traffic Isolation and Connectivity Using SVC and IVR Host 1 fc8/3 Initiator VSAN 3 Management Transit fc8/17 VSAN 4 VSAN 20 Switch Target VSAN 2 fc8/2 fc7/3 fc7/2 fc7/17 Switch Initiator VSAN 13 Management VSAN 14 Target VSAN 12 120127 IBM controller To configure a dual fabric SAN environment in the first fabric, follow these steps: Step 1 Get the switch WWN information for both switches. switch1# show wwn switch Switch WWN is 20:00:00:05:30:00:41:de Step 2 switch2# show wwn switch Switch WWN is 20:00:00:05:30:00:07:1e Create the VSANs in Switch1. switch1# configure terminal switch1(config)# vsan database switch1(config-vsan-db)# vsan 2 switch1(config-vsan-db)# vsan 2 interface fc8/2 switch1(config-vsan-db)# vsan 3 switch1(config-vsan-db)# vsan 3 interface fc8/3 switch1(config-vsan-db)# vsan 4 switch1(config-vsan-db)# vsan 20 switch1(config-vsan-db)# exit switch1(config)# <-- target port <-- initiator port Step 3 Set the static domains in Switch 1. Sw1(config)# fcdomain domain 2 static vsan 2 Sw1(config)# fcdomain domain 3 static vsan 3 Sw1(config)# fcdomain domain 4 static vsan 4 Sw1(config)# fcdomain domain 20 static vsan 20 Step 4 Configure the SVC interface into the correct VSANs in Switch 1. switch1(config)# int svc 1/1-2 switch1(config-if)# no initiator vsan 1 switch1(config-if)# initiator vsan 2 switch1(config-if)# no target vsan 1 switch1(config-if)# target vsan 3 switch1(config-if)# no mgmt vsan 1 switch1(config-if)# mgmt vsan 4 switch1(config-if)# exit 10-3

Sample Configuration Chapter 10 Step 5 Set the default zone configuration for the transit VSAN in Switch 1. switch1(config)# no zone default-zone permit vsan 20 Step 6 Configure the target and SVC initiators in a zone in Switch 1. switch1(config)# zone name z_2 vsan 2 switch1(config-zone)# member pwwn 20:06:00:a0:b8:0f:6c:34 switch1(config-zone)# member pwwn 27:8d:00:05:30:00:33:2a switch1(config-zone)# member pwwn 27:89:00:05:30:00:33:2a switch1(config-zone)# exit switch1(config)# zoneset name zs_2 vsan 2 switch1(config-zoneset)# member z_2 switch1(config-zoneset)# exit switch1(config)# zoneset activate name zs_2 vsan 2 <-- target <-- svc initiator <-- svc initiator Step 7 Configure the initiator and SVC targets in a zone in Switch 1. switch1(config)# zone name z_3 vsan 3 switch1(config-zone)# member pwwn 21:01:00:e0:8b:29:f0:04 switch1(config-zone)# member pwwn 27:8e:00:05:30:00:33:2a switch1(config-zone)# member pwwn 27:8a:00:05:30:00:33:2a switch1(config-zone)# exit switch1(config)# zoneset name zs_3 vsan 3 switch1(config-zoneset)# member z_3 switch1(config-zoneset)# exit switch1(config)# zoneset activate name zs_3 vsan 3 <-- initiator <-- svc target <-- svc target Step 8 Configure the SVC management N ports in a zone in Switch 1. switch1(config)# zone name z_4 vsan 4 switch1(config-zone)# member pwwn 27:90:00:05:30:00:33:2a switch1(config-zone)# member pwwn 27:8f:00:05:30:00:33:2a switch1(config-zone)# exit switch1(config)# zoneset name zs_4 vsan 4 switch1(config-zoneset)# member z_4 switch1(config-zoneset)# exit switch1(config)# zoneset activate name zs_4 vsan 4 <-- svc mgmt <-- svc mgmt Step 9 Enable and configure IVR using the switch WWNs (see Step 1 for the required WWNs). switch1(config)# ivr enable switch1(config)# ivr vsan-topology database switch1(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:05:30:00:41:de vsan-ranges 2,4,20 switch1(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:05:30:00:07:1e vsan-ranges 12,14,20 switch1(config-ivr-topology-db)# exit switch1(config)# ivr vsan-topology activate Step 10 Set up the IVR zone to allow SVC initiators in Switch 1 to talk to the target port in Switch 2. switch1(config)# ivr zone name ivr_2_12 switch1(config-ivr-zone)# member pwwn 27:8d:00:05:30:00:33:2a vsan 2 switch1(config-ivr-zone)# member pwwn 27:89:00:05:30:00:33:2a vsan 2 switch1(config-ivr-zone)# member pwwn 20:07:00:a0:b8:0f:6c:34 vsan 12 switch1(config-ivr-zone)# exit Step 11 Set up the IVR zone to allow SVC initiators in Switch 2 to talk to target port in Switch 1. switch1(config)# ivr zone name ivr_12_2 switch1(config-ivr-zone)# member pwwn 23:30:00:05:30:00:8d:e2 vsan 12 10-4

Chapter 10 Sample Configuration switch1(config-ivr-zone)# member pwwn 23:31:00:05:30:00:8d:e2 vsan 12 switch1(config-ivr-zone)# member pwwn 20:06:00:a0:b8:0f:6c:34 vsan 2 switch1(config-ivr-zone)# exit Step 12 Step 13 Set up the IVR zone to allow SVC management on both switches to talk to each other. switch1(config)# ivr zone name ivr_4_14 switch1(config-ivr-zone)# member pwwn 27:90:00:05:30:00:33:2a vsan 4 switch1(config-ivr-zone)# member pwwn 27:8f:00:05:30:00:33:2a vsan 4 switch1(config-ivr-zone)# member pwwn 23:34:00:05:30:00:8d:e2 vsan 14 switch1(config-ivr-zone)# member pwwn 23:35:00:05:30:00:8d:e2 vsan 14 switch1(config-ivr-zone)# exit Create the IVR zone set with the IVR zones and activate the IVR zone set. switch1(config)# ivr zoneset name ivr_zs switch1(config-ivr-zoneset)# member ivr_2_12 switch1(config-ivr-zoneset)# member ivr_12_2 switch1(config-ivr-zoneset)# member ivr_4_14 switch1(config-ivr-zoneset)# exit switch1(config)# ivr zoneset activate name ivr_zs Zone set activation is now initiated. Check inter-vsan zoneset status. If any VSANs are configured to permit the default-zone, then you must use the force option to activate the IVR zone set switch1(config)# ivr zoneset activate name ivr_zs force Zone set activation is now initiated. Check inter-vsam zoneset status. Step 14 Bring up all interfaces, including the E-port, for the IVR transit VSAN. switch1(config)# interface fc8/2, fc8/3 switch1(config-if)# no shutdown switch1(config-if)# exit switch1(config)# interface fc8/17 switch1(config-if)# switchport trunk mode on switch1(config-if)# switchport mode E switch1(config-if)# no shutdown switch1(config-if)# switchport trunk allowed vsan 20 switch1(config-if)# exit You have now configured the first fabric for the dual fabric SAN environment displayed in Figure 10-1. To configure a dual fabric SAN environments in the second fabric, follow these steps: Step 1 Step 2 Get the switch WWN information for both switches (see Step 1 in the previous procedure). Create the VSANs in Switch2. switch2# configure terminal switch2(config)# vsan database switch2(config-vsan-db)# vsan 12 switch2(config-vsan-db)# vsan 12 interface fc7/2 switch2(config-vsan-db)# vsan 13 switch2(config-vsan-db)# vsan 13 interface fc7/3 switch2(config-vsan-db)# vsan 14 switch2(config-vsan-db)# vsan 20 switch2(config-vsan-db)# exit <-- target port <-- initiator port Step 3 Set the static domains in Switch 2. switch2(config)# fcdomain domain 12 static vsan 12 10-5

Sample Configuration Chapter 10 switch2(config)# fcdomain domain 13 static vsan 13 switch2(config)# fcdomain domain 14 static vsan 14 switch2(config)# fcdomain domain 40 static vsan 20 Step 4 Configure the SVC interface into the correct VSANs in Switch 2. switch2(config)# int svc 2/1-2 switch2(config-if)# no initiator vsan 1 switch2(config-if)# initiator vsan 12 switch2(config-if)# no target vsan 1 switch2(config-if)# target vsan 13 switch2(config-if)# no mgmt vsan 1 switch2(config-if)# mgmt vsan 14 switch2(config-if)# exit Step 5 Set the default zone configuration for the transit VSAN in Switch 2. switch1(config)# no zone default-zone permit vsan 20 Step 6 Configure the target and SVC initiators in a zone in Switch 2. switch2(config)# zone name z_12 vsan 12 switch2(config-zone)# member pwwn 20:07:00:a0:b8:0f:6c:34 switch2(config-zone)# member pwwn 23:30:00:05:30:00:8d:e2 switch2(config-zone)# member pwwn 23:31:00:05:30:00:8d:e2 switch2(config-zone)# exit switch2(config)# zoneset name zs_12 vsan 12 switch2(config-zoneset)# member z_12 switch2(config-zoneset)# exit switch2(config)# zoneset activate name zs_12 vsan 12 <-- target <-- svc initiator <-- svc initiator Step 7 Configure the initiator and SVC targets in a zone in Switch 1. switch2(config)# zone name z_13 vsan 13 switch2(config-zone)# member pwwn 21:00:00:e0:8b:09:f0:04 switch2(config-zone)# member pwwn 23:32:00:05:30:00:8d:e2 switch2(config-zone)# member pwwn 23:33:00:05:30:00:8d:e2 switch2(config-zone)# zoneset name zs_13 vsan 13 switch2(config-zoneset)# member z_13 switch2(config-zoneset)# zoneset activate name zs_13 vsan 13 <-- initiator <-- svc target <-- svc target Step 8 Configure the SVC management N ports in a zone in Switch 1. switch2(config)# zone name z_14 vsan 14 switch2(config-zone)# member pwwn 23:34:00:05:30:00:8d:e2 switch2(config-zone)# member pwwn 23:35:00:05:30:00:8d:e2 switch2(config-zone)# zoneset name zs_14 vsan 14 switch2(config-zoneset)# member z_14 switch2(config-zoneset)# zoneset activate name zs_14 vsan 14 <-- svc mgmt <-- svc mgmt Step 9 Enable and configure IVR using the switch WWNs (see Step 1 in the previous procedure). switch2(config)# ivr vsan-topology database switch2(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:05:30:00:41:de vsan-ranges 2,4,20 switch2(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:05:30:00:07:1e vsan-ranges 12,14,20 switch2(config-ivr-topology-db)# exit switch2(config)# ivr vsan-topology activate Step 10 Set up the IVR zone to allow SVC initiators in Switch 1 to talk to the target port in Switch 2. switch2(config)# ivr zone name ivr_2_12 10-6

Chapter 10 Sample Configuration switch2(config-ivr-zone)# member pwwn 27:8d:00:05:30:00:33:2a vsan 2 switch2(config-ivr-zone)# member pwwn 27:89:00:05:30:00:33:2a vsan 2 switch2(config-ivr-zone)# member pwwn 20:07:00:a0:b8:0f:6c:34 vsan 12 switch2(config-ivr-zone)# exit Step 11 Set up the IVR zone to allow SVC initiators in Switch 2 to talk to target port in Switch 1. switch2(config)# ivr zone name ivr_12_2 switch2(config-ivr-zone)# member pwwn 23:30:00:05:30:00:8d:e2 vsan 12 switch2(config-ivr-zone)# member pwwn 23:31:00:05:30:00:8d:e2 vsan 12 switch2(config-ivr-zone)# member pwwn 20:06:00:a0:b8:0f:6c:34 vsan 2 switch2(config-ivr-zone)# exit Step 12 Step 13 Set up the IVR zone to allow SVC management on both switches to talk to each other. switch2(config)# ivr zone name ivr_4_14 switch2(config-ivr-zone)# member pwwn 27:90:00:05:30:00:33:2a vsan 4 switch2(config-ivr-zone)# member pwwn 27:8f:00:05:30:00:33:2a vsan 4 switch2(config-ivr-zone)# member pwwn 23:34:00:05:30:00:8d:e2 vsan 14 switch2(config-ivr-zone)# member pwwn 23:35:00:05:30:00:8d:e2 vsan 14 switch2(config-ivr-zone)# exit Create the IVR zone set with the IVR zones and activate the IVR zone set. switch2(config)# ivr zoneset name ivr_zs switch2(config-ivr-zoneset)# member ivr_2_12 switch2(config-ivr-zoneset)# member ivr_12_2 switch2(config-ivr-zoneset)# member ivr_4_14 switch2(config-ivr-zoneset)# exit switch2(config)# ivr zoneset activate name ivr_zs Zone set activation is now initiated. Check inter-vsan zoneset status. If any VSANs are configured to permit the default-zone, then you must use the force option to activate the IVR zone set switch1(config)# ivr zoneset activate name ivr_zs force Zone set activation is now initiated. Check inter-vsan zoneset status. Step 14 Bring up all interfaces, including the E-port, for the IVR transit VSAN. switch2(config)# interface fc7/2, fc7/3 switch2(config-if)# no shutdown switch2(config-if)# exit switch2(config)# interface fc7/17 switch1(config-if)# switchport trunk mode on switch1(config-if)# switchport mode E switch2(config-if)# no shutdown switch2(config-if)# switchport trunk allowed vsan 20 switch2(config-if)# exit You have now configured the second fabric for the dual fabric SAN environment displayed in Figure 10-1. 10-7

Sample Configuration Chapter 10 10-8