-
It's all about packet control
Learn how VXLAN defines a packet and how EVPN works with VXLAN in what it needs to do. VXLAN and EVPN working together are powerful.
2:42
-
Bridging the gap with VXLAN EVPN
Learn and understand the benefits of choosing VXLAN EVPN as your fabric mode.
4:34
-
VXLAN EVPN to the Rescue!
Define the fundamentals of VXLAN EVPN and how they fit together. Learn the of history of how VXLAN EVPN came about, and what problems it solves.
4:25
-
NX-OS 10.2: EVPN Hybrid IRB Mode Overview
This feature allows NX-OS VTEPs operating in Symmetric IRB mode to seamlessly inter-operate with VTEPs running in Asymmetric IRB mode within the same VXLAN EVPN fabric.
9:35
-
NX-OS 10.2: EVPN Distributed NAT Overview
EVPN Distributed NAT enables Network Address Translation in a VXLAN EVPN fabric and offers enhancements like mobility and traffic engineering at host level and on border nodes for DCI (Data Center Interconnect).
9:20
-
NX-OS 10.2: Multicast NAT Overview
Learn about Multicast Service Reflection on the Nexus 9000 and how bringing this capability within the network itself will improve network performance and scale.
7:27
-
NX-OS 10.2: Inter-VRF and Multi-site Service Chaining Overview
Learn about ePBR enhancements on Inter-VRF service chaining and multi-site support introduced in NX-OS 10.2 and use cases now available with this new capability.
9:43
-
Floating L3Out Enhancements
Starting from Cisco APIC Release 4.2, you could no longer specify L3Out logical interface paths for L3Out by using floating L3Out. APIC Release 5.2 enhances floating L3Out capabilities to optimize traffic path for internal endpoints to floating L3Out
8:46
-
PBR Destination in an L3Out
Prior to APIC Release 5.2, PBR destinations must be in a BD, not in an L3Out. Starting with APIC Release 5.2, PBR destinations can be in an L3Out, which provides a more flexible design for service insertion.
7:16
-
Remote Leaf Back-To-Back Connected Link
Remote leaf provides centralized management of configuration, discovery and operations to a pair of switches without the need of full fabric with APIC and Spine at edge location. It locally forwards traffic to other remote locations and locally conne
6:36
-
Standalone APIC Cluster
Starting in ACI 5.2, ACI supports management of an ACI fabric from an APIC cluster over a layer-3 network. Prior to ACI 5.2, the APIC controllers must by directly connected to ACI leaf switches. With the Standalone APIC feature, the APIC controller
11:51
-
Configuring ACI L4L7 device insertion with service graph redirect
Learn how to leverage the ability of ACI L4 - L7 device insertion with Service Graph Redirect using different Bridge Domains.
12:35
- Load More
Cisco Video Portal
