Page 1 P3AG-3972-02ENZ0 FUJITSU Storage ETERNUS DX S5 series Hybrid Storage Systems Design Guide Functions / features / system configuration design...
Page 2: Table Of Contents
Table of Contents Overview....................... 20 Product Lineup ......................... 20 ETERNUS DX60 S5 ............................21 ETERNUS DX100 S5 ............................22 ETERNUS DX200 S5 ............................24 ETERNUS DX500 S5 ............................26 ETERNUS DX600 S5 ............................27 ETERNUS DX900 S5 ............................28 Function Specification List......................29 Basic Functions ..................... 33 RAID Functions .........................
Page 3 Table of Contents Logical Device Expansion..........................77 LUN Concatenation ............................78 Wide Striping ..............................80 Data Encryption........................82 Encryption with Self Encrypting Drive (SED).....................83 Firmware Data Encryption ..........................84 Key Management Server Linkage ........................85 User Access Management......................88 Account Management............................88 User Authentication............................90 Audit Log .................................92 Environmental Burden Reduction.....................
Page 4 Table of Contents iSCSI Security..............................139 Stable Operation ........................139 Quality of Service (QoS) ..........................139 Host Response ...............................141 Storage Cluster...............................142 Data Migration ........................145 Storage Migration............................145 Non-disruptive Storage Migration ..................147 Server Linkage Functions......................149 Oracle VM Linkage ............................149 VMware Linkage ............................150 Veeam Storage Integration..........................155 Microsoft Linkage ............................157 OpenStack Linkage ............................158...
Page 5 Table of Contents Access Control in an NFS Environment ......................182 Access Control in a Shared CIFS/NFS Environment..................183 CIFS Access Permission Settings....................183 File Sharing ..........................184 CIFS Operation ...............................186 NFS Operation..............................188 Home Directories........................189 Quota ............................. 190 Snapshot ..........................192 Backup ...........................
Page 6 Table of Contents Hardware Configurations..................232 Configuration Schematics ....................... 232 Frontend Enclosure......................... 242 Controller Enclosure ....................... 246 ETERNUS DX60 S5 ............................246 ETERNUS DX100 S5/DX200 S5 ........................249 ETERNUS DX500 S5/DX600 S5 ........................252 ETERNUS DX900 S5 ............................255 Controllers ..............................257 Component ..............................264 Drive Enclosure........................266 External Views of a Drive Enclosure .......................266 External Views of a High-Density Drive Enclosure ..................267 Component ..............................270...
Page 7 Table of Contents Release Information ................... 309 Firmware Release Information ....................309 Specifications ..................... 310 Operating Environment ......................310 Supported OSs (in SAN Environments)......................310 Supported OSs (in NAS Environments)......................316 Function Specifications......................318 Volume Specifications............................318 NAS Volume Specifications..........................319 NAS File System Specifications........................319 Function Specification List .................
Page 8 List of Figures Figure 1 Configuration Example of Each ETERNUS DX ....................20 Figure 2 RAID6-FR Concept.............................34 Figure 3 Example of a RAID Group .........................38 Figure 4 Volume Concept ............................40 Figure 5 Hot Spare ..............................42 Figure 6 Hot Spare Selection Criteria (for the ETERNUS DX500 S5/DX600 S5)............45 Figure 7 Hot Spare Selection Criteria –...
Page 9 List of Figures Figure 44 Overview of the AIS Connect Function ....................103 Figure 45 Security Features............................104 Figure 46 Power Synchronized Unit........................105 Figure 47 Wake On LAN ............................106 Figure 48 Example of Advanced Copy ........................107 Figure 49 REC.................................110 Figure 50 Restore OPC............................112 Figure 51 EC or REC Reverse ...........................112 Figure 52...
Page 10 List of Figures Figure 89 Authentication Server..........................174 Figure 90 Process for Acquiring the Authentication Information (CIFS)..............177 Figure 91 Process for Acquiring the Authentication Information (NFS) ..............178 Figure 92 Home Directories............................189 Figure 93 Quota (for Each User or Group) ......................190 Figure 94 Quota (for Each Shared Folder) ......................191 Figure 95 Snapshot ..............................193...
Page 11 List of Figures Figure 128 Enclosure Connection Path (When Only One Controller Is Installed)............238 Figure 129 Enclosure Connection Path (When Two Controllers Are Installed) ............238 Figure 130 Enclosure Connection Paths (ETERNUS DX500 S5)..................239 Figure 131 Enclosure Connection Paths (ETERNUS DX600 S5)..................240 Figure 132 Enclosure Connection Paths (ETERNUS DX900 S5)..................241 Figure 133...
Page 12 List of Figures Figure 170 Fan Expander Module ..........................270 Figure 171 Power Supply Unit (AC Power Type)......................271 Figure 172 Power Supply Unit (DC Power Type) .......................271 Figure 173 Power Distribution Unit (AC8A/200V, 1U, 4 Outlets)................275 Figure 174 Power Distribution Unit (AC16A/200V, 2U, 16 Outlets)................276 Figure 175 Power Distribution Unit (AC24A/200V, 2U, 16 Outlets)................277 Figure 176...
Page 13 List of Tables Table 1 Specifications (ETERNUS DX60 S5) ......................21 Table 2 Specifications (ETERNUS DX100 S5 [AC Power Type]) ................22 Table 3 Specifications (ETERNUS DX100 S5 [DC Power Type])................23 Table 4 Specifications (ETERNUS DX200 S5) ......................24 Table 5 Specifications (ETERNUS DX500 S5) ......................26 Table 6 Specifications (ETERNUS DX600 S5) ......................27 Table 7...
Page 14 List of Tables Table 43 ETERNUS Web GUI Operating Environment ....................97 Table 44 Levels and Contents of Events That Are Notified ..................100 Table 45 SNMP Specifications ..........................101 Table 46 Control Software (Advanced Copy) ......................107 Table 47 Characteristics of SnapOPC/SnapOPC+ Operations with Each Type of Copy Destination Logical Volume..............................108 Table 48 REC Data Transfer Mode .........................110...
Page 15 List of Tables Table 83 Recovery Requirements After a Link Down State for All Member Ports ...........227 Table 84 Maximum System Memory Capacity for Each Controller .................257 Table 85 Capacity and Number of BUDs for Each Controller ..................258 Table 86 Maximum Number of Host Interfaces per Controller ................259 Table 87 Host Interface Specifications ........................259...
Page 16 List of Tables Table 121 Maximum Number of TPPs/NAS TPVs (NAS Volumes) That Can Be Created (For the ETERNUS DX100 S5/DX200 S5 and the ETERNUS DX500 S5/DX600 S5) ..............319 Table 122 NAS File System Specifications (Max.)....................319 Table 123 List of Supported Protocols........................321 Table 124 Target RAID Groups/Pools of Each Function ....................322 Table 125...
Page 17 Preface Fujitsu would like to thank you for purchasing the FUJITSU Storage ETERNUS DX60 S5/DX100 S5/DX200 S5, ETERNUS DX500 S5/DX600 S5/DX900 S5 Hybrid Storage Systems (hereinafter referred to as ETERNUS DX). The ETERNUS DX is designed to be connected to Fujitsu servers (Fujitsu SPARC Servers, PRIMEQUEST, PRIMERGY, and other servers) or non-Fujitsu servers.
Page 18 Preface Trademarks Third-party trademark information related to this product is available at: https://www.fujitsu.com/global/products/computing/storage/eternus/trademarks.html About This Manual Intended Audience This manual is intended for field engineers or system administrators who design ETERNUS DX systems or use the ETERNUS DX. Related Information and Documents The latest information for your model is available at: https://www.fujitsu.com/global/support/products/computing/storage/manuals-list.html...
Page 19 Preface Warning Signs Warning signs are shown throughout this manual in order to prevent injury to the user and/or material damage. These signs are composed of a symbol and a message describing the recommended level of caution. The following explains the symbol, its level of caution, and its meaning as used in this manual. This symbol indicates the possibility of serious or fatal injury if the ETERNUS DX is not used properly.
Page 20: Overview
This chapter provides an overview and describes the features of the ETERNUS DX. Product Lineup The ETERNUS DX S5 series is a family of Hybrid Storage Systems ranging from entry to midrange models. Figure 1 Configuration Example of Each ETERNUS DX...
Page 21: Eternus Dx60 S5
1. Overview Product Lineup ETERNUS DX60 S5 This section provides the storage system specification of the ETERNUS DX60 S5. Table 1 Specifications (ETERNUS DX60 S5) Item ETERNUS DX60 S5 Physical capacity (max.) (*1) SAS disks 230TB Nearline SAS disks 1,344TB SSDs (*2) 30.7TB Number of controllers...
Page 22: Eternus Dx100 S5
1. Overview Product Lineup ETERNUS DX100 S5 This section provides the storage system specification of the ETERNUS DX100 S5. Table 2 Specifications (ETERNUS DX100 S5 [AC Power Type]) Item ETERNUS DX100 S5 Physical capacity SAS disks 346TB (max.) (*1) Nearline SAS disks 2,016TB SSDs (*2) 4,424TB...
Page 23: Table 3 Specifications (Eternus Dx100 S5 [Dc Power Type])
1. Overview Product Lineup *4: These values are only for when all of the installed drives are the same type and the number of these drives is the maximum. *5: For details, refer to "■ Drives" (page 272) "Component" (page 270).
Page 24: Eternus Dx200 S5
1. Overview Product Lineup ETERNUS DX200 S5 This section provides the storage system specification of the ETERNUS DX200 S5. Table 4 Specifications (ETERNUS DX200 S5) Item ETERNUS DX200 S5 Physical capacity SAS disks 634TB (max.) (*1) Nearline SAS disks 3,696TB SSDs (*2) 8,110TB Number of controllers...
Page 25 1. Overview Product Lineup *4: These values are only for when all of the installed drives are the same type and the number of these drives is the maximum. *5: For details, refer to "■ Drives" (page 272) "Component" (page 270).
Page 26: Eternus Dx500 S5
1. Overview Product Lineup ETERNUS DX500 S5 This section provides the storage system specification of the ETERNUS DX500 S5. Table 5 Specifications (ETERNUS DX500 S5) Item ETERNUS DX500 S5 Physical capacity (max.) SAS disks 1,382TB (*1) Nearline SAS disks 7,728TB SSDs 17,695TB Number of controllers...
Page 27: Eternus Dx600 S5
1. Overview Product Lineup ETERNUS DX600 S5 This section provides the storage system specification of the ETERNUS DX600 S5. Table 6 Specifications (ETERNUS DX600 S5) Item ETERNUS DX600 S5 Physical capacity (max.) SAS disks 2,534TB (*1) Nearline SAS disks 14,448TB SSDs 32,440TB Number of controllers...
Page 28: Eternus Dx900 S5
1. Overview Product Lineup ETERNUS DX900 S5 This section provides the storage system specification of the ETERNUS DX900 S5. Table 7 Specifications (ETERNUS DX900 S5) Item ETERNUS DX900 S5 Physical capacity (max.) SAS disks 5,530TB (*1) Nearline SAS disks 31,584TB SSDs 70,779TB Number of controller enclosures...
Page 29: Function Specification List
1. Overview Function Specification List Function Specification List The ETERNUS DX provides various functions to ensure data integrity, enhance security, reduce cost, and optimize the overall performance of the system. The ETERNUS DX integrates block data (SAN area) and file data (NAS area) in a single device and also provides advanced functions according to the SAN or NAS connection.
Page 30: Table 9 San Functions
1. Overview Function Specification List Supported model DX500 S5 Overview Function DX100 S5 DX60 S5 DX600 S5 DX200 S5 DX900 S5 Environmental burden reduction "Eco-mode" (page 93) ¡ ¡ ¡ Functions that adjust the operating "Power Consumption Visualization" (page 96) time and the environment of the installation location in order to reduce power consumption.
Page 31 1. Overview Function Specification List Supported model DX500 S5 Overview Function DX100 S5 DX60 S5 DX600 S5 DX200 S5 DX900 S5 Security measures (unauthorized "Host Affinity" (page 137) ¡ ¡ ¡ access prevention) "iSCSI Security" (page 139) Functions that prevent unintentional storage access.
Page 32: Table 10 Nas Functions
1. Overview Function Specification List Table 10 NAS Functions Supported model Overview Function DX100 S5 DX500 S5 DX200 S5 DX600 S5 Supported protocols "CIFS" (page 161) ¡ ¡ NAS protocols that are supported by the "NFS" (page 162) ETERNUS DX. "FTP/FXP"...
Page 33: Basic Functions
Basic Functions This chapter describes the functions that control the storage system. RAID Functions This section explains the points to note before configuring a system using the ETERNUS DX. Supported RAID The ETERNUS DX supports the following RAID levels. RAID0 (striping) •...
Page 34: Figure 2 Raid6-Fr Concept
2. Basic Functions RAID Functions ● RAID6 (Striping with Double Distributed Parity) Allocating two different parities on different drives (double parity) makes it possible to recover from up to two drive failures. ● RAID6-FR (Striping with Double Distributed Parity which Provides High-Speed Rebuild Capabilities) Distributing multiple data groups and reserved space equivalent to hot spares to the configuration drives makes it possible to recover from up to two drive failures.
Page 35: Table 11 Raid Level Comparison
2. Basic Functions RAID Functions ■ Reliability, Performance, Capacity for Each RAID Level Table 11 shows the comparison result of reliability, performance, capacity for each RAID level. Table 11 RAID Level Comparison RAID level Reliability Performance (*1) Capacity ◎ ◎ RAID0 ´...
Page 36: User Capacity (Logical Capacity)
2. Basic Functions RAID Functions User Capacity (Logical Capacity) User Capacity for Each RAID Level The user capacity depends on the capacity of drives that configure a RAID group and the RAID level. Table 12 shows the formula for calculating the user capacity for each RAID level. Table 12 Formula for Calculating User Capacity for Each RAID Level RAID level...
Page 37: Raid Group
2. Basic Functions RAID Functions *1: The capacity of the product names for the drives is based on the assumption that 1MB = 1,000 bytes, while the user capacity for each drive is based on the assumption that 1MB = 1,024 bytes.
Page 38: Figure 3 Example Of A Raid Group
2. Basic Functions RAID Functions The same size drives (2.5" or 3.5"), the same kind of drives (SAS disks, Nearline SAS disks, SSDs, or SEDs), and the same capacity drives must be used to configure a RAID group. Figure 3 Example of a RAID Group 600GB 600GB...
Page 39 2. Basic Functions RAID Functions Note • Sequential access performance hardly varies with the number of drives for the RAID group. • Random access performance tends to be proportional to the number of drives for the RAID group. • Use of higher capacity drives will increase the time required for the drive rebuild process to complete. •...
Page 40: Volume
2. Basic Functions RAID Functions Volume This section explains volumes. Logical drive areas in RAID groups are called volumes. A volume is the basic RAID unit that can be recognized by the server. Figure 4 Volume Concept Volume 1 Volume 3 Volume 2 RAID group 1 RAID group 2...
Page 41 2. Basic Functions RAID Functions Type Usage Maximum capacity Flexible Tier Volume (FTV) This volume is a target volume for layering. Data is automatically 128TB redistributed in small block units according to the access frequency. FTVs are used as the copy destination for SnapOPC+. An FTV belongs to a Flexible Tier Pool.
Page 42: Hot Spare
2. Basic Functions RAID Functions Hot Spare Hot spares are used as spare drives for when drives in a RAID group fail, or when drives are in error status. Figure 5 Hot Spare Hot spare Failure RAID group Note For RAID6-FR, because a RAID6-FR group reserves an area equivalent to one drive, data can be restored to the reserved space even if a drive fails.
Page 43: Table 18 Number Of Installable Hot Spares (1/3)
2. Basic Functions RAID Functions ■ Number of Installable Hot Spares • For the ETERNUS DX60 S5 Register one hot spare for each drive type. For the ETERNUS DX100 S5/DX200 S5 and the ETERNUS DX500 S5/DX600 S5/DX900 S5 • The number of required hot spares is determined by the total number of drives. The following table shows the recommended number of hot spares for each drive type.
Page 44: Table 21 Hot Spare Selection Criteria - Drives (Eternus Dx100 S5/Dx200 S5)
2. Basic Functions RAID Functions ■ Selection Criteria When multiple Global Hot Spares are installed, the hot spare that will replace a failed drive is automatically selected by searching each drive sequentially according to the selection criteria for hot spares. Note that a "member drive"...
Page 45: Figure 6 Hot Spare Selection Criteria (For The Eternus Dx500 S5/Dx600 S5)
2. Basic Functions RAID Functions *1: If multiple drives are applicable, priority is given to the drives in ascending order of the enclosure number and the drive slot number. *2: When there are multiple hot spares with a larger capacity than the failed drive, the hot spare with the smallest capacity among them is used first.
Page 46: Figure 7 Hot Spare Selection Criteria - Search Order For Drive Enclosures (Eternus Dx900 S5, Example 1)
2. Basic Functions RAID Functions Hot spare selection criteria (drives) • Drives that meet the following criteria are searched. Table 25 Hot Spare Selection Criteria – Drives (ETERNUS DX900 S5) Priority order Selection criteria A hot spare with the same type, same capacity, and same rotational speed (for disks) as the failed drive (*1) A hot spare with the same type and same rotational speed (for disks) as the failed drive but with a larger capacity (*1) (*2) A hot spare with the same type and same capacity as the failed drive but with a different rotational speed (for...
Page 47: Figure 8 Hot Spare Selection Criteria - Search Order For Drive Enclosures (Eternus Dx900 S5, Example 2)
2. Basic Functions RAID Functions The following figures show examples of the search order for drive enclosures if a drive fails in the ETERNUS DX900 S5 when the RAID group is configured with the same controller enclosure. Figure 8 Hot Spare Selection Criteria – Search Order for Drive Enclosures (ETERNUS DX900 S5, Example RAID group CE#0 DE#01...
Page 48: Data Protection
2. Basic Functions Data Protection Data Protection Data Block Guard When a write request is issued by a server, the data block guard function adds check codes to all of the data that is to be stored. The data is verified at multiple checkpoints on the transmission paths to ensure data integrity. When data is written from the server, the Data Block Guard function adds eight bytes check codes to each block (every 512 bytes) of the data and verifies the data at multiple checkpoints to ensure data consistency.
Page 49: Disk Drive Patrol
2. Basic Functions Data Protection The T10-DIF function can be enabled or disabled for each volume when the volumes are created. This function cannot be enabled or disabled after a volume has been created. Caution • The T10-DIF function can be enabled only in the Standard volume. •...
Page 50: Redundant Copy
2. Basic Functions Data Protection Caution The Maintenance Operation privilege is required to set detailed parameters. Redundant Copy Redundant Copy is a function that copies the data of a drive that shows a possible sign of failure to a hot spare. When the Disk Patrol function determines that a drive requires preventative maintenance, the data of the maintenance target drive is recreated by the remaining drives and written to the hot spare.
Page 51: Rebuild
2. Basic Functions Data Protection Rebuild Rebuild processes recover data in failed drives by using other drives. If a free hot spare is available when one of the RAID group drives has a problem, data of this drive is automatically replicated in the hot spare. This ensures data redundancy.
Page 52: Fast Recovery
2. Basic Functions Data Protection Fast Recovery This function recovers data quickly by relocating data in the failed drive to the other remaining drives when a drive error is detected. For a RAID group that is configured with RAID6-FR, Fast Recovery is performed for the reserved area that is equivalent to hot spares in the RAID group when a drive error occurs.
Page 53: Copyback/Copybackless
2. Basic Functions Data Protection Copyback/Copybackless A Copyback process copies data in a hot spare to the new drive that is used to replace the failed drive. Figure 14 Copyback After rebuilding has been completed, replaces the failed drive with the new drive. Failed drive RAID5 (Redundant) Copyback...
Page 54: Figure 15 Copybackless
2. Basic Functions Data Protection • Size (2.5" and 3.5" [including drives for high-density drive enclosures]) Capacity • • Rotational speed (15,000rpm, 10,000rpm, and 7,200rpm) (*1) *1: For SAS disks or Nearline SAS disks (including SEDs) only. If different types of drives have been selected as the hot spare, copyback is performed after replacing the drives even when the Copybackless function is enabled.
Page 55: Protection (Shield)
2. Basic Functions Data Protection Protection (Shield) The Protection (Shield) function diagnoses temporary drive errors. A drive can continue to be used if it is determined to be normal. The target drive temporarily changes to diagnosis status when drive errors are detected by the Disk Drive Patrol function or error notifications.
Page 56 2. Basic Functions Data Protection Caution • The target drives are disconnected and then reconnected during temporary drive protection. Even though a system status error may be displayed during this period, this phenomenon is only temporary. The status returns to normal after the diagnosis is complete. The following phenomenon may occur during temporary drive protection.
Page 57: Reverse Cabling
2. Basic Functions Data Protection Reverse Cabling Because the ETERNUS DX uses reverse cabling connections for data transfer paths between controllers and drives, continued access is ensured even if a failure occurs in a drive enclosure. If a drive enclosure fails for any reason, access to drives installed in the drive enclosures subsequent to the failed drive enclosure is maintained because normal access paths are secured by using reverse cabling.
Page 58: Operations Optimization (Virtualization/Automated Storage Tiering)
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Operations Optimization (Virtualization/Automated Storage Tiering) Thin Provisioning The Thin Provisioning function has the following features: Storage Capacity Virtualization • The physical storage capacity can be reduced by allocating the virtual drives to a server, which allows efficient use of the storage capacity.
Page 59: Figure 18 Storage Capacity Virtualization
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Storage Capacity Virtualization Thin Provisioning improves the usability of the drives by managing the physical drives in a pool, and sharing the unused capacity among the virtual volumes in the pool. The volume capacity that is seen from the server is virtualized to allow the server to recognize a larger capacity than the physical volume capacity.
Page 60: Table 28 Chunk Size According To The Configured Tpp Capacity
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) The following table shows the TPP chunk size that is applied when TPPs are created. Table 28 Chunk Size According to the Configured TPP Capacity Setting value of the maximum pool capacity Chunk size (*1) DX60 S5 DX100 S5...
Page 61: Table 30 Tpp Thresholds
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) ● Threshold Monitoring of Used Capacity When the used capacity of a TPP reaches the threshold, a notification is sent to the notification destination, (SNMP Trap, e-mail, or Syslog) specified using the [Setup Event Notification] function. There are two types of thresholds: "Attention"...
Page 62: Figure 19 Tpv Balancing (When Allocating Disproportionate Tpv Physical Capacity Evenly)
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) TPV Balancing A drive is allocated when a write is issued to a virtual volume (TPV). Depending on the order and the frequency of writes, more drives in a specific RAID group may be allocated disproportionately. Also, the physical capacity is unevenly allocated among the newly added RAID group and the existing RAID groups when physical drives are added to expand the capacity.
Page 63 2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) ● Balancing Level The TPV balance status is displayed by three levels; "High", "Middle", and "Low". "High" indicates that the physical capacity of TPV is allocated evenly in the RAID groups registered in the TPP. "Low" indicates that the physical capacity is allocated unequally to a specific RAID group in the TPP.
Page 64: Figure 21 Tpv/Ftv Capacity Optimization
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) TPV/FTV Capacity Optimization TPV/FTV capacity optimization can increase the unallocated areas in a pool (TPP/FTRP) by changing the physical areas where 0 is allocated for all of the data to unallocated areas. This improves functional efficiency. Once an area is physically allocated to a TPV/FTV, the area is never automatically released.
Page 65: Flexible Tier
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Flexible Tier Flexible Tier provides the following functions: Automated Storage Tiering • This function automatically reallocates data according to the data access frequency and optimizes performance and cost. FTRP Balancing • I/O access to a virtual volume can be distributed among the RAID groups in a pool by relocating and balancing the physical areas allocated to the virtual volume.
Page 66: Figure 22 Flexible Tier
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Figure 22 Flexible Tier ETERNUS DX Management server Monitors the data access frequency and optimizes performance ETERNUS SF Storage Cruiser Access frequency High High speed SSDs High speed SAS disks Large capacity, low-cost Nearline SAS disks Work volume...
Page 67: Figure 23 Ftv Configuration
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Figure 23 FTV Configuration Chunk Chunk SAS disk Nearline SAS disk FTSP (High tier) FTSP (Middle tier) FTSP (Low tier) FTRP (Parent pool) : RAID group Flexible Tier Pool (FTRP) • An FTRP is a management unit for FTSP to be layered. Up to three FTSPs can be registered in one FTRP. This means that the maximum number of layers is three.
Page 68: Table 34 Levels And Configurations For A Raid Group That Can Be Registered In An Ftsp
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) *1: The maximum total number of Thin Provisioning Pools and FTSPs. *2: The maximum pool capacity is the capacity that combines the FTSP capacity and the Thin Provisioning Pool capacity in the ETERNUS DX.
Page 69: Table 35 Ftrp Thresholds
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) ● Threshold Monitoring of Used Capacity When the used capacity of an FTRP or an FTV reaches the threshold, an alarm notification can be sent from ETERNUS SF Storage Cruiser. There are two types of thresholds: "Attention" and "Warning". A different value can be specified for each threshold type.
Page 70: Figure 24 Ftrp Balancing
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) FTRP Balancing When drives are added to a pool, the physical capacity may be allocated unevenly among the RAID groups in the pool. By using the Flexible Tier Pool balancing function, the allocated physical capacity as well as the usage rate of the physical disks in the pool can be balanced.
Page 71 2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Caution • If the free capacity in the FTSP becomes insufficient while FTRP balancing is being performed, an error occurs and the balancing session ends abnormally. Note that insufficient physical capacity cannot be replaced by other FTSPs. •...
Page 72: Extreme Cache
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Extreme Cache The Extreme Cache function uses PCIe Flash Modules (PFM) as the secondary cache to improve the read access performance from the server. Frequently accessed areas are written to the PFM asynchronously with I/O. When a read request is issued from the server, data is read from the PFM to speed up the response.
Page 73: Extreme Cache Pool
2. Basic Functions Operations Optimization (Virtualization/Automated Storage Tiering) Extreme Cache Pool The Extreme Cache Pool function uses SSDs in enclosures as the secondary cache to improve the read access performance from the server. Frequently accessed areas are written asynchronously with I/Os to the SSDs specified as Extreme Cache Pools. When a read request is issued from the server, data is read from the faster SSD to speed up the response.
Page 74: Optimization Of Volume Configurations
2. Basic Functions Optimization of Volume Configurations Optimization of Volume Configurations The ETERNUS DX allows for the expansion of volumes and RAID group capacities, migration among RAID groups, and changing of RAID levels according to changes in the operation load and performance requirements while the system is running.
Page 75: Raid Migration
2. Basic Functions Optimization of Volume Configurations ● Striping for Multiple RAID Groups Wide Striping • Distributing a single volume to multiple RAID groups makes I/O access from the server more efficient and improves the performance. RAID Migration RAID Migration is a function that moves a volume to a different RAID group with the data integrity being guaranteed.
Page 76: Figure 29 Raid Migration
2. Basic Functions Optimization of Volume Configurations The volume number (LUN) does not change before and after the migration. The host can access the volume before, during, or after a migration without being affected by the volume number. The following changes can be performed by RAID Migration. Changing the volume type •...
Page 77: Logical Device Expansion
2. Basic Functions Optimization of Volume Configurations Refer to "Combinations of Functions That Are Available for Simultaneous Executions" (page 325) for details on the functions that can be executed simultaneously, the number of simultaneous executions, and the capacity that can be processed concurrently. Caution During RAID Migration, the access performance for the RAID groups that are specified as the RAID Migration source and RAID Migration destination may be reduced.
Page 78: Lun Concatenation
2. Basic Functions Optimization of Volume Configurations LDE works in terms of RAID group units. If a target RAID group contains multiple volumes, all of the data in the volumes is automatically redistributed when LDE is performed. Note that LDE cannot be performed if it causes the number of data drives to be reduced in the RAID group.
Page 79: Figure 32 Lun Concatenation
2. Basic Functions Optimization of Volume Configurations Figure 32 LUN Concatenation RAID5 (3D+1P) 960GB × 4 RAID5 (3D+1P) 960GB × 4 LUN0 LUN0 LUN1 LUN1 LUN2 LUN2 Unused area Concatenates Concatenation the unused area and LUN2 RAID5 (3D+1P) 960GB × 4 RAID5 (3D+1P) 960GB ×...
Page 80: Wide Striping
2. Basic Functions Optimization of Volume Configurations LUN Concatenation may not be available when other functions are being used in the ETERNUS DX or the target volume. For details on the functions that can be executed simultaneously, refer to "Combinations of Functions That Are Available for Simultaneous Executions"...
Page 81 2. Basic Functions Optimization of Volume Configurations WSVs are created by concatenating RAID groups that have the same state with regard to the following conditions. RAID level • • Number of member drives Stripe depth • Type of drive to be configured and rotational speed (for disks) •...
Page 82: Data Encryption
AES (*1) or Fujitsu Original Encryption can be selected as the encryption method. The Fujitsu Original Encryption method uses a Fujitsu original algorithm that has been specifically created for ETERNUS DX storage systems.
Page 83: Encryption With Self Encrypting Drive (Sed)
2. Basic Functions Data Encryption Encryption with Self Encrypting Drive (SED) An SED has a built-in encryption function and data can be encrypted by controlling the encryption function of an SED from the controller. An SED uses encryption keys when encrypting and storing data. Encryption keys cannot be taken out of the drive.
Page 84: Firmware Data Encryption
The encryption method can be selected from the world standard AES-128, the world standard AES-256, and the Fujitsu Original Encryption method. The Fujitsu Original Encryption method that is based on AES technology uses a Fujitsu original algorithm that has been specifically created for ETERNUS DX storage systems. The Fujitsu Original Encryption method has practically the same security level as AES-128 and the conversion speed for the Fujitsu Original Encryption method is faster than AES.
Page 85: Key Management Server Linkage
2. Basic Functions Data Encryption • When copying encrypted volumes (using Advanced Copy or copy operations via server OS), transfer performance may not be as good as when copying unencrypted volumes. • SDPVs cannot be encrypted after they are created. To create an encrypted SDPV, set encryption when creating a volume.
Page 86: Figure 37 Key Management Server Linkage
2. Basic Functions Data Encryption Function SED authentication key Key Management Server Linkage Key backup Target RAID groups RAID groups (Standard, WSV, SDV, SDPV), REC Disk Buffers, TPPs, FTRPs, and FTSPs (*2) *1: The key becomes unavailable in the key server. *2: After a pool is created or after the pool capacity is expanded, all the RAID groups that configure the pool must be added to the key group.
Page 87 2. Basic Functions Data Encryption Caution If a LAN connection cannot be secured during SED authentication, authentication fails because the authentication key that is managed by the key server cannot be obtained. To use the key server linkage function, a continuous connection to the LAN must be secured. Note When linking with the key management server, the ETERNUS DX obtains the SED authentication key from the key server and performs authentication when key management settings are performed, key...
Page 88: User Access Management
2. Basic Functions User Access Management User Access Management Account Management The ETERNUS DX uses roles to allocate access authority when a user account is created, and sets which functions can be used depending on the user privileges. Since the authorized functions of the storage administrator are classified according to the usage and only minimum privileges are given to the administrator, security is improved and operational mistakes and management hours can be reduced.
Page 89: Table 40 Available Functions For Default Roles
2. Basic Functions User Access Management • Roles and available functions Seven default roles are provided in the ETERNUS DX. The following table shows the roles and the available functions (privileges). Table 40 Available Functions for Default Roles Roles Privilege Software Storage Account...
Page 90: User Authentication
2. Basic Functions User Access Management User Authentication Internal Authentication and External Authentication are available as logon authentication methods. RADIUS authentication can be used for External Authentication. ● Internal Authentication Internal Authentication is performed using the authentication function of the ETERNUS DX. The following authentication functions are available when the ETERNUS DX is connected via a LAN using operation management software.
Page 91 Type Attribute number for the Vendor Specific Attribute Length 7 or more Attribute size (calculated by server) Vendor-Id Fujitsu Limited (SMI Private Enterprise Code) Vendor type Eternus-Auth-Role Vendor length 2 or more Attribute size described after the "Vendor type" item (calculated by server)
Page 92: Audit Log
2. Basic Functions User Access Management Audit Log The ETERNUS DX can send information such as access records by the administrator and setting changes as audit logs to the Syslog servers. Audit logs are audit trail information that record operations that are executed for the ETERNUS DX and the response from the system.
Page 93: Environmental Burden Reduction
2. Basic Functions Environmental Burden Reduction Environmental Burden Reduction Eco-mode Eco-mode is a function that reduces power consumption for limited access disks by stopping the disks rotation during specified periods or by powering off the disks. Disk spin-up and spin-down schedules can be set for each RAID group or TPP. These schedules can also be set to allow backup operations.
Page 94: Table 42 Eco-Mode Specifications
2. Basic Functions Environmental Burden Reduction For RAID groups with the following conditions, the Eco-mode schedule can be set but the disks motor cannot be stopped or the power supply cannot be turned off: SDPVs are registered • • ODX Buffer volumes are registered If disk access occurs while the disk motor is stopped, the disk is immediately spun up and can be accessed within one to five minutes.
Page 95 2. Basic Functions Environmental Burden Reduction AdvancedCopy Manager cannot be shared. Make sure to use only one type of software to manage a RAID group. • Use ETERNUS Web GUI or ETERNUS CLI to set Eco-mode for TPPs. ETERNUS SF Storage Cruiser or ETERNUS SF AdvancedCopy Manager cannot be used to set the Eco-mode for TPPs and FTRPs.
Page 96: Power Consumption Visualization
2. Basic Functions Environmental Burden Reduction Access 9:00 21:00 Stop accessing 1:00 Scheduled operation Stop Operation Stop Operation Operation Accessible in 1 to 5 minutes The motor starts rotating 10 minutes The disk stops 10 minutes before the scheduled operation after the scheduled operation Power Consumption Visualization The power consumption and the temperature of the ETERNUS DX can be visualized with a graph by using the...
Page 97: Operation Management/Device Monitoring
■ ETERNUS SF ETERNUS SF can manage storage environments that center on Fujitsu storage products. An easy-to-use interface enables complicated storage environment design and setting operations, which allows easy installation of a storage system without needing to have high level skills.
Page 98: Performance Information Management
2. Basic Functions Operation Management/Device Monitoring ■ SMI-S Storage systems can be managed collectively using the general storage management application that supports Version 1.6.1 of Storage Management Initiative Specification (SMI-S). SMI-S is a storage management interface standard of the Storage Network Industry Association (SNIA). SMI-S can monitor the ETERNUS DX status and change configurations such as RAID groups, volumes, and Advanced Copy (EC/REC/OPC/SnapOPC/SnapOPC+).
Page 99 2. Basic Functions Operation Management/Device Monitoring ● Controller Performance Information Busy Ratio (CPU usage) • • CPU Core Usage ● CA Port Performance Information Read IOPS (the read count per second) • • Write IOPS (the write count per second) Read Throughput (the amount of transferred data that is read per second) •...
Page 100: Event Notification
2. Basic Functions Operation Management/Device Monitoring Event Notification When an error occurs in the ETERNUS DX, the event notification function notifies the event information to the administrator. The administrator can be informed that an error occurred without monitoring the screen all the time.
Page 101: Table 45 Snmp Specifications
2. Basic Functions Operation Management/Device Monitoring ● Simple Network Management Protocol (SNMP) Using the SNMP agent function, management information is sent to the SNMP manager (network management/monitoring server). The ETERNUS DX supports the following SNMP specifications. Table 45 SNMP Specifications Item Specification Remarks...
Page 102: Device Time Synchronization
2. Basic Functions Operation Management/Device Monitoring Device Time Synchronization The ETERNUS DX treats the time that is specified in the Master CM as the system standard time and distributes that time to other modules to synchronize the storage time. The ETERNUS DX also supports the time correction function by using the Network Time Protocol (NTP).
Page 103: Remote Support
2. Basic Functions Operation Management/Device Monitoring Remote Support There are two types of remote support services for notifying the errors that occur in the ETERNUS DX: AIS Connect and REMCS. ■ AIS Connect Function ● Overview of the AIS Connect Function Figure 44 Overview of the AIS Connect Function Demilitarized zone...
Page 104: Figure 45 Security Features
2. Basic Functions Operation Management/Device Monitoring ● Security Features Figure 45 Security Features Allowed Rejected Firewall ETERNUS DX AIS Connect server behind a firewall Connection from an AIS Connect agent to the AIS Connect server can be set up via a SOAP message that is based on HTTPS.
Page 105: Power Control
2. Basic Functions Power Control Power Control Power Synchronized Unit A power synchronized unit detects changes in the AC power output of the Uninterruptible Power Supply (UPS) unit that is connected to the server and automatically turns on and off the ETERNUS DX. Figure 46 Power Synchronized Unit Server...
Page 106: Remote Power Operation (Wake On Lan)
2. Basic Functions Power Control Remote Power Operation (Wake On LAN) Wake On LAN is a function that turns on the ETERNUS DX via a network. When "magic packet" data is sent from an administration terminal, the ETERNUS DX detects the packet and the power is turned on.
Page 107: Backup (Advanced Copy)
2. Basic Functions Backup (Advanced Copy) Backup (Advanced Copy) The Advanced Copy function (high-speed copying function) enables data backup (data replication) at any point without stopping business operations. For an ETERNUS DX backup operation, data can be replicated without placing a load on the business server. Large amounts of data can be replicated by coordinating the timing of business access so data protection measures can be applied separately from those of operation processes.
Page 108: Backup (San)
2. Basic Functions Backup (Advanced Copy) Backup (SAN) Local Copy The Advanced Copy functions offer the following copy methods: "Mirror Suspend", "Background Copy", and "Copy- on-Write". The function names that are given to each method are as follows: "EC" for the "Mirror Suspend" method, "OPC"...
Page 109 2. Basic Functions Backup (Advanced Copy) • If the SnapOPC+ function is used from ETERNUS SF AdvancedCopy Manager, among the created multiple generations, the data of intermediate generations can be deleted. ● An EC creates data that is mirrored from the copy source to the copy destination beforehand, and then suspends the copy and handles each data independently.
Page 110: Table 48 Rec Data Transfer Mode
2. Basic Functions Backup (Advanced Copy) Figure 49 Main site Backup site Management Management server server Remote copy (REC) Operating Backup volume volume ETERNUS AF/DX ETERNUS AF/DX The REC data transfer mode has two modes: the synchronous transfer mode and the asynchronous transfer mode.
Page 111 REC Disk Buffers can only be used if the ETERNUS DX set as the REC Buffer (for transmission) and the ETERNUS DX set for the REC Buffer (for reception) both support REC Disk Buffers. The following models, which can execute remote copies with the ETERNUS DX S5 series, support REC Disk Buffers. • ETERNUS AF series •...
Page 112: Figure 50 Restore Opc
2. Basic Functions Backup (Advanced Copy) Available Advanced Copy Combinations Different Advanced Copy types can be combined and used together. ● Restore OPC For OPC, QuickOPC, SnapOPC, and SnapOPC+, restoration of the copy source from the copy destination is complete immediately upon request. Figure 50 Restore OPC OPC, QuickOPC,...
Page 113: Figure 52 Targets For The Multi-Copy Function
2. Basic Functions Backup (Advanced Copy) ● Multi-Copy Multiple copy destinations can be set for a single copy source area to obtain multiple backups. Even if the beginning and end of the copy source areas for the copy sessions do not match, multi-copy can be performed for the overlapping copy source area.
Page 114: Figure 54 Multi-Copy (Including Snapopc+)
2. Basic Functions Backup (Advanced Copy) For a SnapOPC+, the maximum number of SnapOPC+ copy session generations can be set for a single copy source area when seven or less multi-copy sessions are already set. Figure 54 Multi-Copy (Including SnapOPC+) ETERNUS AF/DX ETERNUS AF/DX Copy...
Page 115: Figure 56 Multi-Copy (Case 1: When Performing A Cascade Copy For An Rec Session In Consistency Mode)
2. Basic Functions Backup (Advanced Copy) When performing a Cascade Copy for an REC session in Consistency mode, the copy source of the session must not be related to another REC session in Consistency mode with the same destination storage system. Figure 56 Multi-Copy (Case 1: When Performing a Cascade Copy for an REC Session in Consistency Mode) ETERNUS AF/DX...
Page 116: Figure 58 Cascade Copy
2. Basic Functions Backup (Advanced Copy) A Cascade Copy can be performed when all of the target volumes are the same size or when the copy destination volume for copy session 2 is larger than the other volumes. Figure 58 Cascade Copy OPC/QuickOPC/ OPC/QuickOPC/...
Page 117: Table 50 Modified Data Size For Each Quickopc Resolution
2. Basic Functions Backup (Advanced Copy) *2: When issuing a re-copy request for copy session 1 (a request to copy only the data that has been updated after all data is copied), the modified data size should conform to the sizes shown in Table For example, when a QuickOPC session is created at a resolution of 2, the modified data size should be less than 2TB.
Page 118 2. Basic Functions Backup (Advanced Copy) ¡: Possible, ´: Not possible *1: This combination is supported only if the copy size in both the copy source volume and the copy destination volume is less than 2TB. If the copy size is 2TB or larger, perform the following operations instead. •...
Page 119: Figure 59 Cascade Copy (Using Three Copy Sessions)
2. Basic Functions Backup (Advanced Copy) • If a Cascade Copy performs session 1 before session 2, and copy session 1 is an OPC or QuickOPC session, the logical data in the intermediate volume when copy session 2 is started (the copy destination volume for copy session 1) is copied to the copy destination volume for copy session 2.
Page 120: Backup/Restore (Nas)
2. Basic Functions Backup (Advanced Copy) A Cascade Copy that uses the four copy sessions can be performed with the following configuration. However, two EC sessions in the copy destination storage system cannot be "Active" at the same time. Figure 60 Cascade Copy (Using Four Copy Sessions) ETERNUS AF/DX ETERNUS AF/DX...
Page 121: Performance Tuning
2. Basic Functions Performance Tuning Performance Tuning Assigned CMs A controller that controls access is assigned to each RAID group and manages the load balance in the ETERNUS DX. The controller that controls a RAID group is called an assigned CM. Figure 61 Assigned CMs The assigned CM of the RAID...
Page 122: Striping Size Expansion
2. Basic Functions Performance Tuning Number of CMs (number of CEs) The remainder when the RAID group number is divided by the number of controllers 2 (1CE) 4 (2CE) CE#0 CM#1 CE#1 CM#1 — CE#1 CM#0 — CE#0 CM#1 Striping Size Expansion Striping Size Expansion is a function to expand the stripe depth value by specifying the stripe depth when creating a RAID group.
Page 123: Smart Setup Wizard
2. Basic Functions Smart Setup Wizard Smart Setup Wizard The Smart Setup Wizard simplifies the creation of Thin Provisioning Pools and configuration of host affinity for configurations enabled with Thin Provisioning. For the procedure on configuration using the Smart Setup Wizard, refer to "Configuration Guide (Basic)". Note If a Thin Provisioning Pool has not been created, the Smart Setup Wizard automatically creates one.
Page 124 2. Basic Functions Smart Setup Wizard RAID configuration that is to be User capacity created Capacity of the Number of Hot spare Unused drive user data area installed drives RAID group (equivalent Per RAID group Per ETERNUS DX number of drives) RAID5 ´...
Page 125: Figure 62 Raid Configuration Example (When 12 Ssds Are Installed)
2. Basic Functions Smart Setup Wizard RAID configuration that is to be User capacity created Capacity of the Number of Hot spare Unused drive user data area installed drives RAID group (equivalent Per RAID group Per ETERNUS DX number of drives) RAID5 ´...
Page 126 2. Basic Functions Smart Setup Wizard RAID configuration that is to be User capacity created Capacity of the Number of Hot spare Unused drive user data area installed drives RAID group (equivalent Per RAID group Per ETERNUS DX number of drives) RAID6 ´...
Page 127: Figure 63 Raid Configuration Example (When 15 Sas Disks Are Installed)
2. Basic Functions Smart Setup Wizard Figure 63 RAID Configuration Example (When 15 SAS Disks Are Installed) RAID6 × 2, Hot spare × 1, Unused drive × 2 Hot spare Unused drive RAID6 group 1 (*1) Drive#0 Drive#1 Drive#2 Drive#3 Drive#4 Drive#5 Drive#12...
Page 128: San Functions
SAN Functions This chapter describes the functions that are available when a SAN connection is used. Operations Optimization (Deduplication/Compression) IMPORTANT • The Deduplication/Compression function cannot be used for the following storage systems. - ETERNUS DX200 S5 in a single-controller configuration - The Unified License is installed •...
Page 129: Figure 64 Deduplication/Compression Overview
3. SAN Functions Operations Optimization (Deduplication/Compression) Figure 64 Deduplication/Compression Overview Business server 1 Business server 2 Data 1 Data 2 Data 1 is Data 2 is written written Analysis Deduplication Duplicate data blocks are removed Compression: Data blocks are compressed A B C D E F Target volume for deduplication/compression ETERNUS DX...
Page 130: Figure 65 Deduplication Overview
3. SAN Functions Operations Optimization (Deduplication/Compression) ● Deduplication Function This function removes duplicate data blocks and stores the data. Figure 65 Deduplication Overview Business server 1 Business server 2 Data 1 Data 2 Data 1 is Data 2 is written written Analysis Deduplication...
Page 131: Table 56 Deduplication/Compression Function Specifications (Eternus Dx200 S5, Eternus Dx500 S5/ Dx600 S5)
3. SAN Functions Operations Optimization (Deduplication/Compression) The following table provides the function specifications for the Deduplication/Compression. Table 56 Deduplication/Compression Function Specifications (ETERNUS DX200 S5, ETERNUS DX500 S5/ DX600 S5) Model ETERNUS DX200 S5 ETERNUS DX500 S5 ETERNUS DX600 S5 Number of TPPs available for Deduplication/ Compression settings Maximum logical capacity that can be a Up to ten times the DATA_CNTNR Volume (*1)
Page 132: Table 58 Method For Enabling The Deduplication/Compression Function
3. SAN Functions Operations Optimization (Deduplication/Compression) ● Performance When Using the Deduplication/Compression Function The ETERNUS DX performs data deduplication/compression in synchronization with the I/O from the server. Using this function in environments where random access occurs is recommended. Data is intermittently •...
Page 133: Table 59 Volumes That Are To Be Created Depending On The Selection Of "Deduplication" And "Compression
3. SAN Functions Operations Optimization (Deduplication/Compression) *3: The chunk size (21MB – 336MB) during a TPP creation is maintained. The Deduplication/Compression function can be enabled for TPPs whose chunk sizes are not 21MB. *4: If I/O load exists in the ETERNUS DX, enabling or disabling the Deduplication/Compression function in the TPP may take time. If I/O load exists, changing the setting of the Deduplication/Compression function for each TPP is recommended.
Page 134 3. SAN Functions Operations Optimization (Deduplication/Compression) ● Deduplication/Compression System Volumes One DATA_CNTNR Volume is created for each TPP where the Deduplication/Compression function is enabled. Before enabling the Deduplication/Compression function for a TPP, check whether the remaining capacity is sufficient because the DATA_CNTNR volume is created just within the maximum pool capacity. Because the data after deduplication/compression is stored in the DATA_CNTNR Volume, add RAID groups to the TPP or expand the DATA_CNTNR Volume before the usage rate of the TPP or the usage rate of the DATA_CNTNR Volume reaches 100%.
Page 135: Figure 67 Details Of The Deduplication/Compression Function
3. SAN Functions Operations Optimization (Deduplication/Compression) ● Functional Details Figure 67 Details of the Deduplication/Compression Function Server ETERNUS DX I/O request Thin Provisioning Pool (TPP) Maps the Deduplication/Compression Volume (or the virtual volume) and the actual written data Deduplication/ DATA_CNTNR (TPV) Compression Volume (a virtual volume that can be seen...
Page 136: Table 61 Target Deduplication/Compression Volumes Of Each Function
3. SAN Functions Operations Optimization (Deduplication/Compression) ● Operation of the Deduplication/Compression Volumes The following table provides management functions for volumes related to Deduplication/Compression. Table 61 Target Deduplication/Compression Volumes of Each Function Function Deduplication/Compression Volume DATA_CNTNR Volume ´ (*1) Creation ¡ ´...
Page 137: Improving Host Connectivity
3. SAN Functions Improving Host Connectivity Improving Host Connectivity Host Affinity The host affinity function prevents data from being damaged due to inadvertent storage access. By defining a server that can access the volume, security can be ensured when multiple servers are connected. Figure 68 Host Affinity Permission for Server A...
Page 138: Figure 69 Associating Host Groups, Ca Port Groups, And Lun Groups
3. SAN Functions Improving Host Connectivity Figure 69 Associating Host Groups, CA Port Groups, and LUN Groups Host group 1 ETERNUS DX Server A LUN group 1 CE#1 Switch Port Vol#0 Vol#1 Vol#2 Server B Port Switch CA port group 1 CA port group 2 Server C CE#0...
Page 139: Iscsi Security
3. SAN Functions Stable Operation iSCSI Security For an iSCSI interface, the iSCSI authentication function can be used when the initiator accesses the target. The iSCSI authentication function is available for host connections and remote copying. The Challenge Handshake Authentication Protocol (CHAP) is supported for iSCSI authentication. For CHAP Authentication, unidirectional CHAP or bidirectional CHAP can be selected.
Page 140: Figure 71 Copy Path Bandwidth Limit
3. SAN Functions Stable Operation ● REC Bandwidth Limit (Remote Copy QoS) A bandwidth upper limit can be set for each copy path in the remote copy session. Even if a specific path fails, the line bandwidth can be maintained without centralizing the load to other paths.
Page 141: Host Response
3. SAN Functions Stable Operation Host Response The response from the ETERNUS DX can be optimized by switching the setup information of the host response for each connected server. The server requirements of the supported functions, LUN addressing, and the method for command responses vary depending on the connection environments such as the server OS and the driver that will be used.
Page 142: Storage Cluster
3. SAN Functions Stable Operation Storage Cluster Storage Cluster is a function that allows continuous operations by using redundant connections to two ETERNUS AF/DX storage systems so that even if the Primary storage fails, operations are switched to the Secondary storage.
Page 143: Figure 74 Mapping Tfovs, Tfo Groups, And Ca Port Pairs
3. SAN Functions Stable Operation Figure 74 Mapping TFOVs, TFO Groups, and CA Port Pairs CA port pair CA port pair CA#0 CA#1 CA#0 CA#1 TFOV#0 TFOV#0 TFOV#1 TFOV#1 TFOV#2 TFOV#2 Create an association TFO group TFO group Primary storage Secondary storage TFOV •...
Page 144: Table 62 Storage Cluster Function Specifications
3. SAN Functions Stable Operation The following table provides the function specifications for the Storage Cluster. Table 62 Storage Cluster Function Specifications Item Specifications Number of connectable storage systems Business server connections Switch connections only Copy path (connection between storage systems) Direct connection and remote connection Maximum configurable capacity (per storage system) (*1) 2,048TB (ETERNUS DX100 S5/DX200 S5)
Page 145: Data Migration
3. SAN Functions Data Migration Data Migration Storage Migration Storage Migration is a function that migrates the volume data from an old storage system to volumes in a new storage system without using a host in cases such as when replacing a storage system. The migration source storage system and migration destination ETERNUS DX are connected using FC cables.
Page 146 3. SAN Functions Data Migration Caution • For online Storage Migration, the capacity of the migration destination volume must be the same as the migration source volume. • For offline Storage Migration, stop server access to both the migration source volume and the migration destination volume during a migration.
Page 147: Non-Disruptive Storage Migration
3. SAN Functions Non-disruptive Storage Migration Non-disruptive Storage Migration Non-disruptive Storage Migration is a function that migrates the volume data from an old storage system to volumes in a new storage system without stopping a business server in cases such as when replacing a storage system.
Page 148 3. SAN Functions Non-disruptive Storage Migration Connect the external storage system to the ETERNUS DX (local storage system) directly or via a switch. After a connection is established, prepare for the data migration. Create External Drives in the local storage system. Create External RAID Groups using the External Drives and then create volumes in the External RAID Groups.
Page 149: Server Linkage Functions
3. SAN Functions Server Linkage Functions Server Linkage Functions Oracle VM Linkage "Oracle VM Manager", which is the user interface of the "Oracle VM" server environment virtualization software, can provision the ETERNUS DX. "ETERNUS Oracle VM Storage Connect Plug-in" is required to use this function. The Oracle VM Storage Connect framework enables Oracle VM Manager to directly use the resources and functions of the ETERNUS DX in an Oracle VM environment.
Page 150: Vmware Linkage
3. SAN Functions Server Linkage Functions VMware Linkage By linking with "VMware vSphere" (which virtualizes platforms) and "VMware vCenter Server" (which supports integrated management of VMware vSphere), the resources of the ETERNUS DX can be effectively used and system performance can be improved. In addition, by supporting Virtual Volumes that are supported by VMware vSphere 6, the system can be efficiently operated.
Page 151 3. SAN Functions Server Linkage Functions VMware VAAI vStorage APIs for Array Integration (VAAI) are APIs that improve system performance and scalability by using the storage system resources more effectively. The ETERNUS DX supports the following features. • Full Copy (XCOPY) Data copying processes can be performed in the ETERNUS DX without the use of a server such as when replicating or migrating the virtual machine.
Page 152: Figure 79 Vvol (Operational Configuration)
3. SAN Functions Server Linkage Functions Figure 79 VVOL (Operational Configuration) VM management server vSphere vSphere VMware vCenter Server VMware vSphere Client Storage management ETERNUS DX server ETERNUS VASA Provider ETERNUS SF Storage Cruiser ■ System Configuration vSphere accesses VVOLs through Protocol Endpoints (PE). The server recognizes PEs as logical volumes. VVOLs are created in a pool called a storage container.
Page 153: Table 64 Maximum Vvol Capacity
3. SAN Functions Server Linkage Functions ● Storage Container (VVOL Datastore) Storage containers are pools for creating VVOLs. The ETERNUS DX uses FTRPs as storage containers. Multiple storage containers can be created in the ETERNUS DX. ● VVOL VVOLs are logical volumes that are created in FTRPs. Multiple VVOLs can be created in a storage container. ●...
Page 154 3. SAN Functions Server Linkage Functions Caution • When using VVOLs, LUN#224 to LUN#255 (or LUN numbers that are recognized on the server side) cannot be used as Virtual Machine File System (VMFS) volumes because they are used for management. •...
Page 155: Veeam Storage Integration
Backup Proxy using ETERNUS CLI. For more details, refer to "ETERNUS CLI User's Guide". • To enable the ETERNUS DX storage snapshot integration with Veeam Backup & Replication, FUJITSU Plug-In for Veeam Backup & Replication must be installed to the Veeam backup server.
Page 156: Table 66 Volume Types That Can Be Used With Veeam Storage Integration
3. SAN Functions Server Linkage Functions - Virtual Volumes (VVOLs) - Volumes with SnapOPC or EC Advanced Copy sessions - Volumes with SnapOPC+ sessions created by ETERNUS SF AdvancedCopy Manager • Veeam Backup & Replication jobs or operations may fail during a RAID migration, a Thin Provisioning Volume balancing, or a Flexible Tier Pool balancing.
Page 157: Microsoft Linkage
3. SAN Functions Server Linkage Functions Microsoft Linkage The ETERNUS DX supports integrated management of virtualized platforms and cloud linkage by using functions in Windows Server and System Center. Figure 82 Microsoft Linkage Windows Server Server application Backup software Windows Server ETERNUS VSS Hardware Provider Hyper-V...
Page 158: Openstack Linkage
3. SAN Functions Server Linkage Functions • Volume Shadow Copy Service (VSS) VSS is performed in combination with the backup software and the server applications that are compatible with Windows Server VSS while online backups are performed via the Advanced Copy function for the ETERNUS ETERNUS VSS Hardware Provider is required to use this function.
Page 159: Logical Volume Manager (Lvm)
3. SAN Functions Server Linkage Functions Logical Volume Manager (LVM) The Logical Volume Manager is a management function that groups the save areas in multiple drives and partitions and manages these areas as one logical drive. Adding drives and expanding logical volumes can be performed without stopping the system.
Page 160: Nas Functions
NAS Functions This chapter describes the protocols and client OSs that are supported in a NAS environment of an ETERNUS DX, as well as the structure of a NAS system. This chapter also explains the available NAS functions for the ETERNUS DX. Unified Configuration When using the ETERNUS DX as a unified storage system, install the Unified kit and the NAS interface (NIC-CA).
Page 161: Supported Protocols
4. NAS Functions Supported Protocols Supported Protocols The ETERNUS DX supports Common Internet File System (CIFS), a file sharing protocol for Windows, and NFS, a file sharing protocol for UNIX/Linux. In addition to CIFS and NFS, the ETERNUS DX supports FTP/FXP. NAS protocols other than CIFS, NFS, and FTP/FXP are not supported.
Page 162: Nfs
4. NAS Functions Operating Environment for Clients The Network File System (NFS) is a protocol that is used for file sharing in UNIX or Linux system environments. File sharing for NFS can be performed by mounting a shared directory from a client. NFSv3 and v4.0 are supported for the ETERNUS DX.
Page 163: Nas System (Nas Volume Management)
4. NAS Functions NAS System (NAS Volume Management) NAS System (NAS Volume Management) File systems of up to 128TB can be created in the ETERNUS DX NAS system. One file system can be created for a NAS volume. The number of file systems (NAS volumes) that can be created varies depending on the models. Table 67 Number of File Systems Model...
Page 164: Nas File Systems
4. NAS Functions NAS System (NAS Volume Management) NAS File Systems When the first NAS Thin Provisioning Volume (TPV) is created in the ETERNUS DX, system volumes ($SYSVOL1, $SYSVOL2, and $SYSVOL3) are automatically created in the same pool where the TPV is created and then the NAS file system is created.
Page 165: Figure 86 Initial Deployment Of Meta Cache
4. NAS Functions NAS System (NAS Volume Management) Note During the design phase To use the Eco-mode function for TPPs that include NAS volumes, move the system volumes to a different TPP. The Eco-mode function does not work for a TPP that contains system volumes. System volumes can be moved by using RAID Migration.
Page 166: Nas Volume
4. NAS Functions NAS System (NAS Volume Management) NAS Volume TPVs that are used as NAS volumes must be created in a TPP virtual pool. Because TPVs support virtualization of volume capacity, a volume can be used more efficiently by using a volume capacity that is larger than the actual physical capacity.
Page 167 4. NAS Functions NAS System (NAS Volume Management) ■ NAS User Volumes A NAS user volume must have an area of 300GB for the system management area, and an area of 100GB or more for the user area to store user data. Create a TPV with a capacity of 400GB or more for the NAS user volume.
Page 168: Meta Cache Distribution
4. NAS Functions NAS System (NAS Volume Management) SDVs and SDPVs cannot be created in a TPP. SDVs are automatically created in the RAID group that is specified when setting snapshot. SDPVs must be created separately. When acquiring 128 generations of snapshots, a RAID group for registering an SDV and a RAID group for registering an SDPV must be prepared separately.
Page 169: Block Size
4. NAS Functions NAS System (NAS Volume Management) Caution During the configuration phase • The meta cache distribution function can be executed manually or automatically. If automatic execution is selected, meta cache distribution is executed automatically on a regular basis (every hour on the half hour) and when a controller is implemented according to the imbalanced state of the meta cache.
Page 170: File System Specification
4. NAS Functions File System Specification File System Specification ■ File System Usage and Free Space Available free space in the file system is shown differently when the file system area is checked from a CIFS client or an NFS client. The areas described below are displayed as used areas in the file system.
Page 171: Data Encryption
82). Caution During the design phase For each ETERNUS DX, select and specify "AES128", "AES256", or "Fujitsu Original Encryption" as the encryption mode for the firmware data encryption function. To specify the encryption mode, refer to the following notes. • For the ETERNUS DX100 S5 Set the encryption mode to "Fujitsu Original Encryption".
Page 172: Nas Server Name (Host Name)
4. NAS Functions NAS Server Name (Host Name) NAS Server Name (Host Name) The default NAS server name is automatically set for the ETERNUS DX according to the following rules: DX<10-digit ETERNUS DX serial number> (12 digits in total) The NAS server name can be changed to any name by using ETERNUS Web GUI or ETERNUS CLI. For the setup procedures, refer to "NAS Server Name Settings"...
Page 173: User Management
4. NAS Functions User Management User Management This section describes user management for NAS connection with the ETERNUS DX. User management for NAS clients is performed with an authentication server or with local user authentication. ● Windows (CIFS) Environment When the Active Directory authentication server is used, access can be controlled based on the registered user accounts in the authentication server.
Page 174: Figure 89 Authentication Server
4. NAS Functions User Management Figure 89 Authentication Server Active Directory authentication server LDAP authentication server Authentication Authentication CIFS Windows client UNIX/Linux client Shared folder A Shared folder B Assign the folder Mount the folder to the network drive ETERNUS DX Caution During the configuration phase Allocate each authentication server and the NAS interfaces on both CMs of the ETERNUS DX to the same...
Page 175 4. NAS Functions User Management ■ Authentication in a CIFS Environment To allow CIFS access, user authentication settings are required. The ETERNUS DX supports login authentication with the Active Directory authentication server (Kerberos authentication method) and local user authentication. The ETERNUS DX supports Active Directory's one-way and two-way explicit trust relationships. For example, when the trusting domain is set in the ETERNUS DX, setting the trust relationship of the domains as one-way or two- way gives the trusted domain user access to the ETERNUS DX.
Page 176 4. NAS Functions User Management ■ Authentication in an NFS Environment A login authentication by the LDAP authentication server (such as OpenLDAP) is required to perform user management of directories and files with NFS access. Caution During the design phase Operations using an LDAP authentication server that is running Active Directory Lightweight Directory Services are not supported.
Page 177: Figure 90 Process For Acquiring The Authentication Information (Cifs)
4. NAS Functions User Management ■ Authentication in Environments where the CIFS Protocol and the NFS Protocol Are Used Concurrently In environments where the CIFS protocol and the NFS protocol are used concurrently and Active Directory (AD) authentication and LDAP authentication are used, operational design for authentication information (username, group name, and ID) is required.
Page 178: Figure 91 Process For Acquiring The Authentication Information (Nfs)
4. NAS Functions User Management Figure 91 Process for Acquiring the Authentication Information (NFS) 3. Reference the information to authenticate the access request (only if the AD authentication server lacks the Active Directory authentication server LDAP authentication server authentication information) Request access to the Reference the information to shared folder...
Page 179: Local User Authentication
4. NAS Functions User Management Local User Authentication Local user authentication is a function that manages local users/groups who can access the shared folder without using the authentication server and can enable CIFS access on a per created local user/local group basis. Specify the access permission of the shared folder when the shared folder is created.
Page 180 4. NAS Functions User Management sharegroup$ (the group ID is fixed to "451" and other values cannot be specified) For the character strings that can be specified when the local user authentication is configured, the following requirements exist depending on the item. Local usernames and local group names •...
Page 181: Access Control (Acl Function)
4. NAS Functions Access Control (ACL Function) Access Control (ACL Function) A NAS file system reserves extended ACL areas to store permission entries. If the CIFS protocol or the NFSv3 protocol is used, up to 256 access permission entries can be registered for files and directories.
Page 182: Access Control In A Cifs Environment
4. NAS Functions Access Control (ACL Function) Access Control in a CIFS Environment For CIFS access, Windows ACL supported file access management is performed. Windows' Access Based Enumeration (ABE) is supported. With ABE, directories and files can be hidden to users who do not have access privileges.
Page 183: Access Control In A Shared Cifs/Nfs Environment
4. NAS Functions CIFS Access Permission Settings Access Control in a Shared CIFS/NFS Environment When the CIFS protocol and the NFS protocol are used, the access control varies depending on the version of NFS. The NFS access control varies depending on the NFS version. For details, refer to "Access Control in an NFS Environment"...
Page 184: File Sharing
4. NAS Functions File Sharing File Sharing Each client can share files in the NAS file system for the ETERNUS DX. For file sharing, the CIFS protocol is used for Windows and the NFS protocol is used for UNIX/Linux. ■ Shared Folder To share files, create shared folders in the file system for the ETERNUS DX that support the protocol that is to be used.
Page 185 4. NAS Functions File Sharing Note During the design phase • The types of characters that can be used for the owner name and group name are alphanumeric characters (or US-ASCII codes) and symbols from the space character (0x20) to the tilde "~" (0x7E). Note that "?"...
Page 186: Cifs Operation
ADS attributes that can be set is up to 96KB per file. Caution Older storage system models hold ADS information differently from the ETERNUS DX S5 series. Because of this, the ADS information set in older storage system models cannot be migrated using REC.
Page 187 4. NAS Functions File Sharing ■ Changing the Settings for Anonymous Access The setting to allow anonymous access for the CIFS access can be changed. The settings for anonymous access are enabled or disabled for the sessions that are established after the change.
Page 188: Nfs Operation
4. NAS Functions File Sharing NFS Operation This section describes an operation in which the NFS protocol is used. Note During the configuration phase If a data write needs to be ensured, mount the NFS client with the "sync" option to make sure the data is written in the ETERNUS DX.
Page 189: Home Directories
4. NAS Functions Home Directories ■ Commands Different capacity values are shown for the results of the "df" command (shows the usage status of disk drives in UNIX/Linux) and the "du" command (shows the used capacity of disk drives for the directory). •...
Page 190: Quota
4. NAS Functions Quota Quota Quota is a function that limits drive space and the number of files used on a user, group or shared folder basis. The drive capacity can be protected from being used exclusively by a specific user, group, or shared folder by setting the upper limit of the drive space and the number of files available for the user, group, or shared folder.
Page 191: Figure 94 Quota (For Each Shared Folder)
4. NAS Functions Quota Figure 94 Quota (for Each Shared Folder) Set the upper limit drive usage for each shared folder. An alarm notification is sent to the client currently accessing the drive when the threshold is exceeded. 10TB (Upper limit drive usage) Shared folder A Client currently accessing the drive...
Page 192: Snapshot
4. NAS Functions Snapshot Snapshot Snapshot is a function that automatically backs up volume data at a certain point. Unlike usual backup copies, this function only copies differential data from the source volume data. Therefore, the disk space necessary for backup is reduced.
Page 193: Figure 95 Snapshot
4. NAS Functions Snapshot ■ NAS Snapshot Destination Volumes To acquire snapshots, prepare snapshot destination volumes (an SDV and an SDPV). For details on volumes, refer to "■ NAS Snapshot Destination Volumes" (page 193). The following table shows the required capacity for the SDV and the SDPV (guidelines). Table 73 Required Capacity of SDV/SDPV (Guideline) Volume...
Page 194 4. NAS Functions Snapshot ● SDPE Capacity Snap Data Pool Element (SDPE) is a unit of pool area to be allocated from an SDPV to an SDV (copy destination area). When data is written to the copy destination, the SDP is divided into small units called SDPE, so that only as much as is required is used.
Page 195: Backup
Guide for Copy Control Module". Note • If an ETERNUS DX S5 series is used as the remote copy source, volumes can be backed up to older storage systems as the remote copy destination. However, the backup volumes cannot be restored to NAS volumes in the older storage system.
Page 196: Audit Log
4. NAS Functions Audit Log Audit Log Audit logs are audit trail information that record operations that are executed for the ETERNUS DX and the response from the system. This information is required for auditing. The number of files for saving the audit logs can be specified.
Page 197: Performance Index
4. NAS Functions Performance Index Performance Index This section describes the performance index when configuring a NAS environment. Although the ETERNUS DX has sufficient throughput, the performance degrades when the load is high. Performance requirements (indices for process performance) must be taken into consideration. The following table provides the performance requirements for the ETERNUS DX.
Page 198: Connection Configuration
Connection Configuration This chapter explains the connection configuration of the ETERNUS DX. Power Supply Connection Connect the power cords of the ETERNUS DX to the power sockets, the UPS sockets, or the power control unit sockets. For details about the types and number of power sockets that can be used for the ETERNUS DX, refer to "Power Socket Specifications"...
Page 199: Power Synchronized Connections
5. Connection Configuration Power Synchronized Connections Power Synchronized Connections This section describes the connections to automatically turn the ETERNUS DX on or off from a server. In order to control powering the ETERNUS DX on and off with servers, the power control of the ETERNUS DX must be linked with all of the connected servers.
Page 200 5. Connection Configuration Power Synchronized Connections Powering on sequence Power on of all the server UPS units Server startup The server OS startup is suspended until the ETERNUS DX startup is complete (*1). Instruction from the power synchronized unit to turn on the ETERNUS DX ETERNUS DX startup *1: The server must be set to suspend server OS startup until the ETERNUS DX startup is complete.
Page 201: Figure 98 Power Supply Control Using A Power Synchronized Unit (When Connecting Three Or More Servers)
5. Connection Configuration Power Synchronized Connections • When connecting three or more servers Figure 98 Power Supply Control Using a Power Synchronized Unit (When Connecting Three or More Servers) Turns on: 1 Turns off: 2 Turns on: 2 Turns off: 1 Server#1 UPS unit for Server#1...
Page 202: Power Synchronized Connections (Wake On Lan)
5. Connection Configuration Power Synchronized Connections Refer to the manual that is provided with a power synchronized unit for details about connection configurations with power synchronized units and required settings. Power Synchronized Connections (Wake On LAN) By using Wake On LAN, an instruction to power on the ETERNUS DX can be issued via the LAN. "Magic packet"...
Page 203: Lan Connection
5. Connection Configuration LAN Connection LAN Connection The ETERNUS DX requires a LAN connection for operation management. In addition, information such as ETERNUS DX failures is notified to the remote support center. Note Make sure to connect each controller to the LAN for operation management. Specifications for the LAN ports of the ETERNUS DX are shown below.
Page 204: Lan For Remote Support
5. Connection Configuration LAN Connection Note The following figure provides connection examples for when setting the IP address of the Slave CM. Figure 101 Connection Example When the IP Address of the Slave CM Is Set (and a Dedicated Remote Support Port Is Not Used) Administration SNMP...
Page 205: Figure 102 Connection Example With A Dedicated Remote Support Port
5. Connection Configuration LAN Connection Figure 102 Connection Example with a Dedicated Remote Support Port Administration SNMP E-mail server NTP server terminal manager Authentication Syslog server LAN switch server LAN for operation management IP address C IP address A Router CM#0 CM#1 Remote support...
Page 206: Lan Control (Master Cm/Slave Cm)
5. Connection Configuration LAN Connection LAN Control (Master CM/Slave CM) This section explains how the LAN control controller of the ETERNUS DX operates. Of the two controllers in the ETERNUS DX, the controller (CM) that is given the authority to manage the LAN is called the Master CM and the CM that takes over the management when the Master CM fails is called the Slave When an error occurs in the Master CM or LAN, the Master CM is switched automatically.
Page 207: Figure 105 Lan Control (When The Ip Address Of The Slave Cm Is Set)
5. Connection Configuration LAN Connection Note • Each CM has an LED that lights up green to identify when it is the Master CM. • Setting the IP address of the Slave CM ensures that ETERNUS Web GUI or ETERNUS CLI can be used from the Slave CM if an error occurs on the LAN path for the Master CM.
Page 208: Network Communication Protocols
5. Connection Configuration LAN Connection Network Communication Protocols The usable LAN ports and functions are different depending on the usage and protocol. The following table shows how the LAN ports may be used (by usage and protocol). Table 75 LAN Port Availability Master CM Slave CM Port...
Page 209 5. Connection Configuration LAN Connection Master CM Slave CM Port Usage Protocol tcp / udp Direction Remarks number ´ ´ REMCS smtp 25 (*2) ¡ (*3) ¡ (*3) Used for (client) failure (remote support) notificatio n, etc. pop3 110 (*2) ´...
Page 210: San Connection
5. Connection Configuration SAN Connection SAN Connection FC, iSCSI, and SAS are available as host interfaces. The server and the ETERNUS DX can be connected directly or via a switch. Host Interface This section describes each host interface. The supported host interfaces vary between ETERNUS DX models. For details about host interfaces, refer to "Host Interface"...
Page 211: Table 76 Types Of Host Interfaces
5. Connection Configuration SAN Connection The following types of host interfaces are available: Table 76 Types of Host Interfaces DX500 S5 DX100 S5 Type (operation mode) Transfer rate DX60 S5 DX600 S5 DX200 S5 DX900 S5 iSCSI 10Gbit/s Fixed at 10Gbit/s —...
Page 212 5. Connection Configuration SAN Connection • Internet Protocol IPv4 and IPv6 are supported. Data Center Bridging (DCB) • iSCSI 10Gbit/s interfaces support the Data Center Bridging (DCB) function. DCB is an enhanced function of traditional Ethernet and a standard for Fabric connections in data centers. The DCB function allows connections to Converged Enhanced Ethernet (CEE) environments.
Page 213: Access Method
5. Connection Configuration SAN Connection Access Method This section explains the connection configurations between server Host Bus Adapters (HBAs) and ETERNUS DX host interface ports. ■ Single Path Connection A single path configuration connects the ETERNUS DX to a server via a single path. The server cannot access an ETERNUS DX when a component (such as a controller, HBA, switch, or cable) on the path has a problem.
Page 214: Figure 108 Multipath Connection (When A San Connection Is Used - Basic Connection Configuration)
5. Connection Configuration SAN Connection ■ Multipath Configuration A multipath configuration connects the ETERNUS DX to a server via multiple paths (multipath). System reliability is improved due to the path redundancy. If a path fails, access can continue by using the path failover function that switches access from the failed path to another path.
Page 215: Figure 110 Multipath Connection (When A San Connection Is Used For Enhanced Performance)
5. Connection Configuration SAN Connection Figure 110 Multipath Connection (When a SAN Connection Is Used for Enhanced Performance) Server Server Port Port Port Port Port Port Port Port CA#0 CA#1 CA#0 CA#1 CM#0 CM#1 ETERNUS DX Caution • When configuring multipathing for reliability, make sure to configure a redundant connection for the controllers of the ETERNUS DX.
Page 216: Remote Connections
5. Connection Configuration Remote Connections Remote Connections An FC or iSCSI interface is available for a remote connection. When a remote connection is used, change the host interface port mode setting from "CA" to "RA". Caution When different types of remote interfaces exist in the same ETERNUS AF/DX, make sure to use the same type of interface for each REC path.
Page 217: Figure 113 An Fc Connection For A Remote Copy Between Eternus Af/Dx Storage Systems (When Redundant Paths Are Used)
5. Connection Configuration Remote Connections ■ Fibre Channel (FC) Data transfer is performed between multiple ETERNUS AF/DX storage systems by using the host interface. The ETERNUS AF/DX can be connected to the destination storage system directly or with the switch. A digital service unit is required for remote connections if a line is used.
Page 218: Connectable Models
5. Connection Configuration Remote Connections Connectable Models The following table shows the models that can be connected with a remote copy, and the interfaces that can be used. Table 78 Connectable Models and Available Remote Interfaces Remote interface ETERNUS DX100 S5/DX200 S5, ETERNUS DX500 S5/ Connectable model DX600 S5/DX900 S5 iSCSI...
Page 219: Nas Connection
5. Connection Configuration NAS Connection NAS Connection Ethernet is used for a NAS interface (NIC-CA). The server and the ETERNUS DX can be connected directly or via a switch. NAS Interface (NIC-CA) This section describes the NAS interface specifications. Ethernet is a NAS connection interface. An Ethernet network can be accessed as a file server from multiple connected clients with different operating systems, for the easy sharing of data.
Page 220: Table 80 Nas Firewall
5. Connection Configuration NAS Connection Caution During the configuration phase • Since the maximum number of VLAN IDs that can be configured depends on the number of NAS interfaces, the ports that do not use VLAN (with no VLAN ID setting) are also counted as VLAN IDs. •...
Page 221 5. Connection Configuration NAS Connection Caution During the configuration phase • For the NAS system of the ETERNUS DX, the following are used as IP addresses. - 169.254.251.0/16 - 169.254.251.1/16 - 169.254.252.0/16 - 169.254.252.1/16 - 169.254.253.0/16 - 169.254.253.1/16 - 169.254.254.0/16 - 169.254.254.1/16 Therefore, connections with servers and clients with equivalent IP addresses are not possible.
Page 222: Redundant Method
5. Connection Configuration NAS Connection Redundant Method This section explains a NAS connection and also a configuration with a NAS connection for the ETERNUS DX. IMPORTANT During the configuration phase Specify an IP address in a different subnet for each NAS port in the same controller. Single Path Connection For a single path connection, only one controller is connected to the NAS network.
Page 223: Figure 117 Multipath Connection (Active-Active Connection) (When A Nas Connection Is Used)
5. Connection Configuration NAS Connection During the operation phase • During a multipath connection, if a failover or a failback is performed due to a controller failure or a path error, the path that is being accessed becomes temporarily offline and the access path switch occurs.
Page 224: Table 81 Estimated Required Time For Failover Or Failback
5. Connection Configuration NAS Connection ● Estimated Required Time for Failover or Failback The time it takes for a failover or a failback varies depending on the events that occurred, the OS used, and the network environment or configuration. The following table shows the estimated required time. Table 81 Estimated Required Time for Failover or Failback Event...
Page 225: Figure 118 Bonding
5. Connection Configuration NAS Connection Bonding Bonding is a function that creates a single virtual network interface from NAS ports in the ETERNUS DX for communication. By expanding the communication bandwidth, efficient load balancing is realized and performance is improved. In addition, fault tolerance is improved with port duplication. Even if an error occurs in a port or cable with the Bonding setting, communication can be continued with other ports.
Page 226: Table 82 Features Of The Bonding Operation Mode
5. Connection Configuration NAS Connection ■ Bonding Operation Mode Six operation modes are available for Bonding. Select the appropriate mode according to the usage. Using Mode 4 is recommended when there are no special requirements. The following table shows the features of each mode. Table 82 Features of the Bonding Operation Mode Performance improvements (load...
Page 227: Table 83 Recovery Requirements After A Link Down State For All Member Ports
Specify "1" for the "linkaggregation collecting minimum count" in the switch setting. If a value other than "1" is set, the operation may not work correctly. For switches other than the Fujitsu SR-X series, this set item may have different names and specifications.
Page 228: Figure 119 Multipath Connection When Using Bonding
5. Connection Configuration NAS Connection ■ Multipath Connection When Using Bonding To configure a multipath connection, set multipath with master ports with the Bonding setting. For ports configured with a multipath connection, IP addresses in the same subnet must be specified. The following shows an example of a connection when bundling two NAS interface ports by Bonding, defining two VLANs for the virtual devices, and configuring a multipath (Active-Active connection).
Page 229 5. Connection Configuration NAS Connection Configure a multipath using ports with the same port number - CM#0 CA#1 Port#0 and CM#1 CA#1 Port#0 - CM#0 CA#1 Port#1 and CM#1 CA#1 Port#1 - CM#0 CA#1 Port#2 and CM#1 CA#1 Port#2 - CM#0 CA#1 Port#3 and CM#1 CA#1 Port#3 NIC-CA#0 NIC-CA#1 NIC-CA#0...
Page 230: Network Path Control
5. Connection Configuration NAS Connection Network Path Control To connect multiple subnetworks to networks in the NAS environment, configure the appropriate path information between the ETERNUS DX and the client. If the settings are not correct, path control does not work and connection fail or data transfer takes long time because the appropriate path is not selected.
Page 231: Ftp/Fxp
5. Connection Configuration NAS Connection FTP/FXP Shared folders can be accessed using the File Transfer Protocol (FTP) and the File eXchange Protocol (FXP). Up to five shared folders can be published using FTP. For FXP, data in the shared folder can be transferred between ETERNUS DX storage systems. For access using FTP and FXP, a user authentication in the authentication servers (Active Directory authentication servers and LDAP authentication servers) or an account that is registered in the local user authentication setting is required.
Page 232: Hardware Configurations
Hardware Configurations This chapter explains hardware configurations for the ETERNUS DX. Multiple options can be selected in the ETERNUS DX according to the customer's requirements. This chapter describes the installation conditions and standard installation rules for each component. Configuration Schematics The following diagrams show minimum and maximum configurations for ETERNUS DX storage systems.
Page 233: Figure 122 Eternus Dx100 S5/Dx200 S5 Maximum Configuration
6. Hardware Configurations Configuration Schematics ● ETERNUS DX100 S5/DX200 S5 Maximum Configuration Figure 122 ETERNUS DX100 S5/DX200 S5 Maximum Configuration PANEL CM#0 CM#1 Memory Memory (*1) (*1) HD-DE PANEL IOM#0 IOM#1 PANEL IOM#0 IOM#1 *1: For the ETERNUS DX100 S5, one Memory per CM. For the ETERNUS DX200 S5, two Memory per CM.
Page 234: Figure 123 Eternus Dx500 S5 Maximum Configuration
6. Hardware Configurations Configuration Schematics ● ETERNUS DX500 S5 Maximum Configuration Figure 123 ETERNUS DX500 S5 Maximum Configuration PANEL Memory Memory BUD0 BUD0 IOC0 IOC1 IOC0 IOC1 BUD1 BUD1 CM#0 CM#1 CPSU CPSU HD-DE HD-DE PANEL PANEL IOM#0 IOM#1 IOM#0 IOM#1 DPSU DPSU...
Page 235: Figure 124 Eternus Dx600 S5 Maximum Configuration
6. Hardware Configurations Configuration Schematics ● ETERNUS DX600 S5 Maximum Configuration Figure 124 ETERNUS DX600 S5 Maximum Configuration PANEL Memory Memory BUD0 BUD0 IOC0 IOC1 IOC0 IOC1 BUD1 BUD1 CM#0 CM#1 CPSU CPSU HD-DE HD-DE PANEL PANEL IOM#0 IOM#1 IOM#0 IOM#1 DPSU DPSU...
Page 236: Figure 125 Eternus Dx900 S5 Maximum Configuration
6. Hardware Configurations Configuration Schematics ● ETERNUS DX900 S5 Maximum Configuration Figure 125 ETERNUS DX900 S5 Maximum Configuration DE#01 DE#02 DE#E3 DE#04 DE#05 DE#06 DE#E7 DE#08 DE#09 DE#0A DE#EB DE#0C DE#0D DE#0E DE#EF DE#11 DE#12 DE#F3 DE#14 DE#15 DE#16 DE#F7 DE#18 DE#19 DE#1A...
Page 237: Figure 126 Enclosure Connection Path (When Only One Controller Is Installed)
6. Hardware Configurations Configuration Schematics ■ Enclosure Connection Path In the ETERNUS DX, multiple paths are used to connect a controller enclosure (CE) to drive enclosures (DE). A drive enclosure has two independent drive interface ports. Path redundancy is maintained by connecting the drive enclosure to two controllers directly.
Page 238: Figure 128 Enclosure Connection Path (When Only One Controller Is Installed)
6. Hardware Configurations Configuration Schematics ● ETERNUS DX100 S5/DX200 S5 Connect the controller enclosure to the drive enclosure as shown in the following figures. Connection paths are not duplicated when only one controller is installed. Figure 128 Enclosure Connection Path (When Only One Controller Is Installed) DE #0A DI (IN) DE #0x...
Page 239: Figure 130 Enclosure Connection Paths (Eternus Dx500 S5)
6. Hardware Configurations Configuration Schematics ● ETERNUS DX500 S5 One controller enclosure and up to 23 drive enclosures can be connected to the ETERNUS DX500 S5. There are four connection paths between a controller enclosure and drive enclosures. For each connection path, up to six drive enclosures and up to 144 drives can be connected.
Page 240: Figure 131 Enclosure Connection Paths (Eternus Dx600 S5)
6. Hardware Configurations Configuration Schematics ● ETERNUS DX600 S5 One controller enclosure and up to 43 drive enclosures can be connected to the ETERNUS DX600 S5. There are four connection paths between a controller enclosure and drive enclosures. For each connection path, up to 11 drive enclosures and up to 264 drives can be connected.
Page 241: Figure 132 Enclosure Connection Paths (Eternus Dx900 S5)
6. Hardware Configurations Configuration Schematics Figure 132 Enclosure Connection Paths (ETERNUS DX900 S5) Line 0 Line 1 Line 2 Line 3 DI (IN) DI (IN) DI (IN) DI (IN) DE #E3 DE #E7 DE #EB DE #EF DI (IN) DI (OUT) DI (IN) DI (OUT) DI (IN)
Page 242: Frontend Enclosure
6. Hardware Configurations Frontend Enclosure Frontend Enclosure The frontend enclosure of the ETERNUS DX900 S5 has a system operation panel, service controllers (SVCs), and fan units in the front, and power supply units and frontend routers (FRTs) in the rear. ■...
Page 243: Figure 135 Rear View Of A Frontend Enclosure
6. Hardware Configurations Frontend Enclosure SVC (SVC#0, SVC#1) (Refer to "● Service Controllers (SVC)" (page 245).) FEMP-BRG Fan unit (FANU#0, FANU#1, FANU#2, FANU#3) A unit for cooling the inside of the ETERNUS DX. The unit controls the temperature inside the ETERNUS DX.
Page 244: Figure 136 System Operation Panel
6. Hardware Configurations Frontend Enclosure ■ Component This section explains the components of a frontend enclosure. ● System Operation Panel The system operation panel in the front of the frontend enclosure has LEDs, a LCD panel, panel keys, and a Power switch.
Page 245: Figure 137 Service Controllers
6. Hardware Configurations Frontend Enclosure ● Service Controllers (SVC) An SVC coordinates with the controller and is a unit that controls the monitoring function for the entire ETERNUS DX. Two units are installed in a frontend enclosure. Figure 137 Service Controllers CM port This port is used to connect SVCs and CMs.
Page 246: Controller Enclosure
6. Hardware Configurations Controller Enclosure CM port (CM#0, CM#1) This port is used to connect SVCs and CMs. Controller Enclosure This section explains the controller enclosure and the main components of the ETERNUS DX. ETERNUS DX60 S5 • • ETERNUS DX100 S5/DX200 S5 •...
Page 247: Figure 142 Rear View Of A Controller Enclosure (When The Eternus Dx60 S5 Is Installed With Only One Controller)
6. Hardware Configurations Controller Enclosure ● Rear View Figure 142 Rear View of a Controller Enclosure (When the ETERNUS DX60 S5 Is Installed with Only One Controller) CM#0 PSU#0 PSU#1 Controller (CM#0) (Refer to "Controllers" (page 257).) PWC port This port is used to connect a power synchronized unit with an RS232C cable. (Refer to "■...
Page 248: Figure 143 Rear View Of A Controller Enclosure (When The Eternus Dx60 S5 Is Installed With Two Controllers)
6. Hardware Configurations Controller Enclosure Figure 143 Rear View of a Controller Enclosure (When the ETERNUS DX60 S5 Is Installed with Two Controllers) CM#0 CM#1 PSU#0 PSU#1 Controller (CM#0, CM#1) (Refer to "Controllers" (page 257).) PWC port This port is used to connect a power synchronized unit with an RS232C cable. (Refer to "■...
Page 249: Eternus Dx100 S5/Dx200 S5
6. Hardware Configurations Controller Enclosure ETERNUS DX100 S5/DX200 S5 The ETERNUS DX100 S5/DX200 S5 controller enclosure contains drives installed in the front, and controllers and power supply units in the rear. Two types of controller enclosures are available: a 2.5" type and a 3.5" type. ●...
Page 250: Figure 146 Rear View Of A Controller Enclosure (When The Eternus Dx100 S5/Dx200 S5 Is Installed With Only One Controller)
6. Hardware Configurations Controller Enclosure ● Rear View Figure 146 Rear View of a Controller Enclosure (When the ETERNUS DX100 S5/DX200 S5 Is Installed with Only One Controller) CM#0 CA#0 CA#1 PSU#0 PSU#1 Controller (CM#0) (Refer to "Controllers" (page 257).) PWC port This port is used to connect a power synchronized unit with an RS232C cable.
Page 251: Figure 147 Rear View Of A Controller Enclosure (When The Eternus Dx100 S5/Dx200 S5 Is Installed With Only One Controller)
6. Hardware Configurations Controller Enclosure Figure 147 Rear View of a Controller Enclosure (When the ETERNUS DX100 S5/DX200 S5 Is Installed with Only One Controller) CM#0 CM#1 CA#0 CA#1 CA#0 CA#1 PSU#0 PSU#1 Controller (CM#0, CM#1) (Refer to "Controllers" (page 257).) PWC port This port is used to connect a power synchronized unit with an RS232C cable.
Page 252: Eternus Dx500 S5/Dx600 S5
6. Hardware Configurations Controller Enclosure ETERNUS DX500 S5/DX600 S5 The ETERNUS DX500 S5/DX600 S5 controller enclosure contains an operation panel, battery units, PCIe Flash Modules (PFMs), and drives installed in the front and controllers (CMs), host interfaces (CAs), and power supply units in the rear.
Page 253: Figure 150 Rear View Of A Controller Enclosure (Eternus Dx500 S5)
6. Hardware Configurations Controller Enclosure ● Rear View ETERNUS DX500 S5 • Figure 150 Rear View of a Controller Enclosure (ETERNUS DX500 S5) CM#1 CA#0 CA#1 CPSU#0 CPSU#1 CM#0 CA#0 CA#1 Controller (CM#0, CM#1) (Refer to "Controllers" (page 257).) Host interface (CA#0, CA#1) (Refer to "■...
Page 254: Figure 151 Rear View Of A Controller Enclosure (Eternus Dx600 S5)
6. Hardware Configurations Controller Enclosure • ETERNUS DX600 S5 Figure 151 Rear View of a Controller Enclosure (ETERNUS DX600 S5) CA#2 CA#3 CM#1 CA#0 CA#1 CPSU#0 CPSU#1 CA#2 CA#3 CM#0 CA#0 CA#1 Controller (CM#0, CM#1) (Refer to "Controllers" (page 257).) Host interface (CA#0, CA#1, CA#2, CA#3) (Refer to "■...
Page 255: Eternus Dx900 S5
6. Hardware Configurations Controller Enclosure ETERNUS DX900 S5 The ETERNUS DX900 S5 controller enclosure contains an operation panel, battery units, PCIe Flash Modules (PFMs), and drives installed in the front and controllers (CMs), host interfaces (CAs), and power supply units in the rear.
Page 256: Figure 154 Rear View Of A Controller Enclosure (Eternus Dx900 S5)
6. Hardware Configurations Controller Enclosure ● Rear View Figure 154 Rear View of a Controller Enclosure (ETERNUS DX900 S5) CA#2 CA#3 CM#1 CA#0 CA#1 CPSU#0 CPSU#1 CA#2 CA#3 CM#0 CA#0 CA#1 Controller (CM#0, CM#1) (Refer to "Controllers" (page 257).) Host interface (CA#0, CA#1, CA#2, CA#3) (Refer to "■...
Page 257: Controllers
- Unified (NAS connection) is not available. - High-density drive enclosures cannot be installed. • Fujitsu recommends that the dual-controller types, in which the controller and I/O module are duplicated, be used in a system where a high level of reliability is required.
Page 258: Table 85 Capacity And Number Of Buds For Each Controller
6. Hardware Configurations Controller Enclosure ■ A BUD is non-volatile memory in which the firmware of an ETERNUS DX is registered. A BUD is used as an area to back up cache data in the system memory if a power failure occurs. The following table shows the capacity and number of BUDs for each controller.
Page 259: Table 86 Maximum Number Of Host Interfaces Per Controller
6. Hardware Configurations Controller Enclosure ■ Host Interfaces A host interface (CA) is an adapter that has interface ports to connect a controller to a server. The following table shows the maximum number of host interfaces that can be installed per controller. Table 86 Maximum Number of Host Interfaces per Controller Model...
Page 260: Figure 155 Host Interface Ports (Eternus Dx60 S5)
6. Hardware Configurations Controller Enclosure ● ETERNUS DX60 S5 Host Interface There are five types of host interfaces: FC 16Gbit/s, FC 8Gbit/s, iSCSI 10Gbit/s (10GBASE-T), iSCSI 1Gbit/s, and SAS 12Gbit/s. Figure 155 Host Interface Ports (ETERNUS DX60 S5) iSCSI 10Gbit/s (10GBASE-T) SAS 12Gbit/s iSCSI 1Gbit/s Design Guide...
Page 261: Figure 156 Host Interface Ports (Eternus Dx100 S5/Dx200 S5)
6. Hardware Configurations Controller Enclosure ● ETERNUS DX100 S5/DX200 S5 Host Interface There are nine types of host interfaces: FC 32Gbit/s, FC 16Gbit/s, iSCSI 10Gbit/s (10GBASE-SR/10GBASE-CR), iSCSI 10Gbit/s (10GBASE-T), iSCSI 1Gbit/s, Ethernet 10Gbit/s, Ethernet 1Gbit/s, and SAS 12Gbit/s. Figure 156 Host Interface Ports (ETERNUS DX100 S5/DX200 S5) FC 2 ports FC 2 ports...
Page 262: Figure 157 Host Interface Ports (Eternus Dx500 S5/Dx600 S5)
6. Hardware Configurations Controller Enclosure ● ETERNUS DX500 S5/DX600 S5 Host Interface There are seven types of host interfaces: FC 32Gbit/s, FC 16Gbit/s, iSCSI 10Gbit/s (10GBASE-SR / 10GBASE-CR), iSCSI 1Gbit/s, Ethernet 10Gbit/s, and Ethernet 1Gbit/s. Figure 157 Host Interface Ports (ETERNUS DX500 S5/DX600 S5) FC 2 ports FC 4 ports iSCSI 10Gbit/s (10GBASE-SR)
Page 263: Table 88 Drive Interface Port Specification (Controller)
6. Hardware Configurations Controller Enclosure ■ Drive Interface Ports This port is used to connect drive enclosures. The drive interface port specifications are shown below. Table 88 Drive Interface Port Specification (Controller) Interface Transfer rate (max.) Connector type Number of ports for each controller 12Gbit/s miniSAS HD 1 (ETERNUS DX60 S5/DX100 S5/DX200 S5)
Page 264: Component
6. Hardware Configurations Controller Enclosure Component This section explains the components (excluding the controller) in the controller enclosure. ■ PCIe Flash Module (PFM) (ETERNUS DX500 S5/DX600 S5/DX900 S5) A PFM is a module that is installed to operate the Extreme Cache function. The read cache capacity significantly increases when Extreme Cache is used.
Page 265: Figure 160 Power Supply Unit (Eternus Dx100 S5 [Dc Power Type])
6. Hardware Configurations Controller Enclosure ● ETERNUS DX100 S5 (DC Power Type) Figure 160 Power Supply Unit (ETERNUS DX100 S5 [DC Power Type]) POWER LED FAN FAIL LED FAULT LED AC MISSING LED PSU switch This switch is used to turn on and off the DC power supply. Inlet This inlet is used to connect a power cord.
Page 266: Drive Enclosure
6. Hardware Configurations Drive Enclosure Drive Enclosure This section explains the main components in the drive enclosure. The drive enclosure contains drives installed in the front, and I/O modules and power supply units in the rear. There are three types of drive enclosures that correspond to available drive sizes (2.5", 3.5", and high-density 3.5").
Page 267: External Views Of A High-Density Drive Enclosure
6. Hardware Configurations Drive Enclosure ■ Rear View of a Drive Enclosure Figure 164 Rear View of a 2.5"/3.5" Type Drive Enclosure (When Only One I/O Module Is Installed) IOM#0 PSU#0 PSU#1 Figure 165 Rear View of a 2.5"/3.5" Type Drive Enclosure (When Two I/O Modules Are Installed) IOM#0 IOM#1 PSU#0...
Page 268: Figure 167 Top View Of A High-Density Drive Enclosure With The Cover Opened
6. Hardware Configurations Drive Enclosure Operation panel An operation panel has a DE-ID display and LEDs. Disk Activity Panel (DAP) The Disk Activity Panel (DAP) has a Slot No. LED for each drive. Front cover ■ Top View of a High-Density Drive Enclosure Figure 167 Top View of a High-Density Drive Enclosure with the Cover Opened Rear...
Page 269: Figure 168 Rear View Of A High-Density Drive Enclosure
6. Hardware Configurations Drive Enclosure ■ Rear View of a High-Density Drive Enclosure Figure 168 Rear View of a High-Density Drive Enclosure IOM#0 IOM#1 PSU#2 PSU#3 PSU#0 PSU#1 FEM#0 FEM#1 I/O module (IOM#0, IOM#1) (Refer to "■ I/O Modules" (page 270).) Power supply unit (PSU#0, PSU#1, PSU#2, PSU#3) (Refer to...
Page 270: Component
6. Hardware Configurations Drive Enclosure Component This section explains the components of the drive enclosures and the high-density drive enclosures. ■ I/O Modules The I/O module is a component that controls how the controller and the drives interact. The I/O module is connected to the controller or an I/O module on another drive enclosure. A drive enclosure has two I/O modules, which makes it possible for a failed I/O module to be replaced while the system is running.
Page 271: Figure 171 Power Supply Unit (Ac Power Type)
6. Hardware Configurations Drive Enclosure ■ Power Supply Units There are two types of the power supply units: AC power type and DC power type. The AC power type power supply unit converts input AC power from a power socket to DC power and supplies power to each component. Each power supply unit contains fans.
Page 272: Table 92 2.5" Drive Specifications (2.5" Type Drive Enclosure)
6. Hardware Configurations Drive Enclosure ■ Drives Three types of drives are available: 2.5" drives, 3.5" drives, and 3.5" drives for high-density drive enclosures. Up to twenty-four 2.5" drives can be installed in a single 2.5" type drive enclosure. Up to twelve 3.5" drives can be installed in a single 3.5" type drive enclosure. Up to sixty 3.5"...
Page 273: Table 93 3.5" Drive Specifications (3.5" Type Drive Enclosure)
6. Hardware Configurations Drive Enclosure ● 3.5" Drives The 3.5" drive specifications are shown below. Table 93 3.5" Drive Specifications (3.5" Type Drive Enclosure) Drive interface (maximum Rotational Product name Storage media Storage capacity transfer rate) speed SAS disks Serial Attached SCSI Hard disk 1.2TB, 2.4TB (*1) 10,000rpm...
Page 274: Table 94 3.5" Drive Specifications For High-Density Drive Enclosures
6. Hardware Configurations Drive Enclosure ● 3.5" Drives for High-Density Drive Enclosures The 3.5" drive specifications for high-density drive enclosures are shown below. Table 94 3.5" Drive Specifications for High-Density Drive Enclosures Drive interface (maximum Rotational Product name Storage media Storage capacity transfer rate) speed...
Page 275: Power Distribution Unit
6. Hardware Configurations Power Distribution Unit Power Distribution Unit There are two sizes for power distribution units: 1U and 2U. A power distribution unit is an option to connect power supply units to power outlets when power sockets are limited. ■...
Page 276: Figure 174 Power Distribution Unit (Ac16A/200V, 2U, 16 Outlets)
6. Hardware Configurations Power Distribution Unit ■ Power Distribution Unit (AC16A/200V, 2U, 16 Outlets) There are 16 outlets. Figure 174 Power Distribution Unit (AC16A/200V, 2U, 16 Outlets) Main line switch This turns on and off the power distribution unit. Outlet (OUTPUT) This is a socket (IEC60320 C13) for outgoing power supply.
Page 277: Power Synchronized Unit
6. Hardware Configurations Power Synchronized Unit ■ Power Distribution Unit (AC24A/200V, 2U, 16 Outlets) There are 16 outlets. Figure 175 Power Distribution Unit (AC24A/200V, 2U, 16 Outlets) Main line switch This turns on and off the power distribution unit. Outlet (OUTPUT) This is a socket (IEC60320 C13) for outgoing power supply.
Page 278: Installation Conditions And Installation Rules
6. Hardware Configurations Installation Conditions and Installation Rules Installation Conditions and Installation Rules This section describes the installation conditions and standard installation rules for the following optional products. • Controller enclosure Controller module • System memory • • Extreme Cache Host interface •...
Page 279: System Memory
6. Hardware Configurations Installation Conditions and Installation Rules ■ Number of Installable Controller Modules Install two controllers in a controller enclosure. ■ Installation Order Install CM#0 first, followed by CM#1. Figure 176 Controller Installation Order Controller 0 (CM#0) Controller 1 (CM#1) Rear view of a controller enclosure System Memory This section explains the installation conditions and installation rules for system memory modules.
Page 280: Table 98 Estimated System Memory Capacity Of Each Storage System (Eternus Dx500 S5 With Both The Deduplication/Compression Function And The Nas Function Disabled)
6. Hardware Configurations Installation Conditions and Installation Rules ■ Number of Installable System Memory Modules In the ETERNUS DX200 S5, two system memory modules can be installed for each controller and four system memory modules can be installed for each storage system. In the ETERNUS DX500 S5, four system memory modules can be installed for each controller and eight system memory modules can be installed for each storage system.
Page 281: Table 100 Estimated System Memory Capacity Of Each Storage System (Eternus Dx500 S5 With The Deduplication/Compression Function Disabled And The Nas Function Enabled)
6. Hardware Configurations Installation Conditions and Installation Rules Table 100 Estimated System Memory Capacity of Each Storage System (ETERNUS DX500 S5 with the Deduplication/Compression Function Disabled and the NAS Function Enabled) System memory capacity (with the Deduplication/Compression function disabled and the NAS function Drive capacity enabled) Up to 25,599GB...
Page 282: Extreme Cache
6. Hardware Configurations Installation Conditions and Installation Rules Table 105 Estimated System Memory Capacity of Each Controller Enclosure (ETERNUS DX900 S5 with the Compression Function Enabled) Drive capacity System memory capacity (with the Compression function enabled) Up to 112,639GB 768GB 112,640GB or more 1,536GB To enable the Compression function in the ETERNUS DX900 S5, a system memory capacity of 768GB or...
Page 283: Figure 177 Extreme Cache Module Installation Diagram
6. Hardware Configurations Installation Conditions and Installation Rules Caution • The Extreme Cache function is not available because PFMs cannot be installed in the ETERNUS DX60 S5/ DX100 S5/DX200 S5. • PFMs are installed in drive slots of the controller enclosure and the slots can be used by PFMs or drives. PFMs cannot be installed in slots where a drive is already installed.
Page 284: Host Interface
6. Hardware Configurations Installation Conditions and Installation Rules Host Interface This section describes the installation conditions and standard installation rules for host interfaces. ■ Types of Host Interfaces The following types of host interfaces are available: Table 107 Types of Host Interfaces DX100 S5 DX500 S5 Host interface...
Page 285: Figure 178 Host Interface Installation Diagram (Eternus Dx100 S5/Dx200 S5 [Two-Port Ca Type])
6. Hardware Configurations Installation Conditions and Installation Rules ■ Number of Installable Host Interfaces In the ETERNUS DX100 S5/DX200 S5, two host interfaces for base and expansion configurations (four host interfaces per storage system) can be installed in a controller. In the ETERNUS DX500 S5, two host interfaces can be installed in the controller.
Page 286: Figure 179 Host Interface Installation Diagram (Eternus Dx500 S5)
6. Hardware Configurations Installation Conditions and Installation Rules Figure 179 Host Interface Installation Diagram (ETERNUS DX500 S5) CA#0 CA#1 Controller 1 (CM#1) CA#0 CA#1 Controller 0 (CM#0) Rear view of a controller enclosure ETERNUS DX600 S5 • Install the host interfaces in CA#0, CA#1, CA#2, and CA#3 in ascending order according to the priority order. The configuration is the same for Controller 0 (CM#0) and Controller 1 (CM#1).
Page 287: Unified License
6. Hardware Configurations Installation Conditions and Installation Rules Figure 181 Host Interface Installation Diagram (ETERNUS DX900 S5) CA#2 CA#3 CA#0 CA#1 Controller 1 (CM#1) CE#1 CA#2 CA#3 CA#0 CA#1 Controller 0 (CM#0) CA#2 CA#3 CA#0 CA#1 Controller 1 (CM#1) CE#0 CA#2 CA#3 CA#0...
Page 288: Table 108 Number Of Installable Drive Enclosures
6. Hardware Configurations Installation Conditions and Installation Rules ■ Number of Installable Drive Enclosures The following table shows the number of installable drive enclosures. Table 108 Number of Installable Drive Enclosures Type DX60 S5 DX100 S5 DX200 S5 DX500 S5 DX600 S5 DX900 S5 2.5"...
Page 289: Drive
6. Hardware Configurations Installation Conditions and Installation Rules Drive This section explains the installation conditions and installation rules for drives. ■ Types of Drives The ETERNUS DX supports the latest drives that have the high-speed SAS (Max. 12Gbit/s) interface. The following drive types can be installed in the ETERNUS DX. Some drive types have a data encryption function. SAS disks •...
Page 290: Table 110 Drive Characteristics
6. Hardware Configurations Installation Conditions and Installation Rules - 3.5" Nearline SAS disks (8TB) - 3.5" Nearline SAS disks (10TB) - 3.5" Nearline SAS disks (12TB) - 3.5" Nearline SAS disks (14TB) - 3.5" Nearline SAS self encrypting disks (8TB) - 3.5"...
Page 291: Table 111 Number Of Installable Drives
6. Hardware Configurations Installation Conditions and Installation Rules ■ Number of Installable Drives The following table shows the number of installable drives when the maximum number of drive enclosures are installed in each model. Table 111 Number of Installable Drives Type DX60 S5 DX100 S5...
Page 292: Figure 182 Drive Installation Diagram For High-Density Drive Enclosures
6. Hardware Configurations Installation Conditions and Installation Rules ■ Drives for High-Density Drive Enclosures The installation priority order for drives in high-density drive enclosures is shown below. 3.5" Nearline SAS disks for high-density drive enclosures (4TB/7.2krpm) 3.5" Nearline SAS disks for high-density drive enclosures (8TB/7.2krpm) 3.5"...
Page 293: Figure 183 Installation Diagram For 2.5" Drives
6. Hardware Configurations Installation Conditions and Installation Rules ■ Installation Order for 2.5" Drives The installation priority order for 2.5" drives is shown below. 2.5" SSDs (800GB) 2.5" SSDs (960GB) (Value SSDs) 2.5" SSDs (1.92TB) (Value SSDs) 2.5" SSDs (3.84TB) (Value SSDs) 2.5"...
Page 294: Figure 184 Installation Diagram For 3.5" Drives
6. Hardware Configurations Installation Conditions and Installation Rules ■ Installation Order for 3.5" Drives The installation priority order for 3.5" drives is shown below. 3.5" SSDs (800GB) 3.5" SSDs (960GB) (Value SSDs) 3.5" SSDs (1.92TB) (Value SSDs) 3.5" SSDs (3.84TB) (Value SSDs) 3.5"...
Page 295: Recommended Raid Group Configuration
6. Hardware Configurations Recommended RAID Group Configuration Recommended RAID Group Configuration In an ETERNUS DX, a controller enclosure is connected to drive enclosures with multiple paths. For the ETERNUS DX60 S5/DX100 S5/DX200 S5 • There are no restrictions on the installation locations of drives that configure a RAID group. To improve reliability, the installation location of drives that configure a RAID group must be considered.
Page 296: Figure 185 Drive Combination 1
6. Hardware Configurations Recommended RAID Group Configuration Example 1: All drives are installed in a single enclosure Figure 185 Drive Combination 1 DE#00 Mirroring Example 2: Paired drives are installed in two different enclosures Figure 186 Drive Combination 2 DE#00 Mirroring DE#10 Example 3: Paired drives are installed in three different enclosures...
Page 297: Figure 188 Drive Combination 4
6. Hardware Configurations Recommended RAID Group Configuration ■ Double Striping Configuration with Distributed Parity RAID5+0(2D+1P) ´2 is used in the following examples to explain how to install drives that are configured for double striping with distributed parity. The drive number is determined by the DE-ID of the enclosure and the slot number in which the drive is installed.
Page 298: Figure 190 Recommended Raid1/Raid1+0 Configuration Example
6. Hardware Configurations Recommended RAID Group Configuration Redundancy Group 2 ■ RAID Configuration Example (ETERNUS DX500 S5/DX600 S5/DX900 S5) Drives are installed in units of RAID groups. ● Recommended RAID1/RAID1+0 Configuration Example The drives that configure the RAID group are divided into two or more path groups. Make sure the paired drives that configure mirroring are divided into different path groups.
Page 299: Figure 191 Recommended Raid5/Raid5+0/Raid6 Configuration Example
6. Hardware Configurations Recommended RAID Group Configuration ● Recommended RAID5/RAID5+0/RAID6 Configuration Example The drives that configure the RAID group are divided into two or more path groups. Figure 191 Recommended RAID5/RAID5+0/RAID6 Configuration Example Controller (CM#1) Controller (CM#0) DE#01 RAID6 RAID5 RAID5+0 (6D+2P) (4D+1P)
Page 300: Figure 192 Recommended Raid6-Fr Configuration Example
6. Hardware Configurations Recommended RAID Group Configuration ● Recommended RAID6-FR Configuration Example The drives that configure the RAID group are divided into two or more path groups. Figure 192 Recommended RAID6-FR Configuration Example Controller (CM#0) Controller (CM#1) DE#01 RAID6-FR ((3D+2P) ×2+1HS) DE#10 DE#20 DE#30...
Page 301: Maintenance/Expansion
Maintenance/Expansion Hot Swap/Hot Expansion "Hot swap" refers to the replacement of components or updating of the firmware while the system is running. "Hot expansion" refers to the addition of components while the system is running. ETERNUS DX60 S5 The table below shows whether hot swap or hot expansion for components of the ETERNUS DX60 S5 is possible. Table 112 Hot Swap and Hot Expansion Availability for Components (ETERNUS DX60 S5) Component...
Page 302 7. Maintenance/Expansion Hot Swap/Hot Expansion ■ User Maintenance Customers can update the following components. To maintain components that are not described in this section, contact your sales representative or maintenance engineer. • Controller firmware ■ User Expansion Customers can expand (add) the following components. To add components that are not described in this section, contact your sales representative or maintenance engineer.
Page 303: Eternus Dx100 S5/Dx200 S5
7. Maintenance/Expansion Hot Swap/Hot Expansion ETERNUS DX100 S5/DX200 S5 The table below shows whether hot swap or hot expansion for components of the ETERNUS DX100 S5/DX200 S5 is possible. Table 113 Hot Swap and Hot Expansion Availability for Components (ETERNUS DX100 S5/DX200 S5) Component Hot swap Hot expansion...
Page 304 7. Maintenance/Expansion Hot Swap/Hot Expansion *5: Operation can be continued during a failure. The status of the ETERNUS DX can be monitored via ETERNUS Web GUI or ETERNUS CLI. *6: FEMs are installed in high-density drive enclosures. ■ User Maintenance Customers can update the following components.
Page 305: Eternus Dx500 S5/Dx600 S5
7. Maintenance/Expansion Hot Swap/Hot Expansion ETERNUS DX500 S5/DX600 S5 The table below shows whether hot swap or hot expansion for components of the ETERNUS DX500 S5/DX600 S5 is possible. Table 114 Hot Swap and Hot Expansion Availability for Components (ETERNUS DX500 S5/DX600 S5) Component Hot swap Hot expansion...
Page 306 7. Maintenance/Expansion Hot Swap/Hot Expansion *3: Bootup and Utility Device. *4: An I/O suspension may be required depending on the firmware changes. *5: Mid Plane. This is a board that is located between the front and rear (controller (CM) or I/O module (IOM) side) of the ETERNUS DX. *6: Operation can be continued during a failure.
Page 307: Eternus Dx900 S5
7. Maintenance/Expansion Hot Swap/Hot Expansion ETERNUS DX900 S5 The table below shows whether hot swap or hot expansion for components of the ETERNUS DX900 S5 is possible. Table 115 Hot Swap and Hot Expansion Availability for Components Component Hot swap Remarks expansion Frontend enclosure (FE)
Page 308: Drive Sanitization
7. Maintenance/Expansion Drive Sanitization ¡: Allowed / ´: Not allowed (cold swap is possible) / —: Not applicable *1: Mid Plane. A board that is located between the front and rear (SVC or FRT, CM or IOM side) of the ETERNUS DX. *2: All of the host interfaces on the CM that will have maintenance performed go offline.
Page 309: Release Information
Release Information This chapter provides firmware modification information, such as information on functions that have been added or modified. Firmware Release Information The firmware version of the ETERNUS DX may need to be upgraded to add optional products or to use updated functions.
Page 310: Specifications
Red Hat Enterprise Linux 8 (for Intel64) Oracle Linux 6 Oracle Linux 7 VMware vSphere 6.0 VMware vSphere 6.5 VMware vSphere 6.7 VMware vSphere 7.0 Oracle VM 3 UNIX servers Solaris 10 SPARC Enterprise Solaris 11 Fujitsu SPARC Servers Design Guide...
Page 311 VMware vSphere 7.0 Oracle VM 3 Citrix Hypervisor 7 (XenServer 7) Citrix Hypervisor 8 FalconStor NSS Oracle SPARC Enterprise Solaris 10 Fujitsu M10 Servers Solaris 11 Fujitsu SPARC M12 System p AIX 7 Power Systems HP 9000 server HP-UX 11i v3...
Page 312 A. Specifications Operating Environment Server Manufacturer Product name Others Other industry standard servers Windows Server 2012 Windows Server 2016 Windows Server 2019 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 (for Intel64) Red Hat Enterprise Linux 8 (for Intel64) SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 12 SUSE Linux Enterprise Server 15...
Page 313: Table 118 Supported Servers And Oss (Iscsi Interface)
VMware vSphere 6.5 VMware vSphere 6.7 VMware vSphere 7.0 Oracle VM 3 UNIX servers Solaris 10 SPARC Enterprise Solaris 11 Fujitsu SPARC Servers Fujitsu Industry standard servers Windows Server 2012 PRIMERGY Windows Server 2016 Windows Server 2019 Red Hat Enterprise Linux 5...
Page 314 A. Specifications Operating Environment Server Manufacturer Product name Oracle SPARC Enterprise Solaris 10 Fujitsu M10 Servers Solaris 11 Fujitsu SPARC M12 HP 9000 server HP-UX 11i v3 HP Integrity server Others Other industry standard servers Windows Server 2012 Windows Server 2016...
Page 315: Table 119 Supported Servers And Oss (Sas Interface)
Server Manufacturer Product name Fujitsu UNIX servers Solaris 10 SPARC Enterprise Solaris 11 Fujitsu SPARC Servers Industry standard servers Windows Server 2012 PRIMERGY Windows Server 2016 Windows Server 2019 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 (for Intel64)
Page 316: Supported Oss (In Nas Environments)
A. Specifications Operating Environment Supported OSs (in NAS Environments) The ETERNUS DX can be connected to OSs that support available protocols for the ETERNUS DX. The confirmed OS for NFSv4.0 can be connected to the ETERNUS DX. The following OSs are confirmed to connect to the ETERNUS DX as a NAS client. The confirmed OSs with the CIFS protocol •...
Page 317 A. Specifications Operating Environment • Mounting a CIFS shared folder from UNIX/Linux by specifying "cifs" in the "mount" command is not supported. • When accessing with a Solaris OS client, there are combinations with the network environment where connections may not be possible. The following table shows connectibility. Connectibility IPv4 environment IPv6 environment...
Page 318: Function Specifications
*1: Use of RAID0 is not recommended because it is not redundant. For RAID0 configurations, data may be lost due to the failure of a single drive. *2: Fujitsu original RAID level that provides the high speed rebuild function, and striping with double distributed parity. *3: The maximum number of RAID groups that can be registered (for the RAID1 configuration).
Page 319: Nas Volume Specifications
A. Specifications Function Specifications NAS Volume Specifications The following table shows the maximum capacity and the maximum number of TPPs and NAS TPVs (NAS volumes) that can be created in the ETERNUS DX. Table 121 Maximum Number of TPPs/NAS TPVs (NAS Volumes) That Can Be Created (For the ETERNUS DX100 S5/DX200 S5 and the ETERNUS DX500 S5/DX600 S5) Model Item...
Page 320 A. Specifications Function Specifications Item Explanation Number of entries in the Access Control List (ACL) for each CIFS 256 (*6) file NFSv3 256 (*6) Number of FTP/FXP sessions (per ETERNUS DX) Supported file types Normal files, directories, and symbolic links (*7) *1: Total number of directories in an ETERNUS DX that can be created in a root directory of the file system.
Page 321: Function Specification List
Function Specification List This appendix shows the combinations of functions that can be executed at the same time and the targets for each function. List of Supported Protocols Table 123 List of Supported Protocols LAN for Operation Item iSCSI (SAN) Ethernet (NAS) Management Operation mode...
Page 322: List Of Target Pools And Volumes For Each Function
B. Function Specification List List of Target Pools and Volumes for Each Function List of Target Pools and Volumes for Each Function The following section shows the functions which can be performed on RAID groups, REC Disk Buffers, and pools. The functions described in this section include functions that can be performed on RAID groups which comprise REC Disk Buffers and pools.
Page 323: Target Volumes Of Each Function
B. Function Specification List List of Target Pools and Volumes for Each Function *3 : The number of TPPs for which the Deduplication/Compression function can be enabled is as follows: • ETERNUS DX200 S5: 4 • ETERNUS DX500 S5: 4 ETERNUS DX600 S5: 8 •...
Page 324 B. Function Specification List List of Target Pools and Volumes for Each Function Standard ODX Buffer Function SDPV FTV (*1) volume Concatenat Single (*2) ´ ´ ´ Forbid Advanced ¡ ¡ ¡ ¡ ¡ Copy ´ ´ ´ ´ ´ ´...
Page 325: Combinations Of Functions That Are Available For Simultaneous Executions
B. Function Specification List Combinations of Functions That Are Available for Simultaneous Executions Combinations of Functions That Are Available for Simultaneous Executions This section describes the availability of simultaneous execution with other functions, the number of processes that can be executed concurrently, and the capacity that can be processed concurrently for each function. Combinations of Functions That Are Available for Simultaneous Executions There are functions which cannot be performed concurrently when another function is being executed in the ETERNUS DX.
Page 326: Table 127 Combinations Of Functions That Can Be Executed Simultaneously (2/2)
B. Function Specification List Combinations of Functions That Are Available for Simultaneous Executions Table 127 Combinations of Functions That Can Be Executed Simultaneously (2/2) Already running process Volume Eco-mode TPV/FTV Process to be run Disk Drive Storage Conversion (motor is capacity Patrol Balancing...
Page 327: Number Of Processes That Can Be Executed Simultaneously
B. Function Specification List Available Functions for Each Software Number of Processes That Can Be Executed Simultaneously The following upper limits are applied to the number of processes that are to be executed. Only one process can be executed with Logical Device Expansion (LDE). Two or more processes cannot be •...
Page 328 B. Function Specification List Available Functions for Each Software ETERNUS SF ETERNUS SF ETERNUS SF ETERNUS Web Storage Cruiser AdvancedCopy ETERNUS SF Function ETERNUS CLI Express (Web (Web Console) Manager (Web (CLI) Console) (*1) (*1) Console) (*1) NAS interface Creation ´...
Page 329 B. Function Specification List Available Functions for Each Software ETERNUS SF ETERNUS SF ETERNUS SF ETERNUS Web Storage Cruiser AdvancedCopy ETERNUS SF Function ETERNUS CLI Express (Web (Web Console) Manager (Web (CLI) Console) (*1) (*1) Console) (*1) Backup/ Backup ´ ´...
Page 330: Snapshot Configurable Nas Volume Capacity (Guideline)
Snapshot Configurable NAS Volume Capacity (Guideline) This appendix provides the possible NAS volume capacities (guidelines) for snapshot acquisitions. The maximum copy capacity varies depending on the copy table size and resolution settings, and the number of snapshot generations. ● When a Backup Is Performed Using QuickOPC with OPC Restoration The values in the table are calculated based on the requirements when the following copy sessions are set for the NAS user volume.
Page 331: Table 129 Guidelines For Snapshot Configurable Nas Volume Capacity (When Quickopc Is Used)
C. Snapshot Configurable NAS Volume Capacity (Guideline) Table 129 Guidelines for Snapshot Configurable NAS Volume Capacity (When QuickOPC Is Used) Number Resolution ETERNUS DX snapshot ´1 ´2 ´4 ´8 ´16 ´32 ´64 generatio DX100 S5 (Copy 1,819 3,639 7,279 14,559 29,119 58,238 116,476...
Page 332: Eternus Dx Storage Systems [Rec])
C. Snapshot Configurable NAS Volume Capacity (Guideline) ● When a Secondary Backup Is Performed Using a Backup between ETERNUS DX Storage Systems (REC) The values in the table are calculated based on the requirements when the following copy sessions are set for the NAS user volume.
Page 333 C. Snapshot Configurable NAS Volume Capacity (Guideline) Number Resolution ETERNUS DX snapshot ´1 ´2 ´4 ´8 ´16 ´32 ´64 generatio DX500 S5 (Copy 3,448 6,897 13,795 27,590 55,180 110,360 220,720 table size: 1,024MB (3.4) (6.7) (13.5) (26.9) (53.9) (107.8) (215.5) [1GB]) 1,871 3,743...
Page 334 However, Fujitsu shall assume no responsibility for any operational problems as the result of errors, omissions, or the use of information in this manual. Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information •...

This manual is also suitable for:

Eternus dx100 s5 Eternus dx600 s5 Eternus dx900 s5 Eternus dx200 s5 Eternus dx500 s5 Eternus dx60 s5

Fujitsu ETERNUS DX S5 Series Design Manual

1 Overview

2 Basic Functions

3 SAN Functions

4 NAS Functions

5 Connection Configuration

Quick Links

Related Manuals for Fujitsu ETERNUS DX S5 Series

Summary of Contents for Fujitsu ETERNUS DX S5 Series