ACI: Configuring Out-of-Band (OOB) access for your Fabric

Configuring Out-of-Band connectivity to your ACI Fabric devices is a critical component to successfully maintaining and operating your datacenter. When it comes to configuring OOB connectivity to your devices (Leafs, Spines, and APIC Controllers), you’ll have need to do two things to get things going: All devices will need static OOB addresses (APIC Controllers, Leafs, … More ACI: Configuring Out-of-Band (OOB) access for your Fabric

Changing the default port for HTTP(s) access to the APIC GUI

  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

ACI: vPC in ACI

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

ASAv Service Graph – Cloud Orchestrator Package

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

Using MCP (MisCabling Protocol) for ACI

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