java.lang.IllegalStateException: Unable to bind to 10.42.41.68:443. Permission denied. Is this address available on this machine?
This error tells me you have something awry with the cell and console IP address. Do you know how it was configured? Check your ifconfig and find out how you guys are configuring console/proxy access - your healthy cells might be good guiding lights.
Hi
IM trying to understand why during creating
We are Service provider for vCD and environment looks like today:
VCSA6.5 u2d
ESXi: 6.5.0, 8935087, U2b
NSX: 6.4.3 3.9927516
vCD: 9.5
vCD PostgreSQL10
vRLI 4.7
In some ORG and edges, we have an issue during creating ORG routed network.
ERROR: "class java.lang.NullPointerException" what is not clear for us.
Im not sure where should i start looking for some details...
Thanks
vSebastian.net
Hi Guys
We have a vCloudDirector 9.5 managed vCenter (6.7) with NSX for vSphere (6.4.4).
Now we had to install a new second vCenter for another vmware solution (it can not be used with a vCD managed vCenter.)
i created a cross vCenter NSX Installation (the new vCenter without vCloudDirector is bound the secondary nsx manager), with a universal transportzone.
Everything works fine. I can create new networks in NSX, can attach them to my vCloudDirectors Edge Gateway, and on the oder side to some VM's in the other vCenter.
it's great.
But 2 points:
-how can i create the new universal-transport-zone networks from vcloud director?
-i added the universal transport zone in vCloud Director (add Networkpool), but i can't assign the new pool to virtal dataceters.
How can i move some vCloudDirector networks the new vxlan pool with the universal transportzone?
thanks for help.
Hi TMoS86,
vCD 9.5 introduced the capabilities to provide cross-vCenter NSX (or what we call Cross-VDC networking) in a self-service manner. There is some initial setup required and we laid these out in a blog series here: VMware vCloud Director 9.5 - Cross-VDC Networking Blog Series - Intro and Use Cases - VMware Cloud Provider Blog
Also, I just posted a few videos that walkthrough the setup and testing - vCloud Director 9.5 Cross-VDC Networking Video Walkthrough Series
Enjoy,
-Daniel
Thank you for your reply.
this concerns standard cross-vdc-networking.
i think this is not possible for us because:
(please correct me if this is wrong.)
-we only have 1 vcloud director and no DLR.
-One vCenter is vCloudDirector managed.
-the other vCenter is Horizon DaaS managed.
this means: this second site can't be vCloud Director managed.
Therefore is there no other org-vdc that i can group to the vCD org-vdc to use cross vdc-networking. Right?
I just want to bind some vdc-org networks to the universal TZ insted of the local TZ (to use it directly in the other cluster).
Therefore is there no other org-vdc that i can group to the vCD org-vdc to use cross vdc-networking. Right?
<DCP> Right </DCP>
I just want to bind some vdc-org networks to the universal TZ insted of the local TZ (to use it directly in the other cluster).
<DCP> You will need to do this from an external network - create the universal LS and expose it to the vCD orgVDC as an External Network. That would be the only available option at this time. </DCP>
Thanks for your help, this is exactly what i need.
and thanks a lot for that: Cannot create external network in vCD 9 too. ;-)
You are welcome!
Hi,
Is it possible to move edge gateways from one vDC to another vDC if they are backed by different vCenter Servers, but same instance of vCloud Director?
If not, is it possible to download and restore edge gateway configs so that I don't need to recreate all rules again?
/Andreas
1. Not possible to move edges between oVDCs.
2. One could use the REST API and get the Edge config and then update the Edge firewall config on the newly created one.
Hello there,
We have a Edge gateway in vCD that have been removed in NSX. Now vCD unable to delete it.
How to sync changes between NSX and vCD ?
Hi,
I have two vCD installations, both seems to be working fine, however I have noticed that when doing certain tasks I get errors in the log file:
2019-01-16 10:31:01,654 | ERROR | auto-pool-eventPublishing-4-thread-1 | NotificationsAmqpPublisher | Error publishing notification to AMQP broker using connection 'amqp://vcd@<redacted>:5672/' | com.rabbitmq.client.AlreadyClosedException: channel is already closed due to channel error; protocol method: #method<channel.close>(reply-code=404, reply-text=NOT_FOUND - no exchange 'systemExchange' in vhost '/', class-id=60, method-id=40)
at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:198) at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:312) at com.rabbitmq.client.impl.ChannelN.basicPublish(ChannelN.java:664) at com.rabbitmq.client.impl.ChannelN.basicPublish(ChannelN.java:646) at com.rabbitmq.client.impl.ChannelN.basicPublish(ChannelN.java:636) at com.vmware.vcloud.common.event.impl.NotificationsAmqpPublisher.publishXmlNotification(NotificationsAmqpPublisher.java:124) at com.vmware.vcloud.common.event.impl.NotificationsAmqpPublisher.publishBatch(NotificationsAmqpPublisher.java:92) at com.vmware.vcloud.common.event.impl.AuditEventsAmqpPublisher.publishBatch(AuditEventsAmqpPublisher.java:124) at com.vmware.vcloud.common.event.impl.EventPublishingAgent.publishBatch(EventPublishingAgent.java:410) at com.vmware.vcloud.common.event.impl.EventPublishingAgent.publishOwnEvents(EventPublishingAgent.java:376) at com.vmware.vcloud.common.event.impl.EventPublishingAgent.access$800(EventPublishingAgent.java:60) at com.vmware.vcloud.common.event.impl.EventPublishingAgent$1.run(EventPublishingAgent.java:305) at com.vmware.vcloud.common.event.impl.EventPublishingAgent$1.run(EventPublishingAgent.java:287) at com.vmware.vcloud.common.persist.ConversationFactoryImpl.executeIsolated(ConversationFactoryImpl.java:329) at com.vmware.vcloud.common.event.impl.EventPublishingAgent.processEvents(EventPublishingAgent.java:287) at com.vmware.vcloud.common.event.impl.EventPublishingAgent.doPublishing(EventPublishingAgent.java:251) at com.vmware.vcloud.common.event.impl.EventPublishingAgent.access$000(EventPublishingAgent.java:60) at com.vmware.vcloud.common.event.impl.EventPublishingAgent$PublishingRunner.run(EventPublishingAgent.java:159) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-01-16 10:31:01,654 | WARN | auto-pool-eventPublishing-4-thread-1 | NotificationsAmqpPublisher | Error closing AMQP channel |
I have noticed this on my fresh lab install, as well as my 2 year old (and upgraded from 8.10 in steps with every new release) production install.
Looking at the RabbitMQ server, I can see the below exchanges:
Have anyone encountered this, and will it cause some kind of weird error?
/Andreas
Hello,
We are trying to set up a dual site vCloud Director with 9.5 version.
So we are testing cross VDC, we have configured two distinct orgVDC from two distinct provider VDC.
Each provider VDC comes from a vCenter RG / NSX Manager and we have only one instance vCD for both provider VDC.
We cannot configure the org VDC for Cross-VDC option, the option could not be enabled, we have followed several blogs and sources but still have an error.
Do we miss something ? Can we set up cross-vdc with only one instance VCD and two vCenter / NSX mananger ?
We are contacting Vmware for PSO services but the team is busy we need to wait until they can.
Best regards
This will require VCD-DB level clean up since the objects got directly deleted from NSX U.I
Can you provide further details on why Cross-VDC cannot be enabled and what errors you are seeing?
Please engage GSS and open a support request.
Hi Daniel,
We forgot to configure nsx manager options on both vCenter under our vCD portal, it is a little bit better, we can now enable VDC cross option on both org VDC.
We have now another error on the next step when configuring datacenter group. Here is the error :Unable to query VDCs from all sites for VDC Group LABJN
Can we configure Cross VDC with one instance vCD 9.5 and two vCenter / NSX ? Or maybe it is not possible with 9.5 version ?
Best regards
Is this error after attempting to create the Datacenter Group?
You should able to create a Datacenter group between two distinct pVDCs that have two distinct fault domains (Network Provider Scope) in the NSX Manager subtab -
Yes when we are configuring the datacenter group, we have the following error.
Cross-VDC is working with only one vDC instance ? Or we need to configure instance vCD on each site ?
I don't see any further error detail or screenshots.
Cross-VDC requires a minimum of two orgVDCs each with a respective fault domain. I've done extended testing between two vCD instances, but I just verified that it should work within a single vCD instance too (assuming you have separate providerVDCs each with a respective fault domain / network provider scope).
