Cisco MDS 9000 series Configuration Manual

Download

Send documentation comments to mdsfeedback-doc@cisco.com

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: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Text Part Number: OL-20708-01

Send documentation comments to mdsfeedback-doc@cisco.com

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

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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

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 mdsfeedback-doc@cisco.com

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

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

Contents

Send documentation comments to mdsfeedback-doc@cisco.com

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

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 mdsfeedback-doc@cisco.com

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

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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

New and Changed Information

Send documentation comments to mdsfeedback-doc@cisco.com

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Send documentation comments to mdsfeedback-doc@cisco.com

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

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

Preface

Send documentation comments to mdsfeedback-doc@cisco.com

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.

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

Preface

Send documentation comments to mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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

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 mdsfeedback-doc@cisco.com

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

MSM

Example IOA Topology

Send documentation comments to mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

CHAPTER

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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

• 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 mdsfeedback-doc@cisco.com

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 mdsfeedback-doc@cisco.com

• 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 mdsfeedback-doc@cisco.com

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)

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

Command Purpose

Step 1 Step 2 Step 3

Step 4

Switch# config t

Switch(config)# interface vsan 1

Switch (config-if)# ip address

10.1.1.1 255.255.255.0

Switch (config-if)# no shutdown

Enters configuration mode Configures the interface for the specified VSAN (1). Configures the IPV4 address and netmask for the selected

interface. Enables the interface.

After creating the VSAN and configuring the IPv4 address, use the show interface vsan command to verify the configuration:

sw-231-14# show interface vsan 1 vsan1 is up, line protocol is up WWPN is 10:00:00:0d:ec:18:a1:05, FCID is 0xec03c0 Internet address is 10.1.1.1/24 MTU 1500 bytes, BW 1000000 Kbit 0 packets input, 0 bytes, 0 errors, 0 multicast 6 packets output, 384 bytes, 0 errors, 0 dropped

sw-231-14#

Enabling IPv4 Routing

To enable IPv4 routing, perform this task:

Command Purpose

Step 1 Step 2 Step 3

Switch# config t

Switch(config)# ip routing

Switch(config) no ip routing

After enabling IPv4 routing, use the show ip routing to verify the configuration.

sw-231-14(config)# show ip routing ip routing is enabled

Verifying Connectivity

To verify the connectivity, use the show ip route and ping commands.

sw-231-14# show ip route Codes: C - connected, S - static C 10.1.1.0/24 is directly connected, vsan1

Enters configuration mode. Enables IPV4 routing. Disables IPV4 routing.

sw-231-14# ping 10.1.1.2 PING 10.1.1.2 (10.1.1.2) 56(84) bytes of data. 64 bytes from 10.1.1.2: icmp_seq=1 ttl=64 time=0.875 ms 64 bytes from 10.1.1.2: icmp_seq=2 ttl=64 time=0.866 ms 64 bytes from 10.1.1.2: icmp_seq=3 ttl=64 time=0.884 ms 64 bytes from 10.1.1.2: icmp_seq=4 ttl=64 time=0.875 ms

--- 10.1.1.2 ping statistics --4 packets transmitted, 4 received, 0% packet loss, time 3023ms rtt min/avg/max/mdev = 0.866/0.875/0.884/0.006 ms

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-7

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

Creating IOA cluster and IOA interface in the Local Node

To create an IOA cluster and IOA interface in the local node, perform this task:

Command Purpose

Step 1 Step 2

Step 3

Step 4

Switch# config t

Switch(config)# ioa cluster cluster

name

Switch(config-ioa-cl)# node switch-

name/ip addres ip-adderss 10.1.1.1

Switch(config-ioa-cl-node)# int ioa

1/1

Enters configuration mode Creates IOA cluster with specific name.

Adds or Changes the node address from the mgmt0 address to the IPFC interface address.

Adds IOA interfaces to the cluster.

To configure an IOA cluster, you can use the name of the switch if the network supports DNS service. The IOA cluster requires switch name to IP address resolution.

Verifying Cluster Configuration

To verify the cluster configuration, use the show ioa cluster name node summary command.

sw-231-14# sh ioa cluster cltr1 node sum

------------------------------------------------------------------------------Switch Site Status Master Node ID

------------------------------------------------------------------------------sw-231-14(L) site2 online yes 1

To verify the IP address of the node, use the show ioa cluster <name> node command.

sw-231-14# show ioa cluster cltr1 node Node sw-231-14 is local switch Node ID is 1 IP address is 10.1.1.1 Status is online Belongs to Site site2 Node is the master switch

Adding a Remote Node and IOA Interface to the Remote Node

To add a remote node, pe rform th is task:

Command Purpose

Step 1 Step 2

Step 3

Step 4

Switch# config t

Swtich(config)# ioa cluster cluster

name

Switch(config-ioa-cl)# node

<switchname/ip address> ip-address

10.1.1.2

Switch(config-ioa-cl-node)# int ioa

4/1

Enters configuration mode. Enter IOA cluster.

Adds remote node to the cluster with the IPFC interface address.

Adds IOA interfaces to the cluster.

2-8

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 2 Getting Started

Interface vsan 1 : 10.1.1.2

IOA stie : site1

Interface vsan 1 : 10.1.1.1

IOA stie : site2

FCISL

Sw-231-19 Sw-231-14

310152

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

Verifying the Cluster Configuration

To verify the node configuration, use the show ioa cluster name node summary command:

sw-231-14# show ioa cluster cltr1 node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

------------------------------------------------------------------------------sw-231-14(L) site2 online yes 1 sw-231-19 site1 online no 2

To verify the ip address of the node, use the show ioa cluster name node command:

Node sw-231-14 is local switch Node ID is 1 IP address is 10.1.1.1 Status is online Belongs to Site site2 Node is the master switch Node sw-231-19 is remote switch Node ID is 2 IP address is 10.1.1.2 Status is online Belongs to Site site1 Node is not master switch sw-231-14#

To see all of the configured interfaces in the IOA cluster, us e the show ioa cluster name interface summary command:

sw-231-14# show ioa cluster cltr1 interface summary

------------------------------------------------------------------------------Switch Interface Status Flows

------------------------------------------------------------------------------sw-231-14(L) ioa1/1 up 0 sw-231-14(L) ioa1/2 up 0 sw-231-19 ioa4/1 up 0 sw-231-19 ioa4/2 up 0 sw-231-14#

Configuration Example

This section includes an example for creating an IOA cluster using IPFC interface. Figure 2-1 illustrates the IOA cluster configuration used in this example. The sample topology shows the FC ISL between sw-231-14 and sw-231-19 switches.

Figure 2-1 Configuration Example

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-9

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

• Creating an Interface VSAN, page 2-10

• Verifying the Configuration, page 2-10

• Verifying the Connectivity, page 2-11

• Configuring IOA Site on Switch sw-231-14, page 2-11

• Configuring IOA Site on Switch sw-231-19, page 2-11

• Changing the Node to Use IPFC Interface Address, page 2-11

• Adding a Remote Node to the IOA Cluster, page 2-11

• Adding an IOA Interface to the Switch sw-231-14, page 2-12

• Adding an IOA Interface to the Switch sw-231-19, page 2-12

• Verifying the Cluster Configuration, page 2-12

• Verifying the IP Address, page 2-12

• Verifying the IOA Interface, page 2-13

Creating an Interface VSAN

The following example creates an interface VSAN and configure IP address on sw-231-14 and enable IP routing:

sw-231-14(config)# int vsan 1 sw-231-14(config-if)# ip address 10.1.1.1 255.255.255.0 sw-231-14(config-if)# no show sw-231-14(config)# ip routing sw-231-14(config)#

The following example create an interface VSAN and configure IP address on sw-231-19 and enable IP routing.

sw-231-19(config)# int vsan 1 sw-231-19(config-if)# ip address 10.1.1.12 255.255.255.0 sw-231-19(config-if)# no show sw-231-19(config)# ip routing

Verifying the Configuration

The following example verifies the configuration of sw-231-14 using show interface command.

sw-231-14# show interface vsan 1 vsan1 is up, line protocol is up WWPN is 10:00:00:0d:ec:18:a1:05, FCID is 0xec03c0 Internet address is 10.1.1.1/24 MTU 1500 bytes, BW 1000000 Kbit 758 packets input, 110841 bytes, 0 errors, 42 multicast 651 packets output, 122577 bytes, 0 errors, 0 dropped sw-231-14#

2-10

The following example verifies the configuration of sw-231-19 using show interface command:

sw-231-19# show interface vsan 1 vsan1 is up, line protocol is up WWPN is 10:00:00:05:30:01:9f:09, FCID is 0xc60000 Internet address is 10.1.1.2/24

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 mdsfeedback-doc@cisco.com

MTU 1500 bytes, BW 1000000 Kbit 675 packets input, 124613 bytes, 0 errors, 36 multicast 755 packets output, 111785 bytes, 0 errors, 0 dropped sw-231-19#

Verifying the Connectivity

The following example verifies the connectivity using ping command:

sw-231-14# ping 10.1.1.2 PING 10.1.1.2 (10.1.1.2) 56(84) bytes of data. 64 bytes from 10.1.1.2: icmp_seq=1 ttl=64 time=0.868 ms 64 bytes from 10.1.1.2: icmp_seq=2 ttl=64 time=0.898 ms 64 bytes from 10.1.1.2: icmp_seq=3 ttl=64 time=0.906 ms

--- 10.1.1.2 ping statistics --3 packets transmitted, 3 received, 0% packet loss, time 2017ms rtt min/avg/max/mdev = 0.868/0.890/0.906/0.038 ms sw-231-14#

Configuring IOA Site on Switch sw-231-14

The following example configures IOA site on switch sw-231-14:

sw-231-14(config)# ioa site-local site2 sw-231-14(config)#

Configuring IOA Site on Switch sw-231-19

The following example configures IOA site on switch sw-231-19:

sw-231-19(config)# ioa site-local site1 sw-231-19(config)#

Configuring IOA Cluster cltr1 on Switch sw-231-14

The following example configures IOA cluster ctrl1 on switch sw-231-14:

sw-231-14(config)# ioa cluster cltr1 2011 Apr 8 05:00:46 sw-231-14 %CLUSTER-2-CLUSTER_LEADER_ANNOUNCE: Node 0x1 is the new Master of cluster 0x2e05000dec18a133 of 1 nodes 2011 Apr 8 05:00:46 sw-231-14 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x2e05000dec18a133 now has quorum with 1 nodes

Changing the Node to Use IPFC Interface Address

The following example force the node to use IPFC interface addresss:

sw-231-14(config-ioa-cl)# node sw-231-14 ip-address 10.1.1.1 sw-231-14(config-ioa-cl-node)# ex

Adding a Remote Node to the IOA Cluster

The following example adds a remote node to IOA cluster:

sw-231-14(config-ioa-cl)# node sw-231-19 ip-address 10.1.1.2

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-11

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

2011 Apr 8 05:02:47 sw-231-14 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x2e05000dec18a133 now has quorum with 1 nodes 2011 Apr 8 05:02:52 sw-231-14 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x2e05000dec18a133 now has quorum with 2 nodes sw-231-14(config-ioa-cl-node)# ex

Adding an IOA Interface to the Switch sw-231-14

The following example adds an IOA interface on the switch sw-231-14:

sw-231-14(config-ioa-cl)# node sw-231-14 sw-231-14(config-ioa-cl-node)# int ioa 1/1 sw-231-14(config-ioa-cl-node)# int ioa 1/2 sw-231-14(config-ioa-cl-node)# ex

Adding an IOA Interface to the Switch sw-231-19

The following example adds an IOA interface on the switch sw-231-19:

sw-231-14(config-ioa-cl)# node sw-231-19 sw-231-14(config-ioa-cl-node)# int ioa 4/1 sw-231-14(config-ioa-cl-node)# int ioa 4/2 sw-231-14(config-ioa-cl-node)# ex

Verifying the Cluster Configuration

The following example verifies the cluster configuration using show cluster name node summary command:

sw-231-14# show ioa cluster cltr1 node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

------------------------------------------------------------------------------sw-231-14(L) site2 online yes 1 sw-231-19 site1 online no 2

Verifying the IP Address

The following example verifies the IP Address that is configured on the switch using show ioa cluster cluster name node command:

sw-231-14# show ioa cluster cltr1 node Node sw-231-14 is local switch Node ID is 1 IP address is 10.1.1.1 Status is online Belongs to Site site2 Node is the master switch Node sw-231-19 is remote switch Node ID is 2 IP address is 10.1.1.2 Status is online Belongs to Site site1 Node is not master switch

2-12

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 mdsfeedback-doc@cisco.com

Verifying the IOA Interface

The following example verifies the IO A interface that is co nfigured on the switch using show ioa cluster cluster name interface summary command:

sw-231-14# show ioa cluster cltr1 int summary

------------------------------------------------------------------------------Switch Interface Status Flows

------------------------------------------------------------------------------sw-231-14(L) ioa1/1 up 0 sw-231-14(L) ioa1/2 up 0 sw-231-19 ioa4/1 up 0 sw-231-19 ioa4/2 up 0 sw-231-14#

Task Flow for Converting an Existing IOA Cluster to use IPFC interface

To convert an existing IOA cluster to use the IPFC Interface, follow these steps:

• Shut down IOA cluster on both the nodes.

• Remove the IOA cluster that is configured on remote node.

• Remove the remote node from the cluster and convert it as a single node cluster.

• Change the node to use IPFC by entering the commands node id id nodename and ip-address IPFC

address.

• Bring the single node cluster by no-shut.

• Add the remote node and its interface.

• Verify using show commands.

Configuration Example for Converting IOA Cluster to Use the IPFC interface

This example for converting an IOA c luster to use the IPFC interface has the following steps:

• Verifying the IOA Cluster Configuration, page 2-14

• Verifying the IP Address, page 2-14

• Verifying the Flow Status, page 2-14

• Shutting Down IOA Cluster on a Local Node, page 2-14

• Shutting Down the IOA cluster on the remote node, page 2-15

• Removing the IOA Cluster from the Remote Node, page 2-15

• Verifying the IOA Cluster in the Remote Node, page 2-15

• Removing the Remote Node from the Cluster in the Local Switch, page 2-15

• Changing the Local Node Configuration to use IPFC Address, page 2-15

• Activating the Single Node Cluster, page 2-15

• Adding Remote Node with IPFC Address, page 2-16

• Adding IOA Interfaces to the Remote Node, page 2-16

• Verifying the Cluster Nodes, page 2-16

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-13

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

• Verifying the Flow Status, page 2-16

Verifying the IOA Cluster Configuration

The following example v erifies the IO A cluster config uration that is configur ed on the switch using show ioa cluster cluster name node summary command:

sw-231-14(config)# show ioa cluster cltnew node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

------------------------------------------------------------------------------sw-231-14(L) site2 online yes 1 sw-231-19 site1 online no 2

Verifying the IP Address

The following example verif ies the IP address that is configured on th e switch using the show ioa cluster cluster name node command:

sw-231-14(config)# show ioa cluster cltnew node Node sw-231-14 is local switch Node ID is 1 IP address is 172.25.231.14 Status is online Belongs to Site site2 Node is the master switch Node sw-231-19 is remote switch Node ID is 2 IP address is 172.25.231.19 Status is online Belongs to Site site1 Node is not master switch

Verifying the Flow Status

The following example verifies the status of the flows using the show ioa cluster cluster name flows command. The nodes in this example are using mgmt0 interface address

sw-231-14(config)# show ioa cluster cltnew flows

------------------------------------------------------------------------------Host WWN, VSAN WA TA Comp Status Switch,Interface Target WWN Pair

-------------------------------------------------------------------------------

21:01:00:1b:32:22:55:df, 1 Y Y N online sw-231-14, ioa1/1 21:01:00:0d:77:dd:f8:9d, 1 sw-231-19, ioa4/1

Shutting Down IOA Cluster on a Local Node

The following example shuts down the IOA cluster on a local node using shut down command.

sw-231-14(config)# ioa cluster cltnew sw-231-14(config-ioa-cl)# show

This change can be disruptive. Please ensure you have read the "IOA Cluster Recovery Procedure" in the configuration guide. -- Are you sure you want to continue? (y/n) [n] y

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-14

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 mdsfeedback-doc@cisco.com

2011 Apr 8 05:36:41 sw-231-14 %CLUSTER-2-CLUSTER_LOCAL_NODE_EXIT: Local Node 0x1 has left the Cluster 0x2e06000dec18a133

Shutting Down the IOA cluster on the remote node

The following example shuts down the IOA cluster on the remote node using shut down command:

sw-231-19(config)# ioa cluster cltnew sw-231-19(config-ioa-cl)# show This change can be disruptive. Please ensure you have read the "IOA Cluster Recovery Procedure" in the configuration guide. -- Are you sure you want to continue? (y/n) [n] y 2011 Apr 8 05:37:03 sw-231-19 %CLUSTER-2-CLUSTER_LOCAL_NODE_EXIT: Local Node 0x2 has left the Cluster 0x2e06000dec18a133 sw-231-19(config-ioa-cl)# exit

Removing the IOA Cluster from the Remote Node

The following example remove the IOA cluster from the remote node using the no ioa cluster cluster name command:

sw-231-19(config)# no ioa cluster cltnew

Verifying the IOA Cluster in the Remote Node

The following example verify the presence of IOA cluster on the remote node using show ioa cluster cluster name command:

sw-231-19(config)# show ioa cluster sw-231-19(config)#

Removing the Remote Node from the Cluster in the Local Switch

The following example removes the remote node from the cluster in the local switch:

sw-231-14(config-ioa-cl)# no node sw-231-19 sw-231-14(config-ioa-cl)# show ioa cluster cltnew node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

------------------------------------------------------------------------------sw-231-14(L) -- unknown (cluster is offline) 1

Changing the Local Node Configuration to use IPFC Address

The following example change the local node to use IPFC address:

sw-231-14(config-ioa-cl)# node id 1 sw-231-14 ip-address 10.1.1.1 sw-231-14(config-ioa-cl-node)# exit

Activating the Single Node Cluster

The following example activates the single node cluster:

sw-231-14(config-ioa-cl)# no show This change can be disruptive. Please ensure you have read the "IOA Cluster Recovery Procedure" in the configuration guide. -- Are you sure you want to continue? (y/n) [n] y

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

2-15

Chapter 2 Getting Started

Using IOA Cluster with IPFC Interface

Send documentation comments to mdsfeedback-doc@cisco.com

sw-231-14(config-ioa-cl)# 2011 Apr 8 05:39:17 sw-231-14 %CLUSTER-2-CLUSTER_LEADER_ANNOUNCE: Node 0x1 is the new Master of cluster 0x2e06000dec18a133 of 1 nodes 2011 Apr 8 05:39:17 sw-231-14 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x2e06000dec18a133 now has quorum with 1 nodes

Adding Remote Node with IPFC Address

The following example adds a remote node with IPFC address:

sw-231-14(config-ioa-cl)# node sw-231-19 ip-address 10.1.1.2 2011 Apr 8 05:39:36 sw-231-14 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x2e06000dec18a133 now has quorum with 1 nodes 2011 Apr 8 05:39:41 sw-231-14 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x2e06000dec18a133 now has quorum with 2 nodes

Adding IOA Interfaces to the Remote Node

The following example adds the IOA interfaces to the remote node:

sw-231-14(config-ioa-cl-node)# int ioa 4/1 sw-231-14(config-ioa-cl-node)# end sw-231-14#

Verifying the Cluster Nodes

The following example verifies the status of the IOA clusters using show ioa cluster cluster name node summary command:

sw-231-14# show ioa cluster cltnew node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

------------------------------------------------------------------------------sw-231-14(L) site2 online yes 1 sw-231-19 site1 online no 2

Verifying the Flow Status

The following example verif ies the status of the IO A clusters using show ioa cluster cluster name flows command:

sw-231-14# show ioa cluster cltnew flows

------------------------------------------------------------------------------Host WWN, VSAN WA TA Comp Status Switch,Interface Target WWN Pair

-------------------------------------------------------------------------------

21:01:00:1b:32:22:55:df, 1 Y Y N online sw-231-14, ioa1/1 21:01:00:0d:77:dd:f8:9d, 1 sw-231-19, ioa4/1 sw-231-14#

2-16

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Send documentation comments to mdsfeedback-doc@cisco.com

Deployment Considerations

This chapter describes the requirements and guidelines that are necessary to successfully deploy your Cisco I/O Accelerator SAN. Read this chapter before installing or configuring Cisco I/O Accelerator (IOA).

This chapter includes the following sections:

• Supported Topologies, page 3-1

• Deployment Guidelines, page 3-7

• Limitations and Restrictions, page 3-8

• Configuration Limits, page 3-10

Supported Topologies

This section includes the following topics:

• Core-Edge Topology, page 3-1

• Edge-Core-Edge Topology, page 3-2

CHAPTER

• Collapsed Core Topology, page 3-3

• Extended Core-Edge Topology, pa ge 3-4

• Extending Across Multiple Sites, page 3-5

• IVR Topologies, page 3-6

• Other Topologies, page 3-7

Core-Edge Topology

Figure 3-1 illustrates the core-edge topology where you are recommended to place the IOA interfaces

(MSM-18/4 or SSN-16) in the core switches that interconnect the two sites. The ISLs interconnecting the two sites over a MAN or WAN are typically on the core switches as wel, so this becomes a natural place to deploy the IOA service. This deployment provides the following benefits:

• Provides consolidation of IOA service at the core.

• Allows easy scalability of the IOA service engines based on the desired throughput.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

3-1

Chapter 3 Deployment Considerations

Supported Topologies

Send documentation comments to mdsfeedback-doc@cisco.com

• Allows you to plan and transition from FC or FCIP a ccelerati on solutio ns to IOA. This is because

these acceleration solutions will likely be deployed at the core switches already and will allow for a smooth transition to IOA.

• Facilitates planning the capacity based on WAN ISL throughput on the core switches themselves.

• Provides optimal routing as the flows have to traverse these core switches to reach the remote sites.

Figure 3-1 Core-Edge Topology

Site-1 Site-2

Edge-Core-Edge Topology

Figure 3-2 illustrates the edge-core-edge topology where you are recommended to place the MSM-18/4

Module or SSN-16 Module at the core switches that interconnect the two sites.

195419

3-2

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 3 Deployment Considerations

195420

Site-1 Site-2

Supported Topologies

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 3-2 Edge-Core-Edge Topology

Collapsed Core Topology

Figure 3-3 illustrates the collapsed core toplogy where you are recommended to place the MSM-18/4

Module or SSN-16 Module (IOA interfaces) in the core switches that interconnect the two sites.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

3-3

Chapter 3 Deployment Considerations

195418

Site-1 Site-2

Supported Topologies

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 3-3 Collapsed Core Topology

Extended Core-Edge Topology

Figure 3-4 illustrates the extended core-edge topology where you are recommended to place the IOA

interfaces (MSM-18/4 Module or SSN-16 Module) in all the core switches. As the IOA service load balances the traffic by selecting any IOA interface from each site and forms the IOA interface pair for a given flow, certain failures may result in sub-optimal routing. The recommendation is to interconnect the core switches within each site for maximum availability of IOA service. The ISLs between the core switches in the specific site has as much throughput as the WAN ISLs between the sites.

3-4

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 3 Deployment Considerations

Supported Topologies

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 3-4 Extended Core-Edge Topology

Site-1

Extending Across Multiple Sites

Site-2

195422

Figure 3-5 illustrates the IOA implementation where the IOA service is extended across multiple sites.

In this example, Site-4 consolidates the tape backup from Site-1, Site-2, and Site-3. Each IOA cluster represents a site pair, which means that there are three unique clusters. This topology provides segregation and scalability of the IO A service across multiple sites. In Site-4, a sing le switch participates in multiple IOA clusters.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

3-5

Chapter 3 Deployment Considerations

195421

Site-1

Site-4

Site-2

Site-3

Supported Topologies

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 3-5 Extended Across Multiple Sites

IVR Topologies

For IOA to support IVR flows, we recommend that you place the IOA interfaces on the MSM-18/4 or SSN-16 module in the IVR border switches for optimum routing. IOA must always be deployed on the host and target VSANs. Packets from the host get redirected to the IOA interface in the host VSAN, traverses the IVR transi t VSANs for routing, and again gets redirect ed to the IOA interface in the Target VSAN before it reaches the target and vice-versa. IVR transit VSANs are used only for FC routing. IOA is not supported or deployed on transit VSANs.

For more information, refer to the Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide.

3-6

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 3 Deployment Considerations

Deployment Guidelines

Send documentation comments to mdsfeedback-doc@cisco.com

Other Topologies

In certain other topologies, the edge switc hes are connected across the WAN. In such cases, we recommend that you do the following:

• Transition the WAN links from the edge to core switches to provide consolidation and optimal

routing services.

• Deploy the IOA service in the core switches.

Note IOA is supported for IVR flows starting from the Cisco MDS NX-OS Release 5.0(1a).

Deployment Guidelines

This section includes the following topics:

• General Guidelines, p age 3-7

• Scalability and Optimal Performance Considerations, page 3-7

• Resiliency Considerations, page 3-8

General Guidelines

When you deploy IOA, consider these general configuration guidelines:

• The IOA flows bound to the IOA interfaces on the module undergoing an upgrade will be affected.

• Clustering infrastructure uses the management IP network connectivity to communicate with the

other switches. In the case of a switchover, the management IP network connectivity should be restored quickly to preserve the cluster communication. If the management port is connected to a Layer 2 switch, spanning-tree must be disabled on these ports. In a Cisco Catalyst 6000 Series switch, you can implement this by configuring the spanning-tr ee portfast command on these ports which will treat these ports as access or host ports.

Scalability and Optimal Performance Considerations

For maximum scalability and optimal performance, follow these IOA configuration guidelines:

• Zoning considerations: In certain tape backup environments, a common practice is to zone every

backup server with every tape drive available to allow sharing of tape drives across all the backup servers. For small and medium tape backup environments, this may be retained when deploying IOA. For large backup environments, the scalability limit of number of flows in IOA must be considered to check if the zoning configuration can be retained. Best practice for such an environment is to create multiple tape drive pools, each with a set of tape drives and zones of only a set of backup servers to a particular tape drive pool. This allows sharing of tape drives and drastically reduces the scalability requirements on IOA.

• Deploy IOA interfaces (MSM-18/4 or SSN-16) in the core switches in both core-edge and

edge-core-edge topologies. When multiple core switches are interconnected across the MAN or WAN, do the fo llowing:

–

Deploy the IOA interfaces equally among the core switches for high availability.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

3-7

Chapter 3 Deployment Considerations

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

–

Interconnect core switches in each site for optimal routing.

• Plan for Geneneration 2 and above line cards to avoid any FC-Redirect limitations. There is a limit

of only 32 targets per switch if Generation 1 modules are used to link the ISLs connecting the IOA switch and target switches or if the host is directly connected to a Generation 1 module.

• Depending on the WAN transport used, you may have to tune the Fibre Channel extended B2B

credits for the round-trip delay between the sites.

Resiliency Considerations

When you configure IOA, consider the following resiliency guidelines:

• Plan to have a minimum of on e additional IO A service engin e for each site for handling IO A service

engine failures.

• Tuning for E_D_TOV: Fibre Channel Error Detect Timeout Value (E_D_TOV) is used by Fibre

Channel drives to detect errors if any data packet in a sequence takes longer than the specified timeout value. The default timeout value for E_D_TOV is 2 seconds. IOA h a s an built-in reliability protocol (LRTP) to detect and recover from ISL failures by doing the necessary retransmissions. However, you need to ensure that it recovers before the expiry of E_D_TOV. LRTP is not required if the FCP-2 sequence level error - recov ery procedur es are enabled end -to-end (primarily in the tape drivers) because this helps to recover from timeout issues.When the FCP-2 sequence level error-recovery pr ocedure is not enabled, you must tune certain timers in order to protect t he site from ISL failures.

–

Reduce the LRTP retransmit value from the default value of 2.5 seconds to 1.5 seconds. For more information, see the

–

If the ISLs are FCIP links, the FCIP links must be tuned in order to detect link flaps quickly. By default, FCIP links detect a link failure in 6 seconds based on TCP maximum retransmissions. To reduce the time taken to detect failures, you need to set the maximum retransmission attempts in the FCIP profile from the default value of 4 to 1.

Caution Modifying the default setting to a lower value results in quick link failure detections. You must

make sure that this is appropriate for your deployment. We recommend that you modify the default setting only for those applications which are sensitive to E_D_TOV values. For other applications, the default configuration is sufficient.

Limitations and Restrictions

When you configure IOA, consider the following limitations:

• Only 512 flows are supported when IOA and IVR co-exists.

• You can provision only one intelligent application on a single service engine. In SSN-16 there are 4

service engines and each service engine can host a single intelligent application.

• In Cisco NX-OS Release 4.2(1), only IO A and FCIP can run on the same SSN-16 as in the following

exampl e :

–

If one of the service engines runs SME on an SSN-16, you cann ot configu re another appl ication the remaining service engines on this SSN-16.

“Setting the Tunable Parameters” section on page 4-16.

3-8

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 3 Deployment Considerations

Limitations and Restrictions

Send documentation comments to mdsfeedback-doc@cisco.com

–

If one of the service engines runs IOA or FCIP, you can configure other service engines to run either FCIP or IOA.

• IOA uses the image that is bundled as a part of the Cisco MDS NX-OS Release. In Cisco MDS

NX-OS Release 4.2(1), SSI images are not supported for IOA.

• IOA decides the master based on a master election algorithm. If you have multiple switches in the

IOA cluster, you must add all the switches in the site that you manage from into the cluster before adding switches from the remote site. For more information see

and Recovery Scenarios.”

• IOA clustering framework uses IP connectivity for its internal operation. In Cisco NX-OS Release

4.2(1), if an IOA cluster becomes nonoperational due to IP connectivity, IOA flows are brought down to offline state. In this state, the hosts may not be able to see the tar gets. To accelerate the IOA flows, the IOA cluster must be operational and there must be at least one IOA switch in each site that is online within this IOA cluster.

• 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.

• In Cisco MDS NX-OS Release 4.2(1), the following features cannot coexist with IOA for a specif ic

flow: SME, DMM, IVR, NPV and NPIV, F PortChannel or Trunk. In Cisco NX-OS Release 5.0(1), IVR is supported with IOA.

• To implement IOA on IVR flows, the host switches, target switches, border switches, and the IOA

switches must all be running AAM-supported Cisc o MDS NX- OS Release 5.0(1) or later. For more information, refer to the Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide.

• If there are multiple Cisco IOA clusters in a region, a target can be part of the IOA configuration in

only one cluster. To change the target to a different cluster, the configu ration in the fi rst cluster must be deleted before creating the configuration in the second cluster.

Appendix B, “Cluster Management

• IOA licenses are not tied to a specific IOA service engine. IOA licenses are checked out when any

of the following event occurs:

–

An IOA interface is configured.

–

A line card that contains the IOA interface comes online. There are no links between an IOA license and a IOA service engine. If a line card goes offline, another IOA interface can be brought up using the same IOA license. In such cases, when the line card comes back online, the IOA interface is automatically brought down with status displaying No License. You need to to install licenses corresponding to the number of IO A interfaces conf igured rega rdless of the status of the line card.

• If IOA flo ws are configured and a copy running to startup is not performed, FCR rules are remov ed

automatically for these flows in all VSANs except VSAN 1. VSAN 1 is a default VSAN that is always persistent even without a copy running to startup and so, FCR rules are preserved for this VSAN. To recover from this, you can execute "clear fc-redirect decommision-switch" prior to the reboot of the switch to purge the FCR configs in VSAN 1. Alternately, you can cleanup the entire IOA flow configuration prior to the reboot of the switch.

• If an MDS switch is connected through an ISL using a twinpeak line card and the targets are

connected to the MDS switch, then this MDS switch can connect to a maximum of 160 targets. This because the maximum number of ELS entries on the twinpeak li ne card is 320 en tries. F or examp le, in an IOA conf iguratio n that has 5 flo ws (1 ho st : 1 tar get) you can ha v e 10 ELS en tries on a module with ISL and in a IO A conf igurat ion that has 1 0 flo ws (2 h osts : 1 tar get), you can ha v e o nly 10 ELS entries. This because ELS entries depends on the nu mber of targets.

The workaround for such a case would be to implement allowed VSAN on ISL. For example, if

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

3-9

Chapter 3 Deployment Considerations

Configuration Limits

Send documentation comments to mdsfeedback-doc@cisco.com

ISL-1 is connected to module 9 and is limited to VSAN 2000, then all the ELS entries specific to VSAN 2000 will be on module 9. If ISL-2 is connected to module 2 and is limited to VSAN-3000, then all the ELS entries specific to targets of VSAN-3000 will be on module 2.

• IOA flow takes a fe w seconds to become active upon certain triggers su ch as host or target po rt flaps.

PLOGI from the hosts are buffered until the IOA flow becomes active. Once the IOA flo w becomes active, it sends a RSCN to request the host to PLOGI again. Certain target arrays perform a few back-to-back PLOGIs prior to the flow becoming active and upon seeing a failure requires a manual corrective action. To prevent this, IOA flows that have been configured for Write-Acceleration are set up with a default timeout of 10 seconds after which the flow becomes unaccelerated. This is useful specifically in cases where IOA is unable to take over the flow prior to the timeout. For example, linecard reloads where no other IOA interface is available to handle the flow. In certain target arrays, the 10 second timeout is not sufficient and these arrays may require manual recovery using the storage management interfaces. One example of such a target array is HDS AMS.

The workaround for such a case would be to set the timeout to 5 seconds using the CLI command "tune wa-fcr-rule-timeout 5" under the ioa cluster configuration sub-mode. This configuration is cluster-wide persistent across reboots.

Configuration Limits

Table 3-1 lists the IOA configurations and the corresponding limits.

Table 3-1 Cisco I/O Accelerator Configuration Limits

Configuration Limit

Number of switches in a cluster 4

Number of Switches in the SAN for FC-Redirect 34

Number of IOA interfaces in a switch 44

Number of IOA interfaces in a cluster 44

Number of hosts per target 128

Number of flows in a cluster 1024

Number of flows across all clusters 1024

Number of flows per IOA service engine (hard limit) 128

Number of flows per IOA service engine (soft limit) 64

Note When the new flows are load balanced again to the functional IOA interface, the soft limit is enforced

to account for IOA interface failures. If the number of switches in the SAN e xceeds the scalability li mit, consider using CFS regions as described in “Using FC-Redirect with CFS Regions” section on page 2-4.

3-10

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Send documentation comments to mdsfeedback-doc@cisco.com

CHAPTER

Configuring IOA Using the CLI

This chapter describes how to configure IOA using the command line interface (CLI). This chapter describes these sections:

• Configuring IOA, page 4-2

• Configuring an IOA Cluster, page 4-5

• IOA Flow Setup Wizard, page 4-11

• Creating Multiple IOA Clusters on a Single Switch, page 4-14

• Additional Configurations, page 4-15

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-1

Chapter 4 Configuring IOA Using the CLI

Configuring IOA

Send documentation comments to mdsfeedback-doc@cisco.com

Configuring IOA

In this chapter, all conf igur ation steps relate to a refer ence topology shown in Figure 4-1 where SJC and RTP represent two sites connected through the WAN or MAN ISLs. In this example, sjc-sw2 and rtp-sw2 represent the core switches where IOA is deployed. sjc-sw1 and rtp-sw1 are edge switches that has the hosts or targets connected to them.

Figure 4-1 IOA CLI Reference Topology

Site: SJC

Site: RTP

MAN/WAN

MSM

ISLs

sjc-sw2

sjc-sw1

The process of configuring IOA involves a number of configuration tasks that should be completed in order:

On each IOA switch, complete the following configurations:

• Enabling Clustering, page 4-3

• Enabling the IOA Service, page 4-3

• Classifying the Switches to IOA Sites, page 4-3

• Configuring IOA Interfaces, page 4-4

rtp-sw2

rtp-sw1

276372

4-2

On the master IOA switch, complete the following configurations:

• Configuring an IOA Cluster, page 4-5

• Adding Nodes to an IOA Cluster, page 4-6

• Adding Interfaces to an IOA Cluster, page 4-8

• Adding N Ports to an IOA Cluster, page 4-9

• Configuring the IOA Flows, page 4-10

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Configuring IOA

Send documentation comments to mdsfeedback-doc@cisco.com

Enabling Clustering

The first step in the process of configuring IOA is to enable clustering in all of the IOA switches. To enable or disable the IOA cluster on sjc-sw2, perform this task:

Command Purpose

Step 1

Step 2

sjc-sw2# conf t sjc-sw2(config)#

sjc-sw2(config)# feature cluster

sjc-sw2(config)# no feature cluster

Enters configuration mode.

Enables clustering. Disables clustering.

To complete the configuratio n for th e refere nce topology, enable clustering in rtp-sw2.

Enabling the IOA Service

After enabling the IOA cluster, the second step in the process of configuring IOA is to enable the IOA service on each of the IOA switches.

To enable the IOA service on sjc-sw2, perform this task:

Command Purpose

Step 1 Step 2

sjc-sw2# config t

sjc-sw2(config)# feature ioa

sjc-sw2(config)# no feature ioa

To complete the configuratio n for th e refere nce topology, enable the IOA service in rtp-sw2.

Classifying the Switches to IOA Sites

Each of the IOA switches need to be classified into a site. Make sure that you classify only the IOA switches within the physical site into an IOA site.

To classify an IOA switch into the SJC site, perform this task:

Command Purpose

Step 1

Step 2

sjc-sw2# config t sjc-sw2(config)#

sjc-sw2(config)# ioa site-local SJC

Enters configuration mode. Enables IOA feature. Disables IOA feature.

Enters configuration mode.

Configures the site to which the switch belongs to. The maximum name length is restricted to 31 alphabetical characters.

To complete the configuration for the reference topology, classify rtp-sw2 into RTP site.

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

Note This command configures the site to which the

switch belongs to across all the IOA clusters that the switch participates in.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-3

Chapter 4 Configuring IOA Using the CLI

Configuring IOA

Send documentation comments to mdsfeedback-doc@cisco.com

Configuring IOA Interfaces

After enabling the cluster and enabling IOA, configure the IOA interfaces on the switch. To provision an IOA interface, perform this task:

Command Purpose

Step 1

Step 2

sjc-sw2# config t

sjc-sw2(config)#

sjc-sw2(config)# interface ioa

2/1

Enters configuration mode.

Configures IOA on service engine 1 in slot 2.

Step 3

sjc-sw2(config)# interface ioa

2/2

Configures IOA on service engine 2 in slot 2.

Note Service engines 2, 3, and 4 are available only on the

SSN-16 module. The appropriate IOA license is checked out as a part of the creation of the interface.

A standard MDS notation is used to denote the IOA interfaces: ioa slot/service engine. For example, ioa2/1 refers to Slot 1, Service Engine 1. In the case of the MSM-18/4 Module and 9222i Switch, only one service engine exists and so only ioa2/1 is v alid. In the case of the SSN-16 Module, four service engines exist an d so ioa2/1, ioa2/2, ioa2/3, and ioa2/4 are valid interfaces.

sjc-sw2(config)# no interface

ioa 2/2

Deletes the IOA interface.

Note Before deleting an IOA interface, you must remove

the IOA interface from the cluster.

sjc-sw2(config-if)# no

shutdown

sjc-sw2(config-if)# shutdown Disable s the IOA interface.

Enables the IOA interface.

Note FCIP and IOA are not supported on the same engine.

To complete the configuration for the reference topology, configure the interfaces in rtp-sw2.

Displaying IOA Interface Status

After configuring the IOA interface, use the show int command to show whether the IOA interface is down. The interface is down until the interface is added to a cluster:

sjc-sw2# show interface ioa 2/1 ioa2/1 is down (Not in any Cluster) 0 device packets in, 0 device packets out 0 device bytes in, 0 device bytes out 0 peer packets in, 0 peer packets out 0 peer bytes in, 0 peer bytes out

0 i-t create request, 0 i-t create destroy

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-4

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

Chapter 4 Configuring IOA Using the CLI

Configuring an IOA Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

0 i-t activate request, 0 i-t deactivate request

Possible reasons for the interface being down are as follows:

• Administratively down—The interface is shut down.

• Not in any cluster—The interface is not part of any IOA cluster.

• Port software failure—A software failure has occured causing a reset of the IOA service engine.

• No license—The interface does not have a valid IOA license. The license is either not installed or

all the available licenses are in use.

Configuring an IOA Cluster

To configure a cluster, start with a switch and create a cluster and add the remaining IOA switches into the cluster. From this point on, all cluster parameters can be configured from this switch.

To create an IOA cluster, perform this task:

Command Purpose

Step 1

Step 2

sjc-sw2# config t sjc-sw2(config)#

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)#

sjc-sw2(config)# no ioa

cluster tape_vault

Enters configuration mode.

Assigns a user-specified name (tape_vault) to the IOA cluster. The maximum length of the name is 31 alphabetical characters. Enters the cluster configuration submo de. The local switch is im plicitly added to the cluster as part of this command.

Deletes the specified IOA cluster.

Note You need to select a switch that you want to be the master sw itch as the seed switch when you

create the IOA cluster. If you have multiple switches in a site, you may add all the switches in a site that you want to manage from to the cluster before adding the switches from the remote site.

This section inlcudes the following topics :

• Displaying IOA Cluster Status, page 4-5

• Adding Nodes to an IOA Cluster, page 4-6

• Adding Interfaces to an IOA Cluster, page 4-8

• Adding N Ports to an IOA Cluster, page 4-9

• Configuring the IOA Flows, page 4-10

Displaying IOA Cluster Status

The following examples display the cluster information:

sjc-sw2# show ioa cluster IOA Cluster is tape_vault Cluster ID is 0x213a000dec3ee782 Cluster status is online Is between sites SJC and RTP Total Nodes are 2

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-5

Chapter 4 Configuring IOA Using the CLI

Configuring an IOA Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

Cluster Infra Status : Operational Cluster is Administratively Up Cluster Config Version : 26 SSL for ICN : Not Configured

sjc-sw2# show ioa cluster tape_vault IOA Cluster is tape_vault Cluster ID is 0x213a000dec3ee782 Cluster status is online Is between sites SJC and RTP Total Nodes are 2 Cluster Infra Status : Operational Cluster is Administratively Up Cluster Config Version : 26 SSL for ICN : Not Configured

A cluster can have the following statuses:

• Pending—An IOA interface needs to be added to the cluster.

• Online—The cluster is online. IOA services can be run on the cluster.

• Offline—The cluster is offline. Check the infrastructure status for more information.

The infrastructure status has following values:

• Operational—The cluster infrastructure is operational on this switch. The IOA service will be able

to use the cluster on this switch.

• Not Operational—The cluster infrastructure is not operational on this node. The IOA service will

not run on this cluster on this switch.

The administrative status has following values:

• Administratively Up—If the cl uster is not online, check this status to make sure that administrativ ely

the cluster is up.

• Administratively Shutdown—The cluster was shut down.

Adding Nodes to an IOA Cluster

To add nodes to an IOA cluster, perform this task:

Command Purpose

Step 1

Step 2

sjc-sw2# config t

switch(config)#

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)#

Enters configuration mode.

Enters the cluster configuration submode and adds the local switch where this command is executed into the IOA cluster.

4-6

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Configuring an IOA Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

Command Purpose

Step 3

sjc-sw2(config-ioa-cl)# node

local

Enters the node configuration submode for the local switch. The local keyword denotes the switch where the CLI command is execute d.

Note You may also specify the node name of the local

switch to enter sub mode. The node name could be either the IP Address or the DNS name of the local switch.

sjc-sw2(config-ioa-cl)# node sjc-sw2

sjc-sw2(config-ioa-cl-node)#

end

sjc-sw2(config-ioa-cl)# node rtp-sw2

sjc-sw2(config-ioa-cl-node)#

end

sjc-sw2(config-ioa-cl)# no node rtp-sw2

Includes the switch as part of the cluster. Enters the node configuration submode.

Includes the remote switch as part of the cluster. Alternatively, use an IPv4 or IPv6 address. Enters the node configuration submode.

Removes the local or the remote node from the cluster.

The following examples display the nodes information:

sjc-sw2# show ioa cluster summary

------------------------------------------------------------------------------Cluster Sites Status Master Switch

------------------------------------------------------------------------------tape_vault SJC, online 172.23.144.97 RTP

sjc-sw2# show ioa cluster tape_vault node summary

------------------------------------------------------------------------------Switch Site Status Master

-------------------------------------------------------------------------------

172.23.144.97(L) SJC online yes

172.23.144.98 RTP online no

sjc-sw2# show ioa cluster tape_vault node Node 172.23.144.97 is local switch Node ID is 1 Status is online Belongs to Site SJC Node is the master switch Node 172.23.144.98 is remote switch Node ID is 2 Status is online Belongs to Site RTP Node is not master switch

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-7

Chapter 4 Configuring IOA Using the CLI

Configuring an IOA Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

Adding Interfaces to an IOA Cluster

To add IOA interfaces to an IOA cluster, perform this task:

Command Purpose

Step 1

Step 2

Step 3

sjc-sw2# config t

switch(config)#

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)#

sjc-sw2(config-ioa-cl)# node

local

Enters configuration mode.

Enters the cluster configuration submode.

Includes the local switch as part of the cluster. Enters the node configuration submode for the local switch. The local keyword denotes the switch where the CLI command is executed.

Note You may also specify the node name of the local

switch to enter sub mode. The node name could be either the IP address or the DNS name of the local switch.

Step 4

sjc-sw2(config-ioa-cl-node)#

interface ioa 2/1

sjc-sw2(config-ioa-cl-node)#

interface ioa 2/2

sjc-sw2(config-ioa-cl-node)#

no interface ioa 2/2

sjc-sw2(config-ioa-cl)# node

rtp-sw2

Adds the interfaces to the IOA cluster.

Removes the interface from the IOA cluster.

Includes the remote switch as part of the cluster. Alternatively, use a IPv4 or IPv6 address. Enters the node configuration submode.

sjc-sw2(config-ioa-cl-node)#

interface ioa 2/1

sjc-sw2(config-ioa-cl-node)#

interface ioa 2/2

sjc-sw2(config-ioa-cl-node)#

no interface ioa 2/2

Adds the interfaces to the IOA cluster.

Removes the interface from the IOA cluster.

The following examples display IOA interfaces information:

sjc-sw2# show interface ioa2/1 ioa2/1 is up Member of cluster tape_vault 0 device packets in, 0 device packets out 0 device bytes in, 0 device bytes out 0 peer packets in, 0 peer packets out 0 peer bytes in, 0 peer bytes out

4-8

303 i-t create request, 300 i-t create destroy 300 i-t activate request, 0 i-t deactivate request

sjc-sw2# show ioa cluster tape_vault interface summary

------------------------------------------------------------------------------Switch Interface Status Flows

-------------------------------------------------------------------------------

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Configuring an IOA Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

172.23.144.97(L) ioa2/1 up --

172.23.144.97(L) ioa2/2 up --

172.23.144.98 ioa2/1 up --

172.23.144.98 ioa2/2 up --

sjc-sw2# show ioa cluster tape_vault interface Interface ioa2/1 belongs to 172.23.144.97(L)(M) Status is up Interface ioa2/2 belongs to 172.23.144.97(L)(M) Status is up Interface ioa2/1 belongs to 172.23.144.98 Status is up Interface ioa2/2 belongs to 172.23.144.98 Status is up

Note ( L) indicates the Local switch.

(M) indicates the Master switch.

Adding N Ports to an IOA Cluster

To add N ports to the IOA cluster, perform this task:

Command Purpose

Step 1

Step 2

Step 3

sjc-sw2# config t sjc-sw2(config)#

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)# nport pwwn 10:0:0:0:0:0:0:1 site SJC vsan 100

sjc-sw2(config-ioa-cl)# nport pwwn 11:0:0:0:0:0:0:1 site RTP vsan 100

sjc-sw2(config-ioa-cl)# nport pwwn 10:0:0:0:0:0:0:2 site SJC vsan 100

sjc-sw2(config-ioa-cl)# nport pwwn 11:0:0:0:0:0:0:2 site RTP vsan 100

sjc-sw2(config-ioa-cl)# end

sjc-sw2(config-ioa-cl)# no

nport pwwn 10:0:0:0:0:0:0:1

Enters configuration mode.

Enters the cluster configuration submode.

Configures the site and VSAN ID of the N ports that will be a part of accelerated flows.

Removes the N port from the IOA cluster.

This example shows how to display N ports configuration:

sjc-sw2# show ioa cluster tape_vault nports

------------------------------------------------------------------------------P-WWN Site Vsan

------------------------------------------------------------------------------10:00:00:00:00:00:00:01 SJC 100 11:00:00:00:00:00:00:01 RTP 100 10:00:00:00:00:00:00:02 SJC 100 11:00:00:00:00:00:00:02 RTP 100

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-9

Chapter 4 Configuring IOA Using the CLI

Configuring an IOA Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

Configuring the IOA Flows

Before configuring the IOA flows, flow groups must be created. To create a new IOA flow group and add flows, perform this task:

Command Purpose

Step 1

Step 2

Step 3

Step 4

switch# config t

switch(config)#

switch(config)# ioa cluster

tape_vault

switch(config-ioa-cl)#

flowgroup tsm

switch(config-ioa-cl)# no

flowgroup tsm

sjc-sw2(config-ioa-cl-flgrp)#

host 10:0:0:0:0:0:0:1 target

11:0:0:0:0:0:0:1

Enters configuration mode.

Enters the cluster configuration submode.

Creates an IOA flow group.

Deletes an IOA flow group.

Creates a flow with write acceleration.

sjc-sw2(config-ioa-cl-flgrp)#

host 10:0:0:0:0:0:0:2 target

11:0:0:0:0:0:0:2 tape

sjc-sw2(config-ioa-cl-flgrp)#

host 10:0:0:0:0:0:0:3 target

11:0:0:0:0:0:0:3 compression

sjc-sw2(config-ioa-cl-flgrp)#

host 10:0:0:0:0:0:0:4 target

11:0:0:0:0:0:0:4 tape

compression

sjc-sw2(config-ioa-cl-flgrp)#

no host 10:0:0:0:0:0:0:1

target 11:0:0:0:0:0:0:1

Creates a flow with tape acceleration.

Creates a flow with write acceleration and compression.

Creates a flow with tape acceleration, and compression.

Removes the configured flow.

Note We recommend that you suspend the traffic while enabling IOA for a given flow.

The following examples display the configured flow information:

sjc-sw2# show ioa cluster tape_vault flows

------------------------------------------------------------------------------Host WWN, VSAN WA TA Comp Status Switch,Interface Target WWN Pair

-------------------------------------------------------------------------------

4-10

10:00:00:00:00:00:00:01, 100 Y Y N online 172.23.144.97, ioa2/1 11:00:00:00:00:00:00:01 172.23.144.98, ioa2/1 10:00:00:00:00:00:00:02, 100 Y Y Y online 172.23.144.97, ioa2/2 11:00:00:00:00:00:00:02 172.23.144.98, ioa2/2

sjc-sw2# show ioa cluster tape_vault flows detail Host 10:00:00:00:00:00:00:01, Target 11:00:00:00:00:00:00:01, VSAN 100 Is online Belongs to flowgroup tsm

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

IOA Flow Setup Wizard

Send documentation comments to mdsfeedback-doc@cisco.com

Is enabled for WA, TA Is assigned to Switch 172.23.144.97 Interface ioa2/1 (Host Site) Switch 172.23.144.98 Interface ioa2/1 (Target Site) Host 10:00:00:00:00:00:00:02, Target 11:00:00:00:00:00:00:02, VSAN 100 Is online Belongs to flowgroup tsm Is enabled for WA, TA, Compression Is assigned to Switch 172.23.144.97 Interface ioa2/2 (Host Site) Switch 172.23.144.98 Interface ioa2/2 (Target Site)

IOA Flow Setup Wizard

You can use the IOA Flow Setup Wizard to simplify th e provisioning of flo ws especially when there are many flows to provision, and when you add, remove, or replace host HBAs, tape drives or storage controllers.

This section includes the following topics:

• Prerequisites for IOA Flow Setup Wizard, page 4-11

• Using the IOA Flow Setup Wizard, page 4-11

Prerequisites for IOA Flow Setup Wizard

The following prerequisites must be met before you can invoke the IOA Flow Setup Wizard:

• All of the N ports of both initiators and targets that need to be accelerated must be online.

• The zoning configuration must already be in place to per mit the flows that need to communi cate with

each other. If you are replacing a host HBA, you must update the zoning configuration to remove the faulty HBA and to add the new HBA before you invoke the IOA Flow Setup Wizard.

Using the IOA Flow Setup Wizard

To configure flows using the Flow Setup Wizard, follow these steps:

Step 1 Invoke the Flow Setup Wizard on a specific VSAN.

sjc-sw1# ioa flow-setup cluster tape_vault flowgroup repln-fg vsan 100

In the case of an IVR deployment, you can enter th e following CLI command on an IVR b order switch where IOA is deployed:

sjc-sw1# ioa ivr flow-setup cluster tape_vault flowgroup repln-fg

The wizard processes the active zone set for the VSAN and creates a set of ca ndidate flows. When you use the ivr flow-setup command, the active IVR zone set is considered. The zone set may have local flows as well as flows that traverse across sites. The IOA Flow Setup Wizard runs through a series of steps as listed in this procedure to prune the list to capture only the flows that traverse across the sites that need to be accelerated.

Step 2 Classify the switches in the candidate switch list into appropriate sites.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-11

Chapter 4 Configuring IOA Using the CLI

IOA Flow Setup Wizard

Send documentation comments to mdsfeedback-doc@cisco.com

This step is only for those switches where non e of the hosts or t argets have been configured yet for acceleration. From the flows in the active zone set, a candidate switch list is prepared based on where the hosts and targets are logged into.

The following switches need to be classified into appropriate sites

------------------------------------------------------------------------------Do you want to classify sjc-sw1 into site sjc or rtp [sjc] Do you want to classify 172.23.144.96 into site sjc or rtp [sjc] rtp

The candidate flow list is now pruned to contain only the inter-site flows that need to be accelerated.

Step 3 The wizard displays all of the N ports that need to be classified into sites. Enter yes to classify the N

ports into sites.

The following nport to site mapping needs to be configured

------------------------------------------------------------------------------N-Port PWWN: 10:00:00:00:00:00:00:00 Site: sjc N-Port PWWN: 10:00:00:00:00:00:01:00 Site: sjc N-Port PWWN: 10:00:00:00:00:00:02:00 Site: sjc N-Port PWWN: 10:00:00:00:00:00:03:00 Site: sjc N-Port PWWN: 10:00:00:00:00:00:04:00 Site: sjc N-Port PWWN: 11:00:00:00:00:00:00:00 Site: rtp N-Port PWWN: 11:00:00:00:00:00:01:00 Site: rtp N-Port PWWN: 11:00:00:00:00:00:02:00 Site: rtp N-Port PWWN: 11:00:00:00:00:00:03:00 Site: rtp N-Port PWWN: 11:00:00:00:00:00:04:00 Site: rtp Do you want to configure the n-port to site mappings? (yes/no) [yes] yes

Step 4 (Optional) Use this step only when some of the N ports such as those used in remote replication are

represented as scsi-fcp(both) in the FCNS database. Enter the primary direction of the traffic that will be used by IOA to decide on what should be configured as host and target in IOA.

Replication traffic can flow in either direction.

Certain N-ports in this VSAN can act as both initiator and targets Is the traffic flow primarily from sjc to rtp? (yes/no) [yes] yes

Step 5 The wizard configures the list of flows that are not already configured in IOA and attempts to delete the

IOA flows that are not part of the zone set. This operation specif ically handles removing HB As or storage controllers. Enter yes to accept the flows that need to be accelerated. New flows that need to be accelerated are displayed.

The following flows will be configured

------------------------------------------------------------------------------Host: 10:00:00:00:00:00:00:00 VSAN: 100 Target: 11:00:00:00:00:00:00:00 VSAN:100 Host: 10:00:00:00:00:00:00:00 VSAN: 100 Target: 11:00:00:00:00:00:01:00 VSAN:100 Host: 10:00:00:00:00:00:00:00 VSAN: 100 Target: 11:00:00:00:00:00:02:00 VSAN:100 Host: 10:00:00:00:00:00:00:00 VSAN: 100 Target: 11:00:00:00:00:00:03:00 VSAN:100 Host: 10:00:00:00:00:00:01:00 VSAN: 100 Target: 11:00:00:00:00:00:00:00 VSAN:100 Host: 10:00:00:00:00:00:01:00 VSAN: 100 Target: 11:00:00:00:00:00:01:00 VSAN:100 Host: 10:00:00:00:00:00:01:00 VSAN: 100 Target: 11:00:00:00:00:00:02:00 VSAN:100 Host: 10:00:00:00:00:00:01:00 VSAN: 100 Target: 11:00:00:00:00:00:03:00 VSAN:100 Host: 10:00:00:00:00:00:02:00 VSAN: 100 Target: 11:00:00:00:00:00:00:00 VSAN:100 Host: 10:00:00:00:00:00:02:00 VSAN: 100 Target: 11:00:00:00:00:00:01:00 VSAN:100 Host: 10:00:00:00:00:00:02:00 VSAN: 100 Target: 11:00:00:00:00:00:02:00 VSAN:100 Host: 10:00:00:00:00:00:02:00 VSAN: 100 Target: 11:00:00:00:00:00:03:00 VSAN:100 Host: 10:00:00:00:00:00:03:00 VSAN: 100 Target: 11:00:00:00:00:00:00:00 VSAN:100 Host: 10:00:00:00:00:00:03:00 VSAN: 100 Target: 11:00:00:00:00:00:01:00 VSAN:100 Host: 10:00:00:00:00:00:03:00 VSAN: 100 Target: 11:00:00:00:00:00:02:00 VSAN:100 Host: 10:00:00:00:00:00:03:00 VSAN: 100 Target: 11:00:00:00:00:00:03:00 VSAN:100 Host: 10:00:00:00:00:00:04:00 VSAN: 100 Target: 11:00:00:00:00:00:04:00 VSAN:100 Do you want to configure these flows? (yes/no) [yes] yes

4-12

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

IOA Flow Setup Wizard

Send documentation comments to mdsfeedback-doc@cisco.com

You can display the configured flow information by using the following commands:

sjc-sw1# show ioa cluster tape_vault nports

------------------------------------------------------------------------------P-WWN Site Vsan

------------------------------------------------------------------------------10:00:00:00:00:00:00:00 sjc 100 10:00:00:00:00:00:01:00 sjc 100 10:00:00:00:00:00:02:00 sjc 100 10:00:00:00:00:00:03:00 sjc 100 10:00:00:00:00:00:04:00 sjc 100 11:00:00:00:00:00:00:00 rtp 100 11:00:00:00:00:00:01:00 rtp 100 11:00:00:00:00:00:02:00 rtp 100 11:00:00:00:00:00:03:00 rtp 100 11:00:00:00:00:00:04:00 rtp 100

sjc-sw1# show ioa cluster tape_vault flows

------------------------------------------------------------------------------Host WWN, VSAN WA TA Comp Status Switch,Interface Target WWN Pair

-------------------------------------------------------------------------------

10:00:00:00:00:00:00:00, 100 Y N N offline --, -11:00:00:00:00:00:00:00 --, -- 10:00:00:00:00:00:01:00, 100 Y N N offline --, -11:00:00:00:00:00:00:00 --, -- 10:00:00:00:00:00:02:00, 100 Y N N offline --, -11:00:00:00:00:00:00:00 --, -- 10:00:00:00:00:00:03:00, 100 Y N N offline --, -11:00:00:00:00:00:00:00 --, -- 10:00:00:00:00:00:00:00, 100 Y N N offline --, -11:00:00:00:00:00:01:00 --, -- 10:00:00:00:00:00:01:00, 100 Y N N offline --, -11:00:00:00:00:00:01:00 --, -- 10:00:00:00:00:00:02:00, 100 Y N N offline --, -11:00:00:00:00:00:01:00 --, -- 10:00:00:00:00:00:03:00, 100 Y N N offline --, -11:00:00:00:00:00:01:00 --, -- 10:00:00:00:00:00:00:00, 100 Y N N offline --, -11:00:00:00:00:00:02:00 --, -- 10:00:00:00:00:00:01:00, 100 Y N N offline --, -11:00:00:00:00:00:02:00 --, -- 10:00:00:00:00:00:02:00, 100 Y N N offline --, -11:00:00:00:00:00:02:00 --, -- 10:00:00:00:00:00:03:00, 100 Y N N offline --, -11:00:00:00:00:00:02:00 --, -- 10:00:00:00:00:00:00:00, 100 Y N N offline --, -11:00:00:00:00:00:03:00 --, -- 10:00:00:00:00:00:01:00, 100 Y N N offline --, -11:00:00:00:00:00:03:00 --, -- 10:00:00:00:00:00:02:00, 100 Y N N offline --, -11:00:00:00:00:00:03:00 --, -- 10:00:00:00:00:00:03:00, 100 Y N N offline --, -11:00:00:00:00:00:03:00 --, -- 10:00:00:00:00:00:04:00, 100 Y N N offline --, -11:00:00:00:00:00:04:00 --, --

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-13

Chapter 4 Configuring IOA Using the CLI

SITE-RTP

SITE-SAC

276370

SITE-SJC

Creating Multiple IOA Clusters on a Single Switch

Send documentation comments to mdsfeedback-doc@cisco.com

Creating Multiple IOA Clusters on a Single Switch

Figure 4-2 illustrates the IOA implementation where the IOA service is extended across multiple sites.

In the illustration, Site-SJC consolidates the tape backup from Site-R TP and Site-SA C. Each IO A cluster represents a site pair, which means there are two unique clusters. This topology provides segre gation and scalability of the IOA service across multiple sites. In the Site-SJC, a single switch can participate in multiple IOA clusters.

Figure 4-2 Extended Across Multiple Sites

4-14

Note Before creating another cluster on sjc-sw2, create a third site SAC with the sac-sw2 switch. Clustering

and IOA service must be enabled, and IOA interfaces must have been provisioned on the sac-sw2 switch.

To create another IOA cluster on sjc-sw2 with SAC, follow these steps:

Command Purpose

Step 1 Step 2

Step 3

Step 4

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

sjc-sw2# config t

sjc-sw2(config)# ioa cluster

tape_vault_site2

sjc-sw2(config-ioa-cl)# node local

sjc-sw2(config-ioa-cl-node)#

interface ioa2/3

sjc-sw2(config-ioa-cl)# node sac-sw2

sjc-sw2(config-ioa-cl-node)#

interface ioa2/3

Enters configuration mode. Specifies the cluster name and enters IOA cluster

configuration submode. A cluster name can include a maximum of 31 alphabetical characters.

Adds the local switch to the cluster. Enters the node configuration mode.

Adds the IOA interface to the cluster.

Adds the remote node to the cluster and enters the node configuration mode.

Adds the IOA interface to the cluster.

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

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

The following example displays the multiple clusters created using the SJC site:

sjc-sw2# show ioa cluster summary

------------------------------------------------------------------------------Cluster Sites Status Master Switch

------------------------------------------------------------------------------tape_vault SJC, online 172.23.144.97 RTP tape_vault_site2 SAC, online 172.23.144.97 SJC

Note You need to select a switch that you want to be the master switch as the seed switch when you create the

IOA cluster. If you have multiple switches in a site, you may add all the switches in a site that you want to manage from to the cluster before adding the switches from the remote site.

Note In this example, the SJC site may be a natural consolidation point for management, and you may choose

a switch from this site as the preferred master switch.

Additional Configurations

This section inlcudes the following topics :

• Shutting Down a Cluster, page 4-15

• Load Balancing the Flows, page 4-16

• Setting the Tunable Parameters, page 4-16

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

Shutting Down a Cluster

To shut down a cluster, perform this task:

Command Purpose

Step 1 Step 2

Step 3

sjc-sw2# config t

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)# shut

Enters configuration mode. Specifies the cluster name and enters IOA cluster

configuration submode. A cluster name can include a maximum of 31 alphabetical characters.

Shuts down the cluster. This command must be used to recover a cluster when it is partitioned. The change can be disruptive. For more information, see “

Clust e r R e c ove ry

Scenarios, page B-5.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-15

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

Load Balancing the Flows

To load balance the flows, perform this task:

Command Purpose

Step 1 Step 2

Step 3

sjc-sw2# config t

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)#

load-balancing

sjc-sw2(config-ioa-cl)#

load-balancing enable

sjc-sw2(config-ioa-cl)#

load-balancing

11:22:33:44:55:66:77:88

Enters configuration mode. Enters the cluster configuration mode.

Load balances all the IOA flows. This process is disruptive and causes th e hosts to relo gin into tar gets. The load-balancing command will take some time to execute depending on the number of flows. You should not abort the command in the middle of its execution.

The load-balancing enable command turns on the load-balancing attribute for the n ew flows. You may enter the load-balancing enable command only when you abort the load-balancing command process.

Load balances specified targets in the IOA flows. This process is disruptive and causes the hosts to re-login into targets. The load-balancing command will take some time to execute depending on the number of flows. You should not abort the command in the middle of its execution.

Setting the Tunable Parameters

To set the the following tunable parameters based on your deployment requirements, perfo rm this ta sk:

Command Purpose

sjc-sw2(config-ioa-cl)# tune

round-trip-time ms

sjc-sw2(config-ioa-cl)# tune

lrtp-retx-timeout msec

Caution The following are advanced tunable parameters, and you must consult the Cisco Services and Support

team before tuning these parameters.

To set the the following adv a nced tunable parameters based on your deployment requirements, perform this task:

Specifies the round-trip time in millisecon ds. It is the time taken by the IOA data packet to traverse between two sites. The value can vary from 1 to 100 ms. 15 ms is the default.

Specifies the LRTP retransmit timeout in milliseconds. It is the time to wait before LRTP starts retransmitting packets. The value can vary from 500 to 5000 msec. 2500 msec is the default.

For more information, refer to Tuning for E_D_TOV under

“Resiliency Considerations”

section on page 3-8.

4-16

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

Command Purpose

Step 1 Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

sjc-sw2# config t

sjc-sw2(config)# ioa cluster

tape_vault

sjc-sw2(config-ioa-cl)# tune timer rscn-suppression seconds

sjc-sw2(config-ioa-cl)# tune timer load-balance target

seconds

sjc-sw2(config-ioa-cl)# tune timer load-balance global

seconds

sjc-sw2(config-ioa-cl)# tune ta-buffer-size KB

sjc-sw2(config-ioa-cl)# tune wa-buffer-size MB

sjc-sw2(config-ioa-cl)# tune wa-max-table-size KB

Enters configuration mode. Enters the cluster configuration mode.

Specifies the IOA RSCN suppression timer v alue. It is the amount of time the IOA process waits before it queries FCNS (name server) after learning about changes in the network. This helps alleviate the amount of duplicate or repeating query in case of rapid network changes. The value can vary from 1 to 10 seconds. 5 seconds is the default.

Specifies a IOA target load-balance timer value. It is the amount of time the IOA process waits before it attempts to load balance all IT Nexuses of a certain target port after a change in connectivity has been detected. The value can vary from 2 to 30 seconds. 2 seconds is the default.

Specifies a global IOA load-balance timer value. It is the amount of time the IOA process waits before it attempts to load balance all IT Nexuses conf igu red in a cluster after a change in connectivity has been detected. The value can vary from 5 to 30 seconds. 5 seconds is the default.

Specifies the tape acceleration buffer size in KB. It is the amount of buffering allowed for flow control during tape acceleration. The value can vary from 64 to 12288 KB or Auto. Auto is the default. Auto opti on takes WAN latencies and speed of the tape device into account to provide optimum performance.

Specifies the write acceleration buffer size in MB. It is the amount of buffering allowed for flow control during write acceleration. The value can vary from 50 to 100 MB. 70 MB is the default.

Specifies the Write Max Table size in KB. It is the maximum number of active exchanges supported on an IOA flow. The value can vary from 4 to 64 KB. 4 KB is the default.

Changing the Node Description and IP Address of an IOA Cluster

T o perfo rm any o f the follo w ing tasks, follo w the st eps def ined in the Guidelines for Changing the Node

Description and IP Address of an IOA Cluster, page 4-18.

• Change the node-description (IP address) and node IP-address of a cluster.

• Change node-description(DNS name) of a cluster.

• Change the node-description from IP address to DNS name and vice versa.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

4-17

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

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

Follow these steps to change the node description and IP address of an IOA node in the existing IOA cluster.

Step 1 Shut down the IOA cluster on the switch1. Step 2 Shut down the IOA cluster on the switch2. Step 3 Remove the IOA cluster on the switch2. Step 4 Remove the node of switch2 in the switch1. Step 5 Do one of the following based on what you want to perfom on the switch:

• Change the management interface IP Address.

• Change the IP address and the switch name.

• Enable or disable DNS configuration.

Step 6 Change node de scription us ing “node id id, node-description ip-address ip address” command on

switch1.

This step may vary depending on when the node description (DNS name) needs to be changed or node description and node IP address to be changed.

Step 7 Shut down the IOA cluster on the switch1. Step 8 Add switch2 node with new description and the IP address . Step 9 Add IOA interfaces on switch2.

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

This example shows the following configuration procedures used to change the description and IP address:

• Shut Down the IOA Cluster on switch1, page 4-19

• Shut Down the IOA Cluster on switch2, page 4-19

• Remove the IOA Cluster on switch2, page 4-19

• Remove the Node of switch2 in switch1, page 4-19

• Change the Management Interface IP Address on Switches, page 4-20

• Change the Node Description and IP Address on switch1, page 4-20

• No Shut Down IOA Cluster on switch1, page 4-20

• Add switch2 Node with New Description and the IP Address, page 4-20

4-18

• Add IOA Interfaces on switch2, page 4-20

• Verify the Node Description and IP Address and Flows, page 4-20

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

Shut Down the IOA Cluster on switch1

To shut down the IOA cluster on switch1 follow these steps:

sw-231-19(config)# show ioa cluster c1 node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

-------------------------------------------------------------------------------

172.25.231.14 site3 online no 2

172.25.231.19(L) site2 online yes 1 sw-231-19(config)# ioa cluster c1 sw-231-19(config-ioa-cl)# sh This change can be disruptive. Please ensure you have read the "IOA Cluster Recovery Procedure" in the configuration guide. -- Are you sure you want to continue? (y/n) [n] y 2011 Apr 12 07:02:21 sw-231-19 %CLUSTER-2-CLUSTER_LOCAL_NODE_EXIT: Local Node 0x1 has left the Cluster 0x5000530019f08076

Shut Down the IOA Cluster on switch2

To shut down the IOA cluster on switch2 follow these steps:

sw-231-14(config)# ioa cluster c1 sw-231-14(config-ioa-cl)# sh This change can be disruptive. Please ensure you have read the "IOA Cluster Recovery Procedure" in the configuration guide. -- Are you sure you want to continue? (y/n) [n] y 2011 Apr 12 07:02:30 sw-231-14 %CLUSTER-2-CLUSTER_LOCAL_NODE_EXIT: Local Node 0x2 has left the Cluster 0x5000530019f08076

sw-231-14(config-ioa-cl)# sh ioa cluster c1 node sum

------------------------------------------------------------------------------Switch Site Status Master Node ID

-------------------------------------------------------------------------------

192.125.231.14(L) -- unknown (cluster is offline) 2

192.125.231.19 -- unknown (cluster is offline) 1

Remove the IOA Cluster on switch2

To remove the IOA cluster on switch2, follow these steps:

sw-231-14(config-ioa-cl)# no ioa cluster c1 sw-231-14(config)#

Remove the Node of switch2 in switch1

To remove the node of switch 2 in switch1, follow these steps:

sw-231-19(config-ioa-cl)# no node 192.125.231.14 sw-231-19(config-ioa-cl)# sh ioa cluster c1 node sum

------------------------------------------------------------------------------Switch Site Status Master Node ID

-------------------------------------------------------------------------------

192.125.231.19(L) -- unknown (cluster is offline) 1

sw-231-19(config-ioa-cl)#

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-19

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

Change the Management Interface IP Address on Switches

sw-231-19(config)# int mgmt0 sw-231-10(config-if)# ip address 172.25.231.19 255.255.255.0 sw-231-19(config)# int mgmt0 sw-231-10(config-if)# ip address 172.25.231.25 255.255.255.0

Change the Node Description and IP Address on switch1

Change the node description and IP address on the switch1 using the command node id id new-description ip-address new-ip address

sw-231-19(config-ioa-cl)# node id 1 192.125.231.72 ip-address 192.125.231.72

No Shut Down IOA Cluster on switch1

To shut down the IOA cluster on a switch, follow these steps:

sw-231-19(config-ioa-cl-node)# no sh This change can be disruptive. Please ensure you have read the "IOA Cluster Recovery Procedure" in the configuration guide. -- Are you sure you want to continue? (y/n) [n] y sw-231-19(config-ioa-cl)# 2011 Apr 12 07:04:54 sw-231-19 %CLUSTER-2-CLUSTER_LEADER_ANNOUNCE: Node 0x1 is the new Master of cluster 0x5000530019f08076 of 1 nodes 2011 Apr 12 07:04:54 sw-231-19 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x5000530019f08076 now has quorum with 1 nodes

sw-231-19(config-ioa-cl)# show ioa cluster c1 node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

-------------------------------------------------------------------------------

192.125.231.72(L) site2 online yes 1

Add switch2 Node with New Description and the IP Address

To add switch2 node with new description and IP address, follow these steps

sw-231-19(config-ioa-cl)# node 172.25.231.25 2011 Apr 12 07:05:30 sw-231-19 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x5000530019f08076 now has quorum with 1 nodes 2011 Apr 12 07:05:30 sw-231-19 %CLUSTER-2-CLUSTER_QUORUM_GAIN: Cluster 0x5000530019f08076 now has quorum with 2 nodes

Add IOA Interfaces on switch2

To add IOA interfaces on the switch, follow these steps:

sw-231-19(config-ioa-cl-node)# int ioa 1/1 sw-231-19(config-ioa-cl-node)# int ioa 1/2 sw-231-19(config-ioa-cl-node)#

Verify the Node Description and IP Address and Flows

4-20

Use the following show commands to confirm the functioning of the clus ter wi th the new IP address:

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

sw-231-19(config)# show ioa cluster c1 node summary

------------------------------------------------------------------------------Switch Site Status Master Node ID

-------------------------------------------------------------------------------

172.25.231.25 site3 online no 2

172.25.231.72(L) site2 online yes 1

sw-231-19(config)# show ioa cluster c1 int summary

------------------------------------------------------------------------------Switch Interface Status Flows

-------------------------------------------------------------------------------

172.25.231.25 ioa1/1 up 20

172.25.231.25 ioa1/2 up 16

172.25.231.72(L) ioa4/1 up 20

172.25.231.72(L) ioa4/2 up 16

sw-231-19(config)# show ioa cluster c1 node Node 172.25.231.25 is remote switch Node ID is 2 IP address is 172.25.231.25 Status is online Belongs to Site site3 Node is not master switch Node 172.25.231.72 is local switch Node ID is 1 IP address is 172.25.231.72 Status is online Belongs to Site site2 Node is the master switch sw-231-19(config)#

Displaying Interface Statistics

The following examples display interface statistics:

sjc-sw2# show int ioa 2/1 counters ioa1/1 4454232796 device packets in, 375748229 device packets out 8948409208760 device bytes in, 24047886946 device bytes out 526563297 peer packets in, 2471396408 peer packets out 45198770258 peer bytes in, 4697995629324 peer bytes out

8 i-t create request, 4 i-t create destroy 8 i-t activate request, 0 i-t deactivate request

sjc-sw2# show int ioa 2/1 counters brief

------------------------------------------------------------------------------Interface To Device (rate is 5 min avg) To Peer (rate is 5 min avg)

----------------------------- ---------------------------- Rate Total Rate Total MB/s Bytes MB/s Bytes

------------------------------------------------------------------------------ioa1/1 0.56 24049257618 109.66 4698262901274

sjc-sw2# show ioa int int ioa 2/1 summary

---- ----------------------- ---- ------------- ---- --FLOW HOST VSAN STATUS COMP ACC

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-21

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

TARGET

---- ----------------------- ---- ------------- ---- --1 10:00:00:00:00:00:03:00 200 ACTIVE YES WA 11:00:00:00:00:00:03:00 2 10:00:00:00:00:00:02:00 200 ACTIVE NO WA 11:00:00:00:00:00:02:00 3 10:00:00:00:00:00:01:00 100 ACTIVE YES TA 11:00:00:00:00:00:01:00 4 10:00:00:00:00:00:00:00 100 ACTIVE NO TA 11:00:00:00:00:00:00:00

sjc-sw2# show ioa int int ioa 2/1 stats Adapter Layer Stats 4457312829 device packets in, 376008035 device packets out 8954596919462 device bytes in, 24064514554 device bytes out 526927441 peer packets in, 2473105321 peer packets out 45230025550 peer bytes in, 4701244024682 peer bytes out

8 i-t create request, 4 i-t create destroy 8 i-t activate request, 0 i-t deactivate request 0 i-t create error, 0 i-t destroy error 0 i-t activate error, 0 i-t deactivate error 48 i-t-n not found, 0 i-t-n stale logo timer expiry 4 logo sent, 8 logo timer started 4 logo timer fired, 4 logo timer cancelled 4 plogi 4 plogi-acc 4 logo-acc 4 prli 4 prli-acc 0 els-q-err to-device 214279940 orig pkts 12743547488 orig bytes to-peer 8748538 orig pkts 682386268 orig bytes 0 queued 0 flushed 0 discarded LRTP Stats 0 retransmitted pkts, 0 flow control 2464072014 app sent 2464072014 frags sent 0 tx wait 0 rexmt bulk attempts 0 rexmt bulk pkts 2 delayed acks 376008013 in-order 0 reass-order 0 reass-wait 0 dup-drop 376008013 app deliver 376008013 frags rcvd 150919428 pure acks rx 376008013 data pkts rx 0 old data pkts 0 remove reass node, 0 cleanup reass table Tape Accelerator statistics 2 Host Tape Sessions 0 Target Tape Sessions Host End statistics Received 26275926 writes, 26275920 good status, 2 bad status Sent 26275914 proxy status, 10 not proxied Estimated Write buffer 4 writes 524288 bytes Received 0 reads, 0 status Sent 0 cached reads Read buffer 0 reads, 0 bytes Host End error recovery statistics Sent REC 0, received 0 ACCs, 0 Rejects Sent ABTS 0, received 0 ACCs Received 0 RECs, sent 0 ACCs, 0 Rejects Received 0 SRRs, sent 0 ACCs, 0 Rejects Received 0 TMF commands Target End statistics Received 0 writes, 0 good status, 0 bad status Write Buffer 0 writes, 0 bytes Received 0 reads, 0 good status, 0 bad status Sent 0 reads, received 0 good status, 0 bad status Sent 0 rewinds, received 0 good status, 0 bad status Estimated Read buffer 0 reads, 0 bytes Target End error recovery statistics Sent REC 0, received 0 ACCs, 0 Rejects Sent SRR 0, received 0 ACCs Sent ABTS 0, received 0 ACCs

4-22

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

Received 0 TMF commands Write Accelerator statistics Received 726357548 frames, Sent 529605035 frames 0 frames dropped, 0 CRC errors 0 rejected due to table full, 0 scsi busy 0 ABTS sent, 0 ABTS received 0 tunnel synchronization errors Host End statistics Received 188004026 writes, 188004000 XFER_RDY Sent 188004026 proxy XFER_RDY, 0 not proxied Estimated Write buffer 1146880 bytes Timed out 0 exchanges, 0 writes Target End statistics Received 0 writes, 0 XFER_RDY Write buffer 0 bytes TCP flow control 0 times, 0 bytes current Timed out 0 exchanges, 0 writes Compression Statistics Pre Comp Batch size 131072 Post Comp Batch size 2048 4375494911078 input bytes, 50140348947 output compressed bytes 0 non-compressed bytes, 0 incompressible bytes 0 compression errors 0 Compression Ratio De-Compression Statistics 0 input bytes, 0 output decompressed bytes 11883488326 non-compressed bytes 0 de-compression errors

sjc-sw2# show ioa int int ioa 2/1 init-pwwn 10:00:00:00:00:00:03:00 targ-pwwn

11:00:00:00:00:00:03:00 vsan 200 counters

Adapter Layer Stats 1366529601 device packets in, 160768174 device packets out 2699458644986 device bytes in, 10289163140 device bytes out 160844041 peer packets in, 165188790 peer packets out 18652597246 peer bytes in, 47736122724 peer bytes out

0 i-t create request, 0 i-t create destroy 0 i-t activate request, 0 i-t deactivate request 0 i-t create error, 0 i-t destroy error 0 i-t activate error, 0 i-t deactivate error 0 i-t-n not found, 0 i-t-n stale logo timer expiry 1 logo sent, 2 logo timer started 1 logo timer fired, 1 logo timer cancelled 1 plogi 1 plogi-acc 1 logo-acc 1 prli 1 prli-acc 0 els-q-err to-device 80384094 orig pkts 4662277452 orig bytes to-peer 0 orig pkts 0 orig bytes 0 queued 0 flushed 0 discarded LRTP Stats 0 retransmitted pkts, 0 flow control 160768190 app sent 160768190 frags sent 0 tx wait 0 rexmt bulk attempts 0 rexmt bulk pkts 1 delayed acks 160768162 in-order 0 reass-order 0 reass-wait 0 dup-drop 160768162 app deliver 160768162 frags rcvd 75879 pure acks rx 160768162 data pkts rx 0 old data pkts 0 remove reass node, 0 cleanup reass table Write Accelerator statistics Received 1607681842 frames, Sent 1527297774 frames 0 frames dropped, 0 CRC errors 0 rejected due to table full, 0 scsi busy 0 ABTS sent, 0 ABTS received 0 tunnel synchronization errors Host End statistics Received 80384094 writes, 80384082 XFER_RDY

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

4-23

Chapter 4 Configuring IOA Using the CLI

Additional Configurations

Send documentation comments to mdsfeedback-doc@cisco.com

Sent 80384094 proxy XFER_RDY, 0 not proxied Estimated Write buffer 524288 bytes Timed out 0 exchanges, 0 writes Target End statistics Received 0 writes, 0 XFER_RDY Write buffer 0 bytes TCP flow control 0 times, 0 bytes current Timed out 0 exchanges, 0 writes

sjc-sw2# show ioa int int ioa 2/1 init-pwwn 10:00:00:00:00:00:03:00 targ-pwwn

11:00:00:00:00:00:03:00 vsan 200 counters brief

------------------------------------------------------------------------------Interface Input (rate is 5 min avg) Output (rate is 5 min avg)

----------------------------- ---------------------------- Rate Total Rate Total MB/s Frames MB/s Frames

------------------------------------------------------------------------------ioa1/1 Device 60 9573683 0 1126308 Peer 0 1126833 1 1157161 sjc-sw2#

4-24

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Send documentation comments to mdsfeedback-doc@cisco.com

Configuring IOA Using Fabric Manager

This chapter describes how to configure I/O Accelerator (IOA) using Fabric Manager. This chapter contains the following sections:

• IOA Manager, page 5-1

• Launching IOA Manager, page 5-3

• Configuring Clusters, page 5-7

• Configuring Interfaces, page 5-11

• Configuring Flows, page 5-13

IOA Manager

CHAPTER

The IOA Manager is a graphical user interface (GUI) for configuring and managing IOA. The IOA Manager user interface consists of a navigation pane on the left that displays a hierarchy and an information pane on the right that displays t he contents of th e item that you click in the na vig ation pane. The hierarchy is a tree structure that contains elements that you can configure with IO A Manager. It also consists of a toolbar for quick access to the most commonly used options and a Fabric drop-down list box. The Fabric drop-down list box allows you to directly access the fabrics managed by Fabric Manager . The Fabric drop-down list box will be available only if more than one fabric is open.

Note Fabric Manager Client standalone supports IOA Manager from Release 5.0(1a).

Note When you perform some of the time-consuming configuration activities using IOA Manager, the

progress bar indicates that the configuration actions are in progress. You need to wait until the action is complete. You can click Stop to cancel the action. However, stopping the action may not roll back the transactions that were executed.

Figure 5-1 shows the IOA Manager interface.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-1

Chapter 5 Configuring IOA Using Fabric Manager

IOA Manager

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-1 IOA Manager Main Window

Toolbar

The IOA Manager main toolbar provides icons for accessing the most commonly used operations as shown in

Table 5-1 I/O Accelerator Toolbar

Table 5-1.

Icon Description

Applies the changes.

Refreshes the window.

Adds a cluster or interface.

Deletes an existing entry.

Displays a real-time chart of the selected switch.

5-2

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 5 Configuring IOA Using Fabric Manager

Launching IOA Manager

Send documentation comments to mdsfeedback-doc@cisco.com

Launching IOA Manager

To launch IOA Manager, follow these steps:

Step 1 Choose Tools > I/O Acceleration.

You see the Fabric Manager main window as shown in Figure 5-2.

Figure 5-2 Fabric Manager Window

Note When you select IOA Manager, it opens the tree for the fabric that is selected. If t here is no activ e

fabric, IOA Manager launches with the first fabric in the tree.

Configuring Sites

A site is described as a named set of switches. You can click the sites node to view the list of defined sites. There are two tables in the information pane: one for the assigned switches on the top and the another one for unassigned switches below the assigned switches table. You can click the name of the site to display the details in t he inform ation p ane. Only active sites can be used for creating a clusters.

Adding a New Site

To create a new site using IOA Manager, follow these steps:

Step 1 Select Sites in the navigation pane.

You see the IOA Manager window as shown in Figure 5-3.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-3

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Sites

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-3 IOA Manager

Step 2 Click the Add icon on the toolbar.

You see the site name dialog box as shown in Figure 5-4.

Figure 5-4 Site Name Dialog Box

Step 3 Enter the site name and then click OK.

You see the select switch dialog box as s hown in Figure 5-5.

Figure 5-5 Select Switch Dialog Box

Step 4 Select a switch from the drop-down list box and then click OK. Step 5 Click OK in the dialog box to confirm that you have successfuly created the site.

Removing a Site

To remove a site using IOA Manager, follow these steps:

Step 1 In the navigation pane, click the name of the site you want to delete.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-4

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Sites

Send documentation comments to mdsfeedback-doc@cisco.com

You see the IOA Manager window as shown in Figure 5-6.

Figure 5-6 IOA Manager Window

Step 2 Click the Rem ove icon on the toolbar.

Step 3 Click Yes to confirm that you want to remove the site.

Viewing a Site

Step 1 In the navigation pane, click Sites.

You see the confirmation dialog box in as shown in Figure 5-7.

Figure 5-7 Delete Confirmation Dialog Box

To view a site using IOA Manager, follow these steps:

You see the IOA Manager window as shown in Figure 5-8.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-5

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Sites

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-8 Viewing Sites Using IOA Manager

Step 2 Expand the sites in the hierarchy. Step 3 Click the name of the site to view the details in the information pane.

You see the site details as shown in Figure 5-9.

Figure 5-9 Viewing Site Details Using IOA Manager

Adding Switches to a Site

To add a switch to a site, follow these steps:

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-6

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Clusters

Send documentation comments to mdsfeedback-doc@cisco.com

Step 1 In the navigation pane, click Sites. Step 2 Select the switches that you want to add from the Unassigned Switches table. Step 3 Click Add, and then click Apply.

Removing Switches from a Site

To remove a switch from a site, follow these steps:

Step 1 In the navigation pane, click Sites.

You see the IOA Manager window as shown in Figure 5-10.

Figure 5-10 Removing Switches from a Site Using IOA Manager

Step 2 Click to select the switches you want to remove from Assigned Switches table. Step 3 Click Rem ove , and then click Apply.

Configuring Clusters

You can select a cluster to see the details in the information pane. The upper table in the information pane displays the members of a named c luster, and the table below displays the statistical information about the cluster’s active IOA interfaces.

Adding a New Cluster

To create a new cluster using IOA Manager, follow these steps:

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-7

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Clusters

Send documentation comments to mdsfeedback-doc@cisco.com

Step 1 Select Cluster in the navigation pane and then click the Add icon on the toolbar.

You see the IOA Manager window as shown in Figure 5-11.

Figure 5-11 IOA Manager - Add Clusters

Step 2 Enter the Cluster name, and then click OK.

You see the add Cluster name dialog box as shown in Figure 5-12.

Figure 5-12 Add Cluster Name Dialog box

Step 3 Enter the Cluster name and then click OK.

You see the select switch dialog box as s hown in Figure 5-13.

Figure 5-13 Select Switch Dialog Box

Step 4 Select a switch from the drop-down list, and then click OK.

5-8

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Clusters

Send documentation comments to mdsfeedback-doc@cisco.com

Note You need to select a switch that you would like it to be the master switch as the seed switch when

you create the IOA cluster. If you have multiple switches in a site, you may add all the switches in a site that you would like to manage from to the cluster before adding the switches from the remote site.

You see a message box upon successfully creating a cluster as shown in Figure 5-14.

Figure 5-14 Message Box

Step 5 Click OK.

Note If the master switch that you selected is not a member of the site, you may either need to ad d the switch

to an existing site or to create a new site.

Removing a Cluster

To remove a site using IOA Manager, follow these steps:

Step 1 In the navigation pane, click the name of the cluster that you want to delete.

You see the IOA Manager window as shown in Figure 5-15.

Figure 5-15 Removing a Cluster Using IOA Manager

Step 2 Click the Rem ove icon on the toolbar.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-9

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Clusters

Send documentation comments to mdsfeedback-doc@cisco.com

You see the Delete confirmation dialog box as shown in Figure 5-16.

Figure 5-16 Remove Confirmation Dialog Box

Step 3 Click Yes to remove the cluster.

Viewing Clusters

To view a cluster using IOA Manager, follow these steps:

Step 1 Click clusters in the navigation pane.

You see the IOA Manager window with clusters selected as shown in Figure 5-17.

Figure 5-17 Viewing Clusters Using IOA Manager

Step 2 Expand the cluster in the hierarchy. Step 3 Click the name of the cluster to view the details in the information pane.

You see the IOA Manager window with the cluster details as shown in Figure 5-18.

5-10

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Interfaces

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-18 Viewing Cluster Details

Configuring Interfaces

Y ou can select the interfaces in a named cluster to see the details in the information pane. The upper table in the information pane displays informat ion about active and configured IO A interface pairs associated with the cluster. The lower table in the information pane displays information about IOA interface candidates that are ready for use in the cluster.

Assigning Interfaces to a Cluster

To add a new interface to a cluster using IOA Manager, follow these steps:

Step 1 Expand the cluster node in the navigation pane and click Interfaces.

You see the IOA Manager window as shown in Figure 5-19.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-11

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Interfaces

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-19 Adding Interfaces Using IOA Manager

The information pane displays the Assigned Interfaces and Unassigned Interfaces tabs.

Step 2 Select one or more interfaces from the Unassigned Interfaces table in the information pane and then click

Add.

Step 3 Click Apply to apply changes.

Note Y ou can change the admin istrative status of an assigned interface by selecting up or down from the admin

status drop-down list box and then click Apply.

Note Fabric Manager denotes all the candidate service engines that are not currently provisioned for any

service as unconfigured in the unassigned interfaces table. When you select these interfaces, it will automatically provision these service engines for IOA, and configure them as a part of this IOA cluster.

Removing Interfaces from a Cluster

To remove an interface from a cluster, follow these steps:

Step 1 Expand the cluster node in the navigation pane and click Interfaces.

You see the IOA Manager window as shown in Figure 5-20.

5-12

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Flows

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-20 Removing Interfaces Using IOA Manager

Step 2 Select the switches from the Assigned Interfaces table that you want to remove. Step 3 Click Rem ove to move the switches to Unassigned Interfaces table. Step 4 Click Apply.

Configuring Flows

You can select the flows in a named cluster to see the details in the information pane. The upper table in the information pane displays information on active IOA flows. The lower table in the information pane displays information on cand idate IOA flows.

Adding a Flow

To add a flow in the cluster using IOA Manager, follow these steps:

Step 1 Expand the Cluster node in the navigation pane and then click Flows.

You see the IOA Manager window displaying the Assigned Flows and Unassigned Flows as shown in

Figure 5-21.

Note If IVR zoneset is activated, Fabric Manager will automatically consider the IVR zoneset and list the

candidate IVR flows in the Unassigned flows section.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-13

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Flows

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-21 Adding Flows Using IOA Manager

Step 2 Check the Click Show All Zoned Flow Candidates check box to display all the zoned members. Step 3 Select one or more switches from the Unassigned Flows in the information pane and then click Add.

You see the Ad d Flows dialog box as shown in Figure 5-22.

Figure 5-22 Flow Configuration Dialog Box

Step 4 Enter a flow group name. Step 5 Check the Enable Com pression check box to enable compression. Step 6 Check the Enable Tape Acceleration check box to enable tape acceleration.

Note Write accleration is enabled by default.

5-14

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Flows

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-23 Configure Flo w Di alog Box

Step 7 Click the arrow icon to configure the flow in this direction. Step 8 (Optional) Check t he Use this directon for the rest of the Flow group check box to apply the same

direction to rest of the flow group.

Note You may use this step only if some of the N ports are registered as both initiators and targets,

especially in cases of remote replication flow.

Step 9 Click Add and then click Apply.

Removing a Flow

To add a flow in the cluster using IOA Manager, follow these steps:

Step 1 Expand the Cluster node in the navigation pane and then click Flows.

You see the IOA Manager window displaying the Assigned Flows and Unassigned Flows as shown in

Figure 5-24.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-15

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Flows

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-24 Removing Flows Using IOA Manager

Step 2 Select one or more switches from the Assigned Flows in the information pane and then click Remove. Step 3 Click Apply.

Viewing Interface Statistics

To view real-time charts using IOA Manager, follow these steps:

Step 1 Expand the Cluster node in the navigation pane and click the name of the cluster. Step 2 Select a switch from the Interfaces Statistics table in the information pane.

You will see the IOA Manager window as shown in Figure 5-25.

5-16

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Flows

Send documentation comments to mdsfeedback-doc@cisco.com

Figure 5-25 Select IOA Manager Real-time Chart

Step 3 Click the chart icon on the toolbar to monitor real-time charts.

You see the chart as shown in Figure 5-26.

Figure 5-26 IOA Manager Real-time Chart

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

5-17

Chapter 5 Configuring IOA Using Fabric Manager

Configuring Flows

Send documentation comments to mdsfeedback-doc@cisco.com

5-18

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Send documentation comments to mdsfeedback-doc@cisco.com

SCSI Write Acceleration and Tape Acceleration

This appendix describes the concepts of SCSI write acceleration, tape acceleration, and compression. This appendix includes the following sections:

• SCSI Write Acceleration, page A-1

• SCSI Tape Acceleration, page A-2

SCSI Write Acceleration

The SCSI write acceleration feature enables you to significantly improve application write pe rformance when storage traffic is routed over wide area networks using FCIP or Fibre Channel. When write acceleration is enabled, WAN throughput is maximized by minimizing the impact of WAN latency for write operations.

In Figure A-1, the WRITE command without write accelerati on requires two round-trip transfers (RTT), while the WRITE command with write acceleration only requires one R TT . The maximu m sized Transfer Ready is sent from the host side of the FCIP or Fibre Channel link back to the host before the WRITE command reaches the target. This enables the host to start sending the write data withou t waiting fo r the long latency over the FCIP or Fibre Channel link of the WRITE command and Transfer Ready. It also eliminates the delay caused by multiple Transfer Readys needed for the exchange going over the FCIP or Fibre Channel link.

APPENDIX

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

A-1

Appendix A SCSI Write Acceleration and Tape Acceleration

FCFC

FCIP over

WAN

Initiator MDS 9000 MDS 9000 Target

Transfer ready

Command

Data transfer

Status

Without acceleration

RTT1

RT2

FCFC

FCIP over

WAN

Initiator MDS 9000 MDS 9000 Target

With acceleration

SCSI Tape Acceleration

Send documentation comments to mdsfeedback-doc@cisco.com

Figure A-1 SCSI Write Acceleration

SCSI Tape Acceleration

T apes are storag e devices that store and retrie ve user data sequentially. Cisco MDS NX-OS provides both tape write and read acceleration.

Applications that access tape drives normally have only one SCSI WRITE or READ operation outstanding to it. This single command process limits the benefit of the tape acceleration feature when using an FCIP or FC tunnel over a long-distance WAN link. It impacts backup, restore, and restore performance because each SCSI WRITE or READ operation does not complete until the host receives a good status response from the tape drive. The SCSI tape acceleration feature helps solve this problem. It improves tape backup, archive, and restore operations by allowing faster data streaming between the host and tape drive over the WAN link.

In an example of tape acceleration for write operations, the backup server in Figure A-2 issues write operations to a drive in the tape library. Acting as a proxy for the remote tape drives, the local Cisco MDS switch proxies a transfer ready to signal the host to start sending data. After recei ving all the data, the local Cisco MDS switch proxies the successful completion of the SCSI WRITE operation. This

A-2

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Appendix A SCSI Write Acceleration and Tape Acceleration

FCFC

Backup

Server

MDS with

IPS

MDS with

IPS

Tape

Drive

Write Command 1

Write Command N

Status 1 Status 1

Status N

WAN

WRITE FILEMARKS status

WRITE FILEMARKS operation

120492

SCSI Tape Acceleration

Send documentation comments to mdsfeedback-doc@cisco.com

response allows the host to start the next SCSI WRITE operation. This proxy method results in more data being sent over the FCIP or Fibre Channel tunnel in the same time period compared to the time taken to send data without proxying. The proxy method improves the performance on WAN links.

Figure A-2 SCSI Tape Acceleration for Write Operations

At the tape end of the FCIP or Fibre Channel tunnel, another Cisco MDS switch buffers the command and data it has received. It then acts as a backup server to the tape drive by listening to a transfer ready from the tape drive before forwarding the data.

The Cisco NX-OS provides reliable data delivery across the WAN. It maintains write data integrity by allowing the WRITE FILEMARKS operation to complete end-to-end without proxying. The WRITE FILEMARKS operation signals the synchronization of the buffer data with the tape library data. While tape media errors are returned to backup servers for error handling, tape busy errors are retried automatically by the Cisco NX-OS software.

In an example of tape acceleration for read operations, the restore server in Figure A-3 issues read operations to a drive in the tape lib rary. During the restore process, the remote Cisco MDS switch at the tape end, in anticipation of more SCSI read operations from the host, sends out SCSI read operations on its own to the tape drive. The prefetched read data is cached at the local Cisco MDS switch. The local Cisco MDS switch on receiving SCSI read operations from the host, sends out the cached data. This method results in more data being sent over the FCIP or FC tunnel in the same time period compared to the time taken to send data without read acceleration for tapes. This improves the performance for tape reads on WAN links.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

A-3

Appendix A SCSI Write Acceleration and Tape Acceleration

FCFC

Restore

Server

MDS with

IPS

MDS with

IPS

Tape

Drive

WAN

144886

Read data N

Read data N+1

Status N

Status N+1

Read command N

Read command N+1

Read command N+2

Read data N

Status N

Status N+1

SCSI Tape Acceleration

Send documentation comments to mdsfeedback-doc@cisco.com

Figure A-3 SCSI Tape Acceleration for Read Operations

The Cisco NX-OS provides reliable data delivery across the WAN. While tape media errors during the read operation are returned to the restore server for error handling, the Cisco NX-OS software recovers from any other errors.

In tape acceleration for writes, after a certain amount of data has been buffered at the remote Cisco MDS switch, the write operations from th e host are flow controlled by the local Cisco MDS switch by not proxying the Transfer Ready. On completion of a write operation when some data buffers are freed, the local Cisco MDS switch resumes the proxying. Likewise, in tape acceleration for reads, after a certain amount of data has been buffered at the local Cisco MDS switch, the read operations to the tape drive are flow controlled b y th e remote Cisco MDS swi tch by not issuing any further reads. On comp letion of a read operation, when some data buffers are freed, the remote Cisco MDS swit ch resumes issuing r eads.

The default flow control buffering uses the automatic option. This option takes the WAN latencies and the speed of the tape into account to provide optimum performance. You can also specify a flow control buffer size (the maximum buffer size is 12 MB).

A-4

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Send documentation comments to mdsfeedback-doc@cisco.com

APPENDIX

Cluster Management and Recovery Scenarios

This appendix includes information on cluster management and reco v ery procedur es that ar e used whe n one or more switches in a Cisco IOA cluster is offline or when you want to change the master switch assignment from one switch to another switch.

Note The procedures in this appendix describe troubleshooting solutions that use the CLI.

Note The Cisco IOA cluster conf iguration for an of fline switch must be done u sing the CLI. Cisco IO A cluster

configuration for an online switch can be done using Fabric Manager or the CLI.

This appendix includes the following sections;

• Cluster Quorum and Master Switch Election, page B-1

• In-Service Software Upgrade (ISSU) in a Two-Node Cluster, page B-4

• Supported Topologies, page B-5

• Cluster Recovery Scenarios, page B-5

Cluster Quorum and Master Switch Election

This section describes the Cisco IO A cluster quorum and the process for electing the master switch in a cluster.

Node ID

Every switch in a cluster has a node ID. Cisco IOA assigns a node ID to every new switch as it is added to the cluster. The switch where the cluster is created is assigned the node ID of 1. This is the master switch. When a new switch is added to the cluster, it is assigned the next available higher node ID. For example, when a second switch is added to the cluster it gets the node ID of 2 and the third switch gets the node ID of 3, and so on.

Cluster View

The cluster view is the set of switches that are part of the operational cluster.

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

B-1

Appendix B Cluster Management and Recovery Scenarios

Cluster Quorum and Master Switch Election

Send documentation comments to mdsfeedback-doc@cisco.com

Cluster Quorum

For a cluster to be operational, it must include more than half the number of configured switches in the cluster view. In an N-node cluster, N/2 + 1 nodes form a cluster quorum.

If N is even, the cluster quorum requires N/2 nodes and also, the presence of the switch with the lowest node ID.

The quorum logic ensures that in the event of cluster partitions at least one partition can be operational. All other switches are nonoperational. This guarantees the consistency of the cluster.

Master Switch Election

When a cluster is created, the switch on which the cluster is created becomes the cluster master switch. When the master switch fails or is rebooted, another switch takes over as the master switch. The master election logic uses the node ID and the latest cluster configuration to determine which switch in the cluster will become the master switch. The master election logic is described as follows:

• If the master switch fails in an op erational cluster , the switch with the ne xt lowest no de ID takes over

as the master switch. Note that in an operational cluster, all the switches run the same cluster configuration.

–

When the previous master switch comes back online and joins the cluster, it does not immediately become the master.

• When all the switches of a cluster are coming up, the switch that has the latest cluster configuration

becomes the master switch. If there are multiple switches with the same configuration, the switch with the lowest node ID is chosen to be the master switch.

–

Once a master switch is chosen and the cluster is operational (there is a quorum), even if a switch with a lower node ID joins the cluster at a later time, the master switch does not change.

For example, there are three switches S1, S2, and S3 with node IDs 1, 2, and 3, respectively. If switches S2 and S3 form a quorum then switch S2 becomes the master switch. Even if switch S1 with the node ID of 1 comes up and joins the cluster at a later time, switch S2 continues to be the master. However, if switch S2 goes down for any reason, switch S1 will become the master switch.

Two-Switch Cluster Scenarios

According to the cluster quorum logic, a cluster with two configured switches can be operational if both switches are operational or the switch with the lowest node ID is operational.

In the latter case, the switch with the lowest node ID is the master of the one-switch cluster. The other switch could have failed or simply lost connectivity to the operational switch. In either case, the switch with the higher node ID would become nonoperational. If the node with the lower node ID failed, the other switch cannot form an operational cluster.

The examples that follow describe these scenarios. The first three examples consider single switch failures.

1. Assume that in a two-switch cluster with switches S1 (node ID 1) and S2 (node ID 2), S1 is the

master (the master has the lower node ID).

B-2

When the switches lose connectivity between them, the master switch S1 continues to be operational since it has the lower node ID and can form an (N/2) switch cluster. Switch S2 becomes nonoperational.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Appendix B Cluster Management and Recovery Scenarios

Cluster Quorum and Master Switch Election

Send documentation comments to mdsfeedback-doc@cisco.com

2. Assume that in a two-switch cluster with switches S1 (node ID 1) and S2 (node ID 2), S2 is the

master (note that the master has the higher node ID because it has the latest configuration when both the switches came online).

When the switches lose connectivity between them, switch S2 becomes nonoperational and S1 takes over as the master to form a 1-switch cluster. This is consistent with the quorum logic in a two-switch cluster (N/2 with lowest node ID).

3. Assume that in a two-switch cluster with switches S1 (node ID 1) and S2 (node ID 2). If S1 fails

(regardless of which switch was the master), S2 will also become non-operational as long as S1 is down.

When S1 comes up, S1 and S2 will form a two-switch cluster.

The next set of examples describe reboots of both switches (S1 with node ID 1 and S2 with node ID 2):

Caution If you perform any configuration change on a cluster, you must save the running configuration to the

startup configuration by entering the copy running-config startup-conf ig CLI command on all switches before rebooting them. Otherwise, the cluster may not form correctly after the reboot (see example 3.).

1. After a reboot, if both switches S1 and S2 come up about the same time, a two-switch cluster will

be formed.

a. If the cluster configurations are the same, S1 (with the lower node ID) will become the master. b. If the cluster configurations are different, the switch with the latest cluster configuration will

become the master.

2. After a reboot, if switch S2 comes up first, it will not be able to form a cluster until S1 also comes

up. After that, the algorithm explained in the previous case will be used.

3. After a reboot, if switch S1 comes up first, it will form a one-switch cluster (N/2 with lowest node

ID). When S2 comes up, it will join the cluster to form a two-switch cluster. When S2 comes up and if it happens to have the latest cluster configuration in the startup

configuration (this can happen if you did not save the running configuration to the startup configuration on S1 but did so on S2), it will not be able to join the cluster formed by S1.

Caution It is critical that you save the running configuration on all switches before a reboot.

Three-Switch Cluster Scenarios

In a three-switch cluster, the quorum requires two switches to be in the cluster view (N/2 + 1). The examples below explain three scenarios in a three-switch cluster with switches S1 (node ID 1), S2 (node ID 2) and S3 (node ID 3). S1 is the master switch.

1. In a three-switch operational cluster, if switch S3 fails or loses connectivity with the other two

switches, then S3 becomes nonoperational. Switches S1 and S2 will form an operational cluster. When S3 comes up again, it will rejoin the cluster.

2. In a three-swi tch operational cluster , if the master switch S1 fails or lo ses connectivity with t he other

two switches, then S1 becomes nonoperational. Switches S2 and S3 wi ll form an operational cluster and S2 will be the master. When S1 comes up again, it will rejoin the cluster. Note that S2 will continue to be the master.

3. If two switches fail, the cluster will become nonoperational.

These examples describe reboots on all switches in the cluster:

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

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

B-3

Appendix B Cluster Management and Recovery Scenarios

In-Service Software Upgrade (ISSU) in a Two-Node Cluster

Send documentation comments to mdsfeedback-doc@cisco.com

Caution If you perform any configuration change on a cluster, you must save the running configuration to the

startup configuration by entering the copy running-config startup-config command on all switches before rebooting them. Otherwise, the cluster may not form correctly after the reboot.

1. After a reboot, if all swit ches come up at about the same time, fir st a 2-switch cluster will be formed

and later the third switch will be added.

a. If the cluster configurations are the same, S1 (with the lower node ID) will become the master

switch and form the 2-switch cluster first; and then add the third switch.

b. If the cluster configurations are different, the switch that is running the latest configuration will

become the master switch and then form a 2-switch cluster; and then add the third switch.

2. After a reboot, if the switches come up one at a time, a 2-switch cluster will be formed after the first

two switches are up. Later, when the third switch comes online, it will join the cluster. If the third switch happens to be running th e latest cluster conf i guration in the startup config uration

(this can happen if you save th e runnin g conf ig uration onl y on this swi tch b ut not on th e other two ), the third switch will not be able to join the cluster.

Caution It is critical that you save the running configuration on all switches before a reboot.

Four-Switch Cluster Scenarios

The four-switch cluster scenario is very si milar to the e xamples abov e. The clust er will be operational if the cluster view has at least three switches (N/2 + 1), or if the cluster view has two switches including the switch with the lowest node ID (N/2 with lowest node ID).

In-Service Software Upgrade (ISSU) in a Two-Node Cluster

In-Service Software Upgrade (ISSU) is a comprehensive, transparent software upgrade application that allows you to deploy bug fixes and add new features and services without any disruption to the traffic.

In a cluster comprising of the MDS 9222i Switches as nodes, if the nodes are not able to communicate, then the node having the lowest node identifier (node ID) remains in the cluster while the other node leaves the cluster. However, w hen an ISSU is performed on a node having the lowest node identifier, a complete loss of the cluster results because both the nodes leave the cluster.

This undesirable situation is addressed in a two-node cluster as follows:

• The upgrading node sends a message to the other node of the intent to leave the cluster. The

upgrading node can either be a master node or a slave node.

• The remaining node remains in the cluster and performs the role of the master node if it was a slave

node. This node continues to remain in the cluster with the quorum intact.

• After the ISSU is completed and the switches boot up, the upgraded node rejoins the cluster as a

slave node.

B-4

Note This feature is tied to ISSU logic and no additional commands need to be executed.

Cisco MDS 9000 Family I/O Accelerator Configuration Guide

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

Cisco MDS 9000 series Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

CONTENTS

New and Changed Information

Preface

Audience

Organization

Document Conventions

Related Documentation

Release Notes

Regulatory Compliance and Safety Information

Compatibility Information

Hardware Installation

Software Installation and Upgrade

Cisco NX-OS

Cisco Fabric Manager

Command-Line Interface

Intelligent Storage Networking Services Configuration Guides

Troubleshooting and Reference

Obtaining Documentation and Submitting a Service Request

Overview

About Cisco I/O Accelerator

Unified Acceleration Service

Topology Independent

Transport Agnostic

High Availability and Resiliency

Improved Tape Acceleration Performance

Load Balancing

Example IOA Topology

Terminology

Clustering

Hardware Requirements

Software Requirements

License Requirements

Getting Started

Enabling SSH

Enabling CFS

IP Access Lists

Zone Default Policy

FC-Redirect

FC-Redirect Unsupported Switches

FC-Redirect Requirements

Configuring FC-Redirect v2 Mode

Using FC-Redirect with CFS Regions

Guidelines for Designing CFS Regions For FC-Redirect

Using IOA Cluster with IPFC Interface

Configuring CFS Regions For FC-Redirect

Task Flow for Configuring IOA Cluster To Use the IPFC Interface

Configuring IOA Cluster To Use the IPFC Interface

Creating a VSAN Interface and Configuring IPv4 Addresses

Enabling IPv4 Routing

Verifying Connectivity

Creating IOA cluster and IOA interface in the Local Node

Verifying Cluster Configuration

Adding a Remote Node and IOA Interface to the Remote Node

Verifying the Cluster Configuration

Configuration Example

Creating an Interface VSAN

Verifying the Configuration

Verifying the Connectivity

Configuring IOA Site on Switch sw-231-14

Configuring IOA Site on Switch sw-231-19

Configuring IOA Cluster cltr1 on Switch sw-231-14

Changing the Node to Use IPFC Interface Address

Adding a Remote Node to the IOA Cluster

Adding an IOA Interface to the Switch sw-231-14

Adding an IOA Interface to the Switch sw-231-19

Verifying the Cluster Configuration

Verifying the IP Address

Verifying the IOA Interface

Task Flow for Converting an Existing IOA Cluster to use IPFC interface

Configuration Example for Converting IOA Cluster to Use the IPFC interface

Verifying the IOA Cluster Configuration

Verifying the IP Address

Verifying the Flow Status

Shutting Down IOA Cluster on a Local Node

Shutting Down the IOA cluster on the remote node

Removing the IOA Cluster from the Remote Node