GATE KEEPER:

---------------
To manage DMX we have tool called ECC ( EMC Control Center, SMC and SYMCLI). Let
me first explain
what is gatekeeper and what is use?
To perform software operations on the Symmetrix, we use the low level SCSI comma
nd. To send SCSI commands to the Symmetrix, we need to open a device. We refer t
o the device we open as a gatekeeper. Symmetrix gatekeepers provide communicatio
n paths into the Symmetrix for external software monitoring and/or controlling t
he Symmetrix. There is nothing special about a gatekeeper, any host visible devi
ce can be used for this purpose. We do not actually write any data on this devic
e, nor do we read any date from this device. It is simply a SCSI target for our
special low level SCSI commands. We do perform I/O to these devices and this can
interfere with applications using the same device. This is why we always config
ure small devices (NO data is actually stored) and map them to hosts to be used
as "gatekeepers". Solutions Enabler will consider any device with 10 cylinders o
r less to be the preferred gatekeeper device.
Now you must have understood what is gatekeeper devices.
Let me explain more about uses like how many gatekeeper you want to present host
so there will be no performance impact.
A general recommendation for the number of gatekeepers for a single host with fe
w applications running is 8. However, a common rule of thumb is a minimum of 6.
For a host on which many applications running, 16 is recommended. A gatekeeper s
hould not be mapped/masked to more than one host.
Granular Recommendation (for Solutions Enabler) :
-----------------------------------------------
It is hard to recommend an exact number of gatekeepers required for a single hos
t. The number of gatekeeper's required depends on the specific host's configurat
ion and role. This is because it directly relates to performance, therefore it i
s a subjective number.
The following is a recommendation based upon a number of variables pertaining to
that specific host. At least 2 gatekeepers for simple Solutions Enabler command
s and 1 additional gatekeeper for each daemon or EMC Control Center Agent runnin
g on the host.
Granular Recommendation (for Control Center) :
----------------------------------------------
Two gatekeepers are required when the Storage Agent for Symmetrix is installed o
n the host, and two (total of four) additional gatekeepers are required when you
use Symmetrix Configure commands to manage the Symmetrix system. Each Symmetrix
system needs only two Symmetrix agents. The agents need to be installed on sepa
rate hosts. This is to provide for failover when the primary agent goes down for
maintenance (or failure).
Common Mapping Agent and host agents do not require a gatekeeper.
Note: SYMCLI scripts should not use gatekeepers assigned to ControlCenter; they
should have their own.
Gatekeepers are typically 6 cylinders or 2888 KB in Size. All gatekeeper type de
vices should be protected by either RAID-1 or RAID-S.
Hope this will help you in deciding number of gatekeeper to assign the host.Beca
use it is matter of performance.
-----------------------------------------PAGE BREAK-----------------------------
------------------
EMC Gatekeeper Devices
In this post I am explaining about the use of EMC gatekeeper devices.Most of you
already deal with gatekeeper devices as a storage admin.Lets have a close look
at gatekeeper device.
What is a gatekeeper device ?
-------------------------------
Storage management consoles like ECC or SMC would not be able to achieve much if
it were not able to communicate with Enginuity code running on the Symmetrix an
d access array internal structures. Gathering data on Symmetrix array properties
and status and controlling tasks such as array replication are essential compon
ents of Symmetrix storage management. Gatekeeper devices are used to facilitate
the special communication that controls the Symmetrix array for either requestin
g tasks be performed or retrieving status.In Common word,a gatekeeper is a carri
er of Symcli commands to storage arrays,ie,whenever we issue a symcli commands i
t will create syscalls which is used to retrieve the information from storage bo
xes.This syscalls are routed to storage arrange arrays through gatekeeper device
s.
Do I need to assign gatekeeper device to all host in my environment ?
---------------------------------------------------------------------
No need to assign gatekeeper devices all severs in your data center.As I discuss
earlier,the gatekeeper is used for storage management purpose.So you have to as
sign gatekeeper devices only to your management server.
How many Gatekeepers do I need?
--------------------------------
As per EMC,the answer is, Enough to perform all concurrent Symmetrix commands and
queries without running into a condition in which commands are delayed or rejec
ted for lack of a gatekeeper resource. Practically speaking, any server issuing c
ommands to a Symmetrix, physical or virtual, should have six Gatekeeper devices
uniquely available to it.
What is the standard size of a gatekeeper device ?
---------------------------------------------------
Gatekeepers require only a small amount of space, 3 MB (3 cyl) for Enginuity lev
els 57xx,58xx and higher(for DMX3,DMX4 and Vmax models), and 3 MB (6 cyl) for En
ginuity levels of 56xx and lower(All non DMX3,4 and Vmax). Users are encouraged
to not build Gatekeepers in larger sizes as the small size is used by Enginuity
to automatically identify and use devices as Gatekeepers. Devices under 8 MB hav
e the indication GK in syminq output. Gatekeeper devices must be mapped and mask
ed to single servers only and should not be shared across servers.
Can a gatekeeper device unprotected ?
---------------------------------------
Gatekeepers should be RAID protected in some way so if the device were to fail,
the syscall would be directed to the mirror of the failed device.Suggested RAID pr
otection is mirrored ie RAID 1
How to create gatekeeper devices ?
-----------------------------------
Gatekeeper device can be created using SMC and symcli
1. Create gatekeeper devices using Symmetrix management Console(SMC):
----------------------------------------------------------------------
Right-click the Symmetrix in question. Select the Configure menu and then select
Logical Device Creation.
Enter the amount of gatekeepers you want to create.
Fill out the form as follows:
Emulation: FBA
Type/Host: Open System
Size: 6/3 (please select 3 or 6 depends upon your array model)
Unit: Cylinders
Configuration: Mirrored-2
Commit the changes and mask the devices to your servers.
2.Create gatekeeper device using cli command line:
--------------------------------------------------
Create a text file and input the following:
create dev count=x, config=2-way-mir, emulation=FBA, size=6/3; (please select
6 or 3 depends upon your array model)
Save the file and run the following:
symconfigure -sid xxx -f filename.txt -v preview
symconfigure -sid xxx -f filename.txt -v prepare
symconfigure -sid xxx -f filename.txt -v commit
Once the change is committed mask the devices to your servers. Syminq commands
will automatically pick up these devices as gatekeeper
Can I share Gatekeepers across servers?
-----------------------------------------
Gatekeeper devices must be mapped and masked to single hosts only and should not
be shared for concurrent I/O across hosts.
Can I use thin device as gatekeeper ?
---------------------------------------
From solution enabler version 7.4 and with enginuity 5876 thin device can also b
e used as gatekeeper device
Can I use normal device as gatekeeper device ?
------------------------------------------------
If gatekeeper device with small size is not available,the system selects and use
s a data or system device as a Gatekeeper, applications on the application host
can be impacted!.It is strongly recommends that dedicated Gatekeepers be create
d and used. This is particularly important with Open Systems operation.
How to verify the existence of dedicated gatekeepers ?
------------------------------------------------------
To verify that there are dedicated gatekeepers available for use, run the follow
ing command:
]#stordaemon action storapid -cmd show -gk_stats
- See more at: http://www.emcsaninfo.com/2012/11/emc-gatekeeper-devices.html#sth
ash.ST553TlO.dpuf
----------------------------------------------PAGEBREAK-------------------------
------------------
Provisioning Gatekeepers to a Management Host

In this example, gatekeepers are provisioned to a management host that will moni
tor and manage the Symmetrix using Solutions Enabler. Best practice for assignin
g gatekeepers to hosts specifies that gatekeeper device be assigned on only a si
ngle front-end path.


Steps for provisioning storage:
-------------------------------
for simple configurations you can create a masking view for a single initiator o
n a single port with any number of devices using just one symaccess command...

After the masking view has been created, devices are available to the initiators
on the storage ports. Run host-specific commands to configure the devices to th
e host operating system.

Step 1 - Create a view and specify a view name, HBA pWWN, front-end port, and Sy
mmetrix volumes for the ------ first path.

the view is assigned a name by the user and that name is used for the initiator,
port, and storage groups. To display the HBA pWWNs and the ports that they are
zoned to:

# symaccess list hba

Identifier Physical Device Path Symmetrix ID Dir:P
---------------- -------------------------------- ------------ -----
10000000c9767816 c3t5000097208139918d0s2 000192601254 07E:0
10000000c9767817 c4t5000097208139959d0s2 000192601254 07F:1

To make gatekeepers 08F - 092 available on the first path (first HBA), do the fo
llowing:

# symaccess create view -name mgmtGKpath0 -wwn 10000000c9767816 -dirport 7E:0 de
vs 08F:092 -sid 1254
the view is assigned a name by the user and that name is used for the initiator,
port, and storage groups.



Step 2 - Create a view and specify a view name, HBA WWN, front-end port, and Sym
metrix volumes for the second path.

To make gatekeepers 093 096 available on the second path (2nd HBA), do the follo
wing:
# symaccess create view -name mgmtGKpath1 -wwn 10000000c9767817 -dirport 7F:1 de
vs 093:096 -sid 1254

devices are now available to the initiators on the storage ports. After the host
configures the devices, they are available to the operating system on both path
s:

# symaccess list view -sid 1254
Symmetrix ID : 000192601254
Masking View Name Initiator Group Port Group Storage Group
----------------- --------------- ------------ -------------------------
mgmtGKpath0 mgmtGKpath0 mgmtGKpath0 mgmtGKpath0
mgmtGKpath1 mgmtGKpath1 mgmtGKpath1 mgmtGKpath1

# syminq
Device Product Device
---------------------------- -------------------------- ---------------------
Name Type Vendor ID Rev SerNum Cap (KB)
---------------------------- ------------------------------------------------
/dev/rdsk/c3t50*8d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c3t50*8d1s2 GK EMC SYMMETRIX 5874 540008F000 5760
/dev/rdsk/c3t50*8d2s2 GK EMC SYMMETRIX 5874 5400090000 5760
/dev/rdsk/c3t50*8d3s2 GK EMC SYMMETRIX 5874 5400091000 5760
/dev/rdsk/c3t50*8d4s2 GK EMC SYMMETRIX 5874 5400092000 5760
/dev/rdsk/c4t50*9d0s2 GK EMC SYMMETRIX 5874 5400054000 5760
/dev/rdsk/c4t50*9d1s2 GK EMC SYMMETRIX 5874 5400093000 5760
/dev/rdsk/c4t50*9d2s2 GK EMC SYMMETRIX 5874 5400094000 5760
/dev/rdsk/c4t50*9d3s2 GK EMC SYMMETRIX 5874 5400095000 5760
/dev/rdsk/c4t50*9d4s2 GK EMC SYMMETRIX 5874 5400096000 5760
# symcfg discover

# symaccess show view mgmtGKpath0 -sid 1254
Symmetrix ID : 000192601254
Masking View Name : mgmtGKpath0
Initiator Group Name : mgmtGKpath0
Host Initiators
{
WWN : 10000000c9767816
}
Port Group Name : mgmtGKpath0
Director Identification
{
FA-7E:0
}
Storage Group Name : mgmtGKpath0
Sym Dev Host
Name Dir:P Physical Device Name Lun Attr Cap(MB)
------ ----- ----------------------- ---- ---- -------
008F 07E:0 c3t5000097208139918d1s* 1 5
0090 07E:0 c3t5000097208139918d2s* 2 5
0091 07E:0 c3t5000097208139918d3s* 3 5
0092 07E:0 c3t5000097208139918d4s* 4 5

# symaccess show view mgmtGKpath1 -sid 1254
Symmetrix ID : 000192601254
Masking View Name : mgmtGKpath1
Initiator Group Name : mgmtGKpath1
Host Initiators
{
WWN : 10000000c9767817
}
Port Group Name : mgmtGKpath1
Director Identification
{
FA-7F:1
}
Storage Group Name : mgmtGKpath1
Sym Dev Host
Name Dir:P Physical Device Name Lun Attr Cap(MB)
------ ----- ----------------------- ---- ---- -------
0093 07F:1 c4t5000097208139959d1s* 1 5
0094 07F:1 c4t5000097208139959d2s* 2 5
0095 07F:1 c4t5000097208139959d3s* 3 5
0096 07F:1 c4t5000097208139959d4s* 4 5