I am currently planning to configure a FAS50+DS224C (24x3.84T SAS SSD), but I cannot see 3.84T being used as ADP (root-data-data) in either Fusion or HWU, whereas it is possible with the FAS70. Has anyone done this manually?
#Why can't FAS50 use 3.84T as an ADP partition?
1 messages · Page 1 of 1 (latest)
The last info I remember is that booting from internal SSDs is supported.
Not entirely sure though if using external SSDs with ADPv2 is supported.
Thank you very much for your reply. I still hope that ADPV2 can support external hard drives. Otherwise, given the rising hardware costs, using six 3.84T SSDs for system partitioning is really a bit extravagant.
There's no ADPv2 for the FAS50.
You also have to buy it with spinning drives, can't just do SSD.
I bet you can @solar hawk , you just cannot order it that way:
Order FAS50 with one shelf of external SSD (not NVMe) and some number of spinners
When I get it, remove the SATA disks with only the SSDs. Init the system.
It is not advertised, but I would be surprised if it DID NOT do ADPv2 on the SSDs if they are the ONLY non-flashcache disks in the system
Not supported, of course...it may work though 😉
i'm always talking offically supported 🙂
would certianly be a fun experiment
We have a few F50 with DS460 and ADP... yet I think they may have been migrated from an old setup (FAS2700)... so it seems to work fine, and I wasn't aware that it wasn't supported...
like a disk swap with a 2700 to a fas50 internally?
well we had the old DS212C shelfs attached, together with the F50... then migrated the root aggregates and then the volumes to the D460...
Seem to remember I created the partitions manually... 🙂
Aggregate na12_rootaggr (online, raid_dp) (block checksums)
Plex /na12_rootaggr/plex0 (online, normal, active, pool0)
RAID group /na12_rootaggr/plex0/rg0 (normal, block checksums)RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- dparity 3d.10.0P2 3d 10 0 SA:A 0 FSAS 7200 23928/49004544 23936/49020928 parity 3a.10.1P2 3a 10 1 SA:B 0 FSAS 7200 23928/49004544 23936/49020928 data 3d.10.2P2 3d 10 2 SA:A 0 FSAS 7200 23928/49004544 23936/49020928 data 3a.10.3P2 3a 10 3 SA:B 0 FSAS 7200 23928/49004544 23936/49020928 data 3d.10.4P2 3d 10 4 SA:A 0 FSAS 7200 23928/49004544 23936/49020928 data 3a.10.5P2 3a 10 5 SA:B 0 FSAS 7200 23928/49004544 23936/49020928 data 3d.10.6P2 3d 10 6 SA:A 0 FSAS 7200 23928/49004544 23936/49020928 data 3a.10.7P2 3a 10 7 SA:B 0 FSAS 7200 23928/49004544 23936/49020928 data 3a.10.9P2 3a 10 9 SA:B 0 FSAS 7200 23928/49004544 23936/49020928 data 3d.10.10P2 3d 10 10 SA:A 0 FSAS 7200 23928/49004544 23936/49020928 data 3d.10.12P2 3d 10 12 SA:A 0 FSAS 7200 23928/49004544 23936/49020928
....or was it a part of the root aggr migration where there was a procedure to create the partitions and then run the migration pointing to the P2 partitions?
Pretty sure I had some help in here for that 😉
..and the migration was something like FAS2700 headswap to F50 where we also converted the old FAS2700 controller shelf to a normal shelf with IOM12... (downtime), then attached the DS460, created the new root partitions and migrated to them... then setup new data aggregates on DS460, and volume move to them... finally disconnected old shelfs...
So I'm 99,9% sure you can setup F50 with SAS SSDs and ADP only thing is that you cannot quote a price with F50 and only SSDs (because of marketing reasons)... you need to have some (not sure how many) SAS disks on the quote, and then you are able to quote SSDs and maybe even NVMe... But maybe there is something inside ONTAP which disables ADP when setting up a new system? Then I guess you will need to boot into maint-mode and partition the disks manually.... then assign them, and try an install... But it would surprise me if it doesn't do ADP per default....
Oh, it will do ADP. The question is, with SAS SSD only attached, will it actually do ADPv2 like other FAS platforms do?
OK... I understand... only one way to find out 😉 Or else I guess you "could" hack it a bit by creating the partitions and assigning them in maint. mode... I think there are way too many marketing people interfering in the way we use the hardware 🙂