BGP and asymmetric routing
The post BGP and asymmetric routing appeared first on Noction.
The post BGP and asymmetric routing appeared first on Noction.
Sales of HPC systems were a lot brisker in 2015 than anticipated, and according to the latest prognostications from the market researchers at IDC presented from the International Supercomputing Conference in Frankfurt, Germany this week, growth in the HPC sector will continue to outpace that of the overall IT market for many years to come.
In a sense, the good numbers that the HPC market turned in last year are perhaps a little undercounted. In his traditional early morning breakfast briefing at the conference, Earl Joseph, program vice president for high performance computing at IDC, said that he had been …
HPC Spending Outpaces The IT Market, And Will Continue To was written by Timothy Prickett Morgan at The Next Platform.
Reading my Directed ARP and ICMP Redirects blog post you might have wondered “how did Directed ARP ever get into ***redacted***?”
I searched for “directed ARP cisco” and found this gem, which really talks about unicast ARP behavior, an ancient mechanism documented in RFC 1122 (it’s not my Google-Fu, I got the reference to RFC 1122 in this blog post).
Read more ... Trials are occurring now and OS will be available this summer.
Every now and then, there are waves of technology that threaten to make the previous generation of technology obsolete. There has been a lot of talk about a technique called “serverless” for writing apps. The idea is to deploy your application as a series of functions, which are called on-demand when they need to be run. You don’t need to worry about managing servers, and these functions scale as much as you need, because they are called on-demand and run on a cluster.
But serverless doesn’t mean there is no Docker – in fact, Docker is serverless. You can use Docker to containerize these functions, then run them on-demand on a Swarm. Serverless is a technique for building distributed apps and Docker is the perfect platform for building them on.
So how might we write applications like this? Let’s take our example a voting application consisting of 5 services:
This consists of:
The background processing of votes is a very easy target for conversion to a serverless architecture. In the voting app, we can run a Continue reading
AT&T is starting to see benefits from Domain 2.0.
So this is the fourth blog on EVPN, the previous blogs covered the following topics:
This post will cover the ability of EVPN to provide all-active multi-homing for layer-2 traffic, where the topology contains two different active PE routers, connecting to a switch via a LAG, the setup is similar to the previous labs. Due to some restrictions and in the interests of simplicity, this lab will cover all-active multi-homing for a single VLAN only, (VLAN 100 in this case) consider the network topology:
The topology and general connectivity is the same as the other previous examples, the two big differences are that only VLAN 100 is present here and the connectivity between MX-1 and MX-2 is now using MC-LAG.
The first consideration that needs to be made when running EVPN in all-active mode, is that it must connect to the upstream devices using some sort of LAG, or MC-LAG – consider the wording from the RFC 7432:
https://tools.ietf.org/html/rfc7432#section-14.1.2
IT skills are becoming more demanding.