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

Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o .
c o m
Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide

Cisco MDS 9000 Family NX-OS Release 5.0(1a) February 2010
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
Text Part Number: OL-19988-01
Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o . c o m
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide 2010 Cisco Systems, Inc. All rights reserved.
CONTENTS
New and Changed Information Preface
ix ix ix ix vii
Audience
Organization
Document Conventions
Related Documentation x Release Notes x Regulatory Compliance and Safety Information x Compatibility Information xi Hardware Installation xi Software Installation and Upgrade xi Cisco NX-OS xi Cisco Fabric Manager xii Command-Line Interface xii Intelligent Storage Networking Services Configuration Guides Troubleshooting and Reference xii Obtaining Documentation and Submitting a Service Request
1
xiii
xii
CHAPTER
Basic Inter-VSAN Routing Configuration
1-1
About Inter-VSAN Routing 1-1 IVR Features 1-2 IVR Terminology 1-3 IVR Configuration Limits 1-4 Fibre Channel Header Modifications 1-5 IVR Network Address Translation 1-5 IVR VSAN Topology 1-5 IVR Interoperability 1-6 Basic IVR Configuration Task List
1-6
Basic IVR Configuration 1-6 Configuring IVR and IVR Zones Using the IVR Zone Wizard Enabling IVR 1-7 Distributing the IVR Configuration Using CFS 1-7 Database Implementation 1-8 Enabling Configuration Distribution 1-8
1-7
Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide OL-19988-01
iii
Contents
Locking the Fabric 1-8 Committing the Changes 1-8 Discarding the Changes 1-9 Clearing a Locked Session 1-9 About IVR NAT and IVR Auto Topology Mode 1-9 IVR NAT Requirements and Guidelines 1-10 Transit VSAN Guidelines 1-11 Border Switch Guidelines 1-11 Enabling IVR NAT and IVR Auto Topology Mode 1-12 IVR Virtual Domains 1-13 Manually Configuring IVR Virtual Domains 1-13 Verifying an IVR Virtual Domain Configuration 1-14 Clearing an IVR fcdomain Database 1-14 IVR Zones and IVR Zone Sets 1-14 About IVR Zones 1-15 IVR Zone Limits and Image Downgrading Considerations 1-15 Automatic IVR Zone Creation 1-15 Configuring IVR Zones and IVR Zone Sets 1-16 About Activating Zone Sets and Using the force Option 1-18 Activating or Deactivating IVR Zone Sets 1-19 Verifying IVR Zone and IVR Zone Set Configuration 1-19 Clearing the IVR Zone Database 1-21 IVR Logging 1-21 Configuring IVR Logging Severity Levels 1-22 Verifying Logging Level Configuration 1-22 Database Merge Guidelines 1-22 Resolving Database Merge Failures Default Settings
2
1-28 1-24 1-25
IVR Auto Topology Mode Configuration Example
CHAPTER
Advanced Inter-VSAN Routing Configuration Advanced IVR Configuration Task List

2-1
2-1
Advanced IVR Configuration 2-2 IVR Service Groups 2-2 Service Group Guidelines 2-2 Default Service Group 2-3 Service Group Activation 2-3 Configuring IVR Service Groups 2-4 Copying the Active IVR Service Group Database
2-5
iv
OL-19988-01
Contents
Clearing IVR Service Group Database 2-5 Verifying IVR Service Group Configuration 2-5 Autonomous Fabric IDs 2-5 Autonomous Fabric ID Guidelines 2-6 Configuring Default AFIDs 2-6 Configuring Individual AFIDs 2-7 Verifying the AFID Database Configuration 2-7 IVR Without IVR NAT or IVR Auto Topology Mode 2-7 IVR Without IVR NAT or IVR Auto Topology Guidelines Domain ID Guidelines 2-8 Transit VSAN Guidelines 2-8 Border Switch Guidelines 2-9 Manually Configuring and Activating an IVR Topology 2-9 Manual Configuration Guidelines 2-9 Manually Configuring an IVR Topology 2-10 Activating a Manually Configured IVR Topology 2-11 Viewing an Active IVR Topology 2-11 Working with Existing IVR Topologies 2-11 Adding an IVR-Enabled Switch to an Existing IVR Topology 2-12 Adding VSANs to an Existing IVR Topology 2-12 Copying the Active IVR Topology 2-13 Clearing a Manually Configured IVR Topology Database 2-13 Verifying the IVR Topology 2-13 Migrating from IVR Auto Topology Mode to IVR Manual Topology Mode Persistent FC IDs for IVR 2-14 FC ID Features and Benefits 2-14 FC ID Guidelines 2-15 Configuring Persistent FC IDs for IVR 2-16 Verifying the Persistent FC ID Configuration
2-8
2-14
2-16
Advanced IVR Zones and IVR Zone Sets 2-17 IVR Zone Configuration Guidelines 2-18 Configuring LUNs in IVR Zoning 2-18 Configuring the QoS Attribute 2-19 Verifying the QoS Attribute For an IVR Zone 2-19 Renaming IVR Zones and IVR Zone Sets 2-19 Clearing the Configured IVR Zone Database 2-20 Configuring IVR Using Read-Only Zoning 2-20 Enabling Advanced Fabric Services on IVR Flows 2-20 Configuration Guidelines and Restrictions 2-20
Contents
Enabling AAM Support for IVR 2-21 Enabling IVR Support for FCR 2-22 Disabling AAM Support for IVR 2-22
INDEX
vi
OL-19988-01
New and Changed Information

As ofCisco MDS NX-OS Release 4.2(1) software configuration information is available in new feature-specific configuration guides for the following information:

System management Interfaces Fabric Quality of service Security IP services High availability and redundancy
The information in these new guides previously existed in the Cisco MDS 9000 Family CLI Configuration Guide and in the Cisco MDS 9000 Family Fabric Manager Configuration Guide. Those configuration guides remain available on Cisco.com and should be used for all software releases prior to Cisco MDS NX-OS Release 4.2(1). Each guide addresses the features introduced in or available in a particular release. Select and view the configuration guide that pertains to the software installed in your switch. For a complete list of document titles, see the list of Related Documentation in the Preface. To find additional information about Cisco MDS NX-OS Release 5.0(1), see the Cisco MDS 9000 Family Release Notes available at the following Cisco Systems website: http://www.cisco.com/en/US/products/ps5989/prod_release_notes_list.htm
About This Guide
The information in the new Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide previously existed in the Fabric Configuration section in theCisco MDS 9000 Family CLI Configuration Guide, Release 4.2(1). Table 1 lists the New and Changed features for this guide, starting with Cisco MDS NX-OS Release 5.0(1a).
vii
New and Changed Information
Table 1
New and Changed Features for Cisco MDS NX-OS Release 5.0(1a)
Feature IOA support
New or Changed Topics Updated Enabling Advanced Fabric Services on IVR Flows section. Added Enabling AAM Support for IVR section.
Changed in Release 5.0(1a)
Where Documented Chapter 2, Advanced Inter-VSAN Routing Configuration Chapter 2, Advanced Inter-VSAN Routing Configuration
AAM support
5.01(1a)
viii
OL-19988-01
Preface
This preface describes the audience, organization, and conventions of the Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide. The preface also provides information on how to obtain related documentation.
Audience
This guide is for experienced network administrators who are responsible for planning, installing, configuring, and maintaining Cisco Inter-VSAN Routing.
Organization
This document is organized as follows: Chapter Chapter 1 Chapter 2 Title Basic Inter-VSAN Routing Configuration Advanced Inter-VSAN Routing Configuration Description Presents concepts and instructions for basic IVR configurations. Presents concepts and instructions for advanced IVR configurations.
Document Conventions
Command descriptions use these conventions: boldface font italic font [ ] [x|y|z] Commands and keywords are in boldface. Arguments for which you supply values are in italics. Elements in square brackets are optional. Optional alternative keywords are grouped in brackets and separated by vertical bars.
ix
Preface
Screen examples use these conventions:
screen font boldface screen font
Terminal sessions and information the switch displays are in screen font. Information you must enter is in boldface screen font. Arguments for which you supply values are in italic screen font. Nonprinting characters, such as passwords, are in angle brackets. Default responses to system prompts are in square brackets. An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.
italic screen font

< > [ ] !, #
This document uses the following conventions:
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.
Caution
Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
Related Documentation
The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco Fabric Manager and MDS NX-OS Documentation Locator at: http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.htm
Release Notes

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Releases Cisco MDS 9000 Family Release Notes for MDS SAN-OS Releases Cisco MDS 9000 Family Release Notes for Storage Services Interface Images Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images Release Notes for Cisco MDS 9000 Family Fabric Manager
Regulatory Compliance and Safety Information
Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family
OL-19988-01
Preface
Compatibility Information

Cisco Data Center Interoperability Support Matrix Cisco MDS 9000 NX-OS Hardware and Software Compatibility Information and Feature Lists Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images Cisco MDS 9000 Family Switch-to-Switch Interoperability Configuration Guide Cisco MDS NX-OS Release Compatibility Matrix for IBM SAN Volume Controller Software for Cisco MDS 9000 Cisco MDS SAN-OS Release Compatibility Matrix for VERITAS Storage Foundation for Networks Software
Hardware Installation

Cisco MDS 9500 Series Hardware Installation Guide Cisco MDS 9200 Series Hardware Installation Guide Cisco MDS 9100 Series Hardware Installation Guide Cisco MDS 9124 and Cisco MDS 9134 Multilayer Fabric Switch Quick Start Guide
Software Installation and Upgrade

Cisco MDS 9000 NX-OS Release 4.1(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide Cisco MDS 9000 Family Storage Services Interface Image Install and Upgrade Guide Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide
Cisco NX-OS

Cisco MDS 9000 Family NX-OS Licensing Guide Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide Cisco MDS 9000 Family NX-OS System Management Configuration Guide Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide Cisco MDS 9000 Family NX-OS Fabric Configuration Guide Cisco MDS 9000 Family NX-OS Quality of Service Configuration Guide Cisco MDS 9000 Family NX-OS Security Configuration Guide Cisco MDS 9000 Family NX-OS IP Services Configuration Guide Cisco MDS 9000 Family NX-OS Intelligent Storage Services Configuration Guide Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide
Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide OL-18091-01, Cisco MDS NX-OS Release 5.0(1a)
xi
Preface
Cisco Fabric Manager

Cisco Fabric Manager Fundamentals Configuration Guide Cisco Fabric Manager System Management Configuration Guide Cisco Fabric Manager Interfaces Configuration Guide Cisco Fabric Manager Fabric Configuration Guide Cisco Fabric Manager Quality of Service Configuration Guide Cisco Fabric Manager Security Configuration Guide Cisco Fabric Manager IP Services Configuration Guide Cisco Fabric Manager Intelligent Storage Services Configuration Guide Cisco Fabric Manager High Availability and Redundancy Configuration Guide Cisco Fabric Manager Inter-VSAN Routing Configuration Guide Cisco Fabric Manager Online Help Cisco Fabric Manager Web Services Online Help
Command-Line Interface
Cisco MDS 9000 Family Command Reference
Intelligent Storage Networking Services Configuration Guides

Cisco MDS 9000 I/O Acceleration Configuration Guide Cisco MDS 9000 Family SANTap Deployment Guide Cisco MDS 9000 Family Data Mobility Manager Configuration Guide Cisco MDS 9000 Family Storage Media Encryption Configuration Guide Cisco MDS 9000 Family Secure Erase Configuration Guide Cisco MDS 9000 Family Cookbook for Cisco MDS SAN-OS
Troubleshooting and Reference

Cisco NX-OS System Messages Reference Cisco MDS 9000 Family NX-OS Troubleshooting Guide Cisco MDS 9000 Family NX-OS MIB Quick Reference Cisco MDS 9000 Family NX-OS SMI-S Programming Reference Cisco MDS 9000 Family Fabric Manager Server Database Schema
xii
OL-19988-01
Preface
Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly Whats New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the Whats New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide OL-18091-01, Cisco MDS NX-OS Release 5.0(1a)
xiii
Preface
xiv
OL-19988-01
CH A P T E R

This chapter describes the Inter-VSAN Routing (IVR) feature and provides basic instructions on sharing resources across VSANs using IVR management interfaces. After setting up a basic IVR configuration, see Chapter 2, Advanced Inter-VSAN Routing Configuration, if you need to set up an advanced IVR configuration. This chapter includes the following sections on IVR basic configuration:

About Inter-VSAN Routing, page 1-1 Basic IVR Configuration Task List, page 1-6 Basic IVR Configuration, page 1-6 IVR Virtual Domains, page 1-13 IVR Zones and IVR Zone Sets, page 1-14 IVR Logging, page 1-21 Database Merge Guidelines, page 1-22 IVR Auto Topology Mode Configuration Example, page 1-25 Default Settings, page 1-28
About Inter-VSAN Routing

Virtual SANs (VSANs) improve storage area network (SAN) scalability, availability, and security by allowing multiple Fibre Channel SANs to share a common physical infrastructure of switches and ISLs. These benefits are derived from the separation of Fibre Channel services in each VSAN and the isolation of traffic between VSANs. Data traffic isolation between the VSANs also inherently prevents sharing of resources attached to a VSAN, such as robotic tape libraries. Using IVR, you can access resources across VSANs without compromising other VSAN benefits. This section includes the following topics:

IVR Features, page 1-2 IVR Terminology, page 1-3 IVR Configuration Limits, page 1-4 Fibre Channel Header Modifications, page 1-5 IVR Network Address Translation, page 1-5 IVR VSAN Topology, page 1-5
1-1
Chapter 1 About Inter-VSAN Routing
IVR Interoperability, page 1-6
IVR Features
IVR supports the following features:

Accesses resources across VSANs without compromising other VSAN benefits. Transports data traffic between specific initiators and targets on different VSANs without merging VSANs into a single logical fabric. Establishes proper interconnected routes that travers one or more VSANs across multiple switches. IVR is not limited to VSANs present on a common switch. Shares valuable resources (such as tape libraries) across VSANs without compromise. Fibre Channel traffic does not flow between VSANs, nor can initiators access resources across VSANs other than the designated VSAN. Provides efficient business continuity or disaster recovery solutions when used in conjunction with FCIP (see Figure 1-1). Is in compliance with Fibre Channel standards. Incorporates third-party switches, however, IVR-enabled VSANs may need to be configured in one of the interop modes.
Note
IVR is not supported on the Cisco MDS 9124 Fabric Switch, the Cisco MDS 9134 Fabric Switch, the Cisco Fabric Switch for HP c-Class BladeSystem, and the Cisco Fabric Switch for IBM BladeCenter. Originator Exchange ID (OX ID) load balancing of IVR traffic from IVR-enabled switches is not supported on Generation 1 switching modules. OX ID-based load balancing of IVR traffic from a non-IVR MDS switch could work in some environments. Generation 2 switching modules support OX ID-based load balancing of IVR traffic from IVR-enabled switches.
Note
To configure the sample scenario shown in Figure 1-1, follow the steps in IVR Auto Topology Mode Configuration Example on page 1-25.
1-2
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration About Inter-VSAN Routing
Figure 1-1 Traffic Continuity Using IVR and FCIP
FC or FCIP links (multiple links for redundancy)
IVR-Enabled Switch MDS1
Transit VSAN (VSAN 4) MDS2 MDS3 MDS4
FC
FC
FC
FC
FC
FC
T VSAN 1 VSAN 2
S1
S2 VSAN 3
105294
IVR Terminology
The following IVR-related terms are used in the IVR documentation:

Native VSANThe VSAN to which an end device logs on is the native VSAN for that end device. Current VSANThe VSAN currently being configured for IVR. Inter-VSAN Routing zone (IVR zone)A set of end devices that are allowed to communicate across VSANs within their interconnected SAN fabric. This definition is based on their port world-wide names (pWWNs) and their native VSAN associations. Prior to Cisco SAN-OS Release 3.0(3), you could configure up to 2000 IVR zones and 10,000 IVR zone members on the switches in the network. As of Cisco SAN-OS Release 3.0(3), you can configure up to 8000 IVR zones and 20,000 IVR zone members on the switches in the network. Inter-VSAN routing zone sets (IVR zone sets)One or more IVR zones make up an IVR zone set. You can configure up to 32 IVR zone sets on any switch in the Cisco MDS 9000 Family. Only one IVR zone set can be active at any time. IVR pathAn IVR path is a set of switches and Inter-Switch Links (ISLs) through which a frame from an end device in one VSAN can reach another end device in some other VSAN. Multiple paths can exist between two such end devices. IVR-enabled switchA switch on which the IVR feature is enabled. Edge VSANA VSAN that initiates (source edge-VSAN) or terminates (destination edge-VSAN) an IVR path. Edge VSANs may be adjacent to each other or they may be connected by one or more transit VSANs. VSANs 1, 2, and 3 (see Figure 1-1), are edge VSANs.
Note
An edge VSAN for one IVR path can be a transit VSAN for another IVR path.
1-3
Chapter 1 About Inter-VSAN Routing
Transit VSANA VSAN that exists along an IVR path from the source edge VSAN of that path to the destination edge VSAN of that path. VSAN 4 is a transit VSAN (see Figure 1-1).
Note
When the source and destination edge VSANs are adjacent to each other, then a transit VSAN is not required between them.
Border switchAn IVR-enabled switch that is a member of two or more VSANs. Border switches, such as the IVR-enabled switch between VSAN 1 and VSAN 4 (see Figure 1-1), span two or more different color-coded VSANs. Edge switchA switch to which a member of an IVR zone has logged in to. Edge switches are unaware of the IVR configurations in the border switches. Edge switches do not need to be IVR-enabled. Autonomous Fabric Identifier (AFID)Allows you to configure more than one VSAN in the network with the same VSAN ID and avoid downtime when configuring IVR between fabrics that contain VSANs with the same ID. Service groupAllows you to reduce the amount of IVR traffic to non-IVR-enabled VSANs by configuring one or more service groups that restrict the traffic to the IVR-enabled VSANs.
IVR Configuration Limits

Table 1-1 summarizes the configuration limits for IVR.
Table 1-1 IVR Configuration Limits
IVR Feature IVR VSANs IVR zone members
Maximum Limit 128 As of Cisco SAN-OS Release 3.0(3), 20,000 IVR zone members per physical fabric Prior to Cisco SAN-OS Release 3.0(3), 10,000 IVR zone members per physical fabric
IVR zones
As of Cisco SAN-OS Release 3.0(3), 8000 IVR zones per physical fabric Prior to Cisco SAN-OS Release 3.0(3), 2000 IVR zones per physical fabric
IVR zone sets IVR service groups IVR switches
32 IVR zone sets per physical fabric 16 service groups per physical fabric 25 (IVR auto topology mode)
Note
We recommend IVR manual topology mode if you have more than 25 IVR switches. See Manually Configuring an IVR Topology on page 2-10.
1-4
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration About Inter-VSAN Routing
Fibre Channel Header Modifications

IVR virtualizes the remote end devices in the native VSAN using a virtual domain. When IVR is configured to link end devices in two disparate VSANs, the IVR border switches are responsible for modifying the Fibre Channel headers for all communication between the end devices. The sections of the Fibre Channel frame headers that are modified include:

VSAN number Source FCID Destination FCID
When a frame travels from the initiator to the target, the Fibre Channel frame header is modified such that the initiator VSAN number is changed to the target VSAN number. If IVR Network Address Translation (NAT) is enabled, then the source and destination FCIDs are also translated at the edge border switch. If IVR NAT is not enabled, then you must configure unique domain IDs for all switches involved in the IVR path.
IVR Network Address Translation

IVR Network Address Translation (NAT) can be enabled to allow non-unique domain IDs; however, without NAT, IVR requires unique domain IDs for all switches in the fabric. IVR NAT simplifies the deployment of IVR in an existing fabric where non-unique domain IDs might be present. To use IVR NAT, it must be enabled on all IVR-enabled switches in the fabric. For information on distributing the IVR configuring using CFS, see Distributing the IVR Configuration Using CFS on page 1-7. By default, IVR NAT and IVR configuration distributions are disabled on all switches in the Cisco MDS 9000 Family. See About IVR NAT and IVR Auto Topology Mode on page 1-9 for information on IVR requirements and guidelines as well as configuration information.
IVR VSAN Topology

IVR uses a configured IVR VSAN topology to determine how to route traffic between the initiator and the target across the fabric. IVR auto topology mode automatically builds the IVR VSAN topology and maintains the topology database when fabric reconfigurations occur. IVR auto topology mode also distributes the IVR VSAN topology to IVR-enabled switches using CFS. Using IVR auto topology mode, you no longer need to manually update the IVR VSAN topology when reconfigurations occur in your fabric. If an IVR manual topology database exists, IVR auto topology mode initially uses that topology information. The automatic update reduces disruption in the network by gradually migrating from the user-specified topology database to the automatically-learned topology database. User-configured topology entries that are not part of the network are aged out in about three minutes. New entries that are not part of the user-configured database are added as they are discovered in the network. When IVR auto topology mode is enabled, it starts with the previously active IVR manual topology if it exists, and then the discovery process begins. New, alternate, or better paths my be discovered. If the traffic is switched to an alternate or better path, there may be temporary traffic disruptions that are normally associated with switching paths.
1-5
Chapter 1 Basic IVR Configuration Task List
Note
IVR topology in IVR auto topology mode requires Cisco MDS SAN-OS Release 2.1(1a) or later and CFS must be enabled for IVR on all switches in the fabric.
IVR Interoperability
When using the IVR feature, all border switches in a fabric must be Cisco MDS switches. However, other switches in the fabric may be non-MDS switches. For example, end devices that are members of the active IVR zone set may be connected to non-MDS switches. Non-MDS switches may also be present in the transit VSAN(s) or in the edge VSANs if one of the interop modes is enabled. For additional information on switch interoperability, refer to the Cisco Data Center Interoperability Support Matrix.
Basic IVR Configuration Task List

To configure IVR, follow these steps: Task
Step 1 Step 2 Note Step 3 Step 4 Step 5 Step 6 Step 7 Step 8
Reference See Enabling IVR on page 1-7. See Distributing the IVR Configuration Using CFS on page 1-7. See About IVR NAT and IVR Auto Topology Mode on page 1-9. See About IVR NAT and IVR Auto Topology Mode on page 1-9. See Configuring IVR Zones and IVR Zone Sets on page 1-16. See Committing the Changes on page 1-8. See Verifying IVR Zone and IVR Zone Set Configuration on page 1-19.
Enable IVR on all border switches. Enable IVR distribution. Enable IVR NAT. Enable IVR auto topology mode. Configure IVR virtual domains. Configure and activate zone sets. Commit the IVR configuration. Verify the IVR configuration.
The following steps need to be performed on one switch in the fabric.
Basic IVR Configuration

This section describes how to configure IVR and contains the following sections:

Configuring IVR and IVR Zones Using the IVR Zone Wizard, page 1-7 Enabling IVR, page 1-7 Distributing the IVR Configuration Using CFS, page 1-7 About IVR NAT and IVR Auto Topology Mode, page 1-9 IVR NAT Requirements and Guidelines, page 1-10
1-6
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration Basic IVR Configuration
Enabling IVR NAT and IVR Auto Topology Mode, page 1-12
Configuring IVR and IVR Zones Using the IVR Zone Wizard
The IVR Zone Wizard simplifies the process of configuring IVR zones in a fabric. The IVR Zone Wizard checks the following conditions and identifies any related issues:
Checks all switches in the fabric to identify the Cisco SAN-OS or NX-OS release that is running on the switch. If Cisco MDS SAN-OS Release 2.1(1a) or later is running on the switch, you can decide to migrate to IVR NAT with IVR auto topology mode. Checks all switches in the fabric to identify the Cisco SAN-OS or NX-OS release that is running on the switch. If Cisco MDS SAN-OS Release 2.1(1a) or later is running on a switch, you can decide to upgrade the switch or disable IVR NAT or IVR auto topology mode if they are enabled.
Enabling IVR
The IVR feature must be enabled in all border switches in the fabric that participate in the IVR. By default, this feature is disabled in all Cisco MDS 9000 Family switches. You can manually enable IVR on all required switches in the fabric or configure fabric-wide distribution of the IVR configuration. See Distributing the IVR Configuration Using CFS on page 1-7.
Note
The configuration and verification commands for the IVR feature are only available when IVR is enabled on a switch. When you disable this configuration, all related configurations are automatically discarded. To enable IVR on any participating switch, follow these steps: Command Purpose Enters configuration mode. Enables IVR on the switch. Disables (default) IVR on the switch.
Step 1 Step 2
switch# config t switch(config)# feature ivr switch(config)# no feature ivr
Distributing the IVR Configuration Using CFS

The IVR feature uses the Cisco Fabric Services (CFS) infrastructure to enable efficient configuration management and to provide a single point of configuration for the entire fabric in the VSAN. For information on CFS, refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide. The following configurations are distributed:

IVR zones IVR zone sets IVR VSAN topology IVR active topology and zone set (activating these features in one switch propagates the configuration to all other distribution-enabled switches in the fabric) AFID database
1-7
Chapter 1 Basic IVR Configuration
Note
IVR configuration distribution is disabled by default. For the feature to function correctly, you must enable it on all IVR-enabled switches in the network. This section includes the following topics:

Database Implementation, page 1-8 Enabling Configuration Distribution, page 1-8 Locking the Fabric, page 1-8 Committing the Changes, page 1-8 Discarding the Changes, page 1-9 Clearing a Locked Session, page 1-9
Database Implementation
The IVR feature uses three databases to accept and implement configurations.

Configured databaseThe database is manually configured by the user. Active databaseThe database is currently enforced by the fabric. Pending databaseIf you modify the configuration, you need to commit or discard the configured database changes to the pending database. The fabric remains locked during this period. Changes to the pending database are not reflected in the active database until you commit the changes to CFS.
Enabling Configuration Distribution

To enable IVR configuration distribution, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr distribute switch(config)# no ivr distribute
Purpose Enters configuration mode. Enables IVR distribution. Disables (default) IVR distribution.
Locking the Fabric

The first action that modifies the database creates the pending database and locks the feature in the VSAN. Once you lock the fabric, the following situations apply:

No other user can make any configuration changes to this feature. A copy of the configuration database becomes the pending database along with the first active change.
Committing the Changes

If you commit the changes made to the active database, the configuration is committed to all the switches in the fabric. On a successful commit, the configuration change is applied throughout the fabric and the lock is released.
1-8
OL-19988-01
Chapter 1
To commit IVR configuration changes, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr commit
Purpose Enters configuration mode. Commits the IVR changes.
Discarding the Changes

If you discard (abort) the changes made to the pending database, the configuration database remains unaffected and the lock is released. To discard IVR configuration changes, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr abort
Purpose Enters configuration mode. Discards the IVR changes and clears the pending configuration database.
Clearing a Locked Session

If you have performed an IVR task and have forgotten to release the lock by either committing or discarding the changes, an administrator can release the lock from any switch in the fabric. If the administrator performs this task, your changes to the pending database are discarded and the fabric lock is released.
Tip
The pending database is only available in the volatile directory and is subject to being discarded if the switch is restarted. To use administrative privileges and release a locked DPVM session, use the clear ivr session command in EXEC mode.
switch# clear ivr session
About IVR NAT and IVR Auto Topology Mode

Before configuring an IVR SAN fabric to use IVR NAT and IVR auto topology mode, consider the following:

Configure IVR only in the relevant switches. Enable CFS for IVR on all switches in the fabric. Verify that all switches in the fabric are running Cisco MDS SAN-OS Release 2.1(1a) or later. Acquire a mandatory Enterprise License Package or SAN-EXTENSION license package if you have Cisco MDS SAN-OS Release 2.1(1a) or later and one active IPS card for this feature. For information on licensing, refer to the Cisco MDS 9000 Family NX-OS Licensing Guide.
1-9
Note
The IVR over FCIP feature is bundled with the Cisco MDS 9216i Switch and does not require the SAN extension over IP package for the fixed IP ports on the supervisor module.
Tip
If you change any FSPF link cost, ensure that the FSPF path distance (that is, the sum of the link costs on the path) of any IVR path is less than 30,000.
Note
IVR-enabled VSANs can be configured when the interop mode is enabled (any interop mode) or disabled (no interop mode).
IVR NAT Requirements and Guidelines

The requirements and guidelines for using IVR NAT are listed below:

All IVR-enabled switches must run Cisco MDS SAN-OS Release 2.1(1a) or later. IVR NAT port login (PLOGI) requests that are received from hosts are delayed a few seconds to perform the rewrite on the FC ID address. If the hosts PLOGI timeout value is set to a value less than five seconds, it may result in the PLOGI being unnecessarily aborted and the host being unable to access the target. We recommend that you configure the host bus adapter for a timeout of at least ten seconds (most HBAs default to a value of 10 or 20 seconds). IVR NAT requires Cisco MDS SAN-OS Release 2.1(1a) or later on all IVR switches in the fabric. Load balancing of IVR NAT traffic across equal cost paths from an IVR-enabled switch is not supported. However, load balancing of IVR NAT traffic over PortChannel links is supported. The load-balancing algorithm for IVR NAT traffic over PortChannel with Generation 1 modules is SRC/DST only. Generation 2 modules support SRC/DST/OXID-based load balancing of IVR NAT traffic across a PortChannel. You cannot configure IVR NAT and preferred Fibre Channel routes on Generation 1 module interfaces. IVR NAT allows you to set up IVR in a fabric without needing unique domain IDs on every switch in the IVR path. IVR NAT virtualizes the switches in other VSANs by using local VSAN for the destination IDs in the Fibre Channel headers. In some Extended Link Service message types, the destination IDs are included in the packet data. In these cases, IVR NAT replaces the actual destination ID with the virtualized destination ID. IVR NAT supports destination ID replacement in the Extended Link Service messages described in Table 1-2.
Extended Link Service Messages Supported by IVR NAT
Table 1-2
Extended Link Service Messages Abort Exchange Discover Address Discover Address Accept
Link Service Command (LS_COMMAND) 0x06 00 00 00 0x52 00 00 00 0x02 00 00 00
Mnemonic ABTX ADISC ADISC ACC FARP-REPLY
Fibre Channel Address Resolution Protocol 0x55 00 00 00 Reply
1-10
OL-19988-01
Chapter 1
Table 1-2 Extended Link Service Messages Supported by IVR NAT (continued)
Extended Link Service Messages
Link Service Command (LS_COMMAND)
Mnemonic FARP-REQ LOGO PLOGI REC REC ACC RES RES ACC RLS RSS RRQ RSI RSL TPRLO TPRLO ACC
Fibre Channel Address Resolution Protocol 0x54 00 00 00 Request Logout Port Login Read Exchange Concise Read Exchange Concise Accept Read Exchange Status Block Read Exchange Status Block Accept Read Link Error Status Block Read Sequence Status Block Reinstate Recovery Qualifier Request Sequence Initiative Scan Remote Loop Third Party Process Logout Third Party Process Logout Accept
0x05 00 00 00 0x30 00 00 00 0x13 00 00 00 0x02 00 00 00 0x08 00 00 00 0x02 00 00 00 0x0F 00 00 00 0x09 00 00 00 0x12 00 00 00 0x0A 00 00 00 0x7B 00 00 00 0x24 00 00 00 0x02 00 00 00
If you have a message that is not recognized by IVR NAT and contains the destination ID in the packet data, you cannot use IVR with NAT in your topology. You can still use IVR with unique domain IDs.
Transit VSAN Guidelines

Consider the following guidelines for transit VSANs:
In addition to defining the IVR zone membership, you can choose to specify a set of transit VSANs to provide connectivity between two edge VSANs:
If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though, not
prohibited) to provide connectivity.

If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs
to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled on a switch that is a member of both the source and destination edge VSANs.

Traffic between the edge VSANs only traverses through the shortest IVR path. Transit VSAN information is common to all IVR zone sets. Sometimes, a transit VSAN can also act as an edge VSAN in another IVR zone.
Border Switch Guidelines

Before configuring border switches, consider the following guidelines:

Border switches require Cisco MDS SAN-OS Release 2.1(1a) or later. A border switch must be a member of two or more VSANs.
1-11

A border switch that facilitates IVR communsications must be IVR-enabled. IVR can (optionally) be enabled on additional border switches to provide redundant paths between active IVR zone members. The VSAN topology configuration updates automatically when a border switch is added or removed.
Enabling IVR NAT and IVR Auto Topology Mode

This section includes instructions on how to enable IVR NAT and how to enable IVR auto topology mode. To enable IVR NAT, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# ivr nat switch(config)# no ivr nat
Purpose Enters configuration mode. Enables IVR NAT on the switch. Disables (default) IVR NAT on the switch.
Note
IVR configuration distribution must be enabled before configuring IVR auto topology mode (see Distributing the IVR Configuration Using CFS on page 1-7). Once IVR auto topology mode is enabled, you cannot disable IVR configuration distribution. To enable IVR auto topology mode, follow these steps: Command Purpose Enters configuration mode. Enables IVR auto topology mode.
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr vsan-topology auto
To view an automatically discovered IVR topology, use the show ivr vsan-topology command.
switch# show ivr vsan-topology AFID SWITCH WWN Active Cfg. VSANS -------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-2 1 20:02:00:44:22:00:4a:05 yes yes 1-2,6 1 20:02:00:44:22:00:4a:07 yes yes 2-5 Total: 3 entries in active and configured IVR VSAN-Topology
Current Status: Inter-VSAN topology is AUTO Last activation time: Mon Mar 24 07:19:53 1980
Note
The asterisk (*) indicates the local switch.
1-12
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration IVR Virtual Domains
IVR Virtual Domains

In a remote VSAN, the IVR application does not automatically add the virtual domain to the assigned domains list. Some switches (for example, the Cisco SN5428 switch) do not query the remote name server until the remote domain appears in the assigned domains list in the fabric. In such cases, add the IVR virtual domains in a specific VSAN to the assigned domains list in that VSAN. When adding IVR domains, all IVR virtual domains that are currently present in the fabric (and any virtual domain that is created in the future) will appear in the assigned domains list for that VSAN.
Tip
Be sure to add IVR virtual domains if Cisco SN5428 or MDS 9020 switches exist in the VSAN. When you enable the IVR virtual domains, links may fail to come up due to overlapping virtual domain identifiers. If this occurs, temporarily withdraw the overlapping virtual domain from that VSAN.
Note
Withdrawing an overlapping virtual domain from an IVR VSAN disrupts IVR traffic to and from that domain. Use the ivr withdraw domain command in EXEC mode to temporarily withdraw the overlapping virtual domain interfaces from the affected VSAN.
Tip
Only add IVR domains in the edge VSANs and not in transit VSANs.
Manually Configuring IVR Virtual Domains

To manually configure an IVR virtual domain in a specified VSAN, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr virtual-fcdomain-add vsan-ranges 1-4093 switch(config)# no ivr virtual-fcdomain-add vsan-ranges 1-4093
Purpose Enters configuration mode. Adds the IVR virtual domains in VSAN 1. Perform this step on all IVR switches. Reverts to the factory default of not adding IVR virtual domains and removes the currently active virtual domains for that VSAN from the fcdomain manager list
Note
As of Cisco SAN-OS Release 3.1(2), Cisco Fabric Configuration Services (FCS) supports the discovery of virtual devices. The fcs virtual-device-add vsan-ranges command, issued in FCS configuration submode, allows you to discover virtual devices in a particular VSAN or in all VSANs. To discover the devices that are zoned for IVR using this command, the devices must have request domain_ID (RDI) enabled. For information on using FCS, refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.
1-13
Chapter 1 IVR Zones and IVR Zone Sets
To configure fabric-wide IVR virtual domains in a specified VSAN, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr virtual-fcdomain-add 2 vsan-ranges 1-4093 switch(config)# ivr commit switch(config)# no ivr virtual-fcdomain-add2 vsan-ranges 1-4093
Purpose Enters configuration mode. Adds the IVR virtual domains in VSAN 1. Perform this step on all IVR switches. Commits the fabric-wide configuration. Reverts to the factory default of not adding IVR virtual domains and removes the currently active virtual domains for that VSAN from the fcdomain manager list
Step 3 Step 4
Verifying an IVR Virtual Domain Configuration

To view the status of the IVR virtual domain configuration, use the show ivr virtual-fcdomain-add-status command.
switch# show ivr virtual-fcdomain-add-status IVR virtual domains are added to fcdomain list in VSANS: 1 (As well as to VSANs in interoperability mode 2 or 3)
Clearing an IVR fcdomain Database

To clear the IVR fcdomain database, use the following command:
switch# clear ivr fcdomain database
IVR Zones and IVR Zone Sets

This section describes configuring IVR zones and IVR zone sets and includes the following topics:

About IVR Zones, page 1-15 IVR Zone Limits and Image Downgrading Considerations, page 1-15 Automatic IVR Zone Creation, page 1-15 Configuring IVR Zones and IVR Zone Sets, page 1-16 About Activating Zone Sets and Using the force Option, page 1-18 Activating or Deactivating IVR Zone Sets, page 1-19 Verifying IVR Zone and IVR Zone Set Configuration, page 1-19 Clearing the IVR Zone Database, page 1-21
1-14
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration IVR Zones and IVR Zone Sets
About IVR Zones

As part of the IVR configuration, you need to configure one or more IVR zones to enable cross-VSAN communication. To achieve this result, you must specify each IVR zone as a set of (pWWN, VSAN) entries. Like zones, several IVR zone sets can be configured to belong to an IVR zone. You can define several IVR zone sets and activate only one of the defined IVR zone sets.
Note
The same IVR zone set must be activated on all of the IVR-enabled switches. Table 1-3 identifies the key differences between IVR zones and zones.
Table 1-3 Key Differences Between IVR Zones and Zones
IVR Zones
Zones
IVR zone membership is specified using the VSAN and Zone membership is specified using pWWN, pWWN combination. fabric WWN, sWWN, or the AFID. Default zone policy is always deny (not configurable). Default zone policy is deny (configurable).
IVR Zone Limits and Image Downgrading Considerations

Table 1-4 identifies the IVR zone limits per physical fabric.
Table 1-4 IVR Zone Limits
Cisco Release SAN-OS Release 3.0(3 or later
IVR Zone Limit 8000
IVR Zone Member Limit 20,000 10,000
IVR Zone Set Limit 32 32
SAN-OS Release 3.0(2b) or earlier 2000
Note
A zone member is counted twice if it exists in two zones. See Database Merge Guidelines on page 1-22.
Caution
If you want to downgrade to a release prior to Cisco SAN-OS Release 3.0(3), the number of IVR zones cannot exceed 2000 and the number of IVR zone members cannot exceed 10,000.
Automatic IVR Zone Creation

Figure 1-2 depicts an IVR zone consisting of four members. To allow pwwn1 to communicate with pwwn2, they must be in the same zone in VSAN 1, as well as in VSAN 2. If they are not in the same zone, then the hard-zoning ACL entries will prohibit pwwn1 from communicating with pwwn2. A zone corresponding to each active IVR zone is automatically created in each edge VSAN specified in the active IVR zone. All pWWNs in the IVR zone are members of these zones in each VSAN.
1-15
Figure 1-2 Creating Zones Upon IVR Zone Activation
Active zone in VSAN 1: pwwn1 pwwn2 pwwn3 pwwn4 Active IVZ VSAN1, pwwn1 VSAN2, pwwn2 VSAN2, pwwn3 VSAN3, pwwn4 IVR zone name: OLTP_Backup pwwn1 pwwn2 pwwn3 pwwn4 Active zone in VSAN 3:
105255
Zone name: IVRZ_OLTP_Backup
Active zone in VSAN 2: pwwn1 pwwn2 pwwn3 pwwn4
The zones are created automatically by the IVR process when an IVR zone set is activated. They are not stored in a full zone set database and are lost when the switch reboots or when a new zone set is activated. The IVR feature monitors these events and adds the zones corresponding to the active IVR zone set configuration when a new zone set is activated. Like zone sets, IVR zone sets are also activated nondisruptively.
Note
If pwwn1 and pwwn2 are in an IVR zone in the current as well as the new IVR zone set, then activation of the new IVR zone set does not cause any traffic disruption between them. IVR zone and IVR zone set names are restricted to 64 alphanumeric characters.
Caution
Prior to Cisco SAN-OS Release 3.0(3), you can only configure a total of 2000 IVR zones and 32 IVR zone sets on the switches in the network. As of Cisco SAN-OS Release 3.0(3), you can only configure a total of 8000 IVR zones and 32 IVR zone sets on the switches in the network. See Database Merge Guidelines on page 1-22.
Configuring IVR Zones and IVR Zone Sets

To create IVR zones and IVR zone sets, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr zone name sample_vsan2-3 switch(config-ivr-zone)#
Purpose Enters configuration mode. Creates an IVR zone named sample_vsan2-3.
1-16
OL-19988-01
Chapter 1
Command
Step 3
switch(config-ivr-zone)# member pwwn 21:00:00:e0:8b:02:ca:4a vsan 3
Purpose Adds the specified pWWN in VSAN 3 as an IVR zone member. Adds the specified pWWN in VSAN 2 as an IVR zone member. Returns to configuration mode. Creates an IVR zone named sample_vsan4-5. Adds the specified pWWN in VSAN 4 as an IVR zone member. Adds the specified pWWN in VSAN 4 as an IVR zone member. Adds the specified pWWN in VSAN 5 as an IVR zone member. Returns to configuration mode. Creates an IVR zone set named Ivr_zoneset1. Adds the sample_vsan2-3 IVR zone as an IVR zone set member. Adds the sample_vsan4-5 IVR zone as an IVR zone set member. Returns to configuration mode. Activates the newly created IVR zone set. Forcefully activates the specified IVR zone set. Deactivates the specified IVR zone set. Returns to EXEC mode.
Step 4
switch(config-ivr-zone)# member pwwn 21:00:00:20:37:c8:5c:6b vsan 2
Step 5 Step 6 Step 7
switch(config-ivr-zone)# exit switch(config)# switch(config)# ivr zone name sample_vsan4-5 switch(config-ivr-zone)# switch(config-ivr-zone)# member pwwn 21:00:00:e0:8b:06:d9:1d vsan 4
Step 8
switch(config-ivr-zone)# member pwwn 21:01:00:e0:8b:2e:80:93 vsan 4
Step 9
switch(config-ivr-zone)# member pwwn 10:00:00:00:c9:2d:5a:dd vsan 5
switch(config-ivr-zone)# exit switch(config)# switch(config)# ivr zoneset name Ivr_zoneset1 switch(config-ivr-zoneset)# switch(config-ivr-zoneset)# member sample_vsan2-3
Step 13
switch(config-ivr-zoneset)# member sample_vsan4-5
Step 14 Step 15
switch(config-ivr-zoneset)# exit switch(config) switch(config)# ivr zoneset activate name IVR_ZoneSet1
switch(config)# ivr zoneset activate name IVR_ZoneSet1 force
switch(config)# no ivr zoneset activate name IVR_ZoneSet1
Step 16
switch(config)# end switch#
1-17
About Activating Zone Sets and Using the force Option

Once the zone sets have been created and populated, you must activate the zone set. When you activate an IVR zone set, IVR automatically adds an IVR zone to the regular active zone set of each edge VSAN. If a VSAN does not have an active zone set, IVR can only activate an IVR zone set using the force option, which causes IVR to create an active zone set called nozoneset and adds the IVR zone to that active zone set.
Caution
If you deactivate the regular active zone set in a VSAN, the IVR zone set is also deactivated. This occurs because the IVR zone in the regular active zone set, and all IVR traffic to and from the switch, is stopped. To reactivate the IVR zone set, you must reactivate the regular zone set.
Note
If IVR and iSLB are enabled in the same fabric, at least one switch in the fabric must have both features enabled. Any zoning-related configuration or activation operation (for normal zones, IVR zones, or iSLB zones) must be performed on this switch. Otherwise, traffic might be disrupted in the fabric. You can also use the force command to activate IVR zone sets. Table 1-5 lists the various scenarios with and without the force command option.
Table 1-5 IVR Scenarios with and without the force Command
force command
Case 1 2 3 4 5
1
Default Zone Policy Deny Deny Permit
Active Zone Set before IVR Zone Activation No active zone set Active zone set present No active zone set or Active zone set present
Option Used? No Yes No/Yes No Yes
IVR Zone Set Activation Status Failure Success Success Failure Success
Active IVR Zone Created? No Yes Yes No Yes
Possible Traffic Disruption No No No No Yes
1. We recommend that you use the Case 3 scenario.
Caution
Using the force command of IVR zone set activation may cause traffic disruption, even for devices that are not involved in IVR. For example, if your configuration does not have any active zone sets and the default zone policy is permit, then an IVR zone set activation will fail. However, IVR zone set activation will be successful if the force command is used. Because zones are created in the edge VSANs corresponding to each IVR zone, traffic may be disrupted in edge VSANs where the default zone policy is permit.
1-18
OL-19988-01
Chapter 1
Activating or Deactivating IVR Zone Sets

To activate or deactivate an existing IVR zone set, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr zoneset activate name IVR_ZoneSet1
Purpose Enters configuration mode. Activates the newly created IVR zone set. Forcefully activates the specified IVR zone set. Deactivates the specified IVR zone set.
switch(config)# ivr zoneset activate name IVR_ZoneSet1 force
switch(config)# no ivr zoneset activate name IVR_ZoneSet1
Note
To replace the active IVR zone set with a new IVR zone set without disrupting traffic, activate the new IVR zone set without deactivating the current active IVR zone set.
Verifying IVR Zone and IVR Zone Set Configuration

Verify the IVR zone and IVR zone set configurations using the show ivr zone and show ivr zoneset commands. See Example 1-1 to Example 1-9.
Example 1-1 Displays the IVR Zone Configuration
switch# show ivr zone zone name sample_vsan2-3 pwwn 21:00:00:e0:8b:02:ca:4a vsan 3 pwwn 21:00:00:20:37:c8:5c:6b vsan 2 zone name ivr_qa_z_all pwwn 21:00:00:e0:8b:06:d9:1d pwwn 21:01:00:e0:8b:2e:80:93 pwwn 10:00:00:00:c9:2d:5a:dd pwwn 10:00:00:00:c9:2d:5a:de pwwn 21:00:00:20:37:5b:ce:af pwwn 21:00:00:20:37:39:6b:dd pwwn 22:00:00:20:37:39:6b:dd pwwn 22:00:00:20:37:5b:ce:af pwwn 50:06:04:82:bc:01:c3:84
vsan vsan vsan vsan vsan vsan vsan vsan vsan
1 4 1 2 6 6 3 3 5
Example 1-2
Displays Information for a Specified IVR Zone
switch# show ivr zone name sample_vsan2-3 zone name sample_vsan2-3 pwwn 21:00:00:e0:8b:02:ca:4a vsan 3 pwwn 21:00:00:20:37:c8:5c:6b vsan 2
Example 1-3
Displays the Specified Zone in the Active IVR Zone
switch# show ivr zone name sample_vsan2-3 active
1-19
zone name sample_vsan2-3 pwwn 21:00:00:e0:8b:02:ca:4a vsan 3 pwwn 21:00:00:20:37:c8:5c:6b vsan 2
Example 1-4
Displays the IVR Zone Set Configuration
switch# show ivr zoneset zoneset name ivr_qa_zs_all zone name ivr_qa_z_all pwwn 21:00:00:e0:8b:06:d9:1d pwwn 21:01:00:e0:8b:2e:80:93 pwwn 10:00:00:00:c9:2d:5a:dd pwwn 10:00:00:00:c9:2d:5a:de pwwn 21:00:00:20:37:5b:ce:af pwwn 21:00:00:20:37:39:6b:dd pwwn 22:00:00:20:37:39:6b:dd pwwn 22:00:00:20:37:5b:ce:af pwwn 50:06:04:82:bc:01:c3:84
vsan vsan vsan vsan vsan vsan vsan vsan vsan
1 4 1 2 6 6 3 3 5
zoneset name IVR_ZoneSet1 zone name sample_vsan2-3 pwwn 21:00:00:e0:8b:02:ca:4a vsan 3 pwwn 21:00:00:20:37:c8:5c:6b vsan 2
Example 1-5
Displays the Active IVR Zone Set Configuration
switch# show ivr zoneset active zoneset name IVR_ZoneSet1 zone name sample_vsan2-3 pwwn 21:00:00:e0:8b:02:ca:4a vsan 3 pwwn 21:00:00:20:37:c8:5c:6b vsan 2
Example 1-6
Displays the Specified IVR Zone Set Configuration
switch# show ivr zoneset name IVR_ZoneSet1 zoneset name IVR_ZoneSet1 zone name sample_vsan2-3 pwwn 21:00:00:e0:8b:02:ca:4a vsan 3 pwwn 21:00:00:20:37:c8:5c:6b vsan 2
Example 1-7
Displays Brief Information for All IVR Zone Sets
switch# show ivr zoneset brief Active zoneset name IVR_ZoneSet1 zone name sample_vsan2-3
Example 1-8
Displays Brief Information for the Active IVR Zone Set
switch# show ivr zoneset brief Active zoneset name IVR_ZoneSet1 zone name sample_vsan2-3
1-20
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration IVR Logging
Example 1-9 Displays Status Information for the IVR Zone Set
status
switch# show ivr zoneset Zoneset Status _______________ name : state : last activate time : force option : status per vsan: __________________ vsan status ____ ______ 1 active 2 active
IVR_ZoneSet1 activation success Sat Mar 22 21:38:46 1980 off
Tip
Repeat this configuration in all border switches participating in the IVR configuration.
Note
You can use Cisco Fabric Manager to distribute IVR zone configurations to all IVR-capable switches in the interconnected VSAN network. Refer to the Cisco Fabric Manager Inter-VSAN Routing Configuration Guide.
Clearing the IVR Zone Database

Clearing a zone set only erases the configured zone database, not the active zone database. To clear the IVR zone database, use the clear ivr zone database command.
switch# clear ivr zone database
This command clears all configured IVR zone information.
Note
After issuing a clear ivr zone database command, you need to explicitly issue the copy running-config startup-config command to ensure that the running configuration is used when you next start the switch.
IVR Logging
You can configure Telnet or SSH logging for the IVR feature. For example, if you configure the IVR logging level at level 4 (warning), then messages with a severity level of 4 or above are displayed. Use the instructions in this section to configure and verify the logging levels:

Configuring IVR Logging Severity Levels, page 1-22 Verifying Logging Level Configuration, page 1-22
1-21
Chapter 1 Database Merge Guidelines
Configuring IVR Logging Severity Levels

To configure the severity level for logging messages from the IVR feature, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# logging level ivr 4
Purpose Enters configuration mode. Configures Telnet or SSH logging for the IVR feature at level 4 (warning). As a result, logging messages with a severity level of 4 or above are displayed.
Verifying Logging Level Configuration

Use the show logging level command to view the configured logging level for the IVR feature.
switch# show logging level Facility Default Severity ----------------------... ivr 5 ... 0(emergencies) 1(alerts) 3(errors) 4(warnings) 6(information) 7(debugging) Current Session Severity -----------------------4 2(critical) 5(notifications)
Database Merge Guidelines

A database merge refers to the combination of the configuration database and static (unlearned) entries in the active database. For information on CFS merge support, refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide or Cisco Fabric Manager System Management Configuration Guide. Consider the following when merging two IVR fabrics:

The IVR configurations are merged even if two fabrics contain different configurations. If dissimilar zones exist in two merged fabrics, the zone from each fabric is cloned in the distributed zone set with appropriate names (see Figure 1-3).
1-22
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration Database Merge Guidelines
Figure 1-3 Fabric Merge Consequences
Fabrics with dissimilar zones Fabric X
Both zones contained in the zone set Fabric XY
Cisco MDS switch Fabric Y
Cisco MDS switch
Cisco MDS switch
Cisco MDS switch
Cisco MDS switch

ISL
Cisco MDS switch witch
ivzs1 ivz1 wwn1 wwn2
ivzs1 ivz1 wwn3 wwn4
You can configure different IVR configurations in different Cisco MDS switches. To avoid traffic disruption, after the database merge is complete, the configuration is a combination of the configurations that were present on the two switches involved in the merge.
The configurations are merged even if both fabrics have different configurations. A combination of zones and zone sets are used to get the merged zones and zone sets. If a
dissimilar zone exists in two fabrics, the dissimilar zones are cloned into the zone set with appropriate names so both zones are present.
The merged topology contains a combination of the topology entries for both fabrics. The merge will fail if the merged database contains more topology entries than the allowed
maximum.
The total number of VSANs across the two fabrics cannot exceed 128.
Note
VSANs with the same VSAN ID but different AFIDs are counted as two separate VSANs.
The total number of IVR-enabled switches across the two fabrics cannot exceed 128. The total number of zone members across the two fabrics cannot exceed 10,000. As of Cisco
SAN-OS Release 3.0(3), the total number of zone members across the two fabrics cannot exceed 20,000. A zone member is counted twice if it exists in two zones.
Note
If one or more of the fabric switches are running Cisco SAN-OS Release 3.0(3) or later, and the number of zone members exceeds 10,000, you must either reduce the number of zone members in the fabric or upgrade all switches in both fabrics to Cisco SAN-OS Release 3.0(3) or later.
1-23
120541
ivzs1 ivz1 wwn1 wwn2 ivz1 wwnC wwn3 wwn4
ivzs1 ivz1 wwn1 wwn2 ivz1 wwnC wwn3 wwn4
Chapter 1 Database Merge Guidelines
The total number of zones across the two fabrics cannot exceed 2000. As of Cisco SAN-OS
Release 3.0(3), the total number of zones across the two fabrics cannot exceed 8000.
Note
If only some of the switches in the fabrics are running Cisco SAN-OS Release 3.0(3) or later, and if the number of zones exceeds 2000, you must either reduce the number of zones in the fabric or upgrade all switches in both fabrics to Cisco SAN-OS Release 3.0(3) or later.
The total number or zone sets across the two fabrics cannot exceed 32.
Table 1-6 describes the results of a CFS merge of two IVR-enabled fabrics under different conditions.
Table 1-6 Results of Merging Two IVR-Enabled Fabrics
IVR Fabric 1 NAT enabled Auto mode enabled Conflicting AFID database Conflicting IVR zone set database
IVR Fabric 2 NAT disabled Auto mode disabled
After Merge Merge succeeds and NAT is enabled Merge succeeds and IVR auto topology mode is enabled Merge fails Merge succeeds with new zones created to resolve conflicts
Combined configuration exceeds limits (such as maximum number Merge fails of zones or VSANs) Service group 1 Service group 2 Merge succeeds with service groups combined Merge fails Merge succeeds
User-configured VSAN topology configuration with conflicts User-configured VSAN topology configuration without conflicts
Caution
If you do not follow these conditions, the merge will fail. The next distribution will forcefully synchronize the databases and the activation states in the fabric.
Resolving Database Merge Failures

If a merge failure occurs, you can use the following CLI commands to display the error conditions:

show ivr merge status show cfs merge status name ivr show logging last lines (and look for MERGE failures)
To resolve merge failures, review the failure information indicated in the show command outputs, then find the scenario in this list that relates to the failure and follow the troubleshooting instructions:
If the failure is due to exceeding the maximum configuration limits in a fabric where the switches are running more than one Cisco SAN-OS or NX-OS release, then either upgrade the switches running the earlier release or reduce the number of IVR zones and IVR zone members on the switches running the more recent release to the earlier release limit (see IVR Configuration Limits on page 1-4).
1-24
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration IVR Auto Topology Mode Configuration Example
If the failure is due to exceeding maximum limits in a fabric where all switches are running the same Cisco SAN-OS or NX-OS release, identify the switch that has the correct configuration and perform a CFS commit to distribute the IVR configuration. See Distributing the IVR Configuration Using CFS on page 1-7 and Autonomous Fabric IDs on page 2-5. For other failures, resolve the error causing the merge failure on the switch that has the correct configuration and perform a CFS commit to distribute the IVR configuration. See Distributing the IVR Configuration Using CFS on page 1-7 and Autonomous Fabric IDs on page 2-5.
Note
After a successful CFS commit, the merge will be successful.
IVR Auto Topology Mode Configuration Example

This section provides example configuration steps for enabling IVR auto topology mode.
Step 1
Enable IVR on every border switch in the fabric.

switch# config t Enter configuration commands, one per line. switch(config)# feature ivr switch(config)# exit switch# End with CNTL/Z.
Step 2
Verify that IVR is enabled on every IVR-enabled switch.

switch# show ivr Inter-VSAN Routing is enabled Inter-VSAN enabled switches --------------------------No IVR-enabled VSAN is active. Check VSAN-Topology configuration. Inter-VSAN topology status -------------------------Current Status: Inter-VSAN topology is INACTIVE Inter-VSAN zoneset status ------------------------name : state : idle last activate time : Fabric distribution status ----------------------fabric distribution disabled Last Action : None Last Action Result : None Last Action Failure Reason : None Inter-VSAN NAT mode status -------------------------FCID-NAT is disabled License status ----------------IVR is running based on the following license(s) ENTERPRISE_PKG
1-25
Chapter 1 IVR Auto Topology Mode Configuration Example
Step 3
Enable CFS distribution on every IVR-enabled switch in the fabric.

switch# config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# ivr distribution
Step 4
Enable IVR auto topology mode.

switch(config)# ivr vsan-topology auto fabric is locked for configuration. Please commit after configuration is done.
Step 5
Commit the change to the fabric.

switch(config)# ivr commit switch(config)# exit switch#
Step 6
Verify the status of the commit request.

switch# show ivr session status Last Action : Commit Last Action Result : Success Last Action Failure Reason : None
Step 7
Verify the active IVR auto topology.

switch# show ivr vsan-topology active AFID SWITCH WWN Active Cfg. VSANS -------------------------------------------------------------1 20:00:00:0d:ec:08:6e:40 * yes no 1,336-338 1 20:00:00:0d:ec:0c:99:40 yes no 336,339
Step 8
Configure IVR zone set and zones. Two zones are required:

One zone has tape T (pwwn 10:02:50:45:32:20:7a:52) and server S1 (pwwn 10:02:66:45:00:20:89:04). Another zone has tape T and server S2 (pwwn 10:00:ad:51:78:33:f9:86).
Tip
Instead of creating two IVR zones, you can also create one IVR zone with the tape and both servers.
mds(config)# ivr zoneset name tape_server1_server2 mds(config-ivr-zoneset)# zone mds(config-ivr-zoneset-zone)# mds(config-ivr-zoneset-zone)# mds(config-ivr-zoneset-zone)# mds(config-ivr-zoneset)# zone mds(config-ivr-zoneset-zone)# mds(config-ivr-zoneset-zone)# mds(config-ivr-zoneset-zone)# name tape_server1 member pwwn 10:02:50:45:32:20:7a:52 vsan 1 member pwwn 10:02:66:45:00:20:89:04 vsan 2 exit name tape_server2 member pwwn 10:02:50:45:32:20:7a:52 vsan 1 member pwwn 10:00:ad:51:78:33:f9:86 vsan 3 exit
Step 9
View the IVR zone configuration to confirm that the IVR zone set and IVR zones are properly configured.
mds(config)# do show ivr zoneset zoneset name tape_server1_server2 zone name tape_server1 pwwn 10:02:50:45:32:20:7a:52 vsan 1 pwwn 10:02:66:45:00:20:89:04 vsan 2
1-26
OL-19988-01
Chapter 1
Basic Inter-VSAN Routing Configuration IVR Auto Topology Mode Configuration Example
zone name tape_server2 pwwn 10:02:50:45:32:20:7a:52 vsan 1 pwwn 10:00:ad:51:78:33:f9:86 vsan 3
Step 10
View the zone set prior to IVR zone set activation. Prior to activating the IVR zone set, view the active zone set. Repeat this step for VSANs 2 and 3.
mds(config)# do show zoneset active vsan 1 zoneset name finance_dept vsan 1 zone name accounts_database vsan 1 pwwn 10:00:23:11:ed:f6:23:12 pwwn 10:00:56:43:11:56:fe:ee zone name $default_zone$ vsan 1
Step 11
Activate the configured IVR zone set.

mds(config)# ivr zoneset activate name tape_server1_server2 zoneset activation initiated. check inter-VSAN zoneset status mds(config)# exit mds#
Step 12
Verify the IVR zone set activation.

mds# show ivr zoneset active zoneset name tape_server1_server2 zone name tape_server1 pwwn 10:02:50:45:32:20:7a:52 vsan 1 pwwn 10:02:66:45:00:20:89:04 vsan 2 zone name tape_server2 pwwn 10:02:50:45:32:20:7a:52 vsan 1 pwwn 10:00:ad:51:78:33:f9:86 vsan 3
Step 13
Verify the zone set updates. Upon successful IVR zone set activation, verify that appropriate zones are added to the active zone set. Repeat this step for VSANs 2 and 3.
mds# show zoneset active vsan 1 zoneset name finance_dept vsan 1 zone name accounts_database vsan 1 pwwn 10:00:23:11:ed:f6:23:12 pwwn 10:00:56:43:11:56:fe:ee zone name IVRZ_tape_server1 vsan 1 pwwn 10:02:66:45:00:20:89:04 pwwn 10:02:50:45:32:20:7a:52 zone name IVRZ_tape_server2 vsan 1 pwwn 10:02:50:45:32:20:7a:52 pwwn 10:00:ad:51:78:33:f9:86 zone name $default_zone$ vsan 1 mds# show ivr zoneset status Zoneset Status ______________ name : tape_server1_server2 state : activation success last activate time : Tue May 20 23:23:01 1980 force option : on status per vsan: __________________ vsan status
1-27
Chapter 1 Default Settings
____ 1 ______ active
Default Settings
Table 1-7 lists the default settings for IVR parameters.
Table 1-7 Default IVR Parameters
Parameters IVR feature IVR VSANs IVR NAT QoS for IVR zones Configuration distribution
Default Disabled Not added to virtual domains Disabled Low Disabled
1-28
OL-19988-01
CH A P T E R
Advanced Inter-VSAN Routing Configuration

This chapter provides advanced configuration information and instructions. Before setting up advanced IVR configurations, see Chapter 1, Basic Inter-VSAN Routing Configuration, includes basic configuration instructions and descriptions of IVR features, limits, and terminology. This chapter includes the following sections:

Advanced IVR Configuration Task List, page 2-1 Advanced IVR Configuration, page 2-2 IVR Without IVR NAT or IVR Auto Topology Mode, page 2-7 Manually Configuring and Activating an IVR Topology, page 2-9 Working with Existing IVR Topologies, page 2-11 Persistent FC IDs for IVR, page 2-14 Advanced IVR Zones and IVR Zone Sets, page 2-17 Enabling Advanced Fabric Services on IVR Flows, page 2-20
Advanced IVR Configuration Task List

To configure an advanced IVR topology in a SAN fabric, follow these steps: Configuration Task
Step 1
Resource See IVR Network Address Translation on page 1-5 and IVR NAT Requirements and Guidelines on page 1-10.
Determine whether or not to use IVR Network Address Translation (NAT).
Step 2
If you do not plan to use IVR NAT, verify See Domain ID Guidelines on page 2-8. that unique domain IDs are configured in all switches and VSANs participating in IVR. Enable IVR in the border switches. Configure the service group as required. SeeEnabling IVR on page 1-7. See IVR Service Groups on page 2-2.
Step 3
Step 4 Step 5
Configure the IVR distribution as required. See Distributing the IVR Configuration Using CFS on page 1-7.
2-1
Chapter 2 Advanced IVR Configuration
Configuration Task
Step 6
Resource SeeManually Configuring and Activating an IVR Topology on page 2-9 and Basic IVR Configuration on page 1-6. See Advanced IVR Zones and IVR Zone Sets on page 2-17. SeeVerifying the IVR Topology on page 2-13.
Configure the IVR topology, either manually or automatically. Create and activate IVR zone sets in all of the IVR-enabled border switches, either manually or using fabric distribution. Verify the IVR configuration.
Step 7
Step 8
Advanced IVR Configuration

This section includes instructions on advanced IVR configurations. It includes the following topics:

IVR Service Groups, page 2-2 Autonomous Fabric IDs, page 2-5
IVR Service Groups

In a complex network topology, you might only have a few IVR-enabled VSANs. To reduce the amount of traffic to non-IVR-enabled VSANs, you can configure service groups that restrict the traffic to the IVR-enabled VSANs. A maximum of 16 IVR service groups are allowed in a network. When a new IVR-enabled switch is added to the network, you must update the service groups to include the new VSANs. This section includes the following information on service groups:

Service Group Guidelines, page 2-2 Default Service Group, page 2-3 Service Group Activation, page 2-3 Configuring IVR Service Groups, page 2-4 Copying the Active IVR Service Group Database, page 2-5 Clearing IVR Service Group Database, page 2-5 Verifying IVR Service Group Configuration, page 2-5
Service Group Guidelines

When configuring IVR service groups, consider these guidelines:

If you use service groups with IVR auto topology mode, you should enable IVR and configure your service groups first, then distribute them with CFS before setting the IVR auto topology mode. The CFS distribution is restricted within the service group only when the IVR VSAN topology is in IVR auto topology mode. See IVR VSAN Topology on page 1-5. You can configure as many as 16 service groups in a network. When a new IVR-enabled switch is added to the network, you must update the service group to include the new VSANs.
2-2
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Advanced IVR Configuration

The same VSAN and AFID combination cannot be a member of more than one service group, otherwise, a CFS merge will fail. The total number of AFID and VSAN combinations in all the service groups combined cannot exceed 128. The maximum number of AFID and VSAN combinations in a single service group is 128. The IVR service group configuration is distributed in all IVR-enabled switches. IVR data traffic between two end devices belonging to a service group stays within that service group. For example, two members (for example, pWWN 1 and pWWN 2) cannot communicate if they belong to the same IVR zone and they belong to different service groups. During a CFS merge, service groups with the same name would be merged, as long as there are no conflicts with other service groups. If the total number of service groups exceeds 16 during a CFS merge, the CFS merge fails. CFS distributes service group configuration information to all reachable SANs. If you do not enable CFS distribution, you must ensure that the service group configuration is the same on all IVR-enabled switches in all VSANs. IVR end devices belonging to an IVR service group are not exported to any AFID or VSAN outside of its service group. When at least one service group is defined and an IVR zone member does not belong to the service group, that IVR zone member is not able to communicate with any other device. The default service group ID is zero (0).
Default Service Group

All AFID and VSAN combinations that are part of an IVR VSAN topology but are not part of any user-defined service group are members of the default service group. The identifier of the default service group is 0. By default, IVR communication is permitted between members of the default service group. You can change the default policy to deny. To change the default policy, see Configuring IVR Service Groups on page 2-4. The default policy is not part of ASCII configuration.
Service Group Activation

A configured service group must be activated. Like zone set activation or VSAN topology activation, the activation of a configured service group replaces the currently active service group, if any, with the configured one. There is only one configured service group database and one active service group database. Each of these databases can have up to 16 service groups.
2-3
Configuring IVR Service Groups

To configure an IVR service group, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr service-group name IVR-SG1 switch(config-ivr-sg)#
Purpose Enters configuration mode. Configures the IVR service group called IVR-SG1 and enters IVR server group configuration mode. Deletes the IVR service group.
switch(config)# no ivr service-group name IVR-SG1 Successfully erased service group IVR-SG1
Step 3
switch(config-ivr-sg)# autonomous-fabric-id 10 vsan-ranges 1,2,6-10 switch(config-ivr-sg)# autonomous-fabric-id 11 vsan-ranges 1 switch(config-ivr-sg)# autonomous-fabric-id 12 vsan-ranges 3-5 switch(config-ivr-sg)# no autonomous-fabric-id 12 vsan-ranges 3-5 switch(config-ivr-sg)# exit switch(config)# switch(config)# ivr service-group name IVR-SG2 switch(config-ivr-sg)#
Configures AFID 10 for VSANs 1, 2, and 6 through 10. Configures AFID 11 for VSAN 1. Configures AFID 12 for VSANs 3 through 5. Removes the association between AFID 12 and VSANs 3 through 5. Returns to configuration mode. Configures the IVR service group called IVR-SG2 and enters IVR server group configuration mode. Configures AFID 20 for VSANs 3 through 5. Returns to configuration mode. Activates the service group configuration and sets the communication policy between switches in the default service group as allow (default). Activates the service group configuration and sets the communication policy between switches in the default service group to deny.
Note
switch(config-ivr-sg)# autonomous-fabric-id 20 vsan-ranges 3-5
Step 4 Step 5
switch(config-ivr-sg)# exit switch(config)# switch(config)# ivr service-group activate
switch(config)# ivr service-group activate default-sg-deny
To change the communication policy back to allow, you must issue the ivr service-group activate command again.
switch(config)# no ivr service-group activate
Deactivates (default) the service group configuration. Activates the VSAN topology. Enables CFS distribution for the IVR configuration. Commits the IVR configuration to the fabric.
switch(config)# ivr vsan-topology activate switch(config)# ivr distribute
switch(config)# ivr commit
2-4
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Advanced IVR Configuration
Copying the Active IVR Service Group Database

You can modify the configured IVR service group database; however, you cannot modify the active IVR service group database. To copy the active IVR service group database to the manually configured service group database, use the following command in EXEC mode:
switch# ivr copy active-service-group user-configured-service-group
Clearing IVR Service Group Database

You can clear all entries in the IVR service group database by using the clear ivr service-group database command in EXEC mode. This command only clears the configured database, not the active database.
switch# clear ivr service-group database
Verifying IVR Service Group Configuration

Use the show ivr service-group active command to view the active IVR service group database.
switch# show ivr service-group active IVR ACTIVE Service Group ==================================== SG-ID SG-NAME AFID VSANS -----------------------------------------------------------------------------1 IVR-SG1 10 1-2,6-10 1 IVR-SG1 11 1 2 IVR-SG2 20 3-5 Total: 3 entries in active service group table
Use the show ivr service-group configured command to view the configured IVR service group database.
switch# show ivr service-group configured IVR CONFIGURED Service Group ==================================== SG-ID SG-NAME AFID VSANS -----------------------------------------------------------------------------1 IVR-SG1 10 1-2,6-10 1 IVR-SG1 11 1 2 IVR-SG2 20 3-5 Total: 3 entries in configured service group table
Autonomous Fabric IDs

The autonomous fabric ID (AFID) distinguishes segmented VSANS (for example, two VSANs that are logically and physically separate but have the same VSAN number). Cisco MDS NX-OS Release 4.2(1) supports AFIDs 1 through 64. AFIDs are used in conjunction with IVR auto topology mode to allow segmented VSANs in the IVR VSAN topology database.
2-5
This section includes the following information about AFIDs:

Autonomous Fabric ID Guidelines, page 2-6 Configuring Default AFIDs, page 2-6 Configuring Individual AFIDs, page 2-7 Verifying the AFID Database Configuration, page 2-7
Autonomous Fabric ID Guidelines

You can configure AFIDs individually for VSANs, or you can set the default AFIDs for all VSANs on a switch. If you configure an individual AFID for a subset of the VSANs on a switch that has a default AFID, that subset uses the configured AFID while all other VSANs on that switch use the default AFID. You can only use an AFID configuration when the VSAN topology is in IVR auto topology mode. In IVR manual topology mode, the AFIDs are specified in the VSAN topology configuration itself and a separate AFID configuration is not needed.
Note
Two VSANs with the same VSAN number but different AFIDs are counted as two VSANs out of the total 128 VSANs allowed in the fabric. When devices attached to multiple switches belong to one VSAN, they cannot communicate with each other by configuring the regular zone set because the AFIDs are different. You can consider that the different AFIDs are different fabrics; therefore, the three switches represent three separate fabrics. If we specify the IVR VSAN topology as shown in Example 2-1, IVR will set up the connection between the devices across the switches even though they have the same VSAN.
Example 2-1 IVR VSAN Topology with the Same VSAN
switch# show ivr vsan-topology AFID SWITCH WWN Active Cfg. VSANS ----------------------------------------------------1 20:00:00:0d:ec:27:6b:c0 yes yes 1 2 20:00:00:0d:ec:27:6c:00 yes yes 1 3 20:00:00:0d:ec:27:6c:40 yes yes 1 Total: 3 entries in active and configured IVR VSAN-Topology
Configuring Default AFIDs

To configure the default AFID, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# autonomous-fabric-id database
Purpose Enters configuration mode. Enters AFID database configuration submode.
2-6
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration IVR Without IVR NAT or IVR Auto Topology Mode
Command
Step 3
switch(config-afid-db)# switch-wwn 20:00:00:0c:91:90:3e:80 default-autonomous-fabric-id 5 switch(config-afid-db)# no switch-wwn 20:00:00:0c:91:90:3e:80 default-autonomous-fabric-id 5
Purpose Configures the default AFID for all VSANs not explicitly associated with an AFID. The valid range for the default AFID is 1 to 64. Reverts to the default value (1) for the default AFID.
Configuring Individual AFIDs

To configure individual AFIDs, follow these steps: Command
switch# config t switch(config)# switch(config)# autonomous-fabric-id database switch(config-afid-db)# switch-wwn 20:00:00:0c:91:90:3e:80 autonomous-fabric-id 10 vsan-ranges 1,2,5-8 switch(config-afid-db)# no switch-wwn 20:00:00:0c:91:90:3e:80 autonomous-fabric-id 10 vsan-ranges 2
Purpose Enters configuration mode. Enters AFID database configuration submode. Configures an AFID and VSAN range for a switch. The valid range for AFIDs is 1 to 64. Deletes VSAN 2 from AFID 10.
Verifying the AFID Database Configuration

To view the contents of the AFID database, use the show autonomous-fabric-id database command.
switch# show autonomous-fabric-id database SWITCH WWN Default-AFID -------------------------------------------------------------20:00:00:0c:91:90:3e:80 5
Total:
1 entry in default AFID table
SWITCH WWN AFID VSANS -------------------------------------------------------------20:00:00:0c:91:90:3e:80 10 1,2,5-8
Total:
1 entry in AFID table
IVR Without IVR NAT or IVR Auto Topology Mode

This section includes the following sections on IVR without IVR NAT or IVR auto topology mode:

IVR Without IVR NAT or IVR Auto Topology Guidelines, page 2-8 Manually Configuring an IVR Topology, page 2-10
2-7
Chapter 2 IVR Without IVR NAT or IVR Auto Topology Mode
IVR Without IVR NAT or IVR Auto Topology Guidelines

Before configuring an IVR SAN fabric without IVR in NAT mode or IVR auto topology mode, consider the following general guidelines:

Acquire a mandatory Enterprise License Package or SAN-EXTENSION license package and one active IPS card for this feature. If you change an FSPF link cost, ensure that the FSPF path distance (the sum of the link costs on the path) of any IVR path is less than 30,000. IVR-enabled VSANs can be configured when an interop mode is enabled or disabled. Domain ID Guidelines, page 2-8 Transit VSAN Guidelines, page 2-8 Border Switch Guidelines, page 2-9
This section also includes the following:

Domain ID Guidelines
Before configuring domain IDs, consider the following guidelines:
Configure unique domain IDs across all VSANs and switches participating in IVR operations if you are not using IVR NAT. The following switches participate in IVR operations:
All edge switches in the edge VSANs (source and destination) All switches in transit VSANs
Minimize the number of switches that require a domain ID assignment. This ensures minimum traffic disruption. Minimize the coordination between interconnected VSANs when configuring the SAN for the first time as well as when you add each new switch. Configure the allowed-domains list so that the domains in different VSANs are non-overlapping on all participating switches and VSANs. Configure static, non-overlapping domains for each participating switch and VSAN.
You can configure domain IDs using one of two options:

Note
In a configuration involving IVR without NAT, if one VSAN in the IVR topology is configured with static domain IDs, then the other VSANs (edge or transit) in the topology must be configured with static domain IDs.
Transit VSAN Guidelines

Before configuring transit VSANS, consider the following guidelines:
Besides defining the IVR zone membership, you can choose to specify a set of transit VSANs to provide connectivity between two edge VSANs:
If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though, not
prohibited) to provide connectivity.
2-8
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Manually Configuring and Activating an IVR Topology
If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs
to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled on a switch that is a member of both the source and destination edge VSANs.

Traffic between the edge VSANs only traverses through the shortest IVR path. Transit VSAN information is common to all IVR zone sets. Sometimes, a transit VSAN can also act as an edge VSAN in another IVR zone.
Border Switch Guidelines

Before configuring border switches, consider the following guidelines:

Configure IVR only in the relevant border switches. Border switches require Cisco MDS SAN-OS Release 1.3(1) or later. A border switch must be a member of two or more VSANs. A border switch that facilitates IVR communications must be IVR enabled. IVR can also be enabled on additional border switches to provide redundant paths between active IVR zone members. The VSAN topology configuration must be updated before a border switch is added or removed.
Manually Configuring and Activating an IVR Topology

You must create the IVR topology on every IVR-enabled switch in the fabric if you have not enabled IVR auto topology mode. To use IVR manual topology mode, follow the instructions in this section. This section includes the following:

Manual Configuration Guidelines, page 2-9 Manually Configuring an IVR Topology, page 2-10 Activating a Manually Configured IVR Topology, page 2-11 Viewing an Active IVR Topology, page 2-11
Manual Configuration Guidelines

Consider the following guidelines when using IVR manual topology mode:

You can configure a maximum of 128 IVR-enabled switches and 128 distinct VSANs in an IVR topology (see Database Merge Guidelines on page 1-22). You will need to specify the IVR topology using the following information:
The switch WWNs of the IVR-enabled switches. A minimum of two VSANs to which the IVR-enabled switch belongs. The AFID, which distinguishes two VSANs that are logically and physically separate, but have
the same VSAN number. You can specify up to 64 AFIDs. See Figure 2-1.
2-9
Chapter 2 Manually Configuring and Activating an IVR Topology
Figure 2-1 Example IVR Topology with Non-Unique VSAN IDs Using AFIDs
VSAN 10 AF ID 2
VSAN 5
VSAN 10 AF ID 5
IVR-Enabled MDS switch
Transit VSAN
IVR-Enabled MDS switch

130184
If two VSANs in an IVR topology have the same VSAN ID and different AFIDs, they count as two VSANs for the 128-VSAN limit for IVR. The use of a single AFID does not allow for segmented VSANs in an inter-VSAN routing topology.
Manually Configuring an IVR Topology

Note
Use the show wwn switch command to obtain the switch WWNs of the IVR-enabled switches. To manually configure an IVR topology using Cisco NX-OS, follow these steps: Command Purpose Enters configuration mode. Enters the VSAN topology database configuration mode for the IVR feature. Configures VSANs 1, 2, and 6 to participate in IVR for this switch. Configures VSANs 1, 2 and 3 to participate in IVR for this switch. Removes VSANs 1 and 2 from IVR for this switch. Returns to EXEC mode.
Step 1 Step 2
switch# config t switch(config)# ivr vsan-topology database switch(config-ivr-topology-db)#
Step 3
switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch 20:00:00:05:30:01:1b:b8 vsan-ranges 1-2,6 switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch 20:00:00:05:30:01:1b:c2 vsan-ranges 1-3 switch(config-ivr-topology-db)# no autonomous-fabric-id 1 switch 20:00:00:05:30:01:1b:c2 vsan-ranges 1-2
Step 4
switch(config-ivr-topology-db)# end switch#
View the IVR topology using the show ivr vsan-topology command. In the following example output, VSAN 2 is the transit VSAN between VSANs 1, 5, and 6.
switch# show ivr vsan-topology AFID SWITCH WWN Active Cfg. VSANS -------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * no yes 1-2 1 20:02:00:44:22:00:4a:05 no yes 1-2,6 1 20:02:00:44:22:00:4a:07 no yes 2-5 Total: 3 entries in active and configured IVR VSAN-Topology
2-10
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Working with Existing IVR Topologies
Current Status: Inter-VSAN topology is INACTIVE
Repeat this configuration on all IVR-enabled switches or distribute the IVR configuration using CFS. See Distributing the IVR Configuration Using CFS on page 1-7.
Tip
Transit VSANs are deduced based on your configuration. The IVR feature does not have an explicit transit-VSAN configuration.
Activating a Manually Configured IVR Topology

After manually configuring the IVR topology, you must activate it.
Caution
Active IVR topologies cannot be deactivated. You can only switch to IVR auto topology mode. To activate a manually configured IVR topology, follow these steps: Command Purpose Enters configuration mode. Activates the manually configured IVR topology.
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr vsan-topology activate
Viewing an Active IVR Topology

View the active IVR topology using the show ivr vsan-topology command.
Current Status: Inter-VSAN topology is ACTIVE Last activation time: Mon Mar 24 07:19:53 2009
Note
Working with Existing IVR Topologies

This section includes advanced IVR configurations for existing IVR topologies:

Adding an IVR-Enabled Switch to an Existing IVR Topology, page 2-12 Copying the Active IVR Topology, page 2-13 Clearing a Manually Configured IVR Topology Database, page 2-13
2-11
Chapter 2 Working with Existing IVR Topologies

Verifying the IVR Topology, page 2-13 Migrating from IVR Auto Topology Mode to IVR Manual Topology Mode, page 2-14
Adding an IVR-Enabled Switch to an Existing IVR Topology

Before adding an IVR-enabled switch to an existing fabric, you must add an entry to the IVR topology for the new switch and activate the new IVR topology. To add the IVR-enabled switch to an existing IVR topology, follow these steps: Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8
switch# config t switch(config)# mds(config)# ivr vsan-topology database mds(config-ivr-topology-db)# mds(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:05:40:01:1b:c2 vsan-ranges 1,4 switch(config-ivr-topology-db)# exit switch(config)# switch(config)# ivr vsan-topology activate switch(config)# ivr commit
Purpose Enters configuration mode. Enters IVR VSAN topology database configuration submode. Adds the new IVR-enabled switch to the topology. Returns to configuration mode. Activates the IVR VSAN topology. Commits the IVR configuration change to the fabric. Returns to EXEC mode. Saves the running configuration.
switch(config)# exit switch# switch# copy running-config startup-config
After adding the switch to the IVR topology, enable IVR and CFS on the new switch (see Enabling IVR on page 1-7 and Distributing the IVR Configuration Using CFS on page 1-7).
Adding VSANs to an Existing IVR Topology

To add VSANs to an existing IVR topology you need to specify all VSANs in the command syntax. Example 2-2 shows an IVR configuration with VSANs 1101-1102 and VSANs 2101-2102. Example 2-2 shows the addition of VSANs 1103 and 2103 to the IVR topology.
Example 2-2 First IVR Configuration with VSANs 1101-1102 and 2101-2102
switch(config)# ivr enable switch(config)# ivr distribute switch(config)# ivr vsan-topology database switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:4a:5e:00 vsan-ranges 1101-1102,1199,3100,3150 switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:4a:5f:00 vsan-ranges 2101-2102,2199,3100,3150 switch(config)# ivr vsan-topology activate
Example 2-3
Adding VSANs 1103 and 2103 to the IVR Configuration
switch(config)# ivr enable
2-12
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Working with Existing IVR Topologies
switch(config)# ivr distribute switch(config)# ivr vsan-topology database switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:4a:5e:00 vsan-ranges 1101-1103,1199,3100,3150 switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:4a:5f:00 vsan-ranges 2101-2103,2199,3100,3150 switch(config)# ivr vsan-topology activate
Copying the Active IVR Topology

You can edit a manually configured IVR topology; however, you cannot edit an active IVR topology. To copy the active IVR topology database to the manually configure topology, issue the ivr copy active-topology user-configured-topology command in EXEC mode:
switch# ivr copy active-topology user-configured-topology
Clearing a Manually Configured IVR Topology Database

To clear a manually configured IVR topology database, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# no ivr vsan-topology database
Purpose Enters configuration mode. Clears the previously created IVR topology.
Verifying the IVR Topology

To verify the IVR topology, issue the show ivr vsan-topology command. See Example 2-4 to Example 2-6.
Example 2-4 Displays the Configured IVR VSAN Topology
Current Status: Inter-VSAN topology is ACTIVE Last activation time: Sat Mar 22 21:46:15 1980
Note

Example 2-5 Displays the Active IVR VSAN Topology
switch# show ivr vsan-topology active AFID SWITCH WWN Active
Cfg. VSANS
2-13
Chapter 2 Persistent FC IDs for IVR
-------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-2 1 20:02:00:44:22:00:4a:05 yes yes 1-2,6 1 20:02:00:44:22:00:4a:07 yes yes 2-5 Total: 5 entries in active IVR VSAN-Topology
Current Status: Inter-VSAN topology is ACTIVE Last activation time: Sat Mar 22 21:46:15
Example 2-6
Displays the Configured IVR VSAN Topology
switch# show ivr vsan-topology configured AFID SWITCH WWN Active Cfg. VSANS -------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-2 1 20:02:00:44:22:00:4a:05 yes yes 1-2,6 1 20:02:00:44:22:00:4a:07 yes yes 2-5 Total: 5 entries in configured IVR VSAN-Topology
Migrating from IVR Auto Topology Mode to IVR Manual Topology Mode
If you want to migrate from IVR auto topology mode to IVR manual topology mode, copy the active IVR VSAN topology database to the user-configured IVR VSAN topology database before switching modes. To migrate from IVR auto topology mode to IVR manual topology mode, follow these steps: Command
switch# ivr copy auto-topology user-configured-topology switch# config t switch(config)# switch(config)# ivr vsan-topology active
Purpose Copies the automatic IVR topology database to the user-configured IVR topology. Enters configuration mode. Disables IVR auto topology mode for the IVR topology database and enables IVR manual topology mode.
Persistent FC IDs for IVR

This section includes the following information:

FC ID Features and Benefits, page 2-14 FC ID Guidelines, page 2-15 Configuring Persistent FC IDs for IVR, page 2-16 Verifying the Persistent FC ID Configuration, page 2-16
FC ID Features and Benefits

FC ID persistence improves IVR management by providing the following features:
2-14
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Persistent FC IDs for IVR

Allows you to control and assign a specific virtual domain to use in a native VSAN. Allows you to control and assign a specific virtual FC ID for a device. Host devices always see the same FC ID for targets. FC IDs help you plan your SAN layout better by assigning virtual domains for IVR to use. FC IDs can make SAN monitoring and management easier. When you see the same domain or FC ID consistently assigned, you can readily determine the native VSAN or device to which it refers.
The benefits of persistent FC IDs for IVR are as follows:

FC ID Guidelines
Before configuring persistent FC IDs, consider the following:
You can configure two types of database entries for persistent IVR FC IDs:
Virtual domain entriesContain the virtual domain that should be used to represent a native
VSAN in a specific VSAN (current VSAN). Virtual domain entries contain the following information: Native AFID Native VSAN Current AFID Current VSAN Virtual domain to be used for the native AFID and VSAN in current AFID and VSAN
Virtual FC ID entriesContain the virtual FC ID that should be used to represent a device in a
specific VSAN (current VSAN). Virtual FC ID entries contain the following information: Port WWN Current AFID Current VSAN Virtual FC ID to be used to represent a device for the given pWWN in the current AFID and VSAN
If you use persistent FC IDs for IVR, we recommend that you use them for all the devices in the IVR zone set. We do not recommend using persistent FC IDs for some of the IVR devices while using automatic allocation for other devices. IVR NAT must be enabled to use IVR persistent FC IDs. In an IVR NAT configuration, if one VSAN in the IVR topology is configured with static domain IDs, then the IVR domains that can be exported to that VSAN must also be assigned static domains.
2-15
Chapter 2 Persistent FC IDs for IVR
Configuring Persistent FC IDs for IVR

To configure persistent FC IDs for IVR, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# ivr fcdomain database autonomous-fabric-num 21 vsan 22 switch(config-fcdomain)# switch(config)# no ivr fcdomain database autonomous-fabric-num 21 vsan 22
Purpose Enters configuration mode. Enters IVR fcdomain database configuration submode for current AFID 21 and VSAN 22. Deletes all the database entries, including all the corresponding persistent FC ID entries, for current AFID 21 and VSAN 22. Adds or replaces a database entry for native AFID 20, native VSAN 11, and domain 12, and enters IVR fcdomain FC ID configuration submode. Domains of all the corresponding persistent FC ID entries, if any, are also changed to 12. Deletes the virtual domain entry native AFID 20 and native VSAN 11, and all corresponding FC ID entries. Adds or replaces a database entry for mapping the pWWN to the FC ID. Deletes the database entries for the pWWN. Adds a database entry for mapping the device alias to the FC ID. Deletes the database entries for the device alias.
Step 3
switch(config-fcdomain)# native-autonomous-fabric-num 20 native-vsan 11 domain 12 switch(config-fcdomain-fcid)#
switch(config-fcdomain)# no native-autonomous-fabric-num 20 native-vsan 11
Step 4
switch(config-fcdomain-fcid)# pwwn 11:22:33:44:55:66:77:88 fcid 0x114466 switch(config-fcdomain-fcid)# no pwwn 11:22:33:44:55:66:77:88
Step 5
switch(config-fcdomain-fcid)# device-alias SampleName fcid 0x123456 switch(config-fcdomain-fcid)# no device-alias SampleName
Verifying the Persistent FC ID Configuration

Verify the persistent FC ID configuration using the show ivr fcdomain database command. See Example 2-7 and Example 2-8.
Example 2-7 Displays All IVR fcdomain Database Entries
switch# show ivr fcdomain database ---------------------------------------------------AFID Vsan Native-AFID Native-Vsan Virtual-domain ---------------------------------------------------1 2 10 11 0xc(12) 21 22 20 11 0xc(12) Number of Virtual-domain entries: 2 ---------------------------------------------------AFID Vsan Pwwn Virtual-fcid
2-16
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Advanced IVR Zones and IVR Zone Sets
---------------------------------------------------21 22 11:22:33:44:55:66:77:88 0x114466 21 22 21:22:33:44:55:66:77:88 0x0c4466 21 22 21:22:33:44:55:66:78:88 0x0c4466 Number of Virtual-fcid entries: 3
Example 2-8
Displays the IVR fcdomain Database Entries for a Specific AFID and VSAN
switch# show ivr fcdomain database autonomous-fabric-num 21 vsan 22 ---------------------------------------------------AFID Vsan Native-AFID Native-Vsan Virtual-domain ---------------------------------------------------21 22 20 11 0xc(12) Number of Virtual-domain entries: 1 ---------------------------------------------------AFID Vsan Pwwn Virtual-fcid ---------------------------------------------------21 22 11:22:33:44:55:66:77:88 0x114466 21 22 21:22:33:44:55:66:77:88 0x0c4466 21 22 21:22:33:44:55:66:78:88 0x0c4466 Number of Virtual-fcid entries: 3
Advanced IVR Zones and IVR Zone Sets

This section describes advanced configuration information for IVR zones and IVR zone sets. For basic information on configuring IVR zones and zone sets, see IVR Zones and IVR Zone Sets on page 1-14. As part of the IVR configuration, you need to configure one or more IVR zone to enable cross-VSAN communication. To achieve this, you must specify each IVR zone as a set of (pWWN, VSAN) entries. Different IVR zone sets can contain the same IVR zone, because IVR zones can be members of one or more IVR zone sets.
Note
The same IVR zone set must be activated on all of the IVR-enabled switches.
Caution
Prior to Cisco SAN-OS Release 3.0(3) you can only configure a total of 10,000 zone members on all switches in a network. As of Cisco SAN-OS Release 3.0(3) you can only configure a total of 20,000 zone members on all switches in a network. A zone member is counted twice if it exists in two zones. See Database Merge Guidelines on page 1-22. This section includes the following topics:

IVR Zone Configuration Guidelines, page 2-18 Configuring LUNs in IVR Zoning, page 2-18 Configuring the QoS Attribute, page 2-19 Verifying the QoS Attribute For an IVR Zone, page 2-19 Renaming IVR Zones and IVR Zone Sets, page 2-19
2-17
Chapter 2 Advanced IVR Zones and IVR Zone Sets

Clearing the Configured IVR Zone Database, page 2-20 Configuring IVR Using Read-Only Zoning, page 2-20
IVR Zone Configuration Guidelines

When interop mode is enabled, consider the following IVR configuration guidelines:

When a member's native VSAN is in interop mode (for example, when the interop mode is 2, 3, or 4), then ReadOnly, the QoS attribute, and LUN zoning are not permitted. When a members VSAN is already in interop mode and an attempt is made to configure ReadOnly, the QoS attribute, or LUN zoning, a warning message is displayed to indicate that the configuration is not permitted. When you configure ReadOnly, the QoS attribute, or LUN zoning first, and then change the members VSAN interop mode, a warning message is displayed to indicate the configuration is not permitted. You are then prompted to change the configuration.
Example 2-9 shows samples of the warning messages that are displayed when configuration changes are made that affect ReadOnly, the QoS attribute, and LUN zoning.
Example 2-9 IVR Zone Configuration Warning Messages
switch(config)# vsan database switch(config-vsan-db)# vsan 2 switch(config-vsan-db)# vsan 2 interop 2 switch(config-vsan-db)# exit switch(config)# ivr zoneset name ivr_zs1 switch(config-ivr-zoneset)# zone name ivr_z1 switch(config-ivr-zoneset-zone)# member pwwn 21:00:00:14:c3:3d:45:22 lun 0x32 vsan 2 VSAN is in interop mode, and LUN zoning cannot be set. switch(config)# ivr zoneset name switch(config-ivr-zoneset-zone)# switch(config-ivr-zoneset-zone)# member has been configured, zone switch(config-ivr-zoneset-zone)# zone member has been configured, ivr_zs1 switch(config-ivr-zoneset)# zone name ivr_z1 member pwwn 21:00:00:14:c3:3d:45:22 vsan 2 attribute read-only VSAN is in interop mode and zone cannot be set to READ-ONLY. attribute qos priority medium VSAN is in interop mode and QoS cannot be assigned to zone.
Configuring LUNs in IVR Zoning

LUN zoning can be used between members of active IVR zones.You can configure the service by creating and activating LUN zones between the desired IVR zone members in all relevant edge VSANs using the zoning interface or you can use LUN zoning directly supported by IVR. For more details on the advantages of LUN zoning, refer to the Cisco MDS 9000 Family NX-OS Fabric Configuration Guide or the Cisco Fabric Manager Fabric Configuration Guide. To configure LUNs in IVR zoning, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# ivr zone name IvrLunZone switch(config-ivr-zone)#
Purpose Enters configuration mode. Configures an IVR zone called IvrLunZone.
2-18
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Advanced IVR Zones and IVR Zone Sets
Command
Step 3
switch(config-ivr-zone)# member pwwn 10:00:00:23:45:67:89:ab lun 0x64 vsan 10
Purpose Configures an IVR zone member based on the specified pWWN and LUN value.
Note
The CLI interprets the LUN identifier value as a hexadecimal value whether or not the 0x prefix is included.
switch(config-ivr-zone)# member pwwn 10:00:00:23:45:67:89:ab lun 0x64 vsan 10 autonomous-fabric-id 20 switch(config-ivr-zone)# no member pwwn 20:81:00:0c:85:90:3e:80 lun 0x32 vsan 13 autonomous-fabric-id 10
Configures an IVR zone member based on the specified pWWN, LUN value, and AFID. Removes an IVR zone member.
Note
You can configure LUN zoning in an IVR zone set setup.
Configuring the QoS Attribute

To configure the QoS attribute for an IVR zone, follow these steps: Command
switch# config t switch(config)# switch(config)# ivr zone name IvrZone switch(config-ivr-zone)# switch(config-ivr-zone)# attribute qos priority medium switch(config-ivr-zone)# no attribute qos priority medium
Purpose Enters configuration mode. Configures an IVR zone called IvrZone. Configures the QoS for IVR zone traffic to medium. Reverts to the default QoS setting. The default is low.
Note
If other QoS attributes are configured, the highest setting takes priority.
Verifying the QoS Attribute For an IVR Zone

Use the show ivr zone command to verify the QoS attribute for an IVR zone.
switch(config)# show ivr zone zone name IvrZone attribute qos priority medium
Renaming IVR Zones and IVR Zone Sets

To rename an IVR zone, use the ivr zone rename command in EXEC mode.
switch# ivr zone rename ivrzone1 ivrzone2
2-19
Chapter 2 Enabling Advanced Fabric Services on IVR Flows
To rename an IVR zone set, use the ivr zoneset rename command in EXEC mode.
switch# ivr zoneset rename ivrzone1 ivrzone2
Clearing the Configured IVR Zone Database

Clearing a zone set erases the configured zone database, not the active zone database. To clear the configured IVR zone database, use the clear ivr zone database command. Command
Step 1 Step 2
switch# clear ivr zone database switch(config)# switch# copy running-config startup-config
Purpose Clears all configured IVR zone information. Ensures that the running configuration is used when you restart the switch.
Configuring IVR Using Read-Only Zoning

Read-only zoning (with or without LUNs) can be used between members of active IVR zones. To configure this service, you must create and activate read-only zones between the desired IVR zone members in all relevant edge VSANs using the zoning interface.
Note
Read-only zoning cannot be configured in an IVR zone set setup.
Enabling Advanced Fabric Services on IVR Flows

Advanced fabric services (such as SME and IOA) use fabric-wide FC-Redirect infrastructure to redirect the traffic flows. These services can now be enabled on IVR flows using an internal feature, Abstract ACL Manager (AAM). The steps to enable this functionality is listed in the following sub-sections:

Configuration Guidelines and Restrictions, page 2-20 Enabling AAM Support for IVR, page 2-21 Enabling IVR Support for FCR, page 2-22 Disabling AAM Support for IVR, page 2-22
Configuration Guidelines and Restrictions

The following prerequisites must be considered before enabling AAM for IVR:

CFS distribution must be enabled for IVR. AAM is supported only in IVR-NAT mode.
2-20
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Enabling Advanced Fabric Services on IVR Flows

The switches where the fabric services (such as SME and IOA) are enabled must be running the AAM supported NX-OS release 5.0(1) or later. FC-Redirect can be running in version 1 or version 2 mode. AAM support for IVR must be enabled before enabling IVR support for FCR. Generation 1 modules are not supported when IVR support is enabled for FCR. Specifically, ISLs should not be configured on Generation 1 modules, and the devices that support IVR for FCR should not be connected to Generation 1 modules. LUN zoning is not supported when AAM is enabled for IVR. IVR merge is supported only when both the fabrics have AAM enabled or both the fabrics have AAM disabled. The IVR merge will fail if one of the fabric has AAM enabled and the other fabric has AAM disabled. You must delete all the advanced fabric service (SME and IOA) configurations for IVR devices and then disable IVR support for FCR before disabling AAM support for IVR. Before downgrading to an earlier release to MDS NX-OS Release 5.0(1), you must delete all the advanced fabric service (SME and IOA) configurations for IVR devices, disable IVR support for FCR, and then disable AAM support for IVR.
Enabling AAM Support for IVR

To enable AAM for IVR, follow these steps: Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7
switch# config t switch(config)# switch(config)# feature ivr switch(config)# switch(config)# ivr distribute switch(config)# switch(config)# ivr nat switch(config)# switch(config)# ivr commit switch(config)# switch(config)# ivr aam register switch(config)# switch(config)# ivr commit switch(config)#
Purpose Enters the configuration mode.

1
Enables IVR. Enables CFS distribution for IVR.
Enables NAT mode for IVR. Commits IVR configuration changes. Enables AAM for IVR. Commits IVR configuration changes.
1. These commands must be executed on all IVR switches.
You can use the show ivr aam command to verify if AAM support is enabled for IVR.
switch(config)# show ivr aam AAM mode status -------------------------AAM is enabled
2-21
Enabling IVR Support for FCR

To enable IVR support for FCR, follow these steps: Command
Step 1 Step 2
switch# config t switch(config)# switch(config)# fc-redirect ivr-support enable switch(config)#
Purpose Enters the configuration mode. Enables IVR support for FCR.
You can use the show fc-redirect config command to verify if AAM support is enabled for FCR.
switch(config)# show fc-redirect config switch(config)# switch(config)# switch(config)#
Disabling AAM Support for IVR

To disable AAM support for IVR, follow these steps: Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7
switch# config t switch(config)# switch(config)# ivr aam pre-deregister-check switch(config)# show ivr aam pre-deregister-check
Purpose Enters the configuration mode. Checks for the existence of advanced fabric service configurations for IVR devices. Displays the status of the advanced fabric service configurations for IVR devices. Delete all the advanced fabric service (SME and IOA) configurations for IVR devices. Disables IVR support for FCR. Disables AAM support for IVR. Commits IVR configuration changes.
Refer to the Cisco MDS 9000 Family SME and IOA Configuration Guides.
switch(config)# no fc-redirect ivr-support enable switch(config)# no ivr aam register switch(config)# ivr commit switch(config)#
You must use the ivr aam pre-deregister-check command to see if there is any SME or IOA configuration for IVR devices, before disabling AAM support for IVR.
switch(config)# show ivr aam pre-deregister-check AAM pre-deregister check status -------------------------Run the "ivr aam pre-deregister-check" command first to check whether an ivr aam deregister can be done. switch(config)# ivr aam pre-deregister-check switch(config)# show ivr aam pre-deregister-check AAM pre-deregister check status ------------------------FAILURE
2-22
OL-19988-01
Chapter 2
Advanced Inter-VSAN Routing Configuration Enabling Advanced Fabric Services on IVR Flows
There are merged entries or AAM has not been enabled with the following switches: switch swwn 20:00:00:05:30:00:15:de User has two options: 1. User can go ahead to issue ivr commit, but the above switches in the fabric may fail to deregister. 2. User may also run "ivr abort", then resolve above switches and re-issue the ivr aam deregister. Warning: IVR AAM pre-deregister-check status may not be up-to-date. Please issue the command "ivr aam pre-deregister-check" to get updated status. switch(config)# ivr aam pre-deregister-check switch(config)# show ivr aam pre-deregister-check AAM pre-deregister check status -------------------------SUCCESS Warning: IVR AAM pre-deregister-check status may not be up-to-date. Please issue the command "ivr aam pre-deregister-check" to get updated status.
2-23
2-24
OL-19988-01
INDEX
A
advanced IVR configuration AFIDs configuring default description guidelines Auto mode configuration See AFIDs autonomous fabric identifiers. See AFIDs auto topology mode configuration guidelines enabling
1-12 1-9 1-12 2-6 2-7 2-1 2-17
current VSANs description

1-3
IVR zone zones and zone sets
D
domain IDs IVR configuration guidelines non-unique and IVR NAT unique
2-8 2-8 1-10
configuring individual
1-4, 2-5, 2-9 2-6
verifying database configuration
2-7
E
edge switches description edge VSANs description
1-3 1-4
autonomous fabric ID
F
Fabric Manager
1-7
B
basic IVR configuration basic configuration task list
1-6 1-1
FC ID configuring guidelines
2-16 2-14
features and benefits

2-15
Fibre Channel header modifications
1-5
border switches description

1-4 2-9
I
Inter-VSAN Routing zones. See IVR zones Inter-VSAN Routing zone sets. See IVR zone sets IVR activating topologies
2-11 1-4
IVR configuration guidelines
C
configuration limits
AF IDs
2-9
IN-1
Index
basic configuration border switch
1-4 2-9 2-9 1-1 1-6
virtual domains VSAN topologies
1-13 1-5 1-15 2-18
basic configuration task list border switch, guidelines border switches

1-4 1-4
zone communication zones

1-3, 1-15 to 1-16 1-3 1-7
zone configuration guidelines zone sets
border switch configuration guidelines configuration limits configuring advanced basic

1-6 1-22 2-7 2-2
Zone Wizard
1-6, 2-1
configuration task lists
IVR databases active

1-8 1-8 1-22
configured pending IVR logging

2-7 1-8
merge guidelines
configuring logging levels
configuring without auto topology configuring without IVR NAT guidelines current VSANs databases
1-8 1-28 1-15 2-8 1-3 1-22
configuring levels IVR logging levels
1-22
verifying configuration IVR manual configuration guidelines IVR NAT border switch, guidelines
2-8 2-9
1-22
database merge guidelines default settings
default zone policy domain ID guidelines edge switch edge switches edge VSANs enabling features
1-7 1-4 1-4 1-3
1-11 1-9
domain ID configuration guidelines

2-8
configuration guidelines description

1-10
enabling auto-discovery load balancing requirements

1-7 1-10 1-10
1-12
transit VSANs, guidelines IVR persistent FC IDs configuring

1-5 2-16 2-14
1-11
enabling distribution with CFS

1-2
Fibre Channel header modifications interoperability logging paths

1-22 1-3 1-6
persistent
verifying configuration IVR service groups activation

2-3 2-2
2-16
native VSANs
1-3
characteristics
2-14 2-20 2-2 to 2-5 1-3 2-8
persistent FC IDs read-only zoning service groups terminology transit VSANs
clearing
2-5 2-4 2-5
configuring default
2-3
copying active description

1-4
transit VSAN configuration guidelines

1-4
2-2
IN-2
OL-19988-01
Index
verifying configuration IVR topologies activating a manually configured topology adding IVR-enabled switches clearing manual entries configuring manually copying active topologies
2-13 2-10 2-13 1-12 2-12 2-11 2-5
maximum number renaming

2-19
1-4
verifying configuration IVR Zone Wizard

1-7
1-19
N
NAT. See IVR NAT native VSANs description
1-3
enabling automatic discovery
migrating from IVR auto topology mode to IVR manual topology mode 2-14 verifying configuration IVR virtual domains clearing
1-14 1-13 1-13 1-14 2-13
P
persistent FC IDs configuring description
1-18 2-16 2-14
configuring description IVR zones
verifying configuration
activating with force option advanced description clearing database configuring configuring LUNs description
2-17 1-15 1-21, 2-20
T
transit VSANs configuration guidelines description
1-4, 2-11 2-8 1-11
automatic creation
1-16 to ?? 2-18 1-7
configuring with IVR Zone Wizard

1-3, 1-14, 1-15 1-15 1-4
V
VSANs transit
2-11
differences with zones (table) maximum number of members maximum number of zones renaming
2-19 1-19
1-4
verifying configuration IVR zone sets activating

1-19
Z
2-19
verifying QoS configuration
zones configuration guidelines IVR communication read-only for IVR

1-15 2-20 2-18 1-15
advanced configuration description configuring deactivating description

2-17 1-16 to ?? 1-19 1-3, 1-14
differences with IVR zones
IN-3
Index
IN-4
OL-19988-01

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

Uploaded by

Copyright:

Available Formats

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

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

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

Uploaded by

Copyright:

Available Formats

Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o .