The answer is that both #1 and #2 are online. Regarding #1, as long as you're not taking paths away, the existing paths will not be affected. Regarding #2, this is an intended use case for SLOs. The system is designed for you to make those types of changes easily and online. For general documentation regarding Auto-Provisioning groups, I'd suggest the "Solutions Enabler 8.1 Array Management PDF".
Hi everyone,  I'm going to need to perform the following two separate actions in the near future, and I'm curious whether there's even the slightest possibility that either of them might disrupt host I/O to storage:  1) On a VMAX2, I want to add two more FA ports to a port group that already has two, bringing it up to four.  2) On a VMAX3, I want to change a storage group's SLO policy.  The port group and the storage group in question are both members of masking views used by my production environment, so I'm very nervous that hot changes might disrupt the paths between storage and host. Does anyone have experience making these changes in active masking views and can testify that they're totally harmless? Can anyone link to documentation saying these actions have been tested and proved non-disruptive?  Thanks, everyone!
Changes to existing VMAX masking views: disruptive?