Sie sind auf Seite 1von 64
Brocade Multiprotocol Routing Services Solution Guide Meta SAN Tape Consolidation Version 1.0 Publication Number:

Brocade Multiprotocol Routing Services Solution Guide

Meta SAN Tape Consolidation

Version 1.0

Publication Number: 53-0000489-01 Publication Date: March 01, 2004

Copyright © 2004, Brocade Communications Systems, Incorporated.

Publication Number: 53-0000489-01

Brocade, the Brocade B weave logo, Secure Fabric OS, and SilkWorm are registered trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered trademark of IBM Corporation in the U.S. and other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.

ALL RIGHTS RESERVED.

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.

Notice: The product described by this document may contain “open source” software covered by the GNU General Public License or other open source license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

Export of technical data contained in this document may require an export license from the United States Government.

Brocade Communications Systems, Incorporated

Corporate Headquarters 1745 Technology Drive San Jose, CA 95110 T: (408) 487-8000 F: (408) 487-8101 Email: info@brocade.com

Asia-Pacific Headquarters 9/F, One International Finance Center, 1 Harbour View Street, Central, Hong Kong Tel: +852 2539 0600 Fax: +852 2539 0613 Email: apac-info@brocade.com

European Headquarters 29, route de l’Aeroport Case Postale 105 CH-1211 Geneva 15, Switzerland T: +41 22 799 56 40 F: +41 22 799 56 41 Email: europe-info@brocade.com

Latin America Headquarters 5201 Blue Lagoon Drive Miami, FL 33126 T: (305) 716-4165 Email: latinam-sales@brocade.com

Document History

The table below lists all versions of Meta SAN Tape Consolidation.

Document version

Publication Number

Publication Date

Initial Release

53-0000489-01

3/01/2004

Table of Contents

Preface

 

Chapter 1

Meta SAN Tape Consolidation Overview

 

1.1.

Solution Overview

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

1-3

1.1.1.

Meta SAN Tape Consolidation Solution at a Glance

 

1-3

1.1.1.1. Assumptions

 

1.1.1.2. Step-by-Step Overview

 

Chapter 2

Solution Requirements and Design

 

2.1. Introduction

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

2-2

2.2. Meta SAN Design

 

2-3

2.3. LSAN

Design

and

Plan

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

2-4

2.4. Detailed Hardware and Software List

 

2-5

Chapter 3

Configuring the Brocade Meta SAN

 

3.1. XPATH OS Upgrade

 

3-2

3.2. Configuring FCRS on the Multiprotocol Router

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-3

 

3.2.1 FCRS Configuration Overview

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-3

3.2.2 Meta SAN Logical Connectivity

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-4

3.3.

Configuring Multiprotocol Router FCRS Tape Edge Fabric Connectivity .

3-5

3.4 Configuring FCRS for SAN 1 and SAN 2 on the Multiprotocol Router

 

3-12

 

3.4.1

SAN 1 Configuration Steps .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-12

3.4.2

SAN 2 Single Fabric FCRS Configuration

 

3-13

3.4.3.

Verifying the FCR Configuration

 

3-13

3.5.

Creating the LSAN Configuration

3-14

3.5.1. LSAN Overview

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-14

3.5.2. LSAN Detailed Configuration

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-15

3.6.

LSAN Configuration on SAN 1 Fabric A and SAN 2

3-21

3.6.1. SAN 1 Fabric A and SAN 3 LSAN Configuration Steps

 

3-21

3.6.2. SAN 2 and SAN 3 LSAN Configuration Steps

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-21

3.6.3. Verifying the Completed Meta SAN LSAN Configuration

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

3-22

Chapter 4

Installation and Setup of Veritas NetBackup

 

4.1. Preparing the Sun Solaris Hosts

 

4-2

4.2. Installing NetBackup 4.5 on Solaris

 

4-4

4.2.1. Installing NetBackup DataCenter GA on the UNIX Hosts

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-5

4.2.2. Installing Veritas NetBackup MP6 Patch on Solaris

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-6

4.2.3. Installing the Solaris Media

 

4-7

4.2.4. OPTIONAL: Configuring the SG Driver

 

4-7

4.3. Preparing the Windows Host

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-9

4.4. Installing NetBackup 4.5 on Windows 2000

 

4-11

4.4.1. Installing Veritas NetBackup MP6 Patch on Windows

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-11

4.4.2. OPTIONAL: Install Special Critical Patches

 

4-12

4.5.

Final

Setup

of NetBackup

4.5

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-13

4.5.1. Configuring the Master Server for Backups

 

4-13

4.5.2. Central Management of Media Servers

 

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-14

4.5.3. Configure the STK Tape Library On the Media Server

 

4-14

4.5.4. Viewing the NetBackup 4.5

 

4-17

4.5.5. Performing

a Test Backup.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

4-18

Preface

Warning:

This document is based upon an early release of XPath OS. The information, functionality, and guidelines

discussed are preliminary and may change in substance or form prior to GA (General Availability) of Brocade XPath

OS.

Introduction

Brocade's new SAN Routing technology extends benefits throughout the enterprise by helping to maximize the value of SANs and by providing a flexible foundation for implementing a utility computing infrastructure. The Multiprotocol Router increases SAN functionality and versatility in a single platform by delivering the following functionality:

Fibre Channel Routing Services (FCRS) for FC-to-FC routing

FCIP Tunnelling Services (FCIP) for SAN extension over distance

iSCSI Gateway Services (iSCSI) for iSCSI-to-FC protocol conversion

The objective of the Multiprotocol Router Solution Guide is to identify known working configurations and product functionality and then to communicate this information in a form so that customers can easily use the configuration examples or reasonable derivatives, avoid known issues, and successfully evaluate identified product functionality. This Solution Guide covers the planning, design, installation, configuration and implementation of Multiprotocol Router.

Solutions Using the Multiprotocol Router

Multi-protocol SAN Routing Services are deployed using the Brocade SilkWorm Multiprotocol Router, resulting in centralized management of advanced SAN functions with integrated FC routing, iSCSI, and FCIP tunneling on a single platform. The Multiprotocol Router simplifies SAN design, implementation, and management through centralization and consolidation, providing a seamless way to connect and scale across multiple SAN fabrics without the complexity of merging them into a single large fabric.

One of the benefits of SAN connectivity using the Multiprotocol Router is that SAN troubleshooting and fault isolation is simplified within smaller environments, increasing data availability. Another benefit is that there is no need to resolve zoning or naming conflicts, which shortens the consolidation process.

With the Multiprotocol Router it is possible to create logical SANs (LSANs) that enable selective connectivity between devices residing in different SAN fabrics. Selective sharing of devices using the Multiprotocol Router is useful for SANs that are geographically separated and/or managed by different organizations. Improved asset utilization can be realized by implementing the Multiprotocol Router through more efficient storage resource sharing--for example, sharing tape libraries across multiple SANs or seamlessly moving storage from a SAN that has a storage surplus to a SAN that has a storage deficit.

Those SAN administrators familiar with the Brocade SAN environment will appreciate efficient LSAN provisioning through common zoning techniques already used in Brocade SANs today. It is also now easier to interconnect and support SAN fabrics purchased from different storage vendors.

The flexibility and SAN extensibility enabled by the Silkworm Multiprotocol Router create many use case scenarios. Here are just a few use case examples for Brocade Multiprotocol Router:

SAN fabric Connectivity:

Simplify scalability to support growing SAN environments

Enable sharing of centralized resources: selective sharing or full consolidation across multiple SANs to maximize value of valuable storage resources

Ease implementation of multiple OEMs and firmware revisions through centralization and consolidation

Tape Consolidation:

Centralize backup of multiple SANs fabrics in a single location to maximize value of backup devices and resources

Increase utilization of high-end backup resources

Leverage off-peak network connectivity

Reduce management overhead requirements

Increase asset utilization

Low-cost SAN Connectivity:

Enable iSCSI-to-FC protocol conversion so lower-cost servers can utilize shared Fibre Channel storage resources

Reduce costs by eliminating the need to purchase Host Bus Adapters (HBAs) for lower-cost servers to access SAN resources

Long-distance SAN Extension For Business Continuance:

Enable remote devices to connect to SANs by using long-distance FCIP tunnelling capabilities

Reduce costs by leveraging existing IP WAN infrastructure for long-distance SAN connectivity

Audience

This Solution Guide is targeted for use by partners and end users. The technical professionals that use this guide may include storage administrators, SAN administrators, system administrators, SAN architects, systems engineers, and SAN operators that are involved with the design, deployment, and management of Brocade SANs and Multiprotocol Router solutions.

This Solution Guide is an advanced document and is very concise. Background information and supporting information for a particular topic are kept to a minimum and as appropriate, the reader is referred to supporting documentation. The reader is expected to have working experience with Brocade products. General computer system level troubleshooting skills are always important when configuring sophisticated enterprise solutions. System administration or storage administration experience is also helpful in understanding this document.

About Brocade Products Used in this Solution Guide

Brocade SilkWorm Multiprotocol Router Switch

The Brocade SilkWorm Multiprotocol Router is a 16-port switch that supports link speeds up to 2 Gbit/sec. Each port automatically negotiates to the highest common speed of all devices connected to the port. the Multiprotocol Router includes the Brocade XPath Operating System™ and is compatible with the entire Brocade SilkWorm product family. the Multiprotocol Router employs Brocade’s Inter-Switch Link (ISL) Exchange-Based Trunking to provide a high-speed data path between switches and supports an extensive list of additional features such as Fibre Channel routing, Fibre Channel over IP (FCIP), and iSCSI.

Brocade SilkWorm 3200 and 3800 Switches

The SilkWorm 3200 is an 8-port switch; the SilkWorm 3800 is a 16-port switch. Both are Fibre Channel switches support link speeds up to 2 Gbit/sec. Each port automatically negotiates to the highest common speed of all devices connected to the port. The SilkWorm 3200 and SilkWorm 3800 include the Brocade Fabric Operating System™ version 3.x, and are compatible with the entire Brocade SilkWorm product family. The SilkWorm 3200 and 3800 employ Brocade Inter-Switch Link (ISL) Trunking to provide a high-speed data path between switches.

Brocade SilkWorm 3900 Series Switches

The SilkWorm 3900 is a 32-port Fibre Channel switch that supports link speeds up to 2 Gbit/sec. Each port automatically negotiates to the highest common speed of all devices connected to the port. The SilkWorm 3900 includes the Brocade Fabric Operating System™ version 4.0.2, and is compatible with the entire Brocade SilkWorm product family. The SilkWorm 3900 employs Brocade Inter-Switch Link (ISL) Trunking to provide a high-speed data path between switches.

Brocade SilkWorm 12000 Switches

The SilkWorm 12000 is an enterprise-level Fibre Channel gigabit switch that supports link speeds up to 2 Gbit/sec. Possible configurations range from a 32-port switch to a dual 64-port switch in a single 14U enclosure. The SilkWorm 12000 employs Brocade Inter-Switch Link (ISL) Trunking to provide a high-speed data path between switches.

Brocade Fabric OS

Brocade Fabric OS is a real-time operating system that provides the core infrastructure growing businesses need to deploy scalable and robust Storage Area Networks (SANs). Fabric OS runs on the SilkWorm family of Fibre Channel switches. It supports scalable SAN fabrics that interconnect thousands of devices while ensuring high-performance data transfer among connected resources and servers. Fabric OS easily manages both large switch fabrics and Fibre Channel Arbitrated Loop (FC- AL) configurations. Moreover, Fabric OS is highly flexible, making it easy for network administrators to add functionality and scale their SANs at the speed of business.

Brocade ZONING

Brocade ZONING is a feature allowing an administrator to create segmentation or zones within a Brocade Fabric, comprised of selected storage, servers, or even workstations. It also enforces access of information to only the devices in the defined zone. Zoning ensures environmental security and enables optimization of IT resources in response to user demand and changing user profiles.

Brocade Web Tools

Web Tools provides a graphical interface that allows the administrator to monitor and manage entire fabrics and individual switches and ports from a standard workstation. It is an optionally licensed product that runs on Fabric OS. All switches in the fabric are displayed in the main window of Web Tools, including switches that do not have a Web Tools license. However, only switches that have a Web Tools license installed can be managed through Web Tools (other switches must be managed through Telnet or SES).

Brocade ISL Trunking

Brocade Inter-switch Link (ISL) Trunking is an optionally licensed product available on all Brocade 2 Gbit/sec switches. Brocade ISL Trunking is managed using telnet commands or the Brocade Web Tools interface. The Brocade ISL Trunking feature allows up to four ISLs, connections between two switches through an Expansion Port (E_Port), to merge logically into a single link. When using Brocade ISL Trunking to aggregate bandwidth of up to four ports, the speed of the ISLs between switches in a fabric is quadrupled. For example, at 2 Gbit/sec speeds, Brocade ISL Trunking delivers ISL throughput of up to 8 Gbit/sec. Brocade ISL Trunking simplifies network design and reduces the cost of storage management by optimizing bandwidth utilization and enabling load sharing of traffic at the frame-level.

References

SAN Migration Guide (53-0000360-xx)

Brocade SilkWorm, Design, Deployment, and, Management Guide (53-0000366-xx)

Designing Next-Generation Fabrics With Brocade Switches (whitepaper http://www.brocade.com)

LAN Guidelines For Brocade SilkWorm Switches (53-0000350-0x)

Exploring Brocade ISL Trunking (53-0000263-0x)

Core Switch PID Format Update Best Practices (53-0001626-0x)

Brocade Zoning User's Guide Version 3.1/4.1 (53-0000523-0x)

Zoning Implementation Strategies For Brocade San Fabrics (whitepaper http://www.brocade.com)

XPath OS Procedures Guide (53-0000607-0x)

XPath OS Reference Manual (53-0000605-0x)

SilkWorm Multiprotocol Router Hardware Reference Manual (53-0000611-0x)

Solution Guide Conventions

The formatting and conventions used in this document are designed to help the reader locate and comprehend information quickly. In addition to the information provided in standard text, there are Guidelines, Notes, and Warnings to help focus the reader on important information.

The following table describes the formatting conventions that are used in this book:

Convention

Purpose

bold text

identifies GUI elements

identifies keywords/operands

identifies text to enter at the GUI or CLI

italic text

provides emphasis

identifies variables

identifies paths and internet addresses

identifies book titles and cross references

code text

identifies commands in line with text

identifies CLI output

identifies syntax examples

Notes and Guidelines

The following notices appear in this document:

Note:

A note emphasizes important information or provides a reference to related information.

Guideline: A guideline provides a tip or a recommendation.

Warning:

Warnings alert you to potential damage to hardware, firmware, software, or data.

The red circle with a slash through it (shown below) indicates that a particular action or type of connection is not recommended. While the action or connection may function, there are better ways to perform the action or make the connection.

While the action or connection may function, th ere are better ways to perform the action

Chapter

Meta SAN Tape Consolidation Overview

1

To demonstrate the implementation of the Multiprotocol Router in a real-world context, this Guide uses an imaginary company (April Corporation) with typical SAN configurations and Tape Consolidation challenges.

APRIL Corporation has multiple SAN Islands for their business units (see Figure 1-1). Currently there is one each for Engineering, Accounting and Sales. SAN 1 has dual fabrics, because critical Engineering data is stored on this SAN. Non -critical Sales and Accounting data (and associated backups) are stored on SAN 2, a single fabric SAN Island. SAN 3, a separate SAN Island, is used for backups of the critical data.

The hosts have 3 HBAs, two for accessing the primary storage and a third for backups. APRIL Corporation has multiple Master backup servers and smaller tape libraries. The single tape library used to backup Engineering and Accounting data is not being efficiently utilized. Often it is idle and unused. Due to the separate responsibilities of each group and independent SAN fabric scaling requirements, a merging of SAN Islands to a single larger port count SAN is not feasible. To increase asset utilization and move towards a centralized backup management framework, the company desires a consolidated shared tape SAN environment.

company desires a consol idated shared tape SAN environment. Figure 1-1 APRIL CORP SAN “Before” Architecture

Figure 1-1

APRIL CORP SAN “Before” Architecture

1 Meta SAN Tape Consolidation Overview

After analyzing the business requirements, APRIL Corporation designs a single Meta SAN using a Brocade SilkWorm Multiprotocol Router. By using the Multiprotocol Router, APRIL Corporation is able to increase the utilization of the tape library currently attached to SAN 1. Originally used only by the Engineering department on its dual fabric SAN island, the library is now available to other organizations (see Figure 1-2) . With this change, the second tape library is now free to be re-purposed or retired. The backup SAN Island can now scale completely independently and non-disruptively while achieving increased connectivity.

To share this resource among all hosts in the Meta SAN, a “Logical SAN” (LSAN) is defined on each edge fabric. This allows the tape library to be accessed by a Media Server on each edge fabric. If additional Media Servers are required, it is easy to add them to the LSAN configuration by using the standard Brocade zoning tools. Additional hosts now only need to utilize two HBAs instead of three. The unused HBAs can be repurposed as well.

The tape library, now connected as part of a Meta SAN using a single Brocade Multiprotocol Router for Fibre Channel Routing, provides a centralized backup resource that is easier to maintain and manage. Also, the tape library benefits from far greater utilization since all departments are now able to share it. As the company grows, additional edge fabrics and Media Servers can be easily added non-disruptively and scale independently to meet future business unit requirements.

independently to meet future business unit requirements. Figure 1-2 Target Meta SAN Tape Consolidation Solution 1-2

Figure 1-2

Target Meta SAN Tape Consolidation Solution

Meta SAN Tape Consolidation Overview

1

1.1. Meta SAN Tape Consolidation Solution Overview

The Multiprotocol Router Tape Consolidation Solution presented in this Guide provides an example of how to deploy a Tape Consolidation Use Case, as discussed in the Brocade Multiprotocol Routing Services technical white paper. Please refer to the white paper for details on this and other use cases.

The Multiprotocol Route provides iSCSI, FCIP and Fibre Channel Routing Services (FCRS) services. This solution provides relevant background information and demonstrates the configuration of FCRS for a tape backup environment. ISCSI and FCIP are not covered within the context of this solution. The intent of this Guide is to introduce the Brocade Silkworm Multiprotocol Router and the optionally licensed FCRS feature set to a technical audience by staging an actual FCRS deployment with 3rd party products.

The purpose of the solution is to demonstrate how to configure the Multiprotocol Router to attach to multiple Brocade Fibre Channel fabrics. Establishing connectivity is the first step. Next comes setting up LSANs: LSANs will allow the sharing of tape devices among hosts attached to edge fabrics. The actual solution presented in this document was developed at Brocade, with real hardware and software. As it was developed, some guidelines were developed. These are passed along in this Guide to facilitate actual deployment of a similar solution for evaluation purposes.

1.1.1. Meta SAN Tape Consolidation Solution at a Glance

This section will provide an overview of each step required to design and deploy the Meta SAN Tape Consolidation solution. The remainder of the document will discuss details provided in this section.

1.1.1.1. Assumptions

For this specific solution it is assumed that

All Host Bus Adaptors (HBA) are installed in the hosts, and the drivers configured for F_Port attachment to four Brocade edge fabrics.

The HDS 9910 and LSI E-Series RAID arrays have been set up to present LUNS for a multi-pathing configuration for each fabric-attached port.

All edge fabrics connected to a Multiprotocol Router are properly licensed with Fibre Channel Routing Services (FCRS) and the ports offline.

The switches are racked and configured according to the recommendations of the Design, Deployment, and Management (DDM) Guide Version 2.1 (53-0000366-02).

All Meta SAN components are powered on and attached using proper cable management techniques.

All hosts and switches are configured to properly access the RAID storage devices and are connected to the corporate IP network for management purposes.

1 Meta SAN Tape Consolidation Overview

1.1.1.2. Step-by-Step Overview

The document is organized according to the sequence of steps required to complete the deployment.

Design a Meta SAN for the Tape Consolidation use case. The requirements for this design are based primarily on the device-sharing scheme and MAPS (Management, Availability, Performance and Scalability), as presented in the DDM. Once determined, plan out the Meta SAN deployment. Label all fiber cable edge device connections and ISLs.

Define and configure the Multiprotocol Router Ex_ports for Fibre Channel Routing. These connections are called Inter Fabric Links (IFLs) and provide the base-level connectivity required for device sharing.

Define and configure the LSAN configuration based on the design plan. The LSANs allow devices to be shared between the edge fabrics.

Configure each host's HBAs driver for persistent binding. Reboot and verify that the LSAN tape storage is available on each. Install the Solaris patch required for VERITAS Volume Manager.

Verify that the Tape Library (in this case the STK L180) can be accessed by the Operating System on each device host.

Install and configure VERITAS NetBackup DataCenter 4.5 on the Master Server (int123.) Install the MP6 patch. This includes configuring the SG driver if necessary: The SG driver is installed as part of the NetBackup application. This driver is used for discovering and using the tape library for initiated backup jobs.

Once NetBackup has been installed and configured on the Master Server, verify the setup with a test backup. This entails the setup of a backup Policy.Note that int123 (the Master Server) will act as the robot control host.

Now install the Media Server on int205 (the Solaris Media Server) and int124 (a Windows Media Server.) Add both to the Master Server configuration so that the Master Server can be managed them. Both Media Servers will point to int123 for the STK robot control.

Configure each of the new Media Servers so that they share the STK L180 tape devices with the Master Server.

Perform a test backup on the Media Server. Install the NetBackup client software on the remaining eight hosts.

Do any final tuning to the NetBackup configuration. (This step is not discussed in this Guide.)

This completes the Overview. Please see the VERITAS NetBackup Installation Guide and the Veritas NetBackup Administrators Guide for UNIX and Windows for background information and further detailed instructions on installation and configuration options.

Chapter

Solution Requirements and Design

2

An excellent discussion of SAN Design exists in Brocade’s Design, Deployment, and Management (DDM) Guide. For a current softcopy, please go to the Brocade Connect or Partner websites. Although the current version does not cover the Multiprotocol Router with Fibre Channel Routing Services (FCRS), otherwise known as a Fibre Channel Router (FCR), many of these same concepts and trade-offs still apply to the interconnection of related fabrics, which is what is now being called a Meta SAN. Thus the MAPS (Management, Availability, Performance and Scalability) framework covered in the Design section still apply and will be used as a basis for the discussion that follows. The switch and fabric setup should follow the guidelines in the Deployment section.

2 Solution Requirements and Design

2.1. Introduction

A “Meta SAN” is a related interconnection of previously separate SAN islands. What makes these fabrics related? At one level, they are now connected and frames can be routed from one fabric to another without requiring a fabric merge. Core PID formats, zoning, and other fabric configurations can now remain separate. At a deeper level, devices previously on separate SAN islands can now be shared, providing increased asset utilization. This new sharing paradigm is called an LSAN. It is the LSAN that makes the Meta SAN framework related.

Solution Requirements and Design

2

2.2. Meta SAN Design Connectivity

In the Meta SAN Tape Consolidation solution, the starting point is three separate SAN islands. SAN 1 is a highly available

dual core/edge fabric with approximately 250 ports and attached devices. The fabrics that make up this SAN are called Fabric

A and Fabric B. SAN 2 is a cascaded two-switch fabric. SAN 3 is a single SilkWorm 3800 with an attached STK Library being

used by hosts on SAN 1. This is depicted in Figure XXX. A Meta SAN is desired to improve asset utilization. This will

improve the usage of the tape library, but also will increase the number of utilized SAN fabric ports. not distinguish between SANs, only fabrics.

From a manageability and availability perspective, a single Multiprotocol Router is desired since this Meta SAN is for tape backup purposes. If the Router was to have an unscheduled outage, the hosts still would be able to access the local fabric storage devices without disruption. In this case, therefore, two Multiprotocol Routers are not required.

From a performance and scalability perspective, a single Multiprotocol Router also will meet the need. Each tape device uses

about 30 MB/sec at peak bandwidth usage. While a single Inter Fabric Link (IFL) will be sufficient, (there are only 4 drives),

it is good practice to have a minimum of two: In the event of a downed link, backup jobs can still be performed. Having two

Note that the FCR does

IFLs also provides load balancing for frames that traverse the Meta SAN. With 2 IFLs per fabric, a single Multiprotocol Router can connect up to 8 edge fabrics or 4 core/edge dual fabric SANs. The logical design is shown in Figure 2-1.

Figure 2-1

Fabric A SAN 1
Fabric A
SAN 1
Fabric B SAN 1
Fabric B
SAN 1
AP7420 as FCR Router SAN 3
AP7420 as
FCR
Router
SAN 3

Multiprotocol

SAN 2
SAN 2
2-1 Fabric A SAN 1 Fabric B SAN 1 AP7420 as FCR Router SAN 3 Multiprotocol

2 Solution Requirements and Design

2.3. LSAN Design and Plan

Now that the connectivity is designed, the next step is to design and plan out the LSAN configuration. This section will not cover the details of site preparation, rack layout, specific cable assignments for IFLs, ISLs, hosts and storage placements, etc. These details are covered in the Brocade Design, Deployment, and Management (DDM) Guide. Instead, a simple table with the essential information will be developed to illustrate what is minimally needed.

One host from each fabric in SAN 1 and SAN 2 requires access to the tape library on SAN 3. The information needed is: the edge fabric to which they are attached; the specific port locations; the HBA and Tape physical WWPN and alias names; LSAN Zones. To uniquely identify a fabric, the FCR-assigned FID will be used. By default, this number is 2 + the physical port number to which an edge fabric switch is attached.

The best way to summarize this information is within a table. Table 1 below shows the required information:

Table 2-1

SAN

Edge Fabric

Device Name and port WWPN Physical Port IDs

Imported Zone

LSAN Zones

(FID) Switch

Alias Names

Switch Name

 

SAN 1 Fabric A

14

SW3800

int124 HBA A on port 10

IM16_STK_L180

LSAN_int124_win2k_A_IM

sialab88

10:00:00:00:c9:29:04:8f

16_STKL180_zone

db1a00

SAN 1 Fabric B

15

SW3900

int123 HBA B on port 8

IM16_STK_L180

LSAN_int123_sol_B_IM16_

int219

10:00:00:00:c9:30:d0:62

STKL180_zone

580800

SAN 2

8 SW2800

int205 on port 4

IM16_STK_L180

LSAN_int205_sol_A_IM16_

int193

10:00:00:00:c9:24:94:43

STKL180_zone

bf0400

SAN 3

16

SW3800

STK L180 on ports 0-4

IM14_int124_w2

LSAN_STKL180_int123_sol

int185

50:01:04:f0:00:41:18:00

kIM15_int123_so

_B_zone

50:01:04:f0:00:47:5a:b4

lIM8_int205_sol

LSAN_STKL180_int124_wi

50:01:04:f0:00:47:1e:18

n2k_zone

50:01:04:f0:00:42:90:a9

LSAN_STKL180_int205_sol

50:01:04:f0:00:42:90:67

_zone

b900ef

b90100

b90200

b90301

b90401

Guideline: Before implementing an LSAN, it is highly recommended to create a similar table as part of the planning process. This vastly simplifies the deployment and aids troubleshooting during the setup.

This concludes the Meta SAN Design. Before proceeding to a discussion of LSAN deployment, a section will be devoted to the specific hardware and software used in the Meta SAN Tape Consolidation solution.

Solution Requirements and Design

2

2.4. Detailed Hardware and Software List

As shown in the Figure 2-2 below, the Meta SAN in the Tape Consolidation solution features three SAN Islands. SAN 1 is a dual fabric consisting of SilkWorm 2800, 3800, 3900 and 12000 switches deployed in a core/edge topology. SAN 2 is a single fabric that consists of 2 SilkWorm 2800s as a cascade. SAN 3 is a single SilkWorm 3800. SAN 1 has 6 hosts, 2 of which will

be backup servers. Fabric A has a Windows host that will become a Media Server. Fabric B has a Solaris host that will become

the Master Server.

SAN 2 has a Solaris host that will be used as a second Media Server.

a Solaris host that will be used as a second Media Server. Figure 2-2 Meta SAN

Figure 2-2

Meta SAN Tape Consolidation Logical Connections

Local SAN-based storage exists on each fabric. SAN 1 has a dual attached HDS 9910 and an LSI E-Series RAID (also known as an IBM FastT.) SAN 3 has the STK L180 Tape Library with 4 STK 9840 drives. This tape library will be shared among all three hosts, each of which is sitting on an separate edge fabric. The hosts have Emulex HBAs installed. Some are dual attached. Each edge fabric has a separate zoning configuration that is not merged when connecting to the Silkworm Multiprotocol Router.

Table 2-2 below lists the hardware and software used for this solution.

2 Solution Requirements and Design

Table 2-2

Equipment, Drivers and Software Summary

TESTED HARDWARE AND SOFTWARE

 

BACKUP SERVERS

 

Sun Sunfire 280R (int123)

64

bit Solaris 8

Patch: Generic_108528-26 FW Ver 3.90A7 Driver Ver 5.01e

2

UltraSparc III+ 900 Mhz 2048 MB

Emulex LP9002

2

HBA (2 Gb/sec)

Solaris File Server Netbackup Master Server

 

Sun Enterprise E450 (int205)

64

bit Solaris 8

Patch: Generic_108528-15 FW Ver 3.82a1 Driver Ver 5.02d

1 Ulrasparc II 250 Mhz 256 MB

Emulex LP8000

2 HBA (1 Gb/sec)

Solaris File Server

 

Netbackup Media Server

HP Proliant DL580 (int124)

Windows 2000

Patch: SP4FW Ver 3.90a7 Full Port Driver Ver 5.2.20.4

2

Xeon PIII 750 Mhz, 2048 MB

Emulex LP9002L

2

HBA (2 Gb/sec) (LSI RDAC Multipathing)

Windows SMB File Server

NetBackup Media Server

ENTERPRISE SOFTWARE

   
 

Veritas

NetBackup 4.5

Patch: MP6 Solaris Patch: MP6 Windows

META SAN INFRASTRUCTURE

   

SAN 1 Dual Fabrics A and B 12 BROCADE Switches Total

2

SilkWorm 12k chassis (core)

FOS Version: 4.1.1d

2

SilkWorm 3900 (edge)

FOS Version: 4.1.1d

BROCADE SAN 2 (Single Fabric) BROCADE SAN 3 (Single Fabric) BROCADE Fibre Channel Router

4

SilkWorm 3800 (edge)

FOS Version: 3.1.1d

4

SilkWorm 2800 (edge)

FOS Version: 2.6.1d

2

SilkWorm 2800

FOS Version: 2.6.1d

1

SilkWorm 3800

FOS Version: 3.0.2q

 

SilkWorm Multiprotocol Router (Licensed with FCRS)

1

XPATH OS Ver: Alpha68

STORAGE ENCLOSURES

   

StorageTek

L180 Tape Library (4 drives) Two FC STK 9840B Two FC STK 9840 One FC Robot

Library Firmware: 3.01.029840B Drive FW: 1.30.3169840

Drive FW:

1.30.110

 

HDS

9910 (Four 2Gb/sec ports used)

 
 

LSI

MetaStor 27722 FAST T Controllers

Firmware: 4.01.00.03 Management GUI

 

(4 ports)

8.20

 

JMR

FORTRA JBOD

Firmware 0002

 

15

Seagate ST336605FC

Chapter

Configuring the Brocade Meta SAN

3

Two steps are required to set up the SilkWorm Multiprotocol Router as an FC Router, and to share devices across the edge fabrics that make up the Meta SAN:

Configure the Fibre Channel Routing Services (FCRS) software. This consists primarily of configuring the EX_Ports on the Multiprotocol Router

Define and configure the LSAN import/export members on the edge fabrics. Standard zoning commands are used to accomplish this.

Both of these tasks are relatively straightforward. Before beginning the Fibre Channel Routing Services (FCRS) configuration on the Multiprotocol Router, be sure that the Recovery Kernel and XPATH OS components have been updated to a minimum version of 1.3.0.0 and 7.1.0_ respectively. An overview of the required steps to update the Recovery Kernel (if required) and XPATH OS follows. However, this procedure will not be discussed in detail. Please refer to the XPATH OS Procedures Guide for a detailed discussion on the steps required to perform an upgrade.

Caution:

For this solution, it is assumed that all member switches of each edge fabric has the PID Format set to 1 (Core). This is not required. The PID format, a fabric wide parameter, may be set to different values for different edge fabrics. Be aware that if this is the case, the -p option may be required for portcfgexport.

3 Configuring the Brocade Meta SAN

3.1. XPATH OS Upgrade Overview

It may be necessary to first upgrade the Recovery Kernel. An upgrade is required for specific versions of XPATH OS as discussed in the release notes. It is highly recommended to check the Recovery Kernel version to verify that an upgrade is required before attempting it.

The first steps to upgrade the Recovery Kernel are to boot into the PMON environment, configure the appropriate network

boot and installation configuration parameters, and format the filesystem to which the installation packages will be copied.

These parameters are defined with the set command. Note that a TFTP server is required to do the installation.

parameters are properly defined, a netload is executed. The new Recovery Kernel firmware will load automatically and the Multiprotocol Router will reboot into the new environment without additional keystrokes. This process takes approximately 5 minutes to complete.

At the Recovery Kernel prompt (Recovery Kernel %), the new XPATH Base OS component will be loaded. This package (plus the appropriate license) is all that is required for FCR capability. Typically this code is loaded into Bank 1. Since the XPATH OS Base installation package binary exceeds the TFTP file size limitation, FTP is required. Again, use the set command to setup the required parameters. Once the bank version is set, an FTP session will be opened and the package will download automatically into the defined bank (this takes a couple of minutes.) To install the code, define the set cfgbank parameter to point to the desired bank. After about 10 minutes, the packages will be installed. A reboot is required to finish the process. If required, the XPATH SAS component can be installed in the XPATH OS environment by using the rpgsrvr command. Once installed, the Fibre Channel Routing Services (FCRS) can be configured.

Once the

Configuring the Brocade Meta SAN

3

3.2. Configuring FCRS on the Multiprotocol Router

The steps below show in detail how to define, configure and verify the Multiprotocol Router FCRS setup for the attachment of an edge fabric. This primarily involves defining EX_Ports on the Router. When complete, the edge fabric switch to which the Multiprotocol Router is attached will see an E_port and the Front Domain ID as part of the same physical connection to which the Router has an EX_port defined.

Warning:

If the ports are not configured to be “off” with portstop, the Multiprotocol Router will attempt to merge with edge

fabrics as an ordinary FC switch. Dual fabric SANs could be merged, resulting in loss or corruption of data. The default

setting is subject to change for successive versions of XPATH OS.

3.2.1. FCRS Configuration Overview

This section provides an overview of configuring Fibre Channel Routing Services (FCRS) on the SilkWorm Multiprotocol Router. Figure 3-1 below (Meta SAN Logical Connectivity) displays the Tape Consolidation specific logical edge fabric connections. In short, configuring FCRS is a two-step process:

First establish edge fabric connectivity with the Silkworm Multiprotocol Router.

Secondly, establish device sharing through the use of LSANs. Both steps are required to set up a useful Meta SAN.

The first step is to establish edge fabric connectivity. This involves the creation of EX_Ports and Front Domains (FD). Configuring the Multiprotocol Router ports to have EX_Ports is a three-step process: First the port is stopped using portstop, then portcfgexport is executed, and finally the port is restarted. The FD are created automatically and the edge fabric will have a Fabric ID (FID) assigned. The FID identifies a particular fabric as a unique entity for the routing of frames. As part of the automatic configuration, a Front Domain (FD) will be created and presented off of the configured EX_Port to the edge fabric. The FD can be thought of as a virtual switch that will become a local member of an edge fabric. A FD basically acts as a “doorway” to allow frames to be routed by the Multiprotocol Router from edge fabric to edge fabric. If additional links are required to the same edge fabric, the FID must be specified with the -f command line option. A new FD will be created for each additional link.

The edge fabric switch will display an E_Port connected to the FD on the link where the physical cable is connected. The Multiprotocol Router will display the same physical connection as an EX_Port. This type of connection is known as an Inter Fabric Link (IFL). This will become clearer once the example is walked through. If desired, both the FID and the preferred FD can be specified as part of the port configuration with portcfgexport. This material is covered in the first subsection.

To share devices across the Meta SAN, LSANs are required. LSANs are essentially zones defined at the edge fabrics for imported and exported devices. When an LSAN is established, an Translate (Xlate) Domain (XD) is created automatically. Proxy devices that represent the physical devices are logically attached to the XD and only one XD is created per edge fabric. Additional LSAN zones on the same edge fabrics will use the SAME XD domain. More on this later. Note that LSAN planning becomes extremely important for larger configurations. Some planning guidelines will be discussed. Actually doing each LSAN configuration step is quite straightforward, because standard zoning commands are used to accomplish the task.

Note:

Note that LSANs are unlike traditional zoning, where, if no configuration is in effect, all devices are allowed to access each other. If LSANs are not defined, the devices will not see each other.

3 Configuring the Brocade Meta SAN

The first section, “Configuring Multiprotocol Router FCRS for Tape Edge Fabric Connectivity,” concentrates on configuring the Multiprotocol Router FCRS using portcfgexport for each of the three SANs. Note that there are a total of 4 fabrics that need to be set up. Detailed steps will be shown for SAN 3, where the STK Tape Library resides. The second subsection will display the remaining steps that allow SAN 1 and SAN 2 to attach to the Multiprotocol Router. In this section, the commands required to configure the Router will be shown, but the output will not be shown in detail. The last subsection will illustrate how to do a final verification that confirms that all three SANs that make up the Meta SAN are attached to the Multiprotocol Router, and that the EX_Ports are properly configured and are ready to pass I/O traffic. A separate section, “LSAN Detailed Configuration,” will discuss how to set up the LSANs for each edge fabric.

3.2.2. Meta SAN Logical Connectivity

Figure 3-1 shows the logical Meta SAN layout and device location. This diagram will be referred to throughout the remaining discussion.

SAN 1 (FID 14, FID 15) Fabric A Fabric B FID 14 FID 15 Media
SAN 1 (FID 14, FID 15)
Fabric A
Fabric B
FID 14
FID 15
Media
NBU 4.5
Server
Master Server
int123
Sun
int124 FD Win FD 11 12 FD FD 13 10 AP7420 as FCR FD
int124
FD
Win
FD
11
12
FD
FD
13
10
AP7420 as
FCR
FD

Multiprotocol Router

SAN 2 (FID 13) Fabric A FID 13 FD 8 Media FD 9 Server int205
SAN 2 (FID 13)
Fabric A
FID 13
FD 8
Media
FD 9
Server
int205
Sun
SAN 3 (FID 16) Fabric A FID 16 15 FD 14 STK L180
SAN 3 (FID 16)
Fabric A
FID 16
15
FD
14
STK
L180

Figure 3-1

Tape Consolidation Meta SAN - Logical Connectivity

Configuring the Brocade Meta SAN

3

3.3. Configuring Multiprotocol Router FCRS for Tape Edge Fabric Connectivity

The section details the steps to configure the tape edge fabric, otherwise known as SAN 3, which consists of a single SilkWorm 3800, while at a telnet session.

Note:

Neither Brocade Fabric Manager nor Brocade Web Tools will be used for this discussion.

Follow the following steps for a detailed explanation of setting up and verification of the EX_Port connections.

1. Establish a telnet session on the Silkworm Multiprotocol Router as user admin.

2. Verify the current version of XPath OS using the version (or alternately rpgsrvr) command as illustrated. Note that the output will also show which bank was used for the installation, and the network configuration parameters.

AP7420:admin> version RPG file server

: 192.168.162.209

Root directory

: /mars

FTP username

: ftpuser

FTP password

: ftpuser

Download protocol

: ftp

================== Installed Packages:

=================== Package Name Installed from Installed date Administrative status Primary status Secondary Status

Disk usage on root fs -

: xpath_os_v7.1.0_alpha7_bld68 : bank1 : Jan 16 18:04 : (1) : up : installed and running

Total: 280 Mbytes, Free: 181 Mbytes.

3. Use licenseshow as illustrated below to verify that the proper licenses are installed on the Multiprotocol Router. No additional licenses are required on the edge fabric switches.

AP7420:admin> licenseshow License Key: SQQRSzSzy9TRRSTy Web

License Key: bRcSbRcS9RcSdTcY Zoning

License Key: SzzzydRyddb000zF Trunking

License Key: SzzzydRyddT800zF FCIP

License Key: SzzzydRyddT020z9 Fibre Channel Routing Services

License Key: cQeRcyzczcdhfSdx Base switch license Ports on Demand - enable all 16 ports

3

Configuring the Brocade Meta SAN

Note:

For all 16 ports to be enabled, the “Ports on Demand” license key is required. To use the Multiprotocol Router as a Fibre Channel Router, the “Fibre Channel Routing Services” license key must be installed. As with Fabric OS-based Silkworm switches, the licenseadd command is used to do this.

Now that the XPATH OS version and license keys are verified, the Multiprotocol Router can have EX_Ports configured.

4. The first step is to use portstop to “offline” the Multiprotocol Router FCR ports that are to be connected to the edge fabrics. This will prevent the Router from becoming a member of an attached fabric. The ports can be stopped. This is a very important step. These ports should have been defined ahead of time as part of the planning process. In this particular solution, ports 14 and 15 are used for this purpose. (Stopping a port will take a few moments to complete.)

AP7420:admin> portstop 14 port 14 stopped. AP7420:admin> portstop 15 port 15 stopped.

AP7420:admin>

or AP7420:admin> portstop 14-15 port 14 stopped. port 15 stopped.

Guideline: Always use portstop BEFORE attaching the fiber cables to the Multiprotocol Router and configuring its ports to be used for FC Routing Services.

5. Configure the ports to be used for Fibre Channel Routing using the portcfgexport command as illustrated below. Once the port is started, an EX_Port will be defined and brought online on the Router. On the attached edge fabric switch, an E_Port will be brought online. To facilitate connectivity, a phantom domain will be presented from the Router EX_Port to the attached edge fabric.

AP7420:admin> portcfgexport 14 -a 1

6. To bring up the EX_Port, use portstart on the Multiprotocol Router as illustrated below. To verify that the port is online, use switchshow. Note that port 14 in the output below is now configured as an EX_Port with a presented phantom domain. Part of this process defines a Fabric ID (FID). In this case it is16. This number uniquely identifies a fabric to the Fibre Channel Routing Service (FCRS). The Multiprotocol Router keeps a table of the FIDs so it knows where to route traffic. The FID is important to know because it is required to set up additional EX_Port connections to the same fabric. If not used, FCRS will define a new FID by default and the Router will think it is attached to a different fabric. In this solution, port 15 will be used to attach to the same fabric. Note that switchshow does not show the phantom domain number assignment. To see this information, use fabricshow:

AP7420:admin> portstart 14 port 14 started

AP7420:admin> switchshow

Switch Name

Switch State : Online

:

AP7420

Switch Type

:

38.0

Switch Role

:

Principal

Switch Domain: 100

Switch ID

:

FFFC64

Switch WWN

: 10:00:00:05:1e:13:8b:00

beacon status: OFF

zoning

: ON (backupcfg)

FC router BB Fabric ID: 1

Port Media Speed State

=======================================

Info

Configuring the Brocade Meta SAN

3

0

id

AN

No_Light

1

id

AN

No_Light

2

id

AN

No_Light

3

id

AN

No_Light

4

id

AN

No_Light

5

id

AN

No_Light

6

id

AN

No_Light

7

id

AN

No_Light

8

id

AN

No_Light

9

id

AN

No_Light

10

id

AN

No_Light

11

id

AN

No_Light

12

id

AN

No_Light

13

id

AN

No_Light

14

id

N2

Online

14

id

N2

Online

EX_PORT 10:00:00:60:69:51:0e:44 "int185" (fabric

id = 16)

 

15

id

AN

No_Light stopped

 

Note that switchshow does not show the Front Domain Number assignment. To see this information, use the portcfgexport command as shown in step 6 or fabricshow on the edge fabric switch as discussed in step 7.

7. Verify the EX_Port configuration. Be sure the “Admin:” field is set to enabled as shown. It is important to note the Core PID setting: By default it is set to core. This is equivalent to a setting of 1 on the edge fabric switches. In this case, it is assumed that all edge fabrics have the member switches set to 1 so the setting will not be changed. If required, use the appropriate command line option (use the online Help for details.)

Warning:

The Core PID Formats must match or the FD will not be able to become a member of the edge fabric.

 

Note:

Note the FID is set to 16 and the Front Domain (FD) ID is displayed in decimal as 160. This is a0 in hex and is the first byte in the 24 bit PID. Each FD also has a WWN assigned. In the output below it is

50:00:51:e1:38:b0:0e:0e.

3 Configuring the Brocade Meta SAN

AP7420:admin> portcfgexport 14

Port

14

info

Admin:

enabled

State:

OK

Pid format:

Operate mode:

core native

Edge Fabric ID:

16

Front Domain ID:

 

160

Front WWN:

50:00:51:e1:38:b0:0e:0e

Principal Switch:

 

200

principal WWN:

10:00:00:60:69:c0:06:c3

R_A_TOV:

10000

E_D_TOV:

2000

8. Verify that the Front Domain is presented properly to the edge fabric and has established itself as a member. To display and verify this information, establish a telnet session on the Fabric OS Silkworm switch in question and execute the fabricshow command. Note that in the solution, the phantom domain appears with a name of fcr_fd_160_14 and has a domain number set to a0 hex (160 decimal).

int185:admin> fabricshow

Switch ID

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

Name

Worldwide Name

Enet IP Addr

FC IP Addr

160: fffca0 50:00:51:e1:38:b0:0e:0e

200: fffcc8 10:00:00:60:69:c0:06:c3 192.168.173.242 0.0.0.0

0.0.0.0

0.0.0.0

"fcr_fd_160_14"

>"int185"

The Fabric has 2 switches

Note:

Note that, when fabricshow is executed on the Multiprotocol Router, neither the attached switch nor the FD appear as fabric members. This is expected, because the Router has not merged with the edge fabric.

AP7420:admin> fabricshow

Switch ID

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

Name

Worldwide Name

Enet IP Addr

100: fffc64 10:00:00:05:1e:13:8b:00 192.168.163.103 >"AP7420"

The Fabric has 1 switches

9. Repeat steps 4 - 7 using the assigned Fabric ID (FID), which in this case is 16, when defining the new EX_Port on port 15 of the Multiprotocol Router. Note that the port has already been stopped with portstop in step 1. The required options are illustrated below.

AP7420:admin> portcfgexport 15 -a 1 -f 16

The command argument breakdown is as follows:

15 is the port number.

The -a 1 administratively enables the port for configuration changes.

The -f 16 sets the edge FID to 16, since the port on the Multiprotocol Router is to be attached to the same one-switch fabric.

Warning:

When establishing a second link to the same edge fabric, use the -f option or the EX_Port will segment. This

requirement may not be necessary in future releases.

Configuring the Brocade Meta SAN

3

With no arguments, portcfgexport shows the current settings. Note that the Preferred Domain ID is set to 1 by default. This means the FD Domain ID will be set to 1 if no other switches in the fabric have claimed it. This option can be changed using a command line option if desired.

AP7420:admin> portcfgexport 15

Port

15

info

Admin:

enabled

State:

NOT OK

Pid format:

core

Operate mode:

native

Edge Fabric ID:

16

Preferred Domain ID:

 

1

R_A_TOV:

10000

E_D_TOV:

2000

10. Portstart starts the port with the desired settings as shown above. Note that these can be changed if necessary before the port is started with additional usage of the portcfgexport command.

AP7420:admin> portstart 15 port 15 started

11. Once up and running, portcfgexport is executed again to verify the configuration. Note that the Front Domain WWN is now assigned and the front domain is set to 1.

AP7420:admin> portcfgexport 15

Port

15

info

Admin:

enabled

State:

OK

Pid format:

Operate mode:

core native

Edge Fabric ID:

16

Front Domain ID:

 

1

Front WWN:

50:00:51:e1:38:b0:0e:0f

Principal Switch:

 

200

principal WWN:

10:00:00:60:69:c0:06:c3

R_A_TOV:

10000

E_D_TOV:

2000

Warning:

If the FID is not set with portcfgexport when attaching another Multiprotocol Router EX_Port to the same edge

fabric with a previously set FID, the following error will occur, (when viewed from switchshow)

15 id

AN

No_Light disabled EX_PORT (Last error: Fabric ID oversubscribed).

This is because a new fabric ID has been assigned automatically and the Router assumes the Ex_port is attaching to a new edge fabric. Once this happens, the offending port will be disabled. To fix this condition:. Stop the misconfigured port with portstop, set it with the proper FID with portcfgexport, start using portstart and then finally re-enable it with portenable. The EX_Port now will be online.

12. On the Multiprotocol Router, switchshow should now display the following output. Note that the Fabric ID is 16 for both ports 14 and 15:

3 Configuring the Brocade Meta SAN

AP7420:admin> switchshow

Switch Name

Switch State : Online

:

AP7420

Switch Type

:

38.0

Switch Role

:

Principal

Switch Domain: 100

Switch ID

:

FFFC64

Switch WWN

: 10:00:00:05:1e:13:8b:00

beacon status: OFF

zoning

: ON (backupcfg)

FC router BB Fabric ID: 1

Port Media Speed State

=======================================

Info

0

id

AN

No_Light

1

id

AN

No_Light

2

id

AN

No_Light

3

id

AN

No_Light

4

id

AN

No_Light

5

id

AN

No_Light

6

id

AN

No_Light

7

id

AN

No_Light

8

id

AN

No_Light

9

id

AN

No_Light

10

id

AN

No_Light

11

id

AN

No_Light

12

id

AN

No_Light

13

id

AN

No_Light

14

id

N2

Online

EX_PORT 10:00:00:60:69:c0:06:c3 "int185" (fabric id = 16)

15

id

N2

Online

EX_PORT 10:00:00:60:69:c0:06:c3 "int185" (fabric id = 16)

13. On the edge fabric switch (which contains the tape library devices) the following output from switchshow and fabricshow is displayed.

int185:admin> switchshow

switchName:

int185

switchType:

9.2

switchState:

Online

switchMode:

Native

switchRole: Principal

switchDomain:

185

switchId:

fffcb9

switchWwn:

10:00:00:60:69:51:0e:44

switchBeacon:

OFF

Zoning:

OFF

port

0: id N1 Online

L-Port 1 public

port

1: id N2 Online

F-Port 50:01:04:f0:00:47:5a:b4

port

2: id N2 Online

F-Port 50:01:04:f0:00:47:1e:18

port

3: id N1 Online

L-Port 1 public

port

4: id N1 Online

L-Port 1 public

port

5: id N2 No_Light

port

6: id N2 No_Light

port

7: id N2 No_Light

port

8: id N2 No_Light

port

9: id N2 No_Light

port 10: id N2 No_Light port 11: id N2 No_Light port 12: id N2 No_Light port 13: id N2 No_Light port 14: id N2 Online

E-Port 50:00:51:e1:38:b0:0e:0e "fcr_fd_1_14" (down

stream) port 15: id N2 Online

E-Port 50:00:51:e1:38:b0:0e:0f "fcr_fd_2_15" (down

Configuring the Brocade Meta SAN

stream)

int185:admin> fabricshow

Name

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

Switch ID

Worldwide Name