HPE 3PAR StoreServ Storage
1752790 Members
5700 Online
108789 Solutions
New Discussion

3PAR 8200 new disk enclosure installation disk allocation

 
shang83
Occasional Advisor

3PAR 8200 new disk enclosure installation disk allocation

I have 3par 8200 comes with 1 controller and 2 disk enclosure. It have 6 X 400GB SSD and 48 X 1.8TB FC drives

My management want to add 2 more enclosure with

1 enclosure 6 X 400GB SSD and 10 X 1.8TB FC drives

1 enclosure 8 X 800 SSD and 12 X 1.8TB FC drives.

With the two new enclosure disks installed, is the disk allocation and loading meet the best practices?

The current 3PAR setup is attached. 

1 REPLY 1
Sheldon Smith
HPE Pro

Re: 3PAR 8200 new disk enclosure installation disk allocation

You have three cages now and will be going to five:
Distribute the SSDs across the cages in pairs as evenly as possible.
Then add the FC disks (again in pairs) in the two new cages again as evenly as possible:

2 x 400GB SSD, 16 x 1800GB FC
2 x 400GB SSD, 16 x 1800GB FC
2 x 400GB SSD, 16 x 1800GB FC
4 x 400GB SSD, 12 x 1800GB FC, 4 x 800GB SSD
2 x 400GB SSD, 10 x 1800GB FC, 6 x 800GB SSD
It should be OK, although with more SSDs on the two new cages, there will be a higher IO rate to those two cages.

Alternatively, work with 3PAR Support to move 3 pairs of the 1800GB FC from cages 0 and 1 to cages 3 and 4 so you wind up with
2 x 400GB SSD, 14 x 1800GB FC
on each cage. Then add the remaining SSDs in pairs evenly; each cage should wind up with 18 physical disks:
4 x 400GB SSD, 14 x 1800GB FC, 2 x 800GB SSD
2 x 400GB SSD, 14 x 1800GB FC, 2 x 800GB SSD
2 x 400GB SSD, 14 x 1800GB FC, 2 x 800GB SSD
2 x 400GB SSD, 14 x 1800GB FC, 2 x 800GB SSD
2 x 400GB SSD, 14 x 1800GB FC

Finally, I would recommend using pattern filters on all of the SSD CPGs so the 400GB drives are separate from the 800GB SSDs:
-p -tc_lt <number>
-p -tc_gt <number>
where <number> is midway between the total number of chunklets of the smaller and larger SSDs (say, 600).


Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company

Accept or Kudo