Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

12333

December 2nd, 2013 18:00

gatekeeper error when run symcfg on linux server

./symcfg -sid 1234 list -v

The gatekeeper device (while using the Base Daemon) has an error (Please see the Log file)

It's DMX4 FRAME

Could you please share with me what could be the cause of the error, and how to fix it?

Thank you!

9 Legend

 • 

20.4K Posts

December 15th, 2013 13:00

1) remove gatekeeper devices from host A

symaccess -sid 123 -name sg_name -type storage remove devs #,#,#,#  -unmap

2) add gatekeepers to host B

symaccess -sid 123 -name sg_name -type storage add devs #,#,#,#

Once you discover devices in host B (should be visible in output of syminq), define them

symgate define pd

for example on a windows box you would run this command:

symgate define pd \\.\PHYSICALDRIVE8

9 Legend

 • 

20.4K Posts

December 2nd, 2013 20:00

do you still have access to gatekeepers ? run syminq

2 Intern

 • 

211 Posts

December 4th, 2013 13:00

It seems to me I don't have any gatekeepers. Now does that mean I no longer have the access to gatekeepers? is this due to zoning issue, or provisioning issue? any commands I can use to list all gatekeepers from the frame? Thank you!

# ./syminq

      Device               Product                   Device
----------------- --------------------------- ---------------------
Name       Type   Vendor    ID           Rev  Ser Num      Cap (KB)
----------------- --------------------------- ---------------------
/dev/sda          DELL      PERC 5/i     1.03 N/A         142737408
/dev/sdh          DGC       RAID 5       0326 EE000006     81788928
/dev/sdi          DGC       RAID 5       0326 EE000006     81788928
/dev/sdj          DGC       RAID 5       0326 EE000006     81788928
/dev/sdk          DGC       RAID 5       0326 EE000006     81788928
/dev/sdr          DGC       RAID 5       0326 EE000006     81788928
/dev/sds          DGC       RAID 5       0326 EE000006     81788928
/dev/sdt          Dell      Virtual  Fl* 123  x5                N/A
/dev/dm-14        DGC       RAID 5       0326 EE000006     81788928

9 Legend

 • 

20.4K Posts

December 4th, 2013 17:00

did somebody unzone you from your DMX box, DGC devices are Clariion/VNX.

4 Operator

 • 

2.1K Posts

December 4th, 2013 18:00

You may verify your SE host recognized any GK by running following commands, otherwise your SE command will not run successfully. 

stordaemon action storapid –cmd show –gk_pdevs –sid xxx

stordaemon  action storapid –cmd show -gk_stats –sid xxx


If you don's see any GKs, you'd better to config zoning, mapping, masking for the GKs in your array through another SE host. Refer KB https://support.emc.com/kb/74113 

2 Intern

 • 

211 Posts

December 7th, 2013 09:00

I got the following. What did that indicate?

# ./stordaemon action storapid -cmd show -gk_pdevs -sid 1234

storapid                      [ Operation not supported by daemon ]

# ./stordaemon action storapid -cmd show -gk_stats -sid 1234

storapid                      [ Operation not supported by daemon ]

9 Legend

 • 

20.4K Posts

December 7th, 2013 13:00

don't worry about deamons ..if syminq does not show any symmetrix device you can't manage the array. You need to validate your zoning first, make sure you are at least zoned to an FA that has VCM device on it. Once that is done you will be able to create or provision at least 4 dedicated gatekeepers.

2 Intern

 • 

211 Posts

December 8th, 2013 18:00

Would you please let me know what command to list FA ports that has VMC device on it? and also list where gatekeepers located in the frame?

9 Legend

 • 

20.4K Posts

December 8th, 2013 18:00

symdev list -sid 123 | grep -i vcm

or on windows

symdev list -sid 123 | findstr /I vcm

then run symdev show -sid 123 #VCM

and look for what FA it's mapped to. Now obviuosly you need to run these commands from a host that has connectivity to DMX4. Typically VCM is mapped to all FAs in the box unless somenone specificially unmapped them.

Gateways are regular (2-way mirror) devices that are 3 cylinder in size, you can create them yourself.

symconfigure -sid 123 -cmd "create dev count=1,size=3,emulation=FBA,config=2-Way-Mir,disk_group=0" commit

2 Intern

 • 

211 Posts

December 9th, 2013 08:00

Hi there,

It seems nothing is easy here. I got nothing as the result of running the following command, although I can see lots of disks. this is a VMAX-1. What could I do next? Thanks!

symdev list -sid 123 | grep -i vcm

on the other Window server attaching to a DMX, I got the following:

>symdev list -sid 789 |  findstr /I vcm

The gatekeeper device (while using the Base Daemon) has an error (Please see the Log file)

9 Legend

 • 

20.4K Posts

December 9th, 2013 14:00

whichever server you are trying to use for symmetrix configuration work needs to be zoned to an FA with VCM device mapped to you. Have you verified that you are zoned to an FA with VCM device mapped to you. If yes, can you run syminq ?

2 Intern

 • 

211 Posts

December 9th, 2013 16:00

dynamox,

I am sorry, I have used two different servers, so, you may got confused. On this server, I can list EMC devices, but can not find VCM device by running symdev list -sid 123 | grep -i vcm. the following is the result of syminq:

# syminq

     Device              Product                   Device
--------------- --------------------------- ---------------------
Name     Type   Vendor    ID           Rev  Ser Num      Cap (KB)
--------------- --------------------------- ---------------------
/dev/sda        DELL      PERC H700    2.10 N/A         142737408
/dev/sdb GK     EMC       SYMMETRIX    5875 xxxxxxxx       2880
/dev/sdc R1     EMC       SYMMETRIX    5875 xxxxxxxx  565678080
/dev/sdd        EMC       SYMMETRIX    5875 xxxxxxx   35354880

9 Legend

 • 

20.4K Posts

December 10th, 2013 05:00

that's fine, at least on this one you have 1 gatekeeper (best practices need to have a least 4 if you are doing any significant symcli work). So what's your ultimate goal here, get the other server to manage this array ? If yes than perform these steps

1) zone that server to one or more FAs (if you are using PowerPath you can zone multiple FAs, PowerPath is gatekeeper aware, otherwise only zone one path)

2) if you don't have un-used gatekeepers (remember to never present gatekeepers to multiple hosts), create a couple.

3) map/mask them to your new management host

4) once you can see them on the host, run symgate define .... to define them as gatekeepers on the host, they will have a little GK next to them once you run that command.

2 Intern

 • 

211 Posts

December 13th, 2013 07:00

thanks for steps.

Why I can not see vcm device by running symdev list -sid 123 | grep -i vcm?

I can see one GK as the result of syminq.

What is difference btw GK and VCM DEVICE/VCMDB?

2 Intern

 • 

211 Posts

December 13th, 2013 07:00

I understand the following is the command to create more gatekeepers.

symconfigure -sid 123 -cmd "create gatekeeper count=6 emulation=FBA;" commit

should this command be run by server SA who has SE access, or by storage admin? Would this GK be dedicated to this server only?

So, if I have only one GK shown in syminq, does that mean we definitely only have one GK, are there any other commands to confirm? what could the impact be if we only have 1 GK?

what are those contents will be stored on gatekeepers?

Thank you!

No Events found!

Top