I recently had to perform the following during a CIFs (Windows File Sharing) installation from a NetApp storage controller. The chances of me remembering this again aren't very good so I wanted to post it here for later. We had two issues that caused us some grief.
Issue #1 - For whatever reason when looking for a domain controller it wasn't "attaching" to the local domain controller. The system would ask for a list of domain controllers but then try to communicate with remote AD servers, some of which were behind firewalls. NetApp is nice enough to allow us to "pin" the storage to a preferred list of domain controllers to correct this behavior. From the command line, use the following commands:
- cifs domaininfo - lists which domain controllers the NetApp is communicating with. The preferred list is a list you specify, the favored list is the list AD thinks are closet to you, and then the rest are listed.
- cifs prefdc - This command allows you to populate a list of the domain controllers you want to communicate with first. More than one can be entered in the command seperated by spaces in the format: cifs prefdc add (domain) (dc1) (dc2) (etc...)
- cifs resetdc - After a dc is added you need to reset the connection
- cifs prefdc print - Shows the list
After these two steps were complete, we were able to proceed.
4 comments:
#1 - Was the subnet of the NetApp filer assigned to the site in AD?
Hello, any good papers/docs you used to configure CIFS on a NetApp. We just received our 2040 cluster with CIFS license...
And since we plan to migrate our data to new servers this could be the time.
Greetz
Tim
Hey Tim - Sorry, no good docs that I know of. I took a NetApp CIFS admin class that was great (highly recommend it). You also just learn some tricks playing around with the systems and your methods will get better over time.
Good Luck!
fantastic man,i like ur this way,its a nice trick,so useful.
Post a Comment