4 Beryllium

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.
Labels (1)
18 Replies
3 Silver

Re: GK cannot be opened becase locked or inaccessible

1. Make sure none of your gatekeepers are associated with device groups.
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
0 Kudos
7 Thorium

Re: GK cannot be opened becase locked or inaccessible

1. Make sure none of your gatekeepers are associated
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.
0 Kudos
3 Silver

Re: GK cannot be opened becase locked or inaccessible

According to emc136717:

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'.
0 Kudos
4 Beryllium

Re: GK cannot be opened becase locked or inaccessible

DEBUG enabled on the script . But there are no errors for last three days.

##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
0 Kudos
4 Beryllium

Re: GK cannot be opened becase locked or inaccessible

can a VCMDB device be a candidate for GK?
0 Kudos
5 Tungsten

Re: GK cannot be opened becase locked or inaccessible

Since DMX3 the VCMDB is a GK.
0 Kudos
4 Beryllium

Re: GK cannot be opened becase locked or inaccessible

can you point me a doc saying so?
0 Kudos
3 Zinc

Re: GK cannot be opened becase locked or inaccessible

emc128411 Volume Configuration Manager (VCM) device and Enginuity 5771

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
4 Beryllium

Re: GK cannot be opened becase locked or inaccessible

emc128411 is not so stright forward to understand .Note that my array is at code 5772.

"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
0 Kudos