Should we add detailed for vPC or VXLAN BGP EVPN?
In a Leaf-Spine topology, every Leaf switch connects to every Spine switch. This creates a predictable, low-latency fabric where any server is only two hops away from any other server. Cisco Nexus switches are purpose-built to facilitate this high-bandwidth, non-blocking environment. Key Features of Cisco NX-OS
Zero-touch deployment. A new Nexus switch boots, downloads an NX-OS image from a TFTP server, and pulls its configuration from a Python script. Should we add detailed for vPC or VXLAN BGP EVPN
The decision to deploy Nexus switches is often tied to a fundamental architectural choice between NX-OS and the more familiar Cisco IOS found on Catalyst switches.
Overlay Technologies: NX-OS supports advanced encapsulation methods like VXLAN (Virtual Extensible LAN). VXLAN allows for the creation of massive Layer 2 networks over a Layer 3 infrastructure, which is vital for moving virtual machines across physical boundaries. The Nexus Product Portfolio Cisco Nexus switches are purpose-built to facilitate this
| Series | Ideal Use Case | Key Feature Powered by NX-OS | | :--- | :--- | :--- | | | Ultra-low latency (HFT, AI) | Wire-rate VXLAN routing, sub-microsecond latency | | Nexus 7000 | Classic core/aggregation (End-of-Sale but legacy) | VDC (Virtual Device Contexts) – one chassis, multiple virtual switches | | Nexus 9000 | Spine-leaf, Cloud-scale data centers | Cloud-scale ASIC; supports both NX-OS standalone mode and ACI mode | | Nexus 9300-GX | 100/400GbE leaf | Hardware-accelerated encryption (MACsec) and streaming telemetry |
NX-OS and Cisco Nexus Switching: Next-Generation Data Center Architectures The decision to deploy Nexus switches is often
The explosive growth of Artificial Intelligence (AI) and High-Performance Computing (HPC) is driving perhaps the most significant evolution in data center architecture in a decade, and Cisco is at the forefront.
NX-OS is software, but its magic is unlocked by purpose-built ASICs. Here is the current landscape:
Every protocol and service runs as an independent Unix/Linux process. If a routing protocol like OSPF crashes, the System Manager (SysMgr) restarts just that process. The data forwarding plane continues running without dropping traffic.
+---------+ +---------+ | Spine | | Spine | +----+----+ +----+----+ | \ / | | \ / | | \ / | +----+----+ +----+----+ | Leaf | | Leaf | +---------+ +---------+ Spine Layer