This post is more than 5 years old
207 Posts
0
2125
VBUS and TID
Hello,
I'm running an AIX 5.2 host connected to a dmx1000.
I ran the following command - symcfg -sid 1303 -dir 2b -p 0 list -address -available
Below are the partial results. I'm not sure what VBUS and TID are used for.
Symmetrix ID: 000xxxxxxxxx
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-2B 02B
02C3 /dev/rhdisk5 (M) 0 00 001
0115 /dev/rhdiskpower0 (M) 0 00 002
011D /dev/rhdiskpower1 (M) 0 00 003
0125 /dev/rhdisk22 (M) 0 00 004
012D /dev/rhdiskpower3 (M) 0 00 005
0135 /dev/rhdiskpower4 (M) 0 00 006
013D /dev/rhdiskpower5 (M) 0 00 007
0145 /dev/rhdisk33 (M) 0 00 008
- AVAILABLE 0 00 009 *
I would use the following commands to map my next sym volumes -
map dev 14e to dir 2b:0 target=0, lun=009;
map dev 14f to dir 2b:0 target=0, lun=00a;
map dev 150 to dir 2b:0 target=0, lun=00b;
I just keep incrementing the lun number (next would be 00d) for each new maping.
What if I need to map hundreds more symm volumes. Can I just keep incrementing?
Is there a limit to the number of LUNs for target 0? At some point do I need to start using target 1 or target 2?
Again I'm not sure what VBUS and TID are used for.
Message was edited by: I removed the Symmetrix ID number.
KCSCP
I'm running an AIX 5.2 host connected to a dmx1000.
I ran the following command - symcfg -sid 1303 -dir 2b -p 0 list -address -available
Below are the partial results. I'm not sure what VBUS and TID are used for.
Symmetrix ID: 000xxxxxxxxx
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-2B 02B
02C3 /dev/rhdisk5 (M) 0 00 001
0115 /dev/rhdiskpower0 (M) 0 00 002
011D /dev/rhdiskpower1 (M) 0 00 003
0125 /dev/rhdisk22 (M) 0 00 004
012D /dev/rhdiskpower3 (M) 0 00 005
0135 /dev/rhdiskpower4 (M) 0 00 006
013D /dev/rhdiskpower5 (M) 0 00 007
0145 /dev/rhdisk33 (M) 0 00 008
- AVAILABLE 0 00 009 *
I would use the following commands to map my next sym volumes -
map dev 14e to dir 2b:0 target=0, lun=009;
map dev 14f to dir 2b:0 target=0, lun=00a;
map dev 150 to dir 2b:0 target=0, lun=00b;
I just keep incrementing the lun number (next would be 00d) for each new maping.
What if I need to map hundreds more symm volumes. Can I just keep incrementing?
Is there a limit to the number of LUNs for target 0? At some point do I need to start using target 1 or target 2?
Again I'm not sure what VBUS and TID are used for.
Message was edited by: I removed the Symmetrix ID number.
KCSCP
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
May 13th, 2008 03:00
With AIX you simply use the already mentioned (in the other thread) 12 bits as a single "namespace" to choose your lun address from. So with AIX you can choose any lun between 0x000 and 0xFFF ... No TID or VBUS needed.
However note that the "lun" you choose (0xBAD as an example) MAY be presented to an hpux host sharing the same port. The HPUX host (with the appropriate symmask magic wand) may also see your devices, translating you 0xBAD lun in VBUS=B TGT=A LUN=D .. Note however that HPUX may not see this device even if you mask it since the LUN value is outside allowed ranges (hmm that's why I choose a BAD lun
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
May 13th, 2008 03:00
https://forums.emc.com/forums/thread.jspa?tstart=0&threadID=67674
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
May 13th, 2008 13:00
Message was edited by: I removed the Symmetrix ID
number.
KCSCP
Whoops I didn't notice that there was a symmid visible !!! Shame on me !!!
brad12341
207 Posts
0
May 13th, 2008 15:00
map dev 14e to dir 2b:0 target=0, lun=009;
now I can use
map dev 14e to dir 2b:0 lun=009; (leave the target off)
I can keep incrementing the lun by 1 until I hit FFF (I won't need to go that high as I will only have about 200 luns).
Does this sound correct?
Thanks - Brad
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 13th, 2008 19:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
May 14th, 2008 00:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
May 14th, 2008 02:00
FFF (I won't need to go that high as I will only have
about 200 luns).
Oh, that's a can of worms...
In this case we have a lot less worms
MarcT2
131 Posts
1
May 14th, 2008 02:00
Oh, that's a can of worms...
Many open systems hosts use "peripheral device addressing" and can only recognise the lower two nibbles of the LUN address (ie 000-0FF hex, or 0-255 decimal).
As far as I know this applies to Windows, Solaris (using the sd driver), Linux & Novell. Older versions of AIX with SCSI2 compliant fibre HBAs also fall into this category.
HP & Sequent hosts uses volume set addressing, where the most significant nibble becomes the VBUS, and therefore can make use of it. However with HP-UX, the least significant nibble (which the host interprets as it's lun value) must be in the range 0-7 (ie only xx0-xx7 is allowed).
Solaris with the Leadville (ssd) driver supports LUNs in the range 000-FFF, and the latest I can find about AIX is that we support LUNs from 000-0x1FF with the IBM 6228 adaptor (or later), which is SCSI-3 compliant.
Having said all that, EMC support up to a maximum of 512 LUNs per FA port on a DMX/DMX2 and up to 1024 on the DMX3. The LUN addresses can be above these limits, provided the total number of LUNs does not exceed the limit and the addresses are legal for the type of host attached.
See Knowledgebase article emc7896 for more details.
Hope that helps!
Marc
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 14th, 2008 03:00
512 LUNs per FA port on a DMX/DMX2 and up to 1024 on
the DMX3. The LUN addresses can be above these
limits, provided the total number of LUNs does not
exceed the limit and the addresses are legal for the
type of host attached.
Marc, the 512 LUNs limit ..does that take into account meta heads only or it counts meta members as well ?
Thanks
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 14th, 2008 03:00
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
May 14th, 2008 03:00
star2_bc/root> symcfg -sid 142 -fa 8a -p 0 -address -available list
Symmetrix ID: 000xxxx00142
Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---
FA-8A 08A 0 0000 Not Visible VCM 0 00 000
0B2B Not Visible 0 00 001
0B8D Not Visible 0 00 002
0B31 Not Visible 0 00 003
0B2D Not Visible 0 00 004
0DB6 Not Visible 0 00 005
0B36 Not Visible 0 00 006
0BCC Not Visible 0 00 007
......
12B7 Not Visible (M) 0 00 0D6
12BF Not Visible (M) 0 00 0D7
12C7 Not Visible (M) 0 00 0D8
12CF Not Visible (M) 0 00 0D9
12D7 Not Visible (M) 0 00 0DA
12DF Not Visible (M) 0 00 0DB
12E7 Not Visible (M) 0 00 0DC
12EF Not Visible (M) 0 00 0DD
- AVAILABLE 0 00 0DE *
05BA Not Visible 0 00 0F0
05BB Not Visible 0 00 0F1
- AVAILABLE 0 00 0F2 *
Total ----
Mapped Devices: 98
Including Metamembers: 649
Available Addresses: 941 (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)
star2_bc/root> symcli
Symmetrix Command Line Interface (SYMCLI) Version V6.4.1.0 (Edit Level: 827)
built with SYMAPI Version V6.4.1.0 (Edit Level: 827)
Message was edited by:
Stefano Del Corno
MarcT2
131 Posts
0
May 14th, 2008 04:00
512 LUN assignments per port on DMX/DMX2
1024 LUN assignments per port on DMX3
However...
The maximum number of devices (Symm Vols) that can be configured on an FA or SA processor is 2048 for Enginuity 5566, 5567, 5568, 5669, 5670 and 5671.
The maximum number of devices (Symm Vols) that can be configured on an FA processor is 4096 for Enginuity 5771 and 5772.
...these limits include meta-members and are per FA processor, which of course service multiple ports. A device on multiple ports on the same processor only counts once.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 14th, 2008 05:00