Powervault MD3200i setup on Centos 7

Setup Powervault MD3200i from scratch and restore data thats on the disks

This example shows a setup of a previously configured MD3200i Powervault (with 2 extension modules) in order to restore data thats on the physical disks

Using Centos 7 server as a management server (this is where we will install iscsi command tool, plus Dell Powervault software to configure the disk layout) and also to mount the Powervault logical volumes as actual OS disks

Part A - Powervault physical configuration

    1. Make sure your Powervault devices (MD3200i and any extension MD12xx are powered off)

    2. configure SAN controller + 2 extensions using SAN cables, in this example the SAN controllers are on the bottom box, the 2 extension modules are the 2 boxes on top of the controller,

    3. connect the SAN cables in following order,

    1. connect the 2 ethernet cables for Management ports (see image below, in red) to your switch (these will get their IPs via DHCP, or assign them static IPs based on your local network)

    2. connect 2 ethernet cables to iSCSI ports (in yellow), port 0 on both controllers

    3. in this example, all ethernet connections are going directly to my network switch (using Cisco Meraki switch, which will assign IPs to these ports via DHCP)

    1. Power on the devices in THE FOLLOWING ORDER (doing this incorrectly can wipe out your data!!!)

    2. 1 - power on the top-most MD12xxx extension module (wait 5 minutes for it to fully come up)

    3. 2 - power on the middle MD12xxx extension module (wait 5 min for it to come up)

    4. 3 - power on the MD3200i controller the last, wait 5 min to come up

    5. if no errors you will see green lights on all Powervault units blinking together in sync

    1. Part B - Centos 7 Management server configuration

      1. This example uses a Dell PowerEdge R640 physical server as a management device, the make/model of server doesnt matter, install Centos 7 and install the following utilities

      2. If using a perviously configured MD3200i, You will need to reset the Management port manually,

      3. connect a serial managment cable to the top Red port (red #1), connect this using this cable

      4. (part # Dell CT109 / MN657 For MD1000 / 3000 / 3000i Password Reset Service Cable)

                  1. yum -y install minicom setserial xorg-x11-server-Xorg xorg-x11-xauth xorg-x11-apps xorg-x11-utils iscsi-initiator-utils gtk2

      1. connect the serial cable to the Powrevault config port,

      1. connect the female DB9 connector to your server (in my case, this didnt work so I had to use a Gigabit Serial-to-USB connector, and connected the USB to my Centos7 server)

      1. once USB is connected, see what tty port the USB is connected to by running

                  1. root@qbtch3 /m/n/qbsan# dmesg | grep tty

                  2. [ 0.000000] console [tty0] enabled

                  3. [ 7.132792] 00:02: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A

                  4. [ 7.153559] 00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

                  5. [ 12.615177] usb 1-13: pl2303 converter now attached to ttyUSB0

                  6. [156573.338064] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0

        1. ttyUSB0 is the port we will use to interface with Powervault console

      1. on your Centos7 server, launch minicom (this is a console emulator to connect to devices, we will configure the IP of the Powervault MD3200i controller so we can connect to it)

        1. configure the USB port with following options

                  1. minicom -s

      1. set the Serial device to your USB tty, Bps should be 115200 8N1, hit F and G to set the Hardware and Software control to "No"

      1. hit "X", Enter, select "Save setup as dfl" to save this config

      2. select "Exit", this will now place you into a console terminal

      3. Click "Control + a" and type f (lowercase F), this will initiate connection to MD3200i, once connected, it will display,

      1. Hit Enter, type S (capital S) hit enter

      1. password: supportDell

      2. Now change the IP,

      1. in this example, this controller IP was set with 192.168.30.182 (via DHCP)

      2. To exit minicom, Control + a, x

                  1. root@qbtch3 /o/dell_iso # ls

                  2. autorun* launcher_data/ md_launcher.exe* md_launcher.sh* Readme.txt*

                  3. Autorun.inf* linux/ md_launcher_rhel_x86_64.bin* md_launcher_sles_x86_64.bin* SNMP/

                  4. COPYRIGHT/ linux_hostnameupdates.sh* md_launcher_rhel_x86.bin* md_prereq_install.sh* windows/

                  5. root@qbtch3 /o/dellMD# ./autorun

        1. make sure your Centos 7 server has SSH setup with X11 forwarding set to Yes

        2. logout of server and log back in with -X

        3. try running an X11 program to make sure you can run X11

      1. once Dell software is installed, launch the Manager

      2. Click on the Centos 7 server name and add a new storage array, select Discover, add the IP from steps above (192.168.30.182)

                  1. root@qbtch3 /# cat /etc/ssh/sshd_config | grep X11

                  2. X11Forwarding yes

                  1. ssh -X root@qbtch3

                  1. xclock

                  1. root@qbtch3 /# cd /opt/dell/mdstoragesoftware/mdstoragemanager/client/

                  2. root@qbtch3 /o/d/m/m/client# ./SMclient

      1. once it discovers an array, click Manage Array, should see array details,

      1. click on Setup tab to configure the IPs for Management and ISCSI ports,

      1. RAID controller module 0 port 0 will already be set with our 192.168.30.182 IP (based on previous steps), now configure the IP for Module 1 port 0

      1. setting Module 1 port 0 to be DHCP IP (my switch gave this port IP of 192.168.30.72)

      1. Now configure the ISCSI ports (we are using only 2 ISCSI ethernet connections (see photo at start of this article), although you can also use just 1 cable if you just want to restore the data, not use this for production)

      1. configure the IPs for the ISCSI ports (here Im using DHCP IP of 192.168.30.55)

      1. my 2 ISCSI ports are now 192.168.30.55 and 192.168.30.235

      2. add the new host name of the management server (initiator device) to access all the disk arrays (in this example, qbtch3 is the Centos 7 management server)

    1. Part D - iscsiadm

    2. on Centos 7 server run a discovery of Powervault devices using one of the 2 ISCSI IPs

    3. This will show 2 ISCSI connections, login to both using the IPs

                  1. root@qbtch3> iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.614187700038d2f80000000056431334 --portal 192.168.30.55:3260 --loginroot@qbtch3> iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.614187700038d2f80000000056431334 --portal 192.168.30.235:3260 --login

    4. Check to make sure connections are active

    5. To logout an ISCSI connection

    6. Once the sessions are showing up, you can now mount them as actual filesystem directories, check your logical volumes to see the Powervault arrays

    7. you should see LVs with "md" prefix,

                  1. root@qbtch3> iscsiadm -m discovery -t st -p 192.168.30.55

                  1. root@qbtch3> iscsiadm -m sesssion

                  2. tcp: [7] 192.168.30.235:3260,2 iqn.1984-05.com.dell:powervault.md3200i.614187700038d2f80000000056431334 (non-flash)

                  3. tcp: [8] 192.168.30.55:3260,1 iqn.1984-05.com.dell:powervault.md3200i.614187700038d2f80000000056431334 (non-flash)

                  1. iscsiadm --mode node --target iqn.1984-05.com.dell:powervault.md3200i.614187700038d2f80000000056431334 --portal 192.168.30.235:3260 --logout

                  1. root@qbtch3> lvdisplay

                  1. --- Logical volume ---

                  2. LV Path /dev/md3220i2/lv_qbsan2

                  3. LV Name lv_qbsan2

                  4. VG Name md3220i2

                  5. LV UUID ILVKoT-4HW7-c32N-WAMA-HeVb-9sIl-6Rw74d

                  6. LV Write Access read/write

                  7. LV Creation host, time atlas, 2016-10-17 09:29:49 -0400

                  8. LV Status available

                  9. # open 1

                  10. LV Size 19.95 TiB

                  11. Current LE 5230763

                  12. Segments 1

                  13. Allocation inherit

                  14. Read ahead sectors auto

                  15. - currently set to 256

                  16. Block device 253:5

    1. if LV Status is "Unavailable", run

    2. Create a mount point for the SAN and mount it,

    3. You should now see your SAN data as a local filesystem

to logout of iscsi sessions

iscsiadm -m node --logout all

                  1. vgchange -a y

                  1. mkdir /mnt/san

                  2. mount /dev/md3220i0/lv_qbsan0 /mnt/san