TheITHollow
Enthusiast
Enthusiast

vCNS integration with vCAC 6.1

Jump to solution

I'm getting errors trying to setup vCNS 5.5.3 with my vCAC 6.1 setup.

These are both fresh installs, but I'm receiving the following errors in vCAC trying to do a data collection.

Workflow 'vSphereVCNSInventory' failed with the following exception: Could not reach vCenter Orchestrator endpoint {0}. Trying the next highest priority endpoint.

I found this KB Article relating to this error, noting an issue with data collection if you're using a load balancer in NSX which I am not.

VMware KB: Inventory data collection in VMware vCloud Networking and Security fails with the error: ...

According to the support matrix, these are supported.

https://www.vmware.com/pdf/vcloud-automation-center-61-support-matrix.pdf

Is anyone else having a similar error?

http://www.theithollow.com
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
JamesMW
Enthusiast
Enthusiast

It sounds like the vCO endpoint in vCAC is still mis-configured.

Is the URL path for vCO: https://<FQDN to vCO Server>:8281/vco/

And the custom property VMware.VCenterOrchestrator.Priority added to the endpoint?

View solution in original post

0 Kudos
8 Replies
JamesMW
Enthusiast
Enthusiast

Do you have a vCO endpoint configured in vCAC?

The NSX/vCNS integration for vCAC 6.1 calls vCO workflows that are part of the NSX plugin. That means you have to configure a vCO endpoint that has the NSX plugin installed in order for vCAC to start configuring NSX/vCNS components.

-James

Filin_K
VMware Employee
VMware Employee

I guess you need add vCO as endpoint first, before add NSX or vCNS.

You can add internal vCO from VCAC appl.

For example: https://srv-vcacapp01.home.lab:8281/vco

Kirill.

TheITHollow
Enthusiast
Enthusiast

So an update.

I removed the vcns checkbox and still get the error.  I think my vCAC server can't communicate with vCO but I don't know why.

I rebuilt both vCO and vCAC and made sure they were all on the same SSO Server but that didn't make any difference.  Also a complete rebuild of both vCAC and vCO left me with the same error.

Is anyone successfully using vCO 5.5.3 and vCAC 6.1 together?

Workflow 'vSphereVCNSInventory' failed with the following exception: Could not reach vCenter Orchestrator endpoint {0}. Trying the next highest priority endpoint.

http://www.theithollow.com
0 Kudos
quantum_2
Enthusiast
Enthusiast

I wonder if somehow the load balancing in the vCNS is set to "IP hash" by default?

http://www.definit.co.uk/2014/06/vcac-6-0-build-out-to-distributed-model-part-3-1-configure-load-bal...

0 Kudos
Craig_G2
Hot Shot
Hot Shot

Two things that got me:

1: Firewall from vcac/iaas to vco

2: You need to install the NSX plugin on vco if it is an external instance

Download VMware NSX for vSphere

Good luck!

0 Kudos
TheITHollow
Enthusiast
Enthusiast

No firewalls in place, and the NSX plugin is installed on my external vCO appliance.

http://www.theithollow.com
0 Kudos
JamesMW
Enthusiast
Enthusiast

It sounds like the vCO endpoint in vCAC is still mis-configured.

Is the URL path for vCO: https://<FQDN to vCO Server>:8281/vco/

And the custom property VMware.VCenterOrchestrator.Priority added to the endpoint?

View solution in original post

0 Kudos
TheITHollow
Enthusiast
Enthusiast

wow, really embarrassed.

I had the https://vcoserver.domain.local:8281 but not a /vco at the end.

Simple fix that I should've found.

Thanks for everyones help.

http://www.theithollow.com
0 Kudos