Where is Create Aggregate Option in new System Manager

[Infra-ADM]

Hi,

Since Classic view has been removed from SystemManager, I was wondering where is new Aggregate create option in new Sysmgr Located ?? 

And when I click on Create new volume it says "You can add only NAS volumes".  any idea why this could be happening.

Ontap version is 9.8P2

Your help would be appreciated.

Thanks

[SpindleNinja]

Storage -> Tiers - "Add local tier" 

[Infra-ADM]

Thanks for the response.

When i click on add local tier, it shows this message 

Any idea!!

[SpindleNinja]

Do you have enough spare disks to create an aggr?   I get the same thing on my lab system, but I only have 2 spares.   

Cluster -> disks. will show you in the GUI.  

[Infra-ADM]

Yes, this system is brand new.. no aggregate currently exists on this system.

[SpindleNinja]

Can you connect to the CLI and run the following: 

::>row 0

::>aggr show 

::>storage disk show 

[Infra-ADM]

Here is the output.

::> row 0
(rows)

::> aggr show

Aggregate Size Available Used% State #Vols Nodes RAID Status
--------- -------- --------- ----- ------- ------ ---------------- ------------
aggr0_ _01 159.9GB 7.75GB 95% online 1 -01 raid_dp,
normal
aggr0_ _02 159.9GB 7.75GB 95% online 1 -02 raid_dp,
normal
2 entries were displayed.

::> storage disk show
Usable Disk Container Container
Disk Size Shelf Bay Type Type Name Owner
---------------- ---------- ----- --- ------- ----------- --------- --------

Info: This cluster has partitioned disks. To get a complete list of spare disk capacity use "storage aggregate show-spare-disks".
1.1.0 7.14TB 1 0 FSAS shared aggr0_ _02 -02
1.1.1 7.14TB 1 1 FSAS shared aggr0_ _01 -01
1.1.2 7.14TB 1 2 FSAS shared aggr0_ _02 -02
1.1.3 7.14TB 1 3 FSAS shared aggr0_ _01 -01
1.1.4 7.14TB 1 4 FSAS shared aggr0_ _02 -02
1.1.5 7.14TB 1 5 FSAS shared aggr0_ _01 -01
1.1.6 7.14TB 1 6 FSAS shared aggr0_ _02 -02
1.1.7 7.14TB 1 7 FSAS shared aggr0_ _01 -01
1.1.8 7.14TB 1 8 FSAS shared aggr0_ _02 -02
1.1.9 7.14TB 1 9 FSAS shared aggr0_ _01 -01
1.1.10 7.14TB 1 10 FSAS shared - -02
1.1.11 7.14TB 1 11 FSAS shared - -01
1.12.0 3.49TB 12 0 SSD spare Pool0 -02
1.12.1 3.49TB 12 1 SSD spare Pool0 -02
1.12.2 3.49TB 12 2 SSD spare Pool0 -02
1.12.3 3.49TB 12 3 SSD spare Pool0 -02
1.12.4 3.49TB 12 4 SSD spare Pool0 -02
1.12.5 3.49TB 12 5 SSD spare Pool0 -02
1.12.6 3.49TB 12 6 SSD spare Pool0 -02
1.12.7 3.49TB 12 7 SSD spare Pool0 -02
1.12.8 3.49TB 12 8 SSD spare Pool0 -02
1.12.9 3.49TB 12 9 SSD spare Pool0 -02
1.12.10 3.49TB 12 10 SSD spare Pool0 -02
1.12.11 3.49TB 12 11 SSD spare Pool0 -02
1.12.12 3.49TB 12 12 SSD spare Pool0 -02
1.12.13 3.49TB 12 13 SSD spare Pool0 -02
1.12.14 3.49TB 12 14 SSD spare Pool0 -02
1.12.15 3.49TB 12 15 SSD spare Pool0 -02
1.12.16 3.49TB 12 16 SSD spare Pool0 -02
1.12.17 3.49TB 12 17 SSD spare Pool0 -02
1.12.18 3.49TB 12 18 SSD spare Pool0 -02
1.12.19 3.49TB 12 19 SSD spare Pool0 -02
1.12.20 3.49TB 12 20 SSD spare Pool0 -02
1.12.21 3.49TB 12 21 SSD spare Pool0 -02
1.12.22 3.49TB 12 22 SSD spare Pool0 -02
1.12.23 3.49TB 12 23 SSD spare Pool0 -02

[SpindleNinja]

Internal 8TB SATA drives in ADP. 

External shelf of SSDs

What was the intent of the config as it was sold?   any flashpool?  or just a SATA aggr and a SSD aggr? 

I do wonder why it's not detecting any recommendations.  

[TMACMD]

He is the issue I think

 the system (GUI) wants to use raid-tec to build an aggregate with the SATA drives but I recall 7 being the minimum. Each node has 5 partitioned and one whole for a total of 6. Under the minimum

 additionally I think with ssd the GUI wants to split the ssds between the controllers. They are all assigned to node 2. 

i think you need to turn off the disk auto assignment then remove the ownership of all the data partitions on the partitioned drives for node 2 and reassign them to node 1. 

you can then make a single aggregate with 9 data and 3 parity drives

 you can also decide if you want the ssd to be an aggregate or save some of them and make them a flash pool to add ssd cache to the SATA aggregate

[Infra-ADM]

Hi @TMACMD ,

Thanks for the reply. We did try  to create local tier before these disks were assigned to one controller and got same error. Disks were assigned to one controller later on just to see if this step helps.

btw why system wants to create raid-tec ? is there any option where we could change this preference somehow to create Raid DP by default may be.

Regards,