UNSOLVED

M_Denney

updated

15 years ago

M

M_Denney

4 Posts

0

675

April 29th, 2011 13:00

One domain controller per SITE

Hi Celerra experts,

On some of our Celerras, when looking at server_cifs server_# output we only see 1 domain controller per domain. This is only on Celerras where the domain has SITE= configured. (Most of our Celerras we see multiple/many domain controllers per domain). The single domain controllre per SITE is by Active Directory design.

I understand that if the one domain controller goes down, the Celerra is suppose to rescan for other domain controllers not associated with the SITE.

How long does this rescan take?

What is the effect to end users while a "global" domain controller is located?

Does EMC have any best practises recommendation for providing domain controller services to Celerra cifs servers?

Thanks for opinions and input!

  • MJ991

    32 Posts

    274

    1

    Posted April 29th, 2011 13:00

    check the primus emc232131..

    This is an overview of how the Celerra populates its list of DCs:

  • Every 15 minutes, the Data Mover broadcasts on each enabled interface requesting a list of DCs for each Domain configured.
  • Every 15 minutes, the Data Mover also sends a request for a list of DCs from each interface to WINS server, if configured.
  • Answer to above two actions is a list of IP addresses and/or hostnames.
  • Data Mover builds this list as "*SMBSERVER" for each IP address received.
  • Data Mover then tries to ping each IP address on the list and establish whether the host is a valid DC.
  • For each answer, *SMBSERVER is replaced by the hostname and the corresponding response time.
  • M_Denney

    4 Posts

    274

    0

    Posted April 29th, 2011 14:00

    Hi,

    I read this primus. This primus sounds like my end users can be down for up to 14 minutes 59 seconds if the domain controller goes down?

  • MJ991

    32 Posts

    274

    1

    Posted April 29th, 2011 14:00

    You can reduce the scan time by modifing the below params..Also keep the vaule to "0' for useADSite..that way celerra can scan All the DC outside the SITE

    param_name                       facility  default     current   configured
    useADSite                                ds        
    RetryRefreshDC                        ds        
    RefreshDC                                ds