In Enginuity 5874, customer Engineers (i.e. CE and IDE) handle configuration changes by taking the “CE Lock.” This prevents all dynamic and static configuration changes that can cause serious customer operational problems, or require the CE to rebuild the IMPL upgrade file. Enginuity 5875 and above provides an alternative to this issue by no longer requiring the CE to take the CE lock for most hardware upgrades, and some non-HW upgrades, when reading the “IMPL from System.” Execution of the upgrade is otherwise similar to the scripts, as found in Enginuity 5874. No new scripts have been added to 5875, and the same “Online Configuration Change” script is used. The static or dynamic configuration changes, performed between the time the CE takes “IMPL from System” and goes on-site to run the online configuration change, will be preserved. Once the CE gets to the site to run an online configuration upgrade, SymmWin will only read the hardware configuration changes from the customer Engineer’s IMPL and merge it with the updated System IMPL. All logical changes (if any) in the customer Engineer’s bin file will be ignored in the merge and only the allowable hardware and non-hardware changes will be executed. It is therefore important that the CE decides correctly whether the planned upgrade requires the CE lock taken or not, using the Simulation Utilities in the Procedure Wizard. [IMAGE]
I am looking for a procedure to put a lock on vmax box to prevent configuration session until that lock in not removed. All inputs are welcomed. Thanks in advance
How to lock a VMAX box to prevent config changes by anyone.