UNSOLVED
M
MaximUnited
111 Posts
0
3197
May 13th, 2008 04:00
"symcfg list -address -available" lists unsorted addresses
Hey again,
I think I found another bug
Output from "symcfg list -address -available" command:
root@host:/# symcfg list -address -available -sid xxx -dir 10b -p 0
Symmetrix ID: xxxxxxxxxxxx
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-10B 10B 0 - AVAILABLE 0 00 000 *
01CC Not Visible (M) 0 04 007
- AVAILABLE 0 01 000 *
01D2 Not Visible (M) 0 05 000
01D6 Not Visible (M) 0 05 001
01DA Not Visible (M) 0 05 002
01DE Not Visible (M) 0 05 003
01E2 Not Visible (M) 0 05 004
01E6 Not Visible (M) 0 05 005
.... - - - ....
Notice that Vbus0 Target0 Lun0, then Vbus0 Target4 Lun7 and Vbus0 Target0 Lun1
Tested from different servers locally and remotely attached symms. Tested with both symcli 6.5.0.0 and 6.4.3.0. Same thing is using '-fa' option instead of '-dir'.
Unfortunately, I forgot to test it without the '-available' option.
Now, those addresses are no longer available, since I had to map some devices there.
I only encountered this on this specific FA.
Thanks,
Maxim.
I think I found another bug
Output from "symcfg list -address -available" command:
root@host:/# symcfg list -address -available -sid xxx -dir 10b -p 0
Symmetrix ID: xxxxxxxxxxxx
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-10B 10B 0 - AVAILABLE 0 00 000 *
01CC Not Visible (M) 0 04 007
- AVAILABLE 0 01 000 *
01D2 Not Visible (M) 0 05 000
01D6 Not Visible (M) 0 05 001
01DA Not Visible (M) 0 05 002
01DE Not Visible (M) 0 05 003
01E2 Not Visible (M) 0 05 004
01E6 Not Visible (M) 0 05 005
.... - - - ....
Notice that Vbus0 Target0 Lun0, then Vbus0 Target4 Lun7 and Vbus0 Target0 Lun1
Tested from different servers locally and remotely attached symms. Tested with both symcli 6.5.0.0 and 6.4.3.0. Same thing is using '-fa' option instead of '-dir'.
Unfortunately, I forgot to test it without the '-available' option.
Now, those addresses are no longer available, since I had to map some devices there.
I only encountered this on this specific FA.
Thanks,
Maxim.
1170
0
Posted May 13th, 2008 05:00
Sorry. I thought it was obvious. I definitely run symcfg discover before all those querying. Especially if one of the servers has the Symmetrix+SDM agent for ECC.
And I'm pretty sure it always sorts the LUNs # instead of Device #.
Here's the more devices from same director:
0294 Not Visible (M) 0 0B 000
0298 Not Visible (M) 0 0B 001
029C Not Visible (M) 0 0B 002
0787 Not Visible 0 0B 003
0788 Not Visible 0 0B 004
0789 Not Visible 0 0B 005
- AVAILABLE 0 0B 006 *
078D Not Visible 0 0C 001
078E Not Visible 0 0C 002
04CC Not Visible (M) 0 0C 003
04D2 Not Visible (M) 0 0C 004
And did manage to get the output from same command without the '-available' option:
root@tmapprd1:/ # symcfg list -add -dir 10b -p 0 -sid xxx
Symmetrix ID: xxxxxxxxxxxx
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-10B 10B 0 01CC Not Visible (M) 0 04 007
01D2 Not Visible (M) 0 05 000
01D6 Not Visible (M) 0 05 001
01DA Not Visible (M) 0 05 002
01DE Not Visible (M) 0 05 003
.... - - - ....1170
0
Posted May 13th, 2008 05:00
Hmmm I suspect I'll have a busy day tomorrow ..
Unfortunatly I don't have any hpux port available (so no vbusses to deal with) ... But I'll try to play with an unused port ..
Cheers .. and see you tomorrow.
-s-
PS it looks like you spend a lot of time running symcli commands with the least used options .. isn't it ??1170
0
Posted May 13th, 2008 06:00
Marc unfortunatly I can't run tests 'till tomorrow .. And since this user already reported a bug, I do take his posts VERY seriously!!
I've learned the hard way that he isn't a beginner ..
Marc if you want we can share our findings on this particular issue and report them back to Steve Giampa.1170
0
Posted May 13th, 2008 06:00
You're right, I take it back. The output should be sorted by LUN# and the sort order in your first output is very strange.
Sounds as if Stefano is on the case though...!
By the way, if you post your output within "[ code]" and "[ /code]" tags (without the spaces & quotes), it will display in a fixed width font and therefore look more readable.
eg (from one of my boxes)Director Device Name Attr Address ---------------------- ----------------------------- ---- -------------- Ident Symbolic Port Sym Physical VBUS TID LUN ------ -------- ---- ---- ----------------------- ---- --- --- FA-9C 09C 0 02AA /dev/rdsk/c1t50d0s2 VCM 0 00 000 02C3 /dev/rdsk/emcpower0c 0 00 001 02C4 /dev/rdsk/emcpower1c 0 00 002 02C5 Not Visible 0 00 003 02C6 Not Visible 0 00 004 02FA /dev/rdsk/emcpower2c (M) 0 00 005 02FF /dev/rdsk/emcpower3c (M) 0 00 006 0304 /dev/rdsk/emcpower4c (M) 0 00 007 0309 /dev/rdsk/emcpower5c (M) 0 00 008 - AVAILABLE 0 00 009 * 00FC /dev/rdsk/emcpower6c 0 00 0F0 00FD /dev/rdsk/emcpower7c 0 00 0F1 - AVAILABLE 0 00 0F2 *
Message was edited by:
MarcT
Last edit, I promise!1170
0
Posted May 13th, 2008 07:00
You would probably have boring days without me
Actually I always use this command, since I hate doing mapping with ECC. Too long.
And I've written quite a nice script that creates a file for symconfigure (mapping).
But it's the first time I encounter that "bug".
P.S. I'm playing today with the symstat command. So this is kinda a heads-up
Maxim.1170
0
Posted May 14th, 2008 08:00
Right now I'm mapping some devices to a brand-new HPUX port
I'll be able to run some tests soon ..
-s-1170
0
Posted May 14th, 2008 08:00
Output from a working symcli (forgive if I'm still using 5.5) :
clst02t/root> symcfg -sid 022 -sa 1d -p 0 -address -available list Symmetrix ID: 000xxxx00022 Director Device Name Attr Address ---------------------- ----------------------------- ---- -------------- Ident Symbolic Port Sym Physical VBUS TID LUN ------ -------- ---- ---- ----------------------- ---- --- --- FA-1D 01D 0 - AVAILABLE 0 0 000 * 0617 Not Visible 0 4 007 - AVAILABLE 0 4 008 * 0618 Not Visible 0 5 000 0619 Not Visible 0 5 001 061A Not Visible 0 5 002 - AVAILABLE 0 5 003 * 060E Not Visible VCM 0 E 000 - AVAILABLE 0 E 001 * Legend for Available address: (*): The VBUS, TID, LUN address values represent a gap in the address assignments or are the next available address in the run clst02t/root> symcli Symmetrix Command Line Interface (SYMCLI) Version V5.5.0.0 (Edit Level: 557) built with SYMAPI Version V5.5.0.0 (Edit Level: 557)
And now output from a recent version ...clst01t/root> symcfg -sa 01D -p 0 -address -available list Symmetrix ID: 000xxxx00022 (Local) Director Device Name Attr Address ---------------------- ----------------------------- ---- -------------- Ident Symbolic Port Sym Physical VBUS TID LUN ------ -------- ---- ---- ----------------------- ---- --- --- FA-1D 01D 0 - AVAILABLE 0 00 000 * 0617 Not Visible 0 04 007 - AVAILABLE 0 01 000 * 0618 Not Visible 0 05 000 0619 Not Visible 0 05 001 061A Not Visible 0 05 002 - AVAILABLE 0 05 003 * 060E Not Visible VCM 0 0E 000 - AVAILABLE 0 0E 001 * Total ---- Mapped Devices: 5 Including Metamembers: 5 Available Addresses: 2038 (s) Legend for Available address: (*): The VBUS, TID, LUN address values represent a gap in the address assignments or are the next available address in the run (s): The Available Addresses for a director are shared among its ports (shared) clst01t/root> symcli Symmetrix Command Line Interface (SYMCLI) Version V6.5.0.0 (Edit Level: 872) built with SYMAPI Version V6.5.0.0 (Edit Level: 872)
Maybe it's not a bug .. but it's an undocumented feature .. However the strange behaviour is CONFIRMED1170
0
Posted May 14th, 2008 11:00
As someone may have noticed, even S.E. 5.5 output have a strange "bug" .. After target=4, lun=7 it reports as available target=4, lun=8 (but it's illegal since lun number for hpux can go from 0 to 7
Tomorrow I'll run more tests with S.E. 6.4 and hopefully even other versions.363
0
Posted June 23rd, 2008 06:00
Last update on this thread .. Fix for this issue is scheduled with Solution Enabler 6.5.2 .. Check the release notes and enjoy the fun when 6.5.2 will go live !!
MarcT2
2 Intern
•
131 Posts
1170
0
Posted May 13th, 2008 04:00
It's advisable to run this before querying configuration information to ensure you get the current information.
The data is sorted by the Symm volume#, not the LUN#.