ONTAP Discussions
ONTAP Discussions
configuraton:
SVM add to an AD domain(ETE.COM) which have several domain users(aduser1~aduser10)
from "ONTAP 9 Documentation Center", I can find this help reference:
volume quota policy rule create:
-target <text> - TargetThis parameter specifies the target to which the quota policy rule applies. For default quota rules, this parameter should be specified as "". For explicit tree quotas rules, this parameter should indicate the qtree name. For explicit user quota rules, this parameter can contain UNIX user name, UNIX user identifier, Windows user name, Windows Security Identifier or a path to an existing object within the volume. If a name contains a space, enclose the entire value in quotes. A UNIX user name cannot include a backslash (\) or an @ sign; user names with these characters are treated as Windows names. For multi-user quotas, this parameter can contain multiple user targets separated by a comma. For explicit group quota rules, this parameter can contain UNIX group name or UNIX group identifier or a path to an existing object within the volume. When a path is specified as the target, it should be of the format /vol/<vol-name>/<path to file from volume root> where the volume matches that of the -volume parameter.
test steps:
1. vol quota policy rule create -vserver svm_test001 -policy-name default -volume test_1G -type user -target ete.com\aduser3 -qtree ""
-----OK
2. vol quota policy rule create -vserver svm_test001 -policy-name default -volume test_1G -type user -target ETE\aduser2 -qtree ""
-----OK
3. vol quota policy rule create -vserver svm_test001 -policy-name default -volume test_1G -type user -target aduser2@ete.com -qtree ""
------Error: command failed: Illegal name aduser2@ete.com specified in quota target.
question:
why ad domian user with @ is not OK?
Solved! See The Solution
Hi there,
As per the manual at http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-vsmg%2FGUID-77083F88-7B58-414B-A665-C19FCFA64B13.html&cp=17_2_7_0_8_1 - you can either use the old domain\user format, or the user SID, or a path to an existing file owned by the user. The user@domain format is not supported.
I cannot speculate as to why. If this is a required feature, I encourage you to reach out to your account team to have them lodge an RFE (request for enhancement) for it.
Thanks!
Hi there,
As per the manual at http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-vsmg%2FGUID-77083F88-7B58-414B-A665-C19FCFA64B13.html&cp=17_2_7_0_8_1 - you can either use the old domain\user format, or the user SID, or a path to an existing file owned by the user. The user@domain format is not supported.
I cannot speculate as to why. If this is a required feature, I encourage you to reach out to your account team to have them lodge an RFE (request for enhancement) for it.
Thanks!
Thanks AlexDawson.
I have got it, windows ad user format only support [domain]\[username] and SID.
Further question:
Note: You cannot use a UNIX user name to specify a quota if that name includes a backslash (\) or an @ sign. This is because ONTAP treats names containing these characters as Windows names.
If a UNIX user’s name do include an @ sign,what ONTAP should supposed to do? treated as Windows names? but how?
During my test of a ldap user( ldapuser1@ete.com), It always return an error: command failed: Illegal name ldapuser1@ete.com specified in quota target.
Domain Type : LDAP
User Name : ldapuser1@ete.com
User ID : 30011
Group Name : ldapgroup1(primary)
Group ID : 30001
"@" is not a valid character for a unix username
https://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 & https://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_276
Eh, and what this reference exactly means? Is there a scenario, a unix or windows user with @ sign can add to user quota, or not?
{Note: You cannot use a UNIX user name to specify a quota if that name includes a backslash (\) or an @ sign. This is because ONTAP treats names containing these characters as Windows names.} at http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-vsmg/GUID-F595143B-000C-4AE7-B15D-F1DACEFB6D99.html
No, "@" is not able to be used.
Thanks