Download Print this page

HP StorageWorks 4000/6000/8000 - Enterprise Virtual Arrays Reference Manual

San design
Hide thumbs

Advertisement

Table of Contents
HP StorageWorks
SAN Design Reference Guide
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.
Part number: AA-RWPYF-TE
Fifty-third edition: February 16, 2010

Advertisement

Table of Contents
loading

  Also See for HP StorageWorks 4000/6000/8000 - Enterprise Virtual Arrays

  Related Manuals for HP StorageWorks 4000/6000/8000 - Enterprise Virtual Arrays

  Summary of Contents for HP StorageWorks 4000/6000/8000 - Enterprise Virtual Arrays

  • Page 1 HP StorageWorks SAN Design Reference Guide 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. Part number: AA-RWPYF-TE Fifty-third edition: February 16, 2010...
  • Page 2 Legal and notice information © Copyright 2001-2010 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.
  • Page 3: Table Of Contents

    Contents I ..Architecture ..................25 1 SAN design overview ..............27 SAN solutions ........................27 HP SAN implementations ....................28 SAN components ....................... 29 Fibre Channel technology ....................29 Storage area networks ......................29 SAN infrastructure ......................30 Fabrics ........................30 SAN scaling .......................
  • Page 4 B-series Virtual Fabrics with IFR ..................50 C-series VSANs with IVR ....................51 H-series switches with TR ....................51 FCoE fabric topologies ......................52 Data availability ........................ 53 Levels ......................... 54 Considerations ......................56 Topology migration ......................58 Nondisruptive migration ....................58 Migrating a cascaded fabric SAN .................
  • Page 5 Fabric rules for H-series switches with TR ................. 88 Zoning limits and enforcement ..................90 5 B-series switches and fabric rules ........... 93 B-series Fibre Channel switches, 1606 Extension SAN Switches, and MP Routers ......93 Model numbering ......................94 Model naming ......................
  • Page 6 Model naming ......................158 Switch models ......................158 Features ........................159 Usage ........................160 Fibre Channel fabric rules ....................161 Operating systems and storage products ............... 162 Fabric rules for M-series switches .................. 162 ISL maximums ......................163 Zoning limits and enforcement ..................165 8 SAN fabric connectivity and switch interoperability rules ....
  • Page 7 IBM AIX SAN rules ......................220 Linux SAN rules ....................... 222 Linux multipathing coexistence support ................. 222 Microsoft Windows SAN rules ................... 223 Novell NetWare SAN rules ....................225 Sun Solaris SAN rules ....................... 227 VMware ESX SAN rules ....................230 VMware ESX multipathing coexistence support ..............
  • Page 8 EVA SAN boot support ..................... 256 Storage management server integration ................256 Cabling .......................... 258 Level 4 NSPOF configuration ..................258 Dual-channel HBA configurations ................. 261 12 XP and VA storage system rules ..........263 XP and VA storage systems ....................263 Heterogeneous SAN support ..................
  • Page 9 FCIP bandwidth considerations ................293 FCIP gateways ....................295 Third-party QoS and data encryption FCIP products ..........296 Fibre Channel over SONET ..................296 FC-SONET IP link configurations ................296 FC-SONET network considerations ................. 297 Third-party SONET gateways ................297 Fibre Channel over ATM .....................
  • Page 10 Bridging and routing ....................359 iSCSI boot ........................ 360 iSCSI storage network requirements ..................360 MPX200 Multifunction Router with iSCSI ................360 MPX200 simultaneous operation .................. 360 MPX200 configuration options ..................361 MPX200 iSCSI rules and supported maximums ............. 364 EVA storage system rules and guidelines ..............
  • Page 11 B-series MP Router and iSCSI ..................... 382 Hardware support ...................... 383 Fibre Channel switches ..................383 Storage systems ....................383 Software support ....................... 383 Operating systems and network interface controllers ..........383 Network Teaming ....................383 iSCSI initiators ....................383 Configuration rules .....................
  • Page 12 Storage security compliance ....................402 Security technologies ......................402 IP SAN security technologies ..................403 Fibre Channel SAN security technologies ..............403 Encryption security technologies ................... 403 Key management ....................... 404 Organizational security policies ................... 404 HP security strategy ......................404 HP Secure Advantage ....................
  • Page 13 SAN scaling ........................424 Cascaded fabric expansion ..................425 Meshed fabric expansion .................... 425 Ring fabric expansion ....................425 Core-edge fabric expansion ..................425 SAN fabric merging ......................425 Fabric segmentation errors ..................426 Switch configuration parameters .................. 426 Independent fabric merge ................... 427 High-availability redundant fabric merge ..............
  • Page 14 Figures Single-switch fabric ....................36 Cascaded fabric ..................... 38 Meshed fabric ......................39 ISL connections in a meshed fabric ................40 Ring fabric ......................41 Ring fabric with satellite switches ................42 Core-edge fabric (typical depiction) ................43 Core-edge fabric (hierarchical depiction) ..............43 Core-edge fabric (4 x 12) ..................
  • Page 15 High-availability 1606 Extension SAN Switch configurations ........74 High-availability MP Router configurations ..............75 1606 Extension SAN Switch or MP Router consolidating SAN islands ......76 NSPOF configuration with 1606 Extension SAN Switch providing Fibre Channel routing and FCIP with direct connect devices ................. 77 NSPOF configuration with 400 MP Router providing Fibre Channel routing and FCIP ..
  • Page 16 SAN IOAME configuration (two cascaded switches) with logical and physical redundancy for XP storage systems ................... 209 SAN VIO configuration (two cascaded switches) with logical and physical redundancy for XP storage systems (NS1000, NS14000) ............210 SAN CLIM configuration (two cascaded switches) with logical and physical redundancy for XP storage systems ...................
  • Page 17 HP Continuous Access EVA 3-site configuration with eight gateways ......306 HP Continuous Access EVA 3-site configuration with six mpx110 gateways, full peer-to-peer connectivity ......................307 MPX200 basic FCIP configuration with one or two long-distance links ......310 MPX200 FCIP with B-series Integrated Routing ............310 MPX200 high-availability configuration with one or two long-distance links ....
  • Page 18 MPX200 single-blade direct connect to one EVA configuration ........364 MPX200 dual-blade direct connect to two EVA configuration ........364 Direct connect iSCSI-Fibre Channel attachment mode configuration ......368 EVA4400 direct connect iSCSI-Fibre Channel attachment mode configuration ....368 EVA8000/8100 mpx100 and Windows host direct connect configuration ....369 Fabric iSCSI-Fibre Channel attachment mode configuration .........
  • Page 19 Tables Core-edge fabric topology types ................44 Recommended core-edge fabric ISL ratios ..............44 Data access performance by SAN fabric topology ............46 H-series switch and port topology maximums .............. 47 B-series switch and port topology maximums ............. 47 C-series switch and port topology maximums .............. 48 M-series switch and port topology maximums ............
  • Page 20 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 5.x/6.x ..119 MP Router fabric rules .................... 121 MP Router scalability rules ..................125 Zoning enforcement for B-series Fibre Channel switches and MP Router LSANs ....
  • Page 21 M-series fabric rules ....................162 ISL maximums ....................... 164 M-series and McDATA zoning limits ................. 165 Zoning enforcement for M-series and McDATA switches ..........165 Rules for fiber optic cable connections ..............168 8 Gb/s fiber optic cable loss budgets (nominal bandwidth) ........169 8 Gb/s fiber optic cable loss budgets (higher bandwidth) ..........
  • Page 22 Apple Mac OS X SAN configuration rules ..............219 IBM AIX SAN configuration rules ................220 IBM AIX multipathing coexistence support ..............221 Linux SAN configuration rules ................. 222 Microsoft Windows SAN configuration rules ............. 223 Microsoft Windows multipathing coexistence support ..........224 NetWare SAN configuration rules ................
  • Page 23 Long-wave transceiver distances ................283 WDM system architectures ..................284 Port protocol setting based on the extension architecture ..........288 C-series switch extended fabric settings ..............288 M-series switch extended fabric settings ..............289 FCIP network consideration ..................293 HP FCIP gateways ....................295 FCIP QoS products ....................
  • Page 24 XP Continuous Access direct storage-to-storage distances ........... 340 XP Continuous Access Fibre Channel distances ............341 XP Continuous Access ESCON director and repeater distances ........342 XP Continuous Access WDM distances and equipment ..........343 XP Continuous Access ATM and SONET/SDH products ..........345 Network requirements for long-distance IP gateways with XP Continuous Access ....
  • Page 25: I ..Architecture

    Part I. Architecture SAN architecture is presented in these chapters: SAN design overview, page 27 SAN fabric topologies, page 35 Fibre Channel routing, page 61...
  • Page 27: San Design Overview

    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 StorageWorks SAN architecture provides open network storage solutions for all sizes and types of businesses, including small-to-medium-sized IT departments and enterprise environments.
  • Page 28: Hp San Implementations

    Cost savings SAN total cost of ownership is typically less than DAS. The business realizes a higher return on investment because sharing storage among servers utilizes capacity more efficiently, and expenses for backup hardware are reduced. Increased system availability can help prevent costly downtime and lost data.
  • Page 29: San Components

    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.
  • Page 30: San Infrastructure

    against hardware failure, high-availability topologies connect redundant systems. You can connect a complex and extensible network across long distances by choosing the required topology and appropriate components, and then connecting devices with fiber optic cable. 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.
  • Page 31: Fibre Channel Switches

    Fibre Channel switches A switch is identified by its function in a SAN: Core (or director)—Provides ISLs for any-to-any connectivity Edge (or fabric or SAN)—Provides user ports for connecting servers and storage systems For some switches, the model name (for example, HP StorageWorks Core Switch 2/64) indicates its intended use in a SAN.
  • Page 32: Design Considerations

    Recommended SAN solutions and conventions, see “Best practices” on page 417. Design considerations To design or modify a SAN, evaluate the following: Geographic layout The locations of campuses, buildings, servers, and storage systems determine the required SAN connections. SAN infrastructure components support long-distance connections and multiple interswitch cable segments.
  • Page 33 For information about disaster tolerance and failover protection, see “SAN extension” on page 279. 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: “H-series switches and fabric rules”...
  • Page 34 SAN design overview...
  • Page 35: San Fabric Topologies

    2 SAN fabric topologies This chapter discusses HP standard SAN fabric topologies. It describes the following topics: Fabric topologies, page 35 Routed SAN fabrics, page 36 FCoE SAN fabrics, page 36 Single-switch fabric, page 36 Cascaded fabric, page 37 Meshed fabric, page 39 Ring fabric, page 40...
  • Page 36: Routed San Fabrics

    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” on page 49 “C-series VSANs with IVR”...
  • Page 37: Switch Models

    Switch models For a small, single-switch SAN fabric, use the SN6000 Fibre Channel Switch; the 8/20q Fibre Channel Switch (or the HP Simple SAN Connectivity Kit); or an HP SAN, Fabric, or Edge switch (4, 8, 16, or 20 ports). For a larger single-switch SAN fabric, use a SAN, Fabric, or Edge switch (32 to 40 ports), or a Core or Director switch (64 to 240 ports), which have higher port counts.
  • Page 38: Switch Models

    25090a Figure 2 Cascaded fabric 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.
  • Page 39: Meshed Fabric

    Ease of scalability for increased server and storage connectivity Shared backup and management support Optimum local performance when communicating devices are connected to the same switch in the cascaded fabric Cost efficiency due to the large number of switch ports available Support for local data access and occasional centralized data access Meshed fabric A meshed fabric is a group of interconnected switches using multiple ISLs for fabric resiliency...
  • Page 40: Switch Models

    25092a Figure 4 ISL connections in a meshed fabric Switch models All HP Fibre Channel switches are supported for use in a meshed fabric topology. Meshed fabric topologies typically use the SN6000 Fibre Channel Switch; the 8/20q Fibre Channel Switch (or the HP Simple SAN Connectivity Kit);...
  • Page 41 NOTE: HP does not recommend the ring fabric for applications requiring many-to-many connectivity. 25093a Figure 5 Ring fabric 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).
  • Page 42: Switch Models

    25094a Figure 6 Ring fabric with satellite switches 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);...
  • Page 43: Core-Edge Fabric Types

    25095a Figure 7 Core-edge fabric (typical depiction) Core-edge fabric topologies are typically depicted as shown in Figure 7, but can also be depicted hierarchically as shown in Figure 8. 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.
  • Page 44: Core-Edge Fabric Topology Types

    Fat and skinny trees There are two core-edge fabric topology types: fat tree and skinny tree. Table 1 describes fat and skinny trees. 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.
  • Page 45: Switch Models

    For example, a 4 x 24 core-edge fabric indicates 4 core switches and 24 edge switches, for a total of 28 switches. Figure 9 shows a 4 x 12 core-edge fabric with 4 core switches and 12 edge switches, each connected to the core with 4 ISLs.
  • Page 46: Topology Data Access

    Topology data access To choose a SAN fabric topology, you must determine which data access type is appropriate for your environment. The data access types are as follows: Local (one-to-one)—Data access between a local server and a storage system connected to the same switch Centralized (many-to-one)—Data access between multiple, dispersed servers and one centrally located storage system...
  • Page 47: H-Series Switches

    H-series switches Table 4 lists the H-series switch and port maximums for specific topologies. For large fabrics, the number of user ports is determined by use of SN6000 Fibre Channel Switches and making maximum use of their dedicated 10Gb/20Gb stacking port ISLs, which leaves more of the 8 Gb ports available for device connections.
  • Page 48: C-Series Switches

    C-series switches Table 6 lists the C-series switch and port maximums for specific fabric topologies. Table 6 C-series switch and port topology maximums Number of Total number of SAN topology switches ports Number of user ports Single-switch fabric 3,500 Cascaded fabric (cascaded with 12 Director switches and 10 Fabric switches) 4,000...
  • Page 49: B-Series Meta San

    B-series Meta SAN—Implemented in certain 8 Gb/s switch models with license enabled integrated Fibre Channel routing or using the B-series 1606 Extension SAN Switch, DC Dir Switch MP Exten- sion Blade, 400 Multi-protocol Router (400 MP Router), Multi-protocol Router Blade (MP Router Blade), or Multi-protocol Router (MP Router), which provide selective Fibre Channel routing con- nectivity between multiple B-series fabrics or between B-series and M-series fabrics.
  • Page 50: B-Series Virtual Fabrics With Ifr

    NOTE: Virtual Fabrics and Administrative Domains are mutually exclusive; they cannot run on the switch simultaneously. To use Administrative Domains, you must first disable Virtual Fabrics; to use Virtual Fabrics, you must first delete all administrative domains. Switch models and fabric topologies HP supports Meta SANs with all B-series switches in either HP standard or customized topologies.
  • Page 51: C-Series Vsans With Ivr

    C-series VSANs with IVR VSANs are groups of switch ports from one or more C-series switches. Each VSAN has a unique set of fabric services. Different fabric settings can be applied to each VSAN. This provides a high level of isolation between VSANs. This isolation can be viewed as individual Fibre Channel subnetworks within a C-series fabric.
  • Page 52: Fcoe Fabric Topologies

    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 consolidation Provides centralized backup for multiple fabrics FCoE fabric topologies FCoE technology allows you to converge Ethernet and Fibre Channel technology at the server, providing significant cable, adapter, and switch consolidation.
  • Page 53: Data Availability

    FC attached FC attached HP storage HP storage Fabric B connections connections B-series B-series B-series FCoE FCoE B-series blade blade CN switch CN switch Fabric A 10 GbE Converged Converged 10 GbE CNA 10 GbE CNA connections connections IP network Server Server Server...
  • Page 54: Levels

    Hardware redundancy NOTE: For more information about high-availability configurations when using the HP B-series MP Routers or C-series VSANs, see “High-availability MP Router configurations” on page 74. Several factors affect SAN data availability: Application software Server operating systems Server hardware SAN fabric infrastructure Primary and secondary storage Number of switches...
  • Page 55: Level 2: Single Resilient Fabric

    25099a Figure 13 Level 2: single resilient fabric 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 14).
  • Page 56: Considerations

    Level 4: multiple fabrics and device paths (NSPOF) Level 4 provides multiple data paths between servers and storage systems, but unlike level 3, the paths connect to physically separate fabrics (Figure 15). This level ensures the highest availability with NSPOF protection. If a switch, server HBA, or storage system path failure occurs, data is automatically rerouted through the alternate fabric and there is no interruption in server I/O activity.
  • Page 57: Fabric Design Data Availability

    Table 8 indicates data availability and supported topologies for each level. Table 8 Fabric design data availability Fabric design Availability level SAN topologies Level 1: single connectivity fabric Single switch or multiple switches with single No redundancy Level 2: single resilient fabric Cascaded with two ISLs, meshed, ring, and Medium core-edge...
  • Page 58: Topology Migration

    Topology migration To increase SAN connectivity and capacity: Increase the number of switches. Use switches with more ports. Implement multiple fabrics. Implement Fibre Channel routing. Migrate to another fabric topology. Deploy multiple independent SANs. Nondisruptive migration If you have a level 4 multiple fabric NSPOF SAN, you can fail over all operations to one fabric and then reconfigure the other fabric.
  • Page 59: Migrating A Ring Fabric San

    Meshed to core-edge Use the method described in Cascaded to core-edge on page 58. Migrating a ring fabric SAN This section describes migration paths for a ring fabric SAN. Ring to meshed If you have two ISLs between all switches in the ring fabric, re-cable each ISL so that it connects to the appropriate switch in the meshed fabric you design.
  • Page 60 SAN fabric topologies...
  • Page 61: Fibre Channel Routing

    3 Fibre Channel routing This chapter describes Fibre Channel routing in an HP SAN environment. It describes the following topics: Fibre Channel routing overview, page 61 SAN scaling and routing, page 63 Fibre Channel routing implementations, page 64 Fabric redundancy and routing, page 69 Supported routing configurations, page 71...
  • Page 62: Fabric, Virtual Fabric, And 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.
  • Page 63: San Scaling And Routing

    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.
  • Page 64: Scaling By Routing

    Time Server Simple Name Service 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.
  • Page 65: Basic Mp Router Configuration

    400 Multi-protocol Router (400 MP Router) 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 A C-series switch with IVR connects multiple VSANs, as shown in Figure An H-series switch with TR connects to other B-series or C-series fabrics, as shown in Figure...
  • Page 66: B-Series Fabric Groups

    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.
  • Page 67: H-Series Switch Fabric Routing

    H-series switch fabric routing You can configure any H-series switch 8 Gb port as a TR_Port, which you use to connect devices on the H-series switch to devices on a remote fabric. You do this by configuring TR mapping, which establishes a route to connect one device on the H-series switch to one device on a remote fabric through one TR_Port.
  • Page 68: B-Series Virtual Fabric Ifr

    25266b Figure 21 B-series Virtual Fabric IFR VSAN 3 VSAN 2 VSAN 3 VSAN 1 VSAN 1 VSAN 2 VSAN 3 VSAN 2 VSAN 1 25105a Figure 22 C-series VSAN IVR As shown in Figure 22, VSANs can include devices that connect to a single switch or multiple switches in the SAN.
  • Page 69: Fabric Redundancy And Routing

    Figure 23 shows how TR_Ports on the H-series switch can connect devices in a local fabric to devices in a remote fabric. When a device on the H-series switch is mapped to a device in the remote fabric, the H-series switch automatically creates an inter-fabric zone whose members are the two devices and the TR_Port that connects them.
  • Page 70: Dual-Redundant Meta San With 1606 Extension San Switch Or Mp Router

    1606 Extension SAN Switch, 400 MPR, or MPR (FC Routing) Fabric A2 Fabric A1 Meta SAN A 1606 Extension SAN Switch, 400 MPR, or MPR (FC Routing) Fabric B1 Fabric B2 Meta SAN B 25106d Figure 24 Dual-redundant Meta SAN with 1606 Extension SAN Switch or MP Router FC Switch (IFR) VF A1...
  • Page 71: Supported Routing Configurations

    FC Switch (IVR) VSAN A1 VSAN A2 IVR SAN A FC Switch (IVR) VSAN B1 VSAN B2 IVR SAN B 25107b Figure 26 Dual-redundant VSAN Supported routing configurations Routing requires additional configuration rules for fabrics. For details about routing configuration rules, see “Fibre Channel routing, 400 MP Router, and MP Router Blade fabric rules”...
  • Page 72: Virtual Fabrics Connecting Core Switches

    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. 25268a Figure 28 Virtual Fabrics connecting core switches VSAN 3 VSAN 2 VSAN 3 VSAN 1 VSAN 2 VSAN 1...
  • Page 73: Routing Through An Ip Network

    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 30 Figure 31).
  • Page 74: High-Availability Router Configurations

    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 33 Figure 34 show valid configurations. The first configuration shows servers and storage connected using a pair of redundant fabrics in a level 4 NSPOF configuration.
  • Page 75: 400 Mp Router And Mp Router Blade Use Cases

    400 MPR or MPR (FC Routing) Fabric A1 Fabric A2 400 MPR or MPR (FC Routing) Fabric B1 Fabric B2 NSPOF con guration 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)
  • Page 76: Routing Use Cases

    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.
  • Page 77: Nspof Configuration With 1606 Extension San Switch Providing Fibre Channel Routing And Fcip With Direct Connect Devices

    In nonrouted FCIP configurations, local and remote fabrics merge when connected through an IP network. The IP connection acts as an ISL in a single fabric. By using Fibre Channel routing and FCIP, the local and remote fabrics connect without merging. You can create an LSAN that contains local and remote storage arrays and servers.
  • Page 78: Nspof Configuration With 1606 Extension San Switch Providing Fc Routing And Fcip With Direct Connect Devices

    1606 Extension 1606 Extension SAN Switch SAN Switch IP A Fabric A1 Fabric A2 FCIP with FC routing 1606 Extension 1606 Extension SAN Switch SAN Switch IP B Fabric B1 Fabric B2 FCIP with FC routing 26585b Figure 38 NSPOF configuration with 1606 Extension SAN Switch providing FC routing and FCIP with direct connect devices 400 MPR 400 MPR...
  • Page 79: Extension San Switch Or Mp Router Consolidating Tape Backup In A Meta San

    Figure 41 shows a configuration in which a 1606 SAN Extension Switch or MP Router consolidates tape backup in a Meta SAN. See the HP StorageWorks Enterprise Backup Solutions Design Guide and the EBS compatibility matrix for information about supported HP tape products and backup applications.
  • Page 80 Fibre Channel routing...
  • Page 81: Fabric Infrastructure Rules

    Part II. Fabric infrastructure rules Fabric infrastructure rules are presented in these chapters: H-series switches and fabric rules, page 83 B-series switches and fabric rules, page 93 C-series Fibre Channel and FCoE switches and fabric rules, page 135 M-series switches and fabric rules, page 157 SAN fabric connectivity and switch interoperability rules, page 167...
  • Page 83: 4 H-Series Switches And Fabric Rules

    4 H-series switches and fabric rules This chapter describes the fabric rules for the HP StorageWorks H-series switches. It describes the following topics: H-series switches, page 83 Fabric rules, page 86 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;...
  • Page 84: Model Numbering

    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.
  • Page 85 Nonblocking, full-bandwidth architecture Adaptive trunking Advanced security features (CHAP, RADIUS authentication, SSL/SSH, and port binding) TR_Port configuration, which enables connectivity of SN6000 Fibre Channel Switches to B-series or C-series fabrics High-availability features: Two hot-swappable power supplies in dual power supply model Hot-swappable 8 Gb SFP+ and 10/20 Gb optical transceivers NDCLA Nondisruptive port-license activation...
  • Page 86: Usage

    Table 11 H-series switches high-availability features Redundant/ Redundant/ Nondisruptive Nondisruptive code load/ hot-swappable hot-swappable port expan- Model power cooling activation sion/upgrade HP StorageWorks SN6000 Stackable Dual Power Supply Yes/Yes Yes/Yes Yes/Yes Fibre Channel Switch HP StorageWorks SN6000 Stackable Single Power Sup- No/No No/No Yes/Yes...
  • Page 87: Servers, Operating Systems, And Storage Products

    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 Table 12 H-series switches servers, operating systems, and storage system support Servers Operating systems Storage products HP ProLiant ML-Series and Microsoft Windows Server 2008...
  • Page 88: Fabric Rules For H-Series Switches

    Fabric rules for H-series switches Table 13 describes the rules for creating a SAN with H-series switches. Table 13 H-series switches fabric rules Rule number Description Supports up to 30 switches with up to 600 total 8 Gb/s ports, up to 120 10 Gb/20 Gb stacking ports, and up to 512 user ports in a fabric.
  • Page 89: Supported Switches In An H-Series Switch With Tr Remote Fabric

    Table 14 Supported switches in an H-series switch with TR remote fabric HP StorageWorks switch name Minimum firmware version Brocade 8Gb SAN Switch for HP BladeSystem c-Class 6.1.0_8e1 HP StorageWorks 8/8 Base, SAN Switch HP StorageWorks 8/24 SAN Switch HP StorageWorks 8/40 SAN Switch HP StorageWorks 8/80 SAN Switch Brocade 4Gb SAN Switch for HP c-Class BladeSystem HP StorageWorks 4/8 SAN Switch...
  • Page 90: Zoning Limits And Enforcement

    Rule number Description Local devices on an H-series switch can be mapped to different remote fabrics. For mappings between an H-series switch and a remote fabric, each local device or remote device can be mapped over one TR_Port. Additional mappings to either device must use that TR_Port.
  • Page 91: Zoning Enforcement For H-Series Switches

    Rule number Description Maximum number of zone members per fabric is 10,000. Table 17 describes zoning enforcement for H-series switches. Table 17 Zoning enforcement for H-series switches Switch Configuration Enforcement Comments HP StorageWorks Define zones using domain Access authorization at frame Hard zoning SN6000 Fibre Channel number and port number...
  • Page 92 H-series switches and fabric rules...
  • Page 93: 5 B-Series Switches And Fabric Rules

    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. It describes the following topics: B-series Fibre Channel switches, 1606 Extension SAN Switches, and MP Routers, page 93 Fibre Channel switch fabric rules, page 106...
  • Page 94: Model Numbering

    DC SAN Backbone Director and DC04 SAN Director support the 16, 32, and 48-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. SAN Director 4/256 supports the 16, 32, and 48-port 4 Gb/s Fibre Channel blades, 16, 32, and 48-port 8 Gb/s Fibre Channel blades, 10 Gb/s 10/6 FC ISL Blade, the MP Router Blade, and iSCSI Director Blade.
  • Page 95 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.html SAN Design Reference Guide...
  • Page 96: B-Series Fibre Channel Switches

    Table 18 B-series Fibre Channel switches Fabric Management HP StorageWorks switch name Firmware versions DCFM Number of ports 6.3.1 6.2.1b 6.3.0c 10.3.3 6.2.1 6.3.0b 10.3.1 6.2.0g 6.3.0a HP StorageWorks Encryption SAN Switch 10.3.0 6.2.0e 6.3.0 10.1.4 6.2.0d 6.2.2a 10.1.3 6.2.0b 6.2.2 10.1.2 HP StorageWorks Encryption FC Blade...
  • Page 97: B-Series Fibre Channel Switches And Routers

    Table 19 B-series Fibre Channel switches and routers Fabric Management HP StorageWorks switch name Firmware versions DCFM Number of ports 16 at 8 Gb/s Fibre Channel 6.3.1 HP StorageWorks 1606 Extension SAN Switch 6 at 1 GbE FCIP 6.3.0c 10.3.3 6.3.0b 10.3.1 12 at 8 Gb/s Fibre Channel...
  • Page 98: B-Series Legacy Fibre Channel Switches And Routers (Part I)

    Table 20 B-series legacy Fibre Channel switches and routers (part I) Fabric Management Firmware ver- Legacy HP StorageWorks switch name sions DCFM Number of ports 16 at 1, 2, or 4 Gb/s Fibre Channel HP StorageWorks 400 Multi-protocol Router 2 at 1 GbE 6.3.1 HP StorageWorks 4/32B SAN Switch 6.3.0c...
  • Page 99: B-Series Legacy Hp Fibre Channel Switches And Routers (Part Ii)

    Table 21 B-series legacy HP Fibre Channel switches and routers (part II) Fabric Management Legacy HP StorageWorks switch name Firmware versions DCFM Number of ports HP StorageWorks SAN Switch 2/32, 2/32 power pack HP StorageWorks 2/128, 2/128 SAN Director power pack 5.3.2c 10.3.3 HP StorageWorks SAN Switch 2/8V TAA,...
  • Page 100: Features

    Table 22 B-series legacy HP and Compaq Fibre Channel switches Fabric Management Legacy Compaq switch Firmware Legacy HP switch name name versions DCFM Number of ports HP SureStore FC 1Gb/2Gb Entry Switch 8B Compaq StorageWorks SAN Switch 2/8-EL Compaq StorageWorks 3.2.1c SAN Switch 2/16-EL HP SureStore FC 1Gb/2Gb...
  • Page 101 Fabric Watch—Proactively monitors the health and performance of switches and the fabric. ISL Trunking—Combines multiple links between switches to form a single, logical ISL with a total bandwidth of 64 Gb/s. This feature enables dynamic load balancing of data across ISLs. FCIP Trunking—Allows multiple IP source and destination address pairs (defined as FCIP circuits) via multiples of the 1 GbE or 10 GbE interfaces to provide a high-bandwidth FCIP tunnel and failover resiliency.
  • Page 102 Features of Fabric OS 6.x follow (see the appropriate Fabric OS administrator guide for configuration restrictions and more details): Adaptive Networking with QoS (optional licensed feature)—Provides tools to support high bandwidth on high-priority connections, ensuring optimum performance, even in congested networks. This option includes two features: QoS SID/DID Prioritization and Ingress Rate Limiting.
  • Page 103: B-Series Fibre Channel Switch High-Availability Feature Comparison

    Table 23 provides a comparison of the high-availability features for B-series Fibre Channel switches. Table 23 B-series Fibre Channel switch high-availability feature comparison Redundant Redundant Non- Non- Redundant Redundant /hot- /hot- core disruptive disruptive Redundant active swappable swappable switching control code port compon-...
  • Page 104: Usage

    Usage Table 24 describes the use of B-series Fibre Channel switches as core switches. Table 24 Using B-series Fibre Channel switches as core switches 1-96 user 97-224 user 225-500 user 501-728 user 729-1280 user Model ports ports ports ports ports DC SAN Backbone Director DC04 SAN Director...
  • Page 105: Using B-Series Fibre Channel Switches As Edge Switches

    Table 25 describes the use of B-series Fibre Channel switches as edge switches. Table 25 Using B-series Fibre Channel switches as edge switches 1-96 user 97-224 user 225-500 user 501-728 user 729-1280 user Model ports ports ports ports ports DC SAN Backbone Director DC04 SAN Director SAN Director 4/256 Excellent...
  • Page 106: Fibre Channel Switch Fabric Rules

    Fibre Channel switch fabric rules This section describes the fabric rules for B-series Fibre Channel switches and routers, and other factors you should consider when building B-series fabrics. When using B-series Fibre Channel switches in a fabric: Use the HP default settings for all current HP switches. Use the legacy HP default settings if the fabric contains only legacy HP switches.
  • Page 107: Operating Systems And Storage Products

    Operating systems and storage products The fabric rules for B-series switches and MP Routers apply to SANs that include the operating systems and storage products listed in Table Table 26 B-series Fibre Channel switch operating system and storage system support Operating systems Storage products HP-UX...
  • Page 108: B-Series Fibre Channel Switch Fabric Rules

    Table 27 describes the rules for creating a Fibre Channel SAN with B-series Fibre Channel switches. Table 27 B-series Fibre Channel switch fabric rules Rule number Description A maximum of 56 switches, 2,560 total ports, and 2,300 user ports in a single fabric with DC SAN Backbone Director, 8/8, 8/24, 8/40, 8/80, 4/8, 4/16, 4/32B, 4/32, 4/64, or 4/256 switches using firmware 6.x (or later), or 2/16N, 2/32, 2/64, or 2/128 switches using firmware 5.3.x (or later) .
  • Page 109 Rule number Description EVA4400 Embedded Switch Module, 8 Gb Brocade—Supports connectivity to: Servers Storage Note: The EVA4400 Embedded Switch Module, 8 Gb Brocade supports the same connectivity to HP storage systems as the 8/8, 8/24, and 8/80 switches. Other B-series switches, including the EVA4400 Embedded Switch Module, 8 Gb Brocade EVA and EVA4400 iSCSI Connectivity Option (see “EVA and EVA4400 iSCSI Connectivity Option”...
  • Page 110: Database Size Rules For B-Series Fibre Channel Switches

    Rule number Description Maximum of seven hops (eight switches) between any two communicating devices. The StorageWorks SAN Switch Integrated 32 or 64 and the HP SureStore FC Switch 6164 add a maximum of two hops between devices, depending on the device-to-switch connections and device-to-device access.
  • Page 111: B-Series Encryption Switch Fabric Rules

    Rule number Description Advanced Zoning—The maximum zoning database size is as follows: If all switches in a fabric are using firmware 5.2x (or later), the database size must not exceed 1 MB. If the fabric contains 1 Gb/s switches with firmware 2.6.1x (or later), the database must not exceed 96 KB.
  • Page 112: 1606 Extension San Switch And Dc Dir Switch Mp Extension Blade Fabric Rules

    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.
  • Page 113 Rule number Description FCIP is supported between pairs of 1606 Extension SAN Switches and DC Dir Switch MP Extension Blades, or between a 1606 Extension SAN Switch and a DC Dir Switch MP Extension Blade. FCIP is not supported in between the 1606 Extension SAN Switch or DC Dir Switch MP Extension Blade and the MP Router, 400 MP Router, or MP Router Blade.
  • Page 114: Scalability Rules

    Rule number Description The 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade do not support the following features with firmware 6.3.0: IPsec DiffServ priorities VLAN tagging Third-party WAN optimization IPv6 addresses for FCIP tunnels VEX_Ports (DC Dir Switch MP Extension Blade) Scalability rules Table 32 lists the scalability rules for Meta SANs using integrated Fibre Channel routing, the 1606...
  • Page 115 NOTE: All devices connected to one of the SAN Director's Fibre Channel ports are part of the backbone fabric. If you want to share up to 256 local devices in a backbone fabric connected to multiple edge fabrics For FCIP, if there are DC SAN Backbone Directors or DC04 SAN Directors at both the local site and remote site Use a 1606 Extension SAN Switch: If you do not have a DC SAN Backbone Director or DC04 SAN Director, and do not plan to use...
  • Page 116: Fibre Channel Routing, 400 Mp Router, And Mp Router Blade Fabric Rules

    Fibre Channel routing, 400 MP Router, and MP Router Blade fabric rules This section describes the fabric rules for 8 Gb/s switches with license-enabled integrated Fibre Channel routing, the 400 MP Router, and the MP Router Blade, and other factors you should consider when building B-series fabrics that contain Fibre Channel routing.
  • Page 117 Rule number Description FCIP is supported with IPsec data encryption. This requires a minimum firmware version of 5.2.0a. IPsec is supported with Continuous Access EVA and XP Continuous Access. Note: IPsec and FCIP FastWrite are mutually exclusive and cannot be configured simultaneously. FCIP FastWrite and Fibre Channel FastWrite support: FCIP is supported with FCIP FastWrite SCSI write acceleration.
  • Page 118 Translate phantom domains—Assigned to each remote fabric connected to a 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. Backbone fabric—The 400 MP Router or MP Router Blade backbone fabric consists of at least one 400 MP Router or MP Router Blade and includes all MP Routers and B-series switches connected via E_Port to the 400 MP Router or MP Router Blades.
  • Page 119: Integrated Fibre Channel Routing, 1606 Extension San Switch, Dc Dir Switch Mp Extension

    Table 32 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 5.x/6.x Edge fabric scalability Domains Maximum number of front domains per edge fabric (see Figure Maximum number of EX_Ports per edge fabric...
  • Page 120 Maximum number of total domains per backbone fabric WWNs Maximum number of local WWNs per backbone fabric 512 (32 edge fabrics) 1,280 (1 edge fabric) Hop count scalability Hop count Maximum number of hops between switches (including routers) in a Meta SAN (Figure 400 MP Router and MP Router Blade hop count The 400 MP Router and MP Router Blade are counted in the same way as a Fibre Channel switch...
  • Page 121: Mp Router Fabric Rules

    MP Router fabric rules This section describes the fabric rules for the MP Router and other factors you should consider when building B-series fabrics that contain MP Routers. The fabric rules for the MP Router apply to SANs that include the same operating system and storage products as the B-series switches (see “Operating systems and storage products”...
  • Page 122: Iscsi Storage Device Connectivity For The Mp Router

    Rule number Description Supports routing between B-series and M-series edge fabrics. This requires MP Router firmware 7.4 (or later), B-series firmware 2.6.2x, 3.2.x, or 5.x (or later), and M-series firmware 06.02.00-22 in Open Fabric mode. For MP Router firmware 7.4.1 or later, M-series firmware 07.01.03 and 08.02.00 are supported in Open Fabric mode.
  • Page 123: Fibre Channel Routing Storage Device Connectivity For The Mp Router

    Routable Edge Fabric FC Storage FC Switch E_Ports FC Switch Backbone Fabric EX_Ports Routable FC Switch FC Storage E_Ports E_Ports Routable FC Storage FC Switch EX_Ports Edge Fabric FC Switch E_Ports Routable FC Storage FC Switch 25118a Figure 44 Fibre Channel routing storage device connectivity for the MP Router The following sections describe additional considerations and rules for using the MP Router in a fabric: XPath OS compatibility, page 124...
  • Page 124 XPath OS compatibility Table 18 through Table 22 list the B-series switches and firmware versions that are supported in a SAN with the MP Router XPath OS. Scalability rules Table 34 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.
  • Page 125: Mp Router Scalability Rules

    Table 34 MP Router scalability rules Edge fabric scalability Domains Maximum number of front domains (number of EX_Ports) per edge fabric (see Figure Maximum number of translate domains (number of remote fabrics) per edge fabric Maximum number of real domains (local switches) per edge fabric Maximum number of domains per edge fabric (real domains + front domains + translate domains) Note: The total number of domains in the first three rows must not exceed 80.
  • Page 126: Mp Router With Seven Hops

    Fabric 1 Fabric 2 MPR 1 25119b Figure 45 MP Router with seven hops Fabric 2 Front (phantom) Each fabric can access Translate domain 1 domain (EX_Ports) up to 33 translate (phantom) domains (33 remote fabrics). MPR 1 Fabric 1 Up to 33 Interswitch link (ISL) E_Port translate domains...
  • Page 127: Core Switch Addressing Mode

    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.
  • Page 128: Zoning Limits And Enforcement

    Zoning limits and enforcement Table 35 describes zoning enforcement for B-series Fibre Channel switches and MP Router LSANs. (See also “Zoning” on page 421.) Table 35 Zoning enforcement for B-series Fibre Channel switches and MP Router LSANs Switches or routers Configuration Enforcement Comments...
  • Page 129 For 4 Gb/s and 2 Gb/s SAN fabric switches, avoid transitions to soft zoning in a hardware- enforced zoning environment. B-series Fibre Channel switches allow a maximum of 64 SID entries for each quad. If you exceed this limit, the affected ports transition from hard to soft enforcement. Although the switch logs display warning messages, data integrity is preserved during this transition.
  • Page 130: B-Series Fcoe Converged Network Switch

    absolutely guarantee that a switch that requests to be the principal switch will actually achieve that status. NOTE: The fabricprincipal command is available with Fabric OS version 4.1.0 or later. The primary management switch is used by Fabric Manager as the main access point to that fabric.
  • Page 131: Features

    Features Features of the 2408 FCoE Converged Network Switch are the same as the B-series 8Gb switches, but the following features are not supported: Advanced Zoning (port-based and QoS) Extended Fabrics Adaptive Networking with QoS Virtual Fabrics Integrated Fibre Channel routing FICON Access Gateway Admin Domains...
  • Page 132: Operating Systems And Storage Products

    Operating systems and storage products The fabric rules for the 2408 FCoE Converged Network Switch apply to SANs that include the operating systems and storage products listed in Table Table 38 DC SAN Director Switch 10/24 FCoE Blade and 2408 FCoE Converged Network Switch operating system and storage system support Operating systems Storage products...
  • Page 133: Dc San Director Switch 10/24 Fcoe Blade And 2408 Fcoe Converged Network Switch Fabric Rules

    DC SAN Director Switch 10/24 FCoE Blade and 2408 FCoE Converged Network Switch fabric rules This section describes the fabric rules for the DC SAN Director Switch 10/24 FCoE Blade and 2408 FCoE Converged Network Switch, and other factors you should consider when building FCoE switch fabrics.
  • Page 134: Isl Maximums

    Rule number Description Supports existing B-series Fibre Channel rules and features except for the following: Advanced Zoning (port-based and QoS) Extended Fabrics Adaptive Networking with QoS Virtual Fabrics Integrated Fibre Channel routing FICON Access Gateway Admin Domains TI Zones M-EOS Interop Nondisruptive firmware upgrade A maximum of two DC SAN Director Switch 10/24 FCoE Blades per chassis are supported in DC/DC04 SAN Directors.
  • Page 135: 6 C-Series Switches And Fabric Rules

    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. It describes the following topics: C-series Fibre Channel switches, page 135 Fibre Channel switch fabric rules, page 146 C-series FCoE CN switches, page 151 Fabric rules for C-series Nexus 5000 Converged Network...
  • Page 136 The 18/4 Multiservice Module provides 18 4 Gb/s Fibre Channel ports and 4 GbE IP ports. The 32-port 2 Gb/s SSM is recommended for Fibre Channel write acceleration and SCSI statistics. The 48-port 8 Gb/s Host-Optimized Fibre Channel Switching Module uses four 12-port port groups at 12.8 Gb/s per port group and is recommended for 8 Gb/s low-range host connections.
  • Page 137: Model Naming

    MDS 9124 switches have fixed configurations with 8, 16, and 24 full-rate 4 Gb/s Fibre Channel ports. The 8 and 16-port switches can be upgraded in 8-port increments with a software expansion license. MDS 9124e 12-port Fabric switch and the MDS 9124e 24-port Fabric switch for the c-Class BladeSystem have fixed configurations with 8 internal/4 external or 16 internal/8 external full- rate 4 Gb/s Fibre Channel ports.
  • Page 138: C-Series Fibre Channel Switches For San-Os

    dating switch firmware, you can use two successive NX-OS/SAN-OS/FabricWare versions tem- porarily. Do not enable new switch features until the upgrade is complete. Follow the fabric rules. (See “Fibre Channel switch fabric rules” on page 146.) For the latest information on supported C-series Fibre Channel switches and firmware versions, see the HP SAN Infrastructure website: http://h18006.www1.hp.com/storage/saninfrastructure.html Table 41 C-series Fibre Channel switches for SAN-OS...
  • Page 139: C-Series Fibre Channel Switches For Nx-Os

    Table 42 C-series Fibre Channel switches for NX-OS Maximum number of Fibre Switch Firmware version Channel ports MDS 9506 Multilayer Director MDS 9509 Multilayer Director MDS 9513 Multilayer Director MDS 9222i Multiservice Fabric MDS 9124 NX-OS 4.2(3), 4.2(1a), 4.1(3a), 4.1(1c), 4.1(1b) 32 at 4 Gb/s MDS 9134 2 at 10 Gb/s...
  • Page 140: C-Series Fibre Channel Switching Module Support Matrix For San-Os

    Table 44 C-series Fibre Channel switching module support matrix for SAN-OS Switch type Switching module MDS 9216 MDS 9216A MDS 9216i MDS 9222i MDS 9506 MDS 9509 MDS 9513 16-port Fibre Channel Switching Module (1 Gb, 2 Gb) 32-port Fibre Channel Switching Module (1 Gb, 2 Gb) 14/2 Multiprotocol...
  • Page 141: C-Series Fibre Channel Switching Module Support Matrix For Nx-Os

    NOTE: The 8 Gb/s Fibre Channel Switching Modules require NX-OS. Table 45 describes NX-OS C-series switching module support. Table 45 C-series Fibre Channel switching module support matrix for NX-OS Switch type MDS 9506 MDS 9509 with with MDS 9513 MDS 9513 Supervisor-2 Supervisor-2 with Fabric-1...
  • Page 142: Features

    Switch type MDS 9506 MDS 9509 with with MDS 9513 MDS 9513 Supervisor-2 Supervisor-2 with Fabric-1 with Fabric-2 Switching module MDS 9216i MDS 9222i Modules Modules Modules Modules 48-port 8Gb Performance Fibre Channel Switching Module (2 Gb, 4 Gb, 8 Gb) 24-port 8Gb Fibre Channel Switching Module (2 Gb, 4 Gb, 8 Gb)
  • Page 143: C-Series Fibre Channel Switch High-Availability Feature Comparison

    WWNs to virtual WWNs using NAT. When NPV mode is enabled, FlexAttach allows SAN and server administrators to install and replace servers without having to rezone or reconfigure the SAN. For more information on FlexAttach, see “NPV with FlexAttach” on page 194. The MDS 9222i Multiservice Fabric Switch and the 18/4 Multiservice Module are SME compliant.
  • Page 144 Redundant Nondisruptive Redundant/ Redundant/ control code Protocol hot-swappable hot-swappable Port module Model power cooling processor activation support support MDS 9020 No/No Yes/No C-series switches and fabric rules...
  • Page 145: Usage

    Usage Table 47 describes the use of C-series Fibre Channel switches as core switches. Table 47 Using C-series Fibre Channel switches as core switches Model 1 48 total ports 49 224 total ports 225 512 total ports MDS 9120 Fabric Excellent Not recommended (20 port maximum)
  • Page 146: Fibre Channel Switch Fabric Rules

    Table 48 describes the use of C-series Fibre Channel switches as edge switches. Table 48 Using C-series Fibre Channel switches as edge switches Model 1 48 total ports 49 224 total ports 225 512 total ports MDS 9120 Fabric Excellent MDS 9140 Fabric Excellent MDS 9124 Fabric...
  • Page 147: Operating Systems And Storage Products

    Operating systems and storage products The fabric rules for C-series switches apply to SANs that include the operating systems and storage products listed in Table Table 49 C-series Fibre Channel switch operating system and storage system support Operating systems Storage products HP-UX EVA8400/6400 OpenVMS...
  • Page 148: Fabric Rules For C-Series Fibre Channel Switches

    Fabric rules for C-series Fibre Channel switches The following fabric rules apply to all C-series Fibre Channel SANs. They also apply, in general, to HP XP Continuous Access and HP Continuous Access EVA configurations. However, additional rules apply to HP Continuous Access implementations. See the HP StorageWorks Continuous Access EVA Planning Guide for detailed information.
  • Page 149: Isl Maximums

    ISL maximums You can use all full-rate ports on all C-series Fibre Channel switches for ISLs, with a maximum of one half of the total ISL port count configured to the same destination switch. Table 51 lists the ISL maximums for switches with higher port counts.
  • Page 150: Zoning Limits And Enforcement

    Zoning limits and enforcement Table 52 lists the zoning limits for C-series Fibre Channel switches. (See also “Zoning” on page 421.) Table 52 Zoning limits for C-series Fibre Channel switches Rule number Description Maximum number of zones for a fabric with VSANs is 8,000. Maximum number of zone members for a fabric with VSANs is 20,000.
  • Page 151: C-Series Fcoe Converged Network Switches

    Fabric A Fabric B Management VSAN 3 VSAN 2 VSAN 1 25121a Figure 47 C-series Fibre Channel switch high-availability VSAN management configuration C-series FCoE Converged Network switches This section describes support for C-series FCoE CN switches, switch models, and FCoE fabric rules. For more information on configuring FCoE SANs, see the HP StorageWorks Fibre Channel over Ethernet application note, available at http://www.hp.com/go/SDGmanuals.
  • Page 152: C-Series Nexus Switches For Nx-Os

    Nexus 5000 4-port 4Gb FC + 4-port 10GbE Module Nexus 5000 8-port 4Gb FC Module Nexus 5000 6-port 8Gb FC Module For the latest information on supported C-series FCoE CN switches and firmware versions, see the HP SAN Infrastructure website: http://h18006.www1.hp.com/storage/saninfrastructure.html. Table 54 lists the firmware version and port maximums for the C-series Nexus switches.
  • Page 153: Usage

    High availability (see Table Table 56 provides a comparison of the high-availability features for C-series Nexus 5000 Converged Network Switches. Table 56 C-series Nexus 5000 Series switch high-availability feature comparison Redundant Redundant/ Redundant/ control Protocol hot-swappable hot-swappable Nondisruptive Expansion Switch power cooling processor...
  • Page 154: C-Series Fcoe Converged Network Switch Fabric Rules

    Table 58 lists the rules for creating a SAN with C-series FCoE CN switches. Table 58 C-series FCoE Converged Network switch fabric rules Rule number Description A C-series FCoE CN switch can be a standalone switch or an edge switch in a Fibre Channel fabric.
  • Page 155: Isl Maximums

    ISL maximums Table 59 C-series FCoE CN switch ISL maximums Total number of available FC Number of ports allowed as FC Switch user ports ISLs Nexus 5020 16 at 4 Gb/s Nexus 5010 8 at 4 Gb/s SAN Design Reference Guide...
  • Page 156 C-series switches and fabric rules...
  • Page 157: 7 M-Series Switches And Fabric Rules

    7 M-series switches and fabric rules This chapter describes the M-series switches and the fabric rules for building M-series fabrics. It describes the following topics: M-series switches, page 157 Fibre Channel fabric rules, page 161 NOTE: “SAN fabric connectivity and switch interoperability rules”...
  • Page 158: Model Numbering

    Model numbering The M-series switches typically use the numbering scheme x/y: x—The highest speed at which the switch ports can operate, measured in Gb/s y—The number of switch ports For example, the HP StorageWorks Edge Switch 2/32 is a 2 Gb/s switch with 32 ports. The 4 Gb/s and 2 Gb/s switch ports autonegotiate the signaling speed.
  • Page 159: M-Series Legacy Hp Storageworks Switches

    Table 61 McDATA/Brocade switches supported with M-series switches McDATA/Brocade switch Firmware version Number of ports Sphereon 4700/M4700 Fabric Switch 09.09.06 8 to 32 09.09.05 Sphereon 4400/M4400 Fabric Switch 4 to 16 09.09.03 09.09.02 09.09.00 09.08.03 09.08.01 09.07.02 Intrepid 10000/Mi10K Director 09.09.06 32 to 256 09.09.05...
  • Page 160: M-Series High-Availability Feature Comparison

    Table 63 compares the high-availability features of M-series switches. Table 63 M-series high-availability feature comparison Size Redundant control Redundant active Model (1U = 1.75 inch) processor/switching components McDATA 4 Gb SAN Switch for HP p-Class BladeSystem Edge Switch 2/12 Edge Switch 2/24 Edge Switch 2/32 1.5U Director Switch 2/64...
  • Page 161: Fibre Channel Fabric Rules

    Table 65 describes the use of M-series switches as edge switches. Table 65 Using M-series switches as edge switches Model 1 500 total ports 501 1000 total ports 1000 1632 total ports Director 2/140 Good Very good Excellent Director 2/64 Good Very good Excellent...
  • Page 162: Operating Systems And Storage Products

    Operating systems and storage products The fabric rules for M-series switches apply to SANs that include the operating systems and storage products listed in Table Table 66 M-series Fibre Channel switch operating system and storage system support Operating systems Storage products HP-UX EVA8400/6400 OpenVMS...
  • Page 163: Isl Maximums

    Rule number Description The supported limit of interconnected switches in a single fabric is 31, provided that any Edge Switch 2/32 or Director 2/64 in the fabric is deployed at the edge of the fabric. In fabric configurations exceeding 1,500 devices, use Edge Switch 2/32 and Director 2/64 at the edge of the fabric.
  • Page 164: Isl Maximums

    Table 68 lists the maximums for switches with higher port counts. Table 68 ISL maximums Total number of available user Switch ports Number of E_Ports allowed McDATA 4 Gb SAN Switch for HP p-Class BladeSystem HP StorageWorks Director 2/64 (75% of installed ports) HP StorageWorks Director 2/140 M-series switches and fabric rules...
  • Page 165: M-Series And Mcdata Zoning Limits

    Zoning limits and enforcement Table 69 lists zoning limits for M-series and McDATA switches. (See also “Zoning” on page 421.) Table 69 M-series and McDATA zoning limits Firmware 09. xx . xx Firmware 6.4. x . xx . xx Maximum value with McDATA Maximum value with M-series 4 Gb SAN Switch for HP p-Class Zoning parameter...
  • Page 166: Zoning Enforcement For M-Series And Mcdata Switches

    Table 70 Zoning enforcement for M-series and McDATA switches Switches Configuration Enforcement Comments Define zones using Discovery authentication Soft zoning or hard HP StorageWorks domain number and port Name Server zoning (5.01.00-24 and Edge Switch 2/12 number (HP M-series directory-based later) Edge Switch 2/24 Homogeneous Fabric...
  • Page 167: San Fabric Connectivity And Switch Interoperability Rules

    8 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 167 SAN fabric switch interoperability rules, page 177 Third-party switch support, page 179 SAN performance considerations, page 179 SAN fabric connectivity rules...
  • Page 168: Fiber Optic Cables

    NL_Port—Connects a Fibre Channel device to a Fibre Channel arbitrated loop or switch Fiber optic cables All 8 Gb/s, 4 Gb/s and 2 Gb/s components use industry-standard LC connectors for fiber optic cable connections; all 1 Gb/s components use industry-standard SC connectors. Cables and adapters are available with SC connectors on one end and LC connectors on the other end.
  • Page 169: Gb/S Fiber Optic Cable Loss Budgets (Nominal Bandwidth)

    bandwidth and higher bandwidth fiber optic cable. Nominal specifies modal bandwidth of 500 MHz-km at 850 nm for 50 micron fiber optic cable (type OM2), and 200 MHz-km at 850 nm for 62.5 micron fiber optic cable (type OM1). Higher specifies modal bandwidth of 2000 MHz-km at 850 nm for 50 micron fiber optic cable (type OM3).
  • Page 170: Gb/S Fiber Optic Cable Loss Budgets (Higher Bandwidth)

    Table 73 8 Gb/s fiber optic cable loss budgets (higher bandwidth) Maximum distance per Total channel insertion Maximum loss per Cable cable segment loss mated connector pair 50/125 micron (OM3 2000 MHz-km at 850 150 m 2.04 dB 0.75 dB Table 74 lists the 4 Gb/s fiber optic cable loss budgets when using nominal bandwidth OM1 or OM2 multi-mode fiber optic cable, and single-mode fiber optic cable.
  • Page 171: Storage Product Interface And Transport Distance Rules

    Table 77 2 Gb/s fiber optic cable loss budgets (higher bandwidth) Maximum distance per Total channel insertion Maximum loss per Cable cable segment loss mated connector pair 50/125 micron (OM3 2000 MHz-km at 850 500 m 3.31 dB 0.75 db Table 78 lists the 1 Gb/s fiber optic cable loss budgets when using nominal bandwidth OM1 or OM2 multi-mode fiber optic cable, and single-mode fiber optic cable.
  • Page 172: Gb/S Fibre Channel Distance Rules (B-Series, C-Series, And H-Series)

    Table 79 describes the distance rules for 8 Gb/s Fibre Channel connections when using 8 Gb/s Fibre Channel switch models. Table 79 8 Gb/s Fibre Channel distance rules (B-series, C-series, and H-series) Supported storage Interface/transport Supported distances products 50 micron multi-mode OM2 fiber OM3 fiber Heterogeneous SAN...
  • Page 173: Gb/S Fibre Channel Distance Rules (B-Series And C-Series Switches)

    Table 80 describes the distance rules for 4 Gb/s Fibre Channel connections when using 4 Gb/s Fibre Channel switch models. Table 80 4 Gb/s Fibre Channel distance rules (B-series and C-series switches) Interface/transport Supported distances Supported storage products 50 micron multi-mode fiber OM2 fiber OM3 fiber Heterogeneous SAN servers, Fibre...
  • Page 174: Gb/S Fibre Channel Distance Rules (B-Series, C-Series, And M-Series Switches)

    Table 81 describes the distance rules for 2 Gb/s Fibre Channel connections when using 2 Gb/s Fibre Channel switch models. Table 81 2 Gb/s Fibre Channel distance rules (B-series, C-series, and M-series switches) Interface/transport Supported distances Supported storage products 50 micron multi-mode fiber OM2 fiber OM3 fiber Heterogeneous SAN servers, Fibre...
  • Page 175: Gb/S Fibre Channel Distance Rules (B-Series, C-Series, And M-Series Switches)

    Table 82 describes the distance rules for 1 Gb/s Fibre Channel connections when using 1 Gb/s Fibre Channel switch models. Table 82 1 Gb/s Fibre Channel distance rules (B-series, C-series, and M-series switches) Interface/transport Supported distances Supported storage products 50 micron multi-mode fiber optic cable and short-wave 500 m at 1 Gb/s Heterogeneous SAN servers, Fibre GBICs and GLMs...
  • Page 176: Fcip Extension Ip Network Distance Rules

    Table 84 describes the distance rules for FCIP extension Fibre Channel connections. Table 84 FCIP extension IP network distance rules Interface/transport HP Continuous Access EVA and XP Continuous Access HP B-series 400 MP Router, MP Router 100 ms IP network delay one-way or 200 ms round-trip 100 ms IP network delay Blade (FCIP) one-way or 200 ms round-trip...
  • Page 177: San Fabric Switch Interoperability Rules

    Table 85 describes the distance rules for iSCSI bridging Fibre Channel connections. Table 85 iSCSI bridging Fibre Channel distance rules Interface/transport Heterogeneous SAN Fibre Channel distances HP B-series iSCSI Director Blade HP C-series MDS 9216i, IPS-4, IPS-8, 14/2, 18/4 Table 79 through Table HP EVA iSCSI Connectivity Option...
  • Page 178 A SAN with one fabric containing B-series switches only and a second fabric containing H-series switches only A SAN with one fabric containing B-series switches only and a second fabric containing M-series switches only When creating a dual interoperable, heterogeneous SAN, consider the following: HP recommends that you use the same fabric topology and configuration in both fabrics to maintain balanced SAN performance.
  • Page 179: Interoperable, Heterogeneous Switch Fabrics

    Interoperable, heterogeneous switch fabrics An interoperable, heterogeneous switch fabric can contain different series of switches. Table 87 lists the switch combinations. Table 87 Heterogeneous switches in the same fabric Heterogeneous switch combinations Reference C-series and B-series Fabric interoperability: Merging fabrics based on C-series and B-series Fibre Channel switches application notes C-series and M-series Fabric interoperability: Merging fabrics based on C-series and M-series Fibre...
  • Page 180: Infrastructure Factors

    Infrastructure factors A single-switch fabric provides the highest level of performance. In a fabric with multiple switches, the following factors can affect performance: Latency Switch latency is less than 5% (at 1 Gb/s) of the data transfer time; therefore, the number of switches and hops between devices is not a major performance factor.
  • Page 181 FCC allows C-series switches to intelligently regulate traffic across ISLs and ensure that each initi- ator-target pair of devices has the required bandwidth for data transfer. C-series switches can also prioritize frames using the QoS feature. SAN Design Reference Guide...
  • Page 182 SAN fabric connectivity and switch interoperability rules...
  • Page 183: Host And Storage System Rules

    Part III. Host and storage system rules Host and storage system rules are presented in these chapters: Heterogeneous server rules, page 185 MSA storage system rules, page 235 EVA storage system rules, page 247 XP and VA storage system rules, page 263 SAN Virtualization Services Platform, page 271 Enterprise Backup...
  • Page 185: Heterogeneous Server Rules

    9 Heterogeneous server rules This chapter describes platform configuration rules for SANs with specific operating systems and heterogeneous server platforms: SAN platform rules, page 186 Blade servers, page 186 HP c-Class BladeSystem Virtual Connect, page 187 BladeSystem with Brocade Access Gateway mode, page 189 BladeSystem with Cisco N_Port Virtualization mode, page 192...
  • Page 186: San Platform Rules

    SAN platform rules Table 88 describes SAN platform rules for all SAN server configurations. Table 88 General SAN platform rules Rule number SAN platform configuration Any combination of heterogeneous clustered or standalone servers with any combination of storage systems is supported. The configuration must conform to requirements and rules for each SAN component, including: Operating system Fabric...
  • Page 187: Hp C-Class Bladesystem Virtual Connect

    Blade servers Switches BL3xp B-series Brocade 4Gb SAN Switch for HP p-Class BladeSystem C-series M-series Edge Switch 2/12 and 2/24 only McDATA 4Gb SAN Switch for HP p-Class BladeSystem BL40p B-series C-series M-series For HP ProLiant BL c-Class SAN product support, see the support matrix at http:// h18006.www1.hp.com/storage/saninfrastructure/switches/b4gbsscblade.
  • Page 188: Hp Vc-Fc Connectivity Guidelines

    Allows you to change servers in minutes, not days. You can add, replace, and recover servers quickly without affecting SANs or LANs. Provides connectivity to multiple fabric types (B-series, C-series, H-series, M-series), without inter- operability constraints. Does not use a domain ID, preventing issues with the switch count scalability limit in a fabric and eliminating the additional hop between switches.
  • Page 189: Bladesystem With Brocade Access Gateway Mode

    BladeSystem with Brocade Access Gateway mode AG mode is a software-enabled feature available with the Brocade 8Gb SAN Switch for HP BladeSystem c-Class and the Brocade 4Gb SAN Switch for HP c-Class and p-Class BladeSystems with Fabric OS 5.2.1b (or later). AG mode does not require the purchase of additional hardware or software.
  • Page 190: Failover Policy And Failback Policy

    c-Class BladeSystem Access Gateway N_Port (host) Server Bay 1 F_Port (virtual) Uplink 1 F_Port (NPIV) Server Bay 2 N_Port (NPIV) Server Bay 3 Uplink 2 F_Port (NPIV) N_Port (NPIV) Server Bay 4 c-Class BladeSystem Access Gateway Server Bay 5 Uplink 3 F_Port (NPIV) N_Port (NPIV) Server Bay 6...
  • Page 191: Ag Mode Considerations

    AG mode considerations AG mode considerations follow: Ability to connect B-, C-, and M-series fabrics without interoperability constraints (see the release notes for support information) Flexible licensing option (12 or 24 ports, with a 12-port upgrade option on the 12-port model) Ability to use in either switch mode or AG mode (cannot function in both modes simultaneously, software selectable) Share Fabric OS with B-series switches...
  • Page 192: Bladesystem With Cisco N_Port Virtualization Mode

    Redundant SANs, with each server connecting to one fabric through one AG module Ability to connect to B-series, C-series, and M-series fabrics Support for up to six AGs per blade enclosure BladeSystem with Cisco N_Port Virtualization mode NPV mode is a software-enabled feature available on the Cisco MDS 9124e Fabric Switch for HP c-Class BladeSystem with SAN-OS 3.2(1a) or later.
  • Page 193: Failover Policy

    c-Class BladeSystem N_Port Virtualization N_Port (host) Server Bay 1, fc1/16 F_Port (virtual) ext1, fc1/10 F_Port (NPIV) Server Bay 2, fc1/15 NP_Port Server Bay 3, fc1/11 ext2, fc1/14 F_Port (NPIV) c-Class BladeSystem NP_Port Server Bay 4, fc1/9 N_Port Virtualization Server Bay 5, fc1/4 ext3, fc1/18 (NPV) F_Port (NPIV)
  • Page 194: Npv Mode Connectivity Guidelines

    Failover between NP_Ports (uplinks) is supported. Direct storage attachment is not supported, (requires at least one external Fibre Channel switch). F_Ports, NP_Ports, and SD_Ports are supported. NPIV-capable module servers (nested NPIV) are supported. Local switching is not supported. All traffic is switched using the NPV core switch. Remote SPAN is not supported.
  • Page 195: Cisco Mds 9124E Fabric Switch For Hp C-Class Bladesystem Using Npv With

    With FlexAttach, you can perform the following tasks without the need to make SAN or storage configuration changes: Preconfiguration—You can preconfigure the SAN for the addition of new servers whose WWPNs are unknown, using the virtual WWPNs. Once the servers are available, you can bring them online and into the fabric.
  • Page 196: Hp Bladesystem C3000 Enclosure Considerations

    NOTE: The names of the uplink ports (N_Ports 1 through 8) in Figure 53 are symbolic only. See the NPV documentation for the actual port numbers. HP BladeSystem c3000 enclosure considerations Consider the following when using the HP BladeSystem c3000 enclosure: The c3000 has four interconnect bays: 1, 2, 3, and 4.
  • Page 197: Hba Npiv Connectivity Guidelines

    HBA NPIV connectivity guidelines Figure 54 shows the logical relationship between virtual WWPNs and a VOS with HBA NPIV enabled. A server running a VOS has three instances of VMs. The server has an HBA with a manufacturing-assigned WWPN (20:00:00:00:c9:56:31:ba), and is connected to port 8 of a switch whose domain ID is 37.
  • Page 198: Nonstop Servers (Xp Only)

    NonStop servers (XP only) NonStop servers are supported in direct host attach and SAN configurations for specific storage systems. NonStop servers Storage systems S-series servers: XP disk arrays: S760, S76000 XP128, XP1024 (RAID450) S78, S780, S7800, S78000 XP10000, XP12000 (RAID500) S86000, S88000 XP20000, XP24000 (RAID600) NS-series servers:...
  • Page 199: Nonstop High-Availability Configurations Using Ioames

    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.
  • Page 200: Nonstop Bladesystem With Xp High-Availability Configurations Using Clims

    Table 93 NonStop BladeSystem with XP high-availability configurations using CLIMs (HP Integrity NonStop NB50000c BladeSystem only) Maximum availability config- Direct host attach configura- SAN configuration minim- uration minimum/recommen- NonStop server support tion minimum/recommended um/recommended Number of Fibre Channel SAN fabrics Number of XP storage systems Number of CLIMs per Integrity NonStop BladeSystem...
  • Page 201 Rule number Description The following restrictions apply to CLIMs: The maximum number of LUNs for each CLIM, (including SAS disks, XP disk arrays, and tapes) is 512. Each primary, backup, mirror, and mirror backup path is counted. The XP LUN range for each port is 0 to 499. The maximum number of XP ports for each CLIM is four.
  • Page 202 Rule number Description High-availability SAN Requires dual-redundant SAN fabrics (level 4, NSPOF high-availability SAN configuration; “Data availability” on page 53 for information about data availability levels). Each fabric consists of either a single switch or two cascaded switches, as shown in Figure 58 through Figure...
  • Page 203: Minimum Direct Host Attach Ioame Configuration For Xp Storage Systems

    Figure 55 shows a minimum direct host attach configuration with an IOAME. IOAME p mb XP Array 25122a Figure 55 Minimum direct host attach IOAME configuration for XP storage systems Figure 56 shows a minimum direct host attach configuration with VIO enclosures. VIO Enclosure VIO Enclosure XP Array...
  • Page 204: Minimum Direct Host Attach Clim Configuration For Xp Storage Systems

    Figure 57 shows a minimum direct host attach configuration with CLIMs. CLIM CLIM XP Array 26489a Figure 57 Minimum direct host attach CLIM configuration for XP storage systems Figure 58 shows a minimum SAN configuration with an IOAME. IOAME p mb XP Array 25123a Figure 58 Minimum SAN IOAME configuration for XP storage systems...
  • Page 205: Minimum San Vio Configuration For Xp Storage Systems (Ns1000, Ns14000)

    Figure 59 shows a minimum SAN configuration with VIO enclosures. VIO Enclosure VIO Enclosure mb p XP Array 25280a Figure 59 Minimum SAN VIO configuration for XP storage systems (NS1000, NS14000) Figure 60 shows a minimum SAN configuration with CLIMs. CLIM CLIM mb p...
  • Page 206: San Ioame Configuration With Logical And Physical Redundancy For Xp Storage

    Figure 61 shows a configuration with physical IOAME redundancy. IOAME IOAME XP Array 25124a Figure 61 SAN IOAME configuration with logical and physical redundancy for XP storage systems Heterogeneous server rules...
  • Page 207: San Vio Configuration With Logical And Physical Redundancy For Xp Storage Systems (Ns1000, Ns14000)

    Figure 62 shows a SAN configuration with VIO Fibre Channel PIC redundancy. VIO Enclosure VIO Enclosure XP Array 25281a Figure 62 SAN VIO configuration with logical and physical redundancy for XP storage systems (NS1000, NS14000) SAN Design Reference Guide...
  • Page 208: San Clim Configuration With Logical And Physical Redundancy For Xp Storage

    Figure 63 shows a SAN configuration with CLIM physical redundancy. CLIM CLIM CLIM CLIM b mb2 XP Array 26491a Figure 63 SAN CLIM configuration with logical and physical redundancy for XP storage systems Heterogeneous server rules...
  • Page 209: San Ioame Configuration (Two Cascaded Switches) With Logical And Physical Redundancy

    Figure 64 shows a configuration with physical IOAME redundancy. IOAME IOAME XP Array 25125a Figure 64 SAN IOAME configuration (two cascaded switches) with logical and physical redundancy for XP storage systems SAN Design Reference Guide...
  • Page 210: San Vio Configuration (Two Cascaded Switches) With Logical And Physical Redundancy

    Figure 65 shows a SAN configuration (two cascaded switches) with VIO Fibre Channel PIC redundancy. VIO Enclosure VIO Enclosure mb p XP Array 25278a Figure 65 SAN VIO configuration (two cascaded switches) with logical and physical redundancy for XP storage systems (NS1000, NS14000) Heterogeneous server rules...
  • Page 211: San Clim Configuration (Two Cascaded Switches) With Logical And Physical Redundancy

    Figure 66 shows a SAN (two cascaded switches) configuration with CLIM physical redundancy. CLIM CLIM CLIM CLIM b mb2 XP Array 26492a Figure 66 SAN CLIM configuration (two cascaded switches) with logical and physical redundancy for XP storage systems SAN Design Reference Guide...
  • Page 212: Hp-Ux San Rules

    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 96 describes the SAN configuration rules for HP-UX. Table 97 describes support for HP-UX multipathing coexistence.
  • Page 213: Hp-Ux Multipathing Coexistence Support

    Table 97 HP-UX multipathing coexistence support 4000/4100/4400/ 6000/6100/8000/ 8100 XCS 6x 4400 XCS 09 x XP128/1024/ MSA2000fc G2 EVA3000/5000 6400/8400 XCS 10000/12000/ (MSA2300fc) VCS 4 x 0950x 20000/24000 Notes — — — — MSA2000fc G2 — — — — (MSA2300fc) —...
  • Page 214: Hp Openvms San Rules

    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 98 describes the SAN configuration rules for HP OpenVMS. Table 99 describes support for HP OpenVMS multipathing coexistence.
  • Page 215: Hp Openvms Multipathing Coexistence Support

    Table 99 HP OpenVMS multipathing coexistence support 4000/4100/ 6000/6100/ 8000/8100 XCS 6x 4400 XCS MSA2000fc MSA1000 3000/ 3000/ 09 x MSA1500 5000 5000 single con- 6400/8400 (MSA2300fc) troller VCS 3 x VCS 4 x XCS 0950 x Native multipathing driver MSA2000fc G2 (MSA2300fc) MSA1500 A/A...
  • Page 216: Host-Based Volume Shadowing

    Host-based volume shadowing HP OpenVMS servers with host-based volume shadowing are supported in a heterogeneous SAN. Support includes configurations that use host-based volume shadowing over Fibre Channel links with long-distance transceivers or WDM and use of B-series FC or FCIP Fastwrite, or C-series Write Acceleration.
  • Page 217: Hp Tru64 Unix San Rules

    HP Tru64 UNIX SAN rules This section describes the SAN rules for HP Tru64 UNIX. 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 describes the SAN configuration rules for HP Tru64 UNIX. Table 101 describes support for HP Tru64 UNIX multipathing coexistence.
  • Page 218: Hp Tru64 Unix Multipathing Coexistence Support

    Table 101 HP Tru64 UNIX multipathing coexistence support 4000/4100/ 6000/6100/ MSA1000 EVA3000/ EVA3000/ 8000/8100 MSA1500 5000 5000 single con- troller VCS 3 x VCS 4 x XCS 6x Native multipathing driver MSA1500 A/A MSA1000 single controller EVA3000/5000 VCS 3 x Native mul- tipathing EVA3000/5000 VCS 4 x...
  • Page 219: Apple Mac Os X San Rules

    Apple Mac OS X SAN rules This section describes the SAN rules for Apple Mac OS X. 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 102 describes the SAN configuration rules for Apple Mac OS X.
  • Page 220: Ibm Aix San Rules

    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 103 describes the SAN configuration rules for IBM AIX. Table 104 describes support for IBM AIX multipathing coexistence.
  • Page 221: Ibm Aix Multipathing Coexistence Support

    Table 104 IBM AIX multipathing coexistence support 4000/4100/6000/ 6100/8000/8100 XCS 3000/ 4400 XCS 09 x EVA3000/5000 5000 VCS 3 x VCS 4 x 6400/8400 XCS 0950x Secure Ante- Notes Path meta MPIO MPIO Antemeta HDLM MPIO — — — Secure Path EVA3000/5000 VCS Antemeta —...
  • Page 222: Linux San Rules

    Linux SAN rules This section describes the SAN rules for Linux. 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 105 describes SAN rules for Red Hat Linux and SUSE Linux. Table 105 Linux SAN configuration rules Storage systems Linux SAN rules...
  • Page 223: Microsoft Windows San Rules

    Microsoft Windows SAN rules This section describes the SAN rules for Microsoft Windows. 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 106 describes the SAN configuration rules for Microsoft Windows. Table 107 describes support for Microsoft Windows multipathing coexistence.
  • Page 224: Microsoft Windows Multipathing Coexistence Support

    Table 107 Microsoft Windows multipathing coexistence support XP128/1024 4000/4100/6000/6100/8000/ MSA2000fc XP10000/ 8100 XCS 6x 12000 (MSA2300fc) 3000/5000 4400 XCS 09 x XP20000/ VCS 4 x MSA2000fc 6400/8400 XCS 0950x 24000 MS MPIO MPIO MPIO MPIO MPIO HP MPIO FF MS MPIO DSM MSA2000fc G2 (MSA2300fc) MPIO...
  • Page 225: Novell Netware San Rules

    Novell NetWare SAN rules This section describes the SAN rules for Novell NetWare. 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 108 describes the SAN configuration rules for Novel NetWare. Table 109 describes support for Novell NetWare multipathing coexistence.
  • Page 226: Netware Multipathing Coexistence Support

    Storage systems NetWare SAN rules MSA1000 For Secure Path support and errata, see the compatibility guide at http://www.hp.com/go/MSA. MSA1500 Unlisted but supported storage systems have no additional SAN configuration restrictions. For the latest support information, contact an HP storage representative. Table 109 NetWare multipathing coexistence support MSA1 x 00 4000/4100/...
  • Page 227: Sun Solaris San Rules

    Sun Solaris SAN rules This section describes the SAN rules for Sun 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 110 describes the SAN configuration rules for Sun Solaris. Table 111 describes support for Sun Solaris multipathing coexistence.
  • Page 228 Storage systems Solaris SAN rules EVA3000/ Requires Secure Path multipathing driver. For version support, contact an HP storage representative. 5000 For HP Continuous Access EVA configuration information, see “HP Continuous Access EVA SAN (VCS 3x) integration” on page 254. Unlisted but supported storage systems have no additional SAN configuration restrictions. For the latest support information, contact an HP storage representative.
  • Page 229: Sun Solaris Multipathing Coexistence Support

    Table 111 Sun Solaris multipathing coexistence support 4000/4100/ 6000/6100/ 8000/8100 XCS 6 x 3000/ 3000/ 2000fc G2 5000 5000 4400 6400/8400 (2300fc) VCS 3 x VCS 4 x XCS 0950 x XCS 09 x MPx- MPx- MPx- MPx- MPx- MPxIO Notes HDLM MSA2000fc...
  • Page 230: Vmware Esx San Rules

    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 112 describes the SAN configuration rules for VMware ESX. Table 112 VMware ESX SAN configuration rules Storage systems ESX SAN rules...
  • Page 231: Xen Citrix San Rules

    Xen Citrix 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 113 describes SAN rules for Xen Table 113 Xen SAN configuration rules Storage systems Xen SAN rules...
  • Page 232: Heterogeneous San Storage System Coexistence

    Heterogeneous SAN storage system coexistence HP supports SANs that contain different storage system types. This section defines rules for mixing storage system types in a SAN. Any combination of storage systems is supported in a SAN, provided that the configuration conforms to all applicable fabric rules.
  • Page 233: Common Server, Common Hba

    For all multipath configurations, all paths for a given LUN must only be accessed by HBAs from the same vendor (for example, Emulex or QLogic, but not both). IBM AIX (Table 104, page 221) Sun Solaris (Table 111, page 229) For all other operating systems, 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.
  • Page 234 “Zoning” on page 266 for XP and VA “Zoning enforcement” on page 421 “Zoning guidelines” on page 421 “EBS zoning” on page 423 “Zone naming” on page 423 Heterogeneous server rules...
  • Page 235: 10 P2000 And Msa Storage System Rules

    10 P2000 and MSA storage system rules This chapter describes specific rules for the following entry-level storage systems: HP StorageWorks Modular Smart Array 2000fc and 2000fc G2, page 235 HP StorageWorks Modular Smart Array 1500, page 239 HP StorageWorks Modular Smart Array 1000, page 243 “HP StorageWorks Modular Smart Array 2000i”...
  • Page 236: Heterogeneous San Support

    Table 115 MSA2000fc configurations Storage system Description MSA2012fc single Used in a direct connect or SAN connect configuration with a standard single controller controller MSA2012fc dual controller Used in a direct connect or SAN connect configuration with standard dual controllers MSA2212fc enhanced dual Used in a direct connect or SAN connect configuration with enhanced dual controller...
  • Page 237: Configuration Rules

    Configuration rules Table 117 lists the MSA2000fc and MSA2000fc G2 storage system rules. Table 117 MSA2000fc and MSA2000fc G2 storage system rules Rule number Description The MSA2000fc, MSA2000fc G2 (MSA2300fc), and P2000 G3 FC are supported in all SAN fabric topology configurations described in this guide. Unless otherwise specified, the MSA2000fc, MSA2000fc G2 (MSA2300fc), and P2000 G3 FC can be configured in a SAN using the switch models listed in this guide.
  • Page 238: Zoning

    Third-party storage zones are governed by product-specific configuration guidelines (see the third- party product documentation). “Third-party switch support” on page 179 for third-party fabric and switch support. “Heterogeneous SAN storage system coexistence” on page 232 for storage system coexistence support. Zoning These zoning rules apply to a heterogeneous SAN with MSA2000fc or MSA2000fc G2 storage systems:...
  • Page 239: Management Software Support

    Contact an HP storage representative for a configuration review to determine support for configurations that exceed the stated limits. Management software support The MSA2000fc and MSA2000fc G2 support target-based management interfaces, including Telnet (CLI), FTP, and a web-based interface. The web-based interface is supported with Microsoft Internet Explorer 6 (or later) and Mozilla Firefox 1.0.7 (or later).
  • Page 240: Homogeneous San Support

    Homogeneous SAN support A single MSA1500 supports homogeneous access with the operating systems listed in Table 119. Each operating system requires a dedicated MSA1500. Standalone servers and clustered servers are supported on the same storage system. Table 119 MSA1500 homogeneous SAN support Storage system Firmware Switches...
  • Page 241: Heterogeneous San Support

    Heterogeneous SAN support A single MSA1500 supports heterogeneous access with any of the operating systems listed in Table 120. Standalone servers and clustered servers are supported on the same storage system. Table 120 MSA1500 heterogeneous SAN support Storage system Firmware Switches Operating systems MSA1500...
  • Page 242: Zoning

    the third party is required if HP will provide a single support point of contact that includes the third-party storage. HP provides technical support for its products and cooperates with the third party's technical support staff, as needed. HP provides best-practices recommendations for connecting devices in the SAN (see “Best practices”...
  • Page 243: Hp Storageworks Modular Smart Array 1000

    Overlapping zones are supported with disk and tape. Separate or common HBAs for disk and tape connections are supported. For a VLS, multiple heterogeneous initiators and multiple ports of the VLS device are supported in the same fabric zone. HP recommends using a separate tape-to-HBA connection for servers with backups that require more than four DLT8000 tape drives or two Ultrium (LTO) tape drives.
  • Page 244: Heterogeneous San Support

    Table 123 MSA1000 homogeneous SAN support Storage system Firmware Switches Operating systems MSA1000 B-series HP OpenVMS active/active C-series HP Tru64 UNIX M-series Novell NetWare 5x, 4x B-series HP-UX MSA1000 C-series active/passive or single controller VMware ESX (4x firmware only) M-series For the latest firmware support information, contact an HP storage representative.
  • Page 245: Heterogeneous Storage System Support

    Rule number Description Unless otherwise specified, the MSA1000 can be configured in a SAN using the switch models listed in this guide. See: Table 10 (H-series) Table 18 through Table 22 (B-series) Table 41 (C-series) Table 60 Table 62 (M-series) Multipathing is supported for the following operating systems: HP-UX OpenVMS...
  • Page 246: Zoning

    Zoning These zoning rules apply to a heterogeneous SAN with MSA1000 storage systems: Zoning is required for all operating systems that access an MSA1000. See “Heterogeneous server rules” on page 185. An MSA1000 storage system can be in multiple operating system zones. For configurations that support common server access to multiple storage system types, see “Common server access”...
  • Page 247: 11 Eva Storage System Rules

    11 EVA storage system rules This chapter describes specific rules for the following storage systems: EVA3000/5000 EVA4000/4100 EVA4400 EVA6000/6100 EVA8000/8100 EVA6400/8400 This chapter describes the following topics: EVA storage systems, page 247 EVA data migration, page 253 HP Continuous Access EVA SAN integration, page 254 Zoning, page 256 EVA SAN boot...
  • Page 248: Heterogeneous San Support

    Heterogeneous SAN support EVA HSV-based controller storage systems support shared access with any combination of operating systems listed in Table 127. Table 127 EVA heterogeneous SAN support Switches Storage systems Firmware Operating systems EVA3000/5000 VCS 4x, 3x B-series Apple Mac C-series HP-UX EVA4000/4100...
  • Page 249 Rule number Description For SANs with more than 1,024 HBAs, an HSV controller must be zoned for a maximum of 1,024 HBAs. Add a zone to a SAN to satisfy the 1,024 HBA limit. When using HP Continuous Access EVA, the zoning limit is 256 HBAs. “Heterogeneous SAN storage system coexistence”...
  • Page 250: Heterogeneous Storage System Support

    Rule number Description EVA XL storage systems using XCS 5.100 (or later) or XCS 9.000 (or later) are supported in configurations with a combination of fabric attached and direct connect servers (direct connect uses no Fibre Channel switch). This is subject to the system maximum for host connections. EVA XL storage system support includes support for mixed Fibre Channel speeds on different host ports (8 Gb/s, 4 Gb/s, and 2 Gb/s) when using 4 Gb/s controllers.
  • Page 251: Maximums

    the third party is required if HP will provide a single support point of contact that includes the third-party storage. HP provides technical support for its products and cooperates with the third party's technical support staff, as needed. HP provides best-practices recommendations for connecting devices in the SAN (see “Best practices”...
  • Page 252: Eva Single-Server Maximum Configurations

    For additional information about EVA maximums, see the HP StorageWorks Enterprise Virtual Array compatibility reference. A LUN presentation is the number of hosts presented to, regardless of how many adapters are in each host. For example, if a LUN is presented to eight hosts, that LUN has eight LUN presentations. If a LUN is presented to two hosts, that LUN has two LUN presentations.
  • Page 253: Eva Data Migration

    1, 2 3, 4 Storage systems Operating systems EVA storage systems per HBA LUNs per HBA target For the supported operating system versions, see “Heterogeneous server rules” on page 185. The maximum number of HBAs supported per server depends on the server model. (See the server documentation.) For Tru64 UNIX, the maximum is 64 HBAs per server when using 5.1a (or earlier), 255 HBAs per server when using 5.1b (or later).
  • Page 254: Hp Continuous Access Eva San Integration

    NOTE: The MPX200 data migration has a unique fan-in/fan-out licensing model. Using this particular license, you can migrate data from multiple arrays to a single array or from a single array to multiple arrays, three times; that is, this license can enable three different migration tasks using the same MPX200 chassis at different times.
  • Page 255: Heterogeneous Storage System Support

    Rule number Description Shared usage of HP Continuous Access EVA-configured storage systems by non-HP Continuous Access EVA-configured servers (for example, a single HBA or an operating system without multipathing support) or non-HP Continuous Access EVA-supported operating systems is not suppor- ted.
  • Page 256: Zoning

    Zoning These zoning rules apply to a heterogeneous SAN with EVA storage systems: Zoning is required for all operating systems that access EVA storage systems. See “Heterogeneous server rules” on page 185. EVA storage systems can be in multiple operating system zones. For configurations that support common server access to multiple storage system types, see “Common server access”...
  • Page 257: Storage Management Server Configuration Rules

    NOTE: Command View EVA 6.0 (or later) includes a more flexible security feature, which requires the establishment of read/write (ability to manipulate storage) and/or read-only accounts. Before using Command View EVA, be sure to review and implement the Command View account security feature setup procedures.
  • Page 258: Cabling

    Cabling This section describes cabling options for high-availability multipathing configurations for EVA storage systems. Level 4 NSPOF configuration Figure 67 through Figure 71 show cabling options when implementing a level 4, high-availability, NSPOF configuration. For a description of availability levels, see “Data availability”...
  • Page 259: Eva4000/4100/6000/6100 And Eva3000/5000 Vcs 4X Straight-Cable, High-Availability Configuration

    25130b Figure 68 EVA4000/4100/6000/6100 and EVA3000/5000 VCS 4x straight-cable, high-availability configuration SAN Design Reference Guide...
  • Page 260: Eva4400 9X Straight-Cable Configuration

    Figure 69 shows the physical connections for a straight-cable, high-availability NSPOF configuration for EVA4400 storage systems. This cabling scheme is also supported for HP Continuous Access EVA. 26408a Figure 69 EVA4400 9x straight-cable configuration Figure 70 shows the cabling scheme for both non-HP Continuous Access EVA and HP Continuous Access EVA configurations for EVA8000/8100 storage systems.
  • Page 261: Dual-Channel Hba Configurations

    Figure 71 shows an EVA8000/8100 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. Path failover is available between Fabric A and Fabric B. SAN 2 represents a second dual-redundant SAN with Fabric C and Fabric D.
  • Page 262: Single Pci Slot With Dual-Channel Hba And Two Switches

    Dual-channel Port 1 Port 2 Targets C, D, or Targets A, B,... Targets A, B,... 25138b Figure 73 Single PCI slot with dual-channel HBA and two switches Figure 74 shows a sample NSPOF solution with two dual-channel HBAs. This availability solution is equivalent to using two single-channel HBAs.
  • Page 263: 12 Xp And Va Storage System Rules

    12 XP and VA storage system rules This chapter describes specific rules for the following storage systems: XP24000 VA7410 XP20000 VA7400 XP12000 VA7110 XP10000 VA7100 XP1024 XP128 XP512 XP48 This chapter describes the following topics: XP and VA storage systems, page 263 Configuration rules, page 265 XP and VA SAN boot...
  • Page 264: Heterogeneous San Support

    Heterogeneous SAN support XP and VA storage systems support shared access with any combination of operating systems listed Table 134. Table 134 XP and VA heterogeneous SAN support Storage systems Firmware version Switches Operating systems HP22 B-series HP-UX (except 4 Gb/s switches) VA7410 C-series IBM AIX...
  • Page 265: Configuration Rules

    Configuration rules Table 135 describes XP and VA storage system rules. Table 135 XP and VA storage system rules Rule number Description XP and VA storage systems are supported in all SAN fabric topology configurations described in this guide. Unless otherwise specified, XP and VA storage systems can be configured in a SAN using the switch models listed in this guide.
  • Page 266: Heterogeneous Storage System Support

    Heterogeneous storage system support HP supports HP storage products on shared hosts, and HBAs in HP fabric environments that also have third-party storage products. A third-party cooperative support agreement between HP Services and the third party is required if HP will provide a single support point of contact that includes the third-party storage.
  • Page 267: Xp And Va Storage Systems With Tape Storage In A Shared Fabric

    HP-UX Windows Solaris NetWare All supported switches FC bridge 25140b Figure 75 XP and VA storage systems with tape storage in a shared fabric SAN Design Reference Guide...
  • Page 268: Xp And Va San Boot Support

    XP and VA SAN boot support XP and VA LUNs can be booted from the SAN using B-series, C-series, and M-series switches. SAN boot through the B-series MP Router is not supported. Support for booting from the SAN depends on: Firmware Operating system and version Fibre Channel port speed...
  • Page 269 Enables you to limit access between hosts and array LUNs Uses host WWNs to identify host access by LUN Provides LUN security at the array level to secure data Provides consolidated and consistent data access management, independent of the switch vendor Improves boot performance during ioscan by limiting the visibility between the host and targets SAN Design Reference Guide...
  • Page 270 XP and VA storage system rules...