Hello,

Does anyone have a recommendation for a virtual appliance that is supported to run vCloud for Service Providers 8.1 which can serve as an endpoint for ~200 IPsec VPNs?  The purpose is to connect to SaaS customers.  Looking for something ideally that is certified as supported on vCD and has HA capability.  At the moment the requirement is just for VPN termination.  East-west traffic between VM's I believe is being handled by the native networking.  I am presales and not a vCD expert, this did not seem like a hard thing to solve for, but the first appliance I looked at the ASAv10 mentions in it's docs that it cannot be deployed using vCD.  Thanks in advance.

Jacob Shorr

Moved a test environment to a different location and i need to change the IP addresses.

I remember during the setup of VCD, i had to assign 2 IP addresses,

How to change them and get VCD running in the new network?

I checked https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028657

1/"

Execute these SQL statements:

1. select name from cells;"

Ran ths as query and there was no objects cells.

2/ "From within the Red Hat system which is hosting the vCloud Director software, navigate into the $VCLOUD_HOME/etc directory using the cd command and change these values in the global.properties file:  "

What's the $VCLOUD_HOME? i browsed from root into etc but couldn't find global.properties file.

Any insights greatly welcome, im totally lost.

many thanks

Hi,

question regarding sizing in vShiled Edge in vCloud.

There is a Full-4 vShield edge wihtin VDC deployed and ORGNET is created.

Now orgadmin deployed a new vApp Network - connected to the Orgnet, then a second vShield is automatic deployed - but is the sizing the same then the already deployed VDC vShield edge?

thanks a lot.

regards

I decided to create a new thread , old one had a different title and different issue and was not getting attention anymore.

Ok so , i moved to a different host & network, my Vcenter, NSX and everything else works, except my vcloud director interface.

What i have changed are the centos IP, change the IP of database and vcd using this guide.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028657

After a  - service vmware-vcd status

i get

vmware-vcd-watchdog is running

vmware-vcd-cell is dead, but pidfile exists

the cell goes running and then dead constantly. Is there anything else i should do to get VCD up and running after changing ip?

I did change my DNS entries and it resolves perfectly, have ip in both my DNS and my centos hosts file.

The browser did ask me to accept certificate when i went on https://192.168.120.75 ,  but then i just get "

This site can’t be reached

192.168.120.75 refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

These are my settings, globalproperties.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

# Dtabase connection settings

database.jdbcUrl = jdbc:jtds:sqlserver://192.168.120.72:1433/vcloud;socketTimeout=90;instance=MSSQL-01,jdbc:jtds:sqlserver://192.168.120.72:1433/vcloud;socketTimeout=90;instance=MSSQL-01

database.username = vcloud,vcloud

database.password = tF924cPW5hzRI/YF5YfuMQ==,tF924cPW5hzRI/YF5YfuMQ==

# Product display name

# Product display name

product.display_name = VMware vCloud Director,VMware vCloud Director

# Maximum number blocking tasks (per cell) to be resumed when expired.

# This property is taken into account only when blocking task's default timeout action is "Resume".

# Uncomment this line and set the desired value. Otherwise, the default value (1000) will be used.

# blockingTasks.timeoutResumeRate = 1000

# Maximum number blocking tasks (per cell) to be resumed when expired.

# This property is taken into account only when blocking task's default timeout action is "Resume".

# Uncomment this line and set the desired value. Otherwise, the default value (1000) will be used.

# blockingTasks.timeoutResumeRate = 1000

product.version = 8.10.0.3879706,8.10.0.3879706

product.build_date = 2016-05-12T20:32:07-0700,2016-05-12T20:32:07-0700

vcloud.cell.ip.primary = 192.168.120.75,192.168.120.75

consoleproxy.host.https = 192.168.120.76,192.168.120.76

vcloud.ssl.password = TE0ADoWMkrn/HOIZTw3oK9jajMGmuKnQvoTKRp/S/rU=,TE0ADoWMkrn/HOIZTw3oK9jajMGmuKnQvoTKRp/S/rU=

vcloud.ssl.key.password = ePzQo8AZymcTyNLu13mMdgoyXbHrX1wiKbDqCNgqitw=,ePzQo8AZymcTyNLu13mMdgoyXbHrX1wiKbDqCNgqitw=

vcloud.ssl.truststore.password = gYvMRSlbjynsjMYEGxlSlHoU3FEvjtKP5sxakPDYVdU=,gYvMRSlbjynsjMYEGxlSlHoU3FEvjtKP5sxakPDYVdU=

consoleproxy.keystore.password = Gr9xQgtM4I9YpRyn0+36TQQcnRcwZl1XEBIyfxXtzGc=,Gr9xQgtM4I9YpRyn0+36TQQcnRcwZl1XEBIyfxXtzGc=

consoleproxy.keystore.path = /opt/vmware/vcloud-director/etc/proxycertificates,/opt/vmware/vcloud-director/etc/proxycertificates

audit.syslog.host = \,

audit.syslog.port = 514,514

vcloud.cell.uuid = eebea746-e7c2-47d6-b412-021cbca56205,eebea746-e7c2-47d6-b412-021cbca56205

vcloud.cell.ips = [192.168.120.75,192.168.120.76,192.168.218.74,192.168.218.75,127.0.0.1,fe80:0:0:0:20c:29ff:feb4:f046%ens33,fe80:0:0:0:20c:29ff:feb4:f050%ens34,0:0:0:0:0:0:0:1%lo]

system.info = +MNtwqQXNQdMKtWKw7gp896zd6YpPprCtNqIA0n8FPs=,+MNtwqQXNQdMKtWKw7gp896zd6YpPprCtNqIA0n8FPs=

system.version = 1,1

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

And in SQL i ran,

update cells set primary_ip='192.168.120.75' where name='vcd-01';

---------------------------------------------------------------------------------------------------------------------------------------------------------------

LOG UPDATE -  don't seem to see anymore errors in regard to hostname.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[root@vcd-01 logs]# tail -f vcloud-container-info.log

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[root@vcd-01 logs]# tail -f vcloud-container-debug.log

        currentContext.success=true,

        currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-8991

        currentContext.user.name=system,

        currentContext.user.proxyAddress=,

        entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$7/907858780

        entity.name=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$6/1582928

        entity.type=com.vmware.vcloud.entity.cell,

}] |

2017-02-06 18:55:51,536 | DEBUG    | CloudProxy Application    | Crypto

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd

2017-02-06 18:58:18,182 | DEBUG    | Bootstrap Application     | ProductSSLConstants$CipherConfiist: [SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_56_CBC_SHA, TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_W_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_

2017-02-06 18:58:18,182 | DEBUG    | Bootstrap Application     | ProductSSLConstants$CipherConfiLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AE

2017-02-06 18:58:18,182 | DEBUG    | Bootstrap Application     | ProductSSLConstants$ProtocolConprotocol list: [SSLv3, SSLv2Hello] |

2017-02-06 18:58:18,182 | DEBUG    | Bootstrap Application     | ProductSSLConstants$ProtocolConcols: [TLSv1.2, TLSv1.1, TLSv1] |

2017-02-06 18:58:18,618 | DEBUG    | Bootstrap Application     | EncryptionManager

2017-02-06 18:58:18,695 | DEBUG    | Bootstrap Application     | EncryptionManager

2017-02-06 18:58:33,840 | DEBUG    | Bootstrap Application     | EventHelper                    526-49ff-86b3-7a4d8eed19c0, timestamp=1486393113729, type=com/vmware/vcloud/event/cell/bootstrap

        bootstrap.requiredProperties={vcloud.http.port.standard=80, product.version=8.10.0.38797-05-12T20:32:07-0700, vcloud.http.port.ssl=443},

        currentContext.cell.uuid=,

        currentContext.org.id=System(com.vmware.vcloud.entity.org:a93c9db9-7471-3192-8d09-a8f7ee

        currentContext.success=true,

        currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-8991

        currentContext.user.name=system,

        currentContext.user.proxyAddress=,

        entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$7/907858780

        entity.name=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$6/1582928

        entity.type=com.vmware.vcloud.entity.cell,

}] |

2017-02-06 18:58:34,110 | DEBUG    | OSGI Delegator - listener dispatcher | EventHelper         =27491910-9ff2-48f5-9a6e-a2bfddb5801b, timestamp=1486393113922, type=com/vmware/vcloud/event/cel

        cellApplication.intermediateState=STARTING_FROM_STOPPED,

        cellApplication.name=com.vmware.vcloud.common.main.LegacyCellApplication,

        cellApplication.originState=STOPPED,

        cellApplication.simpleName=LegacyCellApplication,

        cellApplication.simpleState=transitioning,

        cellApplication.targetState=STARTED,

        cellApplication.transitionState=TRANSITIONING,

        currentContext.cell.uuid=,

        currentContext.org.id=System(com.vmware.vcloud.entity.org:a93c9db9-7471-3192-8d09-a8f7ee

        currentContext.success=true,

        currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-8991

        currentContext.user.name=system,

        currentContext.user.proxyAddress=,

        entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$7/907858780

        entity.name=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$6/1582928

        entity.type=com.vmware.vcloud.entity.cell,

}] |

2017-02-06 18:58:34,629 | DEBUG    | OSGI Delegator - listener dispatcher | EventHelper         =70f9013c-9403-4763-8081-c5d9f7c8eaef, timestamp=1486393114629, type=com/vmware/vcloud/event/cel

        cellApplication.intermediateState=STARTING_FROM_STOPPED,

        cellApplication.name=com.vmware.vcloud.cloudproxy.server.CloudProxyApplication,

        cellApplication.originState=STOPPED,

        cellApplication.simpleName=CloudProxyApplication,

        cellApplication.simpleState=transitioning,

        cellApplication.targetState=STARTED,

        cellApplication.transitionState=TRANSITIONING,

        currentContext.cell.uuid=,

        currentContext.org.id=System(com.vmware.vcloud.entity.org:a93c9db9-7471-3192-8d09-a8f7ee

        currentContext.success=true,

        currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-8991

        currentContext.user.name=system,

        currentContext.user.proxyAddress=,

        entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$7/907858780

        entity.name=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$6/1582928

        entity.type=com.vmware.vcloud.entity.cell,

}] |

2017-02-06 18:58:34,629 | DEBUG    | OSGI Delegator - listener dispatcher | EventHelper         =b22ba31b-a1ab-4838-b4e2-e90a68465bb0, timestamp=1486393114629, type=com/vmware/vcloud/event/cel

        cellApplication.intermediateState=STARTING_FROM_STOPPED,

        cellApplication.name=com.vmware.consoleproxy.async.server.ConsoleProxyCellApplication,

        cellApplication.originState=STOPPED,

        cellApplication.simpleName=ConsoleProxyCellApplication,

        cellApplication.simpleState=transitioning,

        cellApplication.targetState=STARTED,

        cellApplication.transitionState=TRANSITIONING,

        currentContext.cell.uuid=,

        currentContext.org.id=System(com.vmware.vcloud.entity.org:a93c9db9-7471-3192-8d09-a8f7ee

        currentContext.success=true,

        currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-8991

        currentContext.user.name=system,

        currentContext.user.proxyAddress=,

        entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$7/907858780

        entity.name=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$6/1582928

        entity.type=com.vmware.vcloud.entity.cell,

}] |

2017-02-06 18:58:34,630 | DEBUG    | OSGI Delegator - listener dispatcher | EventHelper         =c966f7b5-42e8-4452-bb79-36213e2a1230, timestamp=1486393114629, type=com/vmware/vcloud/event/cel

        cellApplication.intermediateState=STARTING_FROM_STOPPED,

        cellApplication.name=com.vmware.vcloud.computeservice.app.ComputeServiceBrokerApplicatio

        cellApplication.originState=STOPPED,

        cellApplication.simpleName=ComputeServiceBrokerApplication,

        cellApplication.simpleState=transitioning,

        cellApplication.targetState=STARTED,

        cellApplication.transitionState=TRANSITIONING,

        currentContext.cell.uuid=,

        currentContext.org.id=System(com.vmware.vcloud.entity.org:a93c9db9-7471-3192-8d09-a8f7ee

        currentContext.success=true,

        currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-8991

        currentContext.user.name=system,

        currentContext.user.proxyAddress=,

        entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$7/907858780

        entity.name=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$6/1582928

        entity.type=com.vmware.vcloud.entity.cell,

}] |

2017-02-06 18:58:38,260 | DEBUG    | CloudProxy Application    | Crypto

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

VMware vCloud Director,VMware vCloud Director 8.10.0.3879706,8.10.0.3879706, Mauritius Time, vcd-01 (192.168.120.75)

2017-02-06 18:59:26,058 | DEBUG    | Bootstrap Application     | ProductSSLConstants$CipherConfigStartupAction | Disallowed cipher list set to default disabled cipher list: [SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA] |

2017-02-06 18:59:26,058 | DEBUG    | Bootstrap Application     | ProductSSLConstants$CipherConfigStartupAction | System configured to use following approved ciphers: [TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA] |

2017-02-06 18:59:26,058 | DEBUG    | Bootstrap Application     | ProductSSLConstants$ProtocolConfigStartupAction | Disallowed SSL protocol list set to default disabled protocol list: [SSLv3, SSLv2Hello] |

2017-02-06 18:59:26,058 | DEBUG    | Bootstrap Application     | ProductSSLConstants$ProtocolConfigStartupAction | System configured to use following approved SSL protocols: [TLSv1.2, TLSv1.1, TLSv1] |

2017-02-06 18:59:26,413 | DEBUG    | Bootstrap Application     | EncryptionManager              | EncryptionManager configured with system key. |

2017-02-06 18:59:26,498 | DEBUG    | Bootstrap Application     | EncryptionManager              | EncryptionManager has been loaded successfully. |

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[root@vcd-01 logs]# tail -f cell.log

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0

Bootstrap application: start

Bundle-Id: 218, Bundle-SymbolicName: jline, Bundle Location: initial@reference:file:jline/jline-2.7.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package org.fusesource.jansi.internal_0.0.0

]

Bundle-Id: 229, Bundle-SymbolicName: client-toolkit, Bundle Location: initial@reference:file:com/vmware/vcloud/client-toolkit/1.0.0/client-toolkit-1.0.0.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package com.vmware.vim.query.client_[0.0.0,1.0.0)

]

Bundle-Id: 252, Bundle-SymbolicName: cell-management-tool-vcd-client, Bundle Location: initial@reference:file:com/vmware/vcloud/cell-management-tool-vcd-client/1.5.0/cell-management-tool-vcd-client-1.5.0.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package com.vmware.vcloud.clienttoolkit.vc_0.0.0

]

All required system properties are present

An unspecified error occurred during application start

All required local configuration properties are present

Successfully bound network port: 80 on host address: 192.168.120.75

Successfully bound network port: 443 on host address: 192.168.120.75

Successfully bound network port: 8999 on host address: 192.168.120.75

All required local configuration properties are present

Successfully initialized system cryptography

Successfully configured HTTP SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/certificates

Current locale "en" verified successfully.

Bootstrap application: complete

Application startup event: Waiting for subsystem 'com.vmware.vcloud.common.core'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.consoleproxy'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.cloud-proxy-server'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.computeservice.broker'

Application startup event: Subsystem 'com.vmware.vcloud.cloud-proxy-server' startup initiated.

Uncaught Exception. Originating thread: Thread[pool-6-thread-1,5,main]. Message: Error creating bean with name 'productInfoService': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'productInfoBean' defined in URL [bundleentry://211.fwk2101249621/META-INF/spring/bundle-context.xml]: Cannot create inner bean 'org.springframework.beans.factory.config.MethodInvokingFactoryBean#5a94d6e8' of type [org.springframework.beans.factory.config.MethodInvokingFactoryBean] while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.beans.factory.config.MethodInvokingFactoryBean#5a94d6e8' defined in URL [bundleentry://211.fwk2101249621/META-INF/spring/bundle-context.xml]: Cannot resolve reference to bean 'productBuildDateBean' while setting bean property 'targetObject'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'productBuildDateBean' defined in URL [bundleentry://211.fwk2101249621/META-INF/spring/bundle-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.joda.time.DateTime]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: Invalid format: "[2016-05-12T20:32:07-0700, 2016-..."

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[root@vcd-01 logs]# tail -f vmware-vcd-watchdog.log

2017-02-06 19:02:32 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it

2017-02-06 19:02:40 | INFO  | Started vmware-vcd-cell (pid=21034)

2017-02-06 19:03:00 | WARN  | wget failed, return code: 4, will retry in 30 seconds

2017-02-06 19:03:50 | WARN  | wget failed, return code: 4, will retry in 30 seconds

2017-02-06 19:04:40 | WARN  | wget failed, return code: 4, will retry in 30 seconds

2017-02-06 19:06:10 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it

2017-02-06 19:06:17 | INFO  | Started vmware-vcd-cell (pid=21650)

2017-02-06 19:06:37 | WARN  | wget failed, return code: 4, will retry in 30 seconds

2017-02-06 19:07:27 | WARN  | wget failed, return code: 4, will retry in 30 seconds

2017-02-06 19:08:17 | WARN  | wget failed, return code: 4, will retry in 30 seconds

Hello,

I have changed the Policy of the Catalog to the new Policy (there is a note that items will be moved) but nothing migrates to the new policy. Note: New Policy has the same Datastores.

Moving inidividual Items is not possible in to the same Catalog... to an other catalog it works.

Anyone else had this situation?

Sorry, since there is in the isolated environment therefore I can't copy the log outside.

I had verify file

cxf-rt-transports-http-hc-2.7.6,jar

global.properties

global.properties.rpmnew

global749292125036625037properties

are all exist

vcloud-container-info.log:

2017-02-07 12:01:16,346 | Warn | Bootstrap Application | DiagnosticsStartupAction | Bundle-Id: 258, Bundle-SymbolicName: org.apache.cxf.cxf-rt-transports-http-hc, Bundle Location: initial@reference:file:org/apache/cxf/cxf-rt-transports-http-hc/2.7.6/cxf-rt-transports-http-hc-2.7.6.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package org.apache.http_[4.2.1,4.3.0)

, Missing imported package org.apache.http.auth_[4.2.1,4.3.0)

, Missing imported package org.apache.http.client_[4.2.1,4.3.0)

, Missing imported package org.apache.http.client.methods_[4.2.1,4.3.0)

, Missing imported package org.apache.http.client.protocol_[4.2.1,4.3.0)

, Missing imported package org.apache.http.concurrent_[4.2.1,4.3.0)

, Missing imported package org.apache.http.conn.params_[4.2.1,4.3.0)

, Missing imported package org.apache.http.entity_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.client_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.nio_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.nio.reactor_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.nio.reactor.ssl_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.nio.util_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.params_[4.2.1,4.3.0)

, Missing imported package org.apache.http.impl.protocol_[4.2.1,4.3.0)

] |

2017-02-07 12:01:16,432 | FATAL | Bootstrap Application | BootstrapApplication | Fatal exception caught during application bootstrap. Halting application. Message: /opt/vmware/vcloud-director/tmp/global749292125036625037properties -> /opt/vmware/vcloud-director/etc/global.properties: Invalid cross-device link

     at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:385)

     at sun.nio.fs.UnixFileSystemProvider.move(UnixCopyFile.java:262)

     at java.nio.file.Files.move(Files.java:1347)

     at com.vmware.vcloud.common.configuration.ConfigurationUtils.commitGlobalPropertiesConfiguration(ConfigurationUtils.java:101)

     at com.vmware.vcloud.common.configuration.ConfigurationUtils.commitGlobalPropertiesConfiguration(ConfigurationUtils.java:48)

     at com.vmware.vcloud.common.main.bootstrap.CopyResponesPropertiesStartupAction.call(CopyResponsesPropertiesStartupAction.java:61)

     at com.vmware.vcloud.common.main.bootstrap.CopyResponesPropertiesStartupAction.call(CopyResponsesPropertiesStartupAction.java:31)

     at com.vmware.vcloud.common.main.DelegatingStartupActioncall(DelegatingStartupAction.java:33)

     at com.vmware.vcloud.common.main.DelegatingStartupActioncall(DelegatingStartupAction.java:21)

     at com.vmware.vcloud.common.main.bootstrap.BootstrapApplication.start(BootstrapApplication.java:138)

     at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandl...

We are currently running vSphere 5.5, vCD 8.0.1 and vCNS 5.5.4.3. My goal is to get on vCD 8.10 and NSX 6.2.x but I would rather not upgrade both components at the same time.  According to the documentation at VMware NSX for vSphere 6.2 Documentation Center however "If you are using vCloud Director earlier than 8.10, you must not upgrade vShield Edge."

This leaves me wondering if there is an upgrade path I can take that will perhaps require multiple upgrades, but can that can take place one at a time. For example is there an earlier version of NSX that I can migrate to and manage edges on using vCD 8.0.1 and vCD 8.10? That would allow me to migrate to NSX, make sure everything is working for a few days or even a week before performing my next vCD upgrade.

Wasn't sure whether this was best in the PowerCLI area or here, but figured it's much more relevant to vCloud Director.

I was frustrated with the lack of options to manipulate independent disks in our vCloud environment and wanted to be able to give some of our customers an easier mechanism to manage these. (Right now the only option is directly via the vCloud API).

So I wrote a PowerShell module which extends PowerCLI with the ability to manage independent disks (list, create, delete, attach and detach) which is now available at https://github.com/jondwaite/cidisk. The readme file has documentation of each cmdlet and parameter information.

As always, test in a non-production environment before relying on this and please be aware that independent disks are not captured by VM snapshots (and so won't be in VM backups that rely on VM snapshots either).

Appreciate any bug reports / issues, hopefully this will be useful to someone else out there, I've also written up example usage on my blog at http://kiwicloud.ninja/2017/02/using-independent-disks-in-vcloud/

Jon

Hello,

I receive an error when I'm trying to set the IP address for VCD Public Console Proxy form the web UI.

When I want to confirm changes with the apply button the following error occurs - "class java.lang.NullPointerException".

The logfile is showing some additional information, but this doesn't help me to solve the problem.

DEBUG    | pool-jetty-76             | AuthorizationMethodInterceptor | Authorizing method: public abstract void com.vmware.vcloud.api.presentation.service.SystemService.updateSystemSettings(com.vmware.vcloud.api.presentation.entity.system.SystemSettings). |

DEBUG    | pool-jetty-76             | InventoryCacheManagerImpl      | [vcId = c3326df3-c82b-4af3-960d-e3e8fb95cccc] Inventory cache miss for [resgroup-371]. |

DEBUG    | pool-jetty-76             | InventoryCacheManagerImpl      | [vcId = c3326df3-c82b-4af3-960d-e3e8fb95cccc] Inventory miss for [resgroup-371]. |

DEBUG    | pool-jetty-76             | ThreadCleanerInterceptor       | Exiting Compute Fabric public method. Compute Fabric Conversation Factory thread context cleared. |

WARN     | pool-jetty-76             | BatchTask                      | Error executing backend call. | java.lang.NullPointerException

The version of vCloud Director is 5.5 and the OS is CentOS.

I hope someone can help.

I've done some testing with this and think I know the answer (that we need to power-off the vApps and move), but has anyone successfully migrated running VMs/vApps in a VDC to a new pVDC?

We're running 8.10.1 vCD-SP and have a 'shared' hosting pVDC which contains many customer VDCs. For one customer specifically we need to migrate their VDCs to a dedicated vSphere cluster which has been defined as a new vCD pVDC.

I can create new VDCs for this customer from the new pVDC with no issues, but can't see any way to live-migrate their vApps/VMs to the new VDCs without outage/power-off which is going to be extremely inconvenient for this customer.

All hosts (in the original and new pVDCs) have common access to the networking and datastores backing the VMs.

We can't 'merge' the pVDCs (and retire the current one afterwards) as other customers will remain on the original/current pVDC once this customer's VDCs are migrated off.

The reason to do this is licensing - we need to get this customer's VMs to a dedicated host cluster for licensing reasons, otherwise they are perfectly happy with the current environment.

Thanks in advance for any ideas...

Hallo,

I've installed vcloud director 8.10 with NSX 6.2 and I wish to enable Dynamic routing protocols (BGP OSPF) from inside the vcloud director gui.

Is id possible? If yes, where ?

Hi,

What is the different between vCD and vRA ? If I am a SP why do I need to use vCD not vRA what is opetion in vCD not in vRA

Thank you

Hi,

Does anyone have expirience with securing vCloud Director login page for tenants with 2 factor authentication? Is there any 3rd party solution which "just works" or is there any other method of implementing 2FA with vCloud Director? I've searched google and didn't find much about this topic.

Hello all,

We have Vcloud Director running on 5.5.3 and we have 3 VDC's.

On VDC1 I have created a OVA file from which I can deploy VM's.

I have used the template, let say, test01, for vm spgb001 in VDC1.

Now in VDC2 I want to create Vapp and when I want to select template test01

it's listed as  spgb001??

In VDC1 I  do not have that problem.

Does anyone know what's happening here??

Regards,

Johan

Hi all!

hope you can help me, getting crazy here.

I'm currently working with latest vCloud Director in a LAB and try to stage some machines.

I uploaded the ISO Files to a library, Status is ready:

When i try to attach this ISO to a VM, i cannot choose it:

Any hint ?

Are there any possibility that the SQL mirroring or AlwaysOn HA for Microsoft SQL Server will be supported as a database high-availability option? Currently, it seems only SQL failover cluster is supported, but we are running a NFS-only environment, and can't create iSCSI LUNs required for failover clustering.

It seems the main reason might be due to vCloud Director using JTDS driver for connecting to SQL Server when I look at the JDBC URL string on the global.properties file, but Microsoft's version of JDBC driver does support connecting and setting up failover instance for SQL mirroring, or redirecting to active instance when connecting to SQL instance with AlwaysOn replicas set up. Is switching JDBC drivers a possibility? The Microsoft JDBC driver is now on GitHub under MIT license, and they just recently implemented the socket timeout option on their 6.1.2 preview driver which seemed to be one of the things missing that was available on JTDS driver.

After installing vCD I'm unable to navigate to the configured hostname/port to finish the setup. I'm getting a 404 page.

I noticed that the services had not started so I did this via:

service vmware-vcd start

But after this I have the same issue.

The cell.log file shows

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0

Bootstrap application: start

Bundle-Id: 214, Bundle-SymbolicName: jline, Bundle Location: initial@reference:file:jline/jline-2.7.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package org.fusesource.jansi.internal_0.0.0

]

Bundle-Id: 225, Bundle-SymbolicName: client-toolkit, Bundle Location: initial@reference:file:com/vmware/vcloud/client-toolkit/1.0.0/client-toolkit-1.0.0.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package com.vmware.vim.query.client_[0.0.0,1.0.0)

]

Bundle-Id: 248, Bundle-SymbolicName: cell-management-tool-vcd-client, Bundle Location: initial@reference:file:com/vmware/vcloud/cell-management-tool-vcd-client/1.5.0/cell-management-tool-vcd-client-1.5.0.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package com.vmware.vcloud.clienttoolkit.vc_0.0.0

]

All required system properties are present

An unspecified error occurred during application start

All required local configuration properties are present

Successfully bound network port: 80 on host address: 192.168.1.1

Successfully bound network port: 443 on host address: 192.168.1.1

Successfully bound network port: 8999 on host address: 192.168.1.1

All required local configuration properties are present

Successfully initialized system cryptography

Successfully configured HTTP SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/certificates

Current locale "en" verified successfully.

Bootstrap application: complete

Application startup event: Waiting for subsystem 'com.vmware.vcloud.common.core'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.cloud-proxy-server'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.computeservice.broker'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.consoleproxy'

Application startup event: Subsystem 'com.vmware.vcloud.cloud-proxy-server' startup initiated.

Application startup begins: Subsystem 'com.vmware.vcloud.cloud-proxy-server' at 27/02/17 17:29

Application startup event: Subsystem 'com.vmware.vcloud.common.core' startup initiated.

Application startup begins: Subsystem 'com.vmware.vcloud.common.core' at 27/02/17 17:29

Successfully connected to database: jdbc:jtds:sqlserver://192.168.1.2:1433/vcloud;socketTimeout=90

Successfully initialized system cryptography

Application Initialization: 'com.vmware.vcloud.common.core' 4% complete. Subsystem 'com.vmware.vcloud.common-cell-impl' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 20% complete. Subsystem 'com.vmware.vcloud.common-cell-impl' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 40% complete. Subsystem 'com.vmware.vcloud.cloud-proxy-services' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 60% complete. Subsystem 'com.vmware.vcloud.hybrid-networking' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 80% complete. Subsystem 'com.vmware.vcloud.hbr-aware-plugin' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 100% complete. Subsystem 'com.vmware.vcloud.cloud-proxy-web' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' complete. Server is ready in 0:44 (minutes:seconds)

Application startup event: Subsystem 'com.vmware.vcloud.consoleproxy' startup initiated.

Successfully configured Console Proxy SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/proxycertificates

Application Initialization: 'com.vmware.vcloud.common.core' 8% complete. Subsystem 'com.vmware.vcloud.common-util' started

Application Initialization: 'com.vmware.vcloud.common.core' 13% complete. Subsystem 'com.vmware.vcloud.common-sso-patch' started

Application Initialization: 'com.vmware.vcloud.common.core' 17% complete. Subsystem 'com.vmware.vcloud.api-framework' started

Application Initialization: 'com.vmware.vcloud.common.core' 21% complete. Subsystem 'com.vmware.vcloud.common-vmomi' started

Application Initialization: 'com.vmware.vcloud.common.core' 26% complete. Subsystem 'com.vmware.vcloud.jax-rs-activator' started

Application Initialization: 'com.vmware.vcloud.common.core' 30% complete. Subsystem 'com.vmware.pbm.placementengine' started

Application Initialization: 'com.vmware.vcloud.common.core' 34% complete. Subsystem 'com.vmware.vcloud.vim-proxy' started

Application Initialization: 'com.vmware.vcloud.common.core' 39% complete. Subsystem 'com.vmware.vcloud.fabric.foundation' started

Application Initialization: 'com.vmware.vcloud.common.core' 43% complete. Subsystem 'com.vmware.vcloud.imagetransfer-server' started

Application Initialization: 'com.vmware.vcloud.common.core' 47% complete. Subsystem 'com.vmware.vcloud.fabric.storage' started

Application Initialization: 'com.vmware.vcloud.common.core' 52% complete. Subsystem 'com.vmware.vcloud.fabric.compute' started

Application Initialization: 'com.vmware.vcloud.common.core' 56% complete. Subsystem 'com.vmware.vcloud.backend-core-base' started

Application Initialization: 'com.vmware.vcloud.common.core' 60% complete. Subsystem 'com.vmware.vcloud.fabric.net' started

Application Initialization: 'com.vmware.vcloud.common.core' 65% complete. Subsystem 'com.vmware.vcloud.service-extensibility' started

Application Initialization: 'com.vmware.vcloud.common.core' 69% complete. Subsystem 'com.vmware.vcloud.backend-core' started

Application initialization detailed status report: 69% complete

    com.vmware.vcloud.common-cell-impl                           Subsystem Status: [COMPLETE]

    com.vmware.vcloud.common-util                                Subsystem Status: [COMPLETE]

    com.vmware.vcloud.common-sso-patch                           Subsystem Status: [COMPLETE]

    com.vmware.vcloud.api-framework                              Subsystem Status: [COMPLETE]

    com.vmware.vcloud.common-vmomi                               Subsystem Status: [COMPLETE]

    com.vmware.vcloud.jax-rs-activator                           Subsystem Status: [COMPLETE]

    com.vmware.pbm.placementengine                               Subsystem Status: [COMPLETE]

    com.vmware.vcloud.vim-proxy                                  Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.foundation                          Subsystem Status: [COMPLETE]

    com.vmware.vcloud.imagetransfer-server                       Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.storage                             Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.compute                             Subsystem Status: [COMPLETE]

    com.vmware.vcloud.backend-core-base                          Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.net                                 Subsystem Status: [COMPLETE]

    com.vmware.vcloud.service-extensibility                      Subsystem Status: [COMPLETE]

    com.vmware.vcloud.backend-core                               Subsystem Status: [COMPLETE]

    com.vmware.vcloud.vapp-lifecycle                             Subsystem Status: [WAITING]

    com.vmware.vcloud.content-library                            Subsystem Status: [WAITING]

    com.vmware.vcloud.presentation-api-impl                      Subsystem Status: [WAITING]

    com.vmware.vcloud.metrics-core                               Subsystem Status: [WAITING]

    com.vmware.vcloud.rest-api-handlers                          Subsystem Status: [WAITING]

    com.vmware.vcloud.jax-rs-servlet                             Subsystem Status: [WAITING]

    com.vmware.vcloud.ui-vcloud-webapp                           Subsystem Status: [WAITING]

 

 

Application Initialization: 'com.vmware.vcloud.common.core' 73% complete. Subsystem 'com.vmware.vcloud.vapp-lifecycle' started

Application Initialization: 'com.vmware.vcloud.common.core' 78% complete. Subsystem 'com.vmware.vcloud.content-library' started

Application Initialization: 'com.vmware.vcloud.common.core' 82% complete. Subsystem 'com.vmware.vcloud.presentation-api-impl' started

Application Initialization: 'com.vmware.vcloud.common.core' 86% complete. Subsystem 'com.vmware.vcloud.metrics-core' started

Application Initialization: 'com.vmware.vcloud.common.core' 91% complete. Subsystem 'com.vmware.vcloud.rest-api-handlers' started

Application startup event: Subsystem 'com.vmware.vcloud.computeservice.broker' startup initiated.

Application startup begins: Subsystem 'com.vmware.vcloud.computeservice.broker' at 27/02/17 17:31

Application Initialization: 'com.vmware.vcloud.computeservice.broker' 50% complete. Subsystem 'com.vmware.vcloud.backend-core-base' started

Application Initialization: 'com.vmware.vcloud.computeservice.broker' 100% complete. Subsystem 'com.vmware.vcloud.computeservice.broker' started

Application Initialization: 'com.vmware.vcloud.computeservice.broker' complete. Server is ready in 0:00 (minutes:seconds)

Application Initialization: 'com.vmware.vcloud.common.core' 95% complete. Subsystem 'com.vmware.vcloud.jax-rs-servlet' started

Application Initialization: 'com.vmware.vcloud.common.core' 100% complete. Subsystem 'com.vmware.vcloud.ui-vcloud-webapp' started

Application Initialization: 'com.vmware.vcloud.common.core' complete. Server is ready in 2:11 (minutes:seconds)

Successfully handled all queued events.

Successfully verified transfer spooling area: /opt/vmware/vcloud-director/data/transfer

and the vcloud-container-debug.log file shows:

2017-02-27 17:31:02,894 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:03,669 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:03,692 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:04,081 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:04,096 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:34,290 | WARN     | Spring Context: com.vmware.vcloud.vapp-lifecycle | StorageProfileValidationJob    | Storage profile job already scheduled. |

2017-02-27 17:31:34,885 | WARN     | Spring Context: com.vmware.vcloud.content-library | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:51,072 | WARN     | pool-async-email-sender-17-thread-1 | EmailManager                   | Failed to send email because SMTP server is not configured. |

2017-02-27 17:31:54,524 | WARN     | Quartz-pool-1-thread-1    | EventDispatcherImpl            | No transaction enclosing call to postTransactionalEvent: eventType=com/vmware/vcloud/event/cell/failover |

Perhaps something has been missed on the installation?

Hello,

I need to move away a whole vCD Provider VDC and its OrgVDC's from Fast Provisioning to Full VMs. So I changed all OrgVDC's and tried to consolidate all Linked Clones with my PowerCLI Script:

# Consolidate VMs
$vms = Get-OrgVdc | Get-CIVM | where {$_.ExtensionData.VCloudExtension.any.VirtualDisksMaxChainLength -ge 1} | Get-CIView
$vms_Success = @()
$vms_Failed = @()
Foreach ($vm in $vms) {    Write-Output "Processing VM: $($VM.name)"    try {        $task = $vm.Consolidate_Task()        Start-Sleep 1        while ((Get-Task -Id $task.Id).State -ne "Success" ) {            Write-Output "$($vm.name) - Percent: $((Get-Task -Id $task.Id).PercentComplete) / State: $((Get-Task -Id $task.Id).State)"            Start-Sleep 1            }        $vms_Success += $vm        } catch {            Write-Output "      $($vm.name) Failed!"            $vms_Failed += $vm            } 
 }

But consolidation via vCD API is ony possible for VMs in State 8 (POWERED_OFF ) and 3 (SUSPENDED). Most of the VMs are in State 4 (POWERED_ON), there is no consolidation possible...

Any workaround or recommendation how to handle that situation?

I have a newly deployed instance of vCD 8.20 and NSX 6.3.0. Everything on the surface looks OK, however I am not seeing any network port groups being created on the DVS.

When I create a Org Network I am getting the following error:

[ bc3f151b-14ba-4985-80d3-dfcc7717e10a ] Cannot deploy organization VDC network  (39980b71-9ff1-4ea0-8b27-60174bd2855b)

com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Cannot create network "dvs.VCDVSAudi-LAN-c20aebbb-8e78-43a1-9a50-fb38bcf9e6aa" from VXLAN network pool "urn:uuid:616b1fe6-8bb7-48e7-a743-ddcce4aa950a". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Cannot create network "dvs.VCDVSAudi-LAN-c20aebbb-8e78-43a1-9a50-fb38bcf9e6aa" from VXLAN network pool "urn:uuid:616b1fe6-8bb7-48e7-a743-ddcce4aa950a". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- Cannot create network "dvs.VCDVSAudi-LAN-c20aebbb-8e78-43a1-9a50-fb38bcf9e6aa" from VXLAN network pool "urn:uuid:616b1fe6-8bb7-48e7-a743-ddcce4aa950a". Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.

- Unable to allocate an available resource for resource type Universal Multicast Address Pool., error code 844

When I check the Network Pools - the VXLAN network is GREEN check. vCenter status is GREEN check and I have tried re-entering the user and password for "vShield Manager" even thou we are using NSX. It connects fine it seems. All the Hosts in the host view are GREEN and vCD Agent is deployed.

NSX Manager config looks good, Lookup service and vCenter registration are fine. And I can deploy edges and create networks via vCenter, just appears to be anything from vCD to NSX is no go.

Anybody have any ideas, or suggestions on where I should be looking?

Thanks!

A fresh vCD 8.1 install is having issues with console access to VMs within a vDC. I'm using a shared IP for the cell, https on one port and console proxy on another. Both NATed from public network to the private DMZ. All vCD config uses the private IP or the vCD Cell server.

vCD is installed on a CentOS 7 server

When I open a console in Chrome, I get "Disconnected" and just a white popup with some options at the top (Power on etc)

In the Developer console (F12) I see:

WebSocket connection to 'wss://EXTERNAL-FQDN/902;cst.........' failed: Error during WebSocket handshake: Unexpected response code: 404

I'm not using port 902 for HTTPS or the Proxy Console, so suspect this is something to do with communication between VDC and VC/ESXi

The console proxy port isn't showing up on the perimeter firewall logs but the HTTPS port set for the UI is, so perhaps the console proxy traffic is encapsulated within the HTTPs traffic? -- Not sure on this one really.

Have tried disabling the vCD server firewall

There is nothing in cell.log

The console-proxy.log file just shows a successful bind of the console port to the interface.

There are no certificate errors on the page (All signed by a trusted CA)

On the IE developer console, I'm getting "Connecting...", a black screen and the below, which is pointing to a possible certificate issue but I can't think where the problem could be other than that I'm using a wildcard SSL cert on for the FQDN?

An error occurred that affected the security of the connection

If I log out and back in again, then open up a console I sometimes get this in the IE developer console:

Object doesn't suport property or method "isReadyToStart"

After reading this vCloud and wildcard cert, it looks like wildcard certs are okay to use now so I'm at a loss!

Any advice is appreciated.