Cascaded to ring

If you have a linear cascaded fabric SAN, connect the last switch in the fabric to the first switch to create a ring fabric SAN. If you have a tree-like cascaded fabric SAN (with multiple levels), you may need to re-cable the ISLs.

Cascaded to core-edge

Determine which switches will be the backbone switches and which ones will be the edge switches. Re-cable the ISLs to connect all edge switches to the core switches. Connect devices (servers and storage) or core switches, as required. This migration is less disruptive if you use the existing switches as edge switches and add switches as core switches.
Migrating a meshed fabric SAN
This section describes migration paths for a meshed fabric SAN.

Meshed to ring

You can migrate a meshed fabric SAN to a ring fabric SAN by removing the cross-connected ISLs and leaving the outer-connected ISLs as a ring. Use the available ports for device connections or for redundant ring ISL connections.

Meshed to core-edge

Use the method described in Cascaded to core-edge (page 43).
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.

Ring to core-edge

This migration is less disruptive if you have two ISLs between all switches in the ring fabric SAN. Use the method described in Cascaded to core-edge (page 43).

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 44) SAN scaling and routing (page 45) Fibre Channel routing implementations (page 47) Fabric redundancy and routing (page 52) Supported routing configurations (page 53)
Fibre Channel routing overview
Fibre Channel routing facilitates the development and management of higher-capacity SANs, significantly increasing device connectivity. By enabling communication between two or more physically independent fabrics, multiple logical fabrics, or VSANs, routing provides high levels of SAN scalability. Each fabric, logical fabric, or VSAN maintains a unique fabric services configuration. NOTE: In the context of Fibre Channel routing, the terms "fabric," "Virtual Fabric," and "VSAN" are used interchangeably. HP does not support using the B-series Fibre Channel routing, 1606 Extension SAN Switches or DC Dir Switch MP Extension Blades, Multi-protocol Routers, or B-series Virtual Fabrics-IFR with C-series IVR functionality in the same SAN configuration. HP only supports routing devices connected to H-series switches through TR_Ports to devices in B-series and C-series fabrics. Routing enables independent fabrics, Virtual Fabrics with IFR, or VSANs with IVR to dynamically share devices without the need to reconfigure or re-cable physical connections. Routed fabrics, Virtual Fabrics with IFR, or VSANs with IVR can consolidate management interfaces. Instead of one management interface per fabric, there can be one per SAN, or two per SAN, if redundant fabrics are used. Routing using the TR feature of the H-series switches does not provide consolidated management of the routed fabric. Fibre Channel routing features include: Increased SAN scalability

25152b

VSANs can be connected through IP using the FCIP functionality of the C-series Fibre Channel switches. See C-series Fibre Channel switches (page 110). Figure 30 (page 56) shows IVR connecting VSANs through IP. Figure 30 IVR connecting VSANs through IP
VSAN 1 VSAN 2. VSAN n FC Switch (IVR) IP FCIP with IVR
VSAN 1 VSAN 2. VSAN n FC Switch (IVR)

25111a

High-availability router configurations
In high-availability configurations, use pairs of 8 Gb/s switches with integrated Fibre Channel routing, 1606 Extension SAN Switches, routers, or IFL pairs to provide redundant paths between fabrics. Figure 31 (page 57) and Figure 32 (page 58) show valid configurations. The first configuration shows servers and storage connected using a pair of redundant fabrics in a level 4 NSPOF configuration. For information about high-availability levels, see Data availability (page 39). The second configuration shows routers cross-wired to provide full fabric connectivity in case a router fails. The third configuration shows multiple IFLs between the 1606 Extension SAN Switch or MP Router and edge fabrics to provide redundancy in case an IFL or MP Router port fails.
The configurations show a small number of SAN fabrics connected to each router. The same principles apply to configurations with a higher number of fabrics connected to a router, and a higher number of routers in a Meta SAN. For scalability rules, such as the maximum number of fabrics and MP Routers, see B-series switches and fabric rules (page 81).
Figure 31 High-availability 1606 Extension SAN Switch configurations
NSPOF configuration 1606 Extension SAN Switch

26597b

Figure 32 High-availability MP Router configurations
400 MPR or MPR (FC Routing)
NSPOF configuration 400 MPR or MPR (FC Routing)

25112c

400 MP Router and MP Router Blade use cases
For configuration examples, see the 400 MP Router and MP Router Blade use-case white papers: http://h18006.www1.hp.com/storage/whitepapers.html
H-series switches with TR configurations
The TR feature allows you to configure each 8 Gb port on the H-series switch as a TR_Port, enabling the sharing of server and storage resources between fabrics through the industry-standard NPIV protocol. The TR feature also provides a higher level of security by ensuring that only customer-specified devices are visible and shared between fabrics. Figure 17 (page 48) shows how an H-series switch can be in a fabric with other H-series switches and how you can connect it to multiple remote B-series or C-series fabrics. Figure 21 (page 52) shows how you can map each device connected to an H-series switch to multiple devices connected in one remote B-series or C-series fabric.

6.4.1b 6.4.1a 6.4.1 6.4.0c 6.4.0b 6.4.0a 6.3.2b 6.3.2a 6.3.2 6.3.1c 6.3.1b 5.53 10.4.5 10.3.4
2 internal 10 external 16 at 1, 2, or 4 Gb/s Fibre Channel 2 at 1-GbE FCIP
HP StorageWorks Multi-protocol Router Blade
HP StorageWorks iSCSI Director Blade
6.3.1a 6.3.0d 6.2.2e 6.2.2d 6.2.2c 6.2.2b
8 at 1, 2, or 4 Gb/s Fibre Channel 8 at 1-GbE iSCSI
FM = Fabric Manager DCFM = Data Center Fabric Manager Using HP StorageWorks Fabric Manager (FM) 5.5 or earlier with Fabric OS 6.1.1 or later can result in problems with Zoning, Performance monitoring, SYSLOG configuration, FICON wizards, IOD Delay, AAA replication, Port enable/disable, and other functions. Fabric Manager is not recommended for fabrics running these versions of Fabric OS, and is not supported with Fabric OS 6.3 or later.
Table 21 B-series legacy Fibre Channel switches and routers
Fabric Management Legacy HP switch name HP StorageWorks 400 Multi-protocol Router HP StorageWorks 4/32B SAN Switch full/power pack HP StorageWorks 4/32B SAN Switch base HP StorageWorks SAN Switch 4/32 base/full HP StorageWorks 4/32 SAN Switch power pack HP StorageWorks 4/64 SAN Switch base/power pack HP StorageWorks 4/64 SAN Switch full HP StorageWorks 4/8 SAN Switch base/full HP StorageWorks 4/16 SAN Switch full/power pack Brocade 4Gb SAN Switch for HP c-Class BladeSystem Brocade 4Gb SAN Switch for HP p-Class BladeSystem HP StorageWorks MSA SAN Switch 2/8 HP StorageWorks 2/128, 2/128 SAN Director power pack 3.2.1c4 5.3.2c 5.3.2b N/A 10.4.5 10.3.8 or 16 at 1 or 2 Gb/s Fibre Channel or 1-GbE N/A (see Table 33 (page 105) for scalability rules) 6.2.2e 6.2.2d 6.2.2c 6.2.2b 1 to 16 internal 1 to 8 external 8 internal 4 external 8 5.53 6.4.1b 6.4.1a 6.4.1 6.4.0c 6.4.0b 6.4.0a 6.3.2b 6.3.2a 6.3.2 6.3.1c 6.3.1b 6.3.1a 6.3.0d 6.2.2e 6.2.2d 6.2.2c 6.2.2b 10.4.5 10.3.4 32/48/32 16/to 32 Firmware versions FM1 DCFM2 Number of ports 16 at 1, 2, or 4 Gb/s Fibre Channel 2 at 1-GbE 32
HP StorageWorks Multi-protocol Router5, 6

7.4.1f 7.4.1e

FM = Fabric Manager DCFM = Data Center Fabric Manager Using HP StorageWorks Fabric Manager (FM) 5.5 or earlier with Fabric OS 6.1.1 or later can result in problems with Zoning, Performance monitoring, SYSLOG configuration, FICON wizards, IOD Delay, AAA replication, Port enable/disable, and other functions. Fabric Manager is not recommended for fabrics running these versions of Fabric OS, and is not supported with Fabric OS 6.3 or later. You cannot manage these switches with DCFM. A minimum of firmware 7.4.1 is required for fabric compatibility with switch firmware 5.1x (or later). You cannot manage this router with DCFM.
Features of the B-series Fibre Channel switches include: Access Gateway ModeProvides connectivity to B-series or other switch-series fabrics that support NPIV. The following B-series Fibre Channel switches support Access Gateway Mode: Brocade 8Gb SAN Switch for HP BladeSystem c-Class, Brocade 4Gb SAN Switch for HP c-Class BladeSystem, HP StorageWorks SAN Switch 4/8 (with 16 ports enabled), 4/16, 8/8 (with 24 ports enabled), 8/24, 8/40 (with 40 ports enabled and 6.2.0a or later), and HP StorageWorks 2408 FCoE Converged Network Switch (Fibre Channel ports with 6.3.1a or later). Advanced Performance MonitorAnalyzes resource utilization throughout the fabric. Advanced WebToolsCentralizes and simplifies switch management through a browser-based application. Advanced ZoningProvides secure access control over fabric resources. Uses the switch hardware to enforce port and WWN zoning. Extended FabricsEnhances performance for Fibre Channel SAN connectivity for distances greater than 1 km (8 Gb/s), 2.5 km (4 Gb/s), 5 km (2 Gb/s), and 10 km (1 Gb/s) to improve disaster recovery operations and ensure business continuity. Extended fabric support for distances up to 10 km is provided in all B-series switches. For distances greater than 10 km, an Extended Fabrics license is required. For maximum supported distances based on the link speed, see SAN fabric connectivity and switch interoperability rules (page 142). Fabric ManagerCentralizes fabric management through a host-based application. This is a legacy product, currently in sustaining mode only. Data Center Fabric Manager (DCFM)Centralizes fabric management through a host-based application. This is available free for single-fabric management (DCFM Professional), or for purchase for multiple-fabric management and increased device count (DCFM Professional Plus and DCFM Enterprise).
NOTE: See Table 19 (page 83) through Table 21 (page 85) for switch models supported with Fabric Manager and DCFM. Fabric WatchProactively monitors the health and performance of switches and the fabric. ISL TrunkingCombines 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 TrunkingAllows 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. FCIP tunnels using 1-GbE ports can have up to four FCIP circuits spread over four 1-GbE ports. FCIP tunnels using 10-GbE ports can have up to ten FCIP circuits per 10-GbE port. Each FCIP circuit supports four QoS classes as a TCP connection (Class-F, Hi, Medium, and Low priority). NOTE: FCIP Trunking is supported only on the 1606 Extension SAN Switch and the DC Dir Switch MP Extension Blade. For more information, see B-series 1606 Extension SAN Switch and DC Dir Switch MP Extension Blade (page 274). Adaptive Rate LimitingDynamically adjusts data transmission through the TCP connections in a FCIP tunnel, based on preconfigured minimum and maximum data rates and by taking feedback from the quality of the TCP connections. This allows FCIP connections to use the maximum bandwidth available while providing a minimum bandwidth guarantee.

Table 56 (page 133) lists zoning limits for H-series switches. See also Zoning (page 371). Table 56 H-series switch zoning limits
Description Maximum number of zone sets is 256. Maximum number of zones is 2,000. Maximum number of zones in a zone set is 2,000. Maximum number of zone members in a zone is 2,000. Maximum number of zone members per fabric is 10,000.
Table 57 (page 134) describes zoning enforcement for H-series switches. Table 57 Zoning enforcement for H-series switches
Switch Configuration Define zones using domain number and port number Enforcement Comments
Access authorization at frame level Hard zoning1 in hardware
HP StorageWorks SN6000 Access authorization at frame level Fibre Channel Switch Hard zoning1 Define zones using WWNs only in hardware HP StorageWorks 8/20q Fibre Channel Switch Define zones using combination Name Server directory-based of domain/port numbers and Soft zoning authentication WWNs
1 Zoning is hardware enforced only on a switch port or device that is a member of no more than 8 zones whose combined membership does not exceed 64. Zoning is hardware enforced on a switch port if the number of logged-in devices plus the number of zone members with access to that port is 64 or less. If these requirements are not met, the port implements soft zoning.
8 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 135) Fibre Channel fabric rules (page 138) NOTE: For information about using switches from the different series in the same SAN or the same fabric, see SAN fabric connectivity and switch interoperability rules (page 142).
M-series switches: Can be core or edge switches. When configured in a core-edge fabric topology, a core switch typically connects to other switches in the SAN; an edge switch typically connects to servers and storage. Have 10, 12, 24, 32, 64, or 140 ports. Include entry-level and high-availability switches. Use the same level of internal firmware for the same switch models. Support plug-and-play compatibility. Support iSCSI and FCIP. See iSCSI storage (page 308) and SAN extension (page 243). For information about switch model support with iSCSI and FCIP, contact an HP storage representative. High availability Scalability Cost efficiency
The M-series switches offer:
The M-series switches typically use the numbering scheme x/y: xThe highest speed at which the switch ports can operate, measured in Gb/s yThe 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. For example, when you connect a 4 Gb/s or 2 Gb/s port directly to a 1 Gb/s port, both ports run at 1 Gb/s in each direction. If the ports are not directly connected, the fabric switch that connects the ports determines the signaling speed.

Total channel insertion loss 3.0 dB 3.85 dB

200 m 500 m 10 km

0.75 dB 7.8 dB 21.5 dB 19 dB 35 km 100 km
9/125 micron (single-mode)
Storage product interface, switches, and transport distance rules
Table 75 (page 146) through Table 79 (page 148) and Table 82 (page 149) and Table 83 (page 150) describe the maximum distances supported for each cable segment type (switch-to-switch or device-to-switch) for each interface and transport type. Unless otherwise specified, the distances specified apply to both switch-to-switch (ISL) connectivity and device-to-switch connectivity. Table 75 (page 146) describes the distance rules for 8 Gb/s Fibre Channel connections when using 8 Gb/s Fibre Channel switch models. Table 75 Fibre Channel distance rules for 8 Gb/s switch models (B-series, C-series, and H-series)
Interface/transport OM2 fiber 50 m at 8 Gb/s 50 micron multi-mode fiber optic cable and short-wave 150 m at 4 Gb/s SFP+ transceivers 300 m at 2 Gb/s 500 m at 1 Gb/s 62.5 micron1 multi-mode fiber optic cable and short-wave SFP+ transceivers
Supported distances OM3, OM3+ fiber 150 m at 8 Gb/s 380 m at 4 Gb/s 500 m at 2 Gb/s
Supported storage products
OM1 fiber 21 m ISL at 8 Gb/s Heterogeneous SAN servers, Fibre Channel switches, and storage systems
10 km ISL at 8 Gb/s (H-series with additional buffer credits HP Continuous Access EVA allocated)2 and XP Continuous Access 10 km ISL at 8 Gb/s (B-series and C-series only) (B-series and C-series only) 9 micron single-mode fiber optic cable and long-wave 25 km ISL at 8 Gb/s (B-series only) SFPs 3.3 km ISL at 8 Gb/s (H-series only, base switch) 6.6 km ISL at 4 Gb/s (H-series only, base switch) 10 km ISL at 2 Gb/s (H-series only, base switch) 40 km ISL at 8 Gb/s (B-series only) Fibre Channel using WDM3
100 km ISL at 4 Gb/s 250 km at 2 Gb/s
Information for 62.5 micron fiber optic cable is provided to facilitate use of installed cable. HP recommends 50 micron fiber optic cable for new installations that require multi-mode fiber. You can use EFMS to allocate more buffer credits to ports of an H-series switch to achieve increased distance up to the limit of the SFP capability. WDM distance is the maximum distance for the WDM link.
Table 76 (page 147) describes the distance rules for 10 Gb/s Fibre Channel ISL connections when using 8 Gb/s Fibre Channel switch models with 10 Gb/s ISL ports.

When adding EVA storage systems to a zone, use the controller port WWNs when implementing a straight-cable configuration. Use the storage system WWN when implementing a cross-cable configuration. For more information, see Cabling (page 218) and the HP StorageWorks Continuous Access EVA Administrator Guide.
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 (page 154). 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 195). Table 128 (page 217) lists zoning rules for heterogeneous SANs with EVA storage systems. Table 128 EVA configuration zoning rules
Description If a storage management server resides in the fabric, each operating system type must be in a separate zone or VSAN. For more information, see Storage management server integration (page 217). For C-series switches, each operating system type must be in a separate zone or VSAN.
The following rules apply to tape storage support in a SAN with EVA storage systems: 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.

EVA SAN boot support

For current storage system support, see the Boot from SAN website at http:// h18006.www1.hp.com/storage/networking/bootsan.html and the SPOCK website at http:// www.hp.com/storage/spock. For the SPOCK website, you must sign up for an HP Passport to enable access. For Continuous Access EVA, if the operating system supports boot from SAN, replication of the boot disk is supported. SAN boot through the B-series MP Router is not supported.
Storage management server integration
A management server is required to manage an EVA storage system. The management server can be an SMA, GPS, management station (dedicated server), or HP Storage Server. The management server communicates with storage systems in-band through a Fibre Channel connection. 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. Once you enable security, you cannot disable it. Table 129 (page 218) describes the rules for using a management server for EVA storage systems.

HP storage replication products
HP provides the following storage replication products: Continuous Access EVA with the EVA4000/4100/4400/6000/6100/6400/8000/8100/8400 using XCS Continuous Access EVA with the EVA3000/5000 using VCS XP Continuous Access with the XP family of storage systems OpenVMS host-based volume shadowing
The following products are qualified by HP as Fibre Channel routers, network gateways, or iSCSI bridges with the EVA storage system: 1606 Extension SAN Switch, DC Dir Switch MP Extension Blade, 400 MP Router, MP Router Blade, and MP Router are qualified as FCIP gateways and Fibre Channel routers. The 1606 Extension SAN Switch, DC Dir Switch MP Extension Blade, 400 MP Router, and MP Router Blade are also qualified as Fibre Channel switches. C-series IP Storage Services Modules (IPS-4, IPS-8), 14/2 Multiprotocol Services Module, MDS 9216i, and MDS 9222i switches are qualified as an FCIP gateway and an iSCSI bridge. MDS 9216i and MDS 9222i switches are also qualified as Fibre Channel switches. MPX200 Multifunction Router is qualified as an FCIP gateway. HP IP Distance Gateway is qualified as an FCIP gateway.

282 SAN extension

The following sections describe network requirements for replication products with qualified gateways: SAN extension best practices for Continuous Access EVA (page 283) Continuous Access EVA4400/6400/8400 with XCS 09x (page 283) Continuous Access EVA with XCS 6.x (page 286) Continuous Access EVA with VCS 4.x (page 288) P9500 and XP Continuous Access (page 291) OpenVMS host-based volume shadowing (page 305)
SAN extension best practices for Continuous Access EVA
HP recommends you consider the following best practices when implementing SAN extension using FCIP with Continuous Access EVA: Separate host traffic from replication traffic in environments that employ FCIP gateways. This decouples the host I/O from throughput on the inter-site link. This can be achieved in the following ways: Use separate switches and separate fabrics for host and replication I/O (preferred solution). Replication zones can be set up through fabric zoning. Using standard fabric zoning, the host traffic is separated from the replication traffic.
For high availability and no single point of failure, the best practice is to deploy a 6-fabric solution, where there are two inter-site links. This solution uses separate switches for the replication and host fabrics. At least one of the EVAs must be an EVA8x00. Two fabrics that are dedicated to replication and four fabrics are dedicated to host I/O traffic. If only a single ISL is available, then a 5-fabric configuration can be used. This solution requires using separate switches for the host and replication fabrics. Only one fabric would be dedicated to replication traffic. Use a 2-fabric (dual fabric) configuration only if the host traffic cannot be separated from the replication traffic. This is recommended only when the customer business requirements permit it. Take care when designing a 2-fabric configuration over FCIP links, as host port blocking can occur.

iSCSI boot is supported for the following operating systems and network interface cards: Microsoft Windows Server 2003 SP2 Red Hat Enterprise Linux 4 AS, Update 7, Update 6, Update 5, and Update 4 SUSE Linux Enterprise Server 9 SP4, SP3
SUSE Linux Enterprise Server 10, 10 SP2, SP1 QLogic QLA4052C, QLE4062C, QMH4062C iSCSI HBA is supported on the following operating systems: Microsoft Windows Server 2008, 2003 SP2 Red Hat Enterprise Linux 5, Update 2, Update 1

334 iSCSI storage

Red Hat Enterprise Linux 4 AS, Update 7, Update 6, Update 5 SUSE Linux Enterprise Server 10, 10 SP2, SP1 SUSE Linux Enterprise Server 9 SP4, SP3
EVA and EVA4400 iSCSI Connectivity Options supported maximums
Table 194 (page 335) lists the maximums supported by the EVA and EVA4400 iSCSI Connectivity Options using the mpx100/100b bridge. Table 194 Supported EVA iSCSI Connectivity Option maximums
Description Maximum per EVA or EVA4400 iSCSI Connectivity Option Hardware EVA storage system mpx100/100b Configuration mpx100150 (single-path or multipath) Total number of iSCSI initiators mpx100b (EVA4400 only)16, 48 (license upgrade 1), 150 (license upgrade 2) (single-path or multipath) Note: The mpx100/100b can serve both single-path and multipath LUNs concurrently. Total number of iSCSI LUNs Total number of iSCSI targets per initiator 150 8
General rules for the EVA and EVA4400 iSCSI Connectivity Options
NOTE: The EVA iSCSI Connectivity Option (mpx100) is supported with EVA4000/4100/4400/4400 (embedded switch)/6000/6100/6400/8000/8100/8400 and EVA3000/5000 storage systems. The EVA4400 iSCSI Connectivity Option (mpx100b) is supported with EVA4400 and EVA4400 (embedded switch) storage systems. Use the following general rules when implementing the EVA or EVA4400 iSCSI Connectivity Option: Each EVA storage system can have a maximum of two mpx100 or two mpx100b bridges. Each EVA controller host port can connect to a maximum of two mpx100/100b Fibre Channel ports. Both mpx100/100b Fibre Channel ports can only connect to one EVA storage system. Each mpx100/100b Fibre Channel port can only connect to one EVA port. Each iSCSI initiator can have a maximum of eight mpx100/100b iSCSI targets.
Table 195 (page 336) describes the maximum number of servers, initiators, and LUNs supported for combined iSCSI and Fibre Channel connectivity to an EVA configured with an mpx100 or 100b.
HP iSCSI bridge products 335
Table 195 Supported EVA/mpx100/100b maximums
EVA with Fibre Channel only Maximum number of servers Maximum number of initiators Maximum number of LUNs2
EVA with Fibre Channel and 1GbE iSCSI (mpx100) 405 with 1 EVA
EVA4400 with Fibre Channel and 1GbE iSCSI (mpx100b) 271, 303, 405 with 1 EVA1
1,170 with 1 EVA 150 iSCSI 1,023 EVA4x00/6000/6100/ 8000/8100 2,047 EVA6400/8400

HP ProLiant Storage Server iSCSI license upgrade options
The HP ProLiant Storage Server iSCSI Feature Pack has three licensed options: Snapshot (page 345) Clustering (page 346) Direct Backup (page 346)
Snapshot The Snapshot option is an upgrade license for HP ProLiant Storage Server iSCSI Feature Pack. The Snapshot option: Works with Microsoft iSCSI initiators only. Prevents accidental deletions, file corruption, and virus attacks. Pauses application hosts running Microsoft Exchange, SQL Server, or Oracle Database to ensure data integrity.
HP iSCSI bridge products 345
Allows delta snapshots using Microsoft VSS interface, and performs automatic delta snapshots of application hosts to reduce potential data loss. Offers several application-specific licensed agent options: Microsoft Visual SourceSafe Microsoft Exchange Microsoft SQL Oracle Database (for a single Microsoft iSCSI initiator)
Clustering Clustering is an upgrade license for the HP ProLiant Storage Server iSCSI Feature Pack (Gateway Edition only). The clustering option: Activates two-node iSCSI target capability using MSCS Eliminates a single point of failure with a dual network connection to the IP network and a dual I/O channel to each storage device
Direct Backup The Direct Backup option is an upgrade license for HP ProLiant Storage Server iSCSI Feature Pack. The Direct Backup option: Works with Microsoft iSCSI initiators only Facilitates centralized, zero-impact backup Allows administrators to use their preferred backup software for centralized backup and recovery of application data directly from the iSCSI storage server
Designing a Microsoft Exchange solution with iSCSI Feature Pack
A Microsoft Exchange solution requires that you configure the network, host, and storage systems for iSCSI NAS. The HP ProLiant Storage Server iSCSI Feature Pack provides iSCSI functionality on a Windows Storage Server (NAS device). Exchange Server 2003 also requires an iSCSI initiator. Network design Existing IP networks may not be suitable for iSCSI storage support. Evaluate traffic on these networks to determine if there is adequate capacity to meet storage requirements. HP recommends a dedicated GbE network for accessing the Windows iSCSI NAS Storage Server. This provides adequate performance and data security. You can also use IPsec to secure the connection on a public, unsecured network, with decreased performance. The distance between the Exchange server and the iSCSI NAS Storage Server may affect performance. You must check the maximum supported distances of the network devices. The maximum distance varies based on the cable type and specifications. Hardware selection The Windows Server Catalog is available at http://www.windowsservercatalog.com/. It lists iSCSI hardware components that are qualified under the Designed for Windows Logo program, Exchange Server 2003 and Exchange Server 2000.

You can use either the Encryption SAN Switch or the Encryption FC Blade for data encryption as part of the B-series Encryption Switch security platform.
Supported security components
B-series Encryption Switch security platform supports the following software components: Encryption Frame filtering Advanced Zoning WebTools
Enhanced Group Management The B-series Encryption Switch security platform supports the following optional software components: Encryption SAN Switch Power Pack+ Software Bundle (optional) Adaptive Networking Fabric Watch Advanced Performance Monitor Extended Fabrics ISL Trunking Integrated Routing Data Center Fabric Manager Enterprise
B-series Fabric OS security
This section describes the B-series Fabric OS security features for resource protection, data protection, and security validation.
This section describes the B-series Fabric OS resource protection features.

362 Storage security

User management Fabric OS provides two options for authenticating users: Remote RADIUS servicesUsers are managed by a remote RADIUS server. All switches in the fabric can be configured to authenticate against this centralized database. Local user databaseUsers are managed by a local database, which is synchronized manually using the distribute command. This command pushes a copy of the switch's database to all other Fabric OS 5.3.0 (or later) switches in the fabric.
Fabric OS uses RBAC to determine which commands are supported for each user. Secure Shell Fabric OS supports SSH encrypted sessions to ensure security. SSH encrypts all messages, including client transmission of passwords during login. SSH includes a daemon (sshd), which runs on the switch and supports many encryption algorithms, such as Blowfish-CBC and AES. Commands that require a secure login channel must be issued from an original SSH session. Nested SSH sessions will reject commands that require a secure channel. NOTE: Fabric OS 4.1.0 (or later) supports SSH V2.0 (ssh2).
To ensure a secure network, avoid using Telnet or any other unprotected applications to communicate with switches. Hypertext Transfer Protocol over SSL B-series WebTools support the use of HTTPS. The SSL protocol provides secure access to a fabric through web-based management tools like B-series WebTools. Switches configured for SSL grant access to the management tools through HTTPS links. SSL uses PKI encryption to protect data. PKI is based on digital certificates obtained from an Internet CA, which acts as the trusted agent. These certificates are based on the switch IP address or fully qualified domain names. NOTE: If you change the switch IP address or domain name after activating its digital certificate, you may need to obtain and install a new certificate. Browser and Java support Fabric OS 4.4.0 (or later) supports the following browsers for SSL connections: Internet Explorer (Microsoft Windows) Mozilla (Sun Solaris and Red Hat Linux) In countries that allow the use of 128-bit encryption, use the current version of the browser.

Typographic conventions

Table 206 Document conventions
Convention Blue text: Table 206 (page 387) Blue, underlined text: http://www.hp.com Uses Cross-reference links and email addresses Website addresses Keys that are pressed Bold text Text typed into a GUI element, such as a box GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Text emphasis File and directory names Monospace text System output Code Commands, their arguments, and argument values Monospace, italic text Monospace, bold text.

Italic text

Code variables Command variables Emphasized monospace text Indication that the example continues.
Typographic conventions 387
WARNING! CAUTION: IMPORTANT: NOTE: TIP:
Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data. Provides clarifying information or specific instructions.
Provides additional information. Provides helpful hints and shortcuts.

Customer self repair

HP CSR programs allow you to repair your HP product. If a CSR part needs replacing, HP ships the part directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your HP-authorized service provider will determine whether a repair can be accomplished by CSR. For more information about CSR, contact your local service provider. For North America, see the CSR website: http://www.hp.com/go/selfrepair This product has no customer-replaceable components.
388 Support and other resources

Glossary

This glossary defines acronyms and terms used in this guide and is not a comprehensive glossary of computer terms.
Symbols 3DC 3PO A AAA ABM access authorization ACL ACU ADG AES AG arbitrated loop ARL ASIC ATM Authentication, Authorization, and Accounting. A security protocol. Array-based management. A fabric security method that provides frame-level access control in hardware and verifies the SID-DID combination of each frame. Also known as hard zoning. Access control list. A data protection feature used to restrict access to data resources based on defined policies. Array Configuration Utility. A utility used to control LUN access. Advanced Data Guarding. Advanced Encryption Standard. An encryption security technology. Access Gateway. A software-enabled feature that allows B-series Blade switches to function as port aggregators. See FC-AL. Adaptive Rate Limiting. Application-specific integrated circuit. Asynchronous Transfer Mode. A communications networking technology for LANs and WANs that carries information in fixed-size cells of 53 bytes (5 protocol bytes and 48 data bytes). Three Data Center. A storage configuration that uses XP storage systems. Third-party option.
B B-series BB_credits BCN BE Fibre Channel switches manufactured for HP by Brocade Communications Systems, Inc. Buffer-to-buffer credits. Backward Congestion Notification. Back-side path. A path between the Data Path Module and the physical storage (for example, an HP EVA). Storage on the back-end array (SVSP). Boot from SAN.

FC-SP FC-to-ATM FC-to-IP FCC
FCDM FCF FCFW FCID FCIP FCoE FCS FCSA FDISC FE FF Fibre Channel FIP FLOGI FOS FPMA FRU G Gb/s GbE GBIC
Gigabits per second. Gigabit Ethernet. An Ethernet standard for transmitting data at 1 Gb/s. Gigabit interface converter. A hardware module that connects fiber optic cables to a device and converts electrical signals to optical signals.
GLM GPS H H-series HA HACMP/ES HAFM HBA heterogeneous high availability HLDM hop host bus adapter HotCAT HTTPS I ICL iFCP IFL IFR IFZ iLO in-band communication INCITS interswitch link IOA IOAME IOS IPS IPsec iSCSI ISID ISL iSNS IT IVR
Gigabit link module. A 1 Gb/s fiber optic transceiver. General-purpose server.
Fibre Channel switches manufactured for HP by QLogic. High availability. The relative ability of a system to operate continuously, regardless of the type of failure. High Availability Cluster Multiprocessing/Enhanced Scalability. High Availability Fabric Manager. A software tool used to configure and manage fabrics. Host bus adapter. A hardware device that connects the host server to the fabric. A mixed environment that incorporates different operating systems, protocols, architectures, and equipment from different vendors or product families. See HA. Hitachi Dynamic Link Manager. An interswitch link between a pair of Fibre Channel switches. See HBA. Hot Code Activation Technology. An M-series switch feature that provides nondisruptive code activation. Hypertext Transfer Protocol over Secure Socket Layer.
Inter-chassis link. A feature that provides dedicated high-bandwidth links between two DC SAN Backbone Director chassis. Internet Fibre Channel Protocol. Inter-fabric link. A pair of switches that provide redundant paths between fabrics. Inter-fabric routing. A feature used to enable device sharing across Virtual Fabrics or VSANs. Inter-fabric zone. A component in inter-fabric routing that contains exactly three WWN members: the local device, the remote device, and the TR_Port attached to the remote fabric. Integrated Lights Out. An HP ProLiant Storage Server connectivity feature. Communication through the same communications channel as the operational data. International Committee for Information Technology Standards. See ISL. IO Accelerator. I/O adapter module enclosure. Internetwork Operating System (Cisco). C-series Internet Protocol Storage Services Module. Internet Protocol Security. A method of data encryption. Internet Small Computer System Interface. A standard protocol that uses SCSI commands to transfer data over IP networks. Initiator session ID. Interswitch link. A connection from an E-port on one switch to an E-port on another switch. Internet Storage Name Service. An iSCSI client-server discovery protocol. Information technology. Inter-VSAN routing. A C-series topology that provides selective Fibre Channel routing connectivity between devices in different VSANs.