Unsolved
This post is more than 5 years old
2 Intern
•
1.3K Posts
1
5823
GK cannot be opened becase locked or inaccessible
DMX4-24 / 5772
SMYCLi V6.5.0.0.0
HP-UX 11.23
We have some scripts which runs the est/spit to the mentioned device group and sometime failing with the following error. I noticed that the same error is even reported with the query. This host has only one device group (three set of BCV though) and synced at every four hour interval. Currently two GK defined and no errors logged in symapi log.
ANY one familar with the errors and a possible fix??
:root [/opt/emc/API/symapi/config] symmir -g p599apps_BRBCV_dg query -multi
A gate keeper cannot be opened because it (or they) are either locked or inaccessible
Device group 'p599apps_BRBCV_dg' does not have any standard devices that are BCV paired.
SMYCLi V6.5.0.0.0
HP-UX 11.23
We have some scripts which runs the est/spit to the mentioned device group and sometime failing with the following error. I noticed that the same error is even reported with the query. This host has only one device group (three set of BCV though) and synced at every four hour interval. Currently two GK defined and no errors logged in symapi log.
ANY one familar with the errors and a possible fix??
:root [/opt/emc/API/symapi/config] symmir -g p599apps_BRBCV_dg query -multi
A gate keeper cannot be opened because it (or they) are either locked or inaccessible
Device group 'p599apps_BRBCV_dg' does not have any standard devices that are BCV paired.
smw61811
45 Posts
0
August 12th, 2009 05:00
2. Did you have any symcli commands that maybe hung, or didn't complete?
3. Check a symcfg -lockn 13 list. If there's nothing going on and you have a lock in place
you might consider removing the lock.
4. You might need a 3rd gatekeeper depending on how many timefinder/etc operations
are happening simultaneously.
5. Try restarting all symapisrv and/or storapid processes and then try your operation again.
Check out emc136717 and emc107027 as a starting point.
Edit: Also check out emc94039.
Message was edited by:
smw6181
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
August 12th, 2009 08:00
Lock Proc.
ID Key State Type Wait Lock Full Path Specification
------ ---------- -------- ---- ----- ----------------------------
1867803 0x450ccfea Unlocked GK 0 /dev/rdsk/c36t0d0
524323 0x450ccff5 Unlocked GK 0 /dev/rdsk/c38t0d0
25 0x450cd123 Locked GK 0 /dev/rdsk/c38t0d1
33 0x450cd125 Unlocked GK 0 /dev/rdsk/c38t0d2
98340 0x450d1e90 Unlocked GK 0 /dev/rdsk/c40t0d0
1179685 0x450d1e86 Unlocked GK 0 /dev/rdsk/c43t0d0
23 0x49157442 Unlocked DB 0 /var/symapi/db/symapi_db.bin
:root [/opt/emc/API/symapi/config] powermt display dev=c43t0d0
Bad dev value c43t0d0, or not under Powerpath control.
:root [/opt/emc/API/symapi/config] powermt display dev=c40t0d0
Bad dev value c40t0d0, or not under Powerpath control.
How can i release/cleaup those inaccessibe GK?
MaximUnited
111 Posts
0
August 13th, 2009 06:00
make sure you got the right number
I also advise killing all stordaemons with 'stordaemon shutdown all -immediate'
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
August 13th, 2009 19:00
with device groups.
why would you not want to associate your gatekeepers with device groups ?. According to "EMC Solutions Enabler Symmetrix Array Management CLI" you do want to associate gatekeepers with a device group so they are used by symcli first instead of regular devices when issuing commands to your Symm.
smw61811
45 Posts
0
August 14th, 2009 06:00
In this particular case, the server did have gatekeepers assigned to it, but all of them had been associated with device groups. The storapid daemon will not select gatekeepers which are in device groups.
I should have been more clear and said, 'make sure at least one GK isn't associated'.
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
August 17th, 2009 05:00
##added on 08142009 for debug
SYMAPI_DEBUG=-1
export SYMAPI_DEBUG
SYMAPI_DEBUG_FILENAME=/eb_rao11_d/applmgr/SYMAPI_DEBUG/SYMAPI_DEBUG.txt
export SYMAPI_DEBUG_FILENAME
## END of debug
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
August 21st, 2009 06:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
August 21st, 2009 11:00
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
August 25th, 2009 02:00
rawstorage
419 Posts
1
August 26th, 2009 00:00
Edit to add link: http://csgateway.emc.com/primus.asp?id=emc128411
This explains all you need to know about how the VCM works with the latest code releases
Message was edited by:
Dave Yates,
The Benevolent Moderator
MKG3
1 Message
1
August 28th, 2009 21:00
Fix As a workaround, recreate the ldb directory by using the following steps (assuming S.E. is in the default directory) and retry the command. If root cause is required, contact the Support Center and quote this solution.
1. c:\program files\emc\symcli\storbin\stordaemon shutdown storapid
2. ren c:\program files\emc\symapi\ldb c:\program files\emc\symapi\ldb.bad
3. c:\program files\emc\symcli\storbin\stordaemon start storapid
never knew what step 2 was but did step 1 and 3 and it fixed my issue. I finally had to add gate keepers as you need a minimum of 6. Good luck
MKG
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
August 29th, 2009 03:00
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
August 29th, 2009 03:00
"Solutions Enabler 6.3 and higher will block the setting of this bit". That does sound like VCMDB is still not used as GK. is that right??
Message was edited by:
SKT
SKT2
2 Intern
2 Intern
•
1.3K Posts
0
September 22nd, 2009 04:00
rawstorage
419 Posts
0
October 12th, 2009 01:00
it is not advisable to run without tha storapid process running. We only ever recommended implementing this as a workaround.
The daemon does lots of neat stuff, and should not be turned off.
If you open an SR with support we can have a look at your configuration and tell you exactly what you need to do to correct your situation.