#Encryption rekey warning?
21 messages · Page 1 of 1 (latest)
On the command line, what does
storage encryption disk show
Look like? (At both sites)
NA-TOR::> storage encryption disk show
Disk Mode Data Key ID
1.0.0 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.1 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.2 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.3 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.4 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.5 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.6 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
1.0.7 data 00000000000000000200000000000100EE7E506DAF640A931AAE7636A01A0336
same key on both sites...
not sure if it could be the root partitions?
not sure if it makes a difference, but I had to run the rekey from the commandline on one of the clusters.. where the other one it managed to do it via SystemManager... but they both look the same now...
....and failover/switchover works 😉
Those are just SEDs. FIPS drives will have a second encryption string field
So then after the rekey, output better?
Nope not inside SystemManager it still has the warning... same on both clusters...
Any messages that seem to correlate? Curious what system manager is referring to?
Nope, that's just it... I can only do a "rekey" again, and again but doesn't make any difference it stays like this... 🙂 and as you can see tha aggregate has barely any volumes on it and now workloads...
On one of the clusters where I had to configure it via command line I get this:
`NA-TOR::*> storage encryption disk show-status
FIPS Latest Start Execution Disks Disks Disks
Node Support Request Timestamp Time (sec) Begun Done Successful
NA-TOR-02
false unknown - - - - -
NA-TOR-01
false unknown - - - - -
2 entries were displayed.`
....guess this is normal and because the nodes has been rebooted...
nothing in the event logs at all... as I try to run the rekey from system manager...
I have the same issue on 9.16.1, seems like a bug?
If it's a bug it isn't fix in 9.17.1P9 yet 😉 I have a support case open right now... hopefully they find a solution
keep us posted
In a MCC this warning can apparently be ignored... "https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/System_Manager_reporting_Need_disk_rekey_(includes_partner_cluster)_in_a_MetroCluster"
Update.. acording to this: https://kb.netapp.com/on-prem/ontap/DM/System_Manager/ONTAP_System_Manager_Issues/CONTAP-443858
...it should be fixed in 9.17.1RC1 onwards... yet we are on 9.17.1P9 and still see the bug...