The post Questions to ask a NetFlow Vendor Before you Buy appeared first on Noction.
In the previous two posts, we’ve seen how to build a custom network API with Kubernetes CRDs and push the resulting configuration to network devices. In this post, we’ll apply the final touches by enabling oAuth2 authentication and enforcing separation between different tenants. All of these things are done while the API server processes incoming requests, so it would make sense to have a closer look at how it does that first.
Every incoming request has to go through several stages before it can get accepted and persisted by the API server. Some of these stages are mandatory (e.g. authentication), while some can be added through webhooks. The following diagram comes from another blogpost that covers each one of these stages in detail:
Specifically for NaaS platform, this is how we’ll use the above stages:
On Monday we wrote about a painful Internet wide route leak. We wrote that this should never have happened because Verizon should never have forwarded those routes to the rest of the Internet. That blog entry came out around 19:58 UTC, just over seven hours after the route leak finished (which will we see below was around 12:39 UTC). Today we will dive into the archived routing data and analyze it. The format of the code below is meant to use simple shell commands so that any reader can follow along and, more importantly, do their own investigations on the routing tables.
This was a very public BGP route leak event. It was both reported online via many news outlets and the event’s BGP data was reported via social media as it was happening. Andree Toonk tweeted a quick list of 2,400 ASNs that were affected.
Quick dumps through the data, showing about 2400 ASns (networks) affected. Cloudflare being hit the hardest. Top 20 of affected ASns below pic.twitter.com/9J7uvyasw2
— Andree Toonk (@atoonk) June 24, 2019
The RIPE NCC operates a very useful archive of BGP routing. Continue reading
On Monday we wrote about a painful Internet wide route leak. We wrote that this should never have happened because Verizon should never have forwarded those routes to the rest of the Internet. That blog entry came out around 19:58 UTC, just over seven hours after the route leak finished (which will we see below was around 12:39 UTC). Today we will dive into the archived routing data and analyze it. The format of the code below is meant to use simple shell commands so that any reader can follow along and, more importantly, do their own investigations on the routing tables.
This was a very public BGP route leak event. It was both reported online via many news outlets and the event’s BGP data was reported via social media as it was happening. Andree Toonk tweeted a quick list of 2,400 ASNs that were affected.
Quick dumps through the data, showing about 2400 ASns (networks) affected. Cloudflare being hit the hardest. Top 20 of affected ASns below pic.twitter.com/9J7uvyasw2
— Andree Toonk (@atoonk) June 24, 2019
This blog contains a large number of acronyms and those are explained at the end of Continue reading
In this episode, you’ll hear from Russ White, Infrastructure Architect, Juniper Networks; Jorge...
SK Telecom has during the last couple months inked collaborative development deals with Microsoft,...
The combined entity will count about 60,000 customers and bolster its No. 3 position in the global...
For the first time IDC expanded its definition of HCI systems, adding a “new breed” called...
The China-based vendor has the strongest 5G mobile base station portfolio, according to a new...
The initial hype of SD-WAN claimed that MPLS was dead as SD-WAN was going to remove all need for SLA based circuits. Now that we’re several years in and have some experience under our collective belts, we take a look at whether or not the original hype was correct and what real world customers are doing when it comes to selecting circuits for their SD-WAN networks.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post MPLS is dead, Long live MPLS appeared first on Network Collective.
Toothy McGrin left a comment after I talked how little effort is required to acheive a vendor certification. Its a hot topic. Here is the discussion, its about 2 minutes in. CCNA/CCNP may not be a big deal in the circles you travel in, but for a lot of employees and employers they […]
The post Response: Certifications Are Not A Big Deal. Stop Being a Princess About It. appeared first on EtherealMind.