This post is more than 5 years old
92 Posts
0
1492
Database list issue
hi...
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
Device Cap(MB) Attr Dir:P
------ ------- ---- ----
---snipped -------
0759 9281 4C:0
-----------------------------
octo1/root: /tmp >symmaskdb list database
------------------snipped---------
Director Identification : FA-4C
Director Port : 1
User-generated
Identifier Type Node Name Port Name Devices
---------------------------------
XXXXXXX Fibre octo1 Direct None
------------------------
-----------snipped ------------
any help..
thank you..
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
Device Cap(MB) Attr Dir:P
------ ------- ---- ----
---snipped -------
0759 9281 4C:0
-----------------------------
octo1/root: /tmp >symmaskdb list database
------------------snipped---------
Director Identification : FA-4C
Director Port : 1
User-generated
Identifier Type Node Name Port Name Devices
---------------------------------
XXXXXXX Fibre octo1 Direct None
------------------------
-----------snipped ------------
any help..
thank you..
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 7th, 2008 04:00
pctech321
92 Posts
0
February 6th, 2008 12:00
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.....
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 12:00
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 12:00
Can you run symdev show -sid XXX 0759 and then
symmaskdb -sid XXX -dev 0759 list assignments
and post output
pctech321
92 Posts
0
February 6th, 2008 13:00
i am sorry..
i just copied the wrong line ..
its
0759 Not Visible 4C:0 01A:D3 RAID-5 N/Grp'd RW 9281
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 13:00
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"
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 13:00
pctech321
92 Posts
0
February 6th, 2008 13:00
man ..
ok, we have just one symmetrix ..if we have two there may be a chance .
pctech321
92 Posts
0
February 6th, 2008 13:00
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..
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 13:00
have you run symcfg discover ?
pctech321
92 Posts
0
February 6th, 2008 13:00
to recognize that lun ..what about windows..what they need to run to see new devices ...
thank you,
-Pctech
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 13:00
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
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
February 6th, 2008 19:00
let's try another way: symcfg -sid XXX list -dir 4c -p 1 -address
do you see that device ?
xe2sdc
2.8K Posts
0
February 7th, 2008 02:00
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 ..
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
Could you please correct me if I didn't understand your problem
-s-
xe2sdc
2.8K Posts
0
February 7th, 2008 04:00
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 ..