Support Center > Search Results > SecureKnowledge Details
No communication with the Secondary MDS after creating its object
Symptoms
  • No communication with the Secondary Multi-Domain Management server (MDS) after creating a Secondary MDS object - the initial synchronization does not take place and CPCA process is down.
  • "Authentication to Server 127.0.0.1 failed" error when adding a user in mdsconfig.

Cause

When creating a Secondary MDS, an IP range was configured, but there was no IP range configured in the Primary MDS object.


Solution
Note: To view this solution you need to Sign In .