Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Selecting domain controllers

About setting domain controllers  Top

Upon startup and as listed below, the filer searches for a Windows domain controller. This section describes how and when the filer finds and selects domain controllers.

The filer searches for domain controllers when the cifs.site_awareness option is enabled and any of the following is true:

Understanding the domain controller discovery process  Top

The following table describes the domain controller discovery process and priority groups. The filer only progresses to a lower priority group when it has failed to contact all domain controllers in the priority group above it.

Note
For Active Directory environments, site membership is one of the criteria by which the filer selects domain controllers (when no preferred domain controllers are available). Therefore, it is important to have the Sites and Services configured properly (with the filer's subnet information included in the same site as the filer).

Domain controller category

Priority groups: Order in which domain controllers are selected

Preferred
Controllers in the prefdc list

Group 1

Preferred domain controllers are selected by the order in which the controllers appear in the prefdc list.

Favored
Controllers that share the same Active Directory site membership with the filer

(This category is empty for filers in Windows NT environments.)

Group 2

Domain controllers from which a response was received within one second of being pinged, in the order of fastest response time

Group 3

Domain controllers that did not respond within one second, but share the same subnet as the filer

Group 4

All non-local domain controllers that did not respond within one second of being pinged

Other
Controllers that do not share site membership

Group 5

Domain controllers from which a response was received within one second of being pinged, in the order of fastest response time

Group 6

Domain controllers that did not respond within one second, but share the same subnet as the filer

Group 7

All non-local domain controllers that did not respond within one second of being pinged

Note
Because site membership is specific to Active Directory domains, there is no "favored" category for Windows NT4 domains, nor for mixed-mode domains in which the filer is configured as an NT4 server. In these environments, all domain controllers found through discovery are assigned the category "other."

Specifying a list of preferred domain controllers  Top

To specify a list of preferred domain controllers, complete the following step.

Step

Action

1

Enter the following command:

cifs prefdc add domain address [address ...]

domain is the domain for which you want to specify domain controllers.

address is the IP address of the domain controller.

Example

The following example specifies two preferred domain controllers for the lab domain:

cifs prefdc add lab 10.10.10.10 10.10.10.11

Note
To force the filer to use a revised list of preferred domain controllers, use the cifs resetdc command.

Deleting preferred domain controllers  Top

After you delete a domain from the prefdc list, you should always perform a cifs resetdc command to update the filer's available domain controller information, as described in step 2 of the following procedure. The filer does not update the domain controller discovery information from network services when the prefdc list is updated. Failure to reset the domain controller information can cause a connection failure, if the filer tries to establish a connection with an unavailable domain controller.

Note
The filer does not automatically perform domain controller discovery operations upon restart; restarting the filer does not update the available domain controller list.

To delete preferred domain controllers, complete the following steps.

Step

Action

1

Enter the following command:

cifs prefdc delete domain

domain is the domain where the preferred domain controllers reside.

Example

The following example deletes the preferred domain controllers for the lab domain:

cifs prefdc delete lab
2

Enter the following command:

cifs resetdc [domain]

domain is the domain you specified in step one.

The filer disconnects and searches for a domain controller in the order specified in the revised prefdc list.

Troubleshooting domain controller connection  Top

To troubleshoot and observe filer domain to controller traffic, enable the cifs.trace_dc_connection filer option. For usage information about this option, see the Data ONTAP command reference.

Displaying a list of preferred domain controllers  Top

To display a list of preferred domain controllers, complete the following step.

Step

Action

1

Enter the following command:

cifs prefdc print [domain]

domain is the domain for which you want to display domain controllers. When a domain is not specified, this command displays preferred domain controllers for all domains.

Example

The following example displays the preferred domain controllers for the lab domain:

cifs prefdc print lab

Reestablishing the filer connection with a domain  Top

To disconnect the filer from the current domain controller and establish a connection between the filer and a preferred domain controller, or to force domain controller discovery to update the list of available domain controllers, complete the following step.

Step

Action

1

Enter the following command:

cifs resetdc domain

domain is the domain from which the filer disconnects. If it is omitted, the filer disconnects from the domain in which the filer is installed.

The filer reestablishes a connection using the methodology described in Understanding the domain controller discovery process.

Example

The following example disconnects the filer from the domain controllers for the lab domain:

cifs resetdc lab

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments