This post is more than 5 years old
76 Posts
0
2721
Determine FC drives vs. SATA drives
Is there a command from the symcli that will list all devices (assigned and unassigned) on the DMX3 and DMX4 that will show which devices are Fibre Channel drives and which drives are SATA drives?
Thanks
-mark
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 13th, 2012 07:00
yep,
you can also run "symdisk show 16B:D5 -sid 123" and look for device speed string (Speed (RPM) )
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 13th, 2012 07:00
if you are talking about symdev, there is a command but its only available on VMAX:
symdev list -sid 123 -technology
markdf
76 Posts
0
June 13th, 2012 07:00
Total Disk Capacity (MB) : 286102
Actual Disk Capacity (MB) : 286102
Hypers (25):
{
--- ---- ---------------- ---- ------------- --- --- -------------- --------
}
Awesome.. now my last question is, does that apply to all the disks, meaning, how did you determine the range "16B:D5". We have four Symmetrix's (one DMX-3 and three DMX-4s), each with different capacities and number of disks. This one reports it has 36 disks in it, but that command seems to have only shown 25 of them (if I'm reading it right).
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
June 13th, 2012 07:00
symdisk list ?
markdf
76 Posts
0
June 13th, 2012 07:00
./symdev list -sid 92 -technology
'-technology': Illegal option.
Yeah, that didn't work. So basically, if they are 300GB they are FC and if they are 1TB or more, they are SATA?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 13th, 2012 07:00
300G - those are FC drives
Sam Claret
86 Posts
0
June 13th, 2012 07:00
Unfortunately the ‘Technology’ and ‘Form Factor’ fields for the SE v7.3 symdisk command are only available on a VMax. They are not available for DMX.
Sam Claret
Technical Support Engineer III
Worldwide Technical Support – OSAPI Windows
Office Hours: Rotating shift, 7AM – 4PM GMT
Office #: +353 21 494 5981
markdf
76 Posts
0
June 13th, 2012 07:00
Thanks, that lists the actual disks, but still doesn't tell me if they are FC or SATA:
------ ---- --- --- ---------- ---------- ---- ---------- ---------- ----------
I googled for a SEAGATE T300R10 and actually got no results (which I thought was nearly impossible with Google )
Edit: Sorry, this answer was for "symdisk list".. just saw your second reply after I submitted this. I'll try that one.
markdf
76 Posts
0
June 13th, 2012 08:00
Okay, thank you! And one final question (which probably should go in another topic/thread), but one of our DMX-4s is showing only two devices available (71GB total):
Symmetrix ID:xxxxxxxxxx78
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
001B Not Visible ???:? 16A:DA 2-Way Mir N/Grp'd RW 3
001C Not Visible ???:? 01A:CA 2-Way Mir N/Grp'd RW 3
001D Not Visible ???:? 16A:DE 2-Way Mir N/Grp'd RW 3
001E Not Visible ???:? 16A:CB 2-Way Mir N/Grp'd RW 3
001F Not Visible ???:? 16A:D8 2-Way Mir N/Grp'd RW 3
0020 Not Visible ???:? 01A:C8 2-Way Mir N/Grp'd RW 3
0021 Not Visible ???:? 01A:D9 2-Way Mir N/Grp'd RW 3
0022 Not Visible ???:? 16A:C9 2-Way Mir N/Grp'd RW 3
008F Not Visible ???:? 01B:C1 RAID-5 N/Grp'd RW 35723
0090 Not Visible ???:? 16B:C0 RAID-5 N/Grp'd RW 35723
But yet, when I look at the drives using the "symdev list", there appears to be a few TB free (when adding up the Capacity Free column):
------ ---- --- --- ---------- ---------- ---- ---------- ---------- ----------
Is this actually the case, there is space available, I just need to activate it by creating new devices from the free space on the drives? And if so, what's the quick command to create more RAID-5 35723MB devices? Yeah, I know, RTFM, but hopefully posting here would be a bit quicker.
Thanks!
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 13th, 2012 08:00
that's not a range, that's just one physical disk. Those 25 devices that you are seeing, those are symdev devices that reside on that physical spindle.
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
June 13th, 2012 09:00
i am not sure what command you ran to list available device but i run " symdev list -sid 123 -noport | grep N/Grp". This will list all devices that are not mapped and not part of any device groups.
you are right, it's possible that you have enought raw space in the disk group to create new devices. You can run something like this to tell you how much raw capacity is available in one particular disk group
expr `symdisk list -sid 123 -disk_group 0 |awk '{a += $9};END{print a}'` / 1024
make sure to substitude 0 for your disk group. Let's say you see 5 TB, just because it says 5TB does not mean you can get 5TB worth of symdevs. This raw space has to satisfy many checks and balances before it creates you devices (IE: make sure RAD-5 members do not share the same physical spindle, DA, etc). What i typicall do is run a symconfigure command in prepare mode just to see how many symdevs it will let me create, for example:
symconfigure -sid 123 -cmd "create dev count=230,size=18414,emulation=FBA,config=RAID-5,data_member_count=7,disk_group=0" prepare
so in this example i am asking symconfigure to tell me if i can create 230 devices of 18414 cylinders (17263 MB) in size. If it runs and says "cannot satisfy raid requirements" or something of that nature, i lower that count number and try again"
markdf
76 Posts
0
June 13th, 2012 10:00
Eh, I'm confused now.
Here's the steps (w/ commands):
# ./symdev -sid 78 list -noport
Symmetrix ID: xxxxxxxxxx78
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
001B Not Visible ???:? 16A:DA 2-Way Mir N/Grp'd RW 3
001C Not Visible ???:? 01A:CA 2-Way Mir N/Grp'd RW 3
001D Not Visible ???:? 16A:DE 2-Way Mir N/Grp'd RW 3
001E Not Visible ???:? 16A:CB 2-Way Mir N/Grp'd RW 3
001F Not Visible ???:? 16A:D8 2-Way Mir N/Grp'd RW 3
0020 Not Visible ???:? 01A:C8 2-Way Mir N/Grp'd RW 3
0021 Not Visible ???:? 01A:D9 2-Way Mir N/Grp'd RW 3
0022 Not Visible ???:? 16A:C9 2-Way Mir N/Grp'd RW 3
008F Not Visible ???:? 01B:C1 RAID-5 N/Grp'd RW 35723
0090 Not Visible ???:? 16B:C0 RAID-5 N/Grp'd RW 35723
Okay, looks like I only have two devices available, each 35723MB. Now, I look to see what is free on the DMX4:
# ./symconfigure -sid 78 list -freespace -units CYLINDERS
Symmetrix ID: xxxxxxxxx78
Emulation Formatted Unformatted
(Cyl) (Cyl)
--------------------- --------- -----------
FBA 12155024 0
IBM_FBA 12155024 0
UNISYS_FBA 12155024 0
Looks to me that I can still create devices, though I'm not sure on cylinder calculation sizes, but surely if I use your example (to create a 17263MB device, I would use 18414 cylinders out of 12155024 free), it can be done. Here's the diskgroups:
# ./symdisk -sid 78 list -by_diskgroup
Symmetrix ID : xxxxxxxxx78
Disks Selected : 52
Disk Group : 0
Disk Group Name : DISK_GROUP_000
Technology : N/A
Speed (RPM) : N/A
Capacity(MB)
Ident Symb Int TID Vendor Type Hypr Total Free Actual
------ ---- --- --- ---------- ---------- ---- ---------- ---------- ----------
DF-1A 01A C E SEAGATE T300R10 0 0 0 286102
DF-1A 01A D B SATASEGT N01TMOO 0 0 0 953870
DF-1B 01B D E SATASEGT N01TMOO 0 0 0 953870
DF-16B 16B C E SEAGATE T300R10 0 0 0 286102
---------- ---------- ----------
Total 0 0 2479944
Disk Group : 1
Disk Group Name : DISK_GROUP_001
Technology : N/A
Speed (RPM) : 10000
Capacity(MB)
Ident Symb Int TID Vendor Type Hypr Total Free Actual
------ ---- --- --- ---------- ---------- ---- ---------- ---------- ----------
DF-1A 01A C 0 SEAGATE T300R10 5 286102 233299 286102
DF-1A 01A C 2 SEAGATE T300R10 6 286102 233293 286102
DF-1A 01A C 4 SEAGATE T300R10 6 286102 236331 286102
DF-1A 01A C 6 SEAGATE T300R10 4 286102 244576 286102
DF-1A 01A D 1 SEAGATE T300R10 5 286102 233299 286102
DF-1A 01A D 3 SEAGATE T300R10 5 286102 233299 286102
DF-1A 01A D 5 SEAGATE T300R10 7 286102 224411 286102
DF-1A 01A D 7 SEAGATE T300R10 5 286102 217534 286102
DF-16A 16A C 1 SEAGATE T300R10 5 286102 233299 286102
DF-16A 16A C 3 SEAGATE T300R10 4 286102 245220 286102
DF-16A 16A C 5 SEAGATE T300R10 7 286102 226488 286102
DF-16A 16A C 7 SEAGATE T300R10 6 286102 226782 286102
DF-16A 16A D 0 SEAGATE T300R10 5 286102 243138 286102
DF-16A 16A D 2 SEAGATE T300R10 6 286102 233293 286102
DF-16A 16A D 4 SEAGATE T300R10 7 286102 226776 286102
DF-16A 16A D 6 SEAGATE T300R10 5 286102 232656 286102
DF-1B 01B C 1 SEAGATE T300R10 5 286102 243138 286102
DF-1B 01B C 3 SEAGATE T300R10 6 286102 233293 286102
DF-1B 01B C 5 SEAGATE T300R10 7 286102 226776 286102
DF-1B 01B C 7 SEAGATE T300R10 5 286102 232656 286102
DF-1B 01B D 0 SEAGATE T300R10 5 286102 233299 286102
DF-1B 01B D 2 SEAGATE T300R10 4 286102 245220 286102
DF-1B 01B D 4 SEAGATE T300R10 7 286102 226488 286102
DF-1B 01B D 6 SEAGATE T300R10 6 286102 226782 286102
DF-16B 16B C 0 SEAGATE T300R10 5 286102 233299 286102
DF-16B 16B C 2 SEAGATE T300R10 5 286102 233299 286102
DF-16B 16B C 4 SEAGATE T300R10 7 286102 224411 286102
DF-16B 16B C 6 SEAGATE T300R10 5 286102 217534 286102
DF-16B 16B D 1 SEAGATE T300R10 5 286102 233299 286102
DF-16B 16B D 3 SEAGATE T300R10 6 286102 233293 286102
DF-16B 16B D 5 SEAGATE T300R10 6 286102 236331 286102
DF-16B 16B D 7 SEAGATE T300R10 4 286102 244576 286102
---------- ---------- ----------
Total 9155273 7447400 9155273
Disk Group : 2
Disk Group Name : DISK_GROUP_002
Technology : N/A
Speed (RPM) : 7200
Capacity(MB)
Ident Symb Int TID Vendor Type Hypr Total Free Actual
------ ---- --- --- ---------- ---------- ---- ---------- ---------- ----------
DF-1A 01A C 8 SATASEGT N01TMOO 69 953870 250293 953870
DF-1A 01A C A SATASEGT N01TMOO 70 953870 238373 953870
DF-1A 01A D 9 SATASEGT N01TMOO 69 953870 250293 953870
DF-16A 16A C 9 SATASEGT N01TMOO 69 953870 250293 953870
DF-16A 16A C B SATASEGT N01TMOO 69 953870 250293 953870
DF-16A 16A D 8 SATASEGT N01TMOO 69 953870 250293 953870
DF-16A 16A D A SATASEGT N01TMOO 70 953870 238373 953870
DF-16A 16A D E SATASEGT N01TMOO 69 953870 250293 953870
DF-1B 01B C 9 SATASEGT N01TMOO 69 953870 250293 953870
DF-1B 01B C B SATASEGT N01TMOO 70 953870 238373 953870
DF-1B 01B D 8 SATASEGT N01TMOO 69 953870 250293 953870
DF-1B 01B D A SATASEGT N01TMOO 69 953870 250293 953870
DF-16B 16B C 8 SATASEGT N01TMOO 69 953870 250293 953870
DF-16B 16B C A SATAHGST N01THGK 69 953870 250293 953870
DF-16B 16B D 9 SATASEGT N01TMOO 69 953870 250293 953870
DF-16B 16B D B SATASEGT N01TMOO 70 953870 238373 953870
---------- ---------- ----------
Total 15261915 3957008 15261915
So, I want to create a 17263MB RAID-5 device, and I'll take it out of disk group 1:
Execute a symconfigure operation for symmetrix 'xxxxxxx78' (y/ ) ? y
A Configuration Change operation is in progress. Please wait...
The configuration change session has failed.
So I can't even create a single 17GB RAID-5 device though it appears to have enough free space? What I am missing or not getting?
I really appreciate your help!
markdf
76 Posts
0
June 13th, 2012 10:00
Oh jeez. I lowered the "data_member_count" to 3, since I guess we're using RAID-5 (3+1) and it accepted it:
Execute a symconfigure operation for symmetrix 'xxxxx78' (y/) ? y
A Configuration Change operation is in progress. Please wait...
The configuration change session has completed successfully.
Heh.. now I just need some sort of cylinder converter that will tell me how many cylinders I should use for 35723MB devices.
markdf
76 Posts
0
June 13th, 2012 11:00
and BOOM!
# ./symdev -sid 78 list -noport
Symmetrix ID: xxxxxx78
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
001B Not Visible ???:? 16A:DA 2-Way Mir N/Grp'd RW 3
001C Not Visible ???:? 01A:CA 2-Way Mir N/Grp'd RW 3
001D Not Visible ???:? 16A:DE 2-Way Mir N/Grp'd RW 3
001E Not Visible ???:? 16A:CB 2-Way Mir N/Grp'd RW 3
001F Not Visible ???:? 16A:D8 2-Way Mir N/Grp'd RW 3
0020 Not Visible ???:? 01A:C8 2-Way Mir N/Grp'd RW 3
0021 Not Visible ???:? 01A:D9 2-Way Mir N/Grp'd RW 3
0022 Not Visible ???:? 16A:C9 2-Way Mir N/Grp'd RW 3
008F Not Visible ???:? 01B:C1 RAID-5 N/Grp'd RW 35723
0090 Not Visible ???:? 16B:C0 RAID-5 N/Grp'd RW 35723
00DA Not Visible ???:? 16B:D7 RAID-5 N/Grp'd RW 35723
00DB Not Visible ???:? 01A:D3 RAID-5 N/Grp'd RW 35723
00DC Not Visible ???:? 01A:C4 RAID-5 N/Grp'd RW 35723
00DD Not Visible ???:? 16B:C4 RAID-5 N/Grp'd RW 35723
00DE Not Visible ???:? 16B:D3 RAID-5 N/Grp'd RW 35723
00DF Not Visible ???:? 01B:D2 RAID-5 N/Grp'd RW 35723
00E0 Not Visible ???:? 01A:D1 RAID-5 N/Grp'd RW 35723
00E1 Not Visible ???:? 16A:D4 RAID-5 N/Grp'd RW 35723
00E2 Not Visible ???:? 01A:C6 RAID-5 N/Grp'd RW 35723
00E3 Not Visible ???:? 01B:D0 RAID-5 N/Grp'd RW 35723
Once again, I cannot thank you enough Dynamox. Patient, informative and on-point as always.
cheers
-mark
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
June 13th, 2012 11:00
so when you tried to create 7+1RAID5 device, disk in that disk group that had available space did not satisfy the different raid/DA requirements so it failed. When you tried to create a 3+1R5 device, since you only need to split your device into 4 larger "splits" vs 8 smaller "splits" , your disk could satisfy that requirement.
Do symdev show on device 008F and see how many cylinders it's using.