#ASAr2 Multi-Admin Verification

1 messages · Page 1 of 1 (latest)

marsh aurora
#

Am I missing something or is ASAr2 missing the ability setup approval for LUN-released processes?

I'd like to setup MAV for things like "lun delete" and "lun unmap", but I don't see the anything for the LUN commands.

fleet elm
#

"lun delete" should be there, I can see it on a unified system (9.18.1RC1) but it's missing on ASAr2 (C30, 9.18.1RC1), together with some other commands which are irrelevant on ASA. Guess they removed one command too much.

#

I would suggest to report it to NetApp as a bug.

#

And I think "lun unmap" was never in the MAV rule list.

#

There is no "storage-unit delete" CMD so I guess "lun delete" is still the valid one.

marsh aurora
#

Yea, I bugged my account team about it yesterday...

vapid burrow
#

lun delete is in there. bu tif it's missing from ASAr2 then yeah. bug. (both should be in there IMHO as unmap can mess shit up too)

I am suprised they did not have you open a support case to track an RFE for Engineering and get this fixed with the next update.

steady scroll
#

MAV is a cool feature... but have they ever "fixed" the integration issue? If you want to use SnapCenter and do clones etc.. but you have "volume delete" in your MAV setup... then SnapCenter also cannot delete clones... same thing with "snapshot delete"...

fleet elm
#

Yeah, I think that's still the case but didn't try it again. They need to implement some query like "-is-clone false" so MAV would not trigger if it's a volclone. But I think last I checked there's no such parameter with "vol delete".

For snapshots you could at least filter for the snapshot name if you know how SnapCenter names the clones.

pallid dragon
steady scroll