N/Asst'd relates to BCVs because you need to "associate" a BCV target to a device group when working with them.
for example :
# symdg create testdg
# symld -g testdg add dev AAA STD000
# symld -g testdg add dev BBB STD001
# symbcv -g testdg associate dev 110 BCV000
# symbcv -g testdg associate dev 111 BCV001
# symmir -g testdg -full -exact establish
So, BCV's should display Asst'd or N/Asst'd under the "Attribute" column in a symdev list
A ???:? relates to devices that aren't mapped to an FA port. For example, VAULT devices or TDATs (DATA Devices), under a #symdev list -all. Or, devices under a #symdev list -noport
Yes, an NA:NA is for TDEVs because they have no specific back-end allocation.[extents on a TDEV are allocated from all TDATs in the pool]
Anonymous User
67 Posts
0
September 14th, 2014 08:00
Grp'd , N/Grp'd relate to DGs.
N/Asst'd relates to BCVs because you need to "associate" a BCV target to a device group when working with them.
for example :
# symdg create testdg
# symld -g testdg add dev AAA STD000
# symld -g testdg add dev BBB STD001
# symbcv -g testdg associate dev 110 BCV000
# symbcv -g testdg associate dev 111 BCV001
# symmir -g testdg -full -exact establish
So, BCV's should display Asst'd or N/Asst'd under the "Attribute" column in a symdev list
A ???:? relates to devices that aren't mapped to an FA port. For example, VAULT devices or TDATs (DATA Devices), under a #symdev list -all. Or, devices under a #symdev list -noport
Yes, an NA:NA is for TDEVs because they have no specific back-end allocation.[extents on a TDEV are allocated from all TDATs in the pool]
Hope this helps.
uhijik
2 Posts
0
September 14th, 2014 08:00
Really helpful.
rwise1
22 Posts
0
September 14th, 2014 08:00
Exactly what I was after rohang, really helpful. Many thanks.
dynamox
9 Legend
•
20.4K Posts
1
September 14th, 2014 10:00
Association also related to VDEVs, not only BCVs