planning guide hp StorageWorks SAN high availability Product Version: FW V05.01.00-24/HAFM SW V07.01.00-09 Third Edition (June 2003) Part Number: AA-RS2DC-TE This guide introduces HP Fibre Channel switching products, storage area networks (SANs), and Fibre Channel technologies. It describes HP StorageWorks directors and edge switches, and High Availability Fabric Manager (HAFM) application.
©Copyright 2001-2003. Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
contents Contents About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 2 Product Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Product Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 HAFM Server Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 HAFM Server Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Fabric Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Cascaded Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Ring Fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Mesh Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Cables and Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Director and Switch Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Fiber-Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Task 8: Plan E-Mail Notification (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 9: Establish Product and HAFM Server Security Measures . . . . . . . . . . . . . . . . . . . . Task 10: Plan Phone Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 11: Diagram the Planned Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 12: Assign Port Names and Nicknames. . . . . . .
Contents 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 Private device connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Public loop connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Private loop connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
about this guide About this Guide This planning guide provides information to help you plan the acquisition and installation of one or more of the following Hewlett-Packard (HP) products: About this Guide ■ HP StorageWorks Director 2/64. ■ HP StorageWorks Director 2/140. ■ HP StorageWorks Edge Switch 2/16. ■ HP StorageWorks Edge Switch 2/24. ■ HP StorageWorks Edge Switch 2/32. ■ High Availability fabric Manager (HAFM) application.
About this Guide Overview This section covers the following topics: ■ Intended Audience ■ Related Documentation Intended Audience This book is intended for use by configuration and installation planners who are experienced with the following: ■ System administration. ■ Customer engineering. ■ Project management. Related Documentation For a list of corresponding documentation, see the “Related Documents” section of the Release Notes that came with the product.
About this Guide Conventions Conventions consist of the following: ■ Document Conventions ■ Text Symbols ■ Equipment Symbols Document Conventions The document conventions included in Table 1 apply in most cases.
About this Guide Text Symbols The following symbols may be found in the text of this guide. They have the following meanings. WARNING: Text set off in this manner indicates that failure to follow directions in the warning could result in bodily harm or death. Caution: Text set off in this manner indicates that failure to follow directions could result in damage to equipment or data. Note: Text set off in this manner presents commentary, sidelights, or interesting points of information.
About this Guide Any surface or area of the equipment marked with these symbols indicates the presence of a hot surface or hot component. Contact with this surface could result in injury. WARNING: To reduce the risk of personal injury from a hot component, allow the surface to cool before touching. Power supplies or systems marked with these symbols indicate the presence of multiple sources of power.
About this Guide Getting Help If you still have a question after reading this guide, contact an HP authorized service provider or access our website: http://www.hp.com. HP Technical Support Telephone numbers for worldwide technical support are listed on the following HP website: http://www.hp.com/support/. From this website, select the country of origin. Note: For continuous quality improvement, calls may be recorded or monitored.
Introduction to HP Fibre Channel Products 1 This chapter introduces Hewlett-Packard (HP) Fibre Channel switching products that allow deployment and implementation of a storage area network (SAN) topology in a Fibre Channel Protocol (FCP) or IBM fiber connection (FICON) environments. HP offers several switch alternatives to build a robust and scalable SAN infrastructure that meets the customer’s data center requirements.
Introduction to HP Fibre Channel Products ■ Arbitrated loop switches — Fibre Channel arbitrated loop (FC-AL) switches are low port count, low-bandwidth products. HP offers related products that act as loop-switching hubs and fabric-attach switches. These switches provide connectivity between attached FC-AL devices, and between FC-AL devices and switched fabric elements.
Introduction to HP Fibre Channel Products 1 2 3 HP Ethernet hub Three Edge Switch 2/16s Three Edge Switch 2/32s 4 5 Shelf-mount HAFM server (HP Omnibook) Two Director 2/64s Figure 1: Rack-mount HP products SAN High Availability Planning Guide 17
Introduction to HP Fibre Channel Products Directors Directors provide high-performance, dynamic connections between end devices such as servers, mass storage devices, and peripherals in a Fibre Channel switched network. Directors also support mainframe and open systems interconnection (OSI) computing environments and provide data transmission and flow control between device node ports (N_Ports) as dictated by the Fibre Channel Physical and Signaling Interface (FC-PH 4.3).
Introduction to HP Fibre Channel Products Director Performance Directors provide the following general performance features: ■ High bandwidth — Each port provides full-duplex serial data transfer at a rate of 2.125 Gbps. ■ High availability — To ensure an availability of 99.999%, director design provides a redundant configuration of critical components with automatic failure detection and notification.
Introduction to HP Fibre Channel Products ■ Multiple topology support — Directors support both point-to-point and multi-switch fabric topologies, and indirectly support arbitrated loop topology. — Point-to-point topology provides a single direct connection between two device N_Ports. This topology supports bidirectional transmission between source and destination ports. Through dynamic switching, directors configure different point-to-point transmission paths.
Introduction to HP Fibre Channel Products Director 2/64 The Director 2/64 is a second-generation, enterprise-class switch that provides switched fabric connectivity for to up to 64 Fibre Channel devices. Figure 2 illustrates the front of the director. Each UPM card provides four 2.125 Gbps Fibre Channel port connections through duplex small form factor pluggable (SFP) fiber-optic transceivers. Shortwave laser transceivers are available for transferring data over multimode fiber-optic cable.
Introduction to HP Fibre Channel Products Figure 3 illustrates the rear of the director. 1 2 Redundant fan modules 3 Power module assembly with AC power switch Redundant serial crossbar (SBAR) assemblies Figure 3: Director 2/64 (rear view) The director provides a modular design that enables quick removal and replacement of FRUs. The power module assembly at the rear of the director also provides a 9-pin, D-type subminiature (DSUB) maintenance port for connection to a local terminal or remote terminal.
Introduction to HP Fibre Channel Products Director 2/140 The Director 2/140 is a third-generation, enterprise-class switch that provides switched fabric connectivity for to up to 140 Fibre Channel devices. Figure 4 illustrates the front of the director. Each UPM card provides four 2.125 Gbps Fibre Channel port connections through duplex small form factor pluggable (SFP) fiber-optic transceivers. Shortwave laser transceivers are available for transferring data over multimode fiber-optic cable.
Introduction to HP Fibre Channel Products Figure 5 illustrates the rear of the director. 1 2 3 Fan modules UPM cards (3) Maintenance port 4 5 6 SBAR assemblies AC modules Power supplies Figure 5: Director 2/140 (rear view) The director provides a modular design that enables quick removal and replacement of FRUs. The rear of the assembly provides a 9-pin, D-type subminiature (DSUB) maintenance port for connection to a local terminal or remote terminal.
Introduction to HP Fibre Channel Products Edge Switches Like directors, edge switches also provide high-performance, dynamic connections between end devices in a Fibre Channel switched network. Edge switches also support mainframe and OSI computing environments. Through non-blocking architecture and limited FRU redundancy, edge switches also offer high availability and high-performance bandwidth.
Introduction to HP Fibre Channel Products Edge Switch 2/16 The Edge Switch 2/16 provides 2.125 Gbps fabric connectivity for to up to 16 Fibre Channel devices. Figure 6 illustrates the front of the switch. Shortwave laser transceivers are available for transferring data over multimode fiber-optic cable. Longwave laser transceivers are available for transferring data over single-mode fiber-optic cable. Fiber-optic cables attach to switch port transceivers with duplex LC connectors.
Introduction to HP Fibre Channel Products Figure 7 illustrates the rear of the switch.
Introduction to HP Fibre Channel Products Edge Switch 2/24 The Edge Switch 2/24 provides 2.125 Gbps fabric connectivity for to up to 24 Fibre Channel devices. Figure 8 illustrates the front of the switch. Shortwave laser transceivers are available for transferring data over multimode fiber-optic cable. Longwave laser transceivers are available for transferring data over single-mode fiber-optic cable. Fiber-optic cables attach to switch port transceivers with duplex LC connectors.
Introduction to HP Fibre Channel Products Figure 9 illustrates the rear of the switch.
Introduction to HP Fibre Channel Products Edge Switch 2/32 The Edge Switch 2/32 provides 2.125 Gbps fabric connectivity for to up to 32 Fibre Channel devices. Figure 10 illustrates the front of the switch. Shortwave laser transceivers are available for transferring data over multimode fiber-optic cable. Longwave laser transceivers are available for transferring data over single-mode fiber-optic cable. Fiber-optic cables attach to switch port transceivers with duplex LC connectors.
Introduction to HP Fibre Channel Products Figure 11 illustrates the rear of the switch. The FRUs on the rear panel include two power supplies and four individual cooling fan FRUs.
Introduction to HP Fibre Channel Products Product Features In addition to the characteristics and performance features described in this chapter, HP-managed directors and switches also provide a variety of: ■ Connectivity features. ■ Security features. ■ Serviceability features.
Introduction to HP Fibre Channel Products ■ State change notification — Directors and switches support a state change notification function that allows attached N_Ports to request notification when other N_Ports change operational state. ■ Port binding — Directors and switches support a feature that binds an attached Fibre Channel device to a specified port through the device’s World Wide Name (WWN).
Introduction to HP Fibre Channel Products Serviceability Features Directors, switches, and the associated HAFM and Product Manager applications support the following serviceability features: ■ LEDs that provide visual indicators of hardware status or malfunctions. LEDs are provided on: — Director and switch FRUs. — The director front bezel. — Switch front panels.
Introduction to HP Fibre Channel Products ■ Redundant FRUs (logic cards, port transceivers, power supplies, and cooling fans) that can be removed or replaced without disrupting director, switch, or Fibre Channel link operation. ■ A modular design that enables quick removal and replacement of FRUs without the use of special tools or equipment. ■ Concurrent port maintenance.
Introduction to HP Fibre Channel Products 36 SAN High Availability Planning Guide
Product Management 2 This chapter describes management of Hewlett-Packard (HP) directors and edge switches. The chapter specifically describes: ■ Out-of-band and inband product management. ■ The High Availability Fabric Manager (HAFM) server, HAFM server specifications, Ethernet hub, and optional workstation support. ■ The firmware, backup and restore features, and software graphical user interface (GUI) delivered with a product and the associated HAFM server.
Product Management Product Management Out-of-band (non-Fibre Channel) management access to HP products is provided through two Ethernet LAN connections to director control processor (CTP) cards or a single connection to a director front panel. The following out-of-band management access methods are provided: ■ Management through the HAFM application. The HAFM application includes the Director 2/64 Product Manager, Edge Switch 2/16 Product Manager, and Edge Switch 2/32 Product Manager applications.
Product Management Figure 12 illustrates an example of out-of-band product management. In the figure, the managed product is a Director 2/64. The customer intranet could be an HP Ethernet hub providing device connectivity.
Product Management ■ Management through the product’s Fibre Connection (FICON) management server (FMS) that communicates with the IBM System Automation for OS/390 (SA OS/390) operating system. The operating system resides on an IBM System/390 or zSeries 900 Parallel Enterprise server attached to a director or switch port, and communicates through a FICON channel. Control of connectivity and statistical product monitoring are provided through a host-attached console.
Product Management HAFM Server Description The HAFM server is a notebook personal computer (PC) that provides a central point of control for up to 48 LAN-connected directors or switches. However, note that the maximum number of switches per storage area network (SAN) fabric is different. For the latest supported topology limits, contact your local HP sales representative or refer to http://h18006.ww1.hp.com/products/storageworks/san/documentation.
Product Management Note: The HAFM server and HAFM application provide a GUI to monitor and manage multiple HP products, and are a dedicated hardware and software solution that should not be used for other tasks. HP tests the HAFM application installed on the HAFM server, but does not compatibility test other third-party software. Modifications to the HAFM server hardware or installation of additional software (including patches or service packs) may interfere with normal operation.
Product Management Ethernet Hub The HAFM server and managed directors and switches can be connected through a 10/100 Base-T Ethernet hub. Figure 15 illustrates the 12-port hub. The hub can be ordered from HP and is installed at the top front of the equipment rack.
Product Management ■ 128 MB or greater RAM. ■ Video card supporting 256 colors at 800 x 600 pixel resolution. ■ Ethernet network adapter. ■ Java-enabled Internet browser, such as Microsoft Internet Explorer (Version 4.0 or later) or Netscape Navigator (Version 4.0 or later). Product Firmware Director or edge switch firmware provides services that manage and maintain Fibre Channel connections between ports.
Product Management ■ Network Services — This function provides TCP/IP transport layers to access management service subsystems from attached management clients. These clients include the HAFM server or an SNMP management station. ■ Application Services — This function supports all software subsystems for system initialization, logging, tracing, debugging, and communicating with the RS-232 maintenance port.
Product Management ■ HafmData directory — Critical information (for all managed products) stored in the HafmData directory is backed up or restored using a backup application. The application is configured to automatically back up the contents of the data directory to a removable disk when the HAFM server is rebooted or when directory contents change.
Product Management Product Software This section describes the Management Services and HAFM applications. The HAFM application includes the Product Manager application for each product (Director 2/64, Director 2/140, Edge Switch 2/16, Edge Switch 2/24, and Edge Switch 2/32). The applications provide a GUI and management services for monitoring and controlling directors and switches.
Product Management The HAFM server also provides hypertext transfer protocol (HTTP) server functionality. Use of this protocol with a standard Web server allows the download of client HAFM and Product Manager applications from the HAFM server to remote workstations. The server is configured to limit the maximum number of concurrent connections to eight.
Product Management Products View When the HAFM application opens, the Products tab opens by default and the Products View (Figure 16) displays. All managed products display as rectangular icons in the view window. Figure 16: Products View A label below each icon identifies the managed product by its configured name or network (IP) address. Additional information associated with each icon includes: ■ Data transmission rate — This rate displays in the upper left corner as 2 Gbps with a yellow background.
Product Management ■ Alert symbol — A large colored alert symbol behind each product illustration indicates the operational status of the product as follows: — A green circle indicates the product is fully operational. — A yellow triangle indicates a redundant component failure or degraded operational status. — A blinking red and yellow diamond indicates a critical failure and that the product is not operational. — A grey square indicates the product status is unknown (network connection failure).
Product Management Fabrics View Select the Fabrics tab at the Products View to open the Fabrics View (Figure 17). When the Fabrics View opens, the Topology tab displays by default. The left panel displays an expandable Fabrics tree that lists managed fabrics, director, and switch elements in each fabric, and nodes (Fibre Channel devices) connected to fabric elements. The right panel graphically displays directors, switches, and ISLs for the selected fabric.
Product Management By double-clicking (selecting) a fabric icon or right-clicking a fabric icon and selecting from pop-up menu options, a user opens the Product Manager application for the element. Refer to “Product Manager Application” on page 53 for additional information. Select the Zone Set tab at the Fabrics View to display the active zone set for the selected fabric (Figure 18 on page 52). Zones and zone members of the set display below the zone set name in a scrollable tree structure.
Product Management Product Manager Application The Product Manager application works in conjunction with the HAFM application, and is a Java-based GUI for managing and monitoring multiple directors or switches. The application operates locally on the HAFM server, or through a network connection from a remote PC or workstation.
Product Management The graphical representation of the product emulates the hardware configuration and operational status of the corresponding real product. For example, if a director or switch is fully redundant and fully populated, this configuration is reflected in the Hardware View. Colored symbols display on the graphical FRUs to represent failed or degraded status. The colors and shapes are consistent with status displays on other windows in the HAFM and Product Manager applications.
Product Management ■ Monitor port status, port statistics, and the active zone set, and display the event log and node list. ■ Perform product firmware upgrades and port diagnostics, reset ports, enable port beaconing, and set the product online or offline. The EWS interface can be opened from a standard Web browser running Netscape Navigator 4.6 or higher or Microsoft Internet Explorer 4.0 or higher. At the browser, enter the IP address of the product as the Internet uniform resource locator (URL).
Product Management The task selection tabs are a function of the menu selected, as follows: ■ View — At the View panel, the Director or Switch (default), Port Properties, FRU Properties, Unit Properties, Operating Parameters, and Fabric task selection tabs display. ■ Configure — At the Configure panel, the Ports (default), Switch, Management, Zoning, Security, and Performance task selection tabs display.
Planning Considerations for Fibre Channel Topologies 3 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 Hewlett-Packard (HP) switching products into Fibre Channel SAN topologies. This chapter specifically describes: ■ Fibre Channel topologies, including point-to-point, arbitrated loop, and multi-switch fabric.
Planning Considerations for Fibre Channel Topologies Fibre Channel Topologies The Director 2/64, Director 2/140, Edge Switch 2/16, Edge Switch 2/24, and Edge Switch 2/32 support point-to-point and multi-switch fabric topologies, and indirectly support arbitrated loop topology. A combination of these topologies (hybrid topology) is also supported. Related HP switches support switched mode and traditional (shared mode) arbitrated loop topologies, and indirectly support a switched fabric topology.
Planning Considerations for Fibre Channel Topologies ■ Multiswitch fabric — This topology provides the ability to connect directors and edge switches through expansion ports (E_Ports) or interswitch links (ISLs) to form a Fibre Channel fabric. Director or switch 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.
Planning Considerations for Fibre Channel Topologies Characteristics of Arbitrated Loop Operation When implementing Fibre Channel arbitrated loop topology, consideration must be given to switch operating mode, device connectivity, and loop configuration. This section describes the characteristics of arbitrated loop operation, including: ■ Switch operation in shared mode or switched mode. ■ Connectivity of public loop devices and private loop devices.
Planning Considerations for Fibre Channel Topologies Figure 21: Shared mode operation ■ Switched mode — When set to switched mode or by default, the switch bypasses full loop arbitration and enables frame transmission through logical connected device pairs. Connections can be established between H_Port pairs, or between an H_Port and fabric loop port (FL_Port).
Planning Considerations for Fibre Channel Topologies Figure 22: Switched mode operation Public Versus Private Devices Arbitrated loop switches support connection of public and private arbitrated loop devices as follows: ■ 62 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.
Planning Considerations for Fibre Channel Topologies Figure 23: Public device connectivity Public devices support normal fabric operational requirements, such as fabric busy and reject conditions, frame multiplexing, and frame delivery order. ■ Private device — A loop device that cannot transmit an FLOGI command to the switch nor communicate with fabric-attached devices is a private device.
Planning Considerations for Fibre Channel Topologies Figure 24: Private device connectivity 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.
Planning Considerations for Fibre Channel Topologies Public Versus Private Loops Arbitrated loop switches support operation of public and private loops as follows: ■ Public loop — A public loop is connected to a switched fabric (through the switch B_Port) and the switch has an active embedded FL_Port that is user transparent. All devices attached to the loop can communicate with each other, and public devices attached to the loop can communicate with fabric-attached devices.
Planning Considerations for Fibre Channel Topologies B_Port Loop Switch Embedded FL_Port H_Ports D1 S1 Figure 26: Private loop connectivity Planning for Private Arbitrated Loop Connectivity Private arbitrated loop topology supports the clustering of isolated servers and storage subsystems into workgroup or departmental SANs. This topology is well suited to small and mid-sized configurations where modest connectivity levels and high data transmission speeds are required.
Planning Considerations for Fibre Channel Topologies Shared Mode Operation When set to shared mode, a loop switch implements standard Fibre Channel arbitrated loop topology, and distributes the frame routing function through each loop port. Shared mode operation and its simplified logical equivalent are illustrated in Figure 27.
Planning Considerations for Fibre Channel Topologies Hubs are cascaded through H_Port-to-H_Port connections (one port per switch or hub). Server S1 communicates with device D1 through a loop that includes H_Ports on all three hubs and NL_Ports on the remaining 18 devices. Loop Switch Loop Switch H_Ports Hub Hub H_Ports S1 D1 Figure 28: 20-Device private arbitrated loop Although connection of additional devices to a loop does not impact switch bandwidth (1.
Planning Considerations for Fibre Channel Topologies ■ Number of loop tenancies — Each cycle of device arbitration, loop opening, frame transmission, frame reception, and loop closing is called a loop tenancy. A Fibre Channel operation, such as a small computer system interface (SCSI) write command, may require several tenancies to complete. Because significant overhead is associated with establishing and ending each loop tenancy, an increase in tenancies decreases loop performance.
Planning Considerations for Fibre Channel Topologies Switched Mode Operation When set to switched mode (default setting), a loop switch enables frame transmission through multiple point-to-point connected pairs. Switched mode operation and its simplified logical equivalent are illustrated in Figure 29. Part (A) of Figure 29 shows server S1 connected to device D1 through a switched pair of H_Ports, communicating at 1.0625 Gbps.
Planning Considerations for Fibre Channel Topologies Loop Switch H_Ports H_Ports Hub S1 Hub S2 D1 Hub S3 D2 Hub S4 D3 Hub S5 D4 Hub S6 D5 Hub S7 D6 Hub S8 D7 D8 Figure 30: Switched mode operation with eight independent looplets When communication within two or more looplets ceases, a device attached to one looplet can be switched to communicate with a device attached to another looplet.
Planning Considerations for Fibre Channel Topologies ■ Consider the data traffic capacity of the department or workgroup (normal and peak load) as part of the switch planning and installation process. Such capacity planning: — Ensures loop traffic is distributed and balanced across servers and storage devices. — Identifies traffic bottlenecks and provides for alternate connectivity solutions if required.
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 a loop switch B_Port. This topology is well suited for: ■ Providing connectivity between a workgroup or departmental SAN and a switched fabric, thus implementing connectivity of FC-AL devices to fabric devices at the core of the enterprise.
Planning Considerations for Fibre Channel Topologies The switch B_Port provides a single 1.0625 Gbps ISL to an E_Port on a director or edge switch. Direct ISL connectivity between loop switches (with or without a redundant B_Port connection to a director or edge switch) is generally not supported. However, a director or edge switch does support the connection of multiple, independent switches. Figure 31 shows a configuration of two loop switches attached to a director.
Planning Considerations for Fibre Channel Topologies ■ Although the B_Port connection (ISL) between the director and switch is a 1.0625 Gbps serial connection, burst transmissions from multiple FC-AL devices are multiplexed and buffered (the link BB_Credit value is eight), and may coexist in the link. Therefore, the sum of the bandwidths of all devices contending for B_Port access should not exceed 1.0625 Gbps. Exceeding the total bandwidth may result in degraded performance, as shown in Figure 32.
Planning Considerations for Fibre Channel Topologies Server Consolidation Providing fabric connectivity for multiple low-bandwidth servers (Windows NT or UNIX-based) by attaching them individually to an expensive Fibre Channel director is not a cost-effective solution. A practical solution is to consolidate the servers on an inexpensive loop switch, then connect the switch to a single director or edge switch E_Port.
Planning Considerations for Fibre Channel Topologies Tape Device Consolidation Providing fabric connectivity for multiple FC-AL tape drives by 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 single director or edge switch E_Port. Figure 34 illustrates the consolidation of three tape drives through one B_Port connection to a director.
Planning Considerations for Fibre Channel Topologies Planning for Multi-Switch Fabric Support A Fibre Channel topology that consists of one or more interconnected director or switch elements is called a fabric. The product operational software provides the ability to interconnect directors and switches (through E_Port connections) to form a multi-switch fabric. Support of multi-switch fabric operation is a major feature of a director or edge switch.
Planning Considerations for Fibre Channel Topologies Fabric elements cooperate to receive data from the N_Port of an attached device, route the data through the proper director or switch fabric ports (F_Ports), and deliver the data to the N_Port of a destination device. The data transmission path through the fabric is typically determined by the fabric elements and is transparent to the user.
Planning Considerations for Fibre Channel Topologies ■ Hop count — The Fibre Channel theoretical limit of ISL connections traversed (hop count) in a single path through the fabric is seven. The maximum hop count supported by a fabric is based on current design rules. For information, refer to http://h18000.www1.hp.com/products/storageworks/san/documentation.html or contact your local HP sales representative.
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.
Planning Considerations for Fibre Channel Topologies Table 2: ISL Transfer Rate versus Fabric Port Availability (Two-Director Fabric) Number of ISLs ISL Data Transfer Rate (at 1.0625 Gbps) ISL Data Transfer Rate (at 2.125 Gbps) 1 1.0625 Gbps 2.1250 Gbps 126 2 2.1250 Gbps 4.2500 Gbps 124 3 3.1875 Gbps 6.3750 Gbps 122 4 4.2500 Gbps 8.5000 Gbps 120 5 5.3125 Gbps 10.6250 Gbps 118 6 6.3750 Gbps 12.7500 Gbps 116 7 7.4375 Gbps 14.8750 Gbps 114 8 8.5000 Gbps 17.
Planning Considerations for Fibre Channel Topologies Special consideration must also be given to applications with high data transfer rates or devices that participate in frequent or critical data transfer operations. For example, in Figure 35 on page 78, suppose device D7 is a server and device D9 is a storage unit and both devices participate in a critical nightly backup operation.
Planning Considerations for Fibre Channel Topologies Note that at least one director or switch in a multi-switch fabric needs to be set as Principal or Default. If all the fabric elements are set to Never Principal, all ISLs will segment. If all but one element are set to Never Principal and the element that was Principal goes offline, then all of the other ISLs will segment. Note: HP recommends configuring the switch priority as Default.
Planning Considerations for Fibre Channel Topologies When assigning preferred domain IDs in an open fabric with directors and switches supplied by multiple OEMs, be aware of the following: — For directors and switches, the firmware adds a base offset of 96 (hexadecimal 60) to the numerically assigned preferred domain ID. Therefore, if a user assigns a director or switch a numerical preferred domain ID of 1, the firmware assigns a hexadecimal domain ID of 61.
Planning Considerations for Fibre Channel Topologies When multiple minimum-hop paths (ISLs) between fabric elements are detected, firmware balances the data transfer load and assigns ISLs as follows: — The director or switch assigns an equal number of device entry ports (F_Ports) to each E_Port connected to an ISL. For example, if a fabric element has two ISLs and six attached devices, the load from three devices is transferred through each ISL.
Planning Considerations for Fibre Channel Topologies — Incompatible zoning configurations — Zoning configurations for the two fabric elements are not compatible. For an explanation, refer to “Configuring Zones” on page 133. — Build fabric protocol error — A protocol error is detected during the process of forming the fabric. — No principal switch — No director or switch in the fabric is capable of becoming the principal switch.
Planning Considerations for Fibre Channel Topologies ■ Zoning configurations for joined fabrics — In a multi-switch fabric, zoning is configured on a fabric-wide basis, and any change to the active zone set is applied to all directors and switches. To ensure zoning is consistent across a fabric, the following rules are enforced when two fabrics (zoned or unzoned) join through an ISL. — Fabric A unzoned and Fabric B unzoned — The fabrics join successfully, and the resulting fabric remains unzoned.
Planning Considerations for Fibre Channel Topologies 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 HP, and are deployed in several customer environments. Fabric topologies described in this section include: ■ Cascaded. ■ Ring. ■ Mesh.
Planning Considerations for Fibre Channel Topologies TM 10/100 RST 31 30 29 28 27 26 25 24 23 22 TM 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 5 3 1 PWR ERR 6 4 2 0 10/100 RST TM PWR TM ERR Interswitch Link Fabric Connection Figure 36: Cascaded fabric One design variation is to use more than one ISL between fabric elements. This eliminates ISLs as a single point of failure and greatly increases the fabric design reliability.
Planning Considerations for Fibre Channel Topologies Ring Fabric A ring fabric consists of a continuous string of directors or switches connected by one or more ISLs. Each fabric element is connected to the next fabric element (like a cascaded fabric, but with the end-point fabric elements connected). Figure 37 illustrates a ring fabric topology.
Planning Considerations for Fibre Channel Topologies Mesh Fabric There are two types of mesh fabrics: full mesh and modified (or partial) mesh. In a full-mesh topology, every director or switch is directly connected to all directors and switches in the fabric. The maximum hop count between fabric-attached devices is one hop. Figure 38 illustrates a full-mesh fabric topology.
Planning Considerations for Fibre Channel Topologies When using low port-count fabric elements, mesh fabrics are best used when the fabric is not expected to grow beyond four or five switches. The cost of ISLs becomes prohibitive for larger mesh fabrics. In addition, full-mesh fabrics do not scale easily because the addition of a switch requires that at least one additional ISL be added from every existing switch in the fabric.
Planning Considerations for Fibre Channel Topologies Core-to-Edge Fabric A core-to-edge fabric consists of one or more Fibre Channel directors or switches acting as core elements that are dedicated to connecting other directors and switches (edge elements) in the fabric. Core directors act as high-bandwidth routers with connectivity to edge fabric elements. Figure 39 illustrates the core-to-edge fabric topology with two core directors and fourteen edge directors and switches (2-by-14 topology).
Planning Considerations for Fibre Channel Topologies Subject to large fabric design constraints, core-to-edge fabrics are easy to scale through the addition of core elements. Figure 40 illustrates a core-to-edge fabric topology with four core directors and twelve edge directors and switches (4-by-12 topology).
Planning Considerations for Fibre Channel Topologies The simplest core-to edge fabric has two or more core switching elements that may or may not be connected (simple or complex). In a simple core topology, as shown in Figure 39 on page 94, core switches are not connected. In a complex core topology, as shown in Figure 40 on page 95, core switches are connected. The figure also illustrates a topology where the core is a full-mesh fabric.
Planning Considerations for Fibre Channel Topologies Planning a Fibre Channel Fabric Topology To be effective, the fabric topology design must: ■ Solve the customer’s business problem and provide the required level of performance. ■ Meet the customer’s requirements for high availability. ■ Be scalable to meet future requirements.
Planning Considerations for Fibre Channel Topologies I/O Requirements HP directors and switches are designed with non-blocking architecture; therefore, any two switch ports can communicate at the full Fibre Channel bandwidth of 2.125 Gbps without impact to other switch ports. Because most SAN-attached devices are not capable of generating I/O traffic at the full bandwidth, there is little potential for congestion between two devices attached through a single director or switch.
Planning Considerations for Fibre Channel Topologies Prior to fabric design, application I/O profiles should be estimated or established that classify the application bandwidth requirements. Bandwidth consumption is classified as light, medium, or heavy. These classifications must be considered when planning ISL and device connectivity. For information about application I/O (in Gbps) and fabric performance problems due to ISL connectivity, refer to “ISL Oversubscription.
Planning Considerations for Fibre Channel Topologies Depending on fabric performance requirements and cost, there are several options to solve ISL oversubscription problems, including: ■ Employ device locality — NT server 1 and its associated storage device can be connected through one director. NT server 2 and its associated storage device can be connected through the other director. As a result, minimal traffic flows across the ISL between directors and the congestion problem is mitigated.
Planning Considerations for Fibre Channel Topologies High Device Locality A Low Device Locality B High Traffic Low Traffic TM TM TM ISL TM ISL Figure 42: Device locality 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.
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 TM TM 1,000 IOPS 1,000 IOPS 1,000 IOPS 1,000 IOPS Interswitch Link Fabric Connection 1,000 IOPS 1,000 IOPS Figure 43: Device fan-out ratio Performance Tuning When designing or tuning a fabric for performance, it is critical to understand application I/O characteristics so that: 102 ■ Device output in Gbps does not oversubscribe ISLs, leading to fabric c
Planning Considerations for Fibre Channel Topologies Figure 44 illustrates performance tuning for a simple fabric using appropriate ISL connectivity, device locality, and fan-out regions for device connectivity.
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).
Planning Considerations for Fibre Channel Topologies Fibre Channel fabrics are classified by four levels of resiliency and redundancy. From least available to most available, the classification levels are: ■ Nonresilient single fabric — Directors and switches are connected to form a single fabric that contains at least one single point of failure (fabric element or ISL). Such a failure causes the fabric to fail and segment into two or more smaller fabrics.
Planning Considerations for Fibre Channel Topologies Figure 45 illustrates simple redundant fabrics. Fabric “A” and fabric “B” are symmetrical, each containing one core director and four edge switches. All servers and storage devices are connected to both fabrics.
Planning Considerations for Fibre Channel Topologies Fabric Scalability A scalable fabric allows for nondisruptive addition of fabric elements (directors and switches) or ISLs to increase the size or performance of the fabric. Scalability also relates to investment protection. If a core edge switch is replaced with a newer or higher port count switch, it is often valuable to use the existing switch elsewhere in the fabric (at the edge).
Planning Considerations for Fibre Channel Topologies ■ Employ a routing protocol to establish the shortest path through the fabric and program route tables for each fabric element. ■ Exchange the active zone set to ensure uniform zoning is enforced between all fabric elements. However, fabric initialization is not a serial process.
Planning Considerations for Fibre Channel Topologies In addition to OEM limitations not discussed in this publication, the considerations that need to be evaluated when intermixing FCP and FICON protocols are: ■ Director or switch management. ■ Port numbering versus port addressing. ■ Management limitations.
Planning Considerations for Fibre Channel Topologies Port Numbering Versus Port Addressing Consideration must be given to the implications of port numbering for the FCP protocol versus logical port addressing for the FICON protocol. FCP configuration attributes are implemented through zoning. Zones are configured through the associated Product Manager application by authorizing or restricting access to name server information associated with device N_Ports that attach to director or switch F_Ports.
Planning Considerations for Fibre Channel Topologies Although Figure 46 depicts a UPM card map only for the Director 2/64, physical port numbers and logical port addresses can be extrapolated for the Director 2/140 (140 ports), Edge Switch 2/16 (16 ports), Edge Switch 2/24 (24 ports), and Edge Switch 2/32 (32 ports).
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.
Planning Considerations for Fibre Channel Topologies ■ Intermix operation in Open Systems management style — When the director or switch is set to Open Systems management style, a traditional Fibre Channel fabric consisting of multiple domains (fabric elements) is supported. Inband management through the OSMS is also supported.
Planning Considerations for Fibre Channel Topologies Multiple Data Transmission Speeds in a Single Fabric The Director 2/64, Edge Switch 2/16, and Edge Switch 2/32 support auto-sensing of 1.0625 and 2.125 Gbps device connections. The introduction of a higher data transmission speed to the SAN design provides several benefits and alternatives: ■ High-speed device connectivity — As Fibre Channel devices and HBAs evolve and become 2.
Physical Planning Considerations 4 This chapter describes the physical planning considerations for incorporating Hewlett-Packard (HP) Director 2/64s, Edge Switch 2/16s, and Edge Switch 2/32s into storage area networks (SANs) and Fibre Channel fabric topologies. The chapter provides planning considerations and recommendations for: ■ Port connectivity and fiber-optic cabling. ■ High Availability Fabric Manager (HAFM) server, Ethernet local area network (LAN), and remote access support.
Physical Planning Considerations Port Connectivity and Fiber-Optic Cabling This section provides planning recommendations for director and switch port connectivity and fiber-optic cabling. Recommendations are provided for: ■ Port requirements (number and type of ports). ■ Small form factor pluggable (SFP) optical transceivers. ■ Extended-distance ports. ■ High-availability considerations. ■ Cabling and connectors. ■ Routing fiber-optic cables.
Physical Planning Considerations ■ Director 2/140 — The director is configured from a minimum of 16 universal port module (UPM) cards (64 ports total), to a maximum of 35 UPM cards (140 ports total). UPM cards provide four 2.125 Gbps port connections, and can be configured with shortwave transceivers, longwave transceivers, and extended longwave laser transceivers, or a combination of all three.
Physical Planning Considerations Consider the following when determining the number and type of each transceiver to use: ■ Distance between a director or switch and the attached Fibre Channel device, or between fabric elements communicating through an ISL. ■ Cost effectiveness. ■ Device restrictions or requirements with respect to existing fiber-optic cable (multimode or single-mode).
Physical Planning Considerations Extended-Distance Ports Through longwave laser transceivers and repeaters or dense wavelength division multiplexing (DWDM) equipment, directors and edge switches support Fibre Channel data transmission distances of up to 100 km at 1 Gbps, or 50 km at 2 Gbps. The extended distance feature is enabled on a port-by-port basis by activating the 10-100 km check box for a specified port at the Product Manager application’s Configure Ports dialog box.
Physical Planning Considerations Cables and Connectors This section provides Fibre Channel cable and connector planning information as follows: ■ Cables for all directors and switches. ■ Optical connectors for Director 2/64, Director 2/140, Edge Switch 2/16, Switch 2/24, and Edge Switch 2/32. Cables Fiber-optic jumper cables are required to connect director and switch ports to servers, devices, distribution panels, or other elements in a multi-switch fabric.
Physical Planning Considerations Director and Switch Connectors Multimode or single-mode cables attach to Director 2/64, Director 2/140, Edge Switch 2/16, Edge Switch 2/24, and Edge Switch 2/32 ports with SFP optical transceivers with LC duplex connectors. Figure 47 illustrates an SFP transceiver and LC duplex connector.
Physical Planning Considerations The need for additional fiber-optic cabling could grow rapidly. More cables may be required for connections to additional servers or storage devices, or for connections to additional fabric elements as a multi-switch fabric is developed. The director or switch may need to be moved for more efficient connection to other units, but still maintain its original connections.
Physical Planning Considerations HAFM Server Connectivity The HAFM server provides an auto-detecting 10/100 Base-T Ethernet interface that connects to a hub. Each director CTP card or switch front panel also provides an auto-detecting 10/100 Base-T Ethernet interface that connects to a hub. A 12-port hub can be ordered from HP and installed at the top front of the equipment rack. Although directors provide two Ethernet connections to a hub, only one connection is active at a time.
Physical Planning Considerations Connectivity Planning Considerations Directors, switches, and the HAFM server can be delivered in an HP-supplied equipment rack in accordance with customer specifications. Consider the following Ethernet connectivity issues when: ■ Installing additional rack-mount products — When installing an additional director or switch, the length of Ethernet cable required to provide LAN connectivity is a function of rack position (top, bottom, or adjacent to the slide-out drawer).
Physical Planning Considerations The LAN interface can be: ■ Part of the customer’s public 10/100 Mbps LAN segment that provides access to managed directors and switches. This product-to-HAFM server Ethernet connection is part of the equipment rack installation and is required. Connection of remote workstations through the hub is optional. This type of network configuration using one Ethernet connection through the HAFM server is shown in Figure 48 on page 126. Director 2/64s are used as an example.
Physical Planning Considerations 1 2 Two Director 2/64s HP Ethernet hub 3 4 HAFM server (laptop or rack mount) Remote user workstation Figure 48: Typical network configuration (one Ethernet connection) ■ Part of a second HAFM server interface that connects to the customer’s private intranet and allows operation of the HAFM and Product Manager applications from remote user PCs or workstations. Connection to this LAN segment is optional and depends on customer requirements.
Physical Planning Considerations Figure 49: Typical network configuration (two Ethernet connections) SAN High Availability Planning Guide 127
Physical Planning Considerations SNMP Management Workstations An SNMP agent that runs on the HAFM server can be configured through the HAFM application. This agent implements Version 3.1 of the Fibre Alliance management information base (MIB). The agent can be configured to send SNMP trap messages to up to 12 recipients. In addition, there is a separate SNMP agent that runs on each director or switch that is configured through the Product Manager application.
Physical Planning Considerations Inband Management Access (Optional) Inband management console access (through a Fibre Channel port) is provided by enabling user-specified features that allow Open Systems or FICON host control of a director or switch. The features are mutually exclusive; only one can be installed at a time. Features are enabled through a feature key encoded to work with the serial number of a unique director or switch.
Physical Planning Considerations When the FICON management server (FMS) feature key is enabled at the Product Manager application, host control and management of the director or switch is provided through an IBM server attached to a product port. The server communicates with the product through a FICON channel.
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 HAFM application, Product Manager application, and Web server interface) is restricted by implementing password protection. Access to attached computing resources (including applications and data) is restricted by implementing name server zoning.
Physical Planning Considerations The system administrator can also use the HAFM application to assign remote workstation access to directors and switches. Remote sessions can be allowed for anyone on a customer intranet, disallowed completely, or restricted to specific workstations. Remote users must log into the HAFM application with a user name and password, just as when logging in to the local HAFM server. Passwords are encrypted when sent across the network.
Physical Planning Considerations Benefits of Zoning System administrators create zones to increase network security measures, differentiate between operating systems, and prevent data loss or corruption by controlling access between devices (such as servers and data storage units), or between separate user groups (such as engineering or human resources). Zoning allows an administrator to establish: ■ Logical subsets of closed user groups.
Physical Planning Considerations ■ The domain identification (ID) and physical port number of the director or switch port to which the device is attached. Caution: If zoning is implemented by port number, a change to the director or switch fiber-optic cable configuration disrupts zone operation and may incorrectly include or exclude a device from a zone. A zone contains a set of attached devices that can access each other. Zones are grouped into zone sets.
Physical Planning Considerations ■ Default zone — The default zone consists of all devices not configured as members of a zone in the active zone set. If there is no active zone set, all devices attached to the fabric are in the default zone. For the default zone: — The default zone is enabled or disabled separately from the active zone set. — If the default zone is enabled, all devices not in a specified zone are included in the default zone and can communicate with each other.
Physical Planning Considerations Factors to Consider When Implementing Zoning Consider the following factors when planning to implement zoning for one or more directors or switches in the enterprise. In particular, consider the implications of zoning within a multi-switch fabric. ■ Reasons for zone implementation — Determine if zoning is to be implemented for the enterprise.
Physical Planning Considerations For persistent binding: ■ 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. — Different storage volume managers and file systems. — Different fabric devices, including disk drives, tape drives, and tape libraries.
Physical Planning Considerations Optional Features HP offers several operating features that are available for the switch as customer-specified options. Available features include: ■ Open Systems Management Server or FICON Management Server — Inband director or switch management is provided through purchase of the OSMS or FMS feature. Note: The Edge Switch 2/24 does not support out-of-band management through FMS.
Physical Planning Considerations Inband Management Console Access Inband management console access (through a Fibre Channel port) is provided by enabling user-specified features that allow Open Systems (OSMS) or FICON (FMS) host control of a director or switch. The features are mutually exclusive; only one can be installed at a time.
Physical Planning Considerations ■ The minimum OS/390 level for a director or switch without the control unit port (CUP) feature is Version 2.6, plus service listed in PSP bucket upgrade 2032, device subset 2032OS390G5+. The minimum OS/390 level for a director or switch with the CUP feature is Version 2.1, plus service listed in the preceding PSP bucket for that function. ■ A host-attached Hardware Management Console.
Physical Planning Considerations ■ Switch binding — Using the switch binding feature, an administrator allows only specified devices and fabric elements to connect to specified director or fabric switch ports. This provides security in environments that include a large number of devices by ensuring that only the intended set of devices attaches to a director or switch. This feature is managed through the Product Manager application.
Physical Planning Considerations SANtegrity Binding Planning Considerations Fabric and switch binding enhance data security by controlling and monitoring director, fabric switch, and device connectivity. The name server zoning feature also provides data security by partitioning devices into restricted-access zones. Use of the SANtegrity Binding and zoning features in conjunction with each other must be carefully planned and coordinated.
Physical Planning Considerations The figure illustrates two Director 2/64 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 to director B without regard to any data rates.
Physical Planning Considerations 144 SAN High Availability Planning Guide
Configuration Planning Tasks 5 This chapter describes configuration planning tasks to be performed before installing the High Availability Fabric Manager (HAFM) server and one or more Director 2/64s, Director 2/140s, Edge Switch 2/16s, Edge Switch 2/24s, or Edge Switch 2/32s in a storage area network (SAN) configuration. The following planning tasks are described in the chapter. ■ Task 1: Prepare a Site Plan. ■ Task 2: Plan Fibre Channel Cable Routing.
Configuration Planning Tasks Task 1: Prepare a Site Plan For each director, switch, or equipment rack installed, design a site plan that provides efficient work flow, operator convenience and safety, and adequate service clearances for the equipment rack. A customer manager should review the site plan with a service representative and consider: ■ Location and relationship of the physical facilities such as walls, doors, windows, partitions, furniture, and telephones.
Configuration Planning Tasks ■ Security necessary to protect the installation’s physical integrity, while maintaining accessibility to the director or switch. ■ Equipment rack front and rear service clearances, operator clearances, and maintenance access clearances. ■ Weight of an equipment rack. Either multiple persons or a lift must be available during installation to remove the rack from the packing crate. ■ Heat dissipation, temperature and humidity requirements.
Configuration Planning Tasks Table 4 lists physical planning and hardware installation tasks, and includes the activity, task owner, due date, and comments. Table 4: Physical Planning and Hardware Installation Tasks Activity Task Owner Due Date Comments Locate the physical facilities. Connect the facility alternating current (AC) power circuits. If more than one director or switch, consider separate power circuits for availability. Obtain an uninterruptable power supply (optional). Recommended.
Configuration Planning Tasks Table 5 lists operational setup tasks, and includes the task owner, due date, and comments. Table 5: Operational Setup Tasks Activity Obtain IP address and subnet mask. Task Owner Due Date Comments HAFM server (if installing on a LAN with non-HP devices). Directors and switches (if installing on a LAN with non-HP devices). Remote user workstation (optional). Simple network management protocol (SNMP) management stations (optional).
Configuration Planning Tasks Table 5: Operational Setup Tasks (Continued) Activity Determine SNMP access to directors and switches. Task Owner Due Date Comments Obtain SNMP trap recipient IP addresses. Determine SNMP information required (generic and productspecific). Determine if write permission is required for modifying SNMP variables. Determine if a multi-switch fabric is to be implemented. Determine if the zone management feature is to be used.
Configuration Planning Tasks Task 2: Plan Fibre Channel Cable Routing Plan for sufficient single-mode fiber-optic and multimode fiber-optic cabling to meet the connectivity requirements for all Fibre Channel servers and devices. If a multi-switch fabric is to be enabled, plan for sufficient fiber-optic cabling to meet interswitch link (ISL) connectivity requirements. Plan for at least one meter (39.
Configuration Planning Tasks Task 3: Consider Interoperability with Fabric Elements and End Devices HP conducts a substantial level of testing to ensure director and switch interoperability with fabric elements and end devices provided by multiple original equipment manufacturers (OEMs). New devices are tested and qualified on a continual basis. Contact your HP representative for the latest information about fabric element, server, host bus adapter (HBA), and device interoperability.
Configuration Planning Tasks Task 4: Plan Console Management Support Plan to implement one or more of the following methods to provide console management and support for directors and switches: ■ HAFM server — The rack-mounted HAFM server is used for product installation, initial software configuration, changing the configuration, and monitoring product operation. — When the HAFM application and Product Manager applications are installed on the HAFM server, the server is used as a local user workstation.
Configuration Planning Tasks If director or switch management through an IBM host is planned, ensure the FMS feature key is ordered with the Product Manager application. This feature key enables host control of the product from an IBM System/390 or zSeries 900 Parallel Enterprise server attached to a Fibre Channel port. ■ Web server interface — If Internet access to a director or switch Embedded Web Server interface is required, plan for access to an analog phone line.
Configuration Planning Tasks Task 6: Plan Network Addresses Depending on the configuration of the LAN on which directors, switches, and the HAFM server are installed, plan network addressing as follows: ■ If installing products and the HAFM server on a dedicated (private) LAN segment, there is no requirement to change any default network addresses. If multiple equipment racks are connected, ensure all directors, switches, and servers have unique IP addresses.
Configuration Planning Tasks ■ HAFM server: — MAC address is unique. — IP address of the Ethernet adapter is 10.1.1.1. — Subnet mask is 255.0.0.0. — Gateway address is blank. Task 7: Plan SNMP Support (Optional) As an option, network administrators can use the HAFM application to configure an SNMP agent that runs on the HAFM server. This agent can be configured to send generic SNMP trap messages to up to 12 SNMP management workstations.
Configuration Planning Tasks Task 8: Plan E-Mail Notification (Optional) As an option, network administrators can configure director and switch e-mail support. The following support considerations are required if the e-mail notification feature is used: ■ Determine if e-mail notification is to be configured and used for significant system events. ■ Determine which persons (up to five) require e-mail notification of significant director or switch events and record their e-mail addresses.
Configuration Planning Tasks Task 10: Plan Phone Connections Plan for one or more telephone connections near the HAFM server for service personnel use. While performing a diagnostic or repair action, a service representative or network administrator at the HAFM server may require voice technical support through a telephone connection.
Configuration Planning Tasks Rules for Port Names Port names can be up to 24 alphanumeric characters in length. Spaces, hyphens ( - ), and underscores ( _ ) are allowed within the name. Each port name must be unique for a director; however, the same port name can be used on separate directors and switches. HP recommends unique port names be used, particularly within a complex multi-switch fabric.
Configuration Planning Tasks Product Planning Worksheet (Page 1 of 4) Director or Switch Name: ____________________________ IP Address: ____________________________ Unit Name: ____________________________ Attached Devices Port Type Port Name Location Model IP Address Zone 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 160 SAN High Availability Planning Guide
Configuration Planning Tasks Product Planning Worksheet (Page 2 of 4) Director or Switch Name: ____________________________ IP Address: ____________________________ Unit Name: ____________________________ Attached Devices Port Type Port Name Location Model IP Address Zone 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SAN High Availability Planning Guide 161
Configuration Planning Tasks Product Planning Worksheet (Page 3 of 4) Director or Switch Name: ____________________________ IP Address: ____________________________ Unit Name: ____________________________ Attached Devices Port Type Port Name Location Model IP Address Zone 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 162 SAN High Availability Planning Guide
Configuration Planning Tasks Product Planning Worksheet (Page 4 of 4) Director or Switch Name: ____________________________ IP Address: ____________________________ Unit Name: ____________________________ Attached Devices Port Type Port Name Location Model IP Address Zone 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 SAN High Availability Planning Guide 163
Configuration Planning Tasks Task 14: Plan AC Power Plan for facility power sources for each equipment rack. Directors and switches in the rack operate at 50 to 60 Hertz (Hz) and 100 to 240 volts alternating current (VAC), and require a minimum dedicated 5-ampere service. If two power sources are supplied (optional but recommended for high availability), the equipment rack contains two customer-specified external power cords.
Configuration Planning Tasks Task 15: Plan a Multi-Switch Fabric (Optional) If a multi-switch fabric topology is to be implemented, carefully plan the physical characteristics and performance objectives of the topology. Include the proposed number of fabric elements, characteristics of attached devices, cost, nondisruptive growth requirements, and service requirements.
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 (differentiation of operating systems, data sets, user groups, devices, or processes) of zone members, zones, and zone sets. If a fabric topology is implemented, zoning is configured on a fabric-wide basis. Planning for zoned configurations must be carefully coordinated with planning a fabric topology.
index A B backup HAFM data directory 46 NVRAM configuration 45 balancing data loads 82 bandwidth director 19 requirements 81 beaconing 35 SAN High Availability Planning Guide Index C Index addresses director gateway address 155 IP address 155 MAC address 155 subnet mask 155 HAFM server gateway address 156 IP address 156 MAC address 156 subnet mask 156 arbitrated loop switch, see FC-AL switch arbitrated loop typology characteristics 60 overview 58 audience 10 authorized reseller, HP 14 binding fabric
Index D data access type 98 data collection 35 default director network addresses 155 HAFM server network addresses 156 definition arbitrated loop 15 director 2/64 15 FC-AL switch 16 description fabric switch 25 software 47 design considerations fabric topology 107 device looplet 70 Tier 1 96 Tier 2 96 Tier 3 96 device fan-out ratio 101 device locality 100 device, private 63 device, public 62 director bandwidth 19 consolidating servers 76 consolidating tape drives 77 definition 15 description 18 high avail
Index fabric island topology 96 fabric switch description 25 performance 25 fabric-attached loop connectivity 73 Fabrics View 51 Topology tab 51 Zone Set tab 52 fan-out ratio 101 FC-AL fabric attached-loop connectivity 73 feature key description 138 Flexport technology 140 FMS 139 format 138 Open Trunking 142 OSMS 139 SANtegrity Binding 140 features connectivity 32 product 32 security 33 serviceability 34 Fibre Channel topologies 58 Fibre Connection management server, see FMS Fibre Connection, see FICON FI
Index I M I/O block size 98 I/O profile 98 I/O traffic requirements 98 inband management access methods 39 inband product management feature keys 139 incorporating switching products 57 introduction director 21, 23 IP address director default 155 HAFM server default 156 ISL, oversubscription 99 ISLs, maximum number 79 MAC address director default 155 HAFM server default 156 management HAFM application 38 out-of-band 38 SNMP agent 38 web server 38 management information bases director-specific MIB 35 Fab
Index notifications, state changes 87 number of loop tenancies 69 O Open Trunking feature description 142 open-system management server description 139 open-system management server, see OSMS optional feature key description 138 Flexport technology 140 FMS 139 format 138 Open Trunking 142 OSMS 139 SANtegrity Binding 140 OSMS product management 39 OSMS feature description 139 out-of-band management description 38 oversubscription, ISL 99 P passwords 33 path selection 85 performance director 19 fabric 97 f
Index R rack stability, warning 13 RAM 42 ration, fan-out 101 read/write mixture 98 redundant fabric 105 related documentation 10 remote user workstations PC platforms 43 UNIX workstations 43 requirements I/O profile 98 I/O traffic 98 restore HAFM data directory 46 NVRAM configuration 45 ring fabric topology 91 RJ-45 connector 42 round-trip time, loop 68 RS-232 maintenance port 34 S S/390 40 SANtegrity Binding feature description 140 Enterprise Fabric mode 141 planning considerations 142 scalable fabric 1
Index T tape drives, consolidation 77 technical support, HP 14 tenancy, loop 69 text symbols 12 Tier 1 96 Tier 2 96 Tier 3 96 topology cascaded fabric 89 core-to-edge fabric 94 fabric island 96 Fibre Channel 58 mesh fabric 92 private arbitrated loop 66 public arbitrated loop 73 ring fabric 91 types of 58 topology support director 20 Topology tab 51 topology, planning 97 tuning, performance 102 typology arbitrated loop characteristics 60 overview 58 SAN High Availability Planning Guide hybrid 58 multiswit
Index 174 SAN High Availability Planning Guide
