Unsolved
This post is more than 5 years old
5 Practitioner
•
274.2K Posts
0
1535
SFA 467233 -VMAX3 x CE config lock
Guys ,
Today we had to make a CE lock in a VMAX3 in order to change the binfile ( RCM did it ).
Taking the SFA 467233 " where a CE lock is required for a system configuration change " https://emcservice--c.na55.visual.force.com/apex/KB_BreakFix_clone?id=kA2j0000000R5z8 , we can find a XLS spreadsheet with following items
VMAX3_CE_locks_policies where changes that are possible to execute with CE lock in place are shown :
| Change Type | Application/Interface |
| Create TDEV | symconfigure |
| Adding a gatekeeper device | symconfigure |
| Adding an RDF mirror | symconfigure |
| Convert DEV (BCV/Celera) | symconfigure |
| Delete device | symconfigure |
| Remove RDF mirror | symconfigure |
| Setting a device identifier | symconfigure |
| Setting a Storage Resource Pool (SRP) parameter | symconfigure |
| Setting a name to an Service Level Objective (SLO) | symconfigure |
| Setting a Symmetrix configuration metric | symconfigure |
| Reserving a device | symconfigure |
| Renaming a Storage Resource Pool (SRP) | symconfigure |
| Activating an edisk for use | symconfigure |
| Starting a drain operation on a external disk | symconfigure |
| Stoping drain operation on a external disk | symconfigure |
| Associating a port to a director emulation | symconfigure |
| Disassociating a port from a director emulation | symconfigure |
| Creating an IP Interface | symconfigure |
| Modifying an IP Interface | symconfigure |
| Deleting an IP Interface | symconfigure |
| Adding an IP Route | symconfigure |
| Removing an IP Route | symconfigure |
| Creating an iSCSI target | symconfigure |
| Modifying an iSCSI target | symconfigure |
| Renaming an iSCSI target | symconfigure |
| Deleting an iSCSI target | symconfigure |
| Attaching an IP Interface to an iSCSI target | symconfigure |
| Detaching an IP Interface from an iSCSI target | symconfigure |
| rw_enable | symdev |
| write_disable | symdev |
| ready | symdev |
| not_ready | symdev |
| hold | symdev |
| unhold | symdev |
| set -geometry | symdev |
| relabel | symdev |
| allocate | symdev |
| allocate -stop | symdev |
| free | symdev |
| reclaim | symdev |
| set -persistent | symdev |
| unset -persistent | symdev |
| set -gcm | symdev |
| unset -gcm | symdev |
| set -no_identity | symdev |
| create -tdev | symdev |
| create <-gk|-as400_gk> [-N <#>] | symdev |
| delete | symdev |
| modify | symdev |
| All RDF operations | symrdf |
| All | symmirr |
| All | symclone |
| All | symsnapvx |
| All | symaccess (masking) |
| All | symrcopy |
| All | symsg |
| Director and port (online/offline) | symcfg |
My question is :
Customer tried to provision some volumes using Unisphere interface and it FAILED pointing that LOCK was in effect and it couldn't be executed.
Is it correct ? Supposedly it should work, right ?
It's a VMAX V3 250F running code 5977-952-892-6243 .
Customer is using a Centralized Unisphere that already is working with their VMAX100K boxes ( Don't know exaclty which version ).
Thanks in advance.