However, as an example, let’s say that we had a leaf switch with 160 Gbps of bandwidth it could use to connect to spine switches. Obviously, the types and number of connections between the leaf and spine switches vary with the switch models being used. It’s also interesting to note that the uplink connections from the leaf switches to the spine switches could be either Layer 2 (i.e. Also, unlike a leaf switch, all ports on a spine switch have a single purpose in life, to connect to a leaf switch. As a result, there’s no need for interconnections between spine switches. You’ll notice in the topology that each leaf switch connects to every spine switch. a server in the rack, a firewall, a load-balancing appliance, or a router leaving the data center) or (2) connecting to a spine switch. Ports in a leaf switch have one of two responsibilities: (1) connecting to a node (e.g. These ToR switches act as the leaves in a Leaf-and-Spine topology. You might have heard the term top-of-rack (ToR) used to refer to these types of switches, because they physically reside in the top of a rack. Frequently, there will be a couple of switches at the top of each rack, and, for redundancy, each server in the rack has a connection to both of those switches. Imagine a cabinet in a data center, filled with servers. It’s called a Leaf-and-Spine topology, and in this short blog post, you’re going to learn the basics of how it’s structured.
However, within today’s data centers, a new topological design has taken over. The Core Layer then provided very fast transport between Distribution Layer switches. The Distribution Layer redundantly interconnected Access Layer switches, and provided redundant connections to the campus backbone (i.e. The Access Layer connected to our end devices (e.g. For decades, we’ve heard about Cisco’s three-tier network design where we had the following layers: (1) Access, (2) Distribution, and (3) Core.
0 kommentar(er)
