Prerequisites Make sure and have the appropriate Contracts configured for OOB to permit the access to the desired port. If you do not have this in place, the traffic destined to the new port will be killed by the contracts. While not a prerequisite, Since HTTPs access via the GUI is generally the “front … More Changing the default port for HTTP(s) access to the APIC GUI
Prerequisites While there are no prerequisites, if you need a refresher on Fabric Access Policy Configurations inside of ACI (i.e., AAEP, Switch Profiles, Interface Profiles, Vlan Pools, Policy Groups), check out this post, Configuring Fabric Access Policies. vPC Overview A virtual port channel (vPC) allows links that are physically connected to two different ACI Leaf … More ACI: vPC in ACI
Introduction Introduced in ACI 3.1, the Cloud Orchestrator Package greatly simplifies the configuration of Service Graphs. Intended for use with an Orchestrator such as Microsoft Azure for a generic configuration of any L4-L7 device. Prerequisites ACI 3.1 Supported Device Package Supported L4-L7 Device BD Configuration to match the Service Insertion configuration Since this is routed mode … More ASAv Service Graph – Cloud Orchestrator Package
MisCabling Protocol (or MCP) detects loops from external sources (i.e., misbehaving servers, external networking equipment running STP) and will err-disable the interface on which ACI receives its own packet. Enabling this feature is a best practice and it should be enabled globally and on all interfaces, regardless of the end device. MCP limits the blast … More Using MCP (MisCabling Protocol) for ACI
The CIMC is Cisco’s answer to lights-out management for UCS servers, including the UCS servers that house the APICs. For troubleshooting the APIC, most engineers assume you must have direct console (i.e., physical access) or use the Java (or later HTTP)-based KVM Console to get true OOB access to your APIC, however, this is not … More Using Serial-over-Lan (SOL) on the CIMC to access the APIC (instead of KVM console)
In this post we will see how to use Postman Runner in order to deploy ACI configuration with variables from a CSV file. Pre-requisite Postman should be installed and running with access to your APIC Postman In this example we will configure 5 new Bridge Domains in a tenant. Tenant = KM VRF = … More ACI: Using Postman Runner with .csv files
HealthScores are a good way to monitor faults and the general health of your ACI Fabric. But in certain cases, such as CRC errors, if the interface does not change state (up/down), no fault will be generated and consequently the HealthScore is not affected. In this article we examine what steps are necessary to ensure … More Configuration to affect HealthScore with CRC errors
One of the main advantages that ACI offers is the ability to simplify the configuration, and the ability to backup, your entire datacenter configuration. In a traditional datacenter network, backups must occur on a box-by-box basis (leading to configuration sprawl), and the process to back them up is generally managed by a combination of network … More Creating a backup for your APIC Cluster
After a brief break from the APIC, the auto-provisioning feature is available (again) inside of the APIC GUI starting with APIC version 2.3 release and later. However, if you need it (or want it) and you are running at least APIC 2.2, you can configure the feature via API (i.e., XML or JSON). Why would … More Using the auto-provision feature to automatically upgrade new switches added to your ACI Fabric
One issue that can pop up when trying to maintain an ACI Fabric is the presence of cosmetic faults that drag our health score down. For example, let’s say we pre-configure server ports to be members of an EPG, but the servers have yet to be plugged into the fabric. In that case, the health … More Ignoring Acknowledged Faults