SDC containers get created but SDC portal errors with 500 Internal Server Error. Attaching the screenshot.

Following is seen in the FE container log:

017-11-20T22:49:41.316Z|||main||ASDC-FE||INFO|||10.0.3.1||o.o.s.f.m.FeMonitoringService||ActivityType=<?>, Desc=<FE monitoring service is disabled>

2017-11-20T22:49:42.348Z|||FE-Health-Check-Thread||ASDC-FE||INFO|INFORMATIONAL||10.0.3.1||o.o.s.c.config.EcompErrorLogUtil||ActivityType=<?>, Desc=<ETYPE = "RECOVERY" ENAME = "FeHealthCheckRecovery" ECODE = "ASDC209I" ECONTEXT = "FE Health Recovered" EDESC = "Connectivity to ASDC BE Server is recovered.">

2017-11-20T22:50:05.742Z|||qtp110718392-55||ASDC-FE||INFO|||10.0.3.1||com.jcabi.aspects.aj.NamedThreads||ActivityType=<?>, Desc=<jcabi-aspects 0.20.1/f0aff93 started new daemon thread jcabi-loggable for watching of @Loggable annotated methods>

2017-11-20T22:52:31.303Z|||FE-Health-Check-Thread||ASDC-FE||ERROR|CRITICAL||10.0.3.1||o.o.s.c.config.EcompErrorLogUtil||ActivityType=<?>, Desc=<ETYPE = "SYSTEM_ERROR" ENAME = "FeHealthCheckError" ECODE = "ASDC204E" ECONTEXT = "Connection with ASDC-BE is probably down" EDESC = "Unable to connect to a valid ASDC Backend Server">

2017-11-20T22:55:59.030Z|183785a0-ba21-4b0f-9c89-41f0cdb62012||qtp110718392-46||ASDC-FE|demo|INFO||172.17.0.6|10.0.3.1|10.172.52.117|o.o.sdc.fe.servlets.FeProxyServlet||ActivityType=<?>, Desc=<GET /sdc1/feProxy/rest/v1/catalog/dataTypes HTTP/1.1>

2017-11-20T22:55:59.029Z|f2668bea-e30f-4379-b32e-5f5f159cbaf4||qtp110718392-61||ASDC-FE|demo|INFO||172.17.0.6|10.0.3.1|10.172.52.117|o.o.sdc.fe.servlets.FeProxyServlet||ActivityType=<?>, Desc=<GET /sdc1/feProxy/rest/version HTTP/1.1>

2017-11-20T22:55:59.034Z|c071f50d-282b-46b2-b39a-4658806d6781||qtp110718392-68||ASDC-FE|demo|INFO||172.17.0.6|10.0.3.1|10.172.52.117|o.o.sdc.fe.servlets.FeProxyServlet||ActivityType=<?>, Desc=<GET /sdc1/feProxy/rest/v1/configuration/ui HTTP/1.1>

2017-11-20T22:55:59.039Z|ab0c01c0-5e2b-4362-81a3-c9d4d516c561||qtp110718392-67||ASDC-FE|demo|INFO||172.17.0.6|10.0.3.1|10.172.52.117|o.o.sdc.fe.servlets.FeProxyServlet||ActivityType=<?>, Desc=<GET /sdc1/feProxy/rest/v1/user/authorize HTTP/1.1>

2017-11-20T22:55:59.141Z|183785a0-ba21-4b0f-9c89-41f0cdb62012||qtp110718392-67||ASDC-FE|demo|INFO||172.17.0.6|10.0.3.1|10.172.52.117|o.o.sdc.fe.servlets.FeProxyServlet|114|ActivityType=<?>, Desc=<SC="500">

In SDC BE log, following error is thrown:

017-11-20T23:23:24.734Z|||||qtp2116908859-26680||Health check|SDC-BE|||||||N/A|ERROR||||10.0.3.1||o.o.s.h.impl.HealthCheckManagerImpl||ActivityType=<?>, Desc=<All host(s) tried for query failed (no host was tried)>

com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried)

at com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:84) ~[cassandra-driver-core-2.1.9.jar:na]

at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37) ~[cassandra-driver-core-2.1.9.jar:na]

at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:214) ~[cassandra-driver-core-2.1.9.jar:na]

at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:52) ~[cassandra-driver-core-2.1.9.jar:na]

at com.datastax.driver.mapping.MethodMapper.invoke(MethodMapper.java:168) ~[cassandra-driver-mapping-2.1.9.jar:na]

at com.datastax.driver.mapping.AccessorInvocationHandler.invoke(AccessorInvocationHandler.java:65) ~[cassandra-driv