Non-dedicated gatekeeper devices have been used - error

What does the gatekeeper selection report say? C:\Program Files\EMC\SYMAPI\log\GatekeeperSelectionReport.txt

Is there more than one Symm here? what does syminq or sympd list say? Makes me wonder if because of the ACLX (or VCM) devices present and they are, by definition, not dedicated it used them and doesnt like that they are not dedicated.

You could try altering these settings:

storapid:gk_use

This variable will instruct the Base Daemon to restrict itself to using dedicated gatekeeper devices only when making syscalls, or that it may use other non-dedicated devices to make syscalls.

Possible Settings for this variable:
legacy - (default) The storapid daemon may use non-dedicated devices as gatekeepers.  When this is used the storapid daemon will only use non-dedicated gatekeepers when the syscall load is high enough to warrant their use.

dedicated_only - The storapid must only use dedicated gatekeeper devices.

storapid:use_all_gks
This variable tells the Base Daemon whether or not it is free to use all available gatekeeper candidates.

Possible Settings for this variable:
enabled - (default) The base daemon is free to use all available gatekeepers.  This option also uses an internal locking mechanism to lock gatekeepers instead of using semaphores.  Using all gatekeepers impacts the small number of IFT (InfoMover) customers.

disabled - The base daemon restricts itself to using 75% of the available gatekeepers.

sympd output:

        Device Name           Directors                  Device

--------------------------- ------------- -------------------------------------

                                                                           Cap

Physical               Sym  SA DA :IT  Config        Attribute    Sts   (MB)

--------------------------- ------------- -------------------------------------

\\.\PHYSICALDRIVE3     0028 07G:1 08C:C5  2-Way Mir     N/Grp'd ACLX WD       3

\\.\PHYSICALDRIVE4     0069 07G:1 08D:D5  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE5     006A 07G:1 07C:D5  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE6     006B 07G:1 07D:C5  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE7     006C 07G:1 08A:D4  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE8     006D 07G:1 08B:C4  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE9     006E 07G:1 07A:C4  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE10    006F 07G:1 07B:D4  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE11    0070 07G:1 07A:D5  2-Way Mir     N/Asst'd GK  RW       3

\\.\PHYSICALDRIVE12    04EA 07G:1  NA:NA  RDF1+TDEV     Grp'd    (M) RW  615038

\\.\PHYSICALDRIVE13    0666 07G:1  NA:NA  TDEV          N/Grp'd      RW   51563

\\.\PHYSICALDRIVE15    0028 08F:0 08C:C5  2-Way Mir     N/Grp'd ACLX WD       3

                                         Flags

Device Name                        GK    DPR     Reason

--------------------------------   ---   -----   -------------------------------

PHYSICALDRIVE0                     No    OMS     Not a Symmetrix device

PHYSICALDRIVE1                     No    OMS     Not a Symmetrix device

PHYSICALDRIVE2                     No    OMP     Not a Symmetrix device

PHYSICALDRIVE17                    No    OMS     Not a Symmetrix device

PHYSICALDRIVE10                    Yes   DSN

PHYSICALDRIVE11                    Yes   DSN

PHYSICALDRIVE12                    No    OSN     The device is a thin device, but the version of Enginuity does not support using thin devices as gatekeepers

PHYSICALDRIVE13                    No    OSN     The device is a thin device, but the version of Enginuity does not support using thin devices as gatekeepers

PHYSICALDRIVE15                    Yes   VMS

PHYSICALDRIVE3                     Yes   VMS

PHYSICALDRIVE4                     Yes   DSN

PHYSICALDRIVE5                     Yes   DSN

PHYSICALDRIVE6                     Yes   DSN

PHYSICALDRIVE7                     Yes   DSN

PHYSICALDRIVE8                     Yes   DSN

PHYSICALDRIVE9                     Yes   DSN

PHYSICALDRIVE14                    Yes   VMS

PHYSICALDRIVE16                    Yes   VMS

Legend:

  Flags:

     (D)evice type: D = Dedicated GK, O = Other, V = VCM/ACLX device, ? = Unknown

     (P)athing    : M = Multi-pathed, S = Single Pathed, ? = Unknown

     (R)elation   : C = Child, N = None, P = Parent, S = Sibling, ? = Unknown

I have a feeling it has to do with those ACLX devices. Can you try putting them in the gkavoid file and then trying a symcfg dis and then the stordaemon command again? Do any other commands besides that one fail?

I did search but  did not find gkavoid file. I am using windows

Thanks. I have created the file with  2 entires in it.

I think I know what the problem is. I have 2 arrays that SE talks too thats why it shows that error.Thank you for your help.