HP SAN Design Reference Guide Abstract This reference document provides information about HP SAN architecture, including Fibre Channel, iSCSI, FCoE, SAN extension, and hardware interoperability. Storage architects and system administrators can use this document to plan, design, and maintain an HP SAN.
© Copyright 2001-2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents I Architecture..............................................................................................15 1 SAN design overview............................................................................16 SAN solutions....................................................................................................................16 HP SAN implementations....................................................................................................17 SAN components.....................
Migrating a cascaded fabric SAN...................................................................................41 Migrating a meshed fabric SAN.....................................................................................42 Migrating a ring fabric SAN...........................................................................................42 3 Fibre Channel routing............................................................................43 Fibre Channel routing overview........................
HP 5820 Converged Network Switch...............................................................................82 Usage.....................................................................................................................82 FCoE Converged Network Switch fabric rules...............................................................82 Firmware, CNA, operating systems, and storage products support..............................83 B-series FCoE Converged Network switch................................
Model numbering.......................................................................................................141 Model naming............................................................................................................141 Switch models.............................................................................................................141 Features.....................................................................................................................142 Usage......
HP OpenVMS SAN rules..................................................................................................193 Host-based volume shadowing......................................................................................194 HP Tru64 UNIX SAN rules.................................................................................................194 Apple Mac OS X SAN rules..............................................................................................196 IBM AIX SAN rules..........
14 P9000/XP storage system rules...........................................................235 P9000/XP storage systems................................................................................................235 Heterogeneous SAN support........................................................................................235 Configuration rules......................................................................................................236 Zoning.............................................
WDM system characteristics.....................................................................................262 HP coarse wave division multiplexing........................................................................263 Third-party WDM products......................................................................................263 Extended fabric settings for Fibre Channel switches..........................................................264 B-series switch settings..................................
B-series MP Router configuration examples.................................................................293 C-series MDS 9216i, 9222i, IPS-4, IPS-8, 14/2 Multiprotocol Services Modules, 18/4 Multiservice Modules...................................................................................................294 HP storage replication products.........................................................................................295 SAN extension best practices for HP P6000 Continuous Access.............
Maximum configurations.....................................................................................331 HP iSCSI bridge products..................................................................................................332 Bridging and routing...................................................................................................332 iSCSI bridge to Fibre Channel.......................................................................................
Network Teaming..............................................................................................356 iSCSI initiators...................................................................................................356 Configuration rules.................................................................................................356 C-series iSCSI.............................................................................................................356 Modules overview.................
Resource protection.................................................................................................372 Data protection......................................................................................................373 Security validation..................................................................................................374 Storage security best practices...........................................................................................
SAN scaling...................................................................................................................401 Cascaded fabric expansion..........................................................................................401 Meshed fabric expansion.............................................................................................401 Ring fabric expansion..................................................................................................
Part I Architecture SAN architecture is presented in these chapters: • “SAN design overview” (page 16) • “SAN fabric topologies” (page 23) • “Fibre Channel routing” (page 43) • “Fibre Channel over Ethernet” (page 62)
1 SAN design overview SANs provide the data communication infrastructure for advanced, cost-efficient storage systems. SAN technology offers investment protection, management features, and I/O price performance to minimize capital expense. HP SAN architecture provides open network storage solutions for all sizes and types of businesses, including small-to-medium-sized IT departments and enterprise environments.
expenses for backup hardware are reduced. Increased system availability can help prevent costly downtime and lost data. • Centralized management You can manage consolidated storage by using web-based tools from any location, thus reducing labor costs. • Security SANs support network security measures, such as authentication, authorization, access control, and zoning. • Online scalability You can add storage capacity or expand the fabric as needs change.
SAN components A SAN consists of the following hardware and software components: • Switches A Fibre Channel switch creates the fabric of the SAN. By interconnecting switches, you can create scalable SANs with thousands of port connections. • Routers, bridges, and gateways Router functionality provides high levels of scalability, dynamic device sharing, and Fibre Channel network fault isolation.
SAN infrastructure You use fabric switches to create the SAN communication paths. The number of storage systems that can be connected is determined by the number of ports available and other hardware constraints. SANs enable expansion by scaling storage capacity across numerous systems and long distances. Scaling increases the number of devices and connections in a SAN. You can increase the number of switches in a fabric, or you can use routing technology to connect multiple SAN fabrics or multiple VSANs.
NOTE: This guide describes specific switch and fabric rules for SAN configuration. A heterogeneous environment requires coordination of components based on their rules to create a consolidated system. You must also consider the restrictions and requirements of the servers, HBAs, operating systems, cables, and other components.
multiple interswitch cable segments. Fibre Channel routing interconnects independent SAN islands (fabrics) or VSANs to form a single, geographically distributed SAN. For information about supported distances, see “B-series switches and fabric rules” (page 91). • Data availability A resilient SAN environment minimizes vulnerability to fabric or device failures and maximizes performance.
• Switch and hop counts Minimize the number of hops between devices that communicate regularly in the SAN. For information about switches and hop counts, see: • ◦ “B-series switches and fabric rules” (page 91) ◦ “C-series switches and fabric rules” (page 123) ◦ “H-series switches and fabric rules” (page 140) Oversubscription For improved performance, reduce the potential for oversubscription.
2 SAN fabric topologies This chapter discusses HP standard SAN fabric topologies.
Routed SAN fabrics HP standard fabric topologies support Fibre Channel routing. Fibre Channel routing enables connectivity between devices in multiple fabrics, Virtual Fabrics, or multiple VSANs. HP supports the following routed fabric technologies: • “B-series Meta SAN” (page 35) • “C-series VSANs with IVR” (page 36) • “H-series switches with TR” (page 37) FCoE SAN fabrics HP standard fabric topologies can integrate with FCoE technology.
(32 to 40 ports), or a Core or Director switch (64 to 240 ports), which have higher port counts. For a high-availability SAN, use two switches configured in a dual-fabric SAN.
Switch models All HP Fibre Channel switches are supported for use in a cascaded fabric topology. Cascaded fabric topologies typically use the SN6000 Fibre Channel Switch; the 8/20q Fibre Channel Switch (or the HP Simple SAN Connectivity Kit); or SAN, Fabric, or Edge switches, which support smaller incremental growth. NOTE: Over time, a cascaded fabric topology can result in increased hops between switches. B-series, C-series, and H-series fabrics must not exceed seven hops.
As you add switches, ISLs are connected to two or more adjacent switches to maintain mesh connectivity, ensuring path redundancy throughout the fabric (Figure 4). The additional ISL connectivity provides communicating devices with more paths through the fabric. This dramatically reduces the chance that, as you add switches, you will exceed the maximum hop count. Figure 4 ISL connections in a meshed fabric 25092a Switch models All HP Fibre Channel switches are supported for use in a meshed fabric topology.
NOTE: HP does not recommend the ring fabric for applications requiring many-to-many connectivity. Figure 5 Ring fabric 25093a If the ring fabric has fewer than 12 switches, you can add switches (called satellite switches) outside the ring to create more user ports (Figure 6). Satellite switches are not supported. NOTE: Adding satellite switches slightly reduces fabric availability.
Figure 6 Ring fabric with satellite switches 25094a Switch models All HP Fibre Channel switches are supported for use in a ring fabric topology. Ring fabric topologies typically use the SN6000 Fibre Channel Switch; the 8/20q Fibre Channel Switch (or the HP Simple SAN Connectivity Kit); or SAN, Fabric, or Edge switches, which support smaller incremental growth. To meet higher port-count requirements, use Core or Director switches.
Figure 7 Core-edge fabric (typical depiction) 25095a Core-edge fabric topologies are typically depicted as shown in Figure 7 (page 30), but can also be depicted hierarchically as shown in Figure 8 (page 30). Both figures represent the same physical implementation. How a topology is logically represented can help you understand the potential performance of a core-edge topology.
Table 1 Core-edge fabric topology types Topology type Description Fat tree At least 50% of edge ports are dedicated as ISLs, resulting in an ISL ratio of 1:1. Skinny tree Less than 50% of edge ports are dedicated as ISLs, resulting in an ISL ratio of x:1, where x is 2 or more. Recommended ISL ratios The core-edge fabric type has a high fabric cross-sectional bandwidth (the maximum amount of data that can pass through ISLs at the fabric midpoint, which is the central connection or core of the fabric).
Figure 9 Core-edge fabric (4 x 12) 8 16 24 32 40 48 56 1 9 17 25 33 41 49 57 2 10 18 26 34 42 50 58 3 11 19 27 35 43 51 59 4 12 20 28 36 44 52 60 5 13 21 29 37 45 53 61 6 14 22 30 38 46 54 62 7 15 23 31 39 47 55 63 0 8 16 24 32 40 48 56 1 9 17 25 33 41 49 57 2 10 18 26 34 42 50 58 3 11 19 27 35 43 51 59 4 12 20 28 36 44 52 60 5 13 21 29 37 45 53 61 6 14 22 30 38 46 54 62 7 15 23 31 39
Table 3 (page 33) lists the data access performance ratings for each SAN fabric topology.
C-series switches Table 5 (page 34) lists the C-series switch and port maximums for specific fabric topologies.
• “C-series VSANs with IVR” (page 36)—Implemented using C-series IVR. IVR provides selective Fibre Channel routing connectivity between devices in different VSANs. Ports on one or more switches can be assigned to different VSANs. • “H-series switches with TR” (page 37)—Implemented using the TR feature, which is available with firmware 8.x (or later).
Benefits A Meta SAN: • Allows fabric connections (without the need to merge fabrics), providing a high level of fault isolation and centralized fabric management • Connects multiple SAN islands (independent fabrics), enabling selective resource sharing • Eliminates the need to move and re-cable equipment in different fabrics • Allows connection of fabrics with the same domain ID and zoning definitions • Reduces the impact of scaling limits for individual fabrics • Increases levels of storage cons
Benefits A VSAN: • Isolates fabric services and minimizes fault propagation • Allows multiple secure VSANs over the same physical infrastructure • Restricts device access for improved control and security • Provides selective device access and sharing using the IVR feature H-series switches with TR The TR feature provides inter-fabric routing on a per-port basis, allowing controlled access between devices on an H-series switch (local) fabric and devices on a remote fabric consisting of B-series or C
Data availability SAN data availability depends on the reliability of the SAN fabric, servers, and storage systems during routine operations.
switch automatically reroutes data through an alternate fabric path and there is no interruption in server I/O activity. Figure 11 Level 2: single resilient fabric 25099a Level 3: single resilient fabric with multiple device paths Level 3 is the same as level 2 but also provides multiple server and storage system paths to the fabric to increase availability (Figure 12).
performance and a higher number of available ports, since all fabrics can be accessed simultaneously during normal operations. Figure 13 Level 4: multiple fabrics and device paths (NSPOF) A B 25101a Using two fabrics may increase implementation costs, but it also increases the total number of available ports. For example, in a single meshed fabric with four switches, you have a maximum of 52 user ports for servers and storage.
Table 8 Calculating for data availability levels Fabric design Hardware cost Number of available ports Level 1: single connectivity fabric x1 # ports = n – number of ISL ports2 Level 2: single resilient fabric x + additional ISLs # ports = n – number of ISL ports Level 3: single resilient fabric with multiple device paths x + additional ISLs + additional HBAs # ports = n – number of ISL ports – additional HBA ports3 Level 4: multiple fabrics and device paths (NSPOF) x + additional ISLs + additi
Migrating a meshed fabric SAN This section describes migration paths for a meshed fabric SAN. Meshed to ring You can migrate a meshed fabric SAN to a ring fabric SAN by removing the cross-connected ISLs and leaving the outer-connected ISLs as a ring. Use the available ports for device connections or for redundant ring ISL connections. Meshed to core-edge Use the method described in “Cascaded to core-edge” (page 41). Migrating a ring fabric SAN This section describes migration paths for a ring fabric SAN.
3 Fibre Channel routing This chapter describes Fibre Channel routing in an HP SAN environment.
• • Fabric, Virtual Fabric, or VSAN independence ◦ Isolation of fault domains ◦ Separate fabric services Centralized SAN fabric management ◦ Common fabric management ◦ Tape backup consolidation Fabric, Virtual Fabric, and VSAN independence Fibre Channel routing identifies data frames in a fabric, Virtual Fabric, or VSAN for transfer to other fabrics, Virtual Fabrics with IFR, or VSANs with IVR.
SAN scaling and routing This section describes two methods for increasing the size of SANs: • Increase the Fibre Channel switch capability within a fabric. • Connect independent fabrics using a Fibre Channel router, Virtual Fabrics with IFR, or VSANs with IVR. Switch scaling The switches that make up fabrics define the fabric limits. This section describes the relationship between switches.
Simple fabric services SNS provides a mapping between device names and their addresses in a fabric. To ensure that the mapping is up-to-date, every switch in the fabric implements SNS. Coordinating fabric services Each fabric maintains a unique set of fabric services. When two fabrics are connected, their two sets of services merge to form a single set. As fabrics grow, coordinating the fabric services across switches, hosts, and storage devices becomes more challenging.
◦ Multi-protocol Router Blade (MP Router Blade for the 4/256 SAN Director) ◦ Multi-protocol Router (MP Router) • A B-series switch with IFR connects multiple Virtual Fabrics, as shown in Figure 15 (page 47). • A C-series switch with IVR connects multiple VSANs, as shown in Figure 16 (page 47). • An H-series switch with TR connects to other B-series or C-series fabrics, as shown in Figure 17 (page 47).
B-series fabric groups In B-series routing configurations, devices in different fabrics can be grouped to form LSANs. An LSAN is similar to a Fibre Channel zone, but can extend through a router to include devices in other fabrics. This configuration, which includes the physical fabrics (subnetworks), LSANs, and router, is called a Meta SAN. A Meta SAN consolidates multiple fabrics into a single entity. Figure 14 (page 47) shows Fabric 1, Fabric 2, and Fabric 3, each containing one or more switches.
through one TR_Port. Multiple devices can share TR_Ports, and you can configure multiple TR_Ports to the same remote fabric. HP currently supports connection to B-series and C-series remote fabrics. Figure 17 (page 47) shows how one or more remote fabrics can connect to an H-series switch. Remote Fabric 1, Remote Fabric 2, and the H-series switch fabric each contain one or more switches. Devices connected through routing must comply with the configuration rules for the TR function.
Figure 19 B-series Virtual Fabric IFR LF1 LF3 LF3 LF1 LF2 LF2 LF3 LF1 LF2 25266b As shown in Figure 20 (page 50), VSANs can include devices that connect to a single switch or multiple switches in the SAN. Devices in different VSANs communicate using IVR. Multiple switches can be connected in any supported fabric configuration.
are the two devices and the TR_Port that connects them. CLI commands for adding this zone to the remote fabric zone set are generated automatically.
Figure 23 Dual-redundant Virtual Fabric FC Switch (IFR) VF A1 VF A2 IFR SAN A FC Switch (IFR) VF B1 VF B2 IFR SAN B 25267b Figure 24 Dual-redundant VSAN FC Switch (IVR) VSAN A1 VSAN A2 IVR SAN A FC Switch (IVR) VSAN B1 VSAN B2 IVR SAN B 25107b Supported routing configurations Routing requires additional configuration rules for fabrics.
Figure 25 1606 Extension SAN Switch or MP Router connecting core switches 1606 Extension SAN Switch, 400 MPR, or MPR (FC Routing) 25108c An alternative core switch routing configuration is to use the 8 Gb/s switch integrated Fibre Channel routing feature or MP Router Blades in the SAN Directors.
Figure 27 VSANs connecting core switches VSAN 3 VSAN 1 VSAN 2 VSAN 3 VSAN 2 VSAN 1 VSAN 3 VSAN 1 VSAN 2 25109a Routing through an IP network When connecting fabrics through IP, 1606 Extension SAN Switches or DC Dir Switch MP Extension Blades, MP Routers or Blades serve as FCIP gateways with Fibre Channel routing. Routers that communicate with the FCIP protocol must be installed in pairs (Figure 28 and Figure 29).
Figure 30 (page 55) shows IVR connecting VSANs through IP. Figure 30 IVR connecting VSANs through IP VSAN 1 VSAN 2 . . VSAN n VSAN 1 VSAN 2 . . VSAN n FC Switch (IVR) IP FCIP with IVR FC Switch (IVR) 25111a High-availability router configurations In high-availability configurations, use pairs of 8 Gb/s switches with integrated Fibre Channel routing, 1606 Extension SAN Switches, routers, or IFL pairs to provide redundant paths between fabrics.
Figure 31 High-availability 1606 Extension SAN Switch configurations 1606 Extension SAN Switch Fabric A1 Fabric A2 1606 Extension SAN Switch Fabric B1 Fabric B2 NSPOF configuration 1606 Extension SAN Switch Fabric A1 Fabric A2 1606 Extension SAN Switch Fabric B1 Fabric B2 1606 Extension SAN Switch Fabric A1 Fabric A2 26597b 56 Fibre Channel routing
Figure 32 High-availability MP Router configurations 400 MPR or MPR (FC Routing) Fabric A1 Fabric A2 400 MPR or MPR (FC Routing) Fabric B1 Fabric B2 NSPOF configuration 400 MPR or MPR (FC Routing) Fabric A1 Fabric A2 400 MPR or MPR (FC Routing) Fabric B1 Fabric B2 400 MPR or MPR (FC Routing) Fabric A1 Fabric A2 25112c 400 MP Router and MP Router Blade use cases For configuration examples, see the 400 MP Router and MP Router Blade use-case white papers: http://h18006.www1.hp.
Routing use cases This section describes use cases for routing. SAN island consolidation and scaling B-series routing consolidates SAN islands (multiple independent fabrics) into a Meta SAN. This modular SAN design offers: • Simplified scalability that allows you to scale a SAN without having to merge fabrics. • Selective sharing of devices in different fabrics so that only devices required for specific functions are seen across fabrics.
) and Figure 37 (page 60) show a configuration in which the 1606 Extension SAN Switches or 400 MP Routers are used as both an FCIP gateway and Fibre Channel switch.
Figure 37 NSPOF configuration with 400 MP Router providing Fibre Channel routing and FCIP with direct connect devices 400 MPR 400 MPR VEX Fabric A1 IP A VE Fabric A2 FCIP with FC routing 400 MPR 400 MPR VEX Fabric B1 IP B VE Fabric B2 FCIP with FC routing 25282c Figure 38 NSPOF configuration with MP Router providing Fibre Channel routing and FCIP MPR Fabric A1 MPR Fabric A2 IP A FCIP with FC routing MPR Fabric B1 MPR IP B FCIP with FC routing Fabric B2 25114b Tape backup consolidation
Figure 39 1606 Extension SAN Switch or MP Router consolidating tape backup in a Meta SAN 1606 Extension SAN Switch, 400 MPR, or MPR (FC Routing) Fabric 2 Fabric 3 Fabric 1 Fabric 4 25115c Independent fabrics connected through a 1606 Extension SAN Switch or MP Router cannot have a direct ISL connection (Figure 40). A direct ISL connection between fabrics bypasses the MP Router, resulting in a full fabric merge.
4 Fibre Channel over Ethernet Fibre Channel over Ethernet is a protocol in which Fibre Channel frames can be sent over Ethernet networks. This allows Fibre Channel to use 10-GbE networks while preserving the Fibre Channel protocol. Simultaneously, the 10-GbE network supports Ethernet data thus creating a single converged network for Ethernet and Fibre Channel.
The HP FCoE module and switch product set consists of the following: • HP c-Class BladeSystem Virtual Connect FCoE capable modules: ◦ HP Virtual Connect FlexFabric 10Gb/24-Port Module for c-Class BladeSystem ◦ HP Virtual Connect Flex-10/10D Ethernet Module for c-Class BladeSystem • HP 6125XLG Ethernet Blade Switch—Provides a converged fabric solution that supports Ethernet, native FCoE, and iSCSI protocols that enables connectivity for FCoE or iSCSI storage solutions.
Fibre Channel ports on the HP B-series FCoE CN switches and HP C-series CN switches can be used for ISL connections to an existing Fibre Channel fabric, or to an HP Fibre Channel storage system or HBA. Table 9 (page 64) lists the number of ports for each HP FCoE CN switch.
• “HP StorageWorks DC SAN Director Switch 10/24 FCoE Blade” (page 67) • “HP C-series Nexus 5010/5020 Converged Network Switches” (page 67) • “Cisco Nexus 5548UP/5596UP Converged Network Switches” (page 68) • “HP CN1000E and CN1100E” (page 70) • “HP StoreFabric CN1100R” (page 71) • “HP CN1000Q” (page 71) • “FCoE storage systems” (page 71) Converged network switches and blades HP FlexFabric 5900CP Switch The HP FlexFabric 5900CP Switch is a ToR converged L2/L3 switch with 48 converged ports and
• Powerful QoS features: ◦ Creates traffic classes based on access control lists (ACLs), IEEE 802.1p precedence, IP, DSCP or Type of Service (ToS) precedence. ◦ Supports filter, redirect, mirror, or remark. ◦ Supports the following congestion actions: strict priority (SP) queuing, weighted round robin (WRR), weighted fair queuing (WFQ), weighted random early discard (WRED), weighted deficit round robin (WDRR), and SP+WDRR.
Considerations • The port types are fixed. You cannot use 10-GbE ports for FC connections, and you cannot use FC ports for 10-GbE connections. • L3 routing features are not currently supported. • 10-GbE ports support virtual F_Ports only (virtual E_Ports are not supported). HP StorageWorks DC SAN Director Switch 10/24 FCoE Blade The HP DC SAN Director Switch 10/24 FCoE Blade is a rebranded version of the Brocade FCOE10-24 blade.
Features • L2 access: ◦ IEEE DCB and FCoE support IEEE DCB is a Cisco unified fabric product with additional proprietary features.
• • Cisco Nexus 5596UP (2 RU) ◦ Up to 96 ports—48 unified ports and 3 16-port expansion modules ◦ 48 unified ports can be configured as 1- and 10-GbE and FCoE, or 8/4/2/1 Gb/s FC ports Optional expansion modules include: ◦ 16-port Unified Port Expansion Module—Up to 16 of 1/10 GbE FCoE ports or 16 of 8/4/2/1 Gb/s FC ports ◦ 8-port FC (8/4/2/1-Gb) + 8-port Ethernet and FCoE (1/10 GB) module Cisco Fabric Extender for HP BladeSystem The Cisco Fabric Extender for HP BladeSystem (Model B22HP) provide
Figure 41 FC and FCoE storage with Cisco Fabic Extender for HP BladeSystem configuration Blade servers with CNAs and Cisco Fabric Extender* for HP BladeSystem (*with C-series FCoE switches only) C-series FCoE switches FC switches 3PAR P6300 EVA P6500 EVA FCoE/iSCSI/FC EVA/SAS storage 10-GbE FCoE/iSCSI connection 10-GbE connection Fibre Channel 26663c Converged network adapters Servers with CNAs require fewer adapters per server and, therefore, 75% fewer cable connections for network and FC attachments.
Considerations • x8 PCI Express Gen2 card • Requires 14.5 W of power • 1 GbE is not supported HP StoreFabric CN1100R Features The HP StoreFabric CN1100R Dual Port CNA has the following features: • Ships with half-height and full-height brackets • Dual ports for redundancy • Full 10-Gb/s bandwidth on both ports • Each port can operate as a NIC and/or FCoE port • Two SFP+ connectors • Supports optical or copper cables Considerations • Requires an x8 PCI Express Gen2.
3PAR StoreServ 10400/10800/7200/7400/7450 with 10GbE FCoE host ports FCoE host ports For more information, see the 3PAR StoreServ FCoE product documentation. Operating system and multipath software support For the latest information on operating system and multipath software support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access.
Table 11 P9500 10-GbE FCoE operating system and multipath software support Operating system Clusters P9500 storage system Multipath software Microsoft Windows Server 2008 MPIO with HP DSM (supports both CN1000E and CN1100E) MPIO with Microsoft DSM (supports both CN1000E and CN1100E) Microsoft Windows Server 2003 MPIO with HP DSM (supports CN1000E only) MPIO with Microsoft DSM (supports CN1000E only) Red Hat Linux, SUSE Linux Device Mapper None VMware VMware embedded None Microsoft Windows Ser
Operating system and multipath software support For the latest information on operating system and multipath software support, see the HP SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 12 (page 74) provides the operating system and multipath software support for P63xx/P65xx EVA 10-GbE iSCSI/FCoE.
Figure 44 (page 75) depicts blade server FC/FCoE configurations with B-series, C-series, or HP FlexFabric FCoE switches and either Pass-Thru modules, 6120XG or 6125XLG DCB switches, or Virtual Connect modules. • If Pass-Thru modules are used, this configuration is supported with B-series or C-series FCoE and corresponding FC switches. • If 6120XG switches are used, this configuration is supported with C-series FCoE switches and FC switches only.
Figure 45 Blade server mixed FC/FCoE storage with HP 5820 switches Blade servers with CNAs and Pass-Thru modules or HP 5820* switches (*with B-series or C-series FCoE switches) FCoE switches FC switches 3PAR P63xx EVA P65xx EVA FCoE/iSCSI/FC EVA/SAS storage 10-GbE FCoE/iSCSI connection 10-GbE connection Fibre Channel 76 Fibre Channel over Ethernet 26667c
FCoE configuration rules This section describes configuration rules for the HP FCoE solution. The rules are defined for the CNAs and each of the FCoE CN switch series. Figure 46 (page 77) shows a converged SAN fabric with servers using CNAs only. NOTE: Fibre Channel HBAs can also be connected to B-series, C-series, or HP FlexFabric 5900CP converged ports as F_Ports.
Figure 47 (page 78) shows a converged SAN fabric with servers using CNAs connected to a B-series CN switch and a DC SAN Director Switch 10/24 FCoE Blade.
Figure 48 (page 79) shows a converged fabric that has servers with CNAs and servers with FC HBAs and NICs. NOTE: Fibre Channel HBAs can also be connected to B-series, C-series, , or HP FlexFabric 5900CP Converged Network switch F_Ports.
Figure 49 (page 80) shows an FCoE end-to-end direct-connect storage configuration using an MPX200 Multifunction Router and P6000/EVA Fibre Channel storage systems. This provides 10-GbE FCoE and iSCSI connectivity for up to two P6000/EVA Fibre Channel storage systems without requiring any Fibre Channel switches.
Figure 50 FCoE end-to-end MPX200 fabric-connect P6000/EVA FC storage configuration Servers with NICs Servers with CNAs FCoE/IP /iSCSI iSCSI/IP Converged network X-series CN switches IP FCoE/iSCSI MPX200 FCoE/iSCSI target HP StorageWorks MPX200 MGMT 10GbE4 IOIOI FC1 10GbE3 HP StorageWorks MPX200 10 - 1 GbE Blade MPX200 Multifunction Router FC2 GE1 GE2 MGMT 10GbE4 IOIOI FC1 10GbE3 Ethernet network 10 - 1 GbE Blade MPX200 Multifunction Router FC2 GE1 GE2 Fibre Channel Fabric B Fabri
CNA configuration rules Table 13 HP CNA requirements Item Description Number of CNAs per server (maximum) 2 • SFP+ optical: CN1100E, CN1100R, and CN1000Q 100m; CN1000E 40m Cable types and distances • Copper: CN1100R 5m; CN1100E, CN1000E, and CN1000Q 7m and 10m (with C-series FCoE CN switches only) For current firmware and driver support, see the HP SPOCK website at http://www.hp.com/ storage/spock. You must sign up for an HP Passport to enable access.
Table 14 HP 5820X CN switch fabric rules (continued) Rule number 6 Description Up to two 5820 FCoE modules are supported in a single 5820X switch. However, when using two A5280 FCoE modules, consider the following: • When two 5820 FCoE modules are connected to the same SAN, the FCoE modules attempt to load balance the server load across the two FCoE modules as servers are added by distributing the CNA logins between the two modules.
• Integrated Fibre Channel routing • FICON • Admin Domains • TI Zones • M-EOS Interop • Nondisruptive firmware upgrade Table 16 (page 84) provides a comparison of the high-availability features for the B-series FCoE CN switch.
ports are dual speed, supporting both 10-GbE and 1-GbE. The switch has one expansion slot that can accommodate up to 8 Fibre Channel switch ports. Expansion modules for the C-series Nexus 5000 Series switches The C-series Nexus 5000 Series switches can accommodate expansion modules that connect Fibre Channel SANs to 8, 4, 2, or 1 Gb/s Fibre Channel switch ports. Use these modules to increase the number of 10-GbE, Cisco IEEE DCB, and FCoE ports.
Table 17 Nexus switches for NX-OS Maximum number of Fibre Channel ports Maximum number of Ethernet ports C-series Nexus 5020 16 52 C-series Nexus 5010 8 26 Cisco Nexus 5548UP 48 with expansion module 48 with expansion module Cisco Nexus 5596UP 96 with expansion modules 96 with expansion modules Switch Table 18 (page 86) describes Nexus expansion module support.
Table 19 C-series Nexus 5000 series and Cisco Nexus 5500 series switch high-availability feature comparison Redundant/ hot-swappable power Redundant/ hot-swappable cooling Redundant control processor Nondisruptive code activation Expansion module support Nexus 5020 Yes/Yes Yes/Yes No No Yes Nexus 5010 Yes/Yes Yes/Yes No No Yes Nexus 5548UP Yes/Yes Yes/Yes No No Yes Nexus 5596UP Yes/Yes Yes/Yes No No Yes Switch Protocol support FCIEEE DCB 10-GbE FCoE FCFCoECEE compliant DCBX Us
Windows 2003 (x86, x64) and 2008 (x86, x64) • BFS is supported on all supported HP servers. • The information in HP Boot from SAN Configuration Guide is accurate for Windows BFS on a CNA based server for Windows 2003 with the following exceptions: ◦ You must install an HP CNA driver kit, available for download at the HP website:http:// www.hp.com/support/downloads ◦ For Windows 2003, press F6 to prompt for the driver disk.
SUSE Linux Enterprise Server • BFS is supported on all supported HP servers. • The information in HP Boot from SAN Configuration Guide is accurate for BFS on a CNA based server with the following exception: ◦ Use the GUI to load the driver. See Figure 52. Figure 52 SLES installation The HP Boot from SAN Configuration Guide is available at http://h18006.www1.hp.com/storage/ networking/bootsan.html. Under Features, click Boot from SAN documentation.
Part II Fabric infrastructure rules Fabric infrastructure rules are presented in these chapters: • “B-series switches and fabric rules” (page 91) • “C-series switches and fabric rules” (page 123) • “H-series switches and fabric rules” (page 140) • “SAN fabric connectivity and switch interoperability rules” (page 152)
5 B-series switches and fabric rules This chapter describes the B-series Fibre Channel and FCoE switches and blades; Extension SAN Switches and Blades; MP Routers, and fabric rules for building B-series fabrics.
and 48-port enhanced 8 Gb/s Fibre Channel blades, encryption blade, and DC Dir Switch MP Extension Blade. • DC SAN Backbone Director and DC04 SAN Director support the 16, 32, 48, and 64-port 8 Gb/s Fibre Channel blades, 10 Gb/s 10/6 FC ISL Blade, MP Router Blade, encryption blade, and the DC Dir Switch MP Extension Blade.
Table 22 (page 95). When updating switch firmware, you can use two successive switch firmware versions temporarily in a single-fabric and multi-fabric SAN. • Follow the fabric rules. See “Fibre Channel switch fabric rules” (page 102). For the latest information on supported B-series Fibre Channel switches and firmware versions, see the HP Storage Networking website: http://h18006.www1.hp.com/storage/saninfrastructure.
Table 20 B-series Fibre Channel switches HP switch name Fabric Management Number of Ports HP SN8000B 8-Slot SAN Backbone Director Switch 32 to 512 HP SN8000B 4-Slot SAN Director Switch 32 to 256 HP SN6000B 16Gb Fibre Channel Switch 24 to 48 HP SN3000B 16Gb Fibre Channel Switch HP Network Advisor HP StoreFabric SN6500B 16Gb Fibre Channel Switch 12 to 24 48 to 96 1 to 16 internal Brocade 16Gb SAN Switch for HP BladeSystem c-Class 1 to 12 external HP StorageWorks Encryption SAN Switch 32 HP St
Table 22 B-series legacy Fibre Channel switches and routers Legacy HP switch name Fabric Management Number of ports 8 at 1, 2, or 4 Gb/s Fibre Channel HP StorageWorks iSCSI Director Blade 8 at 1-GbE iSCSI HP Multi-protocol Router Blade for B-Series 16 at 1, 2, or 4 Gb/s Fibre Channel 2 at 1-GbE FCIP HP StorageWorks 400 Multi-Protocol Router HP StorageWorks 4/256 SAN Director base/power pack 16 to 384 HP StorageWorks 4/32B SAN Switch full/power pack HP StorageWorks 4/32B SAN Switch base 32 HP Netwo
distances up to 10 km is provided in all B-series switches. For distances greater than 10 km, an Extended Fabrics license is required. For maximum supported distances based on the link speed, see “SAN fabric connectivity and switch interoperability rules” (page 152). • Data Center Fabric Manager (DCFM)—Centralizes fabric management through a host-based application.
◦ 4 Gb/s: 4/8, 4/16, 4/32B, 4/64, and 4/256, Brocade 4Gb SAN Switch for HP c-Class BladeSystem ◦ 2 Gb/s: 2/128 • Secure Fabric OS—Provides flexible security and policy-based administration to protect data from unauthorized access and corruption. All Secure Fabric OS features are included in the base Fabric OS beginning with 5.3.0 firmware. Secure Fabric OS can coexist in a fabric running Fabric OS 5.3.x firmware, but this is not supported with later versions of Fabric OS. Features of Fabric OS 6.
• 10 Gb/s Fibre Channel capability on 16 Gb/s Fibre Channel platforms—Provides the ability to configure ports on the SN8000B 16 Gb/s 32-port or 48-port Fibre Channel Blades for the HP SN8000B 8-Slot SAN Backbone Director Switch, the HP SN8000B 4-Slot SAN Director Switch, and the HP SN6000B 16Gb FC Switch to operate at 10 Gb/s.
ports on the SN8000B 8-Slot Director, and requires an additional license to enable the remaining ICL ports. • Enterprise ICL—Enables the connection of more than four SN8000B SAN Director platforms within a single fabric using optical ICLs to deliver massive scalability. This license augments but does not replace existing licensed ICL support (ICL licenses are still required to enable ICL ports) for larger ICL-based topologies of 5 to 10 SN8000B SAN Director chassis per fabric.
Table 23 B-series Fibre Channel switch high-availability feature comparison (continued) Model Redundant/hot- Redundant/hotswappable swappable power cooling Redundant core switching blade Redundant control processor Non-disruptive Non-disruptive code port activation expansion Redundant active components DC04 SAN Director Yes/Yes Yes/Yes Yes Yes Yes Yes Yes SAN Director 2/128, 4/256 Yes/Yes Yes/Yes No Yes Yes Yes Yes 400 MP Router Yes/Yes Yes/Yes No No Yes No No MP Router Yes/Y
Table 24 Using B-series Fibre Channel switches as core switches (continued) Model 1-96 user ports 97-224 user ports 225-500 user ports 501-728 user ports 729-1280 user ports EVA4400 Embedded Switch Module, 8 Gb Brocade B-series Fibre Channel switches, 1606 Extension SAN Switches, and MP Routers 101
Table 25 (page 102) describes the use of B-series Fibre Channel switches as edge switches.
• “1606 Extension SAN Switch and DC Dir Switch MP Extension Blade fabric rules” (page 108) • “Fibre Channel routing, 400 MP Router, and MP Router Blade fabric rules” (page 110) • “MP Router fabric rules” (page 114) • “Core switch addressing mode” (page 120) • “Zoning limits and enforcement” (page 120) • “Zoning guidelines for B-series Fibre Channel switches” (page 121) Operating systems and storage products The fabric rules for B-series switches and MP Routers apply to SANs that include the oper
Table 27 B-series Fibre Channel switch fabric rules Rule number Description 1 A maximum of 56 switches and 2,560 virtual or physical connections in a single fabric with HP StoreFabric SN6500B 16Gb FC Switch using firmware 7.1.0a (or later), HP SN8000B 8-Slot SAN Backbone Director Switch, HP SN8000B 4-Slot SAN Director Switch, or HP SN6000B 16Gb FC Switch, or HP SN3000B 16Gb FC Switch using firmware 7.
Table 27 B-series Fibre Channel switch fabric rules (continued) Rule number 6 Description B-series switches and routers supported routing modes with Continuous Access products: • HP P9000 (XP) Continuous Access—Supported with port-based routing (aptpolicy = 1) or exchange-based routing (aptpolicy = 3). See “HP P9000 (XP) Continuous Access FCIP gateway support” (page 314). • HP P6000 Continuous Access—Supported with port-based routing (all XCS versions) or exchange-based routing (XCS 09534000 or later).
Table 27 B-series Fibre Channel switch fabric rules (continued) Rule number Description For HP P9000 (XP) Continuous Access, see “HP P9000 (XP) Continuous Access FCIP gateway support” (page 314). 11 Within a fabric, assign a unique domain number (domain ID) and a unique WWN to each switch. All switch configuration parameters for the same switch models must be the same. Do not configure any switches with a domain ID of 8, which is reserved for HP-UX.
ISL maximums You can use all ports on all B-series Fibre Channel switches for ISLs, with a maximum of one half of the total ISL port count configured to the same destination switch. NOTE: Some switches require licensing for additional ISL ports. DC SAN Director FC8-64 cabling The DC SAN Director FC8-64 port blade requires mSFP fiber optic cable connectors. Table 29 (page 107) describes the two possible connection scenarios and solutions for cabling.
1 This value is half the value of the actual limit supported in a high-availability cluster. 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade fabric rules This section describes the fabric rules for the 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade, and other factors you should consider when building B-series fabrics with Fibre Channel routing enabled. These fabric rules apply to SANs that include the same operating systems and storage products as the B-series switches.
Table 31 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade fabric rules (continued) Rule number 11 Description FCIP tunnels (virtual E_Ports) pass traffic between the SAN extension devices. • The 1606 Extension SAN Switch supports up to 8 FCIP tunnels. • The DC Dir Switch MP Extension Blade supports up to 20 FCIP tunnels. 12 IPsec is supported on the 1606 Extension SAN Switch beginning with firmware 6.3.1a. See Rule 18.
• Front phantom domains—All EX_Ports on a Fibre Channel router that are connected to the same edge fabric are presented as a single front phantom domain. • Translate phantom domains—Assigned to each remote fabric connected to a 1606 Extension SAN Switch, DC Dir Switch MP Extension Blade, 400 MP Router, or MP Router Blade. Each fabric has one unique translate domain, regardless of how many EX_Ports are connected to the fabric.
about configuring MP Routers for FCIP, see “B-series 400 MP Router and MP Router Blade” (page 290). Table 32 (page 111) describes the rules for creating fabrics with Fibre Channel routing using 8 Gb/s switches, 400 MP Routers, and MP Router Blades. Table 32 Integrated Fibre Channel routing, 400 MP Router, and MP Router Blade fabric rules Rule number Description 1 The MP Router Blade supports only the DC SAN Backbone Director, DC04 SAN Director, and SAN Director 4/256.
Table 32 Integrated Fibre Channel routing, 400 MP Router, and MP Router Blade fabric rules (continued) Rule number Description • FCFW does not work in FICON environments. • FCFW flows may be routed to another 400 MPR or MP Router blade on the FC network. This 400 MPR or MP Router blade may have active FCIP tunnels over an IP network. FCFW flows may be passed through the FCIP tunnel, but only if the FCIP FastWrite option is disabled on the tunnel.
Table 33 Integrated Fibre Channel routing, 1606 Extension SAN Switch, DC Dir Switch MP Extension Blade, 400 MP Router, and MP Router Blade scalability rules for firmware 6.2x/6.3x/6.4x/7.x (continued) Meta SAN scalability Edge fabrics containing up to 1,500 WWNs: • Edge fabrics 48 (DC and SN8000B Directors) • 24 (all others) Edge fabrics containing up to 2,000 WWNs (FOS v6.
1 For more information, see Figure 56 (page 119). 2 Tested to 1,200, but can support up to 1,500 or 2,000 (with reduced number of maximum edge fabrics) on v6.3 and higher. Contact your HP representative for further details. Tested to 3,000, but will support up to 5,000 on FOS v6.3 and higher (all backbone FCRs with FOS v6.0.0 and higher). Contact your HP representative for further details.
Table 34 MP Router fabric rules (continued) Rule number Description 4 The MP Router is not supported for use as a Fibre Channel switch. Direct device connectivity to MP Router ports (F_Port) is only supported with iSCSI. See “iSCSI storage” (page 318). You can configure a Fibre Channel port as an E_Port, EX_Port (Fibre Channel Routing), GbE iSCSI, or GbE FCIP.
Figure 53 iSCSI storage device connectivity for the MP Router iSCSIaccessible FC Storage iSCSIaccessible FC Storage FC IP FC Edge Fabric Backbone Fabric MPR FC Switch E_Ports EX_Ports FC Switch FC Switch E_Ports E_Ports FC Switch MPR FC FC IP iSCSIaccessible FC Storage iSCSIaccessible FC Storage 25117b 116 B-series switches and fabric rules
Figure 54 Fibre Channel routing storage device connectivity for the MP Router Routable FC Storage Edge Fabric FC Switch E_Ports FC FC Switch FC Routable FC Storage EX_Ports Backbone Fabric MPR FC Switch E_Ports Routable FC Storage FC Edge Fabric E_Ports FC Switch MPR EX_Ports FC FC Switch E_Ports Routable FC Storage FC Switch 25118a The following sections describe additional considerations and rules for using the MP Router in a fabric: • “XPath OS compatibility” (page 118) • “Scalabi
XPath OS compatibility Table 20 (page 94) through Table 22 (page 95) list the B-series switches and firmware versions that are supported in a SAN with the MP Router XPath OS. Scalability rules Table 35 (page 118) lists the scalability rules for Meta SANs using the MP Router. The following terms describe MP Router scalability: • Front phantom domains—Individual EX_Port connections from the MP Router to the edge fabrics. • Translate phantom domains—Assigned to each remote fabric connected to an MP Router.
MP Router hop count The MP Router counts the same as a Fibre Channel switch is counted with respect to fabric hop count. See Figure 55 (page 119). Devices communicating across fabrics through an MP Router must adhere to both the B-series 7-hop limit within an edge fabric and the MP Router 12-hop limit.
Core switch addressing mode B-series Fibre Channel switches using firmware 4.1 (or later) and all MP Router models are shipped with the Core switch PID parameter bit set to 1. Legacy switches using firmware 4.0 or 3.1 (or earlier) were shipped with this bit set to 0, which limited the number of switches in a fabric and the number of ports on a switch. HP recommends that you set the Core switch PID parameter bit to 1 in all B-series fabrics. Use the configure command to modify the Core switch PID setting.
Table 36 Zoning enforcement for B-series Fibre Channel switches and MP Router LSANs Switches or routers Encryption SAN Switch SN8000B 8-Slot SAN Backbone Director SN8000B 4-Slot SAN Director SN6000B 16Gb FC Switch HP StoreFabric SN6500B 16Gb FC Switch Configuration Define zones using domain number and port number Define zones using WWNs only Enforcement Comments Access authorization at frame level in hardware Hard zoning Name Server directory-based authentication, login authentication Soft zoning, Na
WARNING ZONE-ZONEGROUPADDFAIL, 3, WARNING - port 7 Out of CAM entries WARNING ZONE-SOFTZONING, 3, WARNING - port 7: zoning enforcement changed to SOFT The zoning configuration has exceeded limits, forcing the specified port to change from hardware-enforced zoning to software-enforced zoning. Other zone members remain hardware enforced. These warning messages appear at zoning configuration time (for port-level zoning) or dynamically at run time (for WWN zoning).
6 C-series switches and fabric rules This chapter describes the C-series Fibre Channel and FCoE switches and the fabric rules for building C-series fabrics.
• 124 ◦ The 4-port 10 Gb/s Fibre Channel Switching Module is ideal for ultra-high-bandwidth ISL connectivity and inter-data center connection over a metropolitan optical infrastructure. ◦ IPS modules, Multiprotocol Services Modules, and Multiservice Modules provide MDS iSCSI and FCIP functionality: – IPS-4 and IPS-8 provide 4 and 8 GbE IP ports, respectively. – The 14/2 Multiprotocol Services Module provides 14 2 Gb/s Fibre Channel ports and 2 GbE IP ports.
• • • MDS 9216i switches have 2 slots: ◦ One slot is a fixed configuration with a 14/2 Multiprotocol Services Module. ◦ The second slot can accommodate a 16-port or 32-port 2 Gb/s Fibre Channel Switching Module; 12, 24, or 48-port 4 Gb/s Fibre Channel Switching Module; 4-port 10 Gb/s Fibre Channel Switching Module; IPS-4, IPS-8, 14/2 Multiprotocol Services Module, or 18/4 Multiservice Module for iSCSI and FCIP support; and the 32-port 2 Gb/s SSM.
are mid-range switches; the SN6000C and 91nn switches are entry-level switches. For the 92nn, 91nn, and 90nn, the nn value indicates the number of fixed ports. Multiprotocol and Multiservice products are designated with the i suffix, such as the MDS 9216i and MDS 9222i, or as IP storage services modules, such as the IPS-4, IPS-8, 14/2, and 18/4. For IPS products, the number indicates the total number of IP ports available. For example, the IPS-4 has 4 IP ports and the IPS-8 has 8 IP ports.
Table 37 C-series Fibre Channel switches for NX-OS 4.
Table 38 C-series Fibre Channel switches for NX-OS 5.x, 6.
Table 40 (page 129) describes SAN-OS C-series switching module support.
Table 41 (page 130) and Table 42 (page 131) describe NX-OS C-series switching module support. Table 41 C-series Fibre Channel switching module support matrix for NX-OS 4.
Table 42 C-series Fibre Channel switching module support matrix for NX-OS 5.x, 6.
Table 42 C-series Fibre Channel switching module support matrix for NX-OS 5.x, 6.
• High-availability, fault-tolerant software • PortChannel (ISL aggregation for highly resilient SAN architectures) • Integrated Multiprotocol capability (MDS 95nn and 92nn) for SAN extension (FCIP and iSCSI) • NPV—The following C-series Fibre Channel switches are NPV compliant: MDS 9124, MDS 9134, MDS 9124e, 8Gb fabric switch for HP BladeSystem c-Class, and SN6000C. NPV requires SAN-OS 3.3(5b) (or later). See “SAN fabric connectivity and switch interoperability rules” (page 152).
Table 43 C-series Fibre Channel switch high-availability feature comparison (continued) Redundant/ hot-swappable power Model Redundant/ hot-swappable cooling Redundant control processor Nondisruptive code activation Port module support Protocol support iSCSI MDS 9506/9509/9513 Director, SN8000C Supervisor 2A Fabric 2 Director Switches FC Yes/Yes Yes/Yes Yes Yes Yes HP SN8000C 13-Slot Supervisor 2A Fabric 3 Director Switch MDS 8Gb fabric switch for HP BladeSystem c-Class FCIP iSCSI N/A N/A N
Table 44 Using C-series Fibre Channel switches as core switches (continued) Model 1–48 total ports 49–224 total ports 225–512 total ports SN8500C 8-slot 16Gb FC Director Switch MDS 8Gb Fabric switch for HP BladeSystem c-Class Excellent Not recommended (8 port maximum) Table 45 (page 135) describes the use of C-series Fibre Channel switches as edge switches.
Table 46 C-series Fibre Channel switch operating system and storage system support Operating systems Storage products • P6550/P6500/P6350/P6300 EVA • EVA8400/6400 • EVA4400 • HP-UX • MSA2000fc G2 (MSA2300fc)/MSA2000fc • OpenVMS • MSA2040 • Apple Mac OS X • P9500 • Citrix Xen • P2000 G3 FC • IBM AIX • P4330 FC • Oracle Linux • XP24000/20000 • Red Hat Linux • XP12000/10000 • SUSE SLES Linux • XP7 • Microsoft Windows • 3PAR StoreServ 10000/7000 • Solaris • 3PAR F-Class, T-Class • VMware E
Table 47 C-series Fibre Channel switch fabric rules (continued) Rule number Description 5 HP SN8500C 8-Slot 16Gb FC Director Switch, supports up to 384 ports over eight modular slots (eight 48-port modules1). 6 Maximum of seven switch hops (eight switches) between any two communicating devices 7 Maximum of 80 VSANs per fabric2 8 Maximum of 4,000 IVR shared devices per routed fabric3 Note: IVR is not supported on the MDS 9124, MDS 9124e, and MDS 9134.
Table 48 ISL maximums (continued) Total number of available user ports Number of ports allowed as ISLs MDS 95xx 24-port 8 Gb/s Fibre Channel Switching Module 24 24 at 4 Gb/s MDS 9xxx 48-port 4 Gb/s Fibre Channel Switching Module 48 48 at 1 Gb/s MDS 9xxx 24-port 4 Gb/s Fibre Channel Switching Module 24 24 at 2 Gb/s MDS 9xxx 12-port 4 Gb/s Fibre Channel Switching Module 12 12 at 4 Gb/s MDS 9xxx 4-port 10 Gb/s Fibre Channel Switching Module 4 4 at 10 Gb/s MDS 9xxx 18/4 Multiservice Module 18
Table 50 Zoning enforcement for C-series Fibre Channel switches (continued) Switch Configuration Enforcement Comments MDS 9506 MDS 9509 MDS 9513 MDS 9222i MDS 9124 MDS 9124e MDS 9134 C-series VSAN high availability Figure 57 (page 139) shows a typical high-availability configuration with server and storage connections to different fabrics. It provides two paths for data access between servers and storage.
7 H-series switches and fabric rules This chapter describes the fabric rules for the HP H-series switches. It describes the following topics: • “H-series switches” (page 140) • “Fabric rules” (page 144) H-series switches The SN6000 Fibre Channel Switches: • Can be used as core or edge switches. When configured in a core-edge fabric topology, a core switch typically connects to other switches in the SAN; an edge switch typically connects to servers and storage.
Model numbering The SN6000 Fibre Channel Switch uses the numbering scheme of SN6xxx, which indicates a mid-range size switch type. The 8/20q Fibre Channel Switch uses the numbering scheme x/y: • x—The highest speed at which the switch ports can operate, measured in Gb/s • y—The total number of switch ports available For example, the 8/20q Fibre Channel Switch is an 8 Gb/s switch with up to 20 ports. Model naming The SN6000 Fibre Channel Switch is available as a standalone switch.
7. 8. Under H-series SAN Switches, click appropriate switch product. Select the category of the documentation desired such as User guide, Setup and Install, Getting Started, or General Reference. TIP: 9. Release notes are available in General Reference. To download the document, click the title of the desired document from the table.
◦ Nondisruptive port-license activation ◦ Support in high-availability redundant configurations Features of the 8 Gb Simple SAN Connection Kit include: • Includes all components required to create a four-host SAN infrastructure with connection to a single- or dual-controller storage target—HBA, switch, SFP+ optical transceivers, and cables included in one SKU • Can be installed by HP, a VAR, or the customer • Provides end-to-end management, including switch, HBA, and storage provisioning Features of
Usage The H-series switches can be used as core or edge switches in fabrics with up to 600 ports (including 8 Gb ISLs, but not including 10 Gb/20 Gb stacking port ISLs). The TR feature allows you to connect H-series switches to B-series or C-series fabrics, enabling the sharing of server and storage resources between fabrics through the industry-standard NPIV protocol. Fabric rules This section describes the SAN fabric rules that apply to all H-series switch SANs.
Servers, operating systems, and storage products The fabric rules for H-series switches apply to SANs that include the servers, operating systems, and storage products listed in Table 53 (page 145).
Table 54 H-series switches fabric rules (continued) Rule number Description 3 8/20q Fibre Channel Switch supports from 8 to 20 8 Gb/s ports, in 4-port increments; SN6000 Fibre Channel Switch supports 8 to 20 8 Gb/s ports, in 4-port increments, plus 4 stacking ports. 4 Within a fabric, if you assign a domain number (domain ID), it must be unique. Do not configure any switches with a domain ID of 8, which is reserved for HP-UX.
Table 55 (page 147) describes the supported remote fabric switches you can use to connect to an H-series switch TR_Port.
Table 55 Supported switches in an H-series switch with TR remote fabric (continued) HP switch name Firmware version HP SN8000C 6-Slot Supervisor 2A Director Switch HP SN8000C 9-Slot Supervisor 2A Director Switch HP SN8000C 13-Slot Supervisor 2A Fabric 2 Director Switch Cisco MDS 9513 Multilayer Director Switch Cisco MDS 9509 Multilayer Director Switch C-series 5.
Table 56 H-series switch TR and remote B-series or C-series fabric rules (continued) Rule number Description you merge the two local fabrics, the transparent route becomes inactive for the devices that now have a path over an ISL, and an alarm is generated. IMPORTANT: SCM version 3.00 (or later) is required for the HP SN6000 Fibre Channel Switch. SCM cannot manage or discover remote switches or devices in the remote fabric when using the Transparent Router feature.
Table 58 (page 150) describes zoning enforcement for H-series switches.
8 McDATA/M-series switches All M-series products have reached End Of Support Life (EOSL) and are no longer supported: • McDATA 4 Gb SAN Switch for HP p-Class BladeSystem • HP StorageWorks Director 2/140 • HP StorageWorks Director 2/64 • HP StorageWorks Edge Switch 2/32 • HP StorageWorks Edge Switch 2/24 • HP StorageWorks Edge Switch 2/12 • StorageWorks HA-Fabric Manager (HAFM) • HA Fabric Manager Appliance • HA Fabric Manager Appliance FRU • HP HA Fabric Manager SW UG kit The following M
9 SAN fabric connectivity and switch interoperability rules This chapter describes SAN fabric connectivity and interoperability rules. It describes the following topics: • “SAN fabric connectivity rules” (page 152) • “SAN fabric switch interoperability rules” (page 161) • “Third-party switch support” (page 162) • “SAN performance considerations” (page 162) SAN fabric connectivity rules This section describes SAN fabric connectivity port interfaces, cables, and rules.
use of duplex couplers, provided that you do not exceed the overall cable loss budget for that cable segment. HP recommends the use of HP PremierFlex OM4 and OM3+ fiber optic cables for 50 micron cable installations. HP PremierFlex OM3+ fiber optic cables provide higher bend performance and improved signal-transmission integrity, providing significant improvements in signal quality over industry-standard OM3 fiber optic cable technologies.
Fiber optic cable loss budgets Cable loss budgets are determined by the Fibre Channel Physical Interface Specification. See the standards at http://www.incits.org/. The maximum supported distances are based on modal bandwidth and type of fiber optic cable used. The different modal bandwidth and cable types that HP supports for Fibre Channel are: • 62.
Table 60 16 Gb/s Fibre Channel fiber optic cable loss budgets Maximum distance per cable segment Total channel insertion loss 50/125 micron (OM2 500 MHz-km at 850 nm) 35 m 1.63 dB 50/125 micron (OM3 2000 MHz-km at 850 nm, OM3+ 3000 MHz-km at 850 nm) 100 m 1.86 dB 50/125 micron (OM4 4700 MHz-km at 850 nm) 125 m 1.95 dB 9/125 micron (singlemode) 10 km 6.4 dB1 Cable 1 Maximum loss per mated connector pair 0.75 dB This number assumes use of low-loss fiber optic cables for 16 Gb/s speeds.
Table 63 4 Gb/s Fibre Channel fiber optic cable loss budgets (nominal bandwidth) Maximum distance per cable segment Total channel insertion loss 62.5/125 micron (OM1 200 MHz-km at 850 nm) 70 m 1.78 dB 50/125 micron (OM2 500 MHz-km at 850 nm) 150 m 2.06 dB 50/125 micron (OM3 2000 MHz-km at 850 nm, OM3+ 3000 MHz-km at 850 nm) 380 m 2.48 dB 50/125 micron (OM4 4700 MHz-km at 850 nm) 400 m 2.95 dB 10 km 7.
type. Unless otherwise specified, the distances specified apply to both switch-to-switch (ISL) connectivity and device-to-switch connectivity. Table 66 (page 157) describes the distance rules for 16 Gb/s or 8 Gb/s Fibre Channel connections when using 16 Gb/s or 8 Gb/s Fibre Channel switch models.
1 Information for 62.5 micron fiber optic cable is provided to facilitate use of installed cable. HP recommends 50 micron fiber optic cable for new installations that require multi-mode fiber. Table 68 (page 158) describes the distance rules for 4 Gb/s Fibre Channel connections when using 4 Gb/s Fibre Channel switch models.
Table 69 Fibre Channel distance rules for 2 Gb/s switch models (B-series and C-series switches) Interface/transport Supported distances OM2 fiber 50 micron multi-mode fiber optic cable and short-wave SFPs Supported storage products OM3, OM3+ fiber 300 m at 2 Gb/s 500 m at 2 Gb/s 500 m at 1 Gb/s 62.
Table 71 (page 160) describes the distance rules for ATM extension Fibre Channel connections.
Table 74 (page 161) describes the distance rules for Fibre Channel routing connections. Table 74 Fibre Channel and IP network routing distance rules Interface/transport HP B-series 400 MP Router, MP Router Blade, and MP Router Heterogeneous SAN Fibre Channel distances See Table 68 (page 158) through Table 70 (page 159). HP P6000 Continuous Access and HP P9000 (XP) Continuous Access1 EBS See Table 68 (page 158) through Table 70 (page 159) and Table 72 (page 160).
Interoperable, heterogeneous switch fabrics An interoperable, heterogeneous switch fabric can contain different series of switches. Table 75 (page 162) lists the switch combinations.
Additional factors such as distance, number of switch and device port buffers, and device response times can also affect performance. • Mixed Fibre Channel speeds For fabrics consisting of 16 Gb/s, 8 Gb/s, and 4 Gb/s; or 8 Gb/s, 4 Gb/s, and 2 Gb/s; or 4 Gb/s, 2 Gb/s, and 1 Gb/s switches and devices, the fabric segment connections negotiate the speed at which specific devices communicate.
Part III Host and storage system rules Host and storage system rules are presented in these chapters: • “Heterogeneous server rules” (page 165) • “MSA storage system rules” (page 211) • “P6000/EVA storage system rules” (page 221) • “P9000/XP storage system rules” (page 235) • “SVSP storage system rules” (page 242) • “3PAR StoreServ storage rules” (page 249) • “Enterprise Backup Solution” (page 255)
10 Heterogeneous server rules This chapter describes platform configuration rules for SANs with specific operating systems and heterogeneous server platforms: • “SAN platform rules” (page 166) • “Heterogeneous storage system support” (page 166) • “HP FC Switches for the c-Class BladeSystem server environment” (page 167) • “HP 4 Gb Virtual Connect Fibre Channel module for c-Class BladeSystem” (page 169) • “BladeSystem with Brocade Access Gateway mode” (page 170) • “BladeSystem with Cisco N_Port Vi
SAN platform rules Table 76 (page 166) describes SAN platform rules for all SAN server configurations. Table 76 General SAN platform rules Rule number 1 SAN platform configuration Any combination of heterogeneous clustered or standalone servers with any combination of storage systems is supported.
HP FC Switches for the c-Class BladeSystem server environment Table 77 (page 167) lists supported switches for the HP c-Class BladeSystem server environment.
Virtual Connect FlexFabric modules are more efficient than traditional and other converged network solutions because they do not require multiple Ethernet and Fibre Channel switches, extension modules, cables, and software licenses. Also, built-in Virtual Connect wire-once connection management enables you to add, move, or replace servers in minutes. For more information, see the product QuickSpecs at: http://h18004.www1.hp.com/products/quickspecs/13652_div/13652_div.
The HP Virtual Connect 8 Gb 20-port Fibre Channel Module: • Simplifies server connections by separating the server enclosure from SAN • Simplifies SAN fabrics by reducing cables without adding switches to the domain • Allows you to change servers in minutes For more information, see the product QuickSpecs at: http://h18004.www1.hp.com/products/quickspecs/13421_div/13421_div.
Figure 58 HP Virtual Connect Fibre Channel configuration Server Bay 16 Server Bay 15 Server Bay 14 Server Bay 13 Server Bay 12 VC-FC - Module Server Bay 11 Server Bay 10 Server Bay 9 Server Bay 8 Server Bay 7 Server Bay 6 Server Bay 5 Server Bay 4 Server Bay 3 Server Bay 2 Server Bay 1 Blade enclosure with 16 servers VC-FC - Module Blade enclosure/ Server management N_Ports (NPIV) (uplinks) SAN/ Storage management FC Fabric (B-series, C-series, and H-series) (with NPIV F_Port support) F
Figure 59 Brocade 4Gb SAN Switch for HP c-Class BladeSystem in Access Gateway mode c-Class BladeSystem Access Gateway N_Port (host) Server Bay 1 F_Port (virtual) Uplink 1 Server Bay 2 N_Port (NPIV) Server Bay 3 Uplink 2 Server Bay 4 c-Class BladeSystem Access Gateway Server Bay 5 Server Bay 7 Server Bay 8 Server Bay 9 Server Bay 10 Uplink 3 N_Port (NPIV) Server HBA ports, N_Ports Server Bay 6 N_Port (NPIV) Uplink 4 Default server to uplink mapping (2:1) Server Bay 11 Server Bay 12 Server Bay
• No SAN management from the BladeSystem enclosure once the initial connections have been configured • No direct storage attachment (requires at least one external Fibre Channel switch) • Lacks Fibre Channel embedded switch features (ISL Trunking, dynamic path selection, and extended distances) with external links from AG to core switches • Managed separately from the BladeSystem, but if used with B-series switches, uses common Fabric OS • Cannot move servers without impacting the SAN (Virtual Conn
An NP_Port is an NPIV uplink from the NPV device to the core switch. Switches in NPV mode use NPIV to log in multiple end devices that share a link to the core switch. The Cisco MDS 9124e Fabric Switch is transparent to the hosts and fabric—they no longer function as standard switches. NOTE: This section describes HP c-Class BladeSystems. NPV mode is also supported on the Cisco MDS 9124 and MDS 9134 Fabric Switches. For more information, see the Cisco MDS 9000 Configuration Guide.
disruption when a link fails between an NP_Port on the NPV devices and an F_Port on the external fabric. To avoid disruption when an NP_Port goes online, the logins are not redistributed. NPV mode considerations Consider the following: • Nondisruptive upgrades are supported. • Grouping devices into different VSANs is supported. • A load-balancing algorithm automatically assigns end devices in a VSAN to one of the NPV core switch links (in the same VSAN) at initial login.
The configuration shown in Figure 62 (page 174) includes: • Redundant SANs, with each server connecting to one fabric through one NPV device • Connectivity to C-series and B-series fabrics • Support for up to six NPV devices per HP BladeSystem c7000 enclosure, or three NPV devices per HP BladeSystem c3000 enclosure NPV with FlexAttach The Cisco MDS 9124e Fabric Switch for HP c-Class BladeSystem, MDS 9124 switch, and MDS 9134 switch support NPV with FlexAttach.
Figure 63 Cisco MDS 9124e Fabric Switch for HP c-Class BladeSystem using NPV with FlexAttach SAN management Blade server management c-Class N_Port Virtualization MDS 9124e NPV mode Blade 1 Uplink 1 Blade 2 N_Port (NPIV) Blade 3 Uplink 2 N_Port (NPIV) Blade 4 Blade 6 Blade 7 Blade 8 Blade 9 Blade 10 Blade 11 Blade 12 Blade 13 Blade 14 Blade 15 Blade 16 Server HBA ports, N_Ports Blade 5 HBA aggregator Uplink 3 N_Port (NPIV) Uplink 4 N_Port (NPIV) Uplink 5 N_Port (NPIV) Server-to-uplink mapping (2
HBA N_Port ID Virtualization HBA NPIV is a Fibre Channel standard that allows multiple N_Ports to connect to a switch F_Port. HBA NPIV is used on servers running a VOS. You can assign a unique virtual port name to each VM that shares the HBA. NPIV is supported on all 8 Gb and 4 Gb Emulex and QLogic HBAs when using the vendor-supplied VOS drivers.
Figure 64 VOS with HBA NPIV enabled Server VM1 WWPN: 48:02:00:0c:29:00:00:1a Virtual OS VM2 WWPN: 48:02:00:0c:29:00:00:24 HBA WWPN: 20:00:00:00:c9:56:31:ba 48:02:00:0c:29:00:00:1a 48:02:00:0c:29:00:00:24 48:02:00:0c:29:00:00:2a VM3 WWPN: 48:02:00:0c:29:00:00:2a Port 8 Switch Domain ID: 37 Name Server : : FCID WWPN 370800 20:00:00:00:c9:56:31:ba 370801 48:02:00:0c:29:00:00:1a 370802 48:02:00:0c:29:00:00:24 370803 48:02:00:0c:29:00:00:2a Fabric 26411a When using HBA NPIV, consider the following: • Wh
NonStop servers Storage systems • S760, S76000 • S78, S780, S7800, S78000 • S86000, S88000 NS-series servers: • NS1000, NS1200 • NS14000, NS14200 • NS16000, NS16000CG, NS16200 NonStop Integrity servers: • NS2000, NS2000T/NS2000CG • NS2100 • NS2200, NS2200T/NS2200ST • NS2300 • XP10000, XP12000 (RAID500) • XP20000, XP24000 (RAID600) • P9500 • XP7 • NS2400, NS2400T, NS2400ST • NS3000AC • NS5000T/NS5000CG NonStop Integrity BladeSystem servers: • NB50000c, NB50000c-cg • NB54000c, NB54000c-cg • NB56000c, NB56
NOTE: Consider the following VIO requirements: • For NS1000 and NS1200 servers, expanded ports are available only to customers who have the HP ESS. • The VIO enclosure software is not backward compatible and is supported only on H06.08 and later RVUs. • Prior to December 2006, the NS1000 and NS14000 servers were shipped with a limited IOAME configuration known as the IO Core, which consisted of an IOAME with six adapter slots rather than the usual ten slots.
Table 80 (page 181) describes supported NonStop server configurations with VIO enclosures.
Table 83 (page 182) describes storage system configuration rules for NonStop servers. Table 83 NonStop server configuration rules Rule number Description 1 Requires a minimum of one XP storage system for storage connectivity. 2 Requires a minimum of one IOAME on the server. For the NS1000, NS1200, NS14000, and NS14200 servers using VIO, two VIO enclosures are used instead of the IOAME. For BladeSystems using CLIMs, two CLIMs are used instead of the IOAME.
Table 83 NonStop server configuration rules (continued) Rule number Description • The 2 Gb Fibre Channel PICs (VIO) are supported with 1 Gb/2 Gb CHIPs for XP 10000/12000/20000/24000 and with 4 Gb CHIPs for XP10000/12000/20000/24000. • The 4 Gb Fibre Channel HBAs (in CLIMs) are supported with 1 Gb/2 Gb CHIPs for XP 10000/12000/20000/24000 and with 4 Gb CHIPs for XP10000/12000/20000/24000. 15 High-availability SAN • Requires dual-redundant SAN fabrics (level 4, NSPOF high-availability SAN configuration).
Figure 65 (page 184) shows a minimum direct host attach configuration with an IOAME. Figure 65 Minimum direct host attach IOAME configuration for XP storage systems FCSA FCSA X Y IOAME p mb b m XP Array P M CL1 CL2 25122a Figure 66 (page 184) shows a minimum direct host attach configuration with VIO enclosures.
Figure 67 (page 185) shows a minimum direct host attach configuration with CLIMs. Figure 67 Minimum direct host attach CLIM configuration for XP storage systems CLIM X CLIM Y XP Array m mb b p P M CL1 CL2 26489a Figure 68 (page 185) shows a minimum SAN configuration with an IOAME.
Figure 69 (page 186) shows a minimum SAN configuration with VIO enclosures. Figure 69 Minimum SAN VIO configuration for XP storage systems (NS1000, NS14000) VIO Enclosure Y VIO Enclosure X mb p m b XP Array m mb b p P M CL1 CL2 25280a Figure 70 (page 186) shows a minimum SAN configuration with CLIMs.
Figure 71 (page 187) shows a configuration with physical IOAME redundancy. Figure 71 SAN IOAME configuration with logical and physical redundancy for XP storage systems Y X b2 Y IOAME IOAME p FCSA FCSA FCSA FCSA X mb mb2 m2 m b p2 XP Array m2 mb p p2 mb2 m M P b2 b M2 P2 CL1 CL2 25124a Figure 72 (page 187) shows a SAN configuration with VIO Fibre Channel PIC redundancy.
Figure 73 (page 188) shows a SAN configuration with CLIM physical redundancy. Figure 73 SAN CLIM configuration with logical and physical redundancy for XP storage systems CLIM Y CLIM X mb p m2 CLIM X m b mb2 b2 p2 XP Array m2 p2 m b mb p CLIM Y M P b2 mb2 M2 P2 CL1 CL2 26491a Figure 74 (page 188) shows a configuration with physical IOAME redundancy.
Figure 75 (page 189) shows a SAN configuration (two cascaded switches) with VIO Fibre Channel PIC redundancy.
Figure 76 (page 190) shows a SAN (two cascaded switches) configuration with CLIM physical redundancy.
HP-UX SAN rules This section describes the SAN rules for HP-UX. For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 84 (page 191) describes the SAN configuration rules for HP-UX. Table 85 (page 192) describes support for HP-UX storage, HBA, and multipathing coexistence. Table 84 HP-UX SAN configuration rules Storage systems1 HP-UX SAN rules • Supports HP Serviceguard Clusters.
1 Unlisted but supported storage systems have no additional SAN configuration restrictions. For the latest support information, contact an HP storage representative. Table 85 HP-UX storage system, HBA, and multipath software coexistence support1 P2000 G3 XP7 P9500 MSA2000fc G2 P63xx/P65xx EVA4 10000/12000/ (MSA2300fc) EVA4x00/6x00/8x003 20000/24000 2 Notes SVSP 3.
HP OpenVMS SAN rules This section describes the SAN rules for HP OpenVMS. For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 86 (page 193) describes the SAN configuration rules for HP OpenVMS. Table 87 (page 194) describes support for HP OpenVMS storage, HBA, and multipathing coexistence.
1 Unlisted but supported storage systems have no additional SAN configuration restrictions. For the latest support information, contact an HP storage representative.
Table 88 Tru64 UNIX SAN configuration rules Storage systems1 Tru64 UNIX SAN rules • Zoning is required when Tru64 UNIX is used in a heterogeneous SAN with other operating systems. • Supports TruCluster Server. All supported • Supports boot from SAN. For more information, see “P6000/EVA SAN boot support” (page 229) and “P9000/XP SAN boot support” (page 238). • Supports multipathing high-availability configuration in multiple fabrics or in a single fabric with zoned paths.
Table 89 HP Tru64 UNIX storage system, HBA, and multipath software coexistence support1 EVA4100/6100/81002 XP Native multipathing driver XP24000/20000,XP12000/10000 Native multipathing driver 1 Legend: S = same server and HBA 2 EVA4100/6100/8100 requires XCS firmware 6.cx (or later). S S For more information about storage system coexistence, see “Heterogeneous SAN storage system coexistence” (page 208). Apple Mac OS X SAN rules This section describes the SAN rules for Apple Mac OS X.
Table 90 Apple Mac OS X SAN configuration rules (continued) Storage systems Apple Mac OS X SAN rules • XCS 6.100 (or later) (EVA4100/6100/8100) • XCS 09000000 (or later) (EVA4400) • Command View 6.0.2 (or later) (EVA4100/6100/8100) • Command View 8.0 (or later) (EVA4400) P6550 EVA • Command View host entry operating system: Custom, custom type "00000002024000A8" • HP P6000 Command View 9.4 (or later) (P6300/P6500) Notes: For XCS 6.
IBM AIX SAN rules This section describes the SAN rules for IBM AIX. For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 91 (page 198) describes the SAN configuration rules for IBM AIX. Table 92 (page 199) describes support for IBM AIX storage, HBA, and multipathing coexistence. Table 91 IBM AIX SAN configuration rules Storage systems1 IBM AIX SAN rules • Supports HACMP/ES Clusters.
Table 92 IBM AIX storage system, HBA, and multipath software coexistence support1 P63xx/P65xx EVAEVA 4x00/6x00/8x002 EVA4x00/6x00/ 8x002 P9500, XP7, XP24000/20000, XP12000/10000 SVSP 3.0 3PAR3 3PAR3 SVSP 3.
Table 93 Linux SAN configuration rules Storage systems1 All supported P2000 G3 FC MSA2000fc G2 (MSA2300fc) MSA2000fc Linux SAN rules • Supports multipathing high-availability configuration in multiple fabrics or in a single fabric with zoned paths. • Zoning is required when Linux is used in a heterogeneous SAN with other operating systems. • For HBA parameter settings, see “MSA 2040 SAN, MSA 1040 FC, P2000 G3 FC, MSA2000fc G2 and MSA2000fc storage system rules” (page 213).
Table 94 Linux storage system, HBA, and multipath software coexistence support1 P2000 G3 P9500, XP7 MSA2000fc XP24000/20000/ P63xx/P65xx EVA G2(MSA2300fc) EVA4x00/6x00/8x00 12000/10000 3PAR Device-Mapper Multipath P2000 G3MSA2000fc G2(MSA2300fc) P63xx/P65xx EVA EVA4x00/6x00/8x00 S S S S S S S S S S S S S S S Device-Mapper Multipath P9500, XP7 XP24000/20000/12000/10000 3PAR 1 S Legend: D = same server and different HBA; S = same server and HBA; — = not supported Microsoft Windows SAN
Table 95 Microsoft Windows SAN configuration rules (continued) Storage systems1 Windows SAN rules P6300 EVA • Supports boot from SAN. For more information, see “P6000/EVA SAN boot support” (page 229). P6350 EVA • For HP P6000 Continuous Access configuration information, see “HP P6000 Continuous Access SAN integration” (page 228). P6500 EVA P6550 EVA • Zoning is required when Windows is used in a heterogeneous SAN with other operating systems. SVSP 3.
Table 96 Microsoft Windows storage system, HBA, and multipath software coexistence support1 P2000 G3 XP 7 XP10000/12000XP MSA2000fc G2(MSA2300fc) P63xx/P65xx EVA MSA2000fc EVA4x00/6x00/8x002 20000/24000 P9500 MS MPIO DSM3 HP MPIO FF4 MS MPIO DSM S S S S S HP MPIO FF4 S S — S MS MPIO DSM S — S S S S MS MPIO DSM SVSP 3.
Oracle Solaris SAN rules This section describes the SAN rules for Oracle Solaris. For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 97 (page 204) describes the SAN configuration rules for Oracle Solaris. Table 98 (page 206) describes support for Oracle Solaris storage, HBA, and multipathing coexistence.
1 Unlisted but supported storage systems have no additional SAN configuration restrictions. For the latest support information, contact an HP storage representative.
Table 98 Oracle Solaris storage system, HBA, and multipath software coexistence support1 P2000 G3 MSA2000fc G2(2300fc) Notes3 P63xx/P65xx EVAEVA4x00/ 6x00/8x002 P9500, XP7, XP24000/20000, XP12000/10000 SVSP 3.
VMware ESX SAN rules This section describes the SAN rules for VMware ESX. For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 99 (page 207) describes the SAN configuration rules for VMware ESX. Table 99 VMware ESX SAN configuration rules Storage systems1 All supported ESX SAN rules Zoning is required when ESX is used in a heterogeneous SAN with other operating systems.
Citrix Xen SAN rules This section describes the SAN rules for Xen. For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 100 (page 208) describes SAN rules for Xen Table 100 Xen SAN configuration rules Storage systems1 • Supports multipathing high-availability configuration in multiple fabrics or in a single fabric with zoned paths.
Common SAN coexistence To configure different HP storage system types or third-party storage systems for coexistence in a common SAN, without common access from the same server, define a separate zone for each storage system family.
Connection to a common server with different HBA vendor products requires separate HBA zones for each storage system: • All Fibre Channel HBA zones must contain HBAs from the same vendor. • A zone can contain different HBA models if they are all from the same HBA vendor. • A Fibre Channel HBA can be a member in more than one zone. • All HBA members in the same zone can reside in different servers, but must be the same operating system type.
11 MSA storage system rules This chapter describes specific rules for the following entry-level storage systems: • HP MSA 2040 SAN • HP MSA 1040 FC • MSA P2000 FC, MSA P2000 FC/iSCSI • Modular Smart Array 2000fc G2 • Modular Smart Array 2000fc For the iSCSI rules for the MSA2000i, see “HP StorageWorks MSA family of iSCSI SAN arrays” (page 325). HP MSA storage system configurations Table 101 (page 211) describes the configurations for the MSA family.
Table 102 MSA2000fc controller configurations Storage system Description MSA2012fc single controller Used in a direct connect or SAN connect configuration with a standard single controller MSA2012fc dual controller Used in a direct connect or SAN connect configuration with standard dual controllers MSA2212fc enhanced dual controller Used in a direct connect or SAN connect configuration with enhanced dual controllers Heterogeneous SAN support The MSA 2040/1040, P2000 G3, and MSA2000 families support
For the latest information on firmware versions and MSA storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Configuration rules Table 104 (page 213) describes the MSA 2040 SAN, MSA 1040 FC, P2000 G3 FC, MSA2000fc and MSA2000fc G2 storage system SAN configuration rules.
Table 105 MSA 2040 SAN, MSA 1040 FC, P2000 G3 FC, FC/iSCSI, MSA2000fc G2, and MSA2000fc maximum configurations Storage systems Operating systems Drives Hosts Snapshots and clones1 LUNs LUN size 512 Up to 64 TB depending on vdisk configuration 64 standard (maximum 512 snapshots) 512 Up to 64 TB depending on vdisk configuration 64 standard (maximum 512 snapshots) 64 512 Up to 64 TB 64 standard depending (maximum 512 on vdisk snapshots, clones or configuration remote snaps) 64 512 Up to 64 TB
P2000 data migration The P2000 G3 Fibre Channel storage system supports data migration using the HP StorageWorks MPX200 Multifunction Router data migration feature. This feature provides for block (LUN) level data movement between source and destination storage systems. MPX200 Multifunction Router with data migration The MPX200 Multifunction Router supports iSCSI, FCoE, data migration, and FCIP.
Table 106 P2000 data migration source-destination storage systems Source storage systems P2000 destination storage systems • All HP MSA (Fibre Channel) and P6000/EVA models • P9500/XP24000/20000, XP12000/10000 • SVSP • 3PAR S-Class Third-party array models: • Dell EqualLogic family (iSCSI), Compellent Series 30 and 40 Controllers • EMC CLARiiON AX series, CX Series, Symmetrix DMX Series, Symmetrix VMAX SE, VNX5500 P2000 G3 FC • Fujitsu ETERNUS DX400, DX440 S2, DX8400 • Hitachi Data Systems V series, AMS
For the latest data migration storage system, operating system, and version support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Management software support The MSA 2040 SAN, MSA 1040 FC, P2000 G3 FC, FC/iSCSI, MSA2000fc G2, and MSA2000fc support target-based management interfaces, including Telnet (CLI), FTP, and a web-based interface. The web-based interface is supported with Microsoft Internet Explorer and Mozilla Firefox.
12 HP StoreVirtual storage system rules This chapter describes specific rules for management groups with at least two of the following storage systems: • HP StoreVirtual 4730 FC Storage • HP StoreVirtual 4330 FC Storage This chapter describes the following topics: • “Fibre Channel on HP StoreVirtual 4000 Storage” (page 218) • “Campus cluster support” (page 218) • “Heterogeneous SAN support” (page 219) • “Configuration rules” (page 219) • “Configuration parameters” (page 220) • “Data migration”
NOTE: 500 MB/s (4,000 Mb/s) of bandwidth per storage node pair needs to be allocated on the 10 GbE network between the two locations. Network latency among storage nodes cannot exceed 1 ms. The two Fibre Channel fabrics between the two sites can be stretched using any native and transparent fabric extension technology, such as long-range optics and DWDM. SAN extension using other intermediate protocols, like IP, is not supported in campus cluster configurations.
For information about configuring HP StoreVirtual 4000 Storage using the Centralized Management Console, see HP StoreVirtual 4000 Storage User Guide. Configuration parameters For configuration settings for Fibre Channel on HP StoreVirtual 4000 Storage, see HP StoreVirtual 4000 Storage User Guide, and configuration sets on SPOCK. Data migration Fibre Channel on HP StoreVirtual 4000 Storage does not currently support data migration using the MPX200.
13 P6000/EVA storage system rules This chapter describes specific rules for the following storage systems: • EVA4100 • EVA4400 • EVA6100 • EVA8100 • EVA6400/8400 • P6300/P6500 EVA • P6350/P6550 EVA IMPORTANT: HP P6000 storage was formerly called the HP Enterprise Virtual Array product family. General references to HP P6000 can also refer to earlier versions of HP EVA products.
Heterogeneous SAN support P6000/EVA HSV-based controller storage systems support shared access with any combination of operating systems listed in Table 109 (page 222).
Table 110 P6000/EVA storage system rules (continued) Rule number 7 Description EVA4400 (without the embedded switch module) with XCS 09x and EVA4100/6100/6400/8100/8400 are supported with 8 Gb/s, 4 Gb/s, or 2 Gb/s switch or HBA direct connectivity only (see rule 9). • EVA6400/8400 requires XCS 095x minimum. • EVA4100/6100/8100 requires XCS 6.2x minimum. • P6300/P6500 EVA requires XCS 10001000 minimum. • P6350/P6550 EVA requires XCS 11001000 minimum.
Table 110 P6000/EVA storage system rules (continued) Rule number 10 Description All P6000/EVA host ports must contain a cable or a loopback connector; otherwise, host port error events will persist. If the P6000/EVA host port is empty, perform the following steps: • From the OCP or WOCP, set the port to direct connect mode. • Insert a loopback connector when a P6000/EVA host port is not connected to a switch or an HBA (for direct connect). 11 Supports connection of single HBA servers.
LUNs #161 through #192 are presented to 4-node cluster = 0128 LUN presentations LUNs #193 through #200 are presented to single host = 0008 LUN presentations When all LUNs are presented to all hosts, the number of LUNs multiplied by the number of hosts must not exceed 8,192. Table 111 (page 225) lists the maximum number of EVA storage systems that can be configured on a single server. There is no limit on the maximum number of EVA storage systems in a SAN.
P6000/EVA data migration The P6000/EVA family of Fibre Channel storage systems supports data migration using the HP StorageWorks MPX200 Multifunction Router data migration feature. This feature provides for block (LUN) level data movement between source and destination storage systems. MPX200 Multifunction Router with data migration The MPX200 Multifunction Router supports iSCSI, FCoE, data migration, and FCIP.
Table 112 P6000/EVA data migration source-destination storage systems Source storage systems P6000/EVA destination storage systems • All HP MSA (Fibre Channel) and P6000/EVA models • P9500/XP24000/20000, XP12000/10000 • SVSP • 3PAR S-Class Third-party array models: • Dell EqualLogic family (iSCSI), Compellent Series 30 and 40 Controllers • EVA4400/4400 with embedded switch • EMC CLARiiON AX series, CX Series, Symmetrix DMX • EVA4100/6100/8100 Series, Symmetrix VMAX SE, VNX5500 • EVA6400/8400 • Fujitsu ET
For current data migration storage system support and up-to-date operating system version support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Data migration considerations MPX200 connectivity to P6000/EVA storage as a data migration destination array is obtained through a Fibre Channel switch configured in the same fabric as the MPX200 Fibre Channel ports.
Table 114 HP P6000 Continuous Access heterogeneous SAN configuration rules (continued) Rule number Description 7 The HP P6000 Continuous Access link supports mixed heterogeneous SAN, HP P6000 Continuous Access, and OpenVMS host-based shadowing traffic. 8 Two Storage Management Appliance Command View element managers are required: one active and one either active in standby mode or in powered-off, passive mode.
For HP P6000 Continuous Access, if the operating system supports boot from SAN, replication of the boot disk is supported. SAN boot through the B-series MP Router is not supported. Storage management server integration A management server is required to manage an P6000/EVA storage system. The management server can be an SMA, GPS, management station (dedicated server), or HP Storage Server. The management server communicates with storage systems in-band through a Fibre Channel connection.
Cabling This section describes cabling options for high-availability multipathing configurations for P6000/EVA storage systems. Level 4 NSPOF configuration Figure 77 (page 231) through Figure 80 (page 233) show cabling options when implementing a level 4, high-availability, NSPOF configuration. For a description of availability levels, see “Data availability” (page 38).
Figure 78 EVA4400 9x straight-cable configuration A B 26408a Figure 79 (page 232) shows the cabling scheme for both non-HP P6000 Continuous Access and HP P6000 Continuous Access configurations for EVA8100 storage systems. Figure 79 EVA8100 straight-cable configuration 25131b Figure 80 (page 233) shows an EVA8100 configuration in which all controller host ports support two independent, dual-redundant SANs. In this configuration, SAN 1 represents a dual-redundant SAN with Fabric A and Fabric B.
Figure 80 EVA8100 two independent, dual-redundant SAN configuration Fabric A Fabric C SAN 1 SAN 2 Fabric B Fabric D 25132a Dual-channel HBA configurations Use dual-channel HBAs when the number of server PCI slots is limited. Most installations are configured as shown in Figure 81 (page 233) or Figure 82 (page 233).
Figure 83 (page 234) shows a sample NSPOF solution with two dual-channel HBAs. This availability solution is equivalent to using two single-channel HBAs. For more information, see “Data availability” (page 38). Figure 83 Two dual-channel HBAs (NSPOF) Dual-channel HBA Port 1 Targets A, B,... Port 2 Targets C, D,... 1 Dual-channel HBA Port 1 Port 2 Targets A, B,... Targets C, D,...
14 P9000/XP storage system rules This chapter describes specific rules for the following storage systems: • XP7 • XP12000 • P9500 • XP10000 • XP24000 • XP20000 This chapter describes the following topics: • “P9000/XP storage systems” (page 235) • “P9000/XP SAN boot support” (page 238) • “LUN Configuration and Security Manager XP support” (page 239) • “P9000/XP data migration” (page 239) P9000/XP storage systems Before implementation, contact an HP storage representative for information about su
Table 117 P9000/XP heterogeneous SAN support (continued) Storage systems Firmware version1 Switches2, 3 Operating systems3 Citrix 5.6 XP20000 HP-UX 60x XP24000 IBM AIX Microsoft Windows XP12000 50x XP10000 B-series OpenVMS C-series Red Hat Linux H-series5 Oracle Solaris SUSE Linux Tru64 UNIX VMware ESX 1 Contact an HP storage representative for the latest firmware version support. 2 XP7 and P9500 storage systems are not supported with 2 Gb/s switches.
Table 118 P9000/XP storage system rules (continued) Rule number 6 Description XP24000/20000 and XP12000/10000 storage systems support F_Port, FL_Port, and NL_Port connectivity.
Figure 84 P9000/XP storage systems with tape storage in a shared fabric HP-UX Windows Solaris AIX VMware All supported switches XP P9500 FC bridge 25140c P9000/XP SAN boot support P9000/XP LUNs can be booted from the SAN using B-series, C-series, and H-series switches. switches. SAN boot through the B-series MP Router is not supported.
3 XP12000/10000 boot on OpenVMS and Tru64 requires Alpha Server console 6.9 (or later). 4 Not all storage systems or operating systems listed are supported with H-series switches.
migration, except where noted. Table 121 (page 241) describes the operating system support for online data migration. For information about configuring the MPX200 for data migration, see the HP MPX200 Multifunction Router Data Migration Solution Guide.
Table 121 Online data migration operating system support MPX200 online data migration support1 Online data migration destination storage system and firmware (minimum) • P2000 G3 FC (TS251P002-04) • P4000 (9.0) • P6350/P6550 (11001000) • EVA8000/6000/4000 (6.200) • EVA8100/6100/4100 (6.220) • HP-UX 11iv3, 11iv2, Clusters (Service Guard) 2 • IBM AIX 6.1, 5.
15 SVSP storage system rules This chapter describes the HP SVSP storage system rules.
• Bidirectional, asynchronous remote replication with automated initial normalization between source and destination (up to 150 ms one-way latency for asynchronous mirroring) NOTE: HP SVSP uses built-in iSCSI; therefore, no additional devices are required to connect HP SVSP to the intersite IP network. For network requirements for asynchronous replication, see Table 124 (page 246). • Synchronous mirroring across 100 km or (0.
• IP-based intersite links (for SVSP Continuous Access) • Minimum of one host • Minimum of two HBAs per host or one dual-channel HBA per host NOTE: Long-distance asynchronous remote mirroring requires an additional domain at the other site and sufficient IP-based bandwidth between sites. For network requirements for asynchronous replication, see Table 124 (page 246). For more information, see “Level 4: multiple fabrics and device paths (NSPOF)” (page 39).
Table 123 SVSP heterogeneous SAN storage rules (continued) Rule number Description the switch hop limits, including the host-to-local storage link, the local storage-to-remote storage link, and the local host-to-remote storage link.
SVSP data migration SVSP is supported as a data migration source storage system when using the HP StorageWorks MPX200 Multifunction Router data migration feature. This feature provides for block (LUN) level data movement between source and destination storage systems. For data migration from SVSP to P2000, see “P2000 data migration” (page 215) and for SVSP to P6000/EVA, see “P6000/EVA data migration” (page 226).
Table 124 SVSP inter-site network requirements for long distance gateways (continued) Specification 1 Maximum latency Description 150 ms IP network delay one-way or 300 ms round-trip 2 Average packet-loss ratio 3 Latency jitter Must not exceed 0.5% averaged over a 5-minute window Must not exceed plus or minus 10% over a 5-minute window 1 Pre-existing restriction 2 A high packet-loss ratio indicates the need to retransmit data across the inter-site link.
• ◦ 49,152 with three DPM groups ◦ 65,536 with four DPM groups DPM BE paths 4,096 maximum per DPM (regardless of pairs, all must see same storage) NOTE: For Large LUNs, every 2 TB counts as one LUN. For example, a Large LUN of 8 TB would count as 4 LUNs against the maximum of 2,047 LUNs per EVA. For additional information about SVSP maximums, see HP StorageWorks SAN Virtualization Services Platform Release Notes at http://www.hp.com/go/SVSP.
16 3PAR StoreServ storage rules This chapter describes specific rules for the following storage systems: • 3PAR F200/F400 Storage • 3PAR T400/T800 Storage • 3PAR StoreServ 10400/10800 Storage • 3PAR StoreServ 7200/7400 Storage • 3PAR StoreServ 7450 Storage This chapter describes the following topics: • “3PAR StoreServ storage” (page 249) • “3PAR data migration” (page 251) • “3PAR storage management” (page 254) 3PAR StoreServ storage Before implementation, contact an HP storage representative f
4 5 Apple Mac OS X is supported only with 10400/10800, 7200/7400, and 7450 storage systems, running a minimum 3PAR OS version of 3.1.3. Apple Mac OS X is supported only with B-series and C-series switches. Configuration rules Table 126 (page 250) describes HP 3PAR StoreServ Storage system SAN configuration rules. NOTE: For information about 3PAR StoreServ FCoE target support, see the HP SPOCK 3PAR FCoE configuration sets on the SPOCK website at http://www.hp.com/storage/spock.
For configuration settings for the InServ ports, see the HP 3PAR implementation guide for each of the supported operating systems. Virtual Connect Direct-attach Fibre Channel for 3PAR Storage HP supports Virtual Connect Direct-attach Fibre Channel for 3PAR storage using the Virtual Connect FlexFabric 10 Gb/24-port Module. This provides connectivity between HP c-Class BladeSystems and 3PAR StoreServ Storage systems without a Fibre Channel switch or fabric.
Table 127 HP 3PAR Online Import Utility for EMC Storage host support matrix Host O/S Server type Fibre Channel HBA Source array Windows 2008 R2 EMC CX4-120 Windows 2012 EMC CX4-240 HP ProLiant:Intel/AMD x86/x64 RHEL 6 U3, U4, U5 HP BladeSystem c-Class EMC CX4-480 3PAR 7200 EMC CX4-960 3PAR 7400 EMC VNX5100 3PAR 7450 HP EMC Destination array EMC VNX5300 3PAR 10400 EMC VNX5500 3PAR 10800 EMC VNX5700 EMC VNX7500 MPX200 Multifunction Router with data migration The MPX200 Multifunction Rou
Table 128 3PAR data migration source-destination storage systems Source storage systems 3PAR destination storage systems • All HP MSA (Fibre Channel) and EVA models • P9500/XP24000/20000, XP12000/10000 • SVSP • 3PAR S-Class Third-party array models1: • Dell EqualLogic family (iSCSI), Compellent Series 30 and 40 Controllers • EMC CLARiiON AX series, CX Series, Symmetrix DMX Series, Symmetrix VMAX SE, VNX5500 • Fujitsu ETERNUS DX400, DX440 S2, DX8400 3PAR StoreServ 10400/10800; 3PAR StoreServ 7450; 3PAR St
For the latest data migration storage system, operating system, and version support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. 3PAR data migration considerations MPX200 connectivity to 3PAR storage as a data migration destination array is obtained through a Fibre Channel switch configured in the same fabric as the MPX200 Fibre Channel ports.
17 Enterprise Backup Solution One of the most significant benefits of a SAN is the ability to share the SAN infrastructure for both disk and tape. With a SAN backup solution, you get all the benefits of the SAN, such as, consolidated storage, centralized management, and increased performance. Additionally, implementing a SAN backup solution lays the foundation for advanced data protection features such as serverless backup and backup to disk. The HP solution is the HP Enterprise Backup Solution (EBS).
Part IV SAN extension and bridging SAN extension and bridging are presented in these chapters: • “SAN extension” (page 257) • “iSCSI storage” (page 318) • “Network Attached Storage” (page 365)
18 SAN extension SAN extension enables you to implement disaster-tolerant storage solutions over long distances and multiple sites.
This section describes: • “SAN extension technology” (page 258) • “SAN-iSCSI bridging technology” (page 259) SAN extension technology HP supports the following SAN extension technologies: • • “Fibre Channel long-distance technology” (page 259), including: ◦ “Fiber optic transceivers” (page 259) ◦ “Wavelength division multiplexing” (page 261) ◦ “Extended fabric settings for Fibre Channel switches” (page 264) “Multi-protocol long-distance technology” (page 266), including: ◦ “Fibre Channel over
SAN-iSCSI bridging technology SAN-iSCSI bridging connects Fibre Channel networks and IP networks.
Figure 87 SC GBIC transceiver 25143a Table 131 (page 260) lists supported long-wave transceiver distances and maximum supported distances under ideal operating conditions. Some long-wave optical transceivers can transmit up to a distance of 100 km.
For detailed information about distance rules for long-wave transceivers, see: • “Fibre Channel distance rules for 16 Gb/s and 8 Gb/s switch models (B-series, C-series, and H-series)” (page 157) • “Fibre Channel distance rules for 4 Gb/s switch models (B-series and C-series switches)” (page 158) • “Fibre Channel distance rules for 2 Gb/s switch models (B-series and C-series switches)” (page 159) • “Fibre Channel distance rules for 1 Gb/s switch models (B-series and C-series switches)” (page 159) NOT
WDM system architectures The WDM system architectures are as follows: • Passive (optical transmission protocol) • Active signal amplification • Active protocol handling Most WDM products use one of these architectures or combine attributes of each. Table 132 (page 262) summarizes the WDM system architectures.
• Allow interoperability through standards-compliant interfaces such as Fibre Channel, SONET, and ATM • Convert wavelengths at each interface channel before multiplexing with other channels for transmission HP coarse wave division multiplexing HP offers CWDM, which is similar to DWDM but is less expensive, less expandable (maximum of eight channels), and covers a shorter distance (up to a maximum of 100 km using the 1 Gb/s or 2 Gb/s CWDM SFP transceivers, and a maximum of 40 km using the 4 Gb/s CWDM SFP
Figure 88 Basic WDM configuration using one long-distance fiber optic link Fabric 1 Local Fabric 1 Remote WDM connection Fabric 2 Local Fabric 2 Remote 25144a The configuration in Figure 88 (page 264) is low cost, but has no long-distance link redundancy.
Table 133 (page 265) describes the appropriate port protocol setting based on the WDM system architecture. Table 133 Port protocol setting based on the extension architecture WDM system architecture B-series port protocol setting Active protocol handling (Table 132 (page 262)) portCfgISLMode slot/port, 1 Passive protocol handling portCfgISLMode slot/port, 0 NOTE: The portCfgISLMode and portCfgLongDistance L0.5, L1, or L2 mode cannot be enabled at the same time; otherwise, fabric segmentation occurs.
H-series switch settings The H-series switches have a fixed BB-credit setting. When using supported long-wave SFP, the following distances are supported: • 3.3 km at 8 Gb/s • 6.6 km at 4 Gb/s • 10 km at 2 Gb/s However, you can use EFMS to allocate more buffer credits to ports of an H-series switch to achieve increased distance up to the limit of the SFP capability, allowing 10 km at 8 Gb/s, 4Gb/s, or 2 Gb/s to be supported.
Figure 90 FCIP single-link configuration Fabric 1 Local Fabric 1 Remote IP 25146a FCIP dual-link configuration A dual-link configuration provides redundancy (Figure 91). If one link fails, the other link temporarily handles all data replication. For enhanced fault tolerance, you can use two IP providers.
Table 135 FCIP network consideration Configuration type Mirrored FCIP SAN Data migration Use existing network? Factors No For peak performance, HP recommends using a separate network. A dedicated network is the benchmark for mirrored FCIP SAN systems. Yes Because data migration is usually a one-time event for upgrade or maintenance purposes, you can use your existing network. However, network performance can be significantly degraded during data migration.
Determining the required bandwidth You can determine the required bandwidth for any application. This example explains how to measure the amount of new or changed data: 1. Collect the peak read and write workloads for a given period of time. For Windows operating systems, use a tool such as PERFMON to capture the current performance requirements while HP P6000 Continuous Access is not running. Similar tools exist for other operating systems. 2.
Table 136 HP FCIP gateways Gateway Supported switches “B-series 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade” (page 287) B-series switches “B-series 400 MP Router and MP Router Blade” (page 290) “B-series MP Router” (page 292) “C-series MDS 9216i, 9222i, IPS-4, IPS-8, 14/2 Multiprotocol Services Modules, 18/4 Multiservice Modules” (page 294) C-series switches “HP IP Distance Gateway (mpx110)” (page 273) B-series, C-series, and H-series switches “MPX200 Multifunction Router with FCIP
FC-SONET IP link configurations Using FC-SONET, you can configure the SANs through a single link, dual links, or shared ISL links. FC-SONET dual-link configuration A dual-link configuration is the benchmark for disaster protection (Figure 93 (page 271)). If one link fails, the other link temporarily handles all data replication. For enhanced fault tolerance, you use two IP providers, accessing the data center through two links.
Fibre Channel over ATM Direct FC-to-ATM conversion is supported by the Fibre Channel standards. However, currently, no vendors sell direct FC-to-ATM gateways. If you have an ATM-based network, consider using FC-to-GbE IP gateways, with an ATM blade residing on the Ethernet switch or IP router to convert the GbE to ATM. For detailed information about distance rules for Fibre Channel over ATM, see “ATM extension Fibre Channel distance rules” (page 160).
Table 138 Features and usage for HP supported FCIP SAN extension products (continued) FCIP gateway Supported product fabrics B-series 1606 Extension SAN Switch DC Dir Switch MP Extension Blade B-series 400 MP Router MP Router Blade Inter-fabric connectivity Supported DR software Data compression method/use Recommended IP bandwidths (WAN) Network requirements VEX_Port B-series See Table 141 (page 287).
IP Distance Gateway configuration examples The IP Distance Gateway supports the configurations shown in Figure 95 (page 274) through Figure 105 (page 280). Figure 95 (page 274) shows a basic FCIP configuration with a local mpx110 and a remote mpx110 connected through an IP WAN using one or two long-distance links.
Figure 97 IP Distance Gateway high-availability configuration with a redundant IP network WAN LAN LAN FCIP GbE Local FC servers GbE Fabric A1 Fabric A2 HP Storage Works mpx100 HP FC1 Storage Works mpx100 Remote FC servers FC1 FC2 FC2 MGMT IOIOI GE1 MGMT IOIOI GE1 GE2 GE2 ! ! mpx110 mpx110 Fabric B1 Fabric B2 HP Storage Works mpx100 HP FC1 Storage Works mpx100 FC1 FC2 FC2 MGMT IOIOI GE1 MGMT IOIOI GE1 GE2 GE2 ! ! mpx110 mpx110 GbE Local storage system LAN GbE
Figure 99 IP Distance Gateway FCIP with B-series Integrated Routing LAN WAN LAN FCIP Local FC servers GbE Fabric A1 EX HP GbE E Storage Works mpx100 HP Storage Works mpx100 FC1 FC1 FC2 FC2 MGMT IOIOI GE1 Fabric A2 Remote FC servers MGMT IOIOI GE1 GE2 GE2 ! ! mpx110 mpx110 Local storage system Remote storage system 26626a Figure 100 (page 276) shows a configuration using the mpx110 with FCIP and C-series switches with IVR.
Figure 101 Highly redundant pairs of gateways, two long distance links LAN WAN LAN FCIP GbE Local FC servers Fabric A1 HP GbE Storage Works mpx100 HP FC1 Remote FC servers Fabric A2 Storage Works mpx100 FC1 FC2 FC2 MGMT IOIOI GE1 MGMT IOIOI GE1 GE2 GE2 GbE ! ! GbE mpx110 Fabric B1 HP mpx110 Storage Works mpx100 HP FC1 Fabric B2 Storage Works mpx100 FC1 FC2 FC2 MGMT IOIOI GE1 MGMT IOIOI GE1 GE2 GE2 ! ! mpx110 Local storage system mpx110 Remote storage system
connectivity and redundancy using six mpx110 gateways. Figure 105 shows the highest level of 3-site connectivity using eight mpx110 gateways. The following configuration rules apply to Figure 103 through Figure 105 (fan-in/fan-out): • For Site 1, Site 2 or Site 3 can function as the remote site. • For Site 2 or Site 3, Site 1 can function as the remote site. • Replication between Site 2 and Site 3 is not supported.
Figure 104 HP P6000 Continuous Access 3-site configuration with six mpx110 gateways LAN HP Fabric A2 Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 GE2 ! LAN HP mpx110 A2 Fabric B2 Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 mpx110 B2 GE2 ! Fabric A1 HP LAN Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 GE2 ! Fabric B1 HP mpx110 A1 Site 2 WAN Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 GE2 ! mpx110 B1 LAN LAN Site 1 HP Fabric A3 Storage Works mpx100 FC1 FC2 MGMT IOI
Figure 105 HP P6000 Continuous Access 3-site configuration with eight gateways LAN LAN HP Fabric A2 Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 mpx110 A2 GE2 ! Fabric A1 HP Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 GE2 ! mpx110 A1-1 HP Fabric B2 Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 mpx110 B2 GE2 ! HP Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 GE2 ! mpx110 A1-2 LAN LAN Site 2 WAN LAN LAN HP Storage Works mpx100 FC1 FC2 MGMT IOIOI GE1 GE2 ! mpx110 B1-1 H
Figure 106 (page 281) shows long-distance link redundancy and full connectivity between all three sites.
For current storage system support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Operating system and multipath support The mpx110 gateway is supported using FCIP with all operating systems and multipath software supported by HP for HP P6000 Continuous Access, HP P9000 (XP) Continuous Access, and 3PAR Remote Copy. See Table 139 (page 273) and Table 140 (page 283).
The MPX200 FCIP feature can be configured as a standalone function or for use simultaneously with iSCSI. A license is required to enable the FCIP feature. All licenses are half-chassis based, enabling FCIP to be configured on one or both bays (slots) in a dual-blade chassis configuration.
Figure 107 MPX200 basic FCIP configuration with one or two long-distance links LAN WAN LAN FCIP Local FC servers Fabric A1 GbE GbE GbE HP HP Fabric A2 GbE Remote FC servers Storage Works MPX200 Storage Works MPX200 GE4 GE4 GE3 MGMT GE3 MGMT IOIOI IOIOI MPX200 MPX200 1 GbE Multifuncti Blade on Router 1 GbE Multifuncti Blade on Router FC1 FC1 FC2 FC2 GE1 GE1 GE2 GE2 MPX200 MPX200 Fabric B1 Fabric B2 Local storage system Remote storage system 26609b Figure 108 (page 284) shows
Figure 109 (page 285) shows a configuration using the MPX200 with FCIP and C-series switches with IVR. This provides fabric isolation between the local and remote fabrics, allowing device access without merging the fabrics. This can be implemented in all supported MPX200 FCIP configurations using C-series Fibre Channel switches with IVR.
Figure 111 Local MPX200 basic FCIP configuration with remote IP Distance Gateway (mpx100) LAN WAN LAN FCIP Local FC servers Fabric A1 GbE HP GbE GbE Fabric A2 mpx110 Fabric B2 GbE Remote FC servers Storage Works MPX200 HP GE4 GE3 MGMT Storage Works mpx100 FC1 IOIOI MPX200 FC2 1 GbE Multifuncti Blade on Router MGMT FC1 IOIOI GE1 GE2 FC2 ! GE1 GE2 Fabric B1 MPX200 Local storage system Remote storage system 26611b FCIP Configuration rules The section describes the FCIP configu
For XP, the MPX200 is supported for use with HP P9000 (XP) Continuous Access for XP24000/20000 and XP12000/10000. • The MPX200 Multifunction Router is supported for use in all supported HP P6000 Continuous Access SAN configurations, including the standard two-fabric, five-fabric, and six-fabric configurations. For more information, see the HP P6000 Continuous Access documentation. • FCIP is supported for HP P6000 Continuous Access DR group LUNs and non-DR LUNs.
Table 141 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade features and requirements (continued) Feature Requirements These products are also supported for use as Fibre Channel switches. This provides both Fibre Channel switch connectivity for hosts and storage systems and FCIP connectivity for SAN extension.
Figure 112 NSPOF configuration with 1606 Extension SAN Switches providing Fibre Channel routing and FCIP 1606 Extension SAN Switch 1606 Extension SAN Switch Fabric A1 Fabric A2 IP A FCIP with FC routing 1606 Extension SAN Switch Fabric B1 1606 Extension SAN Switch Fabric B2 IP B FCIP with FC routing 26583b Figure 113 Fibre Channel routing and FCIP using two 1606 Extension SAN Switches Fabric A1 1606 Extension SAN Switch IP A 1606 Extension SAN Switch Fabric A2 IP B Fabric B1 Fabric B2 FCIP w
B-series 400 MP Router and MP Router Blade The B-series 400 MP Router and MP Router Blade offer FCIP SAN extension, Fibre Channel routing, and Fibre Channel switching. You can use all three of these functions on the same 400 MP Router or MP Router Blade simultaneously. A 400 MP Router or MP Router Blade can have: • Up to 2 GbE IP ports for FCIP. For more information, see “SAN extension” (page 257). • Up to 16 EX_Ports for Fibre Channel routing services.
Table 142 400 MP Router and MP Router Blade features and requirements (continued) Feature Requirements • HP P6000 Continuous Access • HP P9000 (XP) Continuous Access • HP 3PAR Remote Copy For operating system support, see “Heterogeneous server rules” (page 165). FCIP FastWrite is supported with HP P9000 (XP) Continuous Access and is not supported with HP P6000 Continuous Access.
HP supports FCIP configurations in which the 400 MP Router or MP Router Blade serves as an FCIP gateway and a Fibre Channel switch. Servers and storage systems that support Continuous Access with FCIP can be directly connected to the Fibre Channel ports on the 400 MP Router or MP Router Blade (Figure 117).
Table 143 B-series MP Router features and requirements Feature Requirements The MP Router is supported with the B-series switches listed in “B-series switches and fabric rules” (page 91). The MP Router is not supported for use as a Fibre Channel switch. Direct device connectivity to MP Router ports (F_Ports) is supported only with iSCSISee “iSCSI storage” (page 318).
Figure 119 MP Routers connecting fabrics using two IP subnets MPR 2 Fabric 2 MPR 1 IP subnet A Fabric 1 IP subnet B MPR 3 Fabric 3 25153a In this sample configuration, MP Router 1 must have a GbE connection to IP subnet A and a GbE connection to a IP subnet B. A Fibre Channel host or device connected to Fabric 1 can access devices in Fabric 2 and/or Fabric 3. Figure 120 (page 294) shows a redundant FCIP configuration in which pairs of MP Routers provide full redundancy.
Table 144 (page 295) lists the features and requirements for the C-series modules.
The following sections describe network requirements for replication products with qualified gateways: • “SAN extension best practices for HP P6000 Continuous Access” (page 296) • “ HP P6000 Continuous Access with XCS 11x, XCS 10x, or XCS 09x” (page 296) • “HP P6000 Continuous Access with XCS 6.x” (page 298) • “HP P6000 Continuous Access with VCS 4.
Table 145 Network requirements for long-distance IP gateways with XCS 11x, XCS 10x, or XCS 09x Specification Description • Must be dedicated to the HP P6000 Continuous Access storage replication function. IP bandwidth1 • The minimum IP bandwidth required for HP P6000 Continuous Access with P63xx/P65xx EVA, EVA4400/6400/8400, and EVA4400 (embedded switch) with FCIP is 2 Mb/s per path, or 4 Mb/s for two paths when using one IP link. • There is no support for dynamic pacing of the gateway.
Table 146 Network requirements for long-distance IP gateways and B-series switches with XCS 11x, XCS 10x, or XCS 09x Minimum IP bandwidth1and maximum DR groups2 Gateway pair HP IP Distance Gateway (mpx110) Minimum supported firmware version DC Dir Switch MP Extension Blade B-series 400 MP Router Single or shared IP link maximum latency 0 to 100 ms one-way 0 to 100 ms one-way See note.
pairs. Table 148 (page 299) lists the network requirements for long-distance gateways that work with EVA XCS 6.x. Table 148 Network requirements for long-distance IP gateways with XCS 6.x Specification Description • Must be dedicated to the HP P6000 Continuous Access storage replication function. IP bandwidth1 • The minimum IP bandwidth required for HP P6000 Continuous Access with FCIP is 2 Mb/s per path, or 4 Mb/s for two paths when using one IP link.
Table 149 Network requirements for long-distance IP gateways and B-series switches with XCS 6.x Minimum IP bandwidth1and maximum DR groups2 Minimum supported Gateway pair firmware version HP IP Distance Gateway (mpx110) Dual IP link maximum latency Single or shared IP link maximum latency 0 to 100 ms one-way 0 to 100 ms one-way See note.
Table 150 (page 301) describes the network bandwidth requirements and IP gateway support for XCS 6.x with C-series switches. Table 150 Network requirements for long-distance IP gateways and C-series switches with XCS 6.x Minimum IP bandwidth1and maximum DR groups2 Minimum supported Gateway pair firmware version HP IP Distance Gateway (mpx110) Dual IP link maximum latency Single or shared IP link maximum latency 0 to 100 ms one-way 0 to 100 ms one-way See note.
Table 151 Network requirements for long-distance IP gateways with VCS 4.x (continued) Specification Description High-loss network: 0.2% average over 24 hours; must not exceed 0.5% for more than 5 minutes in a two-hour window Latency jitter3 Must not exceed 10 ms over 24 hours 1 Pre-existing restriction 2 A high packet-loss ratio indicates the need to retransmit data across the inter-site link.
Table 152 (page 303) describes the network bandwidth requirements and IP gateway support for VCS 4.x with B-series switches. Table 152 Network requirements for long-distance IP gateways and B-series switches with VCS 4.x Minimum IP bandwidth1and maximum DR groups2 Gateway pair HP IP Distance Gateway (mpx110) Minimum supported firmware version Dual IP link maximum latency Single or shared IP link maximum latency 0 to 100 ms one-way 0 to 100 ms one-way See note.
Table 153 (page 304) describes the network bandwidth requirements and IP gateway support for VCS 4.x with C-series switches. Table 153 Network requirements for long-distance IP gateways and C-series switches with VCS 4.x Minimum IP bandwidth1 and maximum DR groups2 Gateway pair HP IP Distance Gateway (mpx110) Minimum supported firmware version Dual IP link maximum latency Single or shared IP link maximum latency 0 to 100 ms one-way 0 to 100 ms one-way See note.
Table 154 HP P9000 (XP) Continuous Access replication modes1 Storage system P95004 XP24000 XP20000 XP12000 XP10000 Synchronous Asynchronous2 Journal3 Recommended firmware versions Minimum firmware versions • — • V01 V01+1 • • • 60.06.05.00/00 60.01.68.00/00 • • • 50.09.86.00/005 50.05.46.00/005 1 Legend: • = supported; — = not supported 2 XP24000/20000/12000/10000: 32K pairs 3 XP24000 with RAID Manager 1.20.05 (or later), XP12000/10000 with RAID Manager 1.17.
Table 156 HP P9000 (XP) Continuous Access Synchronous replication rules (continued) Rule number Description dark fiber, or less than 5 ms using other extension methods. Distances greater than 200 km or latencies greater than 5 ms require HP approval before implementation. Contact HP product support if using greater distances or latencies.
Table 158 HP P9000 (XP) Continuous Access Journal replication rules (continued) Rule number Description 50.08.05.00/00 (or later) allows creation of Business Copy from these devices, but does not allow a fast-restore operation for a Business Copy device. 9 A P-vol can support a maximum of two remote copies (one Continuous Access Journal copy and one Continuous Access Synchronous copy).
• Direct storage-to-storage • Fibre Channel switches • ESCON directors and repeaters • WDM • ATM and SONET/SDH • FCIP and routing extension Direct storage-to-storage Figure 124 (page 308) shows an HP P9000 (XP) Continuous Access direct storage-to-storage configurations for Fibre Channel and ESCON. Table 159 (page 308) describes the maximum supported distances.
Figure 125 HP P9000 (XP) Continuous Access single-switch and multi-switch Fibre Channel configurations RCU I I RCU RCU I I RCU Local Remote 25327a Table 160 HP P9000 (XP) Continuous Access Fibre Channel distances Configuration Maximum distance Single-switch or multi-switchSee Figure 125 (page 309). Note: For Fibre Channel switch model support, contact an HP storage representative.
Figure 127 HP P9000 (XP) Continuous Access ESCON repeater configuration RCP MME SME LCP SME SME MME LCP MME RCP SME MME Local Remote ESCON repeater/director 25326a Table 161 HP P9000 (XP) Continuous Access ESCON director and repeater distances Configuration Maximum distance IBM 9032/9033 director 3 km for short-wave, multi-mode ESCON (MME) IBM 9036 repeater 20 km for long-wave, single-mode ESCON (SME) Nbase Xyplex Note: Supported only in a director-to-director configuration.
Table 162 HP P9000 (XP) Continuous Access WDM distances and equipment (continued) Configuration Maximum distance and equipment Nortel Optera Metro 5200/5100 Movaz RAYexpress ATM and SONET/SDH Figure 129 (page 311) shows HP P9000 (XP) Continuous Access ATM and SONET/SDH configurations. Table 163 (page 312) describes the supported products.
Table 163 HP P9000 (XP) Continuous Access ATM and SONET/SDH products1 XP storage system Configuration ESCON (ATM) XP24000 XP20000 Supported bandwidths and products OC-3—Brocade-CNT Ultranet Storage Director (USD) firmware 2.7 or 3.2.1 OC-3—Brocade-CNT-Inrange 9801 SNS firmware 2.3 (Build 27) or 2.4 (Build 13) Brocade-CNT-Inrange 9811H FW ACP-3; 3.1.
Figure 131 (page 313) and Figure 132 (page 313) show HP P9000 (XP) Continuous Access FCIP and iFCP configurations.
Table 164 Network requirements for long-distance IP gateways with HP P9000 (XP) Continuous Access (continued) Specification Maximum latency1 Requirement See Table 156 (page 305), Table 157 (page 306), and Table 158 (page 306). Low-loss network: 0.0012% average over 24 hours Average packet-loss ratio2 High-loss network: 0.2% average over 24 hours; must not exceed 0.
Table 165 HP P9000 (XP) Continuous Access FCIP gateway support (continued) Product and minimum supported firmware version Table 21 (page 94). XP storage system XP10000 Notes ◦ aptpolicy = 1 ◦ aptpolicy –ap = 0 (port/asic load sharing) ◦ dlsReset (no dynamic load sharing) Exchange-based routing: ◦ aptpolicy = 3 ◦ aptpolicy –ap = 0 (port/asic load sharing) ◦ dlsSet (dynamic load sharing) For additional requirements, see Table 141 (page 287) and Table 160 (page 309).
1 For current support, see the SPOCK website at http://www.hp.com/storage/spock. You must sign up for an HP Passport to enable access. Table 166 HP P9000 (XP) Continuous Access iFCP gateway support Product and minimum supported firmware version XP storage system Brocade-CNT Edge 3000 Firmware: 3.1.1.3, 3.1.2, 3.1.4, 3.1.
Certified third-party WDM, iFCP, and SONET products This section describes the following topics: • “Certified third-party WDM products” (page 317) Certified third-party WDM products HP supports HP P6000 Continuous Access, HP P9000 (XP) Continuous Access, 3PAR Remote Copy, and SVSP Synchronous Mirrors (RAID1) on all WDM products, including DWDM and CWDM, certified by the Fibre Channel switch vendors for the equivalent HP switch models.
19 iSCSI storage This chapter describes iSCSI storage in an HP SAN environment: • “iSCSI overview” (page 318) • “iSCSI concepts” (page 318) • “iSCSI storage network requirements” (page 322) • “HP Native iSCSI products” (page 322) • “HP iSCSI bridge products” (page 332) iSCSI overview iSCSI is a storage transport protocol. The IETF developed iSCSI to encapsulate the SCSI protocol over an IP network. iSCSI has many of the same mechanisms as the Parallel SCSI and Fibre Channel protocols.
• “Software and hardware iSCSI initiators” (page 321) • “Bridging and routing” (page 332) • “iSCSI boot” (page 321) Initiator and target devices An iSCSI router manages access between iSCSI targets and iSCSI initiators as follows: • iSCSI target (logical target)—An end-node device that is typically a storage system, storage router, or bridge. A storage system with iSCSI support is called native iSCSI storage.
Service Location Protocol Clients (initiators) discover services (targets) using SLP, a client-server protocol. SLP for iSCSI uses three components: • An iSCSI initiator has an SLP UA that serves as a client. • iSCSI targets have an SLP SA that acts as an SLP server. • A DA interprets multicast service requests from the server.
During iSCSI login, the initiator and target negotiate the lowest mutually acceptable value for each parameter. Negotiable parameters include: • Type of security protocol, if any • Maximum size of the data payload • Support for unsolicited data • Time-out values During iSCSI login, the initiator and target also exchange nonnegotiable values such as names and aliases. During an iSCSI session, unique session IDs are created for the initiator and target: 1.
iSCSI storage network requirements HP recommends: • Dedicated IP network for iSCSI storage (can be required for some iSCSI products) • Minimum GbE network bandwidth • Multipathing driver when implementing high availability See the iSCSI product sections for additional requirements: • “HP StoreVirtual Storage” (page 329) • “MPX200 Multifunction Router with iSCSI for P6000/EVA storage” (page 333) • “EVA and EVA4400 iSCSI Connectivity Option ” (page 344) • “B-series MP Router and iSCSI” (page 355)
Table 169 10 GbE iSCSI operating system and multipath software support Operating system Multipath software Clusters Microsoft Windows Server 2008, 2003 3PAR MPIO (Windows 2003) MSCS (Windows 2003) Microsoft MPIO DSM (Windows 2008) Failover Cluster (Windows 2008) Red Hat Linux, SUSE Linux, Citrix XenServer Device Mapper Red Hat native cluster suite Solaris Solaris MPxIO Native Solaris cluster VMware VMware MPxIO Native ESX/ESXi cluster solution Citrix XenServer native cluster suite All host
Table 171 iSCSI operating system and multipath software support Operating system Multipath software Clusters Microsoft Windows Server 2008, 2003 3PAR MPIO (Windows 2003) MSCS (Windows 2003) Microsoft MPIO DSM (Windows 2008) Failover Cluster (Windows 2008) Red Hat Linux, SUSE Linux, Citrix XenServer Device Mapper Red Hat native cluster suite Solaris Solaris MPxIO Native Solaris cluster VMware VMware MPxIO Native ESX/ESXi cluster solution Citrix XenServer native cluster suite All hosts must
Table 172 iSCSI/FCoE operating system and multipath software support Operating system Multipath software Clusters Apple Mac OS X (1GbE iSCSI only) None None Microsoft Windows Server 2008, 2003 MPIO with HP DSMMPIO with Microsoft DSM (with CN1000E only) Failover Clustering, MSCS Hyper-V (1 GbE iSCSI only) Red Hat Linux, SUSE Linux Device Mapper None Solaris (1 GbE iSCSI only) Solaris MPxIO None VMware VMware MPxIO None For more information, see the iSCSI or iSCSI/FCoE configuration rules an
MSA2000i G2 and MSA2000i overview The HP StorageWorks Modular Smart Array 2000i G2 (MSA2300i G2) and the HP StorageWorks Modular Smart Array 2000i (MSA2000i) are controller shelves with an iSCSI interface that serves as an iSCSI target.
Table 174 MSA iSCSI storage family maximum configurations (continued) Model Array chassis Expansion1 Expansion maximum 2024 2.5-in drive bay (SFF, upgrade only) MSA2000i G2 2012 3.5-in drive bay (LFF) MSA2000 LFF drive enclosure 5 total enclosures or 99 drives 60 LFF drives MSA2300i 2024 2.5-in drive bay (SFF) MSA2012i Preconfigured single or 4 total enclosures dual controller 3.
Operating system support Table 175 (page 328) lists the supported operating systems for the MSA iSCSI storage family.
Maximum configurations Table 176 (page 329) lists the maximum configurations for the MSA iSCSI storage family. Table 176 MSA iSCSI storage family maximum configurations Storage systems Operating systems Drives LUNs 64 512 Up to 64 TB, 64 standard depending on (maximum 512 vdisk snapshots) configuration 512 Up to 64 TB, 64 standard depending on (maximum 512 vdisk snapshots) configuration Microsoft Windows MSA 2040 SAN Red Hat Enterprise Linux SUSE Linux Enterprise Server 96 3.5-in LFF 199 2.
volume in the cluster. With multiple iSCSI network interfaces across the cluster, a virtual IP address across these interfaces presents the volumes as targets to iSCSI initiators. Key features include: • A cluster of pooled storage supporting up to 16 storage nodes. For larger configurations, contact an HP storage representative. • Two 1GbE ports per storage node (or optional upgrade to SPF+ 10GbE dual ports per storage node).
• Citrix/Linux/Unix bonding of network interfaces performed at the networking layer • For more information, see the following documents: ◦ HP StoreVirtual 4000 Storage Application Aware Snapshot Manager Deployment Guide, at www.hp.com/go/P4000Support (in the Manuals section) ◦ HP StoreVirtual 4000 Storage with VMware vSphere: Design considerations and best practices, at h20195.www2.hp.com/v2/GetDocument.
Table 177 Configuration recommendations Storage item Best practice Caution Not recommended Status indicator Green Orange Red 1 to 1,000 1,001 to 1,500 1,501+ 1 to 4,000 4,001 to 5,000 5,001+ Nodes per group 1 to 20 21 to 32 33+ Nodes per cluster 1 to 10 11 to 15 16+ Volumes + Snapshots + SmartClones iSCSI sessions per group LUN size The maximum LUN size for a fully provisioned volume depends on the storage node size, local RAID configuration, and network RAID configuration settings f
• EVA iSCSI Connectivity Option • EVA4400 iSCSI Connectivity Option MPX200 Multifunction Router with iSCSI for P6000/EVA storage The P6000/EVA family of FC storage systems supports integrated iSCSI connectivity using the MPX200 Multifunction Router.
Figure 135 (page 334) shows an MPX200-EVA dual-blade fabric-attached configuration. This configuration provides high availability with failover between blades.
Figure 137 MPX200 dual-blade multi-EVA configuration MGMT HP StorageWorks MPX200 MGMT MPX200 blade 1 GE4 IOIOI GE3 FC1 FC2 FC1 HP StorageWorks MPX200 GE1 FC2 MPX200 blade 2 MGMT 1 GbE Blade MPX200 Multifunction Router GE4 IOIOI MGMT GE2 IP network management (WAN/LAN) GE3 1 GbE Blade MPX200 Multifunction Router FC1 FC2 FC1 GE1 GE1 FC2 IP network iSCSI data (LAN/VLAN) GE2 GE1 iSCSI NIC P6000 Command View P6000/EVA storage system FP1 FP2 FP1 FP2 FP1 FP2 FP1 FP2 FP1 FP
Figure 139 MPX200 single-blade direct connect to one EVA configuration IP network management (WAN/LAN) MPX200 MGMT HP StorageWorks MPX200 GE4 IOIOI MGMT GE3 1 GbE Blade MPX200 Multifunction Router FC1 FC2 FC1 GE1 FC2 GE2 iSCSI GE1 IP network iSCSI data (LAN/VLAN) NIC P6000/EVA storage system FP1 FP2 FP1 FP2 A B 26640a Figure 140 MPX200 dual-blade direct connect to two EVA configuration MPX200 blade 1 MGMT HP StorageWorks MPX200 MGMT GE4 IOIOI GE3 FC1 FC2 FC1 HP StorageWorks
Table 178 Supported MPX200 maximums (continued) Maximum per MPX200 solution1 Description Total number of iSCSI LUNs 4,096 per chassis, 1,024 per EVA or XP iSCSI connections, 1-GbE 1,024 per blade, 2,048 per chassis iSCSI connections, 10-GbE 2,048 per blade, 4,096 per chassis 1 For mixed blade type chassis configurations that include one 1-GbE blade and one 10-GbE blade, the maximum values for a 1-GbE blade prevail.
All MPX200 configurations must follow these P6000/EVA connectivity rules: • When using the MPX200 for iSCSI, MPX200 FC connections can be direct connect to a P6000/EVA controller host port or fabric connect through an FC switch. • Each P6000/EVA storage system can connect to a maximum of one MPX200 chassis (two blades). • Each P6000/EVA controller host port can connect to a maximum of two MPX200 FC ports.
NOTE: Communication between HP P6000 Command View and the MPX200 is not secured by the communication protocol. If this unsecured communication is a concern, HP recommends a confined or secured IP network within a data center. P6000/EVA storage system software For FCIP, the MPX200 is supported with HP P6000 Continuous Access, Business Copy, SSSU, or Replication Solutions Manager.
Figure 141 (page 340) shows an MPX200-3PAR single-blade fabric-attached configuration. This is the lowest-cost configuration and is used when high availability for iSCSI hosts is not required.
Figure 143 MPX200-3PAR multi-3PAR fabric-attached configuration IP network management (WAN/LAN) MPX200 MGMT HP StorageWorks MPX200 MGMT GE4 IOIOI GE3 FC1 1 GbE Blade MPX200 Multifunction Router FC2 FC1 GE1 FC2 GE2 GE1 IP network iSCSI data (LAN/VLAN) iSCSI NIC 3PAR storage system Fibre Channel fabric 2 Fibre Channel fabric 1 26666a MPX200 iSCSI rules and supported maximums The MPX200 chassis can be configured with one or two blades.
Table 182 MPX200-3PAR StoreServ operating system and multipath support Operating system Multipath software Citrix Xen 3PAR storage system Native MPxIO Microsoft Windows Server 2012, 2008, 2003 3PAR MPIO (Windows 2003) Microsoft MPIO DSM (Windows 2012, 2008) Oracle VM Server Native Device Mapper Linux Red Hat, SUSE Device Mapper Oracle Solaris Solaris MPxIO 3PAR StoreServ 10000 V-Class; 3PAR StoreServ 7000; 3PAR F-Class, T-Class MPX200 Multifunction Router with iSCSI for XP storage The XP24000/
Figure 145 MPX200-XP dual-blade fabric-attached configuration MPX200 blade 1 MGMT HP StorageWorks MPX200 MGMT GE4 IOIOI GE3 FC1 MGMT HP StorageWorks MPX200 1 GbE Blade MPX200 Multifunction Router FC2 FC1 GE1 FC2 GE2 MGMT GE4 IOIOI GE3 FC1 1 GbE Blade MPX200 Multifunction Router FC2 FC1 GE1 IP network management (WAN/LAN) MPX200 blade 2 GE1 FC2 GE2 iSCSI GE1 IP network iSCSI data (LAN/VLAN) XP24000/20000 storage system NIC Fibre Channel fabric 1 Fibre Channel fabric 2 26655a
• XP24000 • XP20000 All MPX200 configurations must follow these connectivity rules: • When using the MPX200 for iSCSI, MPX200 FC connections must be fabric-attached through an FC switch • Each XP storage system can connect to a maximum of one MPX200 chassis (two blades) • A maximum of one MPX200 chassis (two blades) can be zoned with up to four XP storage systems • XP and EVA storage systems can connect to the same MPX200, the total allowable number of storage systems is four per MPX200 chassis •
Figure 147 Direct connect iSCSI-Fibre Channel attachment mode configuration Discovery IP Address Presented iSCSI Targets D1 FP1B mpx100 HP StorageWorks mpx100 FP1A IP Network management (WAN/LAN) MGMT MGMT IOIOI ! FC1 FC1 FC2 FC2 GE1 GE2 GE1 IP Network iSCSI data (LAN/VLAN) D1 EVA storage system FP1 FP2 FP1 FP2 Existing Fibre Channel HA fabric 1 A B iSCSI NIC P6000 Command View Existing Fibre Channel HA fabric 2 25162c NOTE: Direct connect mode requires a dedicated host port on
Figure 149 EVA4400 direct connect iSCSI-Fibre Channel attachment mode ABM configuration Discovery IP Address Presented iSCSI Targets D1 FP2A FP2B FP2A D2 FP2B FP1A FP1B FP1A FP1B D3 D4 IP Network management (WAN/LAN) mpx100/100b 1 mpx100/100b 2 MGMT MGMT HP StorageWorks mpx100 HP StorageWorks mpx100 MGMT IOIOI MGMT IOIOI ! FC1 FC1 FC2 GE1 ! GE2 GE1 FC2 FC1 GE2 FC1 FC2 FC2 GE1 GE2 GE1 GE2 D2 D1 D4 D3 iSCSI IP Network iSCSI data (LAN/VLAN) NIC EVA4400 with ABM running P60
Figure 151 Fabric iSCSI-Fibre Channel attachment mode configuration Discovery IP Address Presented iSCSI Targets D1 FP2A IP Network management (WAN/LAN) FP2B mpx100 FP1A HP StorageWorks mpx100 FP1B MGMT MGMT IOIOI ! FC1 FC1 FC2 FC2 GE1 GE2 GE1 D1 EVA storage system FP1 FP2 FP1 FP2 IP Network iSCSI data (LAN/VLAN) Existing Fibre Channel HA fabric 1 A B iSCSI NIC P6000 Command View Existing Fibre Channel HA fabric 2 25164c Hardware support This section describes the hardware devi
Table 184 (page 348) describes the connectivity attachment mode based on the EVA storage system model.
See Figure 152 (page 349) and Figure 153 (page 349). NOTE: HP Storage mpx Manager is required for mpx100/100b management.
Figure 154 Multipath direct connect iSCSI-Fibre Channel attachment mode configuration Discovery IP Address Presented iSCSI Targets D1 FP1A D2 FP1B IP Network management (WAN/LAN) mpx100/100b 1* mpx100/100b 2 MGMT MGMT HP StorageWorks mpx100 HP StorageWorks mpx100 MGMT IOIOI MGMT IOIOI ! FC1 FC1 FC2 GE1 ! GE2 GE1 FC2 FC1 GE2 FC1 FC2 FC2 GE2 GE1 GE1 GE2 IP Network iSCSI data (LAN/VLAN) D1 D2 EVA storage system FP1 FP2 FP1 FP2 Existing Fibre Channel HA fabric 1 A B iSC
Operating systems and network interface cards The EVA and EVA4400 iSCSI options support the following operating systems, unless noted otherwise: • Apple Mac OS X • Linux—Red Hat • Linux—SUSE • Microsoft Windows 2008 Enterprise/Standard Editions; 2008 Server Core; 2003 Enterprise/Standard Editions • Microsoft Windows XP Professional Workstation • HP OpenVMS 8.
Table 185 Supported EVA iSCSI Connectivity Option maximums Description Maximum per EVA or EVA4400 iSCSI Connectivity Option Hardware EVA storage system 1 mpx100/100b 2 Configuration mpx100—150 (single-path or multipath) mpx100b (EVA4400 only)—16, 48 (license upgrade 1), 150 (license upgrade 2) (single-path or multipath) Total number of iSCSI initiators Note: The mpx100/100b can serve both single-path and multipath LUNs concurrently.
B-series iSCSI Director Blade The B-series iSCSI Director Blade (FC4-16IP) is a gateway device between Fibre Channel targets and iSCSI initiators. This allows iSCSI initiators in an IP SAN to access Fibre Channel storage in a Fibre Channel SAN. This section describes the following topics: • “Blade overview” (page 353) • “Hardware support” (page 353) • “Software support” (page 354) • “Scalability rules” (page 354) For the latest B-series documentation, see http://h18006.www1.hp.
Storage systems The following storage system is supported with the B-series iSCSI Director Blade. Contact an HP storage representative for specific support information. • XP10000/12000 NOTE: HP supports direct connection of storage systems to the Fibre Channel ports on the B-series iSCSI Director Blade, not to the IP ports. Fibre Channel switches The B-series iSCSI Director Blade is supported on the B-series SAN Director 4/256, with a maximum of four blades per chassis.
Table 187 B-series iSCSI Director Blade scalability rules Rule iSCSI sessions per port 64 Maximum 64 iSCSI ports per FC4–16IP blade 8 iSCSI blades per switch 4 iSCSI sessions per FC4–16IP blade 512 iSCSI sessions per switch 1,024 TCP connections per switch 1,024 TCP connections per iSCSI session 2 iSCSI sessions per fabric 4,096 TCP connections per fabric 4,096 iSCSI targets per fabric 4,096 CHAP entries per fabric 4,096 LUNs per iSCSI target 256 Members per discovery domain 64 Dis
Operating systems and network interface controllers The MP Router supports the following operating systems: • Microsoft Windows 2000 SP3, SP4 • Microsoft Windows 2003 Standard Server and Enterprise Editions The MP Router in iSCSI mode is compatible with all HP-supported NICs for Windows. Network Teaming MP Router iSCSI supports HP Network Teaming with Windows 2000 and Windows 2003. iSCSI initiators MP Router iSCSI supports Microsoft iSCSI initiator 1.06.
Figure 157 (page 357) shows a sample configuration where an IP module bridges an IP network and a Fibre Channel network. Figure 157 C-series Fibre Channel and IP configuration with the IP module Fibre Channel IP link ISL C-series Fibre Channel with IPS module Host 1 Host 2 IP network Fibre Channel C-series fabric Fibre Channel 25167c In addition to presenting Fibre Channel targets to iSCSI hosts, the modules also present each iSCSI host as a Fibre Channel host (in transparent mode).
Fibre Channel switches The C-series IP Storage Services Modules (IPS-4, IPS-8), 14/2 Multiprotocol Services Module, and 18/4 Multiservice Module support the HP C-series switches listed in “C-series switches and fabric rules” (page 123). Table 189 (page 358) describes the C-series switches that support iSCSI.
C-series management applications C-series management applications are as follows: • Cisco Data Center Network Manager (DCNM) • Cisco Fabric Manager • Cisco Device Manager • CLI iSCSI initiators C-series modules support these iSCSI software initiators: • Microsoft Windows iSCSI Initiator • Red Hat iSCSI bundled Initiator • Red Hat SourceForge iSCSI Initiator • SUSE iSCSI bundled Initiator • SUSE SourceForge iSCSI Initiator • IBM AIX native iSCSI Initiator • Oracle Solaris native iSCSI In
The following examples show maximum configurations for initiator/target pairs: • 500 iSCSI initiators, each connecting to one target (storage controller port) • 100 iSCSI initiators, each connecting to five targets • 50 iSCSI initiators, each connecting to eight targets and 100 iSCSI initiators, each connecting to one target The maximum of 500 TCP connections (initiator/target pairs) with 256 LUNs per connection yields 128,000 possible LUNs.
• HP ProLiant DL380 G4 Storage Server (Base, External SCSI, and External SATA models, SAN Storage model Gateway Edition only) • HP StorageWorks NAS 500s • HP StorageWorks NAS 1200s • HP StorageWorks NAS 1500s • HP StorageWorks NAS 2000s • HP StorageWorks NAS 4000s (Gateway Edition only) Application support The following host applications support the HP iSCSI Feature Pack: • Microsoft Exchange Server 2000 • Microsoft Exchange Server 2003 • Microsoft SQL Server 2000 • Microsoft SQL Server 2
• Allows delta snapshots using Microsoft VSS interface, and performs automatic delta snapshots of application hosts to reduce potential data loss. • Offers several application-specific licensed agent options: ◦ Microsoft Visual SourceSafe ◦ Microsoft Exchange ◦ Microsoft SQL ◦ Oracle Database (for a single Microsoft iSCSI initiator) Clustering Clustering is an upgrade license for the HP ProLiant Storage Server iSCSI Feature Pack (Gateway Edition only).
Exchange storage design Important criteria for Exchange storage design include: • Isolation of Exchange transaction logs from databases • Selection of optimum RAID level for performance and fault tolerance • Write-back caching for hardware RAID controller performance Separate volumes for logs and databases HP recommends separate volumes for Exchange transaction logs and databases, to ensure data protection and efficiency.
calculated from the average I/O needs an additional safety factor to maintain performance during peak periods. In practice, the maximum number of users is less than the calculated value when: • Users increase the size of their mailboxes. • Services such as antivirus scanners or content indexers are added to the Exchange server. A medium-sized user profile provides a 60 MB mailbox, and a large profile provides a 100 MB mailbox.
20 Network Attached Storage This chapter describes the HP ProLiant Storage Server family of NAS products. It describes the following topics: • “Storage server and SAN integration” (page 365) • “HP ProLiant Storage Servers” (page 366) NOTE: The HP ProLiant Storage Server family was formerly called the HP StorageWorks NAS family. Legacy NAS products use the HP StorageWorks NAS brand. For information about iSCSI NAS configurations, see “HP ProLiant Storage Server iSCSI Feature Pack support” (page 360).
HP ProLiant Storage Servers The HP ProLiant Storage Servers provide scalability, flexibility, and cost-effective management of storage resources. HP offers the following storage servers: • HP ProLiant DL380 G4 • HP ProLiant DL580 G2 • HP ProLiant DL585 NOTE: The DL380 G4 was formerly called NAS 4000s; the DL580 G2 was called NAS 9000s.
For additional information, see the following QuickSpecs: • DL380 G4: http://h18006.www1.hp.com/products/storageworks/dl380storageserver/ index.html • DL580 G2: http://h18006.www1.hp.com/products/storageworks/dl580storageserver/ specifications.html • DL585: http://h18006.www1.hp.com/products/quickspecs/11902_na/11902_na.html Fabric rules Storage servers are supported in SAN fabrics with B-series or C-series switches.
Part V Storage security, best practices, and support information The following chapters describe storage security and SAN best practices: • “Storage security” (page 369) • “Best practices” (page 383) • “Support and other resources” (page 405)
21 Storage security This chapter describes storage security best practices.
Table 191 Security attack classes (continued) Attack class Description • Use data for fraudulent purposes • Deny authorized users access Nonmalicious attacks can result from: • Carelessness • Lack of knowledge • Circumventing security for nonmalicious purposes to perform tasks Attacks due to modifications to hardware or software made at the factory or during distribution. Distribution attacks can insert malicious code in a product, which can allow future unauthorized access to the system.
5. To ensure the validity of the peer, the server sends challenge messages at random intervals and changes the CHAP identifiers frequently. IPsec IPsec uses an open-standards framework to protect data transmission over IP networks. It uses cryptographic security services.
Advanced Encryption Standard AES is a block cipher designed for use in symmetric cryptography, which encrypts data in 128-bit blocks. AES can use a key size of 128, 192, or 256 bits. The number of rounds varies by the key length (for example, 10, 12, or 14 rounds for key sizes 128, 192, or 256, respectively). The processing in each round is more efficient than DES and is better suited to high-speed parallel operations.
the use of dial-in modems). Access control is a set of controls: confidentiality, integrity, availability, and limiting access to network resources. These depend on the successful prevention of unauthorized access to services or information.
Nonrepudiation Nonrepudiation ensures that all parties in a transaction are authenticated and verifies that they participated in the transaction. Storage technologies are tied closely with data and are often the last line of defense against attacks. Security validation Security validation establishes a secure audit trail across your organization. The audit trail serves as proof of compliance for internal and external audits with real-time alerts.
• Storage network—Consists of switches, appliances, and cables. Switches and appliances come with support to protect themselves. The storage network components support key management, encryption services, and authentication of server and storage arrays. • Servers—Consists of hardware, operating systems, interface cards (NICs and HBAs), and applications (also known as hosts). Each component comes with support for protecting itself. The interfaces cards support authentication and secure tunnel.
Hardware requirements SME requires a minimum of one MDS 9222i switch or one MSM-18/4 module in each cluster. The SME engines on the switch or module provide transparent encryption and compression to hosts and storage devices. A smart card reader is required to take advantage of all of the standard and advanced security levels. Software requirements Table 193 (page 376) lists the software requirements for switches and modules in the SME cluster.
Port security C-series port security features prevent unauthorized access to a switch port by: • Rejecting login requests from unauthorized Fibre Channel devices or switches • Reporting all intrusion attempts to the SAN administrator through system messages • Using the CFS infrastructure for configuration, distribution, and restricting it to CFS-enabled switches Fabric binding C-series switches in a fabric binding configuration ensure that ISLs are enabled between authorized switches only.
• Integration with HP Secure Key Manager, providing secure and automated key sharing between multiple sites to ensure transparent access to encrypted data • Industry-standard AES 256-bit encryption algorithms for disk arrays on a single security platform for SAN environments • Frame Redirection technology that enables easy, nonintrusive deployment of fabric-based security services • Plug-in encryption services available to all heterogeneous servers, including virtual machines, in data center fabrics
Fabric OS uses RBAC to determine which commands are supported for each user. Secure Shell Fabric OS supports SSH encrypted sessions to ensure security. SSH encrypts all messages, including client transmission of passwords during login. SSH includes a daemon (sshd), which runs on the switch and supports many encryption algorithms, such as Blowfish-CBC and AES. Commands that require a secure login channel must be issued from an original SSH session.
IPFilter policy The B-series IPFilter policy applies a set of rules to IP management interfaces as a packet filtering firewall. The firewall permits or denies traffic through the IP management interfaces according to policy rules. Consider the following when setting IPFilter policies: • Fabric OS supports multiple IPFilter policies, which can be defined at the same time. Each policy is identified by name and has an associated IPFilter type (IPv4 or IPv6). Do not mix IPFilter and IP address types.
• In the default configuration, FCAP authentication is tried first, then DHCHAP authentication. Each switch can be configured to negotiate one or both types. • The Authentication policy is designed to accommodate mixed fabric environments that include switches running Fabric OS 5.3.0 (and earlier). • When the Authorization policy is activated, you cannot implement a B-series Secure Fabric OS environment.
• • • Centralized encryption key management for HP LT04 tape libraries ◦ Automatic policy-based key generation and management supporting key and cartridge granularity ◦ ISV transparent key archival and retrieval for multiple libraries ◦ Extensible to emerging open standards Strong auditable security for encryption keys to ensure compliance ◦ Hardened server appliance ◦ Secure identity-based access, administration, and logging ◦ Designed for FIPS 140-2 validation Reliable lifetime key archiv
22 Best practices This chapter describes HP best practices for SAN design and implementation.
A complete design specification includes the following elements: • Topology map—Shows the logical SAN topology and fabric interconnect scheme; describes a strategy to accommodate expansion and technological advances • Configuration layout—Shows the physical layout of components; use for troubleshooting and to verify the correct connectivity • Storage map—Defines the storage system configuration and settings, such as host LUN allocation and RAID levels • Zoning map—Defines the communication access set
Data access patterns Review your data access needs before making a topology choice.
• Cable dressing Use care when routing fiber optic cable and ensure that cables conform to the minimum bend radius requirements. See “Rules for fiber optic cable connections ” (page 153). Use hook-and-loop (such as Velcro brand) tie wraps to group and support the cables. CAUTION: • Plastic tie wraps can damage the internal fiber core if over-tightened. Cable symmetry When connecting cables, use similar slot and port numbers. For example, connect HBA 1 to SAN fabric 1, HBA 2 to SAN fabric 2, and so on.
Zoning This section describes configuration recommendations for: • “Zoning enforcement” (page 387) • “Zoning guidelines” (page 387) • “EBS zoning” (page 389) • “Zone naming” (page 389) Zoning enforcement To protect against unauthorized access, Fibre Channel switches provide three types of zoning enforcement (listed here in order of enforcement): • Access authorization Access authorization provides frame-level access control in hardware and verifies the SID-DID combination of each frame.
• Application • Port allocation Zoning by operating system Zoning by operating system is the minimal required zoning method. This method allows multiple HBAs with the same operating system to be grouped with the accessed storage ports. Zoning by operating system prevents the interaction of HBAs with incompatible operating systems. This method limits the number of zones in a fabric. A large zone can be divided into multiple zones within the operating system type.
Zoning by application Zoning by application configures multiple, sometimes incompatible, operating systems into the same zones. This method allows the potential for disruptions among servers, such as a web server disrupting a data warehouse server. A zone with a large number of members is susceptible to more administrative errors, such as distribution of RSCNs to a larger group than necessary.
RING_1 and Ring_1 are distinct switch identifiers. Server naming Servers are identified by the WWN of the HBA. For server aliases, use the operating system name and the HBA number. For example, for server WIN01 with one HBA, define the alias as WIN01_HBA01; for the second HBA, define the alias as WIN01_HBA02. Storage system naming Fibre Channel storage systems have a unique WWN for each controller port. When implementing multiple fabrics, different ports are configured in each fabric.
1. Create 3 VLANs (for LAN, SAN, and SAN discovery traffic). system-view [switchname] vlan 1001 [switchname-vlan1001] description ToLAN [switchname-vlan1001] quit [switchname] vlan 4001 [switchname-vlan4001] description ToSAN [switchname-vlan4001] quit [switchname] vlan 3001 [switchname-vlan3001] description FIPVLAN [switchname-vlan3001] protocol-vlan 0 mode ethernetii etype 8914 [switchname-vlan3001] quit [switchname] 2. Configure DCBX.
[switchname-interface Ten-GigabitEthernet1/0/1] unicast-suppression 1 [switchname-interface Ten-GigabitEthernet1/0/1] quit • Network (No SAN Access) Interfaces [switchname] interface Ten-GigabitEthernet1/0/14 [switchname-interface Ten-GigabitEthernet1/0/14] [switchname-interface Ten-GigabitEthernet1/0/14] [switchname-interface Ten-GigabitEthernet1/0/14] [switchname-interface Ten-GigabitEthernet1/0/14] [switchname-interface Ten-GigabitEthernet1/0/14] • link-type trunk trunk permit vlan 1001 trunk pvid vl
2408 FCoE Converged Network Switch and DC SAN Director Switch 10/24 FCoE Blade quick setup This procedure is intended for users who are familiar with Brocade FC switches and have experience merging B-series FC switches into an existing FC fabric. Use this procedure to enable servers with CNAs attached to the 2408 FCoE Converged Network Switch or the DC SAN Director Switch 10/24 FCoE Blade to access devices on the attached B-series FC fabric.
switch(config)# exit switch# copy running-config startup-config Overwrite the startup config file (y/n): y Building configuration... switch# 9. Verify that the CEE port link status and VLAN status are correct.
10. Verify the status of the FC and FCoE virtual FC ports. BR8000-01:admin> switchshow switchName: BR8000-1 switchType: 76.
IMPORTANT: If you are not familiar with Cisco FC switches or you do not have experience merging C-series FC switches into an existing FC fabric, use the detailed instructions found in the switch user guide to set up your switch. HP recommends that you use the VFC port assignments listed in Table 195 (page 396).
To establish CNA connectivity and enable login to the HP C-series Nexus 5000 Converged Network Switch, configure the IEEE DCB ports as follows: 1. Enable FCoE (disabled by default). NOTE: The C-series Nexus 5000 Converged Network Switch will require a reload (reboot).
Nexus5010(config-if-range)# interface vfc 1-20 Nexus5010(config-if-range)# exit 1 This command allows the port to access the FCoE VLAN (VLAN 200 in this example). For non-FCoE ports, you can omit the FCoE VLAN from this command; however, both FCoE and non-FCoE ports might require access to other VLANs. 4. Create a new VSAN that includes the FC and VFC ports. By default, all ports are in VSAN 1. HP recommends that you use a different VSAN for SAN connectivity.
Example 1 Creating and binding consecutive VFC ports Nexus5010# configure terminal Nexus5010(config)# interface vfc 1 Nexus5010(config-if)# bind interface Nexus5010(config-if)# exit Nexus5010(config)# interface vfc 2 Nexus5010(config-if)# bind interface Nexus5010(config-if)# exit Nexus5010(config)# interface vfc 3 Nexus5010(config-if)# bind interface Nexus5010(config-if)# exit Nexus5010(config)# interface vfc 4 Nexus5010(config-if)# bind interface Nexus5010(config-if)# exit Nexus5010(config)# interface vfc
Example 2 Creating and binding nonconsecutive VFC ports Nexus5020# configure terminal Nexus5020(config)# interface vfc 1 Nexus5020(config-if)# bind interface ethernet Nexus5020(config-if)# exit Nexus5020(config)# interface vfc 2 Nexus5020(config-if)# bind interface ethernet Nexus5020(config-if)# exit Nexus5020(config)# interface vfc 3 Nexus5020(config-if)# bind interface ethernet Nexus5020(config-if)# exit Nexus5020(config)# interface vfc 4 Nexus5020(config-if)# bind interface ethernet Nexus5020(config-if)#
Nexus5010# copy running-config startup-config [########################################] 100% 9. Copy the running configuration to a backup location. Nexus5010# copy running-config ftp://10.10.20.1/backup.txt 10. Verify the configuration. Nexus5010# show interface brief Nexus5010# show running-config SAN scaling When you expand a topology, avoid making changes that disrupt the original design goals. If data access requirements have changed, consider migrating to a topology that meets the current needs.
Ring fabric expansion Expand a ring fabric by adding a switch to the ring. Add new switches cascaded off the ring, up to the maximum number of switches supported in a single fabric. When expanding outside the ring, ensure that communicating devices are connected by no more than seven hops. Core-edge fabric expansion Expand a core-edge SAN fabric by adding edge switches. Connect edge switches to available ports on the backbone switches. If the current SAN contains only one core switch, add another.
Fabric segmentation errors The following errors can cause fabric segmentation: • Zone type mismatch The name of a zone object in one fabric is identical to the name of a different type of zone object in the other fabric. For example, an object name on fabric A must not be an alias or configuration name in fabric B; otherwise, the fabrics cannot merge. • Zone content mismatch The definition of a zone object in one fabric is different from its definition in the other fabric.
In the following procedure, the SAN consists of fabric A and a redundant fabric B. Each of these fabrics is merged with a SAN consisting of fabrics C and D. 1. Identify and resolve any issues that can cause fabric segmentation. 2. Verify that each fabric provides a redundant path to all attached devices. 3. Verify that paths are open to each device that must remain online during the merge. 4. Select fabrics for merging, for example, fabric A with fabric C. 5.
23 Support and other resources Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Related information Table 196 Related documentation Topic Information source For the latest information on B-series, C-series, and H-series switches and firmware versions, see the SAN Infrastructure website: Switches http://h18006.www1.hp.com/storage/saninfrastructure.html • HP StorageWorks Fabric Interoperability: Merging Fabrics Based on C-series and B-series Fibre Channel Switches Application Notes Fabric interoperability See this document on the SAN Infrastructure website: http://h18006.www1.hp.
IMPORTANT: NOTE: TIP: Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts. Customer self repair HP CSR programs allow you to repair your HP product. If a CSR part needs replacing, HP ships the part directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your HP-authorized service provider will determine whether a repair can be accomplished by CSR.
24 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Glossary This glossary defines acronyms and terms used in this guide and is not a comprehensive glossary of computer terms. Symbols 3DC Three Data Center. A storage configuration that uses XP storage systems. 3PO Third-party option. A AAA Authentication, Authorization, and Accounting. A security protocol. ABM Array-based management. access authorization A fabric security method that provides frame-level access control in hardware and verifies the SID-DID combination of each frame.
CNA Converged Network Adapter. controller pair Two connected controller modules that control a disk array. CWDM Coarse wavelength division multiplexing. The technique of placing more than one optical signal on a single optical cable simultaneously. See also WDM. D DA Directory agent. An iSCSI software component. DAS Direct-attached storage. DCB Data Center Bridging (Cisco). DCBX Data Center Bridging Exchange Protocol. DCC Device Connection Control.
EVA4x00/6x00/8x00 EVA4100/4400/6100/6400/8100/8400 F fabric A network of one or more Fibre Channel switches that transmit data between any two N_Ports on any of the switches. failover An automatic method for transferring operations from a failed system to a secondary, identical system. Fat tree topology A SAN topology where at least 50% of edge ports are dedicated as ISLs. FC Fibre Channel.
GBIC Gigabit interface converter. A hardware module that connects fiber optic cables to a device and converts electrical signals to optical signals. GLM Gigabit link module. A 1 Gb/s fiber optic transceiver. GPS General-purpose server. H H-series Fibre Channel switches manufactured for HP by QLogic. HA High availability. The relative ability of a system to operate continuously, regardless of the type of failure. HACMP/ES High Availability Cluster Multiprocessing/Enhanced Scalability.
iSCSI Internet Small Computer System Interface. A standard protocol that uses SCSI commands to transfer data over IP networks. ISID Initiator session ID. ISL Interswitch link. A connection from an E-port on one switch to an E-port on another switch. iSNS Internet Storage Name Service. An iSCSI client-server discovery protocol. IVR Inter-VSAN routing. A C-series topology that provides selective Fibre Channel routing connectivity between devices in different VSANs. L LAG Link aggregation group.
out-of-band communication Communication through a different communications channel than that used by operational data. oversubscription When transmissions from one or more devices exceed the capacity of an ISL or port. P PAP Password Authentication Protocol. A security protocol. PCM Power and control modules. PDC Processor-Dependent Code. PDU Protocol data unit. PFC Priority flow control. PIC Plug-in card. A hardware component of the HP NonStop server. PKI Public key infrastructure.
SCM HP SAN Connection Manager. Comprehensive management software for H-series switches. SCP Secure Copy. A B-series feature used to securely transfer files between systems. SFF Small form factor. Used to describe a type of drive cage. SFP Small form-factor pluggable transceiver. SFP+ Small form-factor pluggable, plus transceiver. SFTP Secured File Transfer Protocol. A C-series security feature. SID Source ID.
TR Transparent router. A routed fabric feature that provides inter-fabric routing, allowing controlled and limited access between devices on an H-series switch (local) fabric and devices on a remote fabric of other vendor switches. TSID Target session ID. U UA User Agent. An iSCSI software component. unified fabric IEEE DCB enabled network (Cisco). V VAR Value-added reseller. VC-Enet Virtual Connect Ethernet. A hardware component of HP Virtual Connect. VC-FC Virtual Connect Fibre Channel.
Index Symbols 3PAR see 3PAR configuration rules, 250 data migration, 251 heterogeneous SAN support, 249 storage management server integration, 254 storage rules, 249 zoning, 254 3PAR persistent ports, zoning method, 388 3PAR storage systems tape storage system support, 254 A access authorization, hard zoning enforcement, 387 Access Gateway mode B-series switches, 95 c-Class BladeSystem, 170 configuration example, 170 considerations, 171 encryption, 97 failover and failback policies, 171 guidelines, 172 act
supported blade servers, 167 Virtual Connect, 169 c-Class BladeSystem server environment supported switches, 167 C-series features IVR, 36 VSANS with IVR, 36 C-series Fibre Channel and FCoE switches overview, 123 C-series switches capabilities, 123 dividing, 48 extended fabric settings, 265 fabric rules, 136 features, 132 iSCSI, 356 ISL maximums, 137 maximum topology, 34 MDS 9216i, IPS-4 IP Storage Services modules, IPS-8, and 14/2 services modules, 294 models, 126 routing, 50 SAN extension, 258 switching m
data availability design considerations, 40 factors affecting, 38 level 1, 38 level 2, 38 level 3, 39 level 4, 39 NSPOF, 39 SAN, 38 security, 373 Data Center Fabric Manager see DCFM data encryption standard, 371 data integrity, 373 data migration, 268 3PAR, 251 HP P9000, 239 data protection HP SVSP, 242 data provisioning HP SVSP, 242 data replication HP SVSP, 242 database size, B-series switches, 106 DC Dir Switch MP Extension Blade, 287 DCFM B-series switches, 96 DES, 371 design considerations congestion,
FC-SONET gateway, 270 FC-SP, 371 FC-to-ATM, 272 FC4-16IP see B-series iSCSI Director Blade FCIP B-series switches, 97 managing bandwidth, 268 protocol, 266 routing, 58 third-party QoS products, 270 FCIP extension, Fibre Channel distance rules, 160 FCoE described, 62 end-to-end solution, 62 fabric-edge solution, 62 HP products, 63 HP solutions, 62 technology, 63 FCoE SAN fabrics, 24 FCoE switches C-series, 84 high-availability feature comparison, 87 C-series expansion modules, 85 C-series fabric rules, 87 C-
SAN Virtualization Services Platform, 242 standard SAN designs, 20 technical support, 405 HP IP Distance Gateway, 273 HP MPX200 Multifunction Router see MPX200 HP OpenVMS B-series Fibre Channel switch fabric rules, 103 C-series Fibre Channel switch fabric rules, 136 configuration rules, 193 host-based volume shadowing, 194, 316 multipathing coexistence support, 194 SAN rules, 193 supported storage systems, 193 HP P6000 Command View MPX200 support, 338 HP P6000 Continuous Access SAN extension best practices,
basic configuration, 47 overview, 36 K key management, 372 L labels cable, 385 HBA, 385 latency SAN, 162 level 4 high availability, EVA, 231 Linux B-series Fibre Channel switch fabric rules, 103 C-series Fibre Channel switch fabric rules, 136 configuration rules, 200 H-series Fibre Channel Switch fabric rules, 145 multipathing coexistence support, 201 Red Hat supported storage systems, 199 SAN rules, 199 SUSE supported storage systems, 199 login authentication, soft-plus zoning enforcement, 387 LSAN, 35,
iSCSI rules, 336 management rules, 338 multipath software, 339 switch support, 339 using iSCSI, 333 with FCIP, 282 with HP P6000 Command View, 338 with P6000/EVA, 337 MSA2000i and MSA2000i G2, 326 multi-protocol long-distance technology, 266 multipath software MPX200, 339 multipathing coexistence support HP OpenVMS, 194 HP Tru64 UNIX, 196 HP-UX, 192 IBM AIX, 199 Linux, 201 Microsoft Windows, 203 Oracle Solaris, 206 N N_Port Virtualization mode, 172 N_Port_ID_Virtualization HBA NPIV, 177 NAS configuration a
QuickLoop, interconnect, 152 R recommendations SAN best practices, 383 SAN designs, 20 record keeping, connections, 385 Red Hat Linux C-series Fibre Channel switch fabric rules, 136 redundancy, routing, 51 redundant active components B-series Fibre Channel switches, 99 redundant control processor B-series Fibre Channel switches, 99 regulations security, 370 related documentation, 406 ring fabric benefits, 29 expansion, 402 migrating from, 42 uses, 27 ring fabric SAN overview, 27 routed fabric topologies, 3
maximums, 33 meshed fabric, 26 migration, 21 oversubscription, 20 performance workload, 22 ring fabric, 27 scalability, 21 single-switch, 24 SAN Virtualization Services Platform, 242 satellite switch support, 28 scalability migration, 41 MP Router, 118 scaling nondisruptive methods, 401 routing, 46 switch, 45 Secure Fabric OS B-series switches, 97 security AES, 371 attack classes, 369 best practices, 369 CHAP, 370 compliance, 370 confidentiality, 373 data availability, 373 data integrity, 373 data protectio
FCoE CN, 84 for cascaded fabric, 26 for core-edge fabric, 32 for meshed fabric, 27 for Meta SAN, 35 for ring fabric, 29 for single-switch fabric, 24 for VSAN, 36 H-series switches, 141 H-series switches with TR, 37 MPX200 support, 339 switch name, configuration settings, 403 switch settings B-series default, 102 H-series switches, 144 switches mismatched parameters, 403 port covers, 385 third-party, 162 symbols in text, 406 Synchronous Optical Network, 270 overview, 169 VC-FC, 169 virtual disk, 242 virtual
P9000/XP storage systems, 237 zoning enforcement B-series Fibre Channel switches, 120 C-series Fibre Channel switches, 138 H-series switches, 149 zoning method 3PAR persistent ports, 388 HBA port, 388 NPIV port, 388 zoning methods application, 389 HBA, 388 operating system, 388 port allocation, 389 427
