Starting CIFS service on datamover

Question

I have a need to setup new CIFS servers on a different datamover that so far has only been used for NFS. As i have looked through documentation i have not seen any prerequisites before starting a CIFS server, so is it as simple as just starting the service or are they some other things i am missing ? This datamover is configured with usermapper database, so all other datamovers get their authentication information from it.

Thanks

IanSchorr · Accepted Answer

It's for a variety of technical reasons. For example, unicode support is tied to a number of things in the CIFS world, like being able to properly join an Active Directory as a "native" member. If we indicate that we can't send unicode strings (for things like filenames, host names, etc) then there are several assumptions that Windows systems make about us. We also have a handful of internal limitations without unicode support as well.

In the CIFS world, nearly everything is done in unicode (which is a good practice). Even ASCII characters (or the complete English char set) are stored and transmitted as UTF-8 unicode chars. Unicode's used for non-ASCII as well, but it's also standard for storing and describing ASCII characters too.

There's very few reasons NOT to use unicode these days, and does impose a number of restrictions, which is why it's enabled by default these days.

odonovan_kevin · Answer

Seeing as the datamover has NFS only before adding the CIFS, you might need to check a few things...
- NFS isn't too bothered about time sync, whereas with Kerberos its a requirement, so check your clock against the DC / Kerberos server.
- Will you be using CIFS with different mounts than the NFS? If you'll be using some filesystems for both NFS and CIFS, check the mount options used for authentication - MIXED / NATIVE / UNIX / etc etc
- there's that WinNT only step where you add the entry to NETBIOS for your CIFS server

After that its just the usual steps for the CIFS server, create an account in active directory, create the CIFS server on the datamover, start the CIFS service and join the domain.

nandas · Answer

In continuation of the previous reply - it is also very important to find out whether you need Multi-protocol access (NFS and CIFS access to the same file system) - the user mapping becomes very much important in that case. You mentioned USERMAPPER is running on the data mover, but till date only for NFS, usermapper was not doing anything. It will start mapping domain authenticated windows users only after you start CIFS service and join the CIFS server to the domain.

Since usermapper maps the UID/GID to each windows users, it will not be the same for your UNIX world. If you want to keep consistent UID/GID for all users across UNIX and Windows (which is definitely required for Multi-protcol environment), you need to stop usermapper service and use any other method for mapping users (like NIS or using Extended AD schema, or using local files etc) - refer to the "Managin celerra for a Multi-protcol environment" doc.

The other points mentioned in the previous reply are also very important. Also ensure DNS and NTP are set correctly. By default DDNS is used when you join the CIFS server to the AD. If DDNS is not enabled in the AD, then you need to change the CIFS parameter on the Data mover (to disable Dynamic DNS Update) and manually create the DNS entry for the CIFS server(s).

Also, there are many other CIFS paramters, which may need to be set for specific reason depending on your environment. But all default params should work in a normal circumstance.

Hope this helps.
Thanks,
Sandip

dynamox · Answer

Thank you for your replies folks, ..currently i have another datamover that's used for CIFS so usermapper database is actually in use. I am not planning to provide multi-protocol support ..file systems will be enabled either for CIFS or NFS ..but not both. My AD has DNS services running so i should be ok there ..i simply join my CIFS servers to AD and DNS entries get created automatically, but i also set them in BIND for our enterprise DNS .

Rainer_EMC · Answer

just make sure you have Unicode enabled for that data mover - see the "Using International Character Sets with Celerra" manual ( /nas/sbin/uc_config ) or through the GUI

Also consider using the Celerra Manager wizards - they will nicely lead through the steps needed to get CIFS running

dynamox · Answer

why do i have to enable Unicode ? I am not expecting people to save files in non-English character set ..but who knows.

dynamox · Answer

Thank you for explanation Ian.

dynamox · Answer

as i am getting ready to enable Unicode support on an existing datamover that already has NFS file systems, i got a warning:

 1) Unicode cannot be disabled. 
 2) Any file systems you subsequently create on this Data Mover will be usable only on unicode-enabled Data Movers. 
 3) Non-US-ASCII (7-bit ASCII) file systems mounted on this Data Mover will become unusable. Instead, perform 
    Unicode Conversion on these file systems.

number 3 is of concert to me, as i have no idea why data resides on my existing NFS exports. What if there are Non-US-ASCII files on these file systems ..and once i enable unicode they will not be accessable ? I have looked at "Using International Character Sets with Celerra" document ..but can't make sense out of it. Any feedback is appreciated.

Rainer_EMC · Answer

converting the file systems to Unicode isnt a big deal I suggest you open a case with EMC support and let them figure it out

dynamox · Answer

now that i started CIFS services and enabled Unicode, i see a default CIFS server called "DM2" on datamover server_2. Can i delete this default CIFS server because it's not joined to AD and generating a bunch of error messages in log, it's also running my primary usermapper service:

2007-08-18 13:00:21: DPSVC: 4:  DpRequest::execute() BEGIN reqType:DpRequest_ReplicaInt_KeepAlive reqCaller:DpRequest_Caller_KeepAlive reqMode:2
2007-08-18 13:00:21: DPSVC: 4:  DpRequest::execute() END reqType:DpRequest_ReplicaInt_KeepAlive reqCaller:DpRequest_Caller_KeepAlive status:0 reqMode:2
2007-08-18 13:00:34: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:00:34: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:01:34: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:01:34: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:02:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:02:34: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:03:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:03:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:04:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:04:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:04:45: USRMAP: 4:  Export last 311 ms
2007-08-18 13:04:45: ADMIN: 4:  Command succeeded:  usrmapsvc export
2007-08-18 13:04:50: ADMIN: 4:  Command succeeded:  usrmapsvc export erase
2007-08-18 13:04:55: USRMAP: 4:  Export last 304 ms
2007-08-18 13:04:55: ADMIN: 4:  Command succeeded:  usrmapsvc export
2007-08-18 13:04:55: ADMIN: 4:  Command succeeded:  usrmapsvc export erase
2007-08-18 13:05:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:05:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:06:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:06:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:07:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:07:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:08:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:08:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:09:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:09:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:10:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:10:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:11:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:11:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:12:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:12:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:13:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:13:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:14:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:14:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:15:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:15:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:16:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:16:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:17:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:17:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:18:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:18:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:19:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:19:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:20:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:20:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:21:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:21:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:22:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:22:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND
2007-08-18 13:23:33: SMB: 3:  Open&Bind(lsarpc):No DC for Srv=DM2 (91fee404)
2007-08-18 13:23:33: SMB: 3:  OpenAndBind[LSA] failed: NOPDC DOMAIN_CONTROLLER_NOT_FOUND

Celerra

Starting CIFS service on datamover

Was this post helpful?