VNX5200 Unified share access

Being new to Unified, be sure to check out all of the EMC VNX videos on YouTube.  Several of the step by step guides could be quite useful.

Mohammad-t5tDw wrote: I am familiar with VNX block technology but new for Unified. I have installed a VNX5200 Unified with 2 DMs and 2 CS. To start NAS, I create a standalone CIFS server. Then create Filesystems and shares but I cant find any place to create user credentials that clients should be used to connect to share folders. Please reply to my below inquiries. Why I can just create CIFS server on only one DM namely server_2 not server_3 ? If server_3 is just for redundancy and not active I have to add the 3rd DM to the configuration ? server_2 is known as the Primary Datamover.  server_3 should be configured as the Standby Datamover, ready to take over in the event of a failure of the primary. If you experience a failure on the Primary, CIFS and NFS servers will failover to the standby. Why in Disk provisioning wizard I can just create Pools on SAS disks and NL-SAS disks can't be provisioned for file ? When provisioning storage on VNX for File, LUNs are created and added to a storage group for the Datamover.  The Automatic Volume Management (AVM) system will allow you to add the provisioned LUNs to a NAS Pool that can be used to provision filesystem.  Have a look at the EMC document, Managing Volumes and File Systems with VNX AVM.  It will provide specific instructions for provisioning rules for VNX for File. Why the shares cant be accessible via my laptop with user Administrator which created on CIFS server creation ? Have a look at the EMC document, Configuring and Managing CIFS on VNX.  This document discusses CIFS setup, standalone CIFS servers and management of said resources. How can I add users to the shares with access control ? Reference the document I mentioned above.  Once you've set the password on the standalone CIFS server, you can connect to and manage the CIFS server from the Windows MMC management UI.

Let us know if that helps!

Karl

Have you checked the screenshot about the disk provisioning wizard. NL-SAS can;t be configured !

You mean I have to install some snap-in to use windows MMC to connect to Data Mover ?

I will study the above mentioned Docs to see the installation of CIFS server stanalone installation.

Mohammad-t5tDw wrote: Have you checked the screenshot about the disk provisioning wizard. NL-SAS can;t be configured ! You mean I have to install some snap-in to use windows MMC to connect to Data Mover ? I will study the above mentioned Docs to see the installation of CIFS server stanalone installation.

For NL-SAS you should be checking protection mode - which means RAID6

Even if you cant configure it there - you can also configure through a wizard in UniSphere or manually

You dont need to install an extra MMC - it is the same MMC that you use on Windows to manage CIFS servers remotely

Please read the CIFS manual. You choice is either:

1) standalone CIFS server - then you can ONLY use local user/group accounts on the VNX that you have to create via MMC (dont forget that you HAVE to change the Administrator password through a Windows client FIRST)

2) domain-joined CIFS server - then every Windows user in your domain can use the shares - including the Domain Administrator (you can also enable local users/groups)

I could connect to shared but there is some folders like etc and .... how can we define users not seeing the system folders of shares ?

By default, you should avoid exporting the root of a filesystem.  Let's assume you create a filesystem called "fs01" and create the export as "/fs01".  This means that users can see, access and delete the special folders, lost+found and .etc.

What you should do instead is create a folder at the root of the filesystem and export that folder instead.  Using my example, after I create the filesystem "fs01", I would create a folder called "share" at the root of fs01, i.e. "fs01/share".  Then I would export that folder instead.  There will be no lost+found or .etc folder within "share", and no user will be able to access the directory above.

Let us know if that helps!

Karl

easiest way is to create a treequota instead of a folder.

It acts like a folder plus you have the option to set a quota limit.

Good point - thanks for the clarification!