steps for map devices to FA ..confirm me..

Looks good so far.

If your host has multipathing (PowerPath, etc), don't forget to also map the device on the other FA ports.

The other thing you'll probably need to do is LUN masking. Depending on the Solutions Enabler version, this can be done in the symconfigure map command.

Alternatively use the symmask command (or ECC/SMC GUI) to do the job.

BR, Marc

Yes , when I run symmask list logins I found the vio is associated with FA ( 5A:1) too , other than 14B:1

Director Identification : FA-5B
Director Port : 1

User-generated Logged On
Identifier Type Node Name Port Name FCID In Fabric
---------------- ----- --------------------------------- ------ ------ ------
10000000c942517f Fibre VIO_1 SW1 611613 Yes Yes
50012482008acbc3 Fibre RPA1_HBA1_P0 SWT1 610e13 Yes Yes
50012482008ef2b3 Fibre RPA2_HBA1_P0 SWT1 611013 Yes Yes

and on vio we have powerpath.. actally we need space for an LPAR which takes disk space from vio..and on that LPAR has powerpath installed but powerpath commands are not working on that I don¿t know why see here

county22/root: / > lslpp -l | grep -i powerpath*
EMCpower.base 4.4.2.2 COMMITTED PowerPath Base Driver and
EMCpower.consistency_grp 4.4.2.2 COMMITTED PowerPath Consistency Group
EMCpower.hr 4.4.2.2 COMMITTED PowerPath HighRoad Extension
EMCpower.multi_path 4.4.2.2 COMMITTED PowerPath Multi_Pathing
EMCpower.multi_path_aa 4.4.2.2 COMMITTED PowerPath Multi_Pathing
EMCpower.multi_path_ap 4.4.2.2 COMMITTED PowerPath Multi_Pathing
4.4.2.2 COMMITTED PowerPath Multi_Pathin

county22/root: / > powermt display dev=all
county22/root: / >

Ok In either of the case i need to map the device to both 14B:1 & 5B:1 right ..because first the device need to seen by vio where powerpath is
present ? so I map that device to 5A:1 too ..all remaining steps are ok or I need to add any more steps for mapping part..

is the VIO zoned to 14B:1 ? Do you have other FA's on the same switch fabric as 14B:1 ...best practice would be to follow rule of 17 and connect your host to two FA's that combined are equal to 17. For example 5A:1 and 12A:1 ...or something of that nature. That will ensure that FA connected to the host reside in two different power zones on the DMX.

Once upon a time .. rule of 17 was in place to avoid issues (congestion/DU) with internal busses .. Now we don't have internal busses but we have powerzones .. But rule of 17 is still here .. forever ..

After I map I need to do run
symcfg discover
right.
masking :

symmask -sid XXXX ¿wwn XXX add devs XXX -dir 14b -p 1

after this I have to run
symmask refresh

right..one last question because before all this processes It¿s better to take VCMDB database backup right for that
if I am in /usr/symcli/bin path and if I run this command

symmaskdb -sid XXXX backup ¿file /tmp/emcfiles/vcmdbfile1.122007

this will keep the vcmdb database backup to that located path file right¿

thank you guys¿

well ...based on this ..VIO is already zoned and logged in to FA 14B:1, so yes you can go ahead and map your device to 14B:1 and only mask it to VIO, other systems will not see that device.

See the brief configuration..Here host for FA-14B:0 are connected to the same switch port SW2..so I am wonder , say if I map device to 14B:1 The Hosts
( downey2,downey3,downey1) which are attached to SW2 can also see the device or what & any problem ..do i need to check any more info here ..

Director Identification : FA-5B
Director Port : 0

User-generated Logged On
Identifier Type Node Name Port Name FCID In Fabric
---------------- ----- --------------------------------- ------ ------ ------
10000000c93212c8 Fibre downey1 SW2 631713 Yes Yes
10000000c9407e23 Fibre VIO_1 SW3 630e13 Yes Yes
5001248202cacbc3 Fibre RPA1_HBA1_P2 SWT3 630513 Yes Yes
5001248202cef2b3 Fibre RPA2_HBA1_P2 SWT3 631913 Yes Yes

Director Identification : FA-14B
Director Port : 1

User-generated Logged On
Identifier Type Node Name Port Name FCID In Fabric
---------------- ----- --------------------------------- ------ ------ ------
10000000c939629a Fibre server4 SW2 611013 Yes Yes
10000000c93aa711 Fibre server3 SW2 611713 Yes Yes
10000000c9407e1a Fibre VIO_1 SW2 611113 Yes Yes

Director Identification : FA-14B
Director Port : 0

User-generated Logged On
Identifier Type Node Name Port Name FCID In Fabric
---------------- ----- --------------------------------- ------ ------ ------
10000000c9346535 Fibre downey2 SW2 610b13 Yes Yes
10000000c9346556 Fibre downey3 SW2 610d13 Yes Yes


thank you..

Silly thing here ..
The map file file1 ( then in a text file file1 map dev 04EF to dir 14B:1 lun=079 )
Should be kept in usr/symcli/bin right because I execute command at that path otherwise if I have to export the Path then I can keep that file any where.. am I right??

thank you so much guys....

i learn lun masking today so glad for ur support

Usually people learn simple things at first and later learn hardest things .. You started with FrontEnd configuration issues, gatekeepers not willing to work as expected ... and now you are at masking, a "simple" task.. You are learning really fast !!
Congrats!!

Could you post "cat /home/pctech321/myfile" or the file1 we discussed


I am just want to make sure of the syntax on the config file..

scripts for this process no
but we are using scripts for SRDF process , EMC provided scripts for SRDF we run those manually if the host is recycled..otherwise those are running continuously like loop process establish , suspend , synchronize,split ..etc

i run commands at /usr/symcli/bin if i want to export path i use below command
but today i didn't export the path all commands i run at /usr/symcli/bin path

export PATH=$PATH:/usr/symcli/bin

thank you...

do you have some kind of scripts that you are using ..it's really strange that your executables keep getting corrupted like that. Are you still running your commands from /usr/symcli/bin or did you export PATH correctly.

ok here is the syntax of file
more /home/pctech321/myfile

map dev 04EF to dir 14B:1, lun=079;

...guys today i map & mask the 2-way mirror 5MB device to the some other host where symcli is installed , everything if fine after all emc_cfgmgr process i found the new device as (lsdev -Cc disk ) hdisk30 and even sympd list shows me the new device

/dev/rhdisk30 0037 13A:1 16C:D2 2-Way Mir N/Grp'd RW 5

i am happy that i done successful this process but strange thing is the symdev commands are not working and symdev file showing size 0 as like same syminq of my previous thread both syminq , symdev showing with size 0.. i didn't run any manipulation symdev commands see here

-r-xr-xr-x 1 root system 0 Dec 26 09:41 symdev

it saying that one is modified today itself ..

whats the solution ??
New S.E