i have a database issue here ..i try to find out devices attached to one specific
FA ..i run
symdev list -sid XXX -sa 4C -p 1
-------------------------------
0759 Not Visible 4C:1 01A:D3 RAID-5 N/Grp'd RW 9281
------------------------------
and for port 0
symdev list -sid XXX -sa 4C -p 0
------------------------------
0759 Not Visible 4C:1 01A:D3 RAID-5 N/Grp'd RW 9281
------------------------------
but the strange thing is when i run symmaskdb list database , i didnot seen that device is attached to 4C -p 1 and even host list capacity didn't showing me that the device attached to 4C:1 , actually that device is attached to host octo1
see here..
octo1/root: /tmp > symmaskdb -host octo1 list capacity
Symmetrix ID : XXXXXXX
Host Name : octo1
Identifiers Found : XXXX
i just copied FA related data ...... octor1/root:/tmp>symdev show -sid XXX 0759
-------snipped -----
Front Director Paths (2): { ---------------------------------------------------------------------- POWERPATH DIRECTOR PORT LUN --------- ---------- ---- -------- --------- PdevName Type Type Num Sts VBUS TID SYMM Host ---------------------------------------------------------------------- Not Visible N/A FA 4C:0 RW 000 00 05A N/A Not Visible N/A FA 4D:1 RW 000 00 05A N/A }
------------------snipped---------
octor1/root:/tmp>symmaskdb -sid XXX -dev 0759 list assignment
i am curious ..if we attach a lun to unix we need to run emc-cfg or cfgmgr to recognize that lun ..what about windows..what they need to run to see new devices ...
thank you,
-Pctech
i typically start diskpart and type rescan ..or you can go to Disk Management and select "Rescan"
this is a silly question ..but i will ask anyway ..are you specifying correct SID id when you are running symdev list ? Just wanted to make sure you are not getting output from another symm that has the same device on it.
yes.. the database (symmaskdb ) related commands showing its not mapped and masked to host but device related commands ( symdev ) showing its mapped to 4C:1 .. i run symcfg discover now, still same results .. this problem arised because we assgign a lun to windows box , and windows guys unable to recongnise that lun ...funny thing is not just this 0749 that box already has 2 more luns from DMX , i check the those devices too, those are same as like this new 0749 device i mean same configuration ..when i run for other device 045A ( which is attach to same box ) symdev list -sid XXX -sa 4C -p 1 symdev list -sid XXX -sa 4C -p 0
it giving the same results as like 0749 ,but those are good with that box
dynamox
11 Legend
•
20419 Posts
•
87439 Points
1009
0
Posted February 7th, 2008 04:00