The last two production eDirs (mdsacns1.fsu.edu & sprded02.erp.fsu.edu) are back on the ring and answering to LDAP/LDAPS traffic. To summarize, here is the list of LDAP servers to use for FSUID authentication and that all share the same schema and values:

• mdsoti.fsu.edu [146.201.105.140] - primary LDAP service for non-Sliger LDAP traffic
• mdsacns1.fsu.edu [146.201.2.68] - primary LDAP service for Sliger building LDAP traffic
• sprded01.erp.fsu.edu (prod-edir01.fsu.edu) - dedicated LDAP service for ERP private network
• sprded02.erp.fsu.edu (prod-edir02.fsu.edu) - dedicated LDAP service for ERP private network
• mdsdata.uc.fsu.edu [146.201.105.179] - going to be the "data load" LDAP server (recommended only as "last resort", as it'll be the busiest)

Here's the order I suggest you configure your various systems to fail over in:

• ERP: sprded01 or sprded02, mdsoti, mdsacns1, mdsdata
• Sliger building (including production CAS): mdsacns1, mdsoti, mdsdata
• UCC servers (and rest of campus): mdsoti, mdsacns1, mdsdata

Don't forget to remove udbprod.uc.fsu.edu [146.201.105.143] from your lists; that server is no longer a production eDir server. Also, you will need to go grab new certificates for sprded01, sprded02, mdsacns1 and mdsdata if you haven't done so already (e.g., point your browser to https://mdsacns1.fsu.edu:636/ and save/install the cert that pops up).

I have already reconfigured the three RADIUS servers that we have using these LDAPs (on sprded01, sprded02 for ERP VPN authentication and mdsoti for FSU VPN authentication) and double checked the mod_ldap .htaccess files on fsuid.fsu.edu and the Parature Perl passthrough CGI script on fsuid.fsu.edu. Sherry & Clint, you might want to double-check your BlueSocket configs to make maximum use of the failover addresses.