Hi friends,
I am trying to configure vCloud Director 9.5.3 with vSphere 6.5 and NSX-t 2.3. The bellow error appear after providing NSX-T2.3 details.
Please help me if you have any solutions.
[ 899ee1b3-734e-4409-bf78-e682710b0b41 ] Failed to connect to the NSX Manager
- /api/2.0/services/vcconfig, error code 98
Regards,
Kishor Kulkarni
Hello guys,
We are testing vCAV 3.0 in order to migrate or protect VMs from on premise to vCD.
So on premise site, when configuring the tenant appliance , setting the FQDN for the public api endoint for vCAC is not working "timeout has occured" , instead setting directly the public ip , it works.
By the way, connecting directly from the browser on the endpoint of the vCAV with FQDN is not working "time out", direct ip it works.
The hostname on the tunnel appliance is the FQDN used for the endpoint vCAV, and we have import a wildcertifcat.
Our lab is working , failover and DR are working perfectly, but something is not working well with the FQDN, in production it is better to use FQDN.
Guys have any ideas ?
Best regards
Hello.
We are using vCloud Director 9.5 and 9.7 and we would like integrate with "vROPS Tenant APP for vCloud Director 2.2".
Two VMs was deployed . First this is vROPS 7.5 and 2nd VM is"vROPS Tenant APP for vCloud Director 2.2"
Now everything working fine but we are used trial version. We wanted to use license key "vRealize Operations Chargeback per Processor".
After use this key
and logout from vROPS we lost access to GUI. We have only warning:
Insufficient License "For access to the product UI, please consider upgrading to the higher (Std/Adv/Ent) edition. Note that data collection does not stop due to an insufficient license."
If this is normal ? im woried what will happend when we would like reconfigure something inside vrops. But maybe this by design
Our components versions:
vRealize-Operations-Manager-Appliance-7.5.0.13165949_OVF10.ova
vROps-Tenant-App-for-vCD-2.2.0.29049-13473471_OVF10.ova
vmware-MPforVCD-5.1.0-13477673.pak
vmware-MPforNSX-vSphere-3.5.2-8185708.pak
Greetings
Sebastian
I have most of the environment on self gen certs except for the VCD cells which are on a proper SSL public wildcard cert.
When I run the Initial Setup from vCloud Availability on step 3. vCloud Director, when I enter the URL and VCD administrator@system with the password I use to log in, it gives an error:
Could not find SSL/X509 certificate from "https://my-vcd-url/api" (I changed the URL name for this post)
I thought perhaps the vCAV needed the cert imported, so I then imported the cert under https://url:8441 backend.
Note, I don't have the vCAV setup setup on DNS for the public name, merely internal DNS.
So I am not sure if I needed to import the wildcard cert and if I did, it stands to reason that like with the VCD setup , I need to change to the respective domain name for each vCAV appliance.
Anyone seen this issue?
Hi all,
I'm trying to enable the federation on vCloud using VMWare Identity Manager as SAML Identity Provider.
The SAML authentication seems to work
vcloud-container-debug.log.3:2019-06-18 17:14:15,557 | INFO | pool-jetty-66 | SAMLDefaultLogger | AuthNResponse;SUCCESS;10.100.120.10;pippo;https://vidm.rsa.lab/SAAS/API/1.0/GET/metadata/idp.xml;pippo;; | requestId=a7484b3d-5a9c-483d-917e-426dce95a99b,request=POST https://10.100.120.20/cloud/org/pippo/saml/SSO/alias/vcd,requestTime=1560870855030,remoteAddress=10.100.120.10:52141,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/2010...,accept=text/html application/xhtml+xml application/xml;q 0.9 */*;q 0.8
The issue is in importing users:
vcloud-container-debug.log:2019-06-19 11:23:09,744 | DEBUG | pool-jetty-84 | AbstractEventBuilder | Source object was null when constructing com/vmware/vcloud/event/user/import | requestId=47ae118e-3e54-45fe-a644-b28e305112cc,request=POST https://vcd.rsa.lab/cloud/amfsecure,requestTime=1560936189703,remoteAddress=10.100.120.10:51770,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/2010...,accept=*/* method=orgService.importUser
vcloud-container-debug.log:2019-06-19 11:23:09,744 | WARN | pool-jetty-84 | EventDispatcherImpl | No transaction enclosing call to postTransactionalEvent: eventType=com/vmware/vcloud/event/user/import | requestId=47ae118e-3e54-45fe-a644-b28e305112cc,request=POST https://vcd.rsa.lab/cloud/amfsecure,requestTime=1560936189703,remoteAddress=10.100.120.10:51770,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/2010...,accept=*/* method=orgService.importUser
vcloud-container-debug.log:2019-06-19 11:23:09,745 | DEBUG | pool-jetty-84 | EventDispatcherImpl | No transaction enclosing call to postTransactionalEvent: stackTrace=com.vmware.vcloud.management.system.OrgServiceImpl.postEvent(OrgServiceImpl.java:3025)#com.vmware.vcloud.management.system.OrgServiceImpl.importUser(OrgServiceImpl.java:1659)#sun.reflect.GeneratedMethodAccessor1727.invoke(Unknown Source)#sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)#java.lang.reflect.Method.invoke(Method.java:498)#org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)#org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)# | requestId=47ae118e-3e54-45fe-a644-b28e305112cc,request=POST https://vcd.rsa.lab/cloud/amfsecure,requestTime=1560936189703,remoteAddress=10.100.120.10:51770,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/2010...,accept=*/* method=orgService.importUser
vcloud-container-debug.log:2019-06-19 11:23:09,745 | WARN | pool-jetty-84 | AuditEventHandler | Missing value for placeholder 'entity.name' in event: Event [id=ce57442d-0b36-4a7a-ad65-b79017b5e09e, timestamp=1560936189744, type=com/vmware/vcloud/event/user/import, serviceNamespace=com.vmware.vcloud, properties={
vcloud-container-debug.log:2019-06-19 11:23:09,751 | WARN | pool-jetty-84 | BatchTask | Error executing backend call. | requestId=47ae118e-3e54-45fe-a644-b28e305112cc,request=POST https://vcd.rsa.lab/cloud/amfsecure,requestTime=1560936189703,remoteAddress=10.100.120.10:51770,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/2010...,accept=*/* method=orgService.importUser
What does 'entity.name' refers?
Thanks,
Alessandro
Hi,
I have brought VCD9.5 and trying to attach NSX-T 2.3 to it,
Support matrix shows its supported. but when i try to attach i am getting below error.
Can i get some support on resolving the same ?
Failed to connect to the NSX-Manager
-/api/2.0/services/vcconfig, error code 98
Thanks & Regards
Velann
If this is correct state of solution 0 metrics and resources ?
Can compare somebody? with your environment ?
thanks
Sebastian
Hello,
When configuring the pVDC, we are unable to see datastore behind a datastore cluster (with or without SDRS).
But if we move the datastore out of the datastore cluster, we can see it throught the SP.
All datasore used tags for matching the SP, and each SP have SIOC configured for max IOPS by vmdk.
vCD 9.7 is normally compatible with datastore cluster ? Or i missed something.
Best regards
Hi,
Im using this REST command to get a list of all vcd users:
curl -i -k -H "Accept:application/*+xml;version=31.0" -H "x-vcloud-authorization:f9c49bfdghkjkfgd4ebf4d7e2d89c17b" -X GET https://my-vcd/api/query?type=adminUser
the problem is im getting only the first page.
<QueryResultRecords xmlns="http://www.vmware.com/vcloud/v1.5" xmlname="adminUser" page="1" pageSize="25" total="43" href="https://my-vcd/api/query?type=adminUser&page=1&pageSize=25&format=records"> <Link rel="nextPage" href="https://my-vcd/api/query?type=adminUser&page=2&pageSize=25&format=records" type="application/vnd.vmware.vcloud.query.records+xml"/> <Link rel="lastPage" href="https://my-vcd/api/query?type=adminUser&page=2&pageSize=25&format=records" type="application/vnd.vmware.vcloud.query.records+xml"/> <Link rel="alternate" href="https://my-vcd/api/query?type=adminUser&page=1&pageSize=25&format=references" type="application/vnd.vmware.vcloud.query.references+xml"/>
this info is from the header.
as you can see I have total of 43 users spread into 2 pages.
I have read the REST manual and tried the following:
curl -i -k -H "Accept:application/*+xml;version=31.0" -H "x-vcloud-authorization:f9c49bfdghkjkfgd4ebf4d7e2d89c17b" -X GET https://my-vcd/api/query?type=adminUser&page=2
curl -i -k -H "Accept:application/*+xml;version=31.0" -H "x-vcloud-authorization:f9c49bfdghkjkfgd4ebf4d7e2d89c17b" -X GET https://my-vcd/api/query?type=adminUser&pageSize=128 (128 is the max entries number per page)
but I keep getting the first page..
I wish to get all 43 users in the same page.
any help ?
vCloud Director versions in play are:
Old Build: 9.1.0.8825784
New Build: 9.5.0.12982517
I had previously been scripting uploads from the vCD Cell's Linux system using VMware ovftool 4.3.0 (build-12320924).
I had my command saved in history for syntax on uploading to vCloud Director 9.1, and every so often I sync new ISOs from an NFS mount into vCloud Director.
As of updating to 9.5 yesterday, the ovftool uploads fail with the only output being:
Transfer Failed
Error: Failed to send http data
Completed with errors
I finally fired up the HTML5 client as a workaround ... which seems to have loaded the ISO to catalog.
Just curious if anyone has seen something similar.
Hi all,
We just deployed a new 9.5 appliance into a brownfield vCenter with NSX (this is a Lab) and everything is working as expected.
While testing I noticed that the vCD created VMs in vCenter no longer have the 33 character vCloud Director object ID "VMNAME (048613d6-b485-4e3d-a626-8888b516e30e)" appended to VM names (vapps and edges do btw), instead they have a "-" then a random 4 character string "VMNAME-aUGX" is added to the VM name. Additionally the VM discovery function does not alter the VM name in vCenter like it did in 9.1 on import.
Is this expected new behavior or is there another config item at play here? I cant find any documentation related to this.
(vCenter 6.7.0.30000 Build 13007398, NSX 6.4.513282012, vCD 9.5.0.12982517 (updating next))
Thanks in advance
Hi,
i'm currently evaluation vCD 9.7 and can't edit/create roles via H5 client.
In both cases, loading of the rights properites failes and nothing is displays:
Script errors are thrown:
https://vcd.xxxxxx.de/cloudapi/1.0.0/rights?page=1&pageSize=128&links=true -> 502 Bad Gateway
Also Postman shows me the "BAD GATEWAY" error:
But if i remove the filter from the url "https://vcd.xxxx.de/cloudapi/1.0.0/rights i got an response
Hi Guys,
Im want to upload new media with REST API
but I cannot find how to do this.
I already tried to do that with powershell but everytime I tried I got "stream is too long" error so now Im trying my luck with REST API
Thanks.
Hi,
is it possible to change the Primary Resource Pool in a vCloud Provider Virtual Datacenter? I would like to make the Cluster-vCD-01 the pirmary Resource Pool.
What will happen if i delete the vSphere Cluster backing the Cluster-vCD-02 Resource Pool? I do not have any objects (vApps, vApp Templates, Catalogs, Edge devices and so on) in the Cluster-vCD-02 and the ESXi hosts are disabled in vCloud Director.
Thanks in advance.
//Magnus
Dear community,
We are pleased to notice you that vCloud Director Object Storage Extension 1.0is general available now!!
What's New?
VMware vCloud Director Object Storage Extension product enables cloud providers to bring their in-house & heterogeneous storage drives as a storage service and enables them to compete with public cloud storage offerings. More than that, this product will bring a number of valuable solutions for vCloud Director platform, e.g. backup and catalog sharing.
Download
vCloud Director Object Storage Extension 1.0
Release Notes
vCloud Director Object Storage Extension 1.0 Release Notes
Documentation
Installing and Configuring vCloud Director Object Storage Extension
vCloud Director Object Storage Extension User's Guide for Service Providers
vCloud Director Object Storage Extension User's Guide for Tenant Users
We are here helping you on the Object Storage Extension usage and hearing your feedbacks!
Hello, can someone give some advice on how I can evaluate vCloud Director 9.x?
Thanks,
Stephen
Hello,
We would like to apply differents permissions on specificy orgVDC owned by the same Org.
On GUI, the permissions seems only possible on Organization and not on the orgVDC.
Is there a way to do it ? API rest ? How ?
Best regards
I'm reaching out to the community because I'm at my wits end at deploying the vCD 9.7 OVA using all the methods available. Some info:
So I've tried the following:
When I login to the console, and view the setupvcd.log file I get the following:
And the contents of the update-appliance-type.log file
Both log files imply that I have not selected a valid cell type yet I am 100% certain that I chose "primary small" during the OVA deployment.
I can confirm that the vCD cell can reach the NFS transfer server, has mounted the NFS share and that it has successfully written to the directory.
I can also confirm that the user and group ownership are correct.
This times out and eventually I get to the VAMI screen saying the networking is not configured. Basically the vCD appliance is useless at this point. I cannot even login using the credentials I used during the OVA deployment. Nothing much can be done besides deleting the appliance and starting again.
Here's a copy of the ovftool syntax I'm using. It reflects the same properties I'm using during the UI deployment.
ovftool \
--noSSLVerify \
--acceptAllEulas \
--datastore='Datastore1' \
--allowAllExtraConfig \
--net:"eth0 Network"="VM Network" \
--net:"eth1 Network"="VM Network 2" \
--name=vCD \
--diskMode=thin \
--prop:"vami.ip0.VMware_vCloud_Director"="192.168.32.51" \
--prop:"vami.ip1.VMware_vCloud_Director"="10.0.0.51" \
--prop:"vami.DNS.VMware_vCloud_Director"="192.168.32.30" \
--prop:"vami.domain.VMware_vCloud_Director"="kfmlab.local" \
--prop:"vami.gateway.VMware_vCloud_Director"="192.168.32.2" \
--prop:"vami.netmask0.VMware_vCloud_Director"="255.255.255.0" \
--prop:"vami.netmask1.VMware_vCloud_Director"="255.255.255.0" \
--prop:"vami.searchpath.VMware_vCloud_Director"="kfmlab.local" \
--prop:"vcloudapp.enable_ssh.VMware_vCloud_Director"="True" \
--prop:"vcloudapp.expire_root_password.VMware_vCloud_Director"="False" \
--prop:"vcloudapp.nfs_mount.VMware_vCloud_Director"="192.168.32.61:/storage" \
--prop:"vcloudapp.ntp-server.VMware_vCloud_Director"="0.au.pool.ntp.org" \
--prop:"vcloudapp.varoot-password.VMware_vCloud_Director"="Password01!" \
--prop:"vcloudconf.db_pwd.VMware_vCloud_Director"="Password01!" \
--prop:"vcloudconf.admin_email.VMware_vCloud_Director"="admin@kfmlab.local" \
--prop:"vcloudconf.admin_fname.VMware_vCloud_Director"="vcdadmin" \
--prop:"vcloudconf.admin_pwd.VMware_vCloud_Director"="Password01!" \
--prop:"vcloudconf.admin_uname.VMware_vCloud_Director"="administrator" \
--prop:"vcloudconf.inst_id.VMware_vCloud_Director"="1" \
--prop:"vcloudconf.sys_name.VMware_vCloud_Director"="vcd01" \
--deploymentOption="primary-small"
Any help/assistance/ideas would be greatly appreciated!
When going to the vCloud Director tools download area and trying to download the Extender OVA, the website shows "couldn't complete the request". Does anyone have the same issue? Any help is appreciated.
Thanks!
Stephen
vCD 5.5.5.3153714
ESXi 5.5.0, 3248547
Networking Setup
Need
Environment where multiple of the same vApp will be running at the same time (identical VMs)
Issue
VMs are unable to connect to the Internet when in a fenced network
Testing
A vShield Edge device gets deployed when fencing is configured but VMs do not seem to be able to communicate to the External network. Any input or thoughts on the issue or direction where to look would be greatly appreciated.