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

Symmetrix ID : XXXXXXXXXX

Device Identifier Type Dir:P
------ ---------------- ----- ----------------
0759 XXXXXX FIBRE FA-4C:0

i snipped first output mostly, except FA info ..if u want all i can post it

thank you.....

so it probably means that the device is mapped but not masked to any hosts.

Oops ..ignore last comment.

Can you run symdev show -sid XXX 0759 and then

symmaskdb -sid XXX -dev 0759 list assignments

and post output

hey dynamox..

i am sorry..
i just copied the wrong line ..
its
0759 Not Visible 4C:0 01A:D3 RAID-5 N/Grp'd RW 9281

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.

hahaaaaaaaaaaaaaaa.

man ..
ok, we have just one symmetrix ..if we have two there may be a chance .

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

thank you..

i don't see that device being mapped to 4C:1 nor masked to 4C:1 ...so what makes you think it's mapped/masked to 4C:1 ?

have you run symcfg discover ?

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

this is strange ..if device was really mapped to 4C:1 ..than we would see it with symdev show command.

I am also surprised to see that when you run symdev list -sid XXX -sa 4C -p 0 ...it shows 4C:1 ...it should show 4C:0



symdev list -sid XXX -sa 4C -p 0
------------------------------
0759 Not Visible 4C:1 01A:D3 RAID-5 N/Grp'd RW 9281

had to ask man ..i was pulling my hair one time seeing weird stuff ..just to realize i was looking at another frame .

let's try another way: symcfg -sid XXX list -dir 4c -p 1 -address

do you see that device ?

Please forgive me if I jump in .. But please let me tell you what I understood from this thread...

You have a device (0749) that is mapped on 2 ports (4C:0 and 4C:1) as per "symdev show" command ..
Your host can see the device via 4C:0 (as per "syminq" output) and from "symmask list assignments" you can see that there is a masking for your host on 4C:0.

What I can't really understand is why you are saying that symmaskdb is telling you that the device isn't mapped .. In fact symmaskdb will NEVER tell you if a device is mapped .. It's up to symdev to show you if the device is mapped.

Could you please correct me if I didn't understand your problem

-s-

ThX for the correction .. I was almost sure that I was missing something .. Now I know what I missed

It's a long thread and I'm still out of office .. I gave a fast read at the thread but wasn't able to find the main issue .. ThX again ..