Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A network fabric is the complete, coordinated network architecture: its devices, links, topology, addressing, virtual networks, control systems, and operating policies. A protocol is a defined set of communication or control rules that devices follow. The fabric is the system being built; protocols are mechanisms that make the system function.
For example, a data-center fabric may use a routed IP underlay, a VXLAN overlay for tenant traffic, and EVPN control-plane signaling carried by BGP. VXLAN, EVPN, and BGP are protocols or protocol functions inside that architecture—not the fabric itself.
What “network fabric” means
Fabric is an architectural term rather than the name of one standardized protocol stack. It describes how network elements are connected and coordinated so that the resulting system provides reachability, isolation, policy enforcement, and operational control.
The word can describe several scopes:
- Data-center fabric: A switching architecture connecting servers, storage, security appliances, and tenant networks.
- Campus fabric: A coordinated design for wired and wireless access, distribution, segmentation, and policy.
- Branch or WAN fabric: A managed arrangement that connects sites, users, and cloud services across geographic links.
- Hybrid fabric: A design that combines on-premises, cloud, and sometimes software-defined segments.
Consequently, a statement that an organization “uses a fabric” is incomplete without its context. You still need to know whether the speaker means the physical topology, a virtual overlay, or a managed system that combines networking hardware, software, automation, and policy.
#1 Best Overall
- 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
What a protocol is
A protocol is a rule set. It specifies such things as message formats, addressing, state, timers, encapsulation, error handling, or how devices advertise and learn reachability. Protocols let independent devices make predictable decisions.
Protocols can operate at different functions within one network:
| Function | What the protocol does | Example from a fabric design |
|---|---|---|
| Data plane | Carries user packets, including any required encapsulation. | VXLAN encapsulates tenant traffic across an IP network. |
| Control plane | Distributes reachability or state so devices know where traffic should go. | EVPN distributes endpoint and segment reachability, commonly through BGP. |
| Underlay routing | Provides reachability between the physical network devices and tunnel endpoints. | A routed IP underlay connects the switches that carry the overlay. |
A protocol therefore answers “what rules do devices use?” A fabric answers “what complete network arrangement are those devices and rules creating?”
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Fabric versus protocol: the distinction in one view
| Question | Network fabric | Protocol |
|---|---|---|
| What is it? | An overall architecture and operating system for connectivity. | A formal set of communication or control rules. |
| What does it include? | Devices, links, topology, underlay, overlays, policies, and often automation. | Messages, packet formats, state machines, and behavior for a specific function. |
| How broad is it? | Can span a data center, campus, branch, WAN, or hybrid environment. | Usually addresses one networking function or layer. |
| Can it exist alone? | A fabric needs multiple components and operating choices. | A protocol can be implemented by devices and used inside many different architectures. |
| Typical example | A leaf-spine data-center fabric with an IP underlay and tenant overlay. | VXLAN, EVPN, or BGP used within that fabric. |
Calling VXLAN “the fabric” is therefore a category error. VXLAN is one data-plane protocol that a fabric may use. Likewise, EVPN is a control-plane technology, not a complete physical topology or operating model.
How a modern data-center fabric is assembled
1. The physical underlay
The underlay is the physical transport network: switches, links, interfaces, addresses, and routing that provide basic IP reachability. In a common data-center design, the underlay connects the devices that serve as tunnel endpoints. Its job is to deliver packets between those endpoints without needing to understand every tenant network carried above it.
2. The logical overlay
The overlay creates virtual networks on top of the underlay. It can carry separate tenant or application segments across the same physical switches, allowing logical connectivity to be designed independently of the exact cable path. VXLAN is an overlay encapsulation protocol used for this purpose: the original tenant frame or packet is wrapped so it can cross the routed IP underlay.
3. The control plane
Encapsulation alone does not tell a device where a remote endpoint resides. EVPN distributes reachability information for the overlay. In many implementations, EVPN uses multiprotocol BGP (MP-BGP) to advertise that information between network devices. The devices can then select the appropriate tunnel endpoint and forwarding behavior.
Cisco’s June 13, 2025 design guide summarizes the relationship precisely: “VXLAN is the data plane protocol that works with the MP-BGP EVPN control plane protocol.” The sentence describes cooperation between protocols; it does not redefine either protocol as the fabric.
Rank #3
- Compatible with Cisco Nexus 9000 Series Switch Compatible with: Cisco Nexus 9000 Series Switch 92160YC-X, 92300YC, 92304QC, 92348GC-X, 9236C, 9272Q, 93108TC-EX, 93108TC-FX, 93120TX, 93128TX, 93128TX Hot Air Exhaust, 9316D-GX, 93180LC-EX, 93180LC-FX, 93180YC-EX, 93180YC-FX
- Compatible with 93216TC-FX2, 93240YC-FX2, 9332C ACI Spine, 9332PQ, 93360YC-FX2, 9336C-FX2, 9336PQ ACI Spine, 9348GC-FXP, 93600CD-GX, 9364C ACI & NX-OS Spine, 9372PX, 9372PX-E, 9372TX, 9372TX-E, 9396PX, 9396PX Hot Air Exhaust, 9396TX, 9500 Platform Fabric Module, 9504, 9504 Chassis Bundle, 9508, 9508 Chassis Bundle, 9516
- Capacity: 8GB
- parts-quick Equivalent to Cisco NXK-MEM-8GB=
- System Specific Memory backed by parts-quick Lifetime Warranty and Toll Free Technical Support
4. Policy and operations
A usable fabric also includes segmentation rules, device configuration, monitoring, failure handling, and sometimes centralized automation. Those operational elements are why “fabric” often refers to more than a diagram of switches. Two networks can use the same protocols yet behave differently because their topology, policy, automation, and operational practices differ.
A worked VXLAN–EVPN example
Consider two servers in the same tenant network attached to different leaf switches. A simplified packet journey looks like this:
- Endpoint connection: Each server connects to a leaf switch. The leaves are the devices that attach endpoints to the fabric.
- Local learning: The leaf identifies the server’s local address and the tenant segment to which it belongs.
- Reachability advertisement: EVPN control-plane information, commonly carried by BGP, tells other participating devices which leaf can reach that endpoint or segment.
- Encapsulation: When the source server sends to a remote server, the ingress leaf places the tenant traffic inside a VXLAN packet addressed across the IP underlay.
- Underlay forwarding: The physical network routes the encapsulated packet from the ingress tunnel endpoint to the remote tunnel endpoint.
- Decapsulation and delivery: The egress leaf removes the VXLAN wrapper and forwards the original tenant traffic to the destination server.
The underlay, VXLAN, EVPN, BGP, leaf switches, spine switches, endpoint attachments, and policy together form the fabric. No single item in that list is equivalent to the whole architecture.
Recommended Free Tools
Why leaf-spine is common
A leaf-spine CLOS topology is one common way to build a data-center fabric. Endpoints connect to leaf switches, while spine switches connect the leaves. Traffic normally traverses a leaf and one or more spine paths rather than following a large, manually layered hierarchy.
This arrangement is an architecture choice, not the definition of every fabric. A campus fabric, WAN fabric, or another data-center design may use a different topology. Even within leaf-spine deployments, the number of devices, link speeds, routing choices, and redundancy model depend on application requirements and scale.
The practical benefit of separating endpoint-facing leaves from the spine is that the design can be expanded by adding devices in the appropriate layer. The resulting capacity, convergence behavior, and fault domains still depend on the implementation; the word “fabric” does not guarantee a particular result.
Design dimensions when comparing fabrics
There is no universally best fabric. Cisco’s design guidance emphasizes that hardware, software, scale, protocols, architecture, and network functionality must be selected against application requirements. Use these dimensions to compare designs:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Dimension | Questions to ask |
|---|---|
| Topology and scale | How many endpoints, sites, or tenants must connect? Does the physical layout provide the required capacity and failure isolation? |
| Underlay protocol choice | How will the physical devices establish IP reachability, and can the operations team troubleshoot that routing independently of the overlay? |
| Overlay and control plane | Is an overlay required for tenant separation or mobility? Which control-plane method distributes endpoint and segment reachability? |
| Multi-vendor operation | Do all devices implement the selected protocols and interoperability details consistently, or does the design depend on one vendor’s extensions? |
| Staff familiarity | Can the team diagnose underlay, overlay, and control-plane failures without treating them as one opaque system? |
| Convergence and fault isolation | How quickly should traffic reroute after a link or device failure, and which users or segments should be affected by that failure? |
These are decision axes, not a scorecard that automatically selects one architecture. A smaller environment may value operational simplicity over extensive segmentation; a large multi-tenant data center may accept more control-plane complexity to obtain logical isolation and scale.
Best Value
- Compatible with Cisco Nexus 9000 Series Switch Compatible with: Cisco Nexus 9000 Series Switch 92160YC-X, 92300YC, 92304QC, 92348GC-X, 9236C, 9272Q, 93108TC-EX, 93108TC-FX, 93120TX, 93128TX, 93128TX Hot Air Exhaust, 9316D-GX, 93180LC-EX, 93180LC-FX, 93180YC-EX, 93180YC-FX
- Compatible with 93216TC-FX2, 93240YC-FX2, 9332C ACI Spine, 9332PQ, 93360YC-FX2, 9336C-FX2, 9336PQ ACI Spine, 9348GC-FXP, 93600CD-GX, 9364C ACI & NX-OS Spine, 9372PX, 9372PX-E, 9372TX, 9372TX-E, 9396PX, 9396PX Hot Air Exhaust, 9396TX, 9500 Platform Fabric Module, 9504, 9504 Chassis Bundle, 9508, 9508 Chassis Bundle, 9516
- Capacity: 16GB
- parts-quick Equivalent to CISCO NXK-MEM-16GB=
- System Specific Memory backed by parts-quick Lifetime Warranty and Toll Free Technical Support
What the fabric term does not imply
It does not require VXLAN
VXLAN is common in contemporary data-center overlays, but a fabric can be built for other environments and with other mechanisms. Cisco uses the term across campus, branch, WAN, and hybrid data-center contexts. Do not assume that every product or design labeled “fabric” contains VXLAN.
It does not require EVPN or BGP
EVPN with MP-BGP is a widely documented control-plane combination for VXLAN fabrics, but the label “fabric” by itself does not prescribe that choice. The control plane must be evaluated against the required scale, interoperability, operations, and failure behavior.
It does not mean a physical mesh
Fabric may describe physical interconnections, a virtualized overlay, or the managed combination of both. A leaf-spine CLOS is one common physical arrangement; it is not a synonym for fabric.
It does not guarantee performance
A fabric name is not a benchmark. Throughput, latency, convergence, and resilience depend on hardware, software versions, link design, protocol settings, and traffic patterns.
Understanding the VLAN and VXLAN scale comparison
Juniper’s EVPN-VXLAN material cites an approximate comparison of 4,000 VLANs and 16 million VXLAN segments. This is a vendor technical comparison of identifier space, not an independently measured performance statistic. It illustrates why VXLAN is attractive when a design needs many logical segments, but it does not prove that a particular fabric can deliver that number of usable, isolated networks under every operational condition.
How to evaluate a fabric proposal
- Define the scope: Write down whether the proposal covers a data center, campus, branch, WAN, cloud connection, or a hybrid of these.
- Separate layers: Draw the physical underlay, logical overlay, control plane, and policy or automation components as distinct layers.
- Trace a packet: Identify where a packet enters, how the destination is learned, whether it is encapsulated, which devices route the underlay, and where it is decapsulated.
- List protocol responsibilities: Name the protocol used for each job rather than calling the entire stack one protocol.
- Check interoperability: Confirm that every participating device supports the required protocol features and that multi-vendor behavior is documented.
- Test failures: Simulate a failed link, leaf, spine, tunnel endpoint, or control-plane session and record the expected convergence and affected traffic.
- Document operations: Provide separate troubleshooting procedures for underlay reachability, overlay encapsulation, control-plane advertisements, and policy errors.
This method prevents a common design mistake: selecting a protocol first and then assuming it automatically supplies the topology, scale, policy, and operating model that a complete fabric requires.
Common terminology mistakes
- “Our fabric is BGP.” BGP may carry control-plane information, but the fabric also includes physical devices, links, topology, overlays, and policy.
- “VXLAN replaces the network.” VXLAN carries encapsulated traffic; it still needs an underlay that can reach the relevant tunnel endpoints.
- “Leaf-spine is a protocol.” Leaf-spine describes topology. Routing, encapsulation, and reachability protocols operate within that topology.
- “A vendor’s fabric label is a standard.” Product names can package automation and policy in different ways. Read the implementation details rather than inferring a universal protocol stack from the label.
The practical takeaway
Use fabric when you are describing the coordinated network system and its architecture. Use protocol when you are naming the rules that perform a particular networking function. In a typical data-center example, the routed IP underlay, leaf-spine connections, VXLAN data plane, EVPN/BGP control plane, endpoint attachments, and operating policies are all parts of one fabric. VXLAN, EVPN, and BGP remain distinct protocols with distinct jobs inside it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
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.
