Unsolved
This post is more than 5 years old
1 Message
0
1416
September 26th, 2011 06:00
V-MAX SYMCLI---Need clarification.
I have a little query about symcli commands. Hope you can help out in a better way.
------------------------
1-Symcfg –sid 36 list –addr –avail -fa 7e –p 0---->it will show the avaialbe LUN# of the particular port
Symconfigure –sid 36 –cmd “map dev 20 to dir 7e:00, lun=41” commit -----> mapping a device to port with LUN# and I hope this will be visible in the host side.
So is it required any masking view for getting the LUN in the host side?
2-Is it required to use symmasking command if we are using masking views?
Thanks
Shaf.
No Events found!
Jill_M
86 Posts
0
September 26th, 2011 07:00
Hi Shaf,
The team is going to move this thread to the Support Forums community where your question can be addressed.
Kind regards,
Jill
RFritz11
2 Intern
•
244 Posts
0
September 26th, 2011 08:00
Hi Shaf,
We've moved your question to the Symmetrix Support Forum where it should receive a prompt response.
Kind regards,
Bob.
RobertDudley
2 Intern
•
448 Posts
0
September 26th, 2011 08:00
masking views are created using the symaccess command to create all the components.
Storage group
Port group
Initator group
Masking view
SKT2
2 Intern
•
1.3K Posts
0
September 26th, 2011 08:00
In VMAX we dont run any separate mapping and masking commands, the auto provisioning takes care of it.
Just follow the masking view concepts and crete a view and add the device to the concerned storage group
dynamox
9 Legend
•
20.4K Posts
0
September 26th, 2011 08:00
White Paper: Storage Provisioning: Transitioning to EMC Symmetrix V-Max Auto-provisioning Groups A Detailed Review
sauravrohilla
859 Posts
0
September 26th, 2011 08:00
HI Shaf,
Symconfigure –sid 36 –cmd “map dev 20 to dir 7e:00, lun=41” commit -----> mapping a device to port with LUN# and I hope this will be visible in the host side.
lun# in your command is not the lun# which is visible to the host. IN case of VMAX autoprovisioning, symmetrix will automatically use the least lun# available on the HBA, so you dont need to use lun offset or dynmaic lun addressing.
As SKT mentioned, use the autoprovisioning (masking view) concepts to provision storage to the host.
regards,
Saurabh
SKT2
2 Intern
•
1.3K Posts
0
September 26th, 2011 09:00
symsg -sg sgname add dev xxx
symaccess -name sgname -type storage add dev xxxx
did u try any of these?
dynamox
9 Legend
•
20.4K Posts
0
September 27th, 2011 08:00
not on AIX, hdisk devices will assume the name of how they were discovered. I have native hdisk32, PowerPath devices hdiskpower103. If you look on the array it's assigned to Host id 9.
dynamox
9 Legend
•
20.4K Posts
0
September 27th, 2011 08:00
i don't know about that, especially when you have dynamic lun masking in the picture. For example:
$ symmaskdb -sid 123 list devs -wwn 10000000c92df8b0
Symmetrix ID : 000290100123
Originator Port wwn : 10000000c92df8b0
User-generated Name : myhost/h1
Sym Dev LUN
Name Dir:P Physical Device Name VBUS TID SYMM HOST Attr Cap(MB)
------ ----- ----------------------- ---- --- ---- ---- ---- -------
0359 8A:1 Not Visible 0 0 3f 0 (M) 34526
035B 8A:1 Not Visible 0 0 40 1 (M) 34526
If you look at device 035B, it's mapped to FA address 40 (hex) but we are also using dynamic lun masking so it's actual LUN address is 1. Now when we look on the host in PowerPath we see this:
Pseudo name=hdiskpower10
Symmetrix ID=000290100123
Logical device ID=035B
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
0 fscsi0 hdisk24 FA 8aB active alive 0 0
as you can see, AIX has discovered this device with a native/power device that do not match arrays LUN address. Maybe in a brand new, pristine setup it will match ..but who has pristine environments ?