Unsolved

This post is more than 5 years old

4 Posts

2429

May 2nd, 2013 13:00

vnx 5300 multiprotocol

Hello ,

i am trying to setup vnx5300 for CIFS and NFS , but i can't manage to work name mapping  between AD users and linux users.

windows users can access HOME share without problem, but when i am trying to mount home dir to linux i can't access mounted home directory because

of wrong ownership. i have installed Celerra Cifs mgmt package on domain controller, i can see that AD schema was extened, but regardless of creating user and assign UID - still no luck, in our current setup we use NIS, which we actually want to stop using on new infrastructure.

in other words i am trying to find out how to windows account can be mapped to an appropriate UID.

thanks,

D.

4 Apprentice

 • 

1.2K Posts

May 20th, 2013 10:00

Can you take a look at the document "Configuring Usermapper for VNX"?  On one hand, it sounds like you're still using the built-in Usermapper - which is how the VNX maps Windows GUID to the VNX's internal UID.  The document outlines some steps you'll need to take to make the UNIX UID and Windows GUID equivalent.

Have a look at the document then reply back with questions - I'll help any way I can.


Thanks!

Karl

4 Posts

May 22nd, 2013 11:00

Hello Karl,

i've  configured user mapping - now it's working, my setup:

AD (windows 2008 r2) + Centrify Direct control + ldap proxy + celerra

celerra getting users from AD trought centrify ldap proxy.
i've noticed strange issue with permissions (in bold)

denis@ub12:~$ ls -la

total 16

drwxr--r-- 4 denis domainusers 1024 May 22 20:42 .

drwxr-xr-x 3 root  daemon        80 May 22 20:24 ..

-rw------- 1 denis domainusers   28 May 22 20:27 .bash_history

drwxr-xr-x 2 denis domainusers   80 May 22 20:42 folder created from unix

d---rwxrwx 2 denis domainusers   80 May 22 20:41 folder created from windows

denis@ub12:~$

do you have any idea what can be wrong ?

6 Operator

 • 

8.6K Posts

May 22nd, 2013 13:00

My guess – different way default Unix permission (umask) is determined

For CIFS – system wide umask configured on the VNX

For NFS – umask is set and determined on the client and the Unix permissions are explicitly sent with the NFS request

Of course it also depends on what access policy you are using – whether and how CIFS permissions are synchronized

User mapping alone wont do that

Take a look at the Parameters guide – maybe there are some settings that can help

Rainer

4 Posts

May 23rd, 2013 07:00

i tried to re-configure cifs/nfs - now all seems to be ok, btw is there any way to create user home dir automatically, or using script - for example linux users need to login once from windows machine to create home dir..

4 Apprentice

 • 

1.2K Posts

May 28th, 2013 10:00

Take a look a the document EMC VNX Home Directory A Detailed Review.  You can have the VNX auto-create home directories and do interesting things with regular expressions.  Have a look at the guide then let us know if you have any questions.

Thanks!

Karl

4 Posts

May 30th, 2013 03:00

thanks Karl, i already using that feature and its works fine with windows users, but linux users accessing their home dir by nfs , seems that we need to have them to do first login from windows machine to autocreate home dir.

4 Apprentice

 • 

1.2K Posts

May 30th, 2013 07:00

That's correct - old the older Celerra, the home directory feature was always referred to the CIFS Home Directory feature, since it was built to work on the CIFS protocol.  That is, to get the automatic home directory creation, you had to first connect via CIFS to get the home directory to be auto-created.  The same thing applies today - you will probably have to make the connection first via Windows to get the directory created.

As part of the new user setup process in your environment, you might consider writing a Windows script that will connect to the NAS as the new user, to ensure the directory is created.

6 Operator

 • 

8.6K Posts

May 30th, 2013 08:00

This is because the difference in how CIFS works vs. NFS

On CIFS there is a connect/login and we can identify that a user wants to connect to its home directory

On NFS we cannot – NFS doesn’t authenticate a user – it authenticates a machine.

Simpler said – you don’t mount your homedir as the user – the client OS does it as root

IF you need homedir’s to be created for NFS users then you should do it as part of your user provisioning process.

You could also try to script this in the users profile

No Events found!

Top