Unsolved
This post is more than 5 years old
12 Posts
0
5138
Symcfg Discover & Symcfg Sync commands
We are using VMAX 20K via Red Hat Linux with SYMCLI 8.1.2.0 Version.
Periodically when the frame goes out of sync with the BIN files, we have to perform either a "symcfg discover" or "symcfg sync" command to bring the frame and BIN file back into sync.
When either of these commands are executed, must other symcli commands, i.e. symclone, wait until the syncing has completed or can other processes be executing other symcli commands in parallel while the syncing is in progress?
In other words, do we have to stop all other processes from executing other symcli commands until the "symcfg discover" or "symcfg sync" commands have completed?
finbarrcorksac
99 Posts
0
October 5th, 2017 03:00
Hi Thomas,
no all these symcli these commands can run asynchronously but you may need to open a new command line as the discover and sync will normally take a minute to run.
Regards
Fin.
ThortonMellon
12 Posts
0
October 9th, 2017 09:00
Fin,
Thanks so much for replying to my question, I appreciate you taking the time to do so.
Just to be clear before we code a solution to solve the issue of the frame and BIN files being out of sync.
If I have two independent processes actively running where the first process is executing a "symcfg discover" command, can the second process then execute successfully "symclone recreate" and "symclone activate" commands before the first process has completed the "symcfg discover" command, as you say the discover may take a minute or two to complete?
The concern centers around whether while updating the BIN files by one process it can interfere with simultaneous access to the BIN files by other processes.
As a side note, we've noticed that when the frame and BIN files are out of sync, the symcli commands can take up to four times longer to complete, hence the reason for us running discovers in between other symcli commands.
Thanks again for any light you can shed on this question.
TL
PedalHarder
465 Posts
0
October 9th, 2017 14:00
When the symapi_db.bin is being updated, an exclusive lock is obtained and therefore its possible for other processes to wait for this. To avoid or minimize this, use the SE environment variable SYMCLI_CTL_ACCESS=PARALLEL.
The number of gatekeepers is also important when running CLI commands in parallel. Over and above the minimum number of GK's, there should be one for each concurrent CLI command to ensure there is an available target for the command.
ThortonMellon
12 Posts
0
October 11th, 2017 05:00
Jason,
Thanks so much for replying to my questions. I appreciate you taking the time to do so.
We are currently using the settings below so it sounds like we should be good:
SYMCLI_CTL_ACCESS=PARALLEL
SYMCLI_WAIT_ON_DB=1
SYMCLI_WAIT_ON_GK=1
Do you foresee any changes with regard to the release of the 8.4 SYMCLI release on how the SYMCFG Discover functions?
Thanks again,
TL
PedalHarder
465 Posts
0
October 11th, 2017 19:00
No, you should be all set with those environmental settings.