This is also in the Solutions Enabler Array Controls Product Guide.  Below is from page 49 of the latest 7.6 version: SCSI3_persist_reserv (persistent group reservation) -  In Enginuity 5874 and lower, this attribute is disabled by default. In Enginuity 5875 and higher, this attribute is enabled by default. When running Solutions Enabler V7.5 with Enginuity 5876 Q42012SR and higher, you can set or clear the SCSI-3 persistence attribute only if the device is unmapped.
Guys , Customer needs to set PER bit for some volumes at VMAX running 5876 code. This box was installed at 5874 code, so , volumes doesn't have PER bit by default.  It was upgraded to 5875 and 5876. They realized that some W2K8 devices doesn't have PER bit and some have.  They informed that when trying to set this attribute , they are receiving a warning saying that volumes shoud be Unmapped from FA first.  Doing a binfile simulation it shows just the modification that we want :   I would like to know if both situations are really different , I mean , will software change UNMAP volumes from FA port and using binfile NOT ?  Need I handle it as a DIsruptive activity at host perspective ? Thanks in advance, Joelson
will PER bit setting force Unmap\MAP from FA port for VMAX boxes ?