Solved

How to configure disks on FAS2040

Posted on 2012-03-21
9
2,257 Views
Last Modified: 2012-06-21
I have a FAS2040 and a DS4243. I created a vif on the FAS2040 for e0a and e0b and created an etherchannel port on my Cisco switch. I can access the FAS2040 through the web interface and the System Manager. I then connected to the console of the other controller and went through the setup. In System Manager. I can only see the one controller, the first one which is SATA drives. I cannot see the 24 SAS drives on the DS4243.

There is a root aggregate on the 2040 which has 3 drives and one spare, however I have 12 SATA drives in the 2040. How do I go about creating an aggregate and utilizing my SATA drives in the best way possible? Should the root aggregate be seperate and what size should it be?  I want to use RAID-DP. Would 11 drives and 1 spare be a good configuration for the SATA drives?  How do I get the SAS drives configured to where I can see them in System Manager and configure the shelf? Please provide step by step as I am new to NetApp.  Thanks
0
Comment
Question by:wayy2be
  • 5
  • 4
9 Comments
 
LVL 42

Expert Comment

by:paulsolov
Comment Utility
How many controllers do you have?

Keeep in mind that when creating an aggregate you lose 3 drives of the op (parity, dual pairty,and for OS (about 250GB for Ontap 8).  You also need one spare even though Netapp recommends two.

If you have two controllers I would move the vol0 for the second controller to the shelf, if you have one controller just create an aggregate with 11 drives withe drives on the DS 4243 shelf.

You're using FileView..Create an NOW account from now.netapp.com and download Netapp OnCommand System Manager and use it to create another aggregate.
0
 

Author Comment

by:wayy2be
Comment Utility
I have two controllers. I am using On Command System Manager. I named one controller S1 (which is the SATA drives) and the other controller is named S2 (which is the SAS drives). In On Command System Manager I have a tab for S1 but no tab for S2. Eight of the drives are owned by S1 and the rest are owned by S2, that is the way I received the unit from NetApp. All of the SAS drives are unassigned at this point. I tried to assign all of the remaining SATA drives owned by S2 to S1 to have all the SATA drives on S1. However when I try to do this via the console it tells me that S2 owns the drives and cannot be changed. How do I get over this hump?

Here is my volume status on S1:

S1> vol status -r
Aggregate aggr0 (online, raid_dp) (block checksums)
  Plex /aggr0/plex0 (online, normal, active, pool0)
    RAID group /aggr0/plex0/rg0 (normal)

      RAID Disk Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      --------- ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity   0c.00.1         0c    0   1   SA:A   0  SATA  7200 847555/1735794176 847884/1736466816
      parity    0c.00.3         0c    0   3   SA:A   0  SATA  7200 847555/1735794176 847884/1736466816
      data      0c.00.5         0c    0   5   SA:A   0  SATA  7200 847555/1735794176 847884/1736466816
      data      0c.00.9         0c    0   9   SA:A   0  SATA  7200 847555/1735794176 847884/1736466816
      data      0c.00.8         0c    0   8   SA:A   0  SATA  7200 847555/1735794176 847884/1736466816
      data      0c.00.7         0c    0   7   SA:A   0  SATA  7200 847555/1735794176 847884/1736466816


Pool1 spare disks (empty)

Pool0 spare disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block or zoned checksum traditional volumes or aggregates
spare           0c.00.10        0c    0   10  SA:A   0  SATA  7200 847555/1735794176 847884/1736466816
spare           0c.00.11        0c    0   11  SA:A   0  SATA  7200 847555/1735794176 847884/1736466816

Partner disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
partner         0c.00.2         0c    0   2   SA:A   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.0         0c    0   0   SA:A   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.4         0c    0   4   SA:A   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.6         0c    0   6   SA:A   0  SATA  7200 0/0               847884/1736466816


Volume status from S2:

S2> vol status -r
Aggregate aggr0 (online, raid_dp) (block checksums)
  Plex /aggr0/plex0 (online, normal, active, pool0)
    RAID group /aggr0/plex0/rg0 (normal)

      RAID Disk Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      --------- ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity   0c.00.0         0c    0   0   SA:B   0  SATA  7200 847555/1735794176 847884/1736466816
      parity    0c.00.2         0c    0   2   SA:B   0  SATA  7200 847555/1735794176 847884/1736466816
      data      0c.00.4         0c    0   4   SA:B   0  SATA  7200 847555/1735794176 847884/1736466816


Pool1 spare disks (empty)

Pool0 spare disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block or zoned checksum traditional volumes or aggregates
spare           0c.00.6         0c    0   6   SA:B   0  SATA  7200 847555/1735794176 847884/1736466816

Partner disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
partner         0c.00.11        0c    0   11  SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.10        0c    0   10  SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.9         0c    0   9   SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.8         0c    0   8   SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.5         0c    0   5   SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.7         0c    0   7   SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.3         0c    0   3   SA:B   0  SATA  7200 0/0               847884/1736466816
partner         0c.00.1         0c    0   1   SA:B   0  SATA  7200 0/0               847884/1736466816

I am trying to assign all the SATA drives to S1 and all the SAS drives to S2. It appears as if the root volume is on S1 in aggr0. It appears that this is the only aggregate and volume, there is none for the SAS drives.
0
 

Author Comment

by:wayy2be
Comment Utility
I wanted to add that the S1 is showing in System Manager as a HA pair, could this be why I cannot see the other controller?
0
 
LVL 42

Expert Comment

by:paulsolov
Comment Utility
Both of your controllers are there, you just can't see the other shelf.

By having both controllers on the same shelf you have already lost 3 drives since each controllers creates an aggr0.

If you create an aggregate on the SAS shelf it will lose 3 drives but if you move the vol0 for S2 onto that aggregate you will regain 3 drives (assuming you move the volumes on that aggregate as well that are being used).

please provide output for

"disk show -a"
"disk show -n"

and

"environment status all"
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 42

Expert Comment

by:paulsolov
Comment Utility
Just to be clear, each controller is a separate entity so there are 2 aggr0 on the built in drives..this should make it easier.   The controllers are stand alone units so each has an aggr0 and a vol0 which is why when you create another aggr on the shelf it will use up another 3 drives..
0
 

Author Comment

by:wayy2be
Comment Utility
Here it is:


S1> disk show -a
  DISK       OWNER                  POOL   SERIAL NUMBER
------------ -------------          -----  -------------
0c.00.5      S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.3      S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.9      S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.1      S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.4      S2       (142255951)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.7      S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.6      S2       (142255951)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.10     S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.0      S2       (142255951)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.11     S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.2      S2       (142255951)   Pool0  xxxxxxxxxxxxxxxxxxxxx
0c.00.8      S1       (142256056)   Pool0  xxxxxxxxxxxxxxxxxxxxx
NOTE: Currently 24 disks are unowned. Use 'disk show -n' for additional information.
S1>




S1> disk show -n
  DISK       OWNER                  POOL   SERIAL NUMBER
------------ -------------          -----  -------------
0d.02.4      Not Owned              NONE   xxxxxxxx
0d.02.14     Not Owned              NONE   xxxxxxxx
0d.02.23     Not Owned              NONE   xxxxxxxx
0d.02.17     Not Owned              NONE   xxxxxxxx
0d.02.10     Not Owned              NONE   xxxxxxxx
0d.02.8      Not Owned              NONE   xxxxxxxx
0d.02.2      Not Owned              NONE   xxxxxxxx
0d.02.9      Not Owned              NONE   xxxxxxxx
0d.02.1      Not Owned              NONE   xxxxxxxx
0d.02.12     Not Owned              NONE   xxxxxxxx
0d.02.15     Not Owned              NONE   xxxxxxxx
0d.02.16     Not Owned              NONE   xxxxxxxx
0d.02.11     Not Owned              NONE   xxxxxxxx
0d.02.0      Not Owned              NONE   xxxxxxxx
0d.02.6      Not Owned              NONE   xxxxxxxx
0d.02.3      Not Owned              NONE   xxxxxxxx
0d.02.20     Not Owned              NONE   xxxxxxxx
0d.02.19     Not Owned              NONE   xxxxxxxx
0d.02.7      Not Owned              NONE   xxxxxxxx
0d.02.5      Not Owned              NONE   xxxxxxxx
0d.02.18     Not Owned              NONE   xxxxxxxx
0d.02.22     Not Owned              NONE   xxxxxxxx
0d.02.13     Not Owned              NONE   xxxxxxxx
0d.02.21     Not Owned              NONE   xxxxxxxx
S1> environment status all
Voltage ok
Temperature ok
Power Supplies OutVoltage ok
Battery ok
Power Supply 1 ok
Power Supply 2 ok
        Environment for channel 0c
        Number of shelves monitored: 1  enabled: yes
        Environmental failure on shelves on this channel? no

        Channel: 0c
        Shelf: 0
        SES device path: local access: 0c.00.99
        Module type: ESAS; monitoring is active
        Shelf status: normal condition
        SES Configuration, shelf 0:
         logical identifier=0x500c0ff00dbd1a3c
         vendor identification=NETAPP
         product identification=DS12-ESAS
         product revision level=0505
        Vendor-specific information:
         Product Serial Number:
        Status reads attempted: 30870; failed: 0
        Control writes attempted: 90; failed: 0
        Shelf bays with disk devices installed:
          11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0
          with error: none
        Power Supply installed element list: 1, 2; with error: none
        Power Supply information by element:
          [1] Serial number:   Part number: <N/A>
              Type: <N/A>
              Firmware version: Y140  Swaps: 0
          [2] Serial number:   Part number: <N/A>
              Type: <N/A>
              Firmware version: Y140  Swaps: 0
        Voltage Sensor installed element list: 1, 2, 3, 4, 5, 6; with error: none
        Shelf voltages by element:
          [1] 12.90 Volts Normal voltage range
          [2] 5.110 Volts Normal voltage range
          [3] 3.580 Volts Normal voltage range
          [4] 12.100 Volts Normal voltage range
          [5] 5.130 Volts Normal voltage range
          [6] 3.570 Volts Normal voltage range
        Current Sensor installed element list: 1, 2, 3, 4; with error: none
        Shelf currents by element:
          [1] 5960 mA Normal current range
          [2] 2750 mA Normal current range
          [3] 5780 mA Normal current range
          [4] 2700 mA Normal current range
        Cooling Unit installed element list: 1, 2; with error: none
        Cooling Units by element:
          [1] 5470 RPM
          [2] 5540 RPM
        Temperature Sensor installed element list: 1, 2, 3, 4; with error: none
        Shelf temperatures by element:
          [1] 32 C (89 F)  Normal temperature range
          [2] 29 C (84 F)  Normal temperature range
          [3] 31 C (87 F)  Normal temperature range
          [4] 32 C (89 F)  Normal temperature range
        Temperature thresholds by element:
          [1] High critical: 62 C (143 F); high warning 54 C (129 F)
              Low critical:  0C (32 F); low warning 10 C (50 F)
          [2] High critical: 62 C (143 F); high warning 54 C (129 F)
              Low critical:  0C (32 F); low warning 10 C (50 F)
          [3] High critical: 62 C (143 F); high warning 55 C (131 F)
              Low critical:  0C (32 F); low warning 10 C (50 F)
          [4] High critical: 62 C (143 F); high warning 55 C (131 F)
              Low critical:  0C (32 F); low warning 10 C (50 F)
        ES Electronics installed element list: 1, 2; with error: none
        ES Electronics reporting element: 1
        SAS Expander Module installed element list: 1, 2; with error: none
        SAS Expander master module: 2

        Shelf mapping (shelf-assigned addresses) for channel 0c:
          Shelf   0:  11  10   9   8   7   6   5   4   3   2   1   0


        Environment for channel 0d
        Number of shelves monitored: 1  enabled: yes
        Environmental failure on shelves on this channel? no

        Channel: 0d
        Shelf: 2
        SES device path: local access: 0d.02.99
        Module type: IOM3; monitoring is active
        Shelf status: normal condition
        SES Configuration, shelf 2:
         logical identifier=0x50050cc10202a91a
         vendor identification=NETAPP
         product identification=DS4243
         product revision level=0132
        Vendor-specific information:
         Product Serial Number:
        Status reads attempted: 13094; failed: 0
        Control writes attempted: 39; failed: 0
        Shelf bays with disk devices installed:
          23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0
          with error: none
        Power Supply installed element list: 1, 2, 3, 4; with error: none
        Power Supply information by element:
          [1] Serial number:   Part number: 0082562-20
              Type: 9C
              Firmware version: 0311  Swaps: 0
          [2] Serial number:   Part number: 0082562-20
              Type: 9C
              Firmware version: 0311  Swaps: 0
          [3] Serial number:   Part number: 0082562-20
              Type: 9C
              Firmware version: 0311  Swaps: 0
          [4] Serial number:   Part number: 0082562-20
              Type: 9C
              Firmware version: 0311  Swaps: 0
        Voltage Sensor installed element list: 1, 2, 3, 4, 5, 6, 7, 8; with error: none
        Shelf voltages by element:
          [1] 5.70 Volts Normal voltage range
          [2] 12.140 Volts Normal voltage range
          [3] 5.110 Volts Normal voltage range
          [4] 12.220 Volts Normal voltage range
          [5] 5.70 Volts Normal voltage range
          [6] 12.140 Volts Normal voltage range
          [7] 5.110 Volts Normal voltage range
          [8] 12.140 Volts Normal voltage range
        Current Sensor installed element list: 1, 2, 3, 4, 5, 6, 7, 8; with error: none
        Shelf currents by element:
          [1] 3390 mA Normal current range
          [2] 7260 mA Normal current range
          [3] 4210 mA Normal current range
          [4] 5740 mA Normal current range
          [5] 3630 mA Normal current range
          [6] 5030 mA Normal current range
          [7] 5820 mA Normal current range
          [8] 5150 mA Normal current range
        Cooling Unit installed element list: 1, 2, 3, 4, 5, 6, 7, 8; with error: none
        Cooling Units by element:
          [1] 3670 RPM
          [2] 3000 RPM
          [3] 3370 RPM
          [4] 2920 RPM
          [5] 3450 RPM
          [6] 3000 RPM
          [7] 3750 RPM
          [8] 3070 RPM
        Temperature Sensor installed element list: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12; with error: none
        Shelf temperatures by element:
          [1] 24 C (75 F) (ambient)  Normal temperature range
          [2] 33 C (91 F)  Normal temperature range
          [3] 34 C (93 F)  Normal temperature range
          [4] 42 C (107 F)  Normal temperature range
          [5] 35 C (95 F)  Normal temperature range
          [6] 48 C (118 F)  Normal temperature range
          [7] 36 C (96 F)  Normal temperature range
          [8] 45 C (113 F)  Normal temperature range
          [9] 34 C (93 F)  Normal temperature range
          [10] 45 C (113 F)  Normal temperature range
          [11] 37 C (98 F)  Normal temperature range
          [12] 37 C (98 F)  Normal temperature range
        Temperature thresholds by element:
          [1] High critical: 42 C (107 F); high warning 40 C (104 F)
              Low critical:  0C (32 F); low warning 5 C (41 F)
          [2] High critical: 55 C (131 F); high warning 50 C (122 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [3] High critical: 55 C (131 F); high warning 50 C (122 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [4] High critical: 70 C (158 F); high warning 65 C (149 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [5] High critical: 55 C (131 F); high warning 50 C (122 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [6] High critical: 70 C (158 F); high warning 65 C (149 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [7] High critical: 55 C (131 F); high warning 50 C (122 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [8] High critical: 70 C (158 F); high warning 65 C (149 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [9] High critical: 55 C (131 F); high warning 50 C (122 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [10] High critical: 70 C (158 F); high warning 65 C (149 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [11] High critical: 60 C (140 F); high warning 55 C (131 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
          [12] High critical: 60 C (140 F); high warning 55 C (131 F)
              Low critical:  5C (41 F); low warning 10 C (50 F)
        ES Electronics installed element list: 1, 2; with error: none
        ES Electronics reporting element: 1
        ES Electronics information by element:
          [1] Serial number:   Part number: 0948580-20
              CPLD version: 14  Swaps: 0
          [2] Serial number:   Part number: 0948580-20
              CPLD version: 14  Swaps: 0
        SAS connector attached element list: 1, 3; with error: none
        SAS cable information by element:
          [1] Vendor: Molex Inc.
              Type: QSFP copper 2m  ID: 01  Swaps: 0
              Serial number:   Part number: 112-00177+A0
          [2] Vendor: <N/A> (disconnected)
              Type: <N/A> <N/A>  <N/A>  ID: <N/A>  Swaps: 0
              Serial number: <N/A>  Part number: <N/A>
          [3] Vendor: Molex Inc.
              Type: QSFP copper 2m  ID: 00  Swaps: 1
              Serial number:   Part number: 112-00177+A0
          [4] Vendor: <N/A> (disconnected)
              Type: <N/A> <N/A>  <N/A>  ID: <N/A>  Swaps: 0
              Serial number: <N/A>  Part number: <N/A>
        ACP installed element list: 1, 2; with error: none
        ACP information by element:
          [1] MAC address:
          [2] MAC address:
        SAS Expander Module installed element list: 1, 2; with error: none
        SAS Expander master module: 1

        Shelf mapping (shelf-assigned addresses) for channel 0d:
          Shelf   2:  23  22  21  20  19  18  17  16  15  14  13  12  11  10   9   8   7   6   5   4   3   2   1
0
 
LVL 42

Expert Comment

by:paulsolov
Comment Utility
So...

You see the "not owned disks"?

That is your shelf.  If you create an aggregate on it you will lose 3 drives to create it but otherwise the system sees it.

To create an aggregate you can assign the drives to a particular controller and then create the aggregate.

What do you want to do? Are you using any volumes on either controller with actual data?

If not I would recommend creating an aggegate on the shelf on S2, move vol0 to that new aggegate, and then delete the aggr assoiated with S2. This will free up 4 drives to add to aggr0 of S1 and thus give you another 2TB of usable storage on your SAS drives.

If you are not comfortable with this get a consultant to help you.
0
 

Author Comment

by:wayy2be
Comment Utility
I did manage to assign all of the SAS drives to the second controller. I also created another aggregate on the second controller. All I have to do now is to create a root volume on the new aggregate and copy the contents from the root volume on aggr0 on the second controller to aggr1 on the sencond controller. Do you know what commands I can use to accomplish this?
0
 
LVL 42

Accepted Solution

by:
paulsolov earned 500 total points
Comment Utility
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

How to fix error ""Failed to validate the vCentre certificate. Either install or verify the certificate by using the vSphere Data Protection Configuration utility" when you are trying to connect to VDP instance from Vcenter.
The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now