Welcome to our new video. I'm Apoor talker, a customer success specialist at Cisco CX. Today we begin an extensive dive into the Cisco ACI six.X features. Moving to six.X marks a milestone for any ACI.00:05Fabric, bringing features that boost automation, visibility, and scalability. Our agenda includes the executive summary and the ACI six.X release and scale improvements. Next, we'll explore enhanced visibility and traffic analytics to simplify troubleshooting. We'll also cover architectural updates like.00:20Virtual Apic and warm standby.00:40Plus new interface workflows and Nutanix integration. Finally, we'll wrap up with best practices to ensure a seamless ACI upgrade. Let's start with the executive summary. ACI six decks enhances operational efficiency and network stability speeding up digital transformation with a resilient automated fabric.00:42We focus on greater stability and higher uptime driven by advanced analytics that proactively fix issues to cut downtime. In short, ACI Sixtyx makes your fabric smarter, more stable, and easier to manage. Let's demystify the ACI sixtex release model now. We've dropped short and long.01:02In lived terms, we now use F releases for new features and M releases strictly for bug fixes.01:22Each major train follows a clear four year support life cycle covering development cycles, maintenance, extended support with cert fixes, and standard tax support. Understanding this cadence is essential for upgrade planning, helping you time your releases according to your specific stability requirements and feature needs.01:27Now, let us examine the specific release and the scale improvements. Let us discuss the scale. ACI six point X offers enormous increases in fabric capacity, expanding limits to 400 leaves per pod and 500 per multipod. Routing capacity has doubled with more BGP OSPF sessions and larger IPV.01:45Four IPV six LPM entries for large complex routing tables. We have also extended external connectivity and visibility from LE Outs and granular security contracts to deeper netflow analytics. SRMPLS scale has improved.02:05Ultimately, this enables constructing more expansive and complex multi tenant environments without hitting scale ceilings. From scale to visibility across teams, ACI six X shifts emphasis toward proactive management. The goal is to resolve bottlenecks before they affect users.02:21We achieved this through three pillars. Fine grained telemetry for live analysis, analytics to pinpoint performance issues with better accuracy and upgraded dashboards for a single cross fabric health view. These elements feed a proactive pillar for the network. Centralizing this data yields a clearer view of your fabric state.02:38Shifting from firefighting to a model in which you have insights to constantly optimize network health.02:58ACI 16 X introduces virtual Apex clusters. Removing the need for dedicated physical hardware. APEX can run as Vmiss on ESXi or Nutanix AHV, offering flexibility, link them over layer two networks across all topologies, including remote leaf, multipod, and multi site.03:04The new mixed cluster support with ACI 6.21 lets you run virtual and physical apex in the very same cluster. This is ideal for scaling current clusters or moving to a virtual management plane now, giving you the architectural freedom to fit your data center environment.03:24Next consider a disaster recovery improvement, the warm standby apex C added in ACI six point twelve. Previously losing three or more active apex demanded a complex time consuming recovery with Cisco TAC.03:42Warm standby provides a robust failover, letting recovery from unrecoverable states occur without manual intervention. Warm standby is now standard. It handles single APIC failures like the legacy cold standby and is far more capable.03:57Since ACI 06:21 cold Standby is phased out. Standby apex default to warm standby. You can support up to three warm standby apex with virtual APEX support available since 613I highly recommend adding warm standby to your upgrade plan. It is an essential way to protect your fabric management plane.04:13Now that we've covered the basics, let's look at two primary use cases for warm standby. 1st, a single APEX replacement. If a controller fails, redundancy is required immediately. Unlike cold standby, which needs full data sync from remaining apics, warm standby has the data ready enabling near instant replacement.04:33Second and most crucial indeed is disaster recovery. If you lose three or more apEX, the whole cluster warm standby acts as your insurance policy. Because it maintains a complete data backup, you can rebuild the cluster from scratch restoring your fabric management plane without manual recovery, whether it's routine hardware failure or.04:51Total cluster loss, warm standby reduces downtime and simplifies recovery.05:11It's the ultimate insurance for your ACI fabric. Now that the control plane is secured, let's discuss visibility across the fabric. ACI six X works with Cisco Nexus dashboard to deliver truly advanced traffic analytics, giving broad visibility into packet drops, congestion, and latency anomalies without manual.05:16The filters. It gives a service based view, auto categorizing DNS, web, and SQL traffic, and flagging top talkers to speed troubleshooting now.05:36The dashboard turns telemetry into clear insights showing service health scores and traffic patterns. These actionable insights let you resolve bottlenecks before they affect users, giving the data you need for capacity planning. It's the difference between guessing what's happening in your fabric and actually knowing.05:46Next, let's review our improved interface configuration workflow designed to reduce complexity in large fabrics. We concentrated on three major areas. 1st, keeping focus simplifies the path of physical connections, helping you stay on task without menu hopping.06:04Second, the modern interface workflow provides a clear UI that guides you through configurations ending the need to hunt for settings. 3rd, streamline network configuration greatly shortened steps for common tasks like port channels and VPCS. By minimizing clicks for these repetitive tasks, we're saving you time and reducing human error during deployment.06:21Deployment. It's a cleaner, faster way to manage your fabric.06:41If you've managed ACI, you know the classic four step dance to configure a port, creating switch and interface profiles and selectors. It was effective but time consuming. With ACI six point oh one F, we've modernized this by collapsing four complex steps into a single streamlined interface setup menu. This changed.06:45Isn't just fewer clicks. It truly reduces cognitive load and misconfiguration risk. You can now run interfaces in a fraction of the time avoiding nested policies.07:05It's a more intuitive approach to access policies and a massive win for daily operations. What does this new workflow look like? Here is the new interface configuration menu. On the left, you have a clean, well consolidated sidebar. You simply select your node type, port type, and interface aggregation, whether individual.07:14Port channel or VPC. Enter your node and interface range and select the policy group and you're done. All in one view indeed. On the right, a clear table view shows your current interface states, letting you see set ports, modes, and policy groups at a glance. You'll notice a yellow banner confirming you use the new method.07:34It offers a migration path to reference older settings. This interface is far more transparent and actionable than the prior nested menu approach, showing how ACI six.X prioritizes day to day usability. Next, let's discuss Nutanix integration in more detail. If you're familiar with aci's VMware.07:53V Center integration, this workflow is intuitive.08:13ACI communicates with Nutanix Prism Central by API, automatically pushing ACI EPGs as subnets into AHV. We map terminology to ensure seamless transition Prism Central access V center, Nutanix virtual switch functions like VMware VDS, and Nutanix subnets mapped to VMware port groups.08:17You get full intra EPG isolation. Essential for security. We support one prism element cluster per Prism central. This enables aci's policy based automation in Nutanix HV environment. Next consider PBR weighted ECM. Standard PBR shares traffic.08:37Like evenly, but service nodes vary in capacity, just like a fast 400 G server versus a legacy node.08:57With PBR weighted ECMP, you can assign a weight to each destination. Giving higher weights to more capable nodes makes the ACI fabric allocate more buckets and route more traffic to them. This ensures traffic distribution reflects actual node capacity.09:04It works best with diverse, evenly hashing traffic across the buckets to optimize your service chains. We understand weighted PBR now. Let's see how it works. Each PBR destination gets await from one to ten with up to 128 weights per policy.09:20In this example, setting weights of 432, and one makes destination one get 40 % of traffic while the others get 3020, and 10 %. By tuning these weights, you tell the fabric to transmit more traffic toward nodes that can handle it. This provides a straightforward way to keep powerful nodes in use while.09:38Without overloading smaller ones, matching traffic to each destination's capacity.09:58Bridging the policy gap between campus and data center remains a common challenge. Today we bridge the gap with ISE ACI integration for a unified policy. PX Grid is the secret sauce. ISE shares user and application context across domains, so ACI can identify who the user is NO matter where they can.10:04Connect. This enables end to end micro segmentation by mapping campus SGTS to ACI EPGs enforced at border nodes or firewalls.10:23For instance, a sales rep sergeant could access CRM EPG, Benefits include clear group policies, not ACLs, member updates, and flexible policy enforcement points. Whether running multi tenant data centers or integrating with SD WAN and Meraki, this provides a unified security posture.10:33Now let us move to the final portion of our series, preparing for your ACI upgrade. We have covered the features and benefits. Now let's wrap up with the most critical part, preparing for your ACI upgrade. Think of this pyramid as your foundation. Start by choosing the right release and reviewing documentation.10:52Next, map your integrations carefully and utilize the ACI pre upgrade checklist and upgrade guide. These are your blueprints for success. Following the structure ensures focus, a smooth predictable upgrade path, validation confirming fabric readiness with pre upgrade tools, migration, proven paths to minimize downtime stability.11:11The long term reliability for mission critical applications.11:31Upgrading doesn't have to be hard for your data center today. By planning and following these industry standard best practices, you aren't just updating software. You're keeping your data center healthy. Never start an upgrade without running the ACI pre upgrade validation script, please.11:35This Cisco tool runs locally on Epic with zero impact on services. This script runs 45 checks for Apic and switch readiness, giving very precise actionable reasons for failures. Fully supported by TAC, this script is standard in our workflow. It's on GitHub. The quick start guide makes it easy to run and spot any failed.11:52More manual checks.12:12Think of this as a pre surgery health screening. It catches common issues like disk space or firmware compatibility that cause upgrades to stall. Run it, clear your warnings and ensure a smooth successful upgrade. Now, let us walk through the nine step upgrade workflow. By following this sequence, you minimize downtime and preserve fabric stability.12:131st, start the preparation phase. Carry out your APIC cluster backup, step one, and do not skip it. Step two entails the CIMC upgrade. Steps three through five, address the logistics, downloading the software, uploading it to the APIC, and scheduling your maintenance window.12:33Then comes the controller upgrade Step six. Step seven is critical. Verify the fabric is operational and the apic cluster is healthy. If not, stop and troubleshoot before proceeding. Finally perform the fabric upgrade by upgrading switches in phase groups eight and nine steps. Verifying status after each group. This isolates issue.12:49Issues and preserves workload connectivity.13:09Preparation, verification, and phased execution are essential for a successful ACI upgrade. Before hitting upgrade, let's review the golden rules for a smooth maintenance window. 1st, ensure your APEC cluster is fully fit and clear all critical faults. A clean fabric is the baseline for success. Next, verify.13:12NTP sync to avoid certificate and log issues and always have CIMC KVM access ready as a safety net.13:31Clear any pre upgrade script failures and promptly open a proactive tack case. An engineer on standby marks a planned mission critical upgrade today. That concludes the ACI six.X series on features, scaling and upgrade best practices.13:39I hope this roadmap helps you plan your upcoming maintenance window with confidence. If you found this series beneficial, please like comment, and subscribe for our next deep dive. Thanks for watching and happy upgrading.13:54
