AFF-A150 show as FAS2750 in the GUI and CLI

[stuck night]

We where adding 2 new nodes AFF-A150 to the existing AFF-A200 cluster which are connected to CN1610, however, the AFF-A200 is on 9.9.1P15, so we did the netboot and option 7 boot menu to keep the same image as the existing one, however, it seems, if you downgrade the AFF-A150 less than 9.10 [recommended by NetApp], the platform show as FAS2750, but the disks are on ADPv2[interesting]

So what happen if we upgrade the AFF-A150 from 9.9.1P15 to 9.11 to 9.12, will still showing as FAS2750? or will show as AFF-A150?
If not, do we need to remove the nodes, and wipe out the AFF-A150 then make the netboot steps and install the new image[9.11 or 9.12]
Once is done, with that, allow the cluster with AFF-A200 running 9.9.1P15 can run mix ontap releases, based on the doc mix cluster, and we have up to 90 days to make the migrations

keys

90 days allow only
enable mix version in the old cluster
https://docs.netapp.com/us-en/ontap/upgrade/concept_mixed_version_requirements.html#requirements-for-mixed-version-ontap-clusters

https://docs.netapp.com/us-en/ontap-systems/whats-new.html#platform-support

"Do not attempt to install or boot your AFF A150 storage system with an unsupported version of ONTAP. If you attempt to install or boot your system with an unsupported version of ONTAP, ONTAP will allow it (ONTAP will not block the attempt). The consequence is that your AFF A150 storage system will come up as a FAS2750 storage system."

We already have a case open, however, I'm looking for more perspectives

[indigo bridge]

Any reason you can't update your existing A200 cluster to 9.11.1 first before adding the new A150 nodes?

[stuck night]

they're not under support, they do not want to take any risks

yeah the easier and fastest step will making an upgrade

[brisk yew]

Yeah. Should have checked the support matrix before loading an old/unsupported version on the a150. You can try to reinit with 9.10. It’s fine to have a mixed version cluster especially for migrations.

Also if you have SSD only on a fas you still get adpv2. That is 100% normal

[stuck night]

I have done this before with some platforms, I've never had this behavior before, that's why got me curious about it,
So do you think, If I upgrade the A150 the system profile will show as A150? or just reinit everything?

Also if you have SSD only on a fas you still get adpv2. That is 100% normal, I did not know that

[brisk yew]

I’ve been known to detach spinners, init fas with only SSD to maximize symmetry and minimize parity. Then attach the spinners

I have no idea on the upgrade. If you aren’t using yet, I’d remove from the cluster, reinit and verify

[stuck night]

Gotcha, That's something interesting and makes sense, because, in fusion give us 72TB but due to this issue, only gave us 68TB, I Think the best path here is reinit to verify the space and address the issue

[brisk yew]

I’ve found do many “bugs” in fusion where I can’t build like I do in the field.
Heck on an aff in the field of I have two different models of the same drive, I can build a single aggregate but fusion won’t allow it. I use it for guidance and sometimes a half build and then double space

[velvet gyro]

I'd remove the A150, reimage it directly with 9.12.1 (can have up to 4 major versions difference in a mixed-version cluster since 9.8+), then join it back, then migrate everything and get that A200 out of there asap.

I have to do this next week for a customer getting of an A200.

And did it recently moving from FAS8060 to A400 for another customer (9.8 and 9.12.1 in a mixed version cluster). No problems.

[brisk yew]

@velvet gyro if you do that you MUST get the ONTAP license keys for those nodes until ONTAP effective cluster version is 9.10 or higher