Unsolved
This post is more than 5 years old
14 Posts
0
1061
Question on # of devices allowed per FA port...
I have a question and hoping someoine can give me a direct answer...
when calculating the # of devices on a FA port, I know the limit is 4096, but if I am mapping a meta head to 2 FA ports and one comes up as Not Visible..
I am assuming that both FA ports hold the # of symdevs within it's limit....as an example; if I am mapping to FA port 09C and 08C...
and mapping 1 meta device built of 3 hypers, each hyper which is built from a 3 member raid-5 devices, then I am assuming that I have 10 devices charged
to my limit within 09C and 08C fa ports correct?, 3 for each hyper, 3 devs per hyper plus the metahead = 10
Also is there a quick and easy way or a CLI command that would allow show me the poper amount of symdevs that are already assigned to a FA port.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 17th, 2011 13:00
each port has 2 CPUs so 4096 is the total for both ports ( IE: 8C:0 and 8C:1). Each member of a meta takes a spot of that 4096
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
1
October 17th, 2011 14:00
it's not on the port, it's total for CPU, here is one of my FAs
Quincy561
1.3K Posts
1
October 17th, 2011 14:00
There are two ports on the FA CPU. The maximum per CPU is 4096. So each port has a maximum of 2048 devices. I think the 2048 limit is enforced on the port. However this is a lot of devices. Have you thought of making larger devices so you don't need so many?
ACPRATICO1
14 Posts
1
October 17th, 2011 14:00
Thank you for the response, but I am not sure you answered my question. each FA port has 2 CPU's yes but these are 2 different FA ports we map to. What you are saying the TOTAL for both port 0 and 1 is 4096...so each port has
2048 or the division does not matter they just need to tally to 4096 on both?
anoopcr
148 Posts
0
October 18th, 2011 09:00
If the count is not port wise,why the below output showing diffrent value ?
C:\Program Files (x86)\EMC\SYMCLI\bin>symcfg -sid 2847 -dir 9c -p 0 -address -available list
Symmetrix ID: 000190102847
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-9C 09C 0 0082 Not Visible VCM 0 00 000
0183 Not Visible 0 00 001
0184 Not Visible 0 00 002
0185 Not Visible 0 00 003
0186 Not Visible 0 00 004
0187 Not Visible 0 00 005
0188 Not Visible 0 00 006
0189 Not Visible 0 00 007
018A Not Visible 0 00 008
01A3 Not Visible 0 00 009
01A4 Not Visible 0 00 00A
01A5 Not Visible 0 00 00B
01A6 Not Visible 0 00 00C
01A7 Not Visible 0 00 00D
01A8 Not Visible 0 00 00E
01A9 Not Visible 0 00 00F
01AA Not Visible 0 00 010
01AB Not Visible 0 00 011
01AC Not Visible 0 00 012
016B Not Visible 0 00 013
016C Not Visible 0 00 014
016D Not Visible 0 00 015
016E Not Visible 0 00 016
016F Not Visible 0 00 017
0170 Not Visible 0 00 018
0171 Not Visible 0 00 019
0172 Not Visible 0 00 01A
- AVAILABLE 0 00 01B *
Total ----
Mapped Devices: 27
Including Metamembers: 27
Available Addresses: 4069 (s)
-------------------------------------------------------------------------------------------
C:\Program Files (x86)\EMC\SYMCLI\bin>symcfg -sid 2847 -dir 9c -p 1 -address -available list
Symmetrix ID: 000190102847
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-9C 09C 1 0082 Not Visible VCM 0 00 000
018B Not Visible 0 00 001
018C Not Visible 0 00 002
018D Not Visible 0 00 003
018E Not Visible 0 00 004
018F Not Visible 0 00 005
0190 Not Visible 0 00 006
0191 Not Visible 0 00 007
0192 Not Visible 0 00 008
- AVAILABLE 0 00 009 *
Total ----
Mapped Devices: 9
Including Metamembers: 9
Available Addresses: 4087 (s)
FA 9C port 0 showing Available Addresses: 4069 and 9C port 1 Available Addresses: 4087 (s)
ACPRATICO1
14 Posts
0
October 18th, 2011 10:00
we are using OPENVMS and the OS will not allow us to unmap a device and remap to another FA without a reboot involved for the entire cluster...For some reason the FRAME itself does not like it either and whenever we UNMAP devices we need to reboot our cluster.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 18th, 2011 10:00
i hear you, i have a couple VMS 7.3 boxes myself. PITA
ACPRATICO1
14 Posts
0
October 18th, 2011 10:00
According to what is posted here the total # of devices you have on 09C is 36...27 for 09C P 0 and 9 for P 1.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 18th, 2011 10:00
don't have any additional FAs?
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 18th, 2011 10:00
it's not reporting total per CPU but total per port, a sum of those ports can not exceed 4096
ACPRATICO1
14 Posts
0
October 18th, 2011 10:00
Yes we do need to create larger devices to reduce that amount but unable to do that at this time, we are looking at expansion of META's that were created when the original EMC storage frames were put in place. If we are not able to expand, we need to then create new META's and replace the old which is more downtime than we really wanted to take.
ACPRATICO1
14 Posts
0
October 18th, 2011 10:00
Yes we have additional FA ports and we will use them to create new devices, just was not aware until researched and found the PRIMUS that explained my situation....EMC had initally created these devices and at the time all of our clients were NOT on EMC DMX frame. Now all are on the frame along with TEST slots.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 18th, 2011 10:00
some OS are very forgiving, you could map devices from existing FAs to new FAs, mask them to the host and make sure PowerPath starts using them. Then you can write_disable these devices on the old FAs only and unmask/unmap from old FAs ..giving you more available slots.