amber yew
Hey! How do I check if my C-series system is R1 or R2?
I assume there's an easy comparison between the two when looking at the CPU cores or something like that but I only have one system.
Also taking the opportunity to say that removing the CPU category in HWU is a shitty decision and I hope NetApp product management realize this.
Obviously I think that all R2 systems should be unlocked as well, rolling back this whole PR disaster.
brazen snow
I think, but am not sure, it will say R2 on the front panel?
upper dagger
Hmmm I don't think so, since the differences between AFF C-Series R1 and R2 where kind of internal. They only "reused" the R2 name but I think externally they are still called for example AFF C30 without any mentioning of "R2".
lime axle
yeah, no external differences AFAIK.... The only way to tell I think is by the number of CPU cores reported in ONTAP
it's not even as easy as saying "if it was sold after $DATE it's r2" because they were still selling R1 systems for a while (or maybe still are?), since R2 models were not HANA certified for example
wise harness
Yep, Date is the easiest way to tell. after Q1 2025 is R2
lime axle
not really, we still have a few R1's incoming for some customers...
wise harness
ya said the quiet part outloud again buddy.
brazen snow
not really, we still have a few R1's incoming for some customers...
so did we... sold a MCCIP which isn't even installed yet... and they should be R1 models... so would actually be nice to know how this can be verified 😉 this system was delivered Q4 25...
upper dagger
So the OSDNA value can't be checked on the system? (via ASUPs or something)
lime axle
So the OSDNA value can't be checked on the system? (via ASUPs or something)
those IDs are not public though I think, so you can't really make sense of them without the list 🙂
wise harness
yeah the matrix to decode it isn't public
amber yew
Damn, this seems way harder than it should be to find out.
brazen snow
Damn, this seems way harder than it should be to find out.
Totally agree
upper dagger
I've just noticed you can see it directly in "sysconfig -a" without any matrix decoding shenanigans.
Look for this line: Model Revision: r2 (checked on a system with 9.16.1P9)
When it's missing you have an r1 model.
amber yew
I've just noticed you can see it directly in "sysconfig -a" without any matrix d...
Awesome! I just got an answer from NetApp through Partner channels for making sure it's R1:
bootarg.init.dna = 48
obsidian fox
Awesome! I just got an answer from NetApp through Partner channels for making su...
this value has a small chance of being wrong: FAS500f has also dna 48 - just for your info 😉 but for C-Series R1 its also valid
upper dagger
Yeah, there are also other models which use the value 48. But since the corresponding R2 models have other values you can still use it to differentiate. But I think using "sysconfig -a" is the easiest.
keen moat
WTF! -> I just had a customer have a failed boot media on an A400. AFter the engineer replaced the media, the bootarg.init.dna was set to freaking 0!!!! The system would not function!
Why TF would this get set to 0? How TF would this get set to 0?
It took the engineer 6 hours to replace the boot media because of this ONE variable
lime axle
I guess there was an env file on that bootmedia with the wrong setting?
keen moat
It’s one of those read only variables. Took some effort to “fix” it since the node wouldn’t boot