Cisco MDS 9000 series Configuration Manual

Send documentation comments to [e-mail]

Cisco MDS 90 00 Family I/O Accelerator
Configuration Guide

Cisco MDS 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: [phone]

800 553-NETS (6387)

Fax: [phone]

Text Part Number: OL-20708-01

Send documentation comments to [e-mail]

THE SPECIFICATIONS AND INFORMATION REGA RDING THE P RODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE W ITH OUT NOT ICE. A LL
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 RESPONSIBILIT Y FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRA NTY FO R THE A CCOMPA NYING PRODUCT A RE SET FORTH IN T HE INFORM ATION P ACKET 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 UCB’s 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 DO CUMENT FILES AND SOFTW ARE OF THESE SUPPL IERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM AL L WARRANTIES, EX PRESSED OR
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICUL AR PURPOSE AND NON INFRINGEMENT OR ARISIN G 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, LOS T PROFITS OR LOSS OR DAMAGE TO DATA ARISIN G OUT OF THE US E OR INABILI TY TO USE THIS MA NUAL, EVEN I F CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SU CH DAMA GES.

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Ci sco 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 G ood , Flip
Mino, Flipshare (Design), Flip Ultra, Flip Vide o, Flip Video (Design ), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work,
Live, Play, and Learn, Cisco
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 impl y a partner ship relati onshi p
between Cisco and any other company. (1002R)

Any Internet Protocol (IP) addresses and phone numbers us ed in thi s docu ment are not intend ed 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 I/O Accelerator Configuration Guide

© 2010 Cisco Systems, Inc. All rights reserved.

Capital, Cis c o Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and

IMPLIED, INCLUDING, WITHOUT

Send documentation comments to [e-mail]

CONTENTS

New and Changed Information ix
Preface xi

Audience xi
Organization xi
Document Conventions xii
Related Documentation xii

Release Notes xii
Regulatory Compliance and Safety Information xiii
Compatibility Information xiii
Hardware Installation xiii
Software Installation and Upgrade xiii
Cisco NX-OS xiii
Cisco Fabric Manager xiv
Command-Line Interface xiv
Intelligent Storage Networking Services Configuration Guides xiv
Troubleshooting and Reference xiv

CHAPTER

Obtaining Documentation and Submitting a Service Request xv

1 Overview 1-1

About Cisco I/O Accelerator 1-1

Unified Acceleration Service 1-1
Topology Independent 1-2
Transport Agnostic 1-2
High Availability and Resiliency 1-2
Improved Tape Acceleration Performance 1-2

Load Balancing 1-2
Example IOA Topology 1-3
Terminology 1-3
Clustering 1-5
Hardware Requirements 1-5
Software Requirements 1-5
License Requirements 1-6

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

iii

Contents

Send documentation comments to [e-mail]

CHAPTER

2 Getting Started 2-1

Enabling SSH 2-1
Enabling CFS 2-1
IP Access Lists 2-2
Zone Default Policy 2-2
FC-Redirect 2-2

FC-Redirect Unsupported Switches 2-2

FC-Redirect Requirements 2-2
Configuring FC-Redirect v2 Mode 2-3
Using FC-Redirect with CFS Regions 2-4

Guidelines for Designing CFS Regions For FC-Redirect 2-4

Configuring CFS Regions For FC-Redirect 2-5
Using IOA Cluster with IPFC Interface 2-5

Task Flow for Configuring IOA Cluster To Use the IPFC Interface 2-6

Configuring IOA Cluster To Use the IPFC Interface 2-6

Creating a VSAN Interface and Configuring IPv4 Addresses 2-6
Enabling IPv4 Routing 2-7
Verifying Connectivity 2-7
Creating IOA cluster and IOA interface in the Local Node 2-8
Verifying Cluster Configuration 2-8
Adding a Remote Node and IOA Interface to the Remote Node 2-8
Verifying the Cluster Configuration 2-9

Configuration Example 2-9

Creating an Interface VSAN 2-10
Verifying the Configuration 2-10
Verifying the Connectivity 2-11
Configuring IOA Site on Switch sw-231-14 2-11
Configuring IOA Site on Switch sw-231-19 2-11
Configuring IOA Cluster cltr1 on Switch sw-231-14 2-11
Changing the Node to Use IPFC Interface Address 2-11
Adding a Remote Node to the IOA Cluster 2-11
Adding an IOA Interface to the Switch sw-231-14 2-12
Adding an IOA Interface to the Switch sw-231-19 2-12
Verifying the Cluster Configuration 2-12
Verifying the IP Address 2-12

Verifying the IOA Interface 2-13
Task Flow for Converting an Existing IOA Cluster to use IPFC interface 2-13
Configuration Example for Converting IOA Cluster to Use the IPFC interface 2-13

Verifying the IOA Cluster Configuration 2-14

iv

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Contents

Send documentation comments to [e-mail]

Verifying the IP Address 2-14
Verifying the Flow Status 2-14
Shutting Down IOA Cluster on a Local Node 2-14
Shutting Down the IOA cluster on the remote node 2-15
Removing the IOA Cluster from the Remote Node 2-15
Verifying the IOA Cluster in the Remote Node 2-15
Removing the Remote Node from the Cluster in the Local Switch 2-15
Changing the Local Node Configuration to use IPFC Address 2-15
Activating the Single Node Cluster 2-15
Adding Remote Node with IPFC Address 2-16
Adding IOA Interfaces to the Remote Node 2-16
Verifying the Cluster Nodes 2-16
Verifying the Flow Status 2-16

CHAPTER

CHAPTER

3 Deployment Considerations 3-1

Supported Topologies 3-1

Core-Edge Topology 3-1
Edge-Core-Edge Topology 3-2
Collapsed Core Topology 3-3
Extended Core-Edge Topology 3-4
Extending Across Multiple Sites 3-5
IVR Topologies 3-6
Other Topologies 3-7

Deployment Guidelines 3-7

General Guidelines 3-7
Scalability and Optimal Performance Considerations 3-7

Resiliency Considerations 3-8
Limitations and Restrictions 3-8
Configuration Limits 3-10

4 Configuring IOA Using the CLI 4-1

Configuring IOA 4-2

Enabling Clustering 4-3

Enabling the IOA Service 4-3

Classifying the Switches to IOA Sites 4-3

Configuring IOA Interfaces 4-4

Displaying IOA Interface Status 4-4

Configuring an IOA Cluster 4-5

Displaying IOA Cluster Status 4-5

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

v

Contents

Send documentation comments to [e-mail]

Adding Nodes to an IOA Cluster 4-6
Adding Interfaces to an IOA Cluster 4-8
Adding N Ports to an IOA Cluster 4-9
Configuring the IOA Flows 4-10

IOA Flow Setup Wizard 4-11

Prerequisites for IOA Flow Setup Wizard 4-11

Using the IOA Flow Setup Wizard 4-11
Creating Multiple IOA Clusters on a Single Switch 4-14
Additional Configurations 4-15

Shutting Down a Cluster 4-15

Load Balancing the Flows 4-16

Setting the Tunable Parameters 4-16

Changing the Node Description and IP Address of an IOA Cluster 4-17

Guidelines for Changing the Node Description and IP Address of an IOA Cluster 4-18

Configuration Example for Changing the Node Description and Node IP Address of an IOA

Cluster 4-18

Shut Down the IOA Cluster on switch1 4-19
Shut Down the IOA Cluster on switch2 4-19
Remove the IOA Cluster on switch2 4-19
Remove the Node of switch2 in switch1 4-19
Change the Management Interface IP Address on Switches 4-20
Change the Node Description and IP Address on switch1 4-20
No Shut Down IOA Cluster on switch1 4-20
Add switch2 Node with New Description and the IP Address 4-20
Add IOA Interfaces on switch2 4-20
Verify the Node Description and IP Address and Flows 4-20

Displaying Interface Statistics 4-21

CHAPTER

vi

5 Configuring IOA Using Fabric Manager 5-1

IOA Manager 5-1

Toolbar 5-2
Launching IOA Manager 5-3
Configuring Sites 5-3

Adding a New Site 5-3

Removing a Site 5-4

Viewing a Site 5-5

Adding Switches to a Site 5-6

Removing Switches from a Site 5-7
Configuring Clusters 5-7

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Contents

Send documentation comments to [e-mail]

Adding a New Cluster 5-7
Removing a Cluster 5-9
Viewing Clusters 5-10

Configuring Interfaces 5-11

Assigning Interfaces to a Cluster 5-11
Removing Interfaces from a Cluster 5-12

Configuring Flows 5-13

Adding a Flow 5-13
Removing a Flow 5-15
Viewing Interface Statistics 5-16

APPENDIX

APPENDIX

A SCSI Write Acceleration and Tape Acceleration A-1

SCSI Write Acceleration A-1
SCSI Tape Acceleration A-2

B Cluster Management and Recovery Scenarios B-1

Cluster Quorum and Master Switch Election B-1

Cluster Quorum B-2
Master Switch Election B-2

Two-Switch Cluster Scenarios B-2
Three-Switch Cluster Scenarios B-3

Four-Switch Cluster Scenarios B-4
In-Service Software Upgrade (ISSU) in a Two-Node Cluster B-4
Supported Topologies B-5

Single-Fabric Topology B-5
Cluster Recovery Scenarios B-5

Deleting an Offline Switch from a Cisco IOA Cluster B-5
Deleting a Cisco IOA Cluster with One or More Offline Switches while the Master Switch is

Online B-6
Deleting a Cisco IOA Cluster when All Switches Are Offline B-7
Reviving a Cisco IOA Cluster B-8

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

vii

Contents

Send documentation comments to [e-mail]

viii

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Send documentation comments to [e-mail]

New and Changed Information

This document provides release-specific informati on for each new and changed feature for Cisco I/O
Accelerator. The Cisco MDS 9000 Family I/O Acceler ator Conf igurati on Guide applies t o Cisco NX-OS
and Fabric Manager Release 4.2(1) and later.

To check for additional information about this release and to determine if this release supports I/O
Accelerator, refer to the Cisco MDS 9000 Family Release Notes and Cisco Fabric Manager Release
Notes available at the following Cisco Systems website:

http://www.cisco.com/en/US/products/ps5989/prod_release_notes_list.html
Table 1 summarizes the new and changed features as described in the Cisco MDS 9000 Family I/O

Accelerator Configuration Guide, each supported NX-OS release for the Cisco MDS 9500 Series, with
the latest release first. The table includes a brief description of each new feature and the release in which
the change occurred.

Table 1 New and Changed Features for Cisco I/O Accelerator

Feature GUI Change Description

ISAPI enhancements - Added information about ISAPI

enhancements.

IOA is supported with
IVR

- Added IVR flows support with IOA 5.0(1a) Chapter 3, “Deployment

Changed
in
Release

5.0(1a) Chapter 4, “Configuring

Where Documented

IOA Using the CLI”

Considerations”

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

ix

New and Changed Information

Send documentation comments to [e-mail]

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

x

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Send documentation comments to [e-mail]

Preface

This preface describes the audience, organization, and conventions of the Cisco MDS 9000
Family

I/O Accelerator 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 the Cisco MDS 9000 Family I/O Accelerator (IOA) feature.

Organization

This document is organized as follows:

Chapter Title Description

Chapter 1 Overview Presents an overview of the Cisco MDS I/O

Chapter 2 Getting Started Describes the various configurations that need

Chapter 3 Deployment Considerations Describes the various deployment scenarios

Chapter 4 Configuring IOA Using the CLI Describes how to use IOA CLI commands to

Chapter 5 Configuring IOA Using Fabric

Appendix A SCSI Write Acceleration and Tape

Appendix B Cluster Management and Recovery

Manager

Acceleration

Scenarios

Accelerator feature and the software and
hardware requirements.

to be completed before configuring IOA.

and considerations.

configure and monitor Cisco IOA clusters.
Describes how to use Fabric Manager to

configure and monitor Cisco IOA clusters.
Describes the concept of SCSI write

acceleration, tape acceleration, and
compression.

Describes the cluster management g uidelines
and cluster recovery procedures.

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

xi

Preface

Send documentation comments to [e-mail]

Document Conventions

Command descriptions use these conventions:

boldface font Commands and keywords are in boldface.
italic font Arguments for which you supply values are in italics.
[ ] Elements in square brackets are optional.
[ x | y | z ] Optional alternative keywords are grouped in brackets and separated by

vertical bars.

Screen examples use these conventions:

screen font

boldface screen font

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 read er be caref ul. In this situation, you might do something that could result in equipment

damage or loss of data.

Related Documentation

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.

Release Notes

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

xii

The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a
document online, use the Cisco MDS NX-OS Documentation Locator at:

http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.htm

• 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

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Preface

Send documentation comments to [e-mail]

• 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

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 Fundamentals Configuration Guide

• Cisco MDS 9000 Family NX-OS Licensing Guide

• Cisco MDS 9000 Family NX-OS System Management Configuration Guide

• Cisco MDS 9000 Fa mily 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 Fa mily NX-OS Security Configuration Guide

• Cisco MDS 9000 Fa mily NX-OS IP Services Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

xiii

Preface

Send documentation comments to [e-mail]

• Cisco MDS 9000 Fa mily NX-OS Intelligent Storage Services Configuration Guide

• Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide

• Cisco MDS 9000 Fa mily NX-OS Inter-VSAN Routing Configuration Guide

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 Family I/O Accelerator 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

xiv

• Cisco NX-OS System Messages Reference

• Cisco MDS 9000 Fa mily 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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Preface

Send documentation comments to [e-mail]

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s
revised Cisco

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s 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.

technical documentation, at:

New in Cisco Product Documentation, which also lists all new and

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

xv

Preface

Send documentation comments to [e-mail]

xvi

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Send documentation comments to [e-mail]

Overview

This chapter provides an overview of the Cisco I/O Accelerator feature and includes the following
sections:

• About Cisco I/O Accelerator, page 1-1

• Example IOA Topology, page 1-3

• Terminology, page 1-3

• Hardware Requirements, page 1-5

• Software Requirements, page 1-5

• License Requirements, page 1-6

About Cisco I/O Accelerator

CHAPTER

1

The Cisco MDS 9000 Family I/O Accelerator (IOA) feature provides Small Computer System Interface
(SCSI) acceleration in a storage area network (SAN) where the sites are interconnected over long
distances using Fibre Channel or Fibre Channel over IP (FCIP) Inter-Switch Links (ISLs).

IOA provides these features, which are described in the following sections:

• Unified Acceleration Service, page 1-1

• Topology Independent, page 1-2

• Transport Agnostic, page 1-2

• High Availability and Resiliency, page 1-2

• Improved Tap e Accelera tion Perform ance, page 1-2

• Load Balancing, page 1-2

Unified Acceleration Service

IOA provides both SCSI write acceleration and tape acceleration features as a unified fabric service.
These services were provided in previous releases in the form of Fibre Channel write acceleration for
remote replication over Fibre Channel links and FCIP write acceleration and tape acceleration over FCIP
links. Fibre Channel write acceleration was offered on the Storage Services Module (SSM) and FCIP
write acceleration and tape acceleration were offered on the IP storage services modules. IOA of fers both

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

1-1

1 Overview

About Cisco I/O Accelerator

Send documentation comments to [e-mail]

the write acceleration and tap e accele ration se rvices on the Cisco M DS MSM -18/4 mo dule, SSN- 16
module, and 9222i switch as a fabric service. This elimin ates the need to buy separate hardware to obtain
Fibre Channel write acceleration and FCIP write acceleration and tape acceleration.

Topology Independent

IOA can be deployed anywhere in the fabric without rewiring the hardware or reconfiguring the fabric.
There are no restrictions on where the hosts and targets are connected to. Both the Fibre Channel and
FCIP write acceleration is supported only on PortChannels but do not support multiple equal-cost links.
FCIP tape acceleration is not supported on PortChannels. IOA eliminates these topological restrictions.

Transport Agnostic

IOA is completely transport-agnostic and is supported on both Fibre Channel and FCIP ISLs between
two sites.

High Availability and Resiliency

IOA equally supports both PortChannels and equal-cost multiple path (ECMP) links across two data
centers. This allows you to seamlessly add ISLs across the two data centers for capacity building or
redundancy . IO A is completely resilient against ISL f ailures. IO A uses a Lightweight Reliable T ransport
Protocol (LRTP) to guard against any ISL failures as long as there is an alternate path available across
the two data centers. Remote replication and tape backup applications are completely unaffected by these
failures.

Improved Tape Acceleration Performance

IOA tape acceleration provides higher throughput numbers than the FCIP tape acceleration, which is
limited by a single Gigabit Ethernet throughput.

Load Balancing

IOA uses clustering technology to provide automatic load balancing and redundancy for traffic flows
across multiple IOA service engines that can be configured for the IOA service. When an IOA service
engine fails, the affected traffic flows are automatically redirected to the available IOA service engines
to resume acceleration.

1-2

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

1 Overview

Application

Servers

Tape

Library

276371

MAN/WAN

ISLs

Site: SJC

Site: RTP

Physical Fabric

Storage

Array

Storage

Array

I

1

I

2

T

1

MSM

MSM

Example IOA Topology

Send documentation comments to [e-mail]

Example IOA Topology

Figure 1-1 illustrates a physical fabric that consists of two sites in different locations interconnected

across the MAN or WAN using Fibre Channel or FCIP links. Remote replication and remote tape backup
services run across these two data centers.

Figure 1-1 Fabric with Two Sites

Note This topology illustrates a single fabric onl y. In a dual fabric, the second fabric is an exact replica of this

topology , and the concepts that are described in this document are applicab le to the second fabric as w ell.

Terminology

The following Cisco IOA-related terms are used in this book:

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

• Fabric—A physical topology of switches interconnected by Fibre Channel or FCIP ISLs.

• IOA Site—Represents a set of switches within the physical fabric that is in a specific physical

location. Multiple IOA sites within the physical fabric are typically interconnected over a MAN or
WAN using Fibre Channel or FCIP links. IOA provides the acceleration service for flows tra v ersing
across sites. As a part of the IOA configur ation, the switches must b e classified into appropriate IO A

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

1-3

1 Overview

Terminology

Send documentation comments to [e-mail]

sites. Acceleration is provided for flows t ra v er si ng the MAN or WAN across sites. The main reason
to classify the sites is to select the intersite flows for acceleration. No intrasite flows will be allowed
to participate in acceleration.

Note When using the CLI, only the switches where IOA is deployed need to be classified into a

site. When using the Fabric Manager, all the switches in a physical location need to be
classified into a site. The site classification is used internally by the Fabric Manager to
automate the classification of the flows that traverse across sites.

• IOA Interface—Represents a single service engine in the MSM-18/4 Module or the SSN-16

Module. An IOA interface must be provisioined to enable IOA service on the service engine. The
MSM-18/4 Module has one service engine and the SSN-16 Mo dule has four ser vice engines, whi ch
directly represents the number of IOA interfaces that can be created on these modules. In the CLI,
an IOA interface is represented as interface ioa x/y where x represents the slot and y represents the
service engine ID. With the SSN-16, the servi ce engine ID can be 1 to 4. Each IOA interface requires
a IOA license to be checked out.

An IOA interface must be brought up administratively to enable the IOA service on the service
engine.

• IOA Switch—Represents a switch that has one or more IOA Interfaces configured for the IOA

service. The terms IOA switch and IOA node are used interchangeably in this configuration guide.

• IOA Cluster—A set of IOA switches that can operate in a coordinated manner to provide the IOA

service. An IOA cluster can only span two IOA sites. If there is a consolidation site that has
connectivity to various other sites, each site pair must be represented by a unique IOA cluster. A
switch may participate in multiple IOA clusters due to this reason, but each IOA interface is bound
only to one IOA cluster. This architecture allows for cluster scalability and limiting the scope of
configuration distribution as appropriate.

• IOA N Port—Represents a Fibre Channel N port represented by a port world-wide name. IOA

requires that the site to which the N port belongs and the VSAN ID be configured. The site
classification is required to identify how to redirect the traffic flow for acceleration.

• FC-Redirect —Fibre Channel Redirect (FC-Redirect) infrastructure provi des the ability to redirect

a flow to a specific servi ce engine in the f abric to provide certain intelligent services such as Storage
Media Encryption and Data Mobility Manager. This infrastructure has been extended for IOA to
redirect the flow to two service engines in the fabric that can then work together to provide the
acceleration intelligence.

Both the host and the target or tape must be directly attached to a FC-Redirect-capable switch.

• IOA Flow—A flo w that is accelerated across the MAN or WAN by the IOA cluster. Each IOA flow

is identified by initiator PWWN and target PWWN.
IOA provide bidirectional acceleration for each configured flow. A separate reverse flow

configuration is not required.

• IOA Flow Group—A set of IOA flows classified for a specific purpose. For example, if the same

IOA cluster is being used for remote replication and backup, you can have all the replication flows
classified into the replication flow group and all the backup flows classified into the backup flow
group.

1-4

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

1 Overview

Clustering

Send documentation comments to [e-mail]

Note You can have more than one IOA service engine in the same site in the IOA cluster. In fact, this is the

preferred configuration wherein if an IOA service engine fails , then all the flows bound to it can be
automatically moved to another available IOA service engine in the same site. This is taken care of by
the IOA cluster based load balancer.

Clustering

IOA is offered as a clustered service that consists of a set of switches that operates in coordination with
each other. Clustering provides the following advantages:

• Single point management— IOA can be managed as a fabri c service from a single switch. You need

not configure multiple switches individually to provide IOA as a fabric service.

• Automatic load-balancing— You can provision all of the flows that need to be accelerated through

IOA. Clustering allows these flows to load-balance automatically across all the available IOA
service engines within the cluster. It also makes it easy to plan for capacity as you just need to add
an additional IOA service engine when there is a need to add more throughput within IOA.

• Resiliency— Allows automatic failover of the IOA flows whenever an IOA service engine fails on

any of the switches. If a switch fails, an alternate switch in the cluster takes over the failed flows to
maintain the contiuity of the IOA service.

IOA clustering uses standard algorithms to provide consistency and reliability of the configuration
metadata required for the service to be operational. A master switch is internally elect ed by the clustering
infrastructure to perform certain tasks such as load-balancing and failover. To keep the process simple,
we recommend that you provision the IOA from the master switch. If the network fails, which partitions
the switches in a cluster, a standard majority node-based quorum algorithm is used to decide which
partition should be operational to be able to guarantee the consistency.

An internal node ID that is allocated as a part of adding the switches to the cluster is used in the master
election algorithm. If you intend to manage IOA from a specific switch or a site, we recommend that you
use this switch as a seed switch when a IOA cluster is configured, and also add all the nodes in this site
before you add the nodes from the remote site into the IOA cluster.

Hardware Requirements

IOA is supported on the Cisco MDS 9000 F amily 18/4-port Multi service (MSM-18/4) Module, the Cisco
MDS 9222i Switch, and the 16-Port Storage Serv ices Node (SSN-16) mo dule. Each MSM- 18/4 Module
and 9222i Switch has one service engine that can be configured for the Cisco IOA service. The SSN-16
module has four service engines that can be used for the IOA service.

Software Requirements

T o enable IO A feature on the MSM-18/4 Module or SSN-16 Module, the MDS 9000 F amily switch must
run Cisco NX-OS Release 4.2(1) or later. You must also use Fabric Manager 4.2(1) to manage the
switches. Hosts must be connected to a switch running Cisco SAN-OS 3.3(1c) or later. Targets must be
connected to a switch running Cisco NX-OS Release 4.2(1) or later.

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

1-5

1 Overview

License Requirements

Send documentation comments to [e-mail]

License Requirements

The Cisco MDS 9000 Family IOA package is licensed per service engine and is tied to the chassis. The
number of licenses required is equal to the number of service engines on which the intelligent fabric
application is used.

IOA runs on the MDS 9222i Switch (native) and on the MSM-18/4 Module and SSN-16 Module. The
modules are supported in the MDS 9500 Directors and the MDS 9222i Switch.

On the SSN-16 Module, a separate license is required for each engine that will run IOA. Each SSN- 1 6
engine configured for IOA checks out a license from the pool managed at the chassis level. For
convenience, SSN-16 Module licenses can be purchased singly (the usual model) or in a package of four .
Once they are installed into an MDS 9000 chassi s, there is no difference between the IOA package of
four and four single IOA licenses.

On the SSN-16 Module, because each engine is licensed independently, different licensed features can
be configured on the four engines based on the following requirements for NX-OS Release 4.2(1):

• As with the MDS 9222i Switch and the MSM-18/4 Module, only one licensed feature can run on an

engine at a time.

• On the SSN-16 Module, mix and match is supported for IOA and SAN Extension over IP in any

combination (4+0, 1+3, 2+2, 3+1, or 0+4) .

• Storage Media Encryption (SME) is not supported for mix and match in NX-OS Release 4.2(1).

To use the IOA features, Cisco MDS NX-OS Release 4.2(1) or later must be installed on a Cisco MDS
9000 Family switch.

Table 1-1 lists the available Cisco IOA licenses.

Table 1-1 Cisco I/O Accelerator Licenses

Part Number Description Applicable Product

M92IOA184 Cisco I/O Acceleration License

for MSM-18/4 on MDS 9200,
spare.

M95IOA184 Cisco I/O Acceleration License

for MSM-18/4 on MDS 9500,
spare.

M95IOASSN Cisco IOA License (1 engine) for

SSN-16 on MDS 9500, spare.

M92IOASSN Cisco IOA License (1 engine) for

SSN-16 on MDS 9200, spare.

M95IOASSN4X Cisco IOA License (4 engines)

for SSN-16 on MDS 9500, spare.

M92IOASSN4X Cisco IOA License (4 engines)

for SSN-16 on MDS 9200, spare.

MSM-18/4 on MDS 9200

MSM-18/4 on MDS 9500

SSN-16 on MDS 9500

SSN-16 on MDS 9200

SSN-16 on MDS 9500

SSN-16 on MDS 9200

1-6

M9222IIOA Cisco I/O Accelerator License

for MDS 9222i, spare.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

MDS 9222i Switch

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

1 Overview

License Requirements

Send documentation comments to [e-mail]

Note A device is either a switch or a module. When you enter the serial number for the device, make sure that

you enter the serial number for the correct device; either the switch or the module for which you want
to get the license. You can use the show license host-id command to find out which ser ial number to lock
the license against.

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

1-7

1 Overview

License Requirements

Send documentation comments to [e-mail]

1-8

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Send documentation comments to [e-mail]

CHAPTER

2

Getting Started

This chapter provides an overview of the basic configurations that need to be completed before getting
started with IOA-specific configurations:

• Enabling SSH, page 2-1

• Enabling CFS, page 2-1

• IP Access Lists, page 2-2

• Zone Default Policy, page 2-2

• FC-Redirect, page 2-2

• Configuring FC-Redirect v2 Mode, page 2-3

• Using FC-Redirect with CFS Regions, page 2-4

• Using IOA Cluster with IPFC Interface, page 2-5

Enabling SSH

SSH needs to be enabled on all the IOA switches for Fabric Manager to provision IOA. By default, the
SSH service is enabled with the RSA key.

To enable the SSH service, follow these steps:

Command Purpose

Step 1
Step 2

switch# config t

switch(config)# feature ssh
updated

For more information about the SSH service, refer to the Cisco MDS 9000 Family NX-OS Security
Configuration Guide.

Enabling CFS

CFS must be enabled on the IOA switches as well as those switches of which the hosts and targets are
directly connected to. FC-Redirect internally uses CFS to configure the rules for any given flow in the
fabric.

Enters configuration mode.
Enables the use of the SSH service.

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-1

Chapter 2 Getting Started

IP Access Lists

Send documentation comments to [e-mail]

To globally enable CFS distribution on a switch, follow these steps:

Command Purpose

Step 1

Step 2

switch# config t
switch(config)#

switch(config)# cfs distribute

For more information about CFS, refer to the Cisco MDS 9000 Family NX-OS System Management
Configuration Guide.

Enters configuration mode.

Enables (default) CFS distribution on the switch.

IP Access Lists

Cluster communication requires the use of the Management interface. I P A CL configuratio ns must allow
UDP and TCP traffic on ports 9333, 9334, 9335, and 9336.

Zone Default Policy

For FC-Redirect to work correctly, the default zone policy on all the switches in the IOA environment
must be configured to deny and the initiator-target pairs must be configured in user-defined zones.

FC-Redirect

This section includes the following topics:

• FC-Redirect Unsupported Switches, page 2-2

• FC-Redirect Requirements, page 2-2

FC-Redirect Unsupported Switches

FC-Redirect is not supported on the following switches, which also means that IOA is not supported:

• Cisco MDS 9148 Switch

• Cisco MDS 9140 Switch

• Cisco MDS 9134 Switch

• Cisco MDS 9124 Switch

• Cisco MDS 9120 Switch

• Cisco MDS 9020 Switch

FC-Redirect Requirements

FC-Redirect requirements for IOA include the following:

• The MDS switch with the MSM-18/4 Module installed or the 9222i Switch needs to be running

Cisco MDS NX-OS Release 4.2(1) or later.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-2

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Chapter 2 Getting Started

Configuring FC-Redirect v2 Mode

Send documentation comments to [e-mail]

• The targets must be connected to a FC-Redirect-capable switch running Cisco MDS NX-OS Release

4.2(1) or later. The hosts must be connected to a FC-Redirect-capable switch running Cisco MDS
SAN-OS Release 3.3(1c) or later.

• 32 targets per MSM-18/4 Module can be FC-Redirected.

• In FC-Redirect v2 mode, up to 128 hosts per target are supported. If you do not enable FC-Redirect

v2, this is limited to 16 hosts per target.

• CFS is enabled by default. Ensure that the CFS is enabled on the switches that have the host and the

target connected. Also ensure that the CFS is not disabled on switches that are part of the IOA
cluster.

• Advanced zoning capabilities lik e quali ty of serv ice (QoS), l ogi cal un it numb er (LUN ) zoning , and

read-only LUNs must not be used for FC-Redirect hosts and targets.

Configuring FC-Redirect v2 Mode

To enable the v2 mode in FC-Redirect, use t he fc-redirect version2 enable command in configuration
mode. To disable the v2 mode in FC-Redirect, use the no form of the command.

This command is used to increase scalability of FC-Redirect. Disabling v2 mode after it is enabled in
the fabric is not recommended. However, if you want to disable v2 mode, you cannot disable it until all
FC-Redirect configurations are deleted. FC-Redirect configurations can be deleted only by deleting all
corresponding application configurations.

The MDS switches not running Cisco NX-OS 3.3(1c) and later cannot be added t o the fabri c after the v2
mode is enabled. If the switches are added, all further FC-Redirect configuration changes will fail across
the fabric. This could lead to traffic disruption for applications such as IOA, SME, and DMM.

Use the show fc-redirect configs command to se e the list of applications that create FC-Redirect
configurations.

If v2 mode is enabled in the fabric and you want to move a switch to a different fabric, use the clear
fc-redirect decommission-switch command before mo vi ng the switch to a different fabric. If the mode
is not enabled, all switches in the new fabric will be converted to v2 mode automatically.

Note Ensure that there are no fabric changes or upgrades in progress. For more information see “Software

Requirements” section on page 1-5. Use the show fc-r edirect peer-switches command (UP state) to see

all the switches in the fabric.

To enable v2 mode in FC-Redirect, follow these steps:

Step 1 Enter the following command:

switch# fc-redirect version2 enable

Step 2 Enter yes.

Please make sure to read and understand the following implications
before proceeding further:

1) This is a Fabric wide configuration. All the switches in the
fabric will be configured in Version2 mode.Any new switches
added to the fabric will automatically be configured in version2
mode.

2) SanOS 3.2.x switches CANNOT be added to the Fabric after Version2
mode is enabled. If any 3.2.x switch is added when Version2 mode

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-3

Chapter 2 Getting Started

Using FC-Redirect with CFS Regions

Send documentation comments to [e-mail]

is enabled, all further FC-Redirect Configuration changes will Fail
across the fabric. This could lead to traffic disruption for
applications like SME.

3) If enabled, Version2 mode CANNOT be disabled till all FC-Redirect
configurations are deleted. FC-Redirect configurations can be
deleted ONLY after all the relevant application configurations
are deleted. Please use the command 'show fc-redirect configs'
to see the list of applications that created FC-Redirect
configurations.

4) 'write erase' will NOT disable this command. After 'write erase'
on ANY switch in the fabric, the user needs to do:
'clear fc-redirect decommission-switch'
on that that switch. Without that, if the user moves the switch
to a different fabric it will try to convert all the switches
in the fabric to Version2 mode automatically. This might lead
to Error conditions and hence Traffic disruption.
Do you want to continue? (Yes/No) [No]Yes

Step 3 Enter yes.

Before proceeding further, please check the following:

1) All the switches in the fabric are seen in the output of
'show fc-redirect peer-switches' command and are in 'UP' state.

2) All switches in the fabric are running SanOS version 3.3.x or
higher.

3) Please make sure the Fabric is stable ie.,
No fabric changes/upgrades in progress
Do you want to continue? (Yes/No) [No] Yes

Using FC-Redirect with CFS Regions

The FC-Redirect feature uses Cisco Fabric Services (CFS) regions to distribute the FC-Redirect
configuration. By default, the configuration is propagated to all FC-Redirect-capable switches in the
fabric. CFS regions can be used to restrict the distribution of the FC-Redirect configuration.

Note Using FC Redirect with CFS regions is an optional configuration only if the number of switches in the

SAN exceeds the scalability limit supported by IOA. As of MDS NX-OS Release 4.2(1), the number of
switches supported in a fabric is 34.

To learn more about CFS regions, refer to the Cisco MDS 9000 Family NX-OS System Management
Configuration Guide.

Guidelines for Designing CFS Regions For FC-Redirect

To design CFS regions for FC-Redirect, follow these guidelines:

• Ensure that the CFS region configuration for FC-Redirect can be applied to all FC-Redirect-based

applications. The applications include Cisco SME, Cisco DMM, Cisco IOA, and any future
applications.

• Ensure that all FC-Redirect-capable switches, that are connected to the hos ts, targets, and the

application switches (switches with MSM-18/4 modules in a cluster), are configured in the same
region.

2-4

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to [e-mail]

• All switches in the region must have a common VSAN.

• For existing IOA installations, refer to “Configuring CFS Regions For FC-Redirect” section on

page 2-5 for steps on migrating to CFS regions.

• Remove all instances of the previous configurations when a switch is moved to a region or moved

out of a region.

Configuring CFS Regions For FC-Redirect

To configure the CFS regions for FC-Redirect, do the following tasks:

Step 1 Configure a switch in the CFS region as shown in the following example:

switch# config t
switch# cfs region 2
switch# fc-redirect
switch# end

Repeat this step for all the switches that are included in the specified region.

Step 2 Confirm that all the required switches are available in the CFS region by entering the show fc-redirect

peer-switches command.

Step 3 To migrate existing Cisco IOA installations to CFS regions for FC-Redirect, delete all the existing

FC-Redirect configurations created by the switches in other regions from each switch. To remove the
configurations, perform the following steps:

a. Obtain a list of all FC-Redirect configurations by entering the show fc-redirect configs command.
b. Remove all configurations created by the switches in other regions by using the clear fc-redirect

configs command. The conf igurations are r emoved fr om the switches b ut the switches remain act iv e
in the region in which they are created.

Using IOA Cluster with IPFC Interface

Internet protocol over Fibre Channel (IPFC) pr ovides IP forw arding or in-band switch management over
a Fibre Channel interface (instead of management using the Gig abit Ethernet mgmt 0 interface). You can
use IPFC to specify that IP frames be transported over Fibre Channel using encapsulation techniques. IP
frames are encapsulated into Fibre Channel frames so that cluster management information can transmit
across the Fibre Channel network without using an overlay Ethernet network.

When you use IOA cluster with the IPFC interface, the IOA cluster can use cluster management-related
messages through Fibre Channel ISLs by encapsula ting cluster management related messages in to Fibre
Channel frames instead of using the management interface.

Note Configuring IOA cluster with the IPFC interface is optional and is supported in Cisco MDS NX-OS

Release 5.0(4c) or later. Support for GUI for configuring IOA cluster with the IPFC interface might be
added in the future releases.

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-5

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to [e-mail]

Note You must configure the nodes in an IOA cluster either to use an IPFC interface or a management

interface. We do not recommend using the combination of two interface configurations.

Task Flow for Configuring IOA Cluster To Use the IPFC Interface

To configure IOA cluster using the IPFC Interface, follow these steps:

Step 1 Create an IPFC interface.

a. Create a VSAN to use for in-band management.
b. Configure an IPv4 address and subnet mask for the VSAN interface.
c. Enable IPv4 routing.

d. Verify connectivity.
Step 2 Create an IOA cluster.
Step 3 Change the local node to use IPFC interface’s IPv4 address.
Step 4 Add the IOA interfaces to the cluster.
Step 5 Add the remote node with IPFC interface IPv4 address.
Step 6 Add the IOA interface of the remote cluster.

Configuring IOA Cluster To Use the IPFC Interface

The process of configuring an IOA cluster to use the IPFC interf ace involves a number of configuration
tasks that should be completed in the following order:

• Creating a VSAN Interface and Configuring IPv4 Addresses, page 2-6

• Enabling IPv4 Routing, page 2-7

• Verifying Connectivity, page 2-7

• Creating IOA cluster and IOA interface in the Local Node, page 2-8

• Verifying Cluster Configuration, page 2-8

• Adding a Remote Node and IOA Interface to the Remote Node, page 2-8

• Verifying the Cluster Configuration, page 2-9

Creating a VSAN Interface and Configuring IPv4 Addresses

The first step in the process of configuring IOA cluster to use the IPFC interface is to create a VSAN
interface and configure IPv4 addresses.

To create an interface VSAN, perform this task:

2-6

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

OL-20708-01, Cisco MDS NX-OS Release 5.0(1a)