Packet loss with Fast Reroute!
Do we still lose packet with fast reroute? One of my students asked me this question. And I would like to share the answer with everyone.
Do we still lose packet with fast reroute? One of my students asked me this question. And I would like to share the answer with everyone.
Couple days ago I discussed some IP Mobility solutions, including LISP (Locator Identity Separation Protocol) with the CCDE students.
Don’t expect technical topic in this post. Instead I wanted to show how was my situation before and after the CCDE – Cisco Certified Design Expert !. Enjoy
Fast Convergence and the Fast Reroute Network reliability is an important design aspect for deployability of time and loss sensitive applications. When a link, node or SRLG failure occurs in a routed network, there is inevitably a period of disruption to the delivery of traffic until the network reconverges on the new topology.
Technology prototypes tested and validated by the group are now commercially available and being...
One of my readers sent me a question along these lines…
VXLAN Network Identifier is 24 bit long, giving 16 us million separate segments. However, we have to map VNI into VLANs on most switches. How can we scale up to 16 million segments when we have run out of VLAN IDs? Can we create a separate VTEP on the same switch?
VXLAN is just an encapsulation format and does not imply any particular switch architecture. What really matters in this particular case is the implementation of the MAC forwarding table in switching ASIC.
Read more ...Scaling symbolic evaluation for automated verification of systems code with Serval Nelson et al., SOSP’19
Serval is a framework for developing automated verifiers of systems software. It makes an interesting juxtaposition to the approach Google took with Snap that we looked at last time out. I’m sure that Google engineers do indeed take extreme care when building the low level networking code that powers Google’s datacenters, but their fundamental design point was to enable frequent releases for fast iteration, feedback on their designs, and yes, early detection of problems.
Formal verification is at the other end of the spectrum. In theory it enables you to eliminate whole classes of problems and vulnerabilities entirely (in practice perfection is still hard to come by), and so it can be especially valuable in security sensitive situations. But it comes with a very high price tag:
Writing proofs requires a time investment that is usually measured in person-years, and the size of the proofs can be several times or even more that an order of magnitude larger than that of implementation code.
That’s both very expensive and an incredibly long wait for feedback. To invest in formally modelling something, you really Continue reading
A topic that’s been in the back of my mind since writing the Cluster API introduction post is how someone could use kustomize
to modify the Cluster API manifests. Fortunately, this is reasonably straightforward. It doesn’t require any “hacks” like those needed to use kustomize
with kubeadm
configuration files, but similar to modifying kubeadm
configuration files you’ll generally need to use the patching functionality of kustomize
when working with Cluster API manifests. In this post, I’d like to take a fairly detailed look at how someone might go about using kustomize
with Cluster API.
By the way, readers who are unfamiliar with kustomize
should probably read this introductory post first, and then read the post on using kustomize
with kubeadm
configuration files. I suggest reading the latter post because it provides an overview of how to use kustomize
to patch a specific portion of a manifest, and you’ll use that functionality again when modifying Cluster API manifests.
For this post, I’m going to build out a fictional use case/scenario for the use of kustomize
and Cluster API. Here are the key points to this fictional use case:
Guest Alex Marcham returns to Heavy Networking to explore edge exchanges. Like Internet exchanges, the goal of an edge exchange is to provide direct interconnection and traffic exchange between provider networks, but edge exchanges move that infrastructure closer to end users. Alex walks us through how these exchanges work.
The post Heavy Networking 485: Understanding Edge Exchanges appeared first on Packet Pushers.
Dell Technologies announced an on-demand buying model for its products and autonomous...
When you are always looking for what platform architecture will be mainstream, you have to look at what those on the bleeding edge are doing to see what the leading edge might do, which in turn tells you what everyone else might eventually do. …
Oil And Gas Giants Build Up Their Strategic GPU Reserves was written by Timothy Prickett Morgan at The Next Platform.
On today's Tech Bytes, our sponsor is Tufin, and we’re going to dig into the concept of agility in the enterprise, particularly as organizations adopt cloud services and container-based applications. Our guest is Aleck Brailsford, Director of Sales Engineering for the Americas at Tufin.
The post Tech Bytes: Enabling Agility And Security With Tufin Policy Automation (Sponsored) appeared first on Packet Pushers.
It is a rare HPC cluster that is actually upgraded – meaning some of the components in the servers or the networks or the storage that comprise the system are swapped out somewhere about halfway through its lifecycle and replaced with cheaper, faster, or more capacious components. …
The HPC Community Should Lead In Composability was written by Timothy Prickett Morgan at The Next Platform.
More than 50 communications service providers and technology companies have signed on to TM Forum's...
The carrier says it will be commercially deploying the open mobile transport protocol at scale in...