Article Content
| Issue | Marvin log :- [MARVIN] 2017-07-20T16:58:22:758Z WARN c.v.c.c.s.o.v.VCManagementService:61 - No VC connectivity: unable to connect to VC: The server sent HTTP status code 404: Not Found... waiting thirty seconds. [MARVIN] 2017-07-20T16:58:52:758Z INFO c.v.c.c.s.ManagementConnectionServiceImpl:46 - Management connection timed out, reconnecting. [MARVIN] 2017-07-20T16:58:52:759Z INFO c.v.c.c.s.ManagementConnectionServiceImpl:53 - Connecting to 172.17.86.90 username management@localos [MARVIN] 2017-07-20T16:58:52:759Z INFO c.v.c.c.c.m.ConnectionUtils:119 - Trying to obtain sso token from: https://172.17.86.95/sts/STSService/vsphere.local [MARVIN] 2017-07-20T16:58:52:843Z ERROR c.v.c.c.c.s.ConnectionFactoryImpl:81 - unable to connect to VC com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 404: Not Found at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:332) ~[jaxws-rt-2.2.10.jar:2.2.10] |
| Cause | |
| Resolution | This is not supported procedure. 1, vCenter 6.5 is supported for some VxRail versions 2, if customer want to join VxRail to external vcenter, it should be done at the initial installation step. NOT deploy with internal vcenter and delete it after initial configuration. Now the only approach to get back to the supported configuration is to reset the appliance and re-run the initial configuration. |
| Notes | KB 506472 - VxRail: what is required for external vcenter deployment |