Nexus Dashboard 2.1 – New Features – Federated Clusters

Nexus Dashboard 2.1 has incorporated a lot of New Features/Improvements.  In this write-up, I will primarily discuss the Federated Nexus Dashboard configuration, why use it and also discuss some of other underlying improvements/changes.  I will also show how to send API calls to Nexus Dashboard Federated Clusters to get Federation Related Information. Installing ND is … More Nexus Dashboard 2.1 – New Features – Federated Clusters

Understanding ACI TCAM Utilization & Optimization

Being organized and creating consistent configurations is a great virtue in the Networking / SDN / Cloud and computing field.  ACI is no exception to that rule.  Haphazard, Inconsistent and thoughtless configurations will increase your work and complexity/understanding of your infrastructure once your  Fabric grows.  In addition it will make it more prone to failures … More Understanding ACI TCAM Utilization & Optimization

ACI NetCentric 2 AppCentric Using MicroSegmentation

In this blog post, I’ll discuss a method of moving from Network Centric ACI Deployment to APP Centric ACI deployment using combination of ACI Features: MicroSegmentation/PrefferedGroups/ContractMasters. When ACI Fabric is initially deployed, it is either deployed in a Greenfield or Brownfield method. Green Field means it’s a brand new deployment. Brown Field means that the … More ACI NetCentric 2 AppCentric Using MicroSegmentation

Understanding Scope Of Prefixes in L3Out External EPG in ACI

In ACI the external Routing Peer to the router is done through border leaves with a object called L3Out.   L3Out has an object in it called the L3Out InstP also known as the External EPG.    In the External EPG you can put in Prefixes and choose the scope based on your intended goal.   Under the … More Understanding Scope Of Prefixes in L3Out External EPG in ACI

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

ACI Naming Convention Best Practices

  This statement is especially true when it comes to naming objects inside of ACI. Naming your ACI objects in a meaningful and thoughtful way will increase the supportability of your fabric and even help the fabric to become “self-documenting”. Having naming conventions that are haphazard, will have an equally negative impact. To complicate matters, … More ACI Naming Convention Best Practices