D-Link iSCSI IP SAN storage GbE iSCSI to SATA II / SAS RAID IP SAN storage DSN-6110 & DSN-6120 User Manual Version 1.
Preface Copyright Copyright@2011, D-Link Corporation. All rights reserved. No part of this manual may be reproduced or transmitted without written permission from D-Link corporation. Trademarks All products and trade names used in this manual are trademarks or registered trademarks of their respective companies. About this manual This manual is the introduction of D-Link DSN-61x0 IP SAN storage and it aims to help users know the operations of the disk array system easily.
Table of Contents Chapter 1 1.1 1.2 1.3 1.4 Features .........................................................................................6 1.1.1 1.2.1 1.2.2 1.2.3 Highlights .................................................................................................................7 RAID concepts ...............................................................................8 Terminology ...........................................................................................................
.5 4.6 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.5.1 4.5.2 4.5.3 4.5.4 Physical disk...........................................................................................................49 RAID group ............................................................................................................53 Virtual disk .............................................................................................................56 Snapshot ..............................................................
6.2 A. B. C. Event notifications .....................................................................117 Certification list ..........................................................................123 Microsoft iSCSI initiator..............................................................
Chapter 1 Overview 1.1 Features D-Link DSN-6000 series IP SAN storage provides non-stop service with a high degree of fault tolerance by using D-Link RAID technology and advanced array management features. DSN-6110/6120 IP SAN storage connects to the host system by iSCSI interface. It can be configured to numerous RAID level. The IP SAN storage provides reliable data protection for servers by using RAID 6. The RAID 6 allows two HDD failures without any impact on the existing data.
1.1.
1.2 RAID concepts RAID is the abbreviation of “Redundant Array of Independent Disks”. The basic idea of RAID is to combine multiple drives together to form one large logical drive. This RAID drive obtains performance, capacity and reliability than a single drive. The operating system detects the RAID drive as a single storage device. 1.2.1 Terminology The document uses the following terms: Part 1: Common RAID Redundant Array of Independent Disks.
both data cache and accessed physical disks. WB Write-Back cache-write policy. A caching technique in which the completion of a write request is signaled as soon as the data is in cache and actual writing to non-volatile media occurs at a later time. It speeds up system write performance but needs to bear the risk where data may be inconsistent between data cache and the physical disks in one short time interval. RO Set the volume to be Read-Only. DS Dedicated Spare disks.
MPIO Multi-Path Input/Output. MC/S Multiple Connections per Session MTU Maximum Transmission Unit. CHAP Challenge Handshake Authentication Protocol. An optional security mechanism to control access to an iSCSI storage system over the iSCSI data ports. iSNS Internet Storage Name Service. Part 3: Dual controller SBB 1.2.2 Storage Bridge Bay.
Striping over the member least six hard drives. Striping over the member least six hard drives. Striping over the member least eight hard drives. The abbreviation of “Just least one hard drive. RAID 30 RAID 50 RAID 60 JBOD 1.2.3 RAID 3 volumes. RAID 30 needs at RAID 5 volumes. RAID 50 needs at RAID 6 volumes. RAID 60 needs at a Bunch Of Disks”. JBOD needs at Volume relationship The below graphic describes the relationship of RAID components.
IP SANs are true SANs (Storage Area Networks) which allow several servers to attach to an infinite number of storage volumes by using iSCSI over TCP/IP networks. IP SANs can scale the storage capacity with any type and brand of storage system. In addition, it can be used by any type of network (Ethernet, Fast Ethernet, Gigabit Ethernet, and 10 Gigabit Ethernet) and combination of operating systems (Microsoft Windows, Linux, Solaris, Mac, etc.) within the SAN network.
http://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a-15d6-4585b385-befd1319f825&DisplayLang=en 2. In current Linux distributions, OS built-in iSCSI initiators are usually available. For different kernels, there are different iSCSI drivers. Please check Appendix A for iSCSI initiator certification list. If user needs the latest Linux iSCSI initiator, please visit Open-iSCSI project for most update information. Linux-iSCSI (sfnet) and Open-iSCSI projects merged in April 11, 2005.
8. Front-end 4 GbE NIC ports with high availability/load balancing/fail-over support per controller Microsoft MPIO, MC/S, Trunking, LACP, and etc. SBB Compliant 9. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.
1. 2. 3. 4. 5. 6. 7. S.E.S. inband management UPS management via dedicated serial port Fan speed monitors Redundant power supply monitors Voltage monitors Thermal sensors for both RAID controller and enclosure Status monitors for SAS JBODs 1. Management interface Management UI via serial console SSH telnet HTTP Web UI secured Web (HTTPS) Notification via Email SNMP trap Browser pop-up windows Syslog Windows Messenger iSNS support DHCP support 2. 3. 4. 1. 2. 3. 4. 5. 6.
Drive support 1. 2. 3. 4. 5. 6. 7. 8. SAS SATA II (optional, need SATA Bridge board) SCSI-3 compliant Multiple IO transaction processing Tagged command queuing Disk auto spin-down support S.M.A.R.T. for SATA II drives SAS JBODs expansion Power and Environment AC input: 100-240V ~ 7A-4A 500W with PFC (Auto Switching) DC output: 3.3V-21A; 5V-39A; 12V-30A Operating Temperature: 0 to 40 ℃ Relative Humidity: 5% to 95% non-condensing Dimensions 2U 12 bay 19 inch rackmount chassis 442.
A. B. C. D. E. Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly, the operating ambient temperature of the rack environment may be greater than room ambient. Therefore, consideration should be given to installing the equipment in an environment compatible with the maximum ambient temperature (Tma) specified by the manufacturer.
Chapter 2 Installation 2.1 Package contents The package contains the following items: 1. 2. 3. 4. 5. 6. 7. DSN-6110/6120 IP SAN storage (x1) HDD trays (x12) Power cords (x4) RS-232 cables (x2), one is for console, the other is for UPS. CD (x1) Rail kit (x1 set) Keys, screws for drives and rail kit (x1 packet) 2.2 Before installation Before starting, prepare the following items. 1. 2. 3. 4. 5. 6. A host with a Gigabit Ethernet NIC or iSCSI HBA.
The drives can be installed into any slot in the enclosure. Slot numbering will be reflected in web UI. Tips It is advisable to install at least one drive in slots 1 ~ 4. System event logs are saved to drives in these slots; If no drives are fitted the event logs will be lost in the event of a system reboot. 2.3.2 Front LED lights There are three LED lights on the left frame bar. Figure 2.3.2.1 LED lights description: Power LED: Green Power on. Off Power off.
2.3.3 Install drives Note : Skip this section if you purchased a solution populated with drives.
Figure 2.2.3.3 HDD tray description: 2.3.4 HDD power LED: Green HDD is inserted and good. Off No HDD. HDD access LED: Blue blinking HDD is accessing. Off No HDD. HDD tray handhold. Latch for tray kit removal. Rear view Figure 2.3.4.1 (DSN-6120) PSU and Fan module description: Controller 2.
Controller 1. Power supply unit (PSU2). Fan module (FAN3 / FAN4). Power supply unit (PSU1). Fan module (FAN1 / FAN2). Figure 2.3.4.2 (DSN-6110) PSU and Fan module description: Controller. Power supply unit (PSU2). Fan module (FAN3 / FAN4). Power supply unit (PSU1). Fan module (FAN1 / FAN2). Figure 2.3.4.
Connector, LED and button description: Gigabit ports (x4). LED (from left to right) Controller Health LED: Green Controller status normal or in the booting. Red Other than above status. Master Slave LED: (only for DSN-6120) Green Master controller. Off Slave controller. Dirty Cache LED: Orange Data on the cache waiting for flush to disks. Off No data on the cache.
1. 2. 3. Shutdown IP SAN storage, then power off. Remove the cover of battery backup module. Insert the battery backup module. Figure 2.4.1 4. 5. Tighten the screws up. Power on, BBM will work. Figure 2.4.
2.5 Deployment Please refer to the following topology and have all the connections ready. Figure 2.5.1 (DSN-6120) Figure 2.5.2 (DSN-6110) 1. 2. 3. Setup the hardware connection before power on servers. Connect console cable, management port cable, and iSCSI data port cables in advance. In addition, installing an iSNS server is recommended for dual controller system. Power on DSN-6110/6120 and DSN-6020 (optional) first, and then power on hosts and iSNS server.
4. Host server is suggested to logon the target twice (both controller 1 and controller 2), and then MPIO should be setup automatically. (only for DSN-6120) Tips iSNS server is recommended for dual controller system. For better data service availability, all the connections among host servers, GbE switches, and the dual controllers are recommended as redundant as below. Figure 2.5.
Chapter 3 Quick setup 3.1 Management interfaces There are three management methods to manage D-Link IP SAN storage, describe in the following: 3.1.1 Serial console Use console cable (NULL modem cable) to connect from console port of D-Link IP SAN storage to RS 232 port of management PC. Please refer to figure 2.3.1. The console settings are on the following: Baud rate: 115200, 8 data bit, no parity, 1 stop bit, and no flow control. Terminal type: VT100 Login name: admin Default password: 123456 3.1.
Figure 3.1.4.1 User name: admin Default password: 123456 After login, choose the functions which lists on the left side of window to make any configuration. Figure 3.1.4.2 There are seven indicators and three icons at the top-right corner. Figure 3.1.4.3 Indicator description: RAID light: Green RAID works well. Red RAID fails.
Temperature light: Green Temperature is normal. Red Temperature is abnormal. Voltage light: Green voltage is normal. Red voltage is abnormal. UPS light: Green UPS works well. Red UPS fails. Fan light: Green Fan works well. Red Fan fails. Power light: Green Power works well. Red Power fails. Dual controller light: Green Both controller 1 and controller 2 are present and well.
3.2 How to use the system quickly The following methods will describe the quick guide to use this IP SAN storage. 3.2.1 Quick installation Please make sure that there are some free drives installed in this system. SAS drives are recommended. Please check the hard drive details in “/ Volume configuration / Physical disk”. Figure 3.2.1.1 Step1: Click the “Quick installation” menu item; follow the steps to set up system name and date / time. Figure 3.2.1.
Step2: Confirm the management port IP address and DNS, and then click “Next”. Figure 3.2.1.3 Step 3: Set up the data port IP and click “Next”. Figure 3.2.1.4 Step 4: Set up the RAID level and volume size and click “Next”.
Figure 3.2.1.5 Step 5: Check all items, and click “Finish”. Figure 3.2.1.6 3.2.2 Volume creation wizard “Volume create wizard” has a smarter policy. When the system is inserted with some HDDs. “Volume create wizard” lists all possibilities and sizes in different RAID levels, it will use all available HDDs for RAID level depends on which user chooses.
different sizes of HDDs, e.g., 8*200G and 8*80G, it lists all possibilities and combination in different RAID level and different sizes. After user chooses RAID level, user may find that some HDDs are available (free status). The result is using smarter policy designed by DLink. It gives user: 1. 2. Biggest capacity of RAID level for user to choose and, The fewest disk number for RAID level / volume size. E.g., user chooses RAID 5 and the controller has 12*200G + 4*80G HDDs inserted.
Figure 3.2.2.2 Step 3: Decide VD size. User can enter a number less or equal to the default number. Then click “Next”. Figure 3.2.2.3 Step 4: Confirmation page. Click “Finish” if all setups are correct. Then a VD will be created. Step 5: Done. The system is available now. Figure 3.2.2.4 (Figure 3.2.2.4: A virtual disk of RAID 0 is created and is named by system itself.
Chapter 4 Configuration 4.1 Web UI management interface hierarchy The below table is the hierarchy of web GUI.
Upgrade Firmware synch ronization Reset to factory default Import and export Reboot and shu tdown Browse the firmware to upgrade Synchronize the slave controller’s firmware version with the master’s Sure to reset to factory default? Import/Export / Import file Reboot / Shutdown Quick installation Step 1 / Step 2 / Step 3 / Step 4 / Confirm Volume creation wizard Step 1 / Step 2 / Step 3 / Confirm 4.
Check “Change date and time” to set up the current date, time, and time zone before using or synchronize time from NTP (Network Time Protocol) server. Click “Confirm” in System indication to turn on the system indication LED. Click again to turn off. 4.2.2 Network setting “Network setting” is for changing IP address for remote administration usage. There are 2 options, DHCP (Get IP address from DHCP server) and static IP. The default setting is DHCP.
Figure 4.2.3.1 Check “Change admin password” or “Change user password” to change admin or user password. The maximum length of password is 12 characters. 4.2.4 Mail setting “Mail setting” can enter 3 mail addresses for receiving the event notification. Some mail servers would check “Mail-from address” and need authentication for anti-spam. Please fill the necessary fields and click “Send test mail” to test whether email functions are available.
Figure 4.2.4.1 4.2.5 Notification setting “Notification setting” can set up SNMP trap for alerting via SNMP, pop-up message via Windows messenger (not MSN), alert via syslog protocol, and event log filter for web UI.
Figure 4.2.5.1 “SNMP” allows up to 3 SNMP trap addresses. Default community setting is “public”. User can choose the event log levels and default setting enables ERROR and WARNING event log in SNMP. There are many SNMP tools. The following web sites are for your reference: SNMPc: http://www.snmpc.com/ Net-SNMP: http://net-snmp.sourceforge.net/ If necessary, click “Download” to get MIB file and import to SNMP.
Most UNIX systems build in syslog daemon. “Event log filter” setting can enable event log display on “Pop up events”. 4.3 iSCSI configuration “iSCSI configuration” is designed for setting up the “Entity Property”, “NIC”, “Node”, “Session”, and “CHAP account”. Figure 4.3.1 4.3.1 NIC “NIC” can change IP addresses of iSCSI data ports. DSN-6110/6120 has four gigabit ports on each controller to transmit data.
Figure 4.3.1.2 Default gateway: Default gateway can be changed by checking the gray button of LAN port, click “Become default gateway”. There can be only one default gateway. MTU / Jumbo frame: MTU (Maximum Transmission Unit) size can be enabled by checking the gray button of LAN port, click “Enable jumbo frame”. Maximum jumbo frame size is 3900 bytes. Caution The MTU size of switching hub and HBA on host must be enabled. Otherwise, the LAN connection can not work properly.
LACP packets to the peer. The advantages of LACP are (1) increases the bandwidth. (2) failover when link status fails on a port. Trunking / LACP setting can be changed by clicking the button “Aggregation”. Figure 4.3.1.3 (Figure 4.3.1.3: There are 4 iSCSI data ports on each controller, select at least two NICs for link aggregation.) Figure 4.3.1.4 For example, LAN1 and LAN2 are set as Trunking mode. LAN3 and LAN4 are set as LACP mode.
Figure 4.3.1.5 (Figure 4.3.1.5 shows a user can ping host from the target to make sure the data port connection is well.) 4.3.2 Entity property “Entity property” can view the entity name of the system, and setup “iSNS IP” for iSNS (Internet Storage Name Service). iSNS protocol allows automated discovery, management and configuration of iSCSI devices on a TCP/IP network. Using iSNS, it needs to install an iSNS server in SAN.
Figure 4.3.3.1 CHAP: CHAP is the abbreviation of Challenge Handshake Authentication Protocol. CHAP is a strong authentication method used in point-to-point for user login. It’s a type of authentication in which the authentication server sends the client a key to be used for encrypting the username and password. CHAP enables the username and password to transmit in an encrypted form for protection. To use CHAP authentication, please follow the procedures. 1. 2. 3.
Figure 4.3.3.3 5. Go to “/ iSCSI configuration / CHAP account” page to create CHAP account. Please refer to next section for more detail. Check the gray button of “OP.” column, click “User”. Select CHAP user(s) which will be used. It’s a multi option; it can be one or more. If choosing none, CHAP can not work. 6. 7. Figure 4.3.3.4 8. 9. Click “OK”. In “Authenticate” of “OP” page, select “None” to disable CHAP.
Rename alias: User can create an alias to one device node. 1. 2. 3. 4. 5. Check the gray button of “OP.” column next to one device node. Select “Rename alias”. Create an alias for that device node. Click “OK” to confirm. An alias appears at the end of that device node. Figure 4.3.3.6 Figure 4.3.3.7 Tips After setting CHAP, the initiator in host should be set with the same CHAP account. Otherwise, user cannot login. 4.3.
Figure 4.3.4.1 (iSCSI Session) Check the gray button of session number, click “List connection”. It can list all connection(s) of the session. Figure 4.3.4.2 (iSCSI Connection) 4.3.5 CHAP account “CHAP account” can manage a CHAP account for authentication. DSN-6110/6120 can create multiple CHAP accounts. To setup CHAP account, please follow the procedures. 1. 2. Click “Create”. Enter “User”, “Secret”, and “Confirm” secret again. “Node” can be selected here or later.
3. Click “OK”. Figure 4.3.5.2 4. Click “Delete” to delete CHAP account. 4.4 Volume configuration “Volume configuration” is designed for setting up the volume configuration which includes “Physical disk”, “RAID group”, “Virtual disk”, “Snapshot”, “Logical unit”, and “Replication” (optional). Figure 4.4.1 4.4.1 Physical disk “Physical disk” can view the status of hard drives in the system. The followings are operational steps: 1. 2.
Figure 4.4.1.1 Step 2: If there is any RG which is in protected RAID level and can be set with dedicate spare disk, select one RG, and then click “Submit”. Figure 4.4.1.2 Step 3: Done. View “Physical disk” page. Figure 4.4.1.3 (Figure 4.4.1.3: Physical disks in slot 1,2,3 are created for a RG named “RG-R5”. Slot 4 is set as dedicated spare disk of the RG named “RG-R5”. The others are free disks.) Step 4: The unit of size can be changed from (GB) to (MB).
Figure 4.4.1.4 PD column description: Slot The position of a hard drive. The button next to the number of slot shows the functions which can be executed. Size (GB) (MB) Capacity of hard drive. The unit can be displayed in GB or MB. RG Name RAID group name. Status The status of hard drive: Health Usage “Online” the hard drive is online. “Rebuilding” the hard drive is being rebuilt.
RAID group. “Free disk” This hard drive is free for use. “Dedicated spare” This hard drive has been set as dedicated spare of a RG. “Global spare” This hard drive has been set as global spare of all RGs. Vendor Hard drive vendor. Serial Hard drive serial number. Type Hard drive type: “SATA” SATA disk. “SATA2” SATA II disk. “SAS” SAS disk. Write cache Hard drive write cache is enabled or disabled. Default is “Enabled”. Standby HDD auto spindown to save power.
4.4.2 the indication LED off. More information Show hard drive detail information. RAID group “RAID group” can view the status of each RAID group, create, and modify RAID groups. The following is an example to create a RG. Step 1: Click “Create”, enter “Name”, choose “RAID level”, click “Select PD” to select PD, assign the RG’s “Preferred owner”. Then click “OK”. The “Write Cache” option is to enable or disable the write cache option of hard drives.
Figure 4.4.2.2 (Figure 4.4.2.2: There is a RAID 0 with 4 physical disks, named “RG-R0”. The second RAID group is a RAID 5 with 3 physical disks, named “RG-R5”.) Step 3: Done. View “RAID group” page. RG column description: The button includes the functions which can be executed. Name RAID group name. Total (GB) (MB) Total capacity of this RAID group. The unit can be displayed in GB or MB. Free (GB) (MB) Free capacity of this RAID group. The unit can be displayed in GB or MB.
“Failed” the RAID group fails. “Degraded” the RAID group is not healthy and not completed. The reason could be lack of disk(s) or have failed disk RAID The RAID level of the RAID group. Current owner The owner of the RAID group. The default owner is controller 1. Preferred owner The preferred owner of the RAID group. The default owner is controller 1. RG operation description: Create Create a RAID group. Migrate Change the RAID level of a RAID group.
Command queuing: “Enabled” Enable disk command queue. (Default) “Disabled” Disable disk command queue. More information 4.4.3 Show RAID group detail information. Virtual disk “Virtual disk” can view the status of each Virtual disk, create, and modify virtual disks. The following is an example to create a VD.
Step 2: Confirm page. Click “OK” if all setups are correct. Figure 4.4.3.2 (Figure 4.4.3.2: Create a VD named “VD-01”, from “RG-R0”.) Step 3: Done. View “Virtual disk” page. VD column description: The button includes the functions which can be executed. Name Virtual disk name. Size (GB) (MB) Total capacity of the virtual disk. The unit can be displayed in GB or MB. Write The right of virtual disk: Priority Bg rate “WT” Write Through. “WB” Write Back. “RO” Read Only.
number the background priority of a VD is, the more background I/O will be scheduled to execute. Status Type The status of virtual disk: “Online” The virtual disk is online. “Offline” The virtual disk is offline. “Initiating” The virtual disk is being initialized. “Rebuild” The virtual disk is being rebuilt. “Migrate” The virtual disk is being migrated. “Rollback” The virtual disk is being rolled back. “Parity checking” The virtual disk is being parity check.
The unit can be displayed in GB or MB. #Snapshot Number of snapshot(s) that have been taken. RG name The RG name of the virtual disk VD operation description: Create Create a virtual disk. Extend Extend the virtual disk capacity. Parity check Execute parity check for the virtual disk. It supports RAID 3 / 5 / 6 / 30 / 50 / 60. Regenerate parity: “Yes” Regenerate RAID parity and write. “No” Execute parity check only and find mismatches.
editing. “Disabled” Disable AV-media mode. (Default) Type: “RAID” the virtual disk is normal. (Default) “Backup” the virtual disk is for clone usage. Attach LUN Attach to a LUN. Detach LUN Detach to a LUN. List LUN List attached LUN(s). Set clone Set the target virtual disk for clone. Clear clone Clear clone function. Start clone Start clone function. Stop clone Stop clone function. Schedule clone Set clone function by schedule.
4.4.4 Snapshot “Snapshot” can view the status of snapshot, create, and modify snapshots. Please refer to next chapter for more detail about snapshot concept. The following is an example to take a snapshot. Step 1: Create snapshot space. In “/ Volume configuration / Virtual disk”, Check to the gray button next to the VD number; click “Set snapshot space”. Step 2: Set snapshot space. Then click “OK”. The snapshot space is created. Figure 4.4.4.1 Figure 4.4.4.2 (Figure 4.4.4.
Figure 4.4.4.4 Figure 4.4.4.5 (Figure 4.4.4.5: This is the snapshot list of “VD-01”. There are two snapshots. Snapshot VD “SnapVD-01” is exposed as read-only, “SnapVD-02” is exposed as read-write.) Step 5: Attach a LUN to a snapshot VD. Please refer to the next section for attaching a LUN. Step 6: Done. Snapshot VD can be used. Snapshot column description: The button includes the functions which can be executed. Name Snapshot VD name. Used (GB) (MB) The amount of snapshot space that has been used.
4.4.5 “Good” The snapshot is good. “Failed” The snapshot fails. Exposure Snapshot VD is exposed or not. Right The right of snapshot: “Read-write” The snapshot VD can be read / write. “Read-only” The snapshot VD is read only. #LUN Number of LUN(s) that snapshot VD is attached. Created time Snapshot VD created time. Snapshot operation description: Expose/ Unexpose Expose / unexpose the snapshot VD. Rollback Rollback the snapshot VD. Delete Delete the snapshot VD.
Figure 4.4.5.1 Figure 4.4.5.2 LUN operation description: Attach Attach a logical unit number to a virtual disk. Detach Detach a logical unit number from a virtual disk. The matching rules of access control are followed from the LUN’ created time; the earlier created LUN is prior to the matching rules. For example: there are 2 LUN rules for the same VD, one is “*”, LUN 0; and the other is “iqn.host1”, LUN 1. The host “iqn.host2” can login successfully because it matches the rule 1.
4.4.6 Example The following is an example to create volumes. This example is to create two VDs and set a global spare disk. Example This example is to create two VDs in one RG, each VD shares the cache volume. The cache volume is created after system boots up automatically. Then set a global spare disk. Last, delete all of them. Step 1: Create a RG (RAID group). To create a RAID group, please follow the procedures: Figure 4.4.6.1 1. 2. 3. 4. 5. Select “/ Volume configuration / RAID group”.
Step 2: Create VD (Virtual Disk). To create a data user volume, please follow the procedures. Figure 4.4.6.3 1. 2. 3. 4. 5. Select “/ Volume configuration / Virtual disk”. Click “Create”. Input a VD name, choose a RG Name and enter a size for this VD; decide the stripe height, block size, read / write mode, bg rate, and set priority, finally click “OK”. Done. A VD has been created. Follow the above steps to create another VD. Figure 4.4.6.4 (Figure 4.4.6.
2. In “/ Volume configuration / Logical unit”, click “Attach”. The procedures are as follows: Figure 4.4.6.5 1. 2. 3. Select a VD. Input “Host” IQN, which is an iSCSI node name for access control, or fill-in wildcard “*”, which means every host can access to this volume. Choose LUN and permission, and then click “OK”. Done. Figure 4.4.6.6 Tips The matching rules of access control are from the LUNs’ created time, the earlier created LUN is prior to the matching rules. Step 4: Set a global spare disk.
Figure 4.4.6.7 (Figure 4.4.6.7: Slot 4 is set as a global spare disk.) Step 5: Done. Delete VDs, RG, please follow the below steps. Step 6: Detach a LUN from the VD. In “/ Volume configuration / Logical unit”, Figure 4.4.6.8 1. 2. 3. Check the gray button next to the LUN; click “Detach”. There will pop up a confirmation page. Choose “OK”. Done. Step 7: Delete a VD (Virtual Disk). To delete the virtual disk, please follow the procedures: 1. 2. 3. Select “/ Volume configuration / Virtual disk”.
Step 8: Delete a RG (RAID group). To delete a RAID group, please follow the procedures: 1. 2. 3. 4. 5. Select “/ Volume configuration / RAID group”. Select a RG which all its VD are deleted, otherwise the this RG cannot be deleted. Check the gray button next to the RG number click “Delete”. There will pop up a confirmation page, click “OK”. Done. The RG has been deleted. Tips The action of deleting one RG will succeed only when all of the related VD(s) are deleted in this RG.
4.5.1 Hardware monitor “Hardware monitor” can view the information of current voltages and temperatures.
Figure 4.5.1.1 If “Auto shutdown” is checked, the system will shutdown automatically when voltage or temperature is out of the normal range. For better data protection, please check “Auto Shutdown”. For better protection and avoiding single short period of high temperature triggering auto shutdown, the system use multiple condition judgments to trigger auto shutdown, below are the details of when the Auto shutdown will be triggered. 1. 2. 3.
First, connect the system and APC UPS via RS-232 for communication. Then set up the shutdown values (shutdown battery level %) when power is failed. UPS in other companies can work well, but they have no such communication feature with the system. Figure 4.5.2.2 (Figure 4.5.2.2: With Smart-UPS.) UPS column description: UPS Type Select UPS Type. Choose Smart-UPS for APC, None for other vendors or no UPS. Shutdown Battery Level (%) When below the setting level, system will shutdown.
Battery Level (%) 4.5.3 “UPS shutdown in progress” “Batteries failed. Please change them NOW!” Current power percentage of battery level. SES SES represents SCSI Enclosure Services, one of the enclosure management standards. “SES configuration” can enable or disable the management of SES. Figure 4.5.3.1 (Figure 4.5.1.1: Enable SES in LUN 0, and can be accessed from every host) The SES client software is available at the following web site: SANtools: http://www.santools.com/ 4.5.
S.M.A.R.T. only supports SATA drives. SAS drives do not have this function now. It will show N/A in the web page for SAS drives. Figure 4.5.4.1 (SAS drives & SATA drives) 4.
4.6.2 Status description: Normal Dual controllers are in normal stage. Degraded One controller fails or has been plugged out. Lockdown The firmware of two controllers is different or the size of memory of two controllers is different. Single Single controller mode. Event log “Event log” can view the event messages. Check the checkbox of INFO, WARNING, and ERROR to choose the level of event log display.
Figure 4.6.2.1 The event log is displayed in reverse order which means the latest event log is on the first / top page. The event logs are actually saved in the first four hard drives; each hard drive has one copy of event log. For one system, there are four copies of event logs to make sure users can check event log any time when there are failed disks. Tips Please plug-in any of the first four hard drives, then event logs can be saved and displayed in next system boot up.
4.6.3 Upgrade “Upgrade” can upgrade firmware. Please prepare new firmware file named “xxxx.bin” in local hard drive, then click “Browse” to select the file. Click “Confirm”, it will pop up a message “Upgrade system now? If you want to downgrade to the previous FW later (not recommend), please export your system configuration in advance”, click “Cancel” to export system configuration in advance, then click “OK” to start to upgrade firmware. Figure 4.6.3.1 Figure 4.6.3.
4.6.5 Reset to factory default “Reset to factory default” allows user to reset IP SAN storage to factory default setting. Figure 4.6.5.1 Reset to default value, the password is: 1234, and IP address to default 192.168.0.32 4.6.6 Import and export “Import and export” allows user to save system configuration values: export, and apply all configuration: import.
4.6.7 Reboot and shutdown “Reboot and shutdown” can “Reboot” and “Shutdown” the system. Before power off, it’s better to execute “Shutdown” to flush the data from cache to physical disks. The step is necessary for data protection. Figure 4.6.7.1 4.7 Home/Logout/Mute In the right-upper corner of web UI, there are 3 individual icons, “Home”, “Logout”, and “Mute”. Figure 4.7.1 4.7.1 Home Click “Home” to return to home page. 4.7.2 Logout For security reason, please use “Logout” to exit the web UI.
Chapter 5 Advanced operations 5.1 Volume rebuild If one physical disk of the RG which is set as protected RAID level (e.g.: RAID 3, RAID 5, or RAID 6) is FAILED or has been unplugged / removed, then the status of RG is changed to degraded mode, the system will search/detect spare disk to rebuild the degraded RG to a complete one. It will detect dedicated spare disk as rebuild disk first, then global spare disk. D-LINK IP SAN storage supports Auto-Rebuild. Take RAID 6 for example: 1.
Rebuild operation description: RAID 0 Disk striping. No protection for data. RG fails if any hard drive fails or unplugs. RAID 1 Disk mirroring over 2 disks. RAID 1 allows one hard drive fails or unplugging. Need one new hard drive to insert to the system and rebuild to be completed. N-way mirror Extension to RAID 1 level. It has N copies of the disk. N-way mirror allows N-1 hard drives failure or unplugging. RAID 3 Striping with parity on the dedicated disk.
5.2 RG migration To migrate the RAID level, please follow below procedures. 1. 2. 3. Select “/ Volume configuration / RAID group”. Check the gray button next to the RG number; click “Migrate”. Change the RAID level by clicking the down arrow to “RAID 5”. There will be a pupup which indicates that HDD is not enough to support the new setting of RAID level, click “Select PD” to increase hard drives, then click “OK“ to go back to setup page.
To do migration, the total size of RG must be larger or equal to the original RG. It does not allow expanding the same RAID level with the same hard disks of original RG. The below operations are not allowed when a RG is being migrated. System would reject these operations: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Add dedicated spare. Remove a dedicated spare. Create a new VD. Delete a VD. Extend a VD. Scrub a VD. Perform another migration operation. Scrub entire RG. Take a snapshot. Delete a snapshot.
Figure 5.3.2 Tips The size of VD extension must be larger than original. Caution VD Extension cannot be executed during rebuilding or migration. 5.4 Snapshot Snapshot-on-the-box captures the instant state of data in the target volume in a logical sense. The underlying logic is Copy-on-Write -- moving out the data which would be written to certain location where a write action occurs since the time of data capture.
5.4.1 Create snapshot volume To take a snapshot of the data, please follow the procedures. 1. 2. 3. 4. 5. 6. Select “/ Volume configuration / Virtual disk”. Check the gray button next to the VD number; click “Set snapshot space”. Set up the size for snapshot. The minimum size is suggested to be 20% of VD size, and then click “OK”. It will go back to the VD page and the size will show in snapshot column.
1. 2. There are two methods to clean all snapshots. In “/ Volume configuration / Virtual disk”, check the gray button next to the VD number; click “Cleanup snapshot”. Or in “/ Volume configuration / Snapshot”, click “Cleanup”. “Cleanup snapshot” will delete all snapshots of the VD and release snapshot space. 5.4.2 Auto snapshot The snapshot copies can be taken manually or by schedule such as hourly or daily. Please follow the procedures. 1. 2. 3. There are two methods to set auto snapshot.
5.4.3 Rollback The data in snapshot VD can rollback to original VD. Please follow the procedures. 1. 2. Select “/ Volume configuration / Snapshot”. Check the gray button next to the Snap VD number which user wants to rollback the data; click “Rollback”. Done, the data in snapshot VD is rollback to original VD. 3. Caution Before executing rollback, it is better to dismount file system for flushing data from cache to disks in OS first. System sends pop-up message when user executes rollback function. 5.
Figure 5.4.4.1 On Linux and UNIX platform, a command named sync can be used to make the operating system flush data from write caching into disk. For Windows platform, Microsoft also provides a tool – sync, which can do exactly the same thing as the sync command in Linux/UNIX. It will tell the OS to flush the data on demand. For more detail about sync tool, please refer to: http://technet.microsoft.com/en-us/sysinternals/bb897438.
For example, there are two or more snapshots existed on a VD and the latest snapshot keeps growing. When it comes to the moment that the snapshot space is run out, the system will try to remove the oldest snapshot to release more space for the latest snapshot usage. As the latest snapshot is growing, the system keeps removing the old snapshots.
5.6 VD clone The user can use VD clone function to backup data from source VD to target VD, set up backup schedule, and deploy the clone rules. The procedures of VD clone are on the following: 1. Copy all data from source VD to target VD at the beginning (full copy). 2. Use Snapshot technology to perform the incremental copy afterwards. Please be fully aware that the incremental copy needs to use snapshot to compare the data difference. Therefore, the enough snapshot space for VD clone is very important.
3. Here are the objects, a Source VD and a Target VD. Before starting clone process, it needs to deploy the VD Clone rule first. Click “Configuration”. Figure 5.6.3 4. There are three clone configurations, describe on the following. Figure 5.6.4 Snapshot space: Figure 5.6.4 This setting is the ratio of source VD and snapshot space. The default ratio is 2 to 1.
Figure 5.6.5 The threshold setting will monitor the usage amount of snapshot space. When the used snapshot space achieves its threshold, system will automatically take a clone snapshot and start VD clone process. The purpose of threshold could prevent the incremental copy fail immediately when running out of snapshot space. For example, the default threshold is 50%. The system will check the snapshot space every hour.
Figure 5.6.7 6. Select the target VD. Then click “Confirm”. Figure 5.6.8 7. Now, the clone target “TargetVD_R6” has been set. Figure 5.6.9 8. Click “Start clone”, the clone process will start.
Figure 5.6.10 9. The default setting will create a snapshot space automatically which the capacity is double size of the VD space. Before starting clone, system will initiate the snapshot space. Figure 5.6.11 10. After initiating the snapshot space, it will start cloning. Figure 5.6.12 11. Click “Schedule clone” to set up the clone by schedule.
Figure 5.6.13 12. There are “Set Clone schedule” and “Clear Clone schedule” in this page. Please remember that “Threshold” and “Restart the task an hour later if failed” options in VD configuration will take effect after clone schedule has been set. Figure 5.6.14 Run out of snapshot space while VD clone While the clone is processing, the increment data of this VD is over the snapshot space. The clone will complete, but the clone snapshot will fail.
the clone process. Each time the clone snapshot failed, it means that the system loses the reference value of incremental data. So it will start a full copy at next clone process. When running out of snapshot space, the flow diagram of VD clone procedure will be like the following. Figure 5.6.
5.7 SAS JBOD expansion 5.7.1 Connecting JBOD D-LINK DSN-6000 series support up to 4 additional SAS/SATA JBODs for capacity expansion. When connecting to a dual-controller JBOD, it will display in “Show PD for:” of “/ Volume configuration / Physical disk”. For example, Local, JBOD 1 (DSN6020), JBOD 2 (DSN6020), …etc. Local means disks in local controller, and so on. The hard drives in JBOD can be used as local disks. “/ Enclosure management / Hardware monitor” can display the hardware status of SAS JBODs.
Figure 5.7.2.1 2 3 4 Choose a JBOD which wants to upgrade. Please prepare new firmware file in local hard drive, then click “Browse” to select the file. Click “Confirm”. After finished upgrading, the system must reboot manually to make the new firmware took effect. 5.8 MPIO and MC/S These features come from iSCSI initiator. They can be setup from iSCSI initiator to establish redundant paths for sending I/O from the initiator to the target. 1.
2. MC/S: MC/S (Multiple Connections per Session) is a feature of iSCSI protocol, which allows combining several connections inside a single session for performance and failover purposes. In this way, I/O can be sent on any TCP/IP connection to the target. If one connection fails, another connection can continue processing I/O without interruption to the application. Figure 5.8.2 Difference: MC/S is implemented on iSCSI level, while MPIO is implemented on the higher level.
3. 4. If user installs anyone of Windows XP, Windows Vista or Windows 7, MC/S is the only option since Microsoft MPIO is supported Windows Server editions only. MC/S can provide higher throughput than MPIO in Windows system, but it consumes more CPU resources than MPIO. 5.9 Trunking and LACP Link aggregation is the technique of taking several distinct Ethernet links to let them appear as a single link. It has a larger bandwidth and provides the fault tolerance ability.
A. B. C. This is a simple SAN environment. There is only one switch to connect the server and storage. And there is no extra server to be added in the future. There is no idea of using LACP or Trunking, uses Trunking first. There is a request of monitoring the traffic on a trunk in switch. Figure 5.9.2 Caution Before using trunking or LACP, the gigabit switch must support trunking or LACP and enabled. Otherwise, host can not connect the link with storage device. 5.
Figure 5.10.1.1 5.10.2 Ownership When creating RG, it will be assigned with a prefered owner, the default owner is controller 1. To change the RG ownership, please follow the procedures. 1 2 3 Select “/ Volume configuration / RAID group”. Check the gray button next to the RG name; click “Set preferred owner”. The ownership of the RG will be switched to the other controller. Figure 5.10.2.
Figure 5.10.2.2 (Figure 5.10.2.2: The RG ownership is changed to the other controller.) 5.10.3 Controller status There are four statuses described on the following. It can be found in “/ System maintenance / System information”. 1. Normal: Dual controller mode. Both of controllers are functional. 2. Degraded: Dual controller mode. When one controller fails or has been plugged out, the system will turn to degraded.
5.11 Replication Replication function will help users to replicate data easily through LAN or WAN from one IP SAN storage to another. The procedures of Replication are on the following: 1. Copy all data from source VD to target VD at the beginning (full copy). 2. Use Snapshot technology to perform the incremental copy afterwards. Please be fully aware that the incremental copy needs to use snapshot to compare the data difference. Therefore, the enough snapshot space for VD clone is very important.
Figure 5.11.2 3. If you want the replication port to be on special VLAN section, you may assign VLAN ID to the replication port. The setting will automatically duplicate to the other controller. Create backup VD on the target IP SAN storage 1. Before creating the replication job on the source IP SAN storage, user has to create a virtual disk on the target IP SAN storage and set the type of the VD as “Backup”. Figure 5.11.4 2.
Figure 5.11.5 Create replication job on the source IP SAN storage 1. Click “Create” to create a new replication job. Figure 5.11.6 2. Select the source VD which will be replicated to the target IP SAN storage and click “Next”. Figure 5.11.
Tips If the message displays that there is not enough space for creation, please refer to the section of Configure the snapshot space below for solution. 3. Enter the IP address of iSCSI port on controller 1 of the target IP SAN storage. Click “Next” to continue. Figure 5.11.8 4. The Replication uses standard iSCSI protocol for data replication. User has to log on the iSCSI node to create the iSCSI connection for the data transmission.
5. Choose the backup VD and click “Next”. Figure 5.11.10 6. A new replication job is created and listed on the Replication page. Figure 5.11.11 Run the replication job 1. Click the “OP” button on the replication job to open operation menu. Click “Start” to run the replication job. Figure 5.11.12 2. Click “Start” again to confirm the execution of the replication job.
Figure 5.11.13 3. User can monitor the replication job from the “Status” information and the progress is expressed by percentage. Figure 5.11.14 Create multi-path on the replication job 1. Click the “Create multi-path” in the operation menu of the replication job. Figure 5.11.15 2. Enter the IP of iSCSI port on controller 2 of the target IP SAN storage.
Figure 5.11.16 3. Select the iSCSI node to log on and click “Next”. Figure 5.11.17 4. Choose the same target VD and click “Next”.
Figure 5.11.18 5. A new target will be added in this replication job as a redundancy path. Figure 5.11.19 Configure the replication job to run by schedule 1. Click “Schedule” in the operation menu of the replication job. Figure 5.11.
2. The replication job can be scheduled to run by day, by week or by month. The execution time can be configurable per user’s need. Figure 5.11.21 Configure the snapshot space The Replication uses Snapshot technique of D-LINK, to help user to replicate the data without stop accessing to the source VD. If the snapshot space is not configured on the source VD in advance, the IP SAN storage will allocate snapshot space for the source VD automatically when the replication job is created.
There are three settings in the Replication configuration menu, The Snapshot space specifies the ratio of snapshot space allocated to the source VD automatically when the snapshot space is not configured in advance. The default ratio is 2 to 1. It means when the replication job is creating, the IP SAN storage will automatically use the free space of RG to create a snapshot space which size is double of the source VD. The Threshold setting will monitor the utilization of snapshot space.
5.12 VLAN VLAN (Virtual Local Area Network) is a logical grouping mechanism implemented on switch device using software rather than a hardware solution. VLANs are collections of switching ports that comprise a single broadcast domain. It allows network traffic to flow more efficiently within these logical subgroups. Please consult your network switch user manual for VLAN setting instructions. Most of the work is done at the switch part.
4. VLAN ID 66 for LAN2 is set properly. Figure 5.12.3 Assign VLAN ID to LAG(Trunking or LACP) 1. After creating LAG, press “OP” button next to the LAG, and select “Set VLAN ID”. Figure 5.12.4 2. Put in the VLAN ID and click ok. VLAN ID of LAG 0 is properly set. Figure 5.12.
3. If iSCSI ports are assigned with VLAN ID before creating aggregation takes place, aggregation will remove VLAN ID. You need to repeat step 1 and step 2 to set VLAN ID for the aggregation group. Assign VLAN ID to replication port Please consult figure 5.11.3 of 5.11 Replication section for details. Always make sure correct VLAN IDs are assigned to the correct network ports (iSCSI, switch, and host NIC) to ensure valid connections.
Chapter 6 Troubleshooting 6.1 System buzzer The system buzzer features are listed below: 1. 2. The system buzzer alarms 1 second when system boots up successfully. The system buzzer alarms continuously when there is error occurred. The alarm will be stopped after error resolved or be muted. The alarm will be muted automatically when the error is resolved. E.g., when RAID 5 is degraded and alarm rings immediately, user changes / adds one physical disk for rebuilding.
ERROR ERROR ERROR ERROR ERROR ERROR ERROR INFO INFO INFO INFO SATA PRD mem fail SATA revision id fail SATA set reg fail SATA init fail SATA diag fail Mode ID fail SATA chip count error SAS port reply error SAS unknown port reply error FC port reply error FC unknown port reply error Failed to init SATA PRD memory manager Failed to get SATA revision id Failed to set SATA register Core failed to initialize the SATA adapter SATA Adapter diagnostics failed SATA Mode ID failed SATA Chip count error SAS HBA p
RMS events Level Type INFO Console Login INFO Console Logout INFO INFO INFO WARNING Web Login Web Logout Log clear Send mail fail WARNING WARNING Type WARNING Snap mem Snap space overflow Snap threshold INFO INFO Snap delete Snap auto delete INFO INFO INFO Snap take Snap set space Snap rollback started Snap rollback finished Snap quota reached Snap clear space INFO WARNING INFO Description Failed to allocate snapshot memory for VD .
INFO INFO WARNING INFO INFO INFO BBM status good BBM status charging BBM status fail BBM enabled BBM inserted BBM removed Battery backup module is good Battery backup module is charging Battery Battery Battery Battery backup backup backup backup module is failed feature is .
INFO WARNING Volt recovery Therm warn OT WARNING Therm warn UT WARNING Therm fail OT WARNING Therm fail UT INFO Therm recovery System maintenance events Level INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO WARNING ERROR INFO Voltage of in JBOD is NORMAL Temperature of read as in JBOD is OT WARNING Temperature of read as in JBOD is UT WARNING Temperature of read as in JBOD is OT FAILURE Tempe
ERROR ERROR ERROR ERROR ERROR ERROR INFO CTR memory NG CTR firmware NG CTR lowspeed NG CTR highspeed NG CTR backend NG CTR frontend NG CTR reboot FW sync Memory size mismatch Firmware version mismatch Low speed inter link is down High speed inter link is down SAS expander is down FC IO controller is down Controller reboot, reason [Firmware synchronization completed] Clone events Level Type INFO INFO WARNING INFO INFO INFO WARNING WARNING VD clone started VD clone finished VD clone failed VD clon
Appendix A. Certification list iSCSI Initiator (Software) OS Microsoft Windows Linux Software/Release Number Microsoft iSCSI Software Initiator Release v2.08 System Requirements: 1. Windows 2000 Server with SP4 2. Windows Server 2003 with SP2 3. Windows Server 2008 with SP2 The iSCSI Initiators are different for different Linux Kernels. 1. 2. For Red Hat Enterprise Linux 3 (Kernel 2.4), install linux-iscsi-3.6.3.tar For Red Hat Enterprise Linux 4 (Kernel 2.
Dell Dell HP Netgear ZyXEL PowerConnect 2724 PowerConnect 2708 ProCurve 1800-24G GS724T GS2200 Hard drive SAS drives are recommanded on dual controller system. For SATA drives, SATA bridge boards are required in dual controller configuraiton. SAS 3.5” Vendor Hitachi Hitachi Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Model Ultrastar 15K147, HUS151436VLS300, 36GB, 15000RPM, SAS 3.0Gb/s, 16M Ultrastar 15K300, HUS153073VLS300, 73GB, 15000RPM, SAS 3.
Hitachi Hitachi Maxtor Maxtor Samsung Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Seagate Westem Westem Westem Westem Westem Westem Westem Westem Digital Digital Digital Digital Digital Digital Digital Digital Westem Digital Westem Digital Westem Digital Westem Digital Westem Digital Westem Digital Westem Digital K2A0AD1A) Deskstar E7K1000, HDE721010SLA330, 1TB, 7200RPM, SATA 3.
B. Microsoft iSCSI initiator Here is the step by step to setup Microsoft iSCSI Initiator. Please visit Microsoft website for latest iSCSI initiator. This example is based on Microsoft Windows Server 2008 R2. 1. 2. Connect Run Microsoft iSCSI Initiator. Input IP address or DNS name of the target. And then click “Quick Connect”. Figure B.1 3. Click “Done”.
Figure B.2 4. It can connect to an iSCSI disk now. 5. 6. 7. Figure B.3 MPIO If running MPIO, please continue. Click “Discovery” tab to connect the second path. Click “Discover Portal”. Input IP address or DNS name of the target.
8. Figure B.4 Figure B.5 Figure B.6 Figure B.7 Click “OK”.
9. Click “Targets” tab, select the second path, and then click “Connect”. 10. Enable “Enable multi-path” checkbox. Then click “OK”. 11. Done, it can connect to an iSCSI disk with MPIO. MC/S 12. If running MC/S, please continue. 13. Select one target name, click “Properties…”. 14. Click “MCS…” to add additional connections. Figure B.8 Figure B.9 15. Click “Add…”. 16. Click “Advanced…”.
Figure B.10 Figure B.11 17. Select Initiator IP and Target portal IP, and then click “OK”. 18. Click “Connect”. 19. Click “OK”. Figure B.12 Figure B.13 20. Done.
Disconnect 21. Select the target name, click “Disconnect”, and then click “Yes”. Figure B.14 22. Done, the iSCSI device disconnect successfully.
C. From single controller to dual controllers This SOP applies to upgrading from DSN-6110 to DSN6120 as well as from DSN-6410 to DSN-6420. Before you do this, please make sure that either DSN-6110 or DSN-6410 is properly installed according to the manuals, especially the HDD trays. If you are NOT using SAS hard drives, you need to use HDD trays with either multiplexer board or bridge board to install your HDDs in order to utilize the dual controller mode features.
Please follow the steps below to upgrade to dual controller mode. Step 1 Go to “Maintenance\System”. Copy the IP SAN storage serial number. Step 2 Go to “Maintenance\Upgrade” and paste the serial number into “Controller Mode” section. Select “Dual” as operation mode.
Step 3 Click “confirm”. The system will ask you to shutdown. Please shutdown IP SAN storage. Click Ok.
Go to “Maintenance\Reboot and shutdown”. Click “Shutdown” to shutdown the system. Click Ok. Step 4 Power off DNS-6110 or DSN-6410. Insert the second controller to the IP SAN storage. And then power on the system. The IP SAN storage should now become in dual controller mode as either DSN-6120 or DSN-6420. You may go to “Maintenance\System information” to check out. The IP SAN storage is running in dual controller mode now.
