UCS Director integration with APIC is over HTTP(Port 80) or HTTPS (Port 443) protocol.
UCS Director acts as a client and APIC controller acts as a server. (API provider)
If only HTTPS is enabled on APIC controller, then you need to open port 443 on firewall (Direction is: UCSD --> APIC)
Since UCSD is client here, it uses any random port.
As of today there is "NO" integration from APIC controller back to UCS Director, i.e. APIC controller is calling UCS Director API over HTTPs. So you do not need to open any firewall port from APIC to UCS Director.
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 18.104.22.168
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: firstname.lastname@example.org)
Please watch video for more details: