I’m trying to configure vCloud Director on centos  in my LAB,but I’m getting below error when I go through configure steps .So please can someone help me to fix the issue .

Connecting to the database: jdbc:jtds:sqlserver://192.168.10.11:1433/vCloud;socketTimeout=90;prepareSQL=2

Error: Response file is required to configure this cell

Please use the response file created by the first cell configuration

and rerun the $VCLOUD_HOME/bin/configure command with -r option

supplying the full pathname to the response file as the argument to that option.

@Configuration failed in some way; the vCloud Director service will not be

1. You should review the logs in /opt/vmware/vcloud-director/logs

for details.

When the product has been configured successfully you may manually start

the service using this command: service vmware-vcd start

[root@vcell01 bin]# tail -f /opt/vmware/vcloud-director/logs/cell.log

Bootstrap application: start

All required system properties are present

All required local configuration properties are present

Successfully bound network port: 80 on host address: null

Successfully bound network port: 443 on host address: null

Error starting application: Missing required local configuration property: consoleproxy.host.https

Recently, I setup a vCloud Director 8.10 and vCloud Connector 2.7.2 environment in lab.
I installed vCC 2.7.2 Server in private cloud and vCC 2.7.2 node in a vCloud Director tenant.  All the functions like template copy/deploy worked fine, but when I opened the VM's VMRC console, it displayed black screen.  The VMRC logs shown "connection timed out". My vCloud Director had two address 192.168.2.22 for HTTP, and 192.168.2.23 for Console Proxy. I guess it maybe a SSL issue between vCC node and Console Proxy.

Does anyone have these experience? Thanks.

Hi Team,

Please can you guide/suggest  me high level plan/design for how to proceed with Online Migration of Virtual Data Center since we have currently vCloud setup which are having IBM server and IBM Storage, now we planned to replace the IBM server and Storage  with Cisco UCS C series server and EMC Storage respectively .

So we need to have live migration to new esxi host and Storage. As we have already installed ESXi host on new host and kept in MM in Vcenter

Current setup

vCenter Version : 5.5.0

Esxi Host: IBM

Storage Connected to Host : IBM (SAN)

vCloud Director : 8..0.0

VMware vShiled Manager : 5.5.4.

Two distributed switch(VXLAN and External) in vCenter

Appreciate your help and assistance .

Happy new year .

Thanks in advance.

Hi all,

I created a discussion before on vRealize Orchestrator community but nobody could help me and somebody gave me an advise that vCloud Developer can help me. You can find details of my problem on following link. I have to fix this issue as soon as possible.

I am getting an error while running workflow named "vCloud Director - Add a Gateway" on vCO.

I think this is a BUG. If not, i don't know what can i do.

I need your advice.

Thanks.

Hi,

We recently upgraded our vCenter server and ESXi hosts to version 6 from 5.1 and our vCD server to version 5.5.6.

One step that I would have liked to also done was to change the vCenter server to a new Windows 2012R2 server. (from Windows 2008 R2)

This moving vCenter to a new server was not attempted due to the unknown repercussions that may occur within vCloud-Director.

Hopefully someone out there has been through this and can provide either a link to the information or the information itself.

Current Setup:

vCenter 6.02 on a physical server with all resources being attached to the vCD instance (Storage, memory, networking, CPU's etc...)

Multiple vApp's have been deployed from vCD and are running on the resources provided by the vCenter (there are also multiple catalog vApps saved)

What I would like to achieve is moving vCenter to a new virtual server and attaching the ESXi hosts and resources that are currently managed by the physical vCenter server. Then remove vCenter from the physical server remove it from the environment. It would be beneficial if this can be done with little or no impact on the current vCD environment. From what I understand, removing the current physical vCenter would also remove all the resources from vCD and this would effectively require that all resources would have to be added from the new virtual vCenter (even though they would be the same resources from the ESXi servers).

I am thinking that all vCD configurations and vApp's would have to be re-created but I am hoping that is not the case.

Any assistance or guidance would be appreciated.

Thanks in Advance.

Henry

Hi,

I want to run a script on vm that created by vCloud Director. I have read a lot of article about Customization Script but i guess somethings are wrong ;

I created a vm via vCloud Director Catalog. VM created and powered on successfully, it has an ip address and vm tools.

Then i powered off vm, on Guest OS Customization Tab of vm I enabled Customization checkbox, I changed password as P@ssword and put customization script as you can see at below ; Then, I powered on vm using "Power on and force Recustomization"... But, either password change and customization script is not  working.

This is very very basic folder creating script... Why customization is not working ?

@echo off

if "%1%" == "precustomization" (

echo Do precustomization tasks

) else if "%1%" == "postcustomization" (

echo %DATE% %TIME% > C:vm-is-ready

)

vCloud Director : 8.10.1

Created vm is Windows 2012 R2

All this is done on a test environment,

Want to allocate resource to an organisation, so i have to create a Provider VDC first,

well ,I am trying to create a Provider VDC, but im getting an error saying No resource pools were found for vCenter. I did create a resource pool, see screenshots below.

But it seems Vcloud Director can't see the resource pool.

There's a green tick next to my vcenter, so , looks that everything is fine, not sure what im doing wrong.

Hi there!

We are trying to connect our vcloud Director with Novell eDirectory (LDAP). When performing the ldap connection test we see that obviously the attributes are not matching, however if we change some attributes (to we think valid values) there is no change on that behaviour and vcloud director does not find any data.

We've been using tcpdump to track if the data is transfered correctly - and it is - so there must be a problem with the ldap attributes. Maybe anyone has setup vcloud director with edirectory before or has any tip for us.

Thanks, Best Regards

Hi all,

We are running VCD 8.10 and vCenter 6, and after checking the interoperability matrix / vCloud connector documentation, both solutions are not compatible with vCloud Connector 2.7. Is there any problem if we use it? Is there any alternative tool for VCD 8.10? What about CMP?

Thanks in advance!

Alicia

Does anyone know when VMX-11 VM's will be support?  I does not appear to be supported with 8.10.1.

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...