symmaskdb list no_assignment - not showing correct output..

Can you please show an example of wrong output from symmaskdb command ??

Command:: sudo symmaskdb -sid 4199 list no_asignment | grep -v -i id|grep -v -i port |grep -v assigned |grep . |sort |uniq |grep 762
Output:: 762

When I check the assignment, it is assigned few hbas.

$ sudo symmaskdb -sid 4199 -dev 762 list assignment

Symmetrix ID : 00000000xxxx

Device Identifier Type Dir:P
------ ---------------- ----- ----------------
0762 10000000c96daa05 FIBRE FA-7A:1
10000000c9711684 FIBRE FA-10A:1
10000000c9708aab FIBRE FA-7B:1
10000000c96dbc8e FIBRE FA-10B:1

Message was edited by: Edited the system ID.
KCSCP

AFAIK there isn't a single command that can answer your question.

I guess you have to build a script that collects a list of mapped devices (on any port) and a list of masked devices (again on any port).
The difference (fgrep -vf in unix terms) is the answer to your question.

The long command line you posted doesn't take into account the fact that symmaskdb will list unassigned devices from every FA port.

Probably device 762 is mapped (and not masked) on other ports (and not only 7a:1, 7b:1, 10a:1, 10b:1). Can you please paste output of "symdev -sid 4199 show 762" ??

Thankyou and here is the output of symdev (copied a part of it)

Front Director Paths (8):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 07A:1 RW 000 00 097 N/A
Not Visible N/A FA 10A:1 RW 000 00 097 N/A
Not Visible N/A FA 07B:1 RW 000 00 097 N/A
Not Visible N/A FA 08B:0 RW 000 00 097 N/A
Not Visible N/A FA 08B:1 RW 000 00 097 N/A
Not Visible N/A FA 09B:0 RW 000 00 097 N/A
Not Visible N/A FA 09B:1 RW 000 00 097 N/A
Not Visible N/A FA 10B:1 RW 000 00 097 N/A
}


what is the best command in symcli to findout all the luns which are not masked but mapped to FAs?

Device mapped but not masked to host.

symmaskdb list no_assignment

FDC, were the reply's to your post able to answer your questions? If so, please mark the helpful and correct posts and also mark the thread as answered. Doing so helps others identify what posts were the most useful.

MikeMac,

i understand that you are trying to get threads marked as answered but it marks some many posts that have not changed since April as having new content ..that it generates more confusion than helps.

Not to gang up on you or anything MikeMac, but I have to agree with dynamox on this. I was off on vacation for a while and when I came back there were pages and pages of updated threads. It takes a while to work through that to make sure I'm not missing anything important.

I understand your concern, and that is why I only went back as far as I did trying to get some closure on questions. In the future, I won't go back as far.

Vacation ?? I forgot I had a "V" section in my dictionary !!!

Welcome back Allen.

Vacation is a "relative" term Stefano... in this case literally. I spent a week out of the office with my 4 year old son (out of school for the week) and my father (who was visiting for the week).

Sort of a vacation, and sort of not

This week is actually going to be more of a vacation... I'm down in Orlando for EMC World. And if you have even been, you'll know that this isn't really much of a vacation either. It's well worth it, but exhausting in it's own way. I mean really! How many after hours partner sponsored parties can you attend in one evening. You just have to set limits and stick to them

I actually made 2 scripts for this.
First one does 'symmask list no_assign' and does 'symmask list assign -dev' on every device found. Whichever device is not masked to any host is marked as free and is sent to a unmap configuration file for later use. (The script also checks that devices not a Clone nor SRDF nor a VCM device).

The second one is pretty much like the first, except it checks each FA at a time. Meaning it finds devices which are unmasked per FA and send it to the unmap config file. This one takes a bit longer time to run.