In this Learning Path, you'll build a foundational understanding of enterprise networking and the Extreme Networks platform, starting with core switching and routing principles. From there, you'll learn how IS-IS serves as the control plane behind Extreme Fabric Connect, building and sharing topology information across the fabric so VLANs can reach each other automatically, without manual route configuration. You'll then see how BGP connects the fabric to the WAN, enabling routing between sites and internet access through Extreme SD-WAN appliances, whether traffic is routed centrally over the WAN or broken out locally based on policy. Together, these technologies show how modern enterprise networks are designed, connected, and extended across multiple sites with Extreme Networks.

Cisco ACI is a policy-driven CLOS, or Spine-Leaf, switching fabric that utilizes Layer 3 ECMP routing in the underlay and VXLAN encapsulation in the overlay to transport Layer 2 and Layer 3 traffic both east-west within the fabric and north-south between the fabric and external networks. ACI consists of the Application Policy Infrastructure Controller (APIC), which provides centralized policy, automation, and fabric management capabilities. Leaf switches function as Top-of-Rack (ToR) switches that provide connectivity to servers, storage, and external networks, while spine switches provide high-speed Layer 3 ECMP connectivity between all leaf switches. An ACI fabric can be scaled horizontally by adding additional leaf switches, connecting them to the spine layer, and registering them with the fabric. Cisco ACI was architected to operate as a distributed "single logical system," similar to a modular chassis-based architecture, where APICs provide centralized policy and control functions, spine switches provide the high-speed fabric core, and leaf switches provide endpoint connectivity. This distributed architecture enables organizations to decouple these functions from the constraints of a physical chassis and deploy them anywhere within the data center environment. Cisco ACI further extends this architecture through remote leaf, multi-pod, and multi-site deployments. Remote leaf allows organizations to extend policy and connectivity to remote locations while maintaining centralized operational control. Multi-pod enables geographically separated pods to operate as a single fabric, while multi-site supports independent ACI fabrics interconnected across multiple data centers or cloud environments. With Cisco Nexus Dashboard and Nexus Dashboard Orchestrator (NDO) 4.x, organizations can centrally manage policy, orchestration, analytics, and day-two operations across multiple ACI fabrics and cloud-integrated environments from a unified operational platform. Nexus Dashboard 4.x enhances scalability, resiliency, automation, and operational visibility while integrating advanced analytics, AI-driven assurance, telemetry, and cloud-native application support. This enables consistent policy enforcement, simplified operations, and unified visibility across on-premises data centers, edge environments, and public cloud deployments.

VMware NSX Datacenter(NSX-T) platform allows the creation of secure virtual networks on top of your current physical network and virtual server infrastructure. SDN abstracts the underlying infrastructure of your network and programs separate virtual networks using the software. Using the NSX-T manager to create the NSX infrastructure, we prepare the Compute and Edge hosts participating in NSX. The compute hosts connect to the DC fabric, typically a CLOS or Spine/Leaf architecture. The Edge is connected to the DC fabric and external switches to provide public and private routing to WAN and Internet. Using the software, NSX can recreate entire physical networks, from the layer two switching, complex BGP routing, and FWs load balancers VPNs. This is possible by creating layer 3 Virtual Tunnel Endpoints (VTEPs) that use the Geneve encapsulation protocol to create an overlay in the compute and Edge cluster hosts. This overlay can then build layers two and three segments to connect our Virtual NSX routing and switch infrastructure. This Geneve Encapsulated Overlay also allows us to create a Physical to Virtual (P/V) point where we can either encapsulate the virtual networks and send them across the layer three underlays or decapsulate to connect to devices outside NSX.