#Clean ADP ONTAP install - Mixture of SSD and FSAS

1 messages · Page 1 of 1 (latest)

bold dawn
#

Hi, Trying to do this install on the SSDs rather than FSAS, but it auto-picks the FSAS drives every time. Manually pre-assigning ownership doesn't work either. What can I do other than physically removing the spinning disks? I have the SSDs in shelf ID 01 and the spininers in 02 fwiw
thanks!

tired lintel
#

In the past i've just left the FSAS disconnected. Init the system with ADP and then add the FSAS in.

Note though, if you ADP the SSD, you can't use the drives in flashpool.

bold dawn
#

interesting. what's the best practice?

#

would assume the entire system runs a bit faster with aggr0 on flash, but not sure!

#

The other idea I had was to init with FSAS, then migrate to 3 (unpartitioned) SSDs per controller afterwards. Curious to hear anyone's thoughts. Thanks!

tired lintel
#

it'll run more optimized on SSD for sure.

You'd need to use 8 SSDs to put the root aggrs

From the remaining SSDs, create a StoragePool. and then divy out the partitoined between the 2 FSAS aggrs.

bold dawn
#

oh that's odd. so ontap Cdot now needs to live on 8 whole drives per node? I'm used to the old way of 7-mode where you could get away with 3 per node

tired lintel
#

3 per node, + spare per node

#

3+3+1+1

bold dawn
#

In this case though I'm assuming the best/only way to get the root vol on partitioned SSDs is to make sure they're the only devices attached to the head unit

#

ahh spares schmares 😛

#

we've got 24x SSD and 24x FSAS so I really don't want to use 2/3 of my SSD for just the root vol

#

oh sorry I think I mis-interpreted your 3+3+1+1, that's how ontap9 / cdot runs things?

#

Also seems a little silly that the only possible ONTAP ADP install location is on spinning disks in a hybrid environment. Should at least ask us 🙂

tired lintel
ripe jewel
#

I am pretty sure that if you assign the spinning disks to a random systemid, and clear the ownership of the SSDs. The spinners will not be used as you run the "zeoring of disks"... I haven't tested if it is even possible to assign a random systemid (it may only allow you to set a sysid that it can see).. .but it's worth a try?

#

All the ADP stuff can be done by hand when the system is up on the spinning disks... you then have to create the new aggregates and move the root volume.... it should all be described on the support site... I have done it a few times, but cannot remember the procedure in detail... bu for sure it is possible

fair berry
#

You didn't mention what FAS controller is involved, here...

limpid copper
bold dawn
bold dawn
fair berry
#

I hate to keep asking questions, but how many SSD and HDDs are we talking about, here?
Were you planning on using any SSDs as a Storage Pool?

severe smelt
#

Exactly. If you setup any SSD for adp, then you potentially get the benefit of two SSD aggregates consuming a total of two parity drives.

If the plan is for storage pool then adp the hdd.

It would be useful to have an idea of hours many of everything and how you expect to utilize the drives

fast flint
#

@bold dawn SSDs are always chosen last for ADP implementation during initialization. If you really want ADP on the SSDs, ensure that they are the only drives connected before you reinit the nodes. Otherwise, as you have experienced, it will get implemented on the spindles.