Does anyone know why VMRC console is not starting? The end-user has a possibility to enable/disable and launch the console. Once enabled, when I try to open it I get the message: Resource Not Available. It is UCSD 6.7.4 and vCenter 6.7. VM is up and running. Any clues?
Case solved. UCSD wrongly shows connectivity to vCenter, even if there are some isuues. It's always green, until you perform Check Connectivity, then it updates. If there are any credential issues, the VMRC console will not work.
Greetings, glad the case was resolved. VMRC tunneling/ proxy through the UCS Director instance will be coming soon. This will allow the need for only UCSD to have connectivity to the ESXi hosts and not the client endpoint. Something to check out on the next connector pack update delivered through Intersight.
Since you mentioned Intersight when is it going to be a full-blown orchestrator? Customers are aware that Intersight is to replace UCSD, and they like orchestration which UCSD does, but they do not want to buy it anymore, since UCSD's future is blury. Any news?
In this article, we are providing sample work flows for the private cloud management solution. In our topology, ACI is used for network. We have placed the BMA outside the UCS fabric and connected through L3 switch. The UCS ser...
This workflow will log onto a WLC and find the connected AP(s) and test if they are on the network.
Validated on UCSD 188.8.131.52
This came together via several parties of people (Sasha, Russ and Michael Z.)
The original question was this:
When deploying open automation connector module and trying to create side menu per UCSD docs
This contribution was provided by: Sabina Al Farah.
Many thanks go out to Sabina Al Farah.
2 Workflows are attached :
Ceph - Setup Cluster - using Ansible - on RHEL
Ceph - Provision Block Storage
This is an integration example between UCSD and Cohesity.
Posted for Russ (Please direct questions to: email@example.com)
Please watch video for more details: