In the fourth installment of this 9-video series, Russ White describes methods for scaling data center fabrics. He reviews how to calculate port density in a leaf-spine design, discusses physical restraints on the scale of a fabric based on the spines, fabric types in chassis switches, and the pros and cons of chassis vs. single […]
The post Understanding Data Center Fabrics 04: Clos Scaling – Video appeared first on Packet Pushers.
Once your Mac computer gets connected to a source of wifi and the password has been saved, its unique features enable it to automatically reconnects once in range with the wifi network.. At first, this might be okay not until for some reason, you don’t want it to be connected anymore.
Sometimes, when there are various networks in range that had been previously connected and saved to your Mac, it becomes difficult for your system to choose which one to connect to as they are all saved and could easily be connected. In situations like this, you may want to connect to one particular network but it probably connects to the wrong one. In this scenario, you would want to disconnect with the unwanted wifi network, and to do that means you would need to forget the wifi.
There are other various reasons why you may need to forget your wifi network. Probably you’ve got lots of already connected networks and you would like to reduce them or you no longer really use the network anymore and don’t want it always connected or you probably have more than one wifi and would no longer want to use one but the Continue reading
TL&DR: Ansible might decide to reorder list values in a loop parameter, resulting in unexpected order of execution and (in my case) totally borked device configuration.
A bit of a background first: I’m using an Ansible playbook within netlab to deploy initial device configurations. Among other things, that playbook deploys configuration snippets for numerous configuration modules, and the order of deployment is absolutely crucial. For example, you cannot activate BGP neighbors in Labeled Unicast (BGP-LU) address family (mpls module) before configuring BGP neighbors (bgp module).
TL&DR: Ansible might decide to reorder list values in a loop parameter, resulting in unexpected order of execution and (in my case) totally borked device configuration.
A bit of a background first: I’m using an Ansible playbook within netsim-tools to deploy initial device configurations. Among other things, that playbook deploys configuration snippets for numerous configuration modules, and the order of deployment is absolutely crucial. For example, you cannot activate BGP neighbors in Labeled Unicast (BGP-LU) address family (mpls module) before configuring BGP neighbors (bgp module).
In this post I will show you how to setup Terraform to connect to your Google Cloud Platform (GCP) tenancy to manage your GCP infrastructure as code. Software The following software was used in this post. Terraform - 1.1.7 Ubuntu - 2004 gcloud - 378.0.0 Pre-Flight Check Google...continue reading
Normally, when we look at a system, we think from the compute engines at a very fine detail and then work our way out across the intricacies of the nodes and then the interconnect and software stack that scales it across the nodes into a distributed computing platform. …
Nvidia Will Be A Prime Contractor For Big AI Supercomputers was written by Timothy Prickett Morgan at The Next Platform.
On today's Tech Bytes with sponsor Singtel, we look at SD-WAN as a critical network feature for cloud access, including the use of overlays to simplify operations. We also discuss why organizations might consider a service provider for SD-WAN and dig into Singtel's SD-WAN offering.
The post Tech Bytes: The Advantages Of Singtel SD-WAN For Cloud Access (Sponsored) appeared first on Packet Pushers.
The data center landscape has radically evolved over the last decade thanks to virtualization.
Before Network Virtualization Overlay (NVO), data centers were limited to 4096 broadcast domains which could be problematic for large data centers to support a multi-tenancy architecture.
Virtual Extensible LAN (VXLAN) has emerged as one of the most popular network virtualization overlay technologies and has been created to address the scalability issue outlined above.
When VXLAN is used without MP-BGP, it uses a flood and learns behavior to map end-host location and identity. The VXLAN tunneling protocol encapsulates a frame into an IP packet (with a UDP header) and therefore can leverage Equal Cost Multi-Path (ECMP) on the underlay fabric to distribute the traffic between VXLAN Tunneling Endpoints (VTEP).
Multi-Protocol BGP (MP-BGP) Ethernet VPN (EVPN) allows prefixes and mac addresses to be advertised in a data center fabric as it eliminates the flood and learns the behavior of the VXLAN protocol while VXLAN is still being used as an encapsulation mechanism to differentiate the traffic between the tenants or broadcast domains.
A Multi-Tenancy infrastructure allows multiple tenants to share the same computing and networking resources within a data center. As the physical infrastructure is shared, the physical Continue reading
In the third installment of this 9-video series, Russ White clarifies exactly what a fabric is, complete with drawings, animations, and live illustrations. From there, you’ll be able to determine what is and is not a fabric. In this lesson, Russ also walks through traffic patterns, tiers, and bandwidth between tiers in data center fabrics. […]
The post Understanding Data Center Fabrics 03: Characteristics Of Data Center Fabrics – Video appeared first on Packet Pushers.
Typically when people hear the word edge, everyone gets a little apprehensive of what that means. So Josh, Andy, Martin and Chad got together to collaborate on what that means from their collective experiences across multiple industries. In this blog we will cover what the difference is between the near edge and far edge, as well as give some examples of what we have seen in these environments across multiple industries.
Near edge typically refers to distributed deployments of “scaled-down” IT-like services to support business operations outside the core data centers and public cloud providers. This includes anything from retail stores, branch field offices, manufacturing facilities, warehouses and distribution centers that generally have stable connectivity.
Traditionally, these have been referred to as remote offices or branch offices, with the common acronym ROBO, but there are far more examples of this deployment pattern. Consider the following:
These are all examples that fit under our definition of Continue reading