The goal of this document is to explain the procedures for integrating CloudCenter with ACI via HTTP or HTTPS. By default the APIC is shipped with a self-generated certificate that is associated with the common name “APIC.” It is possible to integrate the APIC into a CloudCenter tenant using either the default HTTPS or the non-default HTTP protocol, both of which will be discussed here. To configure a custom certificate for HTTPS access to the APIC, review and follow this article. The process to create either a self-signed or publicly trusted certificate falls outside of the topic domain of this document.
Configuring the APIC for HTTP access:
To configure the APIC for HTTP access, navigate to Fabric -> Fabric Policies -> Pod Policies -> Policies -> Management Access -> default -> HTTP [Admin State] Enabled. Once this change is submitted, verify that the APIC responds to HTTP by navigating to the web interface (e.g. http://IP_of_APIC).
To configure the ACI Extension for the CloudCenter tenant, enter the same address for “APIC Controller URL"
Configuring the APIC for HTTPS access:
Case 1: Default SSL certificate
To configure the ACI Extension for the CloudCenter tenant to use the APIC’s default SSL certificate, an A record must be added to the DNS zone for the “APIC” name - this matches that name assigned to the default certificate shipped with the APIC. Once the record is added, ensure that https://APIC is resolved to the IP Address of the APIC. This is especially important where it concerns the CloudCenter Manager. To configure the ACI extension, the default certificate must be first be imported into the keystore. There is a useful utility that can facilitate this process:
Log on as root to the CloudCenter Orchestrator appliance & change to the /tmp directory
Capture text necessary to create certificate (*.crt) file
To configure the ACI Extension for the CloudCenter tenant to use a certificate signed by a trusted public root CA, obtain the certificate and install it onto the APIC. Add an A record to the DNS zone for a name that matches the common name of the certificate (e.g. if the common name is apic.cisco.local then the DNS resolved hostname must match). Once the certificate and A record have been added, verify that the name is resolved - this is particularly important in the case of the CloudCenter Manager. Since the certificate is signed by a trusted public CA, there is no requirement to import the certificate into the CloudCenter Manager’s keystore. To configure the ACI Extension for the CloudCenter tenant, enter https://DNS_Resolved_Name(e.g. https://apic.cisco.local).
Fortunately, Cisco thought about it and made available an ACI simulator for people interested by this technology to simulator a whole ACI environment. This simulator includes Cisco APIC instances with real production software, as its native tools (GUI &am...
Hello Everbody, During my use of Umbrella, which I use to study the traffic of my customers, I was faced with the following information, Cisco does not block (NS, SOA, MX) records/queries, even thought the algorithm considering the domains as 100%(Sc...
We are re-architecting a typical server - agent product for AWS SaaS. The UI and configuration DB will be on the cloud while the agents will be deployed on-prem. The problem is that 100K agents need to periodically poll the server if there are any configu...
So I've spent money on OVHS, NFOS, HYDRAPATHS, CLOUDFLAIR, etc but I still end up getting ddosed on Xbox because people end up having bypasses for all of those. I saw something about cisco routers being able to IP spoof (correct me if I'm wrong). My quest...