Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Broadcom’s November 12, 2025 announcement aligned VMware Cloud Foundation (VCF) networking with Cisco Nexus One using standards-based VXLAN EVPN, with BGP EVPN serving as the interoperability point between virtual and physical network domains. The goal is to make private-cloud networking more interoperable and easier to automate; the announcement describes intended benefits, not independently verified performance or savings.

What Broadcom announced

Broadcom said it was building an open, extensible VCF ecosystem around standards-based Ethernet VPN (EVPN) and Border Gateway Protocol (BGP). The approach is intended to connect application environments to physical network fabrics while supporting multiple vendors, retaining existing network investments, and providing consistent routing, protection, and visibility across VCF Networking domains and third-party networks. Broadcom’s announcement specifically aligned VCF with Cisco Nexus One.

How VCF and Cisco Nexus One interoperate

BGP EVPN is the common protocol

The integration centers on BGP EVPN: VMware’s September 8, 2026 follow-up says VCF and Cisco Nexus One both speak the protocol natively, enabling the virtual and physical networking domains to interoperate through a standard rather than a proprietary translation point. VMware’s follow-up identifies this as the interoperability mechanism.

VXLAN EVPN links the fabric domains

Cisco describes Nexus One as a unified data-center fabric based on open VXLAN/EVPN standards. In this context, VXLAN provides the overlay networking approach, while EVPN and BGP provide the control-plane mechanism for exchanging network reachability information. Broadcom’s stated objective is end-to-end, fabric-driven automation across the private-cloud environment; the announcement does not establish how much automation is available for any particular customer design. Cisco’s Nexus One description positions the fabric as a way to maintain consistent policy, control, and operations across heterogeneous data-center networks.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What the integration is intended to improve

  • Interoperability: A standards-based control plane is intended to connect VCF networking with a physical Cisco fabric and support multi-vendor environments.
  • Operational consistency: Broadcom and Cisco describe simpler operations and consistent policy, control, and visibility across network domains.
  • Investment flexibility: Broadcom says the approach is designed to preserve existing network investments and give customers flexibility in fabric choices.
  • Automation: The alignment is presented as a foundation for fabric-driven automation, but the sources do not specify a universal feature set or deployment workflow.
  • Cost: Lower total cost of ownership is a potential benefit claimed by vendors, not a result supported by an audited figure or independent benchmark in the cited material.

These are vendor-stated goals rather than measured outcomes. Network World quoted Broadcom VCF marketing executive Prashanth Shenoy saying the approach would simplify private-cloud networking and improve interoperability between applications and underlying infrastructure. Cisco vice president of data center networking Murali Gandluru characterized the company’s VXLAN EVPN work as part of its commitment to open networking. Network World’s coverage reports both statements; neither establishes a quantified operational or financial result.

Which Cisco hardware is relevant

The relevant physical product family is Cisco Nexus 9000-series switching hardware, used to build a Nexus One VXLAN EVPN fabric. The announcement does not identify a specific switch model, optics, licensing package, or channel availability. Those details depend on the topology and capacity requirements, and should be validated for the planned VCF release and fabric design before purchase.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What to validate before choosing this design

Protocol compatibility is only one part of a production network decision. Evaluate the complete VCF and physical-fabric design, including support and operational fit:

  • Confirm that the target VCF release and the selected Nexus One hardware and software versions have validated lifecycle support together.
  • Check whether BGP EVPN/VXLAN interoperability covers the segmentation, routing, and policy behaviors required by the workloads—not only basic route exchange.
  • Determine how policy, telemetry, and troubleshooting visibility will work across virtual and physical domains, and which tools or teams own each layer.
  • Map existing network investments and migration constraints, including hardware, software, and operational processes that must remain in place.
  • Specify the intended automation tasks and verify that the chosen design supports them end to end.
  • Obtain a deployment-specific bill of materials covering switch models, optics, licensing, and support through the appropriate Cisco or infrastructure partner channel.

Broadcom’s announcement establishes the standards-based alignment and its intended direction; it does not by itself prove that a particular hardware configuration is supported, available, or less expensive.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
Sale
Cisco N9K-C93108TC-EX Nexus 9000 48x Port 10GBase-T 6x 100G QSFP28 Switch w/ Dual PSU (Renewed)
  • Item Package Dimension: 22.48L X 17.28W X 1.73H Inches
  • Item Package Weight - 32.47 Pounds
  • Item Package Quantity - 1
  • Product Type - Electronic Switch

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.