I have gone through domain controller upgrades and swaps many times. The Celerra has always updated everything on its own. Make sure the DC's were correctly removed. IE... demoted from the domain prior to power down, Sites and Serivces are correct and verify the SRV records in the DNS servers were properly removed. the Celerra should remove from the list automatically.
The DC list gets updated dynamically - no need to do anything from Celerra side.
However, if you want to specify any exclusion or preferred list for DC servers - please engage EMC Celerra Support who can help and guide you accordingly.
Others may correct me if needed, and provide more thoughts/suggestions. Regards, Sandip
The actual list of domain controllers is populated when the CIFS service is started. We receive the list from DNS, so if DNS is updated and those DCs are no longer listed, the only way to clean up the list (i.e. remove the old entries) is to stop and start the CIFS service (or failover/reboot the Data Mover)
However, the Domain Controllers in the list are routinely pinged, generally once every 10 minutes, and the first, best Domain Controller to respond is selected as the primary DC for that Data Mover, and any DCs that do not respond are marked as down, so even if the DC is in the list, Celerra will not attempt to use it. It just increases ancillary network traffic as we periodically attempt to assess the condition of that DC.
Ok, so we have had the subnet added to the "sites and services" and hey presto - the NAS is now showing the correct site and only 2 DCs form the "server_cifs" command. I didn't have to do anything to refresh this.
sagle
90 Posts
0
June 10th, 2009 19:00
Sagle
nandas
4 Operator
•
1.5K Posts
1
June 10th, 2009 09:00
However, if you want to specify any exclusion or preferred list for DC servers - please engage EMC Celerra Support who can help and guide you accordingly.
Others may correct me if needed, and provide more thoughts/suggestions.
Regards,
Sandip
TF-9l6i4
54 Posts
0
June 10th, 2009 09:00
BillStein-Dell
Moderator
•
285 Posts
1
June 10th, 2009 10:00
However, the Domain Controllers in the list are routinely pinged, generally once every 10 minutes, and the first, best Domain Controller to respond is selected as the primary DC for that Data Mover, and any DCs that do not respond are marked as down, so even if the DC is in the list, Celerra will not attempt to use it. It just increases ancillary network traffic as we periodically attempt to assess the condition of that DC.
TF-9l6i4
54 Posts
0
June 11th, 2009 01:00
Ok, so we have had the subnet added to the "sites and services" and hey presto - the NAS is now showing the correct site and only 2 DCs form the "server_cifs" command. I didn't have to do anything to refresh this.
All sorted.
Thanks.