Prior to VMAX, there was one single configuration lock (15) that was used for symconfigure. So config changes were required to be single threaded.
With VMAX, front-end, back-end and device level locks have been introduced (more granular level of locking). It is now possible to run certain types of config changes concurrently provided they don't need the same lock type.
I believe (That's what I studied) on DMX running with 5773 or earlier, configuration change acquired Symmetrix lock 15 and will not let any other config changes to occur until the lock is released. So eventually only one configuration change at a time and no parallelism is allowed.
dynamox
9 Legend
•
20.4K Posts
0
June 7th, 2011 05:00
found my old post
https://community.emc.com/message/505348
dynamox
9 Legend
•
20.4K Posts
0
June 5th, 2011 06:00
what array ?
PedalHarder
3 Apprentice
•
465 Posts
1
June 5th, 2011 15:00
Prior to VMAX, there was one single configuration lock (15) that was used for symconfigure. So config changes were required to be single threaded.
With VMAX, front-end, back-end and device level locks have been introduced (more granular level of locking). It is now possible to run certain types of config changes concurrently provided they don't need the same lock type.
OnlySandy
63 Posts
0
June 6th, 2011 21:00
DMX array .. (and going to procure Vmax soon)
GEMC
36 Posts
1
June 7th, 2011 04:00
I believe (That's what I studied) on DMX running with 5773 or earlier, configuration change acquired Symmetrix lock 15 and will not let any other config changes to occur until the lock is released. So eventually only one configuration change at a time and no parallelism is allowed.