Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SED Drives drive-protection-enabled flag reporting incorrectly
2021-04-19
06:49 AM
2,787 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
Did anyone else notice this also applying to 9.8P2?
https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1385348
When I run "storage aggregate show -aggregate * -fields encrypt-with-aggr-key,drive-protection-enabled" it lists the root aggregate for the SED disks as true for drive-protection-enabled and the data aggregates as false. Got myself in a pickle trying to work it out, then found the above bug. It could do with being tagged for 9.8P2 as well.
Solved! See The Solution
1 ACCEPTED SOLUTION
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would suggest registering a case so that it can be tracked, as the bug is relatively new.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you check the "storage encryption disk show -container-id <ID>" do you get the correct response from this output?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When we run 'storage encryption disk show' the disk has its non-default data-key-id and is in mode 'data', as such we know the disk itself is encrypted fine, as the root aggregate also shows drive-protection-enabled as true.
It very much matches the output issue as per that BURT, ideally it needs tagging for 9.8P2 as well as it effects us on that version as well as the ones currently listed.
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would suggest registering a case so that it can be tracked, as the bug is relatively new.
