VMware Cloud Community
andreaspa
Hot Shot
Hot Shot
Jump to solution

Problems setting up vCloud Extender

Hi,

I'm setting up vCloud Extender in our lab in order to familiarize with it before setting it up in production, and I'm really banging my head against the wall with some strange issues with the Replication Manager.

These are the below versions:

vCD: 9.5.0.10264774

vCD Extender: 1.1.0.2 (cx-cloud-service)

Deploying the vCD Extender appliance goes fine, and while running the setup wizard the first failure occurs on step 7 - Activate Replicator. However, it seems like the issue lies within the Replication Manager appliance.

This is what I can see from the replication manager log files (/opt/vmware/h5/manager/log/manager.log):

2018-11-13 09:50:38.325  WARN - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] c.v.vim.sso.client.impl.SoapBindingImpl  : Could not load VECS keystore: java.security.KeyStoreException: VKS not found

2018-11-13 09:50:39.038  INFO - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] com.vmware.identity.token.impl.Util      : Reading resources from zip file path=[/opt/vmware/h4/lib/sso-wst-client-6.5.0-ob-4594768.jar]

2018-11-13 09:50:39.039  INFO - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] com.vmware.identity.token.impl.Util      : Reading resources from decoded zip file path=[/opt/vmware/h4/lib/sso-wst-client-6.5.0-ob-4594768.jar]

2018-11-13 09:50:39.562  WARN - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] c.v.v.s.c.i.SiteAffinityServiceDiscovery : CDC not configured java.lang.NoClassDefFoundError: com/vmware/identity/cdc/CdcFactory

2018-11-13 09:50:40.315  INFO - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] com.vmware.identity.token.impl.Util      : Reading resources from zip file path=[/opt/vmware/h4/lib/sso-saml-token-6.5.0-ob-4594768.jar]

2018-11-13 09:50:40.315  INFO - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] com.vmware.identity.token.impl.Util      : Reading resources from decoded zip file path=[/opt/vmware/h4/lib/sso-saml-token-6.5.0-ob-4594768.jar]

2018-11-13 09:50:40.489  INFO - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] c.v.identity.token.impl.SamlTokenImpl    : SAML token for SubjectNameId [value=vcd@VSPHERE.LOCAL, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element

2018-11-13 09:50:40.555  INFO - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] c.v.v.s.c.impl.SecurityTokenServiceImpl  : Successfully acquired token for user: vcd@vsphere.local

2018-11-13 09:50:40.609 ERROR - [a987b5bd-dcf8-4ccb-ba71-e2da1dee76f7_bg] [https-jsse-nio-8044-exec-5] c.v.h.c.controller.BaseErrorController   : A request from 10.100.200.230 to /sessions failed with [H4 API] Authentication Failure 401

2018-11-13 09:50:40.702  WARN - [8fccc911-de2e-4a12-b2db-ba9b2ece6ac9_th] [https-jsse-nio-8044-exec-1] c.v.vim.sso.client.impl.SoapBindingImpl  : Could not load VECS keystore: java.security.KeyStoreException: VKS not found

2018-11-13 09:50:40.914  WARN - [8fccc911-de2e-4a12-b2db-ba9b2ece6ac9_th] [https-jsse-nio-8044-exec-1] c.v.v.s.c.i.SiteAffinityServiceDiscovery : CDC not configured java.lang.NoClassDefFoundError: com/vmware/identity/cdc/CdcFactory

2018-11-13 09:50:41.121  INFO - [8fccc911-de2e-4a12-b2db-ba9b2ece6ac9_th] [https-jsse-nio-8044-exec-1] c.v.identity.token.impl.SamlTokenImpl    : SAML token for SubjectNameId [value=vcd@VSPHERE.LOCAL, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element

2018-11-13 09:50:41.135  INFO - [8fccc911-de2e-4a12-b2db-ba9b2ece6ac9_th] [https-jsse-nio-8044-exec-1] c.v.v.s.c.impl.SecurityTokenServiceImpl  : Successfully acquired token for user: vcd@vsphere.local

2018-11-13 09:50:41.139 ERROR - [8fccc911-de2e-4a12-b2db-ba9b2ece6ac9_th] [https-jsse-nio-8044-exec-1] c.v.h.c.controller.BaseErrorController   : A request from 10.100.200.230 to /sessions failed with [H4 API] Authentication Failure 401

What I also notice is that the Replication Manager appliance doesnt respond to ping as default, while the rest of the appliances does this. Strange!

Also, the GUI gives me this error:

Error Code 500 Failed to register H4Replicator, Cause [Unable to reach manager service]

Reply
0 Kudos
1 Solution

Accepted Solutions
andreaspa
Hot Shot
Hot Shot
Jump to solution

So, this was solved by letting the Manager VM run over christmas and new year, and then it just worked when coming back from the holidays.

Sometimes IT is strange..

/Andreas

View solution in original post

Reply
0 Kudos
1 Reply
andreaspa
Hot Shot
Hot Shot
Jump to solution

So, this was solved by letting the Manager VM run over christmas and new year, and then it just worked when coming back from the holidays.

Sometimes IT is strange..

/Andreas

Reply
0 Kudos