Page 1 ® McDATA Products in a SAN Environment Planning Manual P/N 620-000124-510 REV A...
Page 2 Record of Revisions and Updates Revision Date Description 620-000124-000 5/2002 Initial release of the manual. 620-000124-100 9/2002 Revision of the manual to describe the Intrepid 6140 Director, Sphereon 4500 Fabric Switch, and Release 6.3 of the Enterprise Fabric Connectivity Manager application. 620-000124-200 2/2003 Revision of the manual to include additional information and describe Release 7.1 of the Enterprise Fabric...
Page 3: Table Of Contents
Contents Preface .......................... xiii Chapter 1 Introduction to McDATA Multi-Protocol Products Product Overview................1-2 Multi-Protocol Hardware ............1-2 SAN Management Applications..........1-5 Directors .....................1-6 Director Performance ..............1-7 Intrepid 6064 Director ...............1-8 Intrepid 6140 Director .............1-10 Intrepid 10000 Director ............1-12 Fabric Switches................1-14 Fabric Switch Performance.............1-15 Sphereon 3232 Fabric Switch..........1-15 Sphereon 4300 Fabric Switch..........1-16 Sphereon 4400 Fabric Switch..........1-18...
Page 4 Contents Chapter 2 Product Management Product Management...............2-2 Out-of-Band Management ............2-2 Inband Management ..............2-5 Management Interface Summary..........2-6 Management Server Support ............2-7 Management Server Specifications .........2-8 Ethernet Hub ................2-10 Remote User Workstations.............2-10 Product Firmware................2-11 Firmware Services ..............2-12 Backup and Restore Features ............2-13 SAN Management Applications...........2-15 SANavigator and EFCM Applications .........2-15 SANvergence Manager Application........2-18...
Page 5 Contents Fabric Scalability ..............3-39 Obtaining Professional Services..........3-40 Mixed Fabric Design Considerations .......... 3-40 FCP and FICON in a Single Fabric ........3-41 Multiple Data Transmission Speeds in a Single Fabric ..3-51 FICON Cascading ................3-52 High-Integrity Fabrics ............3-53 Minimum Requirements ............
Page 6 Contents SANtegrity Binding..............5-19 PDCM Arrays................5-20 Preferred Path ................5-23 Zoning ..................5-25 Server and Storage-Level Access Control ......5-29 Security Best Practices ............5-30 Optional Feature Keys ..............5-33 Inband Management Access ..........5-35 Flexport Technology..............5-36 SANtegrity Authentication ............5-36 SANtegrity Binding..............5-36 OpenTrunking................5-37 Full Volatility................5-38 Full Fabric .................5-38 Remote Fabric ................5-39 N_Port ID Virtualization ............5-39 Element Manager Application..........5-39...
Page 7 Contents Appendix A Product Specifications Director, Fabric Switch, and SAN Router Specifications ..A-1 Dimensions ................A-1 Power Requirements ............... A-3 Heat Dissipation............... A-5 Clearances ................. A-5 Acoustical Noise and Physical Tolerances ......A-6 Storage and Shipping Environment ........A-6 Operating Environment ............
Page 8 Contents viii McDATA Products in a SAN Environment - Planning Manual...
Page 9 Tables Out-of-Band and Inband Product Support Summary ......2-6 mSAN Routing Domain ................4-18 mSAN Supported Limits ................4-21 mFCP Versus iFCP ..................4-28 Transport Technology Comparison ............4-48 Cable Type and Transmission Rate versus Distance and Link Budget 5-5 Types of User Rights ..................
Page 10 Tables McDATA Products in a SAN Environment - Planning Manual...
Page 11 Figures Cabinet-Mount McDATA Products ............1-4 Intrepid 6064 Director .................. 1-9 Intrepid 6140 Director ................1-11 Intrepid 10000 Director ................1-12 Sphereon 3232 Fabric Switch ..............1-15 Sphereon 4300 Fabric Switch ..............1-16 Sphereon 4400 Fabric Switch ..............1-18 Sphereon 4500 Fabric Switch ..............1-19 Sphereon 4700 Fabric Switch ..............
Page 12 Figures Full Mesh Fabric ..................3-15 3-10 2-by-14 Core-to-Edge Fabric ..............3-17 3-11 Example Multiswitch Fabric ..............3-19 3-12 ISL Oversubscription .................. 3-32 3-13 Device Locality .................... 3-34 3-14 Device Fan-Out Ratio ................. 3-35 3-15 Fabric Performance Tuning ............... 3-36 3-16 Redundant Fabrics ..................
Page 13: Preface
Preface This publication is part of a documentation suite that supports ® McDATA multi-protocol switching and routing products, including the: ® • Intrepid 6064 Director. • Intrepid 6140 Director. • Intrepid 10000 Director. • Sphereon™ 3232 Fabric Switch. • Sphereon 4300 Fabric Switch. •...
Page 14 Preface Chapter 1, Introduction to McDATA Multi-Protocol Products This chapter provides an overview of McDATA multi-protocol products, and describes product performance and connectivity, security, and serviceability features. Chapter 2, Product Management - This chapter describes out-of-band and inband product management; the management server;...
Page 15 Preface Related Publications Other publications that provide additional information about McDATA products include: • Intrepid 6064 and 6140 Directors: — McDATA Intrepid 6064 and 6140 Directors Element Manager User Manual (620-000172). — McDATA Intrepid 6064 Director Installation and Service Manual (620-000108). —...
Page 16: Sphereon 4700 Fabric Switch
Preface • Sphereon 4700 Fabric Switch: — McDATA Sphereon 4700 Fabric Switch Element Manager User Manual (620-000242). — McDATA Sphereon 4700 Fabric Switch Installation and Service Manual (620-000239). • Eclipse 1620 SAN Router: — McDATA Eclipse 1620 SAN Router Administration and Configuration Manual (620-000206).
Page 17 Preface — McDATA EFCM Lite Installation Instructions (958-000171). — McDATA FC-512 Fabricenter Equipment Cabinet Installation and Service Manual (620-000100). Ordering Printed To order a printed copy of this publication, submit a purchase order Manuals as described in Ordering McDATA Documentation Instructions at http://www.mcdata.com.
Page 18 Preface All other trademarked terms, indicated by a registered trademark symbol (®) or trademark symbol (™) on first use in this publication, are trademarks of their respective owners in the United States or other countries or both. Forwarding Please send comments to the McDATA Solution Center by telephone, Publication fax, or e-mail.
Page 19 Preface United States and The C-UL-US mark on a product indicates compliance with Canada UL American National Standards Institute (ANSI) and Standards Certification Council of Canada (SCC) safety requirements as tested, evaluated, and certified by Underwriters Laboratories Inc. (UL) and Underwriters Laboratories of Canada (ULC).
Page 20 Preface In addition, the European Union (EU) Council has implemented a series of directives that define product safety standards for member countries. The following directives apply: • Products conform with all protection requirements of EU directive 89/336/EEC (Electromagnetic Compatibility Directive) in accordance with the laws of the member countries relating to EMC emissions and immunity.
Page 21 Preface Australia and New The Australia and New Zealand regulatory compliance mark Zealand C-Tick Mark (C-tick mark) on a product indicates compliance with regulatory requirements for safety and EMC (for information technology equipment) as set forth by the Australian Communications Authority (ACA) and the Radio Spectrum Management Group (RSM) of New Zealand.
Page 22 Preface Japanese VCCI The Voluntary Control Council for Interference (VCCI) statement Statement below applies to information technology equipment, and indicates product compliance with Japanese regulatory requirements. The statement indicates a product is a Class A or Class B product, and in a domestic environment may cause radio interference, in which case the user is required to take corrective actions.
Page 23 Preface Danger and Attention The following DANGER statement appears in this publication and Statements describes safety practices that must be observed while installing or servicing a product. A DANGER statement provides essential information or instructions for which disregard or noncompliance may result in death or severe personal injury.
Page 24 Preface DANGER DANGER Utiliser les câbles d’alimentation fournis. S’assurer que la prise de courant du local est du type correct, délivre la tension requise et est correctement raccordée à la terre. GEFAHR Die mitgelieferten Netzkabel verwenden. Sicherstellen, dass die verwendete Netzsteckdose dem vorgeschriebenen Typ entspricht, die erforderliche Spannung liefert und einwandfrei geerdet ist.
Page 25 Preface PELIGRO Utilice los cables de alimentación proporcionados. Asegúrese que el receptáculo tomacorriente para la instalación sea el tipo correcto, suministre el voltaje necesario, y que esté apropiadamente puesto a tierra. PELIGRO Utilice los cables de alimentación proporcionados. Asegúrese que el receptáculo tomacorriente para la instalación sea del tipo correcto, suministre el voltaje necesario, y que esté...
Page 26 Preface McDATA Products in a SAN Environment - Planning Manual xxvi...
Page 27: Introduction To Mcdata Multi-Protocol Products
Introduction to McDATA Multi-Protocol Products The enterprise-level storage area network (SAN) of today is typically complex and managed at the device layer. These problems result in SANs that use storage assets inefficiently, and are complex, error prone, expensive, and time-consuming to manage. ®...
Page 28: Product Overview
Introduction to McDATA Multi-Protocol Products Product Overview McDATA provides storage network solutions that are integrated across a variety of platforms, original equipment manufacturers (OEMs), and locations. Solutions are modular and support multiple technologies (current and future), protocols, and data transmission speeds.
Page 29 Introduction to McDATA Multi-Protocol Products — 32-port Sphereon 3232 Fabric Switch. — 12-port Sphereon 4300 Fabric Switch. The switch provides both switched fabric and Fibre Channel arbitrated loop (FC-AL) connectivity. — 16-port Sphereon 4400 Fabric Switch. The switch provides both switched fabric and FC-AL connectivity. —...
Page 30: Cabinet-Mount Mcdata Products
Introduction to McDATA Multi-Protocol Products 3. Intrepid 6064 Director. 4. Rack-mount management server. 5. Sphereon 4300 Fabric Switch. 6. Sphereon 4500 Fabric Switch. 7. Intrepid 6140 Director. 8. Eclipse 1620 SAN Router. 9. Eclipse 2640 SAN Router. 10. Intrepid 10000 Director. Cabinet-Mount McDATA Products Figure 1-1 McDATA Products in a SAN Environment - Planning Manual...
Page 31: San Management Applications
Introduction to McDATA Multi-Protocol Products SAN Management McDATA offers the following SAN management applications Applications installed on the rack-mount management server: ® • SANavigator application - The SANavigator application (Version 4.2 or later) is an integrated software package that provides management of an enterprise-wide, heterogeneous SAN (with multiple vendor applications) from a single console.
Page 32: Directors
Introduction to McDATA Multi-Protocol Products Refer to Chapter 2, Product Management for information about SAN management applications and the management server. Chapter 2 also describes switch management through: • The Internet using a product’s EFCM Basic Edition interface. • Inband (Fibre Channel) application clients. •...
Page 33: Director Performance
Introduction to McDATA Multi-Protocol Products Director Directors provide the following general performance features: Performance • High bandwidth - Ports on Intrepid-series directors provide full-duplex serial data transfer at a rate of 1.0625, 2.1250, or 10.2000 gigabits per second (Gbps). • Low communication overhead - Fibre Channel protocol provides efficient use of transmission bandwidth, reduces interlocked handshakes across the communication interface, and efficiently implements low-level error recovery mechanisms.
Page 34: Intrepid 6064 Director
Introduction to McDATA Multi-Protocol Products — A multiswitch fabric topology provides the ability to connect directors (and other McDATA switch elements) through expansion ports (E_Ports) and interswitch links (ISLs) to form a Fibre Channel fabric. Director elements receive data from a device and, based on the destination N_Port address, route the data through the fabric (and possibly through multiple switch elements) to the destination device.
Page 35 Introduction to McDATA Multi-Protocol Products Figure 1-2 Intrepid 6064 Director The director supports McDATA’s non-blocking extendable open network (EON™) architecture and concurrent firmware downloads ® through hot code activation (HotCAT ) technology. The director also provides a modular design that enables quick removal and replacement of FRUs, including: •...
Page 36: Intrepid 6140 Director
Introduction to McDATA Multi-Protocol Products — Universal port module (UPM) cards. Each UPM card provides four 2.1250 Gbps Fibre Channel port connections through duplex SFP fiber-optic transceivers. — Ten-gigabit port module (XPM) cards. Each XPM card provides one 10.2000 Gbps Fibre Channel port connection through a duplex ten-gigabit small form factor pluggable (XFP) fiber-optic transceiver.
Page 37 Introduction to McDATA Multi-Protocol Products Figure 1-3 Intrepid 6140 Director • A minimum of 16 to a maximum of 35 Fibre Channel port cards as follows: — UPM cards. Each UPM card provides four 2.1250 Gbps Fibre Channel port connections through duplex SFP fiber-optic transceivers.
Page 38: Intrepid 10000 Director
Introduction to McDATA Multi-Protocol Products Intrepid 10000 The Intrepid 10000 Director is a fourth-generation, enterprise-class Director product that provides switched fabric connectivity for up to 256 Fibre Channel devices operating at 1.0625 or 2.1250 Gbps, or up to 64 devices operating at 10.2000 Gbps. The product provides high- performance scalable bandwidth, highly-available operation, redundant switched data paths, long transmission distances (up to 2,200 km using a pool of programmable buffer-to-buffer credits), and...
Page 39 Introduction to McDATA Multi-Protocol Products concurrently upgraded. The combination of high port count and the FlexPar feature enables an enterprise to use the director at the core of both small and large SAN fabrics. For example: • Large fabrics built around the director require fewer fabric elements (directors and switches) and ISLs.
Page 40: Fabric Switches
Introduction to McDATA Multi-Protocol Products — Optical paddles that operate at 1.0625 or 2.1250 Gbps provide eight Fibre Channel port connections through duplex SFP fiber-optic transceivers. A fully-populated director supports up to 256 port connections at 1.0625 or 2.1250 Gbps data rates. —...
Page 41: Fabric Switch Performance
Introduction to McDATA Multi-Protocol Products Fabric Switch Fabric switches provide an availability of 99.9% through a redundant Performance configuration of power supplies and cooling fans. When an active FRU (power supply or fan) fails, the backup takes over operation automatically to maintain switch and Fibre Channel link operation. Availability is also provided through concurrent firmware upgrades and spare or unused Fibre Channel ports.
Page 42: Sphereon 4300 Fabric Switch
Introduction to McDATA Multi-Protocol Products • Up to 32 duplex SFP fiber-optic port transceivers. Shortwave laser transceivers are available for transferring data over multimode fiber-optic cable. Longwave laser transceivers are available for transferring data over singlemode fiber-optic cable. Fiber-optic cables attach to switch port transceivers with duplex LC connectors.
Page 43 Introduction to McDATA Multi-Protocol Products Switch ports can be configured as: • Fabric ports (F_Ports) to provide direct connectivity for switched fabric devices. • Fabric loop ports (FL_Ports) to provide switched arbitrated loop connectivity and fabric attachment for FC-AL devices. The switch supports: —...
Page 44: Sphereon 4400 Fabric Switch
Introduction to McDATA Multi-Protocol Products Sphereon 4400 The Sphereon 4400 Fabric Switch operates at 1.0625, 2.1250, or 4.2500 Fabric Switch Gbps, provides connectivity through 16 Fibre Channel generic mixed ports (GX_Ports), and supports EON architecture and HotCAT technology. Figure 1-7 illustrates the switch.
Page 45: Sphereon 4500 Fabric Switch
Introduction to McDATA Multi-Protocol Products • Up to 16 duplex SFP fiber-optic port transceivers. Tri-rate shortwave laser (1.0625, 2.1250, or 4.2500 Gbps) transceivers are available for transferring data over multimode fiber-optic cable. Tri-rate longwave laser transceivers are available for transferring data over singlemode fiber-optic cable.
Page 46 Introduction to McDATA Multi-Protocol Products Switch ports can be configured as: • F_Ports to provide direct connectivity for switched fabric devices. • FL_Ports to provide switched arbitrated loop connectivity and fabric attachment for FC-AL devices. The switch supports: — Connectivity of public loop devices and private loop devices. Refer to Public Versus Private Devices for information.
Page 47: Sphereon 4700 Fabric Switch
Introduction to McDATA Multi-Protocol Products Sphereon 4700 The Sphereon 4700 Fabric Switch operates at 1.0625, 2.1250, or 4.2500 Fabric Switch Gbps, provides connectivity through 32 Fibre Channel generic mixed ports (GX_Ports), and supports FICON, EON architecture, and HotCAT technology. Figure 1-9 illustrates the switch.
Page 48: San Routers
Introduction to McDATA Multi-Protocol Products • Up to 32 duplex SFP fiber-optic port transceivers. Tri-rate shortwave laser (1.0625, 2.1250, or 4.2500 Gbps) transceivers are available for transferring data over multimode fiber-optic cable. Tri-rate longwave laser transceivers are available for transferring data over singlemode fiber-optic cable.
Page 49: San Router Performance
Introduction to McDATA Multi-Protocol Products • Perform SAN routing functions - SAN routers provide FCP- protocol, router port (R_Port) connectivity between local Fibre Channel fabrics (SAN routing). A SAN routing solution provides interoperable FCP connectivity and consolidates IT resources but ensures a disruption in one fabric remains isolated and does not propagate to other fabrics.
Page 50: Eclipse 1620 San Router
Introduction to McDATA Multi-Protocol Products — Data compression - SAN router software identifies repetitive information in an output data stream and applies a compression algorithm to ensure the data is more compact and efficiently transmitted. — FastWrite technology - FastWrite software improves write performance over WANs by responding to initiator write commands with local transfer ready (XFR_RDY) commands, and buffering output data at the SAN router closest to the...
Page 51 Introduction to McDATA Multi-Protocol Products Eclipse 1620 SAN Router Figure 1-10 SAN router ports operate as follows: • Two user-configured FCP (FIBRE CHANNEL 1 and 2) ports provide 1.0625 Gbps Fibre Channel storage connectivity using SFP port connectors. FCP ports can be configured for: —...
Page 52: Eclipse 2640 San Router
Introduction to McDATA Multi-Protocol Products — IP network connectivity (iFCP or iSCSI protocol) at up to full-duplex GbE (1,000 Mbps) port transmission speed, using only the SFP port connector. Refer to Intelligent Port Speed detailed information. For SFP port connectors, shortwave laser transceivers are available for transferring data over multimode fiber-optic cable.
Page 53 Introduction to McDATA Multi-Protocol Products SAN router ports operate as follows: • Twelve user-configured FCP ports (1 through 12) provide 1.0625 or 2.1250 Gbps FCP storage connectivity and UDP-based network connectivity using SFP port connectors. FCP ports can be configured for: —...
Page 54: Product Features
Introduction to McDATA Multi-Protocol Products Product Features In addition to the characteristics and performance features described in this chapter, McDATA managed products also provide a variety of: • Connectivity features. • Security features. • Serviceability features. Connectivity McDATA directors, fabric switches, SAN routers, and their associated Features Element Manager applications support the following connectivity features.
Page 55 Introduction to McDATA Multi-Protocol Products • State change notification - Directors and the Sphereon 3232 Fabric Switch support a state change notification function that allows attached N_Ports to request notification when other N_Ports change operational state. Sphereon 4000-series fabric switches and FCP ports on SAN routers support a state change notification function that allows attached N_Ports and NL_Ports to request notification when fabric or loop-attached devices change operational state.
Page 56 Introduction to McDATA Multi-Protocol Products — Sphereon 4300 Fabric Switch - All switch ports are preset to a BB_Credit value of 5. By enabling the full fabric PFE key, the switch provides a port buffer pool of 144 receive BB_Credits and the per-port value is increased to 12, providing a data transmission distance of up to 24 km at 1.0625 Gbps and 12 km at 2.1250 Gbps.
Page 57: Security Features
Introduction to McDATA Multi-Protocol Products • Port binding - Directors and fabric switches support an optional feature that binds an attached Fibre Channel device to a specified product port through the device’s WWN. NOTE: SAN routers support port binding only for R_Ports. Security Features SAN management and Element Manager applications offer the following security features for McDATA switching products.
Page 58: Serviceability Features
Introduction to McDATA Multi-Protocol Products • Zoning - System administrators can create zones that provide product access control to increase network security, differentiate between operating systems, and prevent data loss or corruption. Zoning can be implemented in conjunction with server-level access control and storage device access control.
Page 59 Introduction to McDATA Multi-Protocol Products — Ethernet link status. — Fibre Channel link status. In addition, threshold alerts and a threshold alert log notify users when the transmit (Tx) or receive (Rx) throughput reaches a specified value for configured ports. •...
Page 60 Introduction to McDATA Multi-Protocol Products • Directors and fabric switches provide an internal modem for use by support personnel to dial in to the management server for event notification and to perform remote diagnostics. NOTE: SAN routers do not provide modem support. •...
Page 61 Introduction to McDATA Multi-Protocol Products • SNMP management for directors and fabric switches using the following MIBs as defined by Internet Engineering Task Force (IETF) working documents, request for comment (RFC) memorandums, and McDATA: — Fibre Channel Management Framework Integration MIB (FC-MGMT-MIB) - This MIB (also called the Fibre Alliance MIB) defines an integrated management environment for Fibre Channel-attached devices.
Page 62 Introduction to McDATA Multi-Protocol Products — VLAN Bridge MIB Module (Q-BRIDGE-MIB) - This MIB defines objects to manage virtual local area network (VLAN) bridging enhancements defined by IEEE 802.1Q-1998. — RFC 1213 - MIB-II - This MIB defines managed objects for the Internet community.
Page 63: Product Management
Product Management This chapter describes the management of McDATA multi-protocol products, including Intrepid-series directors, Sphereon-series fabric switches, and Eclipse-series SAN routers. The chapter specifically describes: • Product management, including out-of-band (non-Fibre Channel) methods, inband (fibre connection (FICON) or Fibre Channel) methods, and a management interface summary.
Page 64: Product Management
Product Management Product Management Out-of-band (non-Fibre Channel) management server access to all McDATA products is provided through an Ethernet local area network (LAN) connection on a director control processor (CTP) card, fabric switch front panel, or SAN router front panel. As an optional feature, inband (Fibre Channel or FICON) management access to selected McDATA products is provided through a Fibre Channel port connection.
Page 65 Product Management • Management using simple network management protocol (SNMP). An SNMP agent is implemented through the Element Manager application that allows administrators on SNMP management workstations to access product management information using any standard network management tool. Administrators can assign Internet protocol (IP) addresses and corresponding community names as follows: —...
Page 66 Product Management In contrast to the applications installed on the management server, EFCM Lite does not include support for the: — Call-home feature. — Ability to download remote clients from the server. Install clients on remote workstations from the software distribution disk provided with this management option.
Page 67: Inband Management
Product Management Inband The following inband management access methods are provided for Management directors and fabric switches as options: • Management through the product’s open-system management server (OSMS) that communicates with an application client. The application resides on an open-systems interconnection (OSI) device attached to a director or switch port, and communicates using Fibre Channel common transport (FC-CT) protocol.
Page 68: Management Interface Summary
Product Management S/390 or zSeries 900 Parallel Enterprise Server Host-Attached Console FICON Channel OSI Server Fibre Channel Connection Intrepid 6064 Director Inband Product Management Figure 2-2 Management Table 2-1 summarizes McDATA products and the out-of-band or Interface Summary inband management interfaces available to support the products. For each table cell, a green indicates the management interface supports the product, and a red...
Page 69: Management Server Support
Product Management Out-of-Band and Inband Product Support Summary (continued) Table 2-1 EFCM SANvergence EFCM Product SANavigator EFCM SNMP Basic OSMS Manager Lite Edition 4300 Fabric Switch 4500 Fabric Switch 1620 SAN Router 2640 SAN Router Management Server Support The management server is a one rack unit (1U) high, LAN-accessed, rack-mount unit that provides a central point of control for up to 48 connected directors, fabric switches, or SAN routers.
Page 70: Management Server Specifications
Product Management The server is dedicated to operation of the SAN management and associated Element Manager applications. These applications provide a GUI and implement web and other server functions. Refer SAN Management Applications for additional information. NOTE: The server and SAN management application provide a GUI to monitor and manage products and are a dedicated hardware and software solution that should not be used for other tasks.
Page 71 Product Management • 24X read speed slim-type compact disk-rewritable (CD-RW) and 8X read speed digital video disk (DVD) combination drive, data only. • 56K peripheral component interconnect (PCI) internal data and fax modem, using the V .92 dial-up specification. • 16 MB graphics card. •...
Page 72: Ethernet Hub
Product Management Ethernet Hub The management server and managed directors, fabric switches, and SAN routers connect through a 10/100 Base-T Ethernet hub. Figure 2-4 illustrates the 24-port hub. MDI X Po rt St at Gr ee n - 10 9 10 0M , Co llis Ba se...
Page 73: Product Firmware
— Linux-based system using an Intel Pentium III processor with ® one GHz or greater clock speed, using the Red Hat 7.3 or higher operating system. ® ® — Hewlett-Packard PA-RISC processor with 400 MHz or ® greater clock speed, using the HP-UX 11 or higher operating system.
Page 74: Firmware Services
Product Management • E/OSi - The Enterprise Operating System (internetworking) performs system configuration, management, and Fibre Channel and IP-based routing functions for Eclipse-series SAN routers. Firmware Services Director and fabric switch firmware (E/OSc and E/OSn) provides services that manage and maintain Fibre Channel connections between ports.
Page 75: Backup And Restore Features
Product Management • Fabric services - This function supports the fabric controller (login server) and name server. For redundant directors, fabric services also implement a replication manager that synchronizes node port (N_Port) registration databases between redundant CTP cards and allows CTP failover. •...
Page 76 Product Management — Operating parameters, such as buffer-to-buffer credit (BB_credit), error detect timeout value (E_D_TOV), resource allocation timeout value (R_A_TOV), switch priority, switch speed (1.0625 or 2.1250 Gbps), and preferred Domain_ID. — Active zoning configuration. — SNMP configuration parameters, such as trap recipients, community names, and write authorizations.
Page 77: San Management Applications
Product Management SAN Management Applications This section describes SAN management applications that provide a GUI to monitor, manage, and control directors, fabric switches, and SAN routers. SAN management applications include SANavigator , EFCM, and SANvergence Manager. An associated Element Manager application is provided for each managed product.
Page 78 Product Management • Centralized configuration - Vendor-specific device management applications can be launched from the SAN management application, including McDATA Element Manager applications. The application also provides management of director and switch zoning across multiple vendors and product models. • Monitoring and notification - The application provides real- time monitoring and event notification for devices in the SAN.
Page 79 Product Management Hardware View Figure 2-5 A status table appears at the top of the window, and a graphical representation of the hardware (front and rear) appears in the center of the window. The graphical representation of the product emulates the hardware configuration and operational status of the corresponding real product.
Page 80: Sanvergence Manager Application
Product Management A status bar at the bottom left corner of the view window displays colored icons (green circle, yellow triangle, red and yellow diamond, or grey square) that indicate the status of the selected managed product. Messages display as required to the right of the icons. SANvergence This section describes the SANvergence Manager and Element Manager...
Page 81 Product Management For additional information about the application, refer to the McDATA SANvergence Manager User Manual (620-000189). Element Manager An Element Manager application is provided for each managed SAN Application router. The application works in conjunction with the SANvergence Manager application and is a router-resident, Java-based applet for managing and monitoring the product.
Page 82: Efcm Basic Edition Interface
Product Management A menu bar at the top of the device window provides File, Configuration, Statistics/Info, Window, Options, and Help selections (with associated pop-up menus) that allow users to perform Element Manager tasks. EFCM Basic Edition Interface With E/OSc firmware installed, administrators or operators with a browser-capable PC and Internet connection can monitor and manage a product through the EFCM Basic Edition interface.
Page 83: Command Line Interface
Product Management The interface provides a GUI similar to the Element Manager application and supports product configuration, statistics monitoring, and basic operation. The EFCM Basic Edition interface manages only a single product (but has hyperlink access to other switches in a fabric). For additional information about the application, refer to the McDATA EFCM Basic Edition User Manual (620-000240).
Page 84 Product Management McDATA Products in a SAN Environment - Planning Manual 2-22...
Page 85: Planning Considerations For Fibre Channel Topologies
Planning Considerations for Fibre Channel Topologies A storage area network (SAN) is typically defined as a network of shared storage resources that can be allocated throughout a heterogeneous environment. This chapter describes planning considerations for incorporating McDATA products into Fibre Channel SAN topologies.
Page 86: Characteristics Of Arbitrated Loop Operation
Planning Considerations for Fibre Channel Topologies • Arbitrated loop - This topology uses a Sphereon 4000-series fabric switch to connect multiple device node loop ports (NL_Ports) in a Fibre Channel arbitrated loop (FC-AL) or hub configuration without benefit of a multiswitch fabric. Both switches support a switched mode topology that provides a single, logical connection between two device NL_Ports.
Page 87: Shared Mode Versus Switched Mode
Planning Considerations for Fibre Channel Topologies This section focuses on loop operation for Sphereon 4000-series fabric switches that operate at 1.0625, 2.1250, or 4.2500 gigabits per second (Gbps) and support FC-AL operation using FL_Ports and public and private device connectivity. Shared Mode Versus Legacy arbitrated loop switches (such as the McDATA ES-1000 Switched Mode...
Page 88: Switched Mode Operation And Logical Equivalent
Planning Considerations for Fibre Channel Topologies Part (A) of Figure 3-1 shows device D connected to server S through a pair of H_Ports. Although the remaining switch H_Ports (six ports) and device D are unavailable for connection, frame traffic between device D and server S travels through a loop that consists of all...
Page 89 Planning Considerations for Fibre Channel Topologies Part (A) of Figure 3-2 shows server S connected to device D through a switched pair of FL_Ports communicating at 1.0625 Gbps. Server S is connected to device D through a second switched pair of ports, also communicating at 1.0625 Gbps.
Page 90: Public Versus Private Devices
Planning Considerations for Fibre Channel Topologies Public Versus Private Sphereon 4000-series fabric switch support connection of public Devices and private arbitrated loop devices as follows: • Public device - A loop device that can transmit a fabric login (FLOGI) command to the switch, receive acknowledgement from the switch’s login server, register with the switch’s name server, and communicate with fabric-attached devices is a public device.
Page 91: Private Device Connectivity
Planning Considerations for Fibre Channel Topologies • Private device - A loop device that cannot transmit an FLOGI command to the switch nor communicate with fabric-attached devices is a private device. As shown in Figure 3-4, device D is a private loop device connected to a Sphereon 4500 Fabric Switch and cannot communicate with any fabric-attached device.
Page 92: Public Versus Private Loops
Planning Considerations for Fibre Channel Topologies Private devices only communicate with other devices on the same arbitrated loop, and interconnected public and private devices can communicate with each other. Such intermixed devices establish operating parameters and loop topology configuration through a port login (PLOGI) command exchange, rather than through the switch’s name server.
Page 93: Public Loop Connectivity
Planning Considerations for Fibre Channel Topologies Public Loop Connectivity Figure 3-5 • Private loop - A private loop is not connected to a switched fabric and the switch’s embedded FL_Port is inactive. All devices attached to the loop can only communicate with each other. Private loop connectivity for a Sphereon 4500 Fabric Switch is illustrated in Figure...
Page 94: Fl_Port Connectivity
Planning Considerations for Fibre Channel Topologies FL_Port Connectivity Sphereon 4000-series fabric switch provide loop connectivity through GX ports that are active as FL_Ports. The ports provide port addressing, physical connectivity, and Fibre Channel frame routing. Each FL_Port (and the embedded FL_Port) has a 24-bit address identifier.
Page 95: Planning For Fabric-Attached Loop Connectivity
Planning Considerations for Fibre Channel Topologies Planning for Fabric-Attached Loop Connectivity Public arbitrated loop topology supports the connection of workgroup or departmental FC-AL devices to a switched fabric through any Sphereon 4000-series fabric switch port active as an E_Port. This topology is well-suited to: •...
Page 96: Server Consolidation
Planning Considerations for Fibre Channel Topologies • Improved resource manageability. Distributed resources are consolidated and managed through Fibre Channel connectivity instead of physical relocation. One management server manages the operation and connectivity of multiple fabric directors, fabric- attached devices, arbitrated loop switches, and FC-AL devices. •...
Page 97: Tape Device Consolidation
Planning Considerations for Fibre Channel Topologies Server Consolidation Figure 3-7 Tape Device Providing fabric connectivity for multiple FC-AL tape drives by Consolidation attaching them individually to a Fibre Channel director is likewise not a cost-effective solution. A practical solution is to consolidate the tape drives on an inexpensive loop switch, then connect the switch to a director E_Port.
Page 98: Fabric Topologies
Planning Considerations for Fibre Channel Topologies Tape Drive Consolidation Figure 3-8 Fabric Topologies Several topologies exist from which to build a Fibre Channel fabric infrastructure. This section describes the most effective fabric topologies and provides guidance on when to deploy each topology. The topologies are effective for a wide variety of applications, are extensively tested by McDATA, and are deployed in several customer environments.
Page 99: Full Mesh Fabric
Planning Considerations for Fibre Channel Topologies Interswitch Link Fabric Connection Full Mesh Fabric Figure 3-9 Full-mesh fabrics provide increased resiliency over cascaded or ring fabrics and are well suited for applications that require any-to-any connectivity. If a single ISL fails, traffic is automatically routed through an alternate path.
Page 100: Core-To-Edge Fabric
Planning Considerations for Fibre Channel Topologies A modified or partial-mesh fabric is similar to a full-mesh fabric, but each switch does not have to be directly connected to every other switch in the fabric. The fabric is still resilient to failure but does not carry a cost premium for unused or redundant ISLs.
Page 101 Planning Considerations for Fibre Channel Topologies Tier 2 Devices Edge Switches Tier 1 Tier 1 Device Core Device Core Director Director Edge Switches Tier 2 Devices Interswitch Link Fabric Connection Figure 3-10 2-by-14 Core-to-Edge Fabric Each edge switch connects (through at least one ISL) to each core switch but not to other edge switches.
Page 102: San Islands
Planning Considerations for Fibre Channel Topologies • Tier 2 - A Tier 2 device connects to an edge switch and Fibre Channel traffic from the device must traverse only one ISL (hop) to reach a device attached to a core director or switch. •...
Page 103: Fabric Topology Limits
Planning Considerations for Fibre Channel Topologies Multiswitch Fabric D = Device ISL = Interswitch Link S = Fabric Switch (Director) Figure 3-11 Example Multiswitch Fabric A multiswitch fabric is typically complex and provides the facilities to maintain routing to all device N_Ports attached to the fabric, handle flow control, and satisfy the requirements of the classes of Fibre Channel service that are supported.
Page 104: Factors To Consider When Implementing A Fabric Topology
Planning Considerations for Fibre Channel Topologies • Heterogeneous fabric - Vendor interoperability in the fabric environment is supported; therefore, fabric elements can include directors, fabric switches, and open-fabric compliant products supplied by original equipment manufacturers (OEMs). To determine if interoperability is supported for a product or if communication restrictions apply, refer to the supporting publications for the product or contact McDATA.
Page 105 Planning Considerations for Fibre Channel Topologies • Distance requirements - The distance between elements in a fabric affects the type of optical port transceiver and cabling required. In addition, variables such as the number of connections, grade of fiber-optic cable, device restrictions, application restrictions, buffer-to-buffer credit limits, and performance requirements can affect distance requirements.
Page 106 Planning Considerations for Fibre Channel Topologies • Bandwidth - ISL connections can be used to increase the total bandwidth available for data transfer between two directors or switches in a fabric. Increasing the number of ISLs between elements increases the corresponding total ISL bandwidth but decreases the number of port connections available to devices.
Page 107 Planning Considerations for Fibre Channel Topologies When balancing a load across multiple ISLs, a director or switch attempts to avoid assigning multiple ports attached to a device to the same ISL. This minimizes the probability that failure of a single ISL will affect all paths to the device. However, because port assignments are made incrementally as devices log into the fabric and ISLs become available, optimal results are not guaranteed.
Page 108 Planning Considerations for Fibre Channel Topologies — If you have three fabric elements and set two to Principal and one to Default, the element with the Principal setting that has the lowest WWN becomes the principal switch. — If you have three fabric elements and set two to Default and one to Never Principal, the element with the Default setting and the lowest WWN becomes the principal switch.
Page 109 Planning Considerations for Fibre Channel Topologies If two operational fabrics join, they determine if any Domain_ID conflicts exist between the fabrics. If one or more conflicts exist, the interconnecting ISL E_Ports segment to prevent the fabrics from joining. To prevent this problem, it is recommended that all directors and switches be assigned a unique preferred Domain_ID.
Page 110 Planning Considerations for Fibre Channel Topologies Channel frames between devices attached to the fabric and enable operation of the fabric services firmware on each director or switch. Paths are determined when the fabric topology is determined and remain static as long as the fabric does not change. If the fabric topology changes (elements are added or removed or ISLs are added or removed), directors and switches detect the change and define new data transfer paths as required.
Page 111 Planning Considerations for Fibre Channel Topologies ATTENTION ! Activating a preferred path can result in receipt of out-of- order frames if the preferred path differs from the current path, if input and output (I/O) is active from the source port, and if congestion is present on the current path.
Page 112 Planning Considerations for Fibre Channel Topologies — No response from attached switch - After a fabric is created, each element in the fabric periodically verifies operation of all attached switches and directors. An ISL segments if a switch or director does not respond to a verification request. —...
Page 113: General Fabric Design Considerations
Planning Considerations for Fibre Channel Topologies — Fabric A zoned and Fabric B zoned - The fabrics join successfully only if the zone sets can be merged. If the fabrics cannot join, the connecting E_Ports segment and the fabrics remain independent. Zone sets for two directors or switches are compatible (the fabrics can join) only if the zone names for each fabric element are unique.
Page 114: Fabric Performance
Planning Considerations for Fibre Channel Topologies If the fabric consists of a large number of elements (and therefore ISLs), Class F traffic may not be processed within the E_D_TOV, resulting in error recovery operations, timeouts, segmented links, or fabric failure. Because of these problems, a fabric with a high ISL count is more difficult to build.
Page 115 Planning Considerations for Fibre Channel Topologies • Software limits, including the maximum number of fabric elements managed by the SAN management application and the maximum number of zones and zone members. For additional information, refer to SAN Management Applications Configuring Zones.
Page 116: Isl Oversubscription
Planning Considerations for Fibre Channel Topologies • I/O block size - The third characteristic of application I/O is data block size, which typically ranges from two kilobytes (KB) to over one megabyte (MB). Applications that generate large blocks of data require high bandwidth to the device. Prior to fabric design, application I/O profiles should be estimated or established that classify the application bandwidth requirements.
Page 117 Planning Considerations for Fibre Channel Topologies Two NT servers, each with maximum I/O of 100 MBps, are contending for the bandwidth of a single ISL operating at 1.0625 Gbps. In addition to data, the ISL must also transmit Class F traffic internal to the fabric.
Page 118 Planning Considerations for Fibre Channel Topologies High Device Locality Low Device Locality Low Traffic High Traffic Device Locality Figure 3-13 Although it is possible to design a SAN that delivers sufficient ISL bandwidth in a zero-locality environment, it is preferable to design local, one-to-one connectivity for heavy-bandwidth applications such as video server, seismic data processing, or medical 3D imaging.
Page 119: Device Fan-Out Ratio
Planning Considerations for Fibre Channel Topologies Device Fan-Out Ratio: 10 to 1 1,000 IOPS 1,000 IOPS 1,000 IOPS 1,000 IOPS 10,000 IOPS 1,000 IOPS 1,000 IOPS 1,000 IOPS 1,000 IOPS 1,000 IOPS Interswitch Link Fabric Connection 1,000 IOPS Device Fan-Out Ratio Figure 3-14 Performance Tuning When designing or tuning a fabric for performance, it is critical to...
Page 120: Fabric Performance Tuning
Planning Considerations for Fibre Channel Topologies Tier 2 Storage 11 to 1 Fan-Out Region 6 to 1 Fan-Out Region 3 to 1 Fan-Out Region 11,000 IOPS 9,000 IOPS 6,000 IOPS Local Tier 1 Devices 2,000 IOPS 6,000 IOPS 40 MBps 2,000 IOPS 6 Total 11 Total...
Page 121: Fabric Availability
Planning Considerations for Fibre Channel Topologies • 11 to 1 fan-out region - Eleven NT servers with I/O capabilities of 10 MBps and 1,000 IOPS are fabric-attached through a 32-port edge switch. The primary applications are e-mail and online transaction processing (OLTP). Because bandwidth use is light and noncritical, the servers are connected to the core director with a single ISL that is intentionally oversubscribed (1.1 Gbps plus Class F traffic).
Page 122 Planning Considerations for Fibre Channel Topologies • Resilient single fabric - Directors and switches are connected to form a single fabric, but no single point of failure can cause the fabric to fail and segment into two or more smaller fabrics. •...
Page 123: Fabric Scalability
Planning Considerations for Fibre Channel Topologies Fabric Fabric “A” “B” Interswitch Link Fabric Connection Redundant Fabrics Figure 3-16 When deploying redundant fabrics, it is not required that the fabrics be symmetrical. As an example, single-attached devices, such as tape drives and noncritical servers and storage, can be logically grouped and attached to one of the fabrics.
Page 124: Obtaining Professional Services
Planning Considerations for Fibre Channel Topologies • High-port count directors - Installing high-port count directors as SAN building blocks provides a larger number of non-blocking Fibre Channel ports per fabric element and reduces the need for ISLs. Newer products support high-bandwidth (10.2000 Gbps) ISLs that also reduce the fabric ISL count.
Page 125: Fcp And Ficon In A Single Fabric
Planning Considerations for Fibre Channel Topologies FCP and FICON in a Fibre Channel Layer 4 (FC-4) describes the interface between Fibre Single Fabric Channel and various upper-level protocols. FCP and FICON are the major FC-4 protocols. FCP is the Fibre Channel protocol that supports the small computer system interface (SCSI) upper-level transport protocol.
Page 126 Planning Considerations for Fibre Channel Topologies • When a director or fabric switch is set to open systems management style, FCP connectivity is defined within a Fibre Channel fabric using WWNs of devices that are allowed to form connections. When connecting to the fabric, an FCP device queries the name server for a list of devices to which connectivity is allowed.
Page 127: Intrepid 6140 Port Numbers And Logical Port Addresses (Front)
Planning Considerations for Fibre Channel Topologies • The Domain_ID and physical port number of the director or fabric switch port to which a device is attached. FICON configuration attributes are implemented through logical port addressing. This concept is consistent with the address-centric nature of FICON and allows ports to be swapped for maintenance operations without regenerating a host configuration.
Page 128: Intrepid 6140 Port Numbers And Logical Port Addresses (Rear)
Planning Considerations for Fibre Channel Topologies Figure 3-18 illustrates port numbering and logical port addressing for Intrepid 6140 Director ports accessed from the rear. UPM Cards UPM Cards SBAR - 1 Module SBAR - 0 Module Intrepid 6140 Port Numbers and Logical Port Addresses (Rear) Figure 3-18 The figure shows: •...
Page 129 Planning Considerations for Fibre Channel Topologies • FICON port-to-port connectivity is hardware enforced, while FCP port-to-port connectivity is software or hardware enforced (depending on the director or switch firmware release level). — FICON architecture controls connectivity through a host-based HCD program, the CUP, and a director or switch-resident PDCM array.
Page 130 Planning Considerations for Fibre Channel Topologies • When employing inband (Fibre Channel) director or switch management, the open-systems management server (OSMS) is associated with the FCP protocol, and the FICON management server (FMS) is associated with the FICON protocol. Management server differences tend to complicate security and control issues.
Page 131 Planning Considerations for Fibre Channel Topologies SANtegrity Binding McDATA offers a SANtegrity Binding feature (including both fabric binding and switch binding) that allows the creation of reliable SAN configurations and provides a mechanism for attached devices to query the user-configured security level employed in a SAN. The feature significantly reduces the impacts of accidental or operator- induced errors.
Page 132 Planning Considerations for Fibre Channel Topologies However, the firmware and SAN management applications do not prevent FCP and FICON device configurations that may interfere with each other. A successful intermix environment requires a set of best practice conventions as follows: 1.
Page 133 Planning Considerations for Fibre Channel Topologies — When using inband director or switch management, either (or both) of the FMS or OSMS features can be enabled. When either (or both) features are enabled, the director or switch can be set to open systems or FICON management style. 3.
Page 134 Planning Considerations for Fibre Channel Topologies 6. Configure PDCM arrays - For each director or switch managed by the FICON management style, define the allow and prohibit settings for FICON device connectivity. Use the Element Manager application’s Configure Allow/Prohibit Matrix - Active dialog box. Port connectivity assignment (step 4) should be reflected in...
Page 135: Multiple Data Transmission Speeds In A Single Fabric
Planning Considerations for Fibre Channel Topologies — All FICON devices must be included in the same zone to facilitate proper state change notification. This is achieved by creating a unique FICON zone or using the default zone. Disable the default zone and explicitly create a unique zone for all FICON devices.
Page 136: Ficon Cascading
Planning Considerations for Fibre Channel Topologies • Better fabric performance - As a connection between fabric switches, a 10.2000 Gbps ISL delivers significantly greater bandwidth. Fibre Channel devices that are not 10.2000 Gbps- capable benefit from a higher-speed ISL, because slower traffic is multiplexed and transmitted through the 10.2000 Gbps ISL.
Page 137: High-Integrity Fabrics
Planning Considerations for Fibre Channel Topologies High-Integrity Cascaded FICON directors and switches must support high-integrity Fabrics fabrics. McDATA fabric elements must have the SANtegrity Binding feature installed and operational with Enterprise Fabric Mode enabled. High-integrity fabric architecture support includes: • Fabric binding - Only directors or switches with fabric binding installed are allowed to attach to specified fabrics in a SAN.
Page 138: Ficon Cascading Best Practices
Planning Considerations for Fibre Channel Topologies — Intrepid 6064 or 6140 Director. — Sphereon 3232 or 4500 Fabric Switch. • E/OSc Version 4.0 (or later) must be installed on all directors or switches. E/OS firmware Version 6.0c (or later) is recommended. All fabric elements must be at the same firmware version level.
Page 139 Planning Considerations for Fibre Channel Topologies c. Ensure the R_A_TOV and E_D_TOV values for fabric elements are identical. d. Route multimode or singlemode fiber-optic cables (depending on the type of transceiver installed) between customer-specified E_Ports at each fabric element. 2. Verify operation of local FICON applications - Ensure the ISL connection(s) do not disrupt fabric element operation nor disrupt local FICON (non-cascaded) traffic.
Page 140 Planning Considerations for Fibre Channel Topologies b. At the SAN management application, configure fabric binding. Refer to installation instructions in the SANavigator Software Release 4.2 User Manual (621-000013) or the EFC Manager Software Release 8.7 User Manual (620-000170). c. At the Element Manager application, configure switch binding.
Page 141 Planning Considerations for Fibre Channel Topologies b. Ensure the Enable Switch Binding check box is checked (enabled). c. Select (click) the Restrict E_Ports radio button to restrict connections from specific fabric elements to E_Ports. WWNs can be added to the membership list to allow fabric element connection and removed from the list to prohibit fabric element connection.
Page 142 Planning Considerations for Fibre Channel Topologies 11. Verify cascaded FICON operation - Have the customer verify operation of established logical FICON paths between channels and control units, and verify that cascaded FICON traffic is transmitted through the fabric as expected. McDATA Products in a SAN Environment - Planning Manual 3-58...
Page 143: Implementing San Internetworking Solutions
Implementing SAN Internetworking Solutions Enterprise-level information technology (IT) departments often deploy storage configurations that include direct-attached storage, network-attached storage (NAS), and small, isolated storage area networks (SANs). These configurations often result in: • Isolated and inefficiently-used applications, data storage, and computing resources.
Page 144: San Island Consolidation
Implementing SAN Internetworking Solutions SAN Island Consolidation SAN islands tend to be constructed along application (such as product test, finance, or engineering), operating system (OS), protocol, or geographical (site-based) boundaries. Because of application and OS segmentation, large data centers at single sites often consist of SAN islands constructed with relatively small Fibre Channel switches.
Page 145 Implementing SAN Internetworking Solutions • Inability to consistently schedule maintenance downtime for each SAN. • Stranded resources. Unused ports in one SAN cannot be used by applications in another (port limited) SAN, and expensive resources (such as tape backup elements) cannot be easily shared across SAN boundaries.
Page 146: Flexible Partitioning Technology
Implementing SAN Internetworking Solutions Another persistent problem associated with large Fibre Channel fabrics is multi-vendor incompatibility. Due to lack of common communications standards and fabric shortest path first (FSPF) protocol, switch vendors may have to support multiple (standards- compliant and proprietary) interoperability modes. In addition, protocol enhancements may force vendors to support multiple firmware versions for the same product.
Page 147: Intrepid 10000 Director Flexpar Functionality
Implementing SAN Internetworking Solutions This feature reduces unused ports and resources and consolidates the enterprise into a single infrastructure, while maintaining multiple independent application and fault isolation domains. Up to four partitions can be enabled for each director (0 though 3), where a partition consists of one or more line modules (LIMs).
Page 148 Implementing SAN Internetworking Solutions • Create up to three additional FlexPars and assign resources to those FlexPars. • Perform director firmware upgrades to all Flexpars. • Enable or disable the protocol subsystem for any Flexpar. • Enable or disable switch modules and control processor (CTP) cards.
Page 149 Implementing SAN Internetworking Solutions Zone FlexPars implement an RSCN zone isolation feature that prevents fabric-format RSCNs from propagating to devices in zones not impacted by the RSCN. With zone FlexPars enabled, zoning change RSCNs are handled like device availability change RSCNs. Because the feature is device centric, zone FlexPars work in loop environments and with node port ID virtualization (NPIV) enabled.
Page 150: San Routing
Implementing SAN Internetworking Solutions SAN Routing Connecting isolated, department-level, and application-specific Fibre Channel SANs is a requirement for most enterprises. Consolidating SAN islands: • Provides campus storage connectivity and interoperability between formerly-incompatible Fibre Channel fabrics (from the same or different vendors). •...
Page 151: San Routing Hierarchy
Implementing SAN Internetworking Solutions • Tier 2 - To connect SAN islands without physically merging the fabrics, the second tier consists of metropolitan storage area networks (mSANs). SAN routers connect fabrics within a data center or campus to form an mSAN and transmit data between fabrics through router ports (R_Ports).
Page 152: San Routing Concepts
Implementing SAN Internetworking Solutions SAN Routing Concepts Figure 4-3 The following sections discuss SAN routing concepts, including: • R_Port operation. • Routed SAN zoning. • mSAN routing. • iFCP operation. • iSAN routing. • Inter-FlexPar routing. • Best practices. McDATA Products in a SAN Environment - Planning Manual 4-10...
Page 153: San Routing - Physical Connectivity
Implementing SAN Internetworking Solutions R_Port Operation To avoid building a large Fibre Channel fabric with its inherent reconfiguration issues, SAN Routing provides any-to-any connectivity (to maximize use of common assets across SAN islands), while retaining the fault isolation characteristics of smaller SANs. SAN routers also support multiple R_Port compatibility modes, making it possible to route OEM versions of a vendor switch, direct- marketed versions of a vendor switch, and switches produced by...
Page 154 Implementing SAN Internetworking Solutions Instead of Class F frame transmission, routing communication is provided by Fibre Channel network address translation (FC_NAT) technology. This is similar to the technology used by IP networks to convert private addresses to public addresses. The principal switch in each router-connected fabric assigns the Domain_ID to the associated R_Port acting as an edge switch.
Page 155: San Routing - Logical Connectivity
Implementing SAN Internetworking Solutions NOTE: Proxy Domain_IDs 30 and 31 are reserved for routing domains and cannot be assigned to directors or switches in any router-attached fabric. The routing domain with proxy Domain_ID 30 represents Fibre Channel devices that are part of a router-attached fabric (part of a local mSAN).
Page 156 Implementing SAN Internetworking Solutions For attached fabrics in which participating element’s Interop Mode is set to McDATA Fabric 1.0, Domain_IDs of 30 and 31 are recognized by SAN management applications and all attached devices. For attached fabrics in which participating element’s Interop Mode is set to Open Fabric 1.0, Domain_IDs of 30 and 31 are recognized by SAN management applications.
Page 157 Implementing SAN Internetworking Solutions R_Port Domain_ID Assignment The default preferred Domain_ID for each SAN router R_Port is 1. However, each port should be assigned a preferred Domain_ID (set at the R_Ports tab of the Fabric Configuration dialog box) that is unique within the attached fabric.
Page 158 Implementing SAN Internetworking Solutions There is only one router fabric manager per fabric. If more than one R_Port (from the same or multiple routers) connects to a fabric, then the port with the lowest worldwide name (WWN) is elected router fabric manager for that fabric.
Page 159 Implementing SAN Internetworking Solutions A No Zone Synchronization policy is typically not suitable for larger SAN routing environments where many devices must be visible to numerous fabrics. Append IPS Zones When the zone policy is set to Append IPS Zones, Internet protocol storage (IPS) zone set information from the router is appended to the active zone set for every router-attached fabric in the mSAN.
Page 160: Msan Routing Domain
Implementing SAN Internetworking Solutions mSAN Routing An mSAN consists of one or two SAN routers that interconnect up to six Fibre Channel fabrics. These fabrics are typically dispersed within a data center or metropolitan campus. If two SAN routers are used, they are connected with multiple (one to four) Gigabit Ethernet (GbE) bandwidth IRLs.
Page 161 Implementing SAN Internetworking Solutions During SAN router configuration, each R_Port is assigned (through the SANvergence manager application) a unique Fabric_ID between 1 and 12. Although the theoretical limit is 12 Fabric_IDs per mSAN, the supported limit is six. As shown in Table 4-1, four Area_IDs are available to each Fabric_ID.
Page 162 Implementing SAN Internetworking Solutions Router Connectivity through mFCP mFCP provides connectivity (through a GbE-bandwidth IRL) between two Eclipse 2640 SAN Routers. mFCP is similar to Fibre Channel protocol (FCP) but implements user datagram protocol (UDP) for open systems interconnection (OSI) Layer 4 transport. mFCP links are used for path failover in high-availability mSANs.
Page 163: Msan Supported Limits
Implementing SAN Internetworking Solutions If a direct Fibre Channel connection exists between routed fabrics, storage traffic traverses the Fibre Channel ISL and not the router- to-router mFCP link. Only SNS traffic traverses the mFCP link. However, if a router-to-router mFCP link is the only path between two Fibre Channel devices, the link is traversed by storage traffic.
Page 164 Implementing SAN Internetworking Solutions iFCP Operation There are three protocols competing to transmit storage-related I/O traffic over long-distance transmission control protocol/Internet protocol (TCP/IP) links: • iSCSI is a TCP/IP-based protocol for establishing and managing connections between IP-based storage devices, hosts, and clients. iSCSI operates on top of TCP, moving block data (iSCSI packets) over an IP Ethernet network.
Page 165 Implementing SAN Internetworking Solutions From the standpoint of fabric build events, the only difference between a local and stretched E_Port connection is the latency introduced by the TCP/IP link and associated WDM or FCIP hardware. A disruptive build fabric event at one local site propagates to the connected site.
Page 166: Ifcp Wan Extension
Implementing SAN Internetworking Solutions iFCP WAN Extension Figure 4-6 iSAN Routing An internetworked SAN (iSAN) is a network composed of multiple Fibre Channel fabrics or mSANs, connected by one or more SAN routers, where at least one fabric is remotely located and connected through a WAN.
Page 167 Implementing SAN Internetworking Solutions SAN Routing also streamlines SAN connectivity by eliminating network address issues associated with duplicate Domain_IDs. Because fabric elements and devices at either end of an iFCP connection remain in separate mSANs, address conflicts between the mSANs do not occur. SAN Routing provides address translation (through FC_NAT) for zoned devices with authorization to communicate across the network.
Page 168 Implementing SAN Internetworking Solutions • Rate limiting - If ingress traffic enters the SAN router faster than egress traffic leaves, port buffers fill and cause dropped data packets. Dropped packets cause TCP to resort to internal (and inefficient) flow control, causing dramatic link throughput decrease.
Page 169 Implementing SAN Internetworking Solutions and results in a lower compression bandwidth. The algorithm has an average compression ratio increase of approximately 30% over LZO. The algorithm is recommended when up to 8 TCP sessions are used and the available bandwidth is between 10 Mbps (thin Ethernet) and 45 Mbps (DS3 transport level).
Page 170: Mfcp Versus
Implementing SAN Internetworking Solutions mFCP to iFCP Table 4-3 compares mFCP to iFCP and summarizes the features of Comparison each protocol. mFCP Versus iFCP Table 4-3 Feature mFCP iFCP Purpose LAN protocol to support short-distance SAN WAN Protocol to support extended-distance router connectivity SAN router connectivity OSI Layer 4 protocol...
Page 171 Implementing SAN Internetworking Solutions Figure 4-7 illustrates inter-FlexPar routing. Flexpar B (tape backup fabric) is isolated from Flexpar C (product development fabric) as normally desired. However, development personnel occasionally perform tape backups that require access to Flexpar B devices. An E_Port from each FlexPar is physically connected to a SAN router R_Port, and Flexpar C servers are zoned to communicate with Flexpar B tape devices.
Page 172 Implementing SAN Internetworking Solutions 2. Domain_ID assignment - Manually assign unique Domain_IDs to all Fibre Channel directors, fabric switches, and SAN router R_Ports. Ensure the Insistent Domain_ID option is enabled at the SAN management or SANvergence Manager application. Do not assign Domain_ID 30 or 31 to any fabric elements.
Page 173 Implementing SAN Internetworking Solutions 7. Use redundant mFCP connections - For high availability (not increased bandwidth), use multiple mFCP connections between SAN routers to ensure the mSAN does not partition and connectivity to routing domains 30 and 31 remains intact. 8.
Page 174 Implementing SAN Internetworking Solutions Local mSAN Name: Boston Local mSAN_ID: 20 Date: 1/12/05 Exported Zone_ID Range: 1 to 100 Local Zone_ID Range: 101 to 512 Local mSAN Zone Summary Exported mSAN ID mSAN Name Description (Y/N) DB_Replication_2 Remote site for disaster recovery. Tape_Library_3 Remote site for data center tape library access.
Page 175 Implementing SAN Internetworking Solutions Local mSAN Name: Chicago Local mSAN_ID: 30 Date: 1/12/05 Exported Zone_ID Range: 1 to 100 Local Zone_ID Range: 101 to 512 Local mSAN Zone Summary Exported mSAN ID mSAN Name Description (Y/N) DB_Replication_2 Replication site for disaster recovery. Web_Server Local web server and associated hardware.
Page 176 Implementing SAN Internetworking Solutions 12. Configure R_Ports - For all configured SAN router R_Ports in the same fabric: a. The R_Port interconnect modes (McDATA Fabric 1.0 or Open Fabric 1.0) must be identical. This parameter is set at the SANvergence Manager application. The corresponding E_Port interoperability mode must also be identical.
Page 177 Implementing SAN Internetworking Solutions c. Port zoning can be confusing in a multi-vendor environment because OEMs implement zoning in different ways. When zoning with vendor-specific SAN management applications, zone through port WWNs, not node (device) WWNs. d. Ensure devices are physically connected before importing their node (device) WWNs to a router.
Page 178: Implementing Bc/Dr Solutions
Implementing SAN Internetworking Solutions Implementing BC/DR Solutions The post-9/11 business environment requires corporations to protect critical data by implementing cost-effective business continuity and disaster recovery (BC/DR) solutions. These BC/DR solutions drive the requirement to extend local data center SANs to geographically distant locations.
Page 179: Extended-Distance Operational Modes
Implementing SAN Internetworking Solutions • Reliability - Local storage traffic requires high-reliability communication and is intolerant of data loss, out-of-order packet receipt, or data retransmission. WANs typically provide best- effort communication service and rely on upper-level protocols for end-to-end transport. Because of these differences, a protocol conversion approach is usually required to integrate Fibre Channel SAN traffic over a geographically-dispersed network.
Page 180 Implementing SAN Internetworking Solutions • Synchronous remote data replication (RDR/S) - This operational mode ensures a remote data copy (identical to the primary copy) is created at the time the primary data is created. An update operation does not complete until confirmed at both the primary and mirrored sites.
Page 181: San Extension Transport Technologies
Implementing SAN Internetworking Solutions SAN Extension There are several extension transport technologies available to Transport connect geographically-dispersed SAN islands, all of which differ in Technologies performance, latency, and implementation cost. The primary technologies include: • Dark fiber (repeated or unrepeated). •...
Page 182: Dark Fiber Extended-Distance Connectivity
Implementing SAN Internetworking Solutions • Creates one logical Fibre Channel fabric through a stretched E_Port connection. The connection is vulnerable to disruptions caused by events at each site or to disruptions caused by problems with the extended-distance dark fiber link. Dark Fiber Extended-Distance Connectivity Figure 4-8 Due to the high cost of burying cables, dark fiber has limited physical...
Page 183: Wdm Extended-Distance Connectivity
Implementing SAN Internetworking Solutions Light wavelengths used are typically around 1,550 nanometers (nm). Optical fiber performs well in this wavelength region, with very little attenuation. For CWDM, differing wavelengths are separated by multiples of 20.0 nm. For DWDM, differing wavelengths are separated by multiples of 0.8 nm.
Page 184 Implementing SAN Internetworking Solutions • Requires sufficient BB_Credits assigned to the link (such as credits available through the Intrepid 10000 Director buffer pool). Because WDM is a method to transmit multiple signals over the same fiber-optic cable, there is no BB_Credit limitation difference between WDM and dark fiber.
Page 185: Sonet Extended-Distance Connectivity
Implementing SAN Internetworking Solutions SONET and SDH are globally standardized technologies, more widely deployed than dark fiber or WDM, and provide a protected connection between two locations. SONET and SDH rings are also self-healing. This means a link is usually restored within 50 ms of break detection without user intervention.
Page 186 Implementing SAN Internetworking Solutions • Does not require Fibre Channel BB_Credits assigned to the link because buffering is built in to the GFP function to enable long-distance transmission of storage traffic. • Creates a routed iSAN or one logical Fibre Channel fabric through a stretched E_Port connection, depending upon the protocol and if one or more SAN routers are deployed in the link.
Page 187 Implementing SAN Internetworking Solutions SONET or SDH service can be purchased on a monthly basis in accordance with a negotiated SLA. However, the transport links may require sufficient BB _Credits to use the purchased bandwidth. Because of BB_Credit limitations, GFP equipment must provide buffering and flow control for native FCP or FICON storage data.
Page 188: Soip Extended-Distance Connectivity
Implementing SAN Internetworking Solutions routed SAN connection ensures disruptions at one site are isolated and not allowed to propagate to other locations. This connection does not support native FCP or FICON operation. SoIP Extended-Distance Connectivity Figure 4-11 Several network service providers provide long-distance IP or GbE network transport services.
Page 189: San Extension Technology Comparison
Implementing SAN Internetworking Solutions SAN Extension Technology Comparison Figure 4-12 • WDM - This technology supports high-bandwidth, low-latency applications with short RTO and RPO requirements. Applications include peer-to-peer computer clustering (grid computing) and real-time disk mirroring (RDR/S or RDR/A operational mode) over short to medium metropolitan distances.
Page 190 Implementing SAN Internetworking Solutions • IP - This technology supports low-bandwidth, high-latency applications with long RTO and RPO requirements. Applications include asynchronous disk backup or tape vaulting over metropolitan to extended (intercity) distances. SAN routers are included in the extended-distance link (iFCP only), so the technology isolates the connected SANS and prevents disruptions caused by fabric or link problems.
Page 191: Distance Extension Through Bb_Credit
Implementing SAN Internetworking Solutions • SAN routing requirements - If a single logical Fibre Channel fabric (created through a stretched E_Port connection) is unacceptable because of the potential for disruptive fabric rebuilds, include one or more SAN routers in the extended- distance link.
Page 192 Implementing SAN Internetworking Solutions To support greater Fibre Channel transmission rates (long-link ports), the Intrepid 10000 Director provides a buffer pool that allocates user-defined BB_Credits to each port. This buffer pool is increased if the remote fabric PFE key is enabled (refer to Remote Fabric information).
Page 193: Intelligent Port Speed
Implementing SAN Internetworking Solutions • 10.2000 Gbps long link (mixed paddles) - A paddle pair with one 1.0625 or 2.1250 Gbps paddle and one 10.2000 Gbps paddle provides ten connections. 16 BB_Credits are assigned to the slowest eight short-link ports, and 96 BB_Credits are assigned to one 10.2000 Gbps short-link port (224 BB_Credits total).
Page 194: Wan Link Performance (Rate Limiting Enabled)
Implementing SAN Internetworking Solutions WAN Link Performance (Rate Limiting Enabled) Figure 4-14 When configuring a SAN router for extended-distance operation over an IP WAN link, the peak available bandwidth must be determined or obtained from the network service provider, and storage traffic over the link must be rate-limited accordingly.
Page 195 Implementing SAN Internetworking Solutions • Digital Signal 1 (DS1) - A framing and formatting specification that transmits 24 digital data channels on a T1 synchronous line. Each channel transmits at 64 Kbps (full-duplex), providing an aggregate bandwidth of 1.544 Mbps. Typical T1 lines are long-distance, point-to-point connections used for private networks and corporate Internet communication.
Page 196 Implementing SAN Internetworking Solutions • Fast Ethernet - A transmission medium specified by IEEE 802.3 that carries information at 100 Mbps (full-duplex) in baseband form using Category-5 copper cable or fiber-optic cable. The specification was developed to enable faster communication of LAN-connected computers.
Page 197: Distance Extension Best Practices
Implementing SAN Internetworking Solutions Distance Extension To implement a successful extended-distance BC/DR solution, follow Best Practices a set of best practice conventions as follows: 1. Use dedicated bandwidth and rate limiting - If possible, negotiate dedicated bandwidth as part of the SLA with the network service provider.
Page 198 Implementing SAN Internetworking Solutions — Jumbo frames - To prevent fragmentation of Fibre Channel frames into multiple IP datagrams, enable jumbo frames to increase the data packet size from 1,500 bytes to approximately 9,000 bytes. Ensure the technology is supported by all IP network equipment in the data link. —...
Page 199 Implementing SAN Internetworking Solutions 6. Do not implement IP network failover - Implement extended- distance link failover through the remote data replication software, not the IP network. Many RDR/S and RDR/A software OEMs do not support IP network link failover. 7.
Page 200: Consolidating And Integrating Iscsi Servers And Storage
Implementing SAN Internetworking Solutions 13. Configure out-of-band product management - SAN routers can be managed through inband or out-of-band connectivity. Inband management is provided through the same GbE connections used for iFCP storage traffic. Out-of-band management is provided through a data center LAN that connects servers, workstations, and other network-related equipment.
Page 201: Iscsi Protocol
Implementing SAN Internetworking Solutions The following sections describe: • iSCSI protocol. • iSCSI server consolidation. • SCSI storage consolidation. iSCSI Protocol iSCSI is based on SCSI protocol that enables hosts to perform block data I/O operations with a variety of target peripherals. Targets include disk drives, tape devices, optical storage devices, printers, and scanners.
Page 202: Iscsi Server Consolidation
Implementing SAN Internetworking Solutions iSCSI Server Many enterprise-level IT departments have deployed decentralized Consolidation computing configurations that include low-end, iSCSI-enabled servers directly attached to storage. While server acquisition costs are typically low, licensing and maintenance costs are often very high in terms of dollars and personnel time.
Page 203: Iscsi Storage Consolidation
Implementing SAN Internetworking Solutions As shown in the figure, server consolidation is enabled by installing an Eclipse 2640 SAN Router that provides iSCSI-to-native FCP connectivity. Stranded servers subject to consolidation do not require installation at one physical location. Servers may be located in a data center or remotely;...
Page 204 Implementing SAN Internetworking Solutions McDATA Products in a SAN Environment - Planning Manual 4-62...
Page 205: Physical Planning Considerations
Physical Planning Considerations This chapter describes physical planning considerations for incorporating McDATA directors and switches into storage area networks (SANs) and Fibre Channel fabric topologies. The chapter provides planning considerations and recommendations for: • Port connectivity and fiber-optic cabling. • Rack-mount management server, Ethernet local area network (LAN), and remote access support.
Page 206: Port Requirements
Physical Planning Considerations Port Requirements Plan for sufficient shortwave laser, longwave laser, and 1.0625, 2.1250, 4.2500, and 10.2000 gigabit per second (Gbps) Fibre Channel ports to meet the needs of the SAN configuration. The number of ports required is equal to the number of device connections (including redundant connections), plus the number of interswitch links (ISLs) between fabric elements, plus the total number of spare port connections.
Page 207 Physical Planning Considerations — Optical paddles that operate at 10.2000 Gbps provide two Fibre Channel port connections. A fully-populated director supports up to 64 connections and can be configured with a combination of shortwave or longwave transceivers. • Sphereon 3232 Fabric Switch - The switch provides up to 32 duplex SFP fiber-optic port transceivers (1.0625 or 2.1250 Gbps operation).
Page 208: Sfp Optical Transceivers
Physical Planning Considerations SFP Optical Shortwave laser SFP optical transceivers (1.0625, 2.1250, 4.2500, or Transceivers 10.2000 Gbps) provide a connection for multimode cable with a core diameter of 50 microns and a cladding diameter of 125 microns (50/125 micron), or multimode cable with a core diameter of 62.50 microns and a cladding diameter of 125 microns (62.5/125 micron).
Page 209: Cable Type And Transmission Rate Versus Distance And Link Budget
Physical Planning Considerations When using multimode cable, note the decrease in performance as the cable core diameter or data transmission rate increases. When using singlemode cable, performance is a function of transceiver type. Data transmission distance and link budget are not affected by data transmission rate.
Page 210: Extended-Distance Ports
Physical Planning Considerations • Existing cable restrictions - The enterprise may contain only one type of fiber-optic cable (multimode or singlemode), and the customer may be required to use the existing cables. Customers may also be required to use existing copper cables for some arbitrated loop devices.
Page 211: Fibre Channel Cables And Connectors
Physical Planning Considerations Fibre Channel This section provides Fibre Channel cable and connector planning Cables and information as follows: Connectors • Cables for directors, fabric switches, and SAN routers. • Intrepid-series director, Sphereon-series fabric switch, and Eclipse-series SAN router optical connectors. Cables Fiber-optic jumper cables are required to connect directors, fabric switches, and SAN routers ports to servers, devices, distribution...
Page 212: Routing Fiber-Optic Cables
Physical Planning Considerations Figure 5-1 SFP Transceiver and LC Duplex Connector Routing Fiber-Optic Follow a logical plan for routing fiber-optic cables to avoid confusing Cables connections during installation and operation. Route cables from the access holes at the bottom of the Fabricenter equipment cabinet to fabric element ports.
Page 213: Management Server, Lan, And Remote Access Support
Physical Planning Considerations • Cable routing outside the equipment cabinet. Plan for 1.5 meters (5 feet) of cable outside the cabinet to provide slack for service clearance, limited cabinet movement, and inadvertent cable pulls. • Cabling distance to servers, storage devices, and directors (for multiswitch fabric support).
Page 214: Management Server
Physical Planning Considerations Management The management server is rack-mounted in a Fabricenter equipment Server cabinet. The server supports up to 48 McDATA directors, fabric switches, or SAN routers (managed products). The server is used to configure the product and associated SAN management and Element Manager applications, monitor product operation, change configurations, download firmware updates, and initiate diagnostics.
Page 215: Remote User Workstations
Physical Planning Considerations Connectivity Planning Directors, fabric switches, SAN routers, and the management server Considerations are delivered in a cabinet-mount configuration in accordance with customer specifications. Because Ethernet cables that connect the managed products, hub, and management server are factory- installed, connectivity planning is not required for a stand-alone cabinet installation.
Page 216: Typical Network Configuration (One Ethernet Connection)
Physical Planning Considerations NOTE: Remote workstation access to Eclipse-series SAN routers is not supported. Remote workstations must have access to the LAN segment on which the management server is installed. Product administrative functions are accessed through the LAN and management server. The LAN interface can be: •...
Page 217: Snmp Management Workstations
Physical Planning Considerations Connection to this LAN segment is optional and depends on customer requirements. This type of network configuration using both Ethernet connections is shown in Figure 5-3. Intrepid 6064 Directors are used as an example. Figure 5-3 Typical Network Configuration (Two Ethernet Connections) If only one management server connection is used and this connection is provided through the customer intranet, all functions provided by the server are available to users throughout the...
Page 218: Efcm Basic Edition Interface
Physical Planning Considerations • Up to 12 authorized management workstations can be configured through the director or fabric switch SAN management application to receive unsolicited SNMP trap messages that indicate product operational state changes and failure conditions. • Up to eight authorized management workstations can be configured through a SAN router Element Manager application to send SNMP trap messages that indicate product operational state changes and failure conditions.
Page 219: Security Provisions
Physical Planning Considerations Security Provisions Security provisions are available to restrict unauthorized access to a director, switch, or attached Fibre Channel devices. Access to the director or switch (through the SAN management application, Element Manager application, or EFCM Basic Edition interface) is restricted by implementing password protection.
Page 220: Santegrity Authentication
Physical Planning Considerations System administrators can use the SAN management application to assign remote workstation access to directors and switches. Remote sessions are allowed for anyone on a customer intranet, disallowed completely, or restricted to specific workstations. Remote users must log into the SAN management application with a user name and password, just as when logging in to the local management server.
Page 221 Physical Planning Considerations The fabric element transmits a random value (used only once), an ID value (incremented at each login), and a shared CHAP secret (16-byte random value) to the server. The server concatenates the random value, ID value, and CHAP secret, and calculates a one- way message digest (also called a hash value).
Page 222 Physical Planning Considerations • RADIUS server support - Remote authentication dial-in user service (RADIUS) is a client-server, UDP-based protocol that supports storage and authentication of passwords and CHAP secrets. Directors, fabric switches, and SAN routers support a RADIUS client (LAN-connected to a primary or secondary RADIUS server) that authenticates CHAP responses and login passwords.
Page 223: Santegrity Binding
Physical Planning Considerations — Authorization errors. — Authentication errors. — Management application user connections. Use of the SANtegrity Authentication feature in conjunction with other security provisions must be carefully planned and coordinated. For additional information, refer to Security Best Practices. Obtain planning assistance from McDATA’s professional services organization before implementing the feature.
Page 224: Pdcm Arrays
Physical Planning Considerations • Rerouting delay - If a fabric topology changes, directors and fabric switches calculate a new least-cost data transfer path through a fabric, and routing tables immediately implement that path. This may result in Fibre Channel frames being delivered to a destination device out of order, because frames transmitted over the new (shorter) path may arrive ahead of previously- transmitted frames that traverse the old (longer) path.
Page 225: Configure Allow/Prohibit Matrix - Active Dialog Box
Physical Planning Considerations Configure Allow/Prohibit Matrix - Active Dialog Box Figure 5-4 To access the dialog box, ensure the FICON management style is enabled for the director or switch, then select the Allow/Prohibit and Active options from the Element Manager application’s Configure menu.
Page 226: Pdcm Array - Example Problem
Physical Planning Considerations PDCM Array - Example Problem Figure 5-5 A PDCM array configured for Director A prohibits logical port address 05 from communicating with logical port addresses 0A, 0B, and 0C. No PDCM array is configured for Director B. The PDCM array configured for Director A prohibits the source server from transmitting or receiving data across ISL 2.
Page 227: Preferred Path
Physical Planning Considerations Preferred Path The preferred path option allows a user to specify and configure one or more ISL data paths between multiple directors or fabric switches in a fabric. At each fabric element, a preferred path consists of a source port on the director or switch being configured, an exit port on the director or switch, and the Domain_ID of the destination director or switch.
Page 228 Physical Planning Considerations A preferred path is configured between a source server and destination device (A or B), traversing Director 1, Director 2, and Director 3. To configure the preferred path through the first director: 1. Select the Preferred Path option from the Element Manager application’s Configure menu.
Page 229: Zoning
Physical Planning Considerations Zoning Directors and fabric switches support a user configuration that partitions attached devices into restricted-access groups called zones. Devices in the same zone can recognize and communicate with each other through switched port-to-port connections. Devices in separate zones cannot recognize name server or route table information and therefore cannot communicate with each other.
Page 230 Physical Planning Considerations Zones are configured through the SAN management application by authorizing or restricting access to name server or route table information (depending on the firmware release level) associated with device N_Ports that attach to director or switch fabric ports (F_Ports).
Page 231 Physical Planning Considerations ATTENTION ! If zoning is implemented by WWN, removal and replacement of a device HBA or Fibre Channel interface (thereby changing the device WWN) disrupts zone operation and may incorrectly exclude a device from a zone. • The domain identification (Domain_ID) and physical port number of the director or fabric switch port to which the device is attached.
Page 232 Physical Planning Considerations — The default zone is enabled or disabled separately from the active zone set. — If the default zone is enabled, then all devices not in a specified zone are included in the default zone and can communicate with each other.
Page 233: Server And Storage-Level Access Control
Physical Planning Considerations • Reasons for zone implementation - Determine if zoning is to be implemented for the enterprise. If so, evaluate if the purpose of zoning is to differentiate between operating systems, data sets, user groups, devices, processes, or some combination thereof. Plan the use of zone members, zones, and zone sets accordingly.
Page 234: Security Best Practices
Physical Planning Considerations • Each server HBA is explicitly bound to a storage volume or LUN, and access is explicitly authorized (access is blocked by default). • The process is compatible with OSI standards. The following are transparently supported: — Different operating systems and applications. —...
Page 235 Physical Planning Considerations 2. SANtegrity Binding - The SANtegrity Binding feature is recommended for large and complex SANs with fabrics and devices provided by multiple OEMs or that intermix FCP and FICON protocols. The feature is required for FICON-cascaded high-integrity SANs. SANtegrity Binding includes: —...
Page 236 Physical Planning Considerations 5. Preferred path - A preferred path provides soft control of fabric routing decisions on a switch-by-switch or port-by-port basis. The path instructs a fabric to use a preferred exit port out of a director or fabric switch for a specified receive port and target domain. If a preferred path is prohibited by SANtegrity Binding, PDCM arrays, or hard zoning, the path is not programmed.
Page 237: Optional Feature Keys
Physical Planning Considerations Follow best practices listed here in order of precedence. Logically work in sequence from the most restrictive method to the least restrictive method, ensuring the most restrictive connectivity or routing paths override all other paths. Optional Feature Keys McDATA offers several operating features that are available for the switch as customer-specified options.
Page 238 Physical Planning Considerations • Full volatility - Enablement of this feature ensures that no Fibre Channel frames are stored after a director or Fabric switch is powered off or fails, and a memory dump file (that possibly includes classified frames) is not included as part of the data collection procedure.
Page 239: Inband Management Access
Physical Planning Considerations Inband Inband management console access (through a Fibre Channel port) is Management provided by enabling user-specified features that allow OSMS or Access FICON (FMS) host control of a director or fabric switch. The features can be simultaneously installed and enabled. OSMS When the OSMS feature key is enabled at the Element Manager application, host control and management of the director or switch is...
Page 240: Flexport Technology
Physical Planning Considerations • Connectivity to an IBM eServer zSeries 800 (z800), zSeries 900 (z900), or zSeries 990 (z990) processor, with one or more FICON or FICON Express channel adapter cards installed, using the z/OS operating system, Version 1.1 or later. •...
Page 241: Opentrunking
Physical Planning Considerations • Switch binding - This portion of the feature allows only specified devices and fabric elements to connect to specified director or fabric switch ports. • Enterprise Fabric Mode - Although Enterprise Fabric Mode is not a keyed feature, it is required for SANtegrity Binding operation.
Page 242: Full Volatility
Physical Planning Considerations The figure illustrates two Intrepid 6064 Directors connected by two ISLs. Three servers use the ISLs to communicate with two storage devices. Without trunking, servers 1 through 3 route Fibre Channel traffic from to director B without regard to any data rates. A possible scenario is that servers 1 and 2 route high data rate traffic through ISL 1 to storage device 1 (ISL oversubscription) and server 3 routes low data rate traffic through ISL 2 to storage device 2...
Page 243: Remote Fabric
Physical Planning Considerations Remote Fabric Intrepid 10000 Director LIMs contain two scalable packet processors, each supporting an optical paddle pair. Each paddle pair provides 16 ports (1.0625 or 2.12500 Gbps operation), four ports (10.2000 Gbps operation), or ten ports (mixed data rate operation). A minimal BB_Credit buffer pool is allocated among all paddle-pair ports that allows a 1.0625 or 2.12500 Gbps port to be set to 60 BB_Credits and a 10.2000 Gbps port to be set to 360 BB_Credits.
Page 244 Physical Planning Considerations McDATA Products in a SAN Environment - Planning Manual 5-40...
Page 245: Configuration Planning Tasks
Configuration Planning Tasks This chapter describes configuration planning best-practices tasks to be performed before installing one or more McDATA Fibre Channel switching products in a storage area network (SAN) configuration. Table 6-1 summarizes planning tasks described in the chapter. Table 6-1 Configuration Planning Tasks Task Page...
Page 246: Task 1: Prepare A Site Plan
Configuration Planning Tasks Configuration Planning Tasks (continued) Table 6-1 Task Page Task 13: Complete the Planning Worksheet 6-14 Task 14: Plan AC Power 6-28 Task 15: Plan a Multiswitch Fabric (Optional) 6-29 Task 16: Plan Zone Sets for Multiple Products (Optional) 6-30 Task 17: Plan SAN Routing (Optional) 6-31...
Page 247: Task 2: Plan Fibre Channel Cable Routing
Configuration Planning Tasks • Power requirements, including an optional uninterruptable power supply (UPS). • Lengths of power cables and location of electrical outlets (for directors, switches, and the management server) having the proper phase, voltage, amperage, and ground connection. DANGER Use the supplied power cords.
Page 248: Task 3: Consider Interoperability With Fabric Elements And End Devices
Configuration Planning Tasks In addition, consider the following when planning cable routing: • The need for additional fiber-optic cables could grow rapidly. Consider installing cable with extra fibers, especially in hard to reach places like underground trenches. Consider locating the equipment cabinet near a fiber-optic patch panel.
Page 249: Task 4: Plan Console Management Support
Configuration Planning Tasks NOTE: If the FICON management server feature is enabled, the default operating style is FICON. The open systems management style cannot be enabled. Consider purchasing and enabling the SANtegrity Authentication and SANtegrity Binding features to provide additional data security in a complex and multi-OEM environment.
Page 250 Configuration Planning Tasks • Remote user workstations - If remote access to the management server is required, plan to install user workstations with the SAN management and Element Manager applications configured. Administrators can use these remote workstations to configure and monitor directors and fabric switches. Up to 25 sessions can be simultaneously active.
Page 251: Task 5: Plan Ethernet Access
Configuration Planning Tasks Task 5: Plan Ethernet Access The management server and one or more products are configured on a dedicated Ethernet LAN segment and delivered in the Fabricenter equipment cabinet. No Ethernet access planning is required for a stand-alone cabinet. This task is required to: •...
Page 252 Configuration Planning Tasks • If installing products and the management server on a dedicated (private) LAN segment, there is no requirement to change any default network addresses. However, if multiple equipment cabinets are connected, ensure all managed products and servers have unique IP addresses.
Page 253: Eclipse 2640 San Router
Configuration Planning Tasks • Intrepid-series directors and Sphereon-series fabric switches: — MAC address is unique for each product. — Default IP address is 10.1.1.10. — Subnet mask is 255.0.0.0. — Gateway address is 0.0.0.0. • Eclipse 1620 SAN Router: — System addresses: •...
Page 254: Task 7: Plan Snmp Support (Optional)
Configuration Planning Tasks • Subnet mask is 0.0.0.0. • Gateway address is 0.0.0.0. — 10/100 Base-T Ethernet management port addresses: • Default IP address is 192.168.100.100. • Subnet mask is 255.255.255.0. • Gateway address is 0.0.0.0. — Intelligent port (13 through 16) addresses: •...
Page 255: Task 8: Plan E-Mail Notification (Optional)
Configuration Planning Tasks • Obtain IP addresses and SNMP community names for management workstations that have access to products. • Determine which (if any) management workstations can have write permission for SNMP variables. • Obtain product-specific trap information from McDATA to load onto SNMP management workstations.
Page 256: Task 10: Plan Phone Connections
Configuration Planning Tasks • Remote access to products is possible through the maintenance port or an internal modem connection to the management server. These connections are for use by authorized service personnel only and should be carefully monitored. • The number of remote workstations with access to the management server and managed products can and should be restricted.
Page 257: Task 12: Assign Port Names And Nicknames
Configuration Planning Tasks Part of this task may have been performed when the configuration was determined. It might be helpful to draw the configuration diagram. Indicate distances in the diagram if necessary. Transfer information from the configuration diagram to the product planning worksheet provided as part of Task 13: Complete the Planning Worksheet.
Page 258: Rules For Nicknames
Configuration Planning Tasks Rules for Nicknames Nicknames can be up to 32 alphanumeric characters in length. Spaces, hyphens, and underscores are allowed within the nickname. Each nickname must be unique (corresponding to a unique WWN). Example nicknames include: Fabric-1. Host system-1. DASD_001.
Page 259 Configuration Planning Tasks Product Planning Worksheet (Page 1 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-15...
Page 260 Configuration Planning Tasks Product Planning Worksheet (Page 2 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone McDATA Products in a SAN Environment - Planning Manual 6-16...
Page 261 Configuration Planning Tasks Product Planning Worksheet (Page 3 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-17...
Page 262 Configuration Planning Tasks Product Planning Worksheet (Page 4 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone McDATA Products in a SAN Environment - Planning Manual 6-18...
Page 263 Configuration Planning Tasks Product Planning Worksheet (Page 5 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-19...
Page 264 Configuration Planning Tasks Product Planning Worksheet (Page 6 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone McDATA Products in a SAN Environment - Planning Manual 6-20...
Page 265 Configuration Planning Tasks Product Planning Worksheet (Page 7 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-21...
Page 266 Configuration Planning Tasks Product Planning Worksheet (Page 8 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone McDATA Products in a SAN Environment - Planning Manual 6-22...
Page 267 Configuration Planning Tasks Product Planning Worksheet (Page 9 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-23...
Page 268 Configuration Planning Tasks Product Planning Worksheet (Page 10 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone McDATA Products in a SAN Environment - Planning Manual 6-24...
Page 269 Configuration Planning Tasks Product Planning Worksheet (Page 11 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-25...
Page 270 Configuration Planning Tasks Product Planning Worksheet (Page 12 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone McDATA Products in a SAN Environment - Planning Manual 6-26...
Page 271 Configuration Planning Tasks Product Planning Worksheet (Page 13 of 13) Attached Devices Switch Name:____________________________ IP Address:____________________________ Unit Name:__________________________ Port Port Name Location Type Model IP Address Zone Configuration Planning Tasks 6-27...
Page 272: Task 14: Plan Ac Power
Configuration Planning Tasks Task 14: Plan AC Power Plan for facility power sources for each Fabricenter equipment cabinet, director, fabric switch, or SAN router as follows: • The Fabricenter equipment cabinet operates at 47 to 63 Hertz (Hz), 200 to 240 volts alternating current (VAC), and requires a minimum dedicated 30-ampere service.
Page 273: Task 15: Plan A Multiswitch Fabric (Optional)
Configuration Planning Tasks Task 15: Plan a Multiswitch Fabric (Optional) If a multiswitch fabric topology is to be implemented, carefully plan the physical characteristics and performance objectives of the topology, including the proposed number of fabric elements, characteristics of attached devices, cost, nondisruptive growth requirements, and service requirements.
Page 274: Task 16: Plan Zone Sets For Multiple Products (Optional)
Configuration Planning Tasks Task 16: Plan Zone Sets for Multiple Products (Optional) If name server zoning is to be implemented, carefully plan the characteristics and security objectives (separation of operating systems, data sets user groups, devices, or processes) of zone members, zones and zone sets.
Page 275: Task 17: Plan San Routing (Optional)
Configuration Planning Tasks Task 17: Plan SAN Routing (Optional) If a routed SAN is to be implemented, carefully plan metropolitan area network (MAN) or wide area network (WAN) connectivity and the integration of SAN routers with standard fibre channel fabric elements.
Page 276 Configuration Planning Tasks • IP network connections - At each location, cables with appropriate connectors must be routed between the IP transport network and the SAN router. The Eclipse 1620 SAN Router supports Ethernet RJ-45 connectors or SFP optical transceivers with LC duplex connectors.
Page 277 Configuration Planning Tasks • Negotiate SLA - Network service providers provide IP WAN transport services in accordance with a negotiated service level agreement (SLA). Ensure the SLA specifies the link availability, peak available bandwidth, latency, security level, monitoring level, packet loss, and mean time to repair (MTTR). •...
Page 278: Task 18: Complete Planning Checklists
Configuration Planning Tasks Task 18: Complete Planning Checklists As a guide for planning tasks, complete the planning checklists under this task. Checklists provide detailed planning activities and provide space for a planned completion date for each activity. The customer’s management information system (MIS) project manager should examine the checklists and determine the personnel and resources required for completing planning and installation tasks.
Page 279: Physical Planning And Hardware Installation Tasks
Configuration Planning Tasks Physical Planning and Hardware Installation Tasks Table 6-2 Activity Task Owner Due Date Comments Locate the physical facilities. Connect the facility alternating current If more than one managed product, consider (AC) power circuits. separate power circuits for availability. Obtain an uninterruptable power supply Recommended.
Page 280: Operational Setup Tasks
Configuration Planning Tasks Physical Planning and Hardware Installation Tasks (continued) Table 6-2 Activity Task Owner Due Date Comments Set up LAN connections to corporate Remote workstation access is supported for intranet for remote workstation access directors and fabric switches only. (optional).
Page 281 Configuration Planning Tasks Operational Setup Tasks (continued) Table 6-3 Activity Task Owner Due Date Comments Determine if inband management of the Management server and Fibre-Channel-attached director or switch is to be used, and if so, server peripheral (optional). the type (FICON or open-systems). Determine if the call-home feature is to be used.
Page 282 Configuration Planning Tasks Operational Setup Tasks (continued) Table 6-3 Activity Task Owner Due Date Comments Configure extended distance ports. If SAN routing is supported, configure extended distance ports in accordance with IP WAN requirements. Enable and configure optional feature keys. Configure link incident alerts.
Page 283: Product Specifications
Product Specifications This appendix lists specifications for McDATA directors, fabric switches, storage area network (SAN) Routers, and the FC-512 Fabricenter equipment cabinet. Director, Fabric Switch, and SAN Router Specifications This section lists specifications (dimensions, weight, power requirements, heat dissipation requirements, cooling airflow clearances, acoustical noise generated, physical tolerances, storage and shipping environment requirements, and operating environment requirements) for directors, fabric switches, and SAN routers.
Page 284: Sphereon 3232 Fabric Switch
Product Specifications Intrepid 10000 Director: Height: 62.2 centimeters (24.5 inches) or 14 rack units. Width: 44.3 centimeters (17.5 inches). Depth: 86.4 centimeters. (34.0 inches). Weight: 152.0 kilograms (335.0 pounds). Sphereon 3232 Fabric Switch: Height: 6.5 centimeters (2.6 inches) or 1.5 rack units. Width: 44.5 centimeters (17.5 inches).
Page 285: Power Requirements
Product Specifications Eclipse 1620 SAN Router: Height: 4.1 centimeters (1.6 inches) or 1 rack unit. Width: 43.7 centimeters (17.2 inches). Depth: 45.7 centimeters (18.0 inches). Weight: 5.9 kilograms (13.0 pounds). Eclipse 2640 SAN Router: Height: 4.1 centimeters (1.6 inches) or 1 rack unit. Width: 43.7 centimeters (17.2 inches).
Page 286 Product Specifications Sphereon 3232 Fabric Switch: Input voltage: 100 to 240 VAC. Input current: 1.3 amps at 208 VAC. Input frequency: 47 to 63 Hz. Sphereon 4300 Fabric Switch: Input voltage: 100 to 240 VAC. Input current: 0.4 amps at 208 VAC. Input frequency: 47 to 63 Hz.
Page 287: Heat Dissipation
Product Specifications Heat Dissipation McDATA products have the following maximum heat dissipation characteristics: Intrepid 6064 Director: 490 watts (1,672 BTU/hr). Intrepid 6140 Director: 841 watts (2,873 BTU/hr). Intrepid 10000 Director: 2,496 watts (8,517 BTU/hr). Sphereon 3232 Fabric Switch: 245 watts (836 BTU/hr). Sphereon 4300 Fabric Switch: 37 watts (127 BTU/hr).
Page 288: Acoustical Noise And Physical Tolerances
Product Specifications Sphereon 3232 Fabric Switch: Right and left side: No clearance required. Front and rear: 7.6 centimeters (3.0 inches). Top and bottom: No clearance required. Sphereon 4000-Series Switches: Right and left side: 1.3 centimeters (0.5 inches). Front and rear: 7.6 centimeters (3.0 inches). Top and bottom: No clearance required.
Page 289: Operating Environment
Product Specifications Shipping temperature: F to 140 F (-40 C to 60 Storage temperature: F to 140 F (1 C to 60 Shipping relative humidity: 5% to 100%. Storage relative humidity: 5% to 80%. Maximum wet-bulb temperature: F (29 Altitude: 40,000 feet (12,192 meters).
Page 290: Dimensions
Product Specifications Dimensions The Fabricenter cabinet has the following physical dimensions: Height: 186.1 centimeters (73.2 inches). A total of 39 rack units (39 U) are available internal to the cabinet for product installation. Width: 61.0 centimeters (24.0 inches). Depth: 105.4 centimeters (41.5 inches). Weight (no installed products): 153.2 kilograms (337.0 pounds).
Page 291: Fabricenter Cabinet Footprint
Product Specifications Fabricenter Cabinet Footprint Figure A-1 Product Specifications...
Page 292 Product Specifications McDATA Products in a SAN Environment - Planning Manual A-10...
Page 293: Firmware Summary
Firmware Summary This appendix summarizes differences and similarities between the Enterprise Operating System, classic (E/OSc) for Intrepid 6000-series directors and Sphereon-series fabric switches; Enterprise Operating System, nScale (E/OSn) for the Intrepid 10000 Director; and Enterprise Operating System, internetworking (E/OSi) for Eclipse-series SAN routers.
Page 294: E/Osc Versus E/Osn And E/Osi - System-Related Differences
Firmware Summary E/OSc versus E/OSn and E/OSi - System-Related Differences (Continued) Table B-1 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Nondisruptive hot code Upgrade nondisruptive to Fibre Director must be set offline to Nondisruptive hot code activation (HotCAT) Channel traffic for single and upgrade a single CTP card.
Page 295 Firmware Summary E/OSc versus E/OSn and E/OSi - System-Related Differences (Continued) Table B-1 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Misaligned word Misaligned words not generated. Misaligned word is generated Misaligned words not generated. generation when the port state machine (PSM) transitions from inactive to active state or from active to inactive state.
Page 296: E/Osc Versus E/Osn And E/Osi - Fibre Channel Protocol-Related Differences
Firmware Summary E/OSc versus E/OSn and E/OSi - Fibre Channel Protocol-Related Differences Table B-2 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Expansion port (E_Port) E_Port staging not supported. The Intrepid 10000 Director E_Port staging not supported. staging supports E_Port staging. The director allows only one E_Port connection to a neighbor switch to take part in a fabric build...
Page 297 Firmware Summary E/OSc versus E/OSn and E/OSi - Fibre Channel Protocol-Related Differences Table B-2 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Reroute delay behavior With reroute delay enabled, the With reroute delay enabled, the Reroute delay not supported. destination route point is cleared Intrepid 10000 Director first and a delay equal to the error pauses incoming port traffic and...
Page 298: E/Osc Versus E/Osn And E/Osi - Management-Related Differences
Firmware Summary E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued) Table B-3 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 General SNMP support SNMP interface supports SNMP interface supports SNMP interface supports Version 1, Version 2c, and a Version 1, Version 2c, and Version 1 and a configuration-related subset of Version 3.
Page 299 Firmware Summary E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued) Table B-3 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 FICON Management FMS is auto-enabled upon PFE When PFE is installed, the user FMS PFE key not supported. Server (FMS) PFE key installation.
Page 300 Firmware Summary E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued) Table B-3 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Port group online Diagnostic errors for any single Diagnostic errors for any single Port grouping (port cards or diagnostics (directors) port in a group (port card) cause port in a group (LIM) are LIMs) not supported.
Page 301 Firmware Summary E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued) Table B-3 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Special port states and Port state Inactive with special Logical port addresses FE and At the CLI, port state Testing reason codes reason codes Reserved and FF forced offline and placed in...
Page 302 Firmware Summary E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued) Table B-3 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 Diagnostics Port set to Failed state upon If external port diagnostics are If external port diagnostics or (port failure state) failing a user- invoked port performed without a loopback management port diagnostics...
Page 303 Firmware Summary E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued) Table B-3 Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6 FICON management User-selectable option on a per User-selectable option on a per FICON management style not style support product basis. Setting is stored user (different for each login ID) supported through the on the product.
Page 304 Firmware Summary McDATA Products in a SAN Environment - Planning Manual B-12...
Page 305 Index asynchronous remote data replication description 4-38 access control list IP transport 4-48 inband 5-18 long-distance requirement 4-38 out-of-band 5-18 SONET/SDH transport 4-47 role-based access any-to-any connectivity 1-28 application I/O profiles 3-31 arbitrated loop switch backup features connectivity features 1-28 CD-RW drive 2-13 default network address...
Page 306 Index Sphereon 4300 Fabric Switch 1-30 cabling Sphereon 4400 Fabric Switch 1-30 50/125 multimode Sphereon 4500 Fabric Switch 1-30 62.5/125 multimode Sphereon 4700 Fabric Switch 1-30 9/125 singlemode best practices best practices 3-20 cabling 3-20 Ethernet cable routing 5-11 configuration planning fiber-optic cable routing connectivity 3-20...
Page 307 Index Tier 1 connections 3-17 FlexPars Tier 2 connections 3-18 performance features Tier 3 connections 3-18 product overview CT authentication 5-17 security features 1-31 serviceability features 1-32 specifications disaster recovery dark fiber distance extension IP versus storage traffic 4-36 bandwidth 4-46 operational mode description...
Page 308 Index proxy Domain_ID 30 4-13, 4-18 illustration 1-26 proxy Domain_ID 31 4-13, 4-25 intelligent ports 1-27 R_Port 4-15 mFCP protocol 4-20 SAN router 4-15 EFCM application description 2-15 GUI description 2-15 product overview E/OSc EFCM Basic Edition interface description 2-11 description 2-20 management-related properties...
Page 309 Index port configuration optimizing WAN use 4-56 remote fabric feature 5-39 FC-AL devices support 1-29 connecting to a multiswitch fabric 3-11 transport technology server consolidation 3-12 dark fiber 4-39 tape device consolidation 3-13 4-45 FCP and FICON intermix SONET/SDH 4-42 best practices 3-47 4-40...
Page 310 Index FICON management server Sphereon 3232 Fabric Switch 1-15 description 5-35 Sphereon 4300 Fabric Switch 1-17 introduction Sphereon 4400 Fabric Switch 1-18 plan console support Sphereon 4500 Fabric Switch 1-20 firmware Sphereon 4700 Fabric Switch 1-21 application services 2-12 full fabric feature E/OSc description 2-11 description...
Page 311 Index IP address director or fabric switch I/O requirements Eclipse 1620 SAN Router application I/O profiles 3-31 Eclipse 2640 SAN Router device locality 3-33 management server ISL oversubscription 3-32 IP distance extension iFCP protocol bandwidth 4-48 build fabric events 4-23 description 4-45 comparison to mFCP...
Page 312 Index plan security measures 6-11 product overview large fabric recommended specifications fabric initialization 3-29 map, port card 3-43 fabric scalability 3-39 mesh fabric high-bandwidth ISLs 3-30 description 3-14 high-port count directors 3-30 illustration 3-15 problems suitability 3-16 laser transceiver mFCP protocol description comparison to iFCP 4-28...
Page 313 Index out-of-band product management command line interface N_Port DHCHAP authentication 5-17 EFCM N_Port ID virtualization feature 5-39 EFCM Basic Edition interface name conventions, ports 6-13 EFCM Lite application name server zoning Element Manager application introduction 1-28 SAN management application planning requirements 6-30 SANavigator network addresses...
Page 314 Index plan SAN routing 6-31 product management plan SNMP support 6-10 command line interface plan zone sets 6-30 EFCM prepare a site plan EFCM Basic Edition interface planning worksheet 6-14 EFCM Lite application port Element Manager application binding 1-31 FMS feature blocking 1-28 inband methods...
Page 315 Index public restore features arbitrated loop CD-RW drive 2-13 loop device connectivity director and fabric switch NV-RAM configuration 2-13 SAN management data directory 2-14 SAN router NV-RAM configuration 2-14 R_Port role-based FlexPars configuring 4-34 Domain_ID assignment 4-15 operation 4-11 RADIUS server support 5-18 SAN island rate limiting...
Page 316 Index mSAN routing 4-18 preferred path 5-23 planning requirements 6-31 SANtegrity Authentication 5-16 R_Port operation 4-11 SANtegrity Binding 5-19 routing domain (iSAN) 4-25 security feature description 1-31 routing domain (mSAN) 4-18 security log description 5-18 SAN island consolidation server-level access control 5-29 Tier 1 (fabrics) storage-level access control...
Page 317 Index SONET/SDH distance extension illustration 1-19 bandwidth 4-47 Sphereon 4700 Fabric Switch description 4-42 description 1-21 illustration 4-43 FL_Port connectivity 3-10 latency 4-47 FRUs 1-21 recovery point objective 4-47 illustration 1-21 recovery time objective 4-47 SSH protocol description 5-18 specifications state change notification 1-29, 3-28 director clearances...
Page 318 Index zoning benefits 5-26 vendor interoperability limitations 3-20 configuring zones 5-26 description 5-25 introduction 1-28 WDM distance extension joining zoned fabrics 5-28 bandwidth 4-47 planning considerations 5-28 description 4-40 planning requirements 6-30 illustration 4-41 SAN router latency 4-47 append IPS zones 4-17 recovery point objective 4-47...

This manual is also suitable for:

Storageworks 2/24 - edge switch 316095-b21 - storageworks edge switch 2/24 Intrepid 6064 Intrepid 6140 Intrepid 10000 Sphereon 3232 ... Show all

McDATA StorageWorks 2/140 - Director Switch Planning Manual

Preface

Chapter 1 Introduction to Mcdata Multi-Protocol Products

Chapter 2 Product Management

Chapter 3 Planning Considerations for Fibre Channel Topologies

Chapter 4 Implementing SAN Internetworking Solutions

Chapter 5 Physical Planning Considerations

Chapter 6 Configuration Planning Tasks

Appendix A Product Specifications

Product Specifications

Appendix B Firmware Summary

Firmware Summary

Quick Links

Related Manuals for McDATA StorageWorks 2/140 - Director Switch

Summary of Contents for McDATA StorageWorks 2/140 - Director Switch