Spectrum Scale, dosen't access to the secondary Active Directory(AD), in spite of AD is Active-Active redundant configuration

*Re-Submitted from ID:134412
Please cancel the request of 134412.

We are facing to the following situation and our client strongly request to resolve this issue as soon as possible.
We think that the function of SS about keeping session with AD should be modified to use secondary AD for improving reliability of SS.

1) System configuration
Spectrum Scale V5.0.3 : 3 nodes redundant configuration. (If one node would be down, it will take over to another two nodes)
Active Directory : 2 node Active-Active redundant configuration. AD will be re-booted periodically one by one. For your reference, AD has not have the virtual IP address.

2) Current issue
If one of two AD would be unavailable because of periodically re-boot, the session between SS and NFS and Windows client will be terminated.
We think this issue becomes the cause of complete out of services of SS, by another one of two AD was re-booted.
For your reference, L3 service person says it is a specification of current SS design, and there is no plan to modify or improve this specification.

3) Requirement
Please modify or improve the logic of keeping session with NFS and Windows client, whether one of two AD would be out of service.
We think the candidates of new implementation would be as follows.

a) If a connection with the AD, which is already used, becomes not available, SS asks DNS again to get an available AD address.
b) Add the new command or API to connect with available AD. We suppose to use the command or API for re-connect SS and AD after the periodically re-boot of AD.