Verizon reportedly makes a bid for Charter; Toyota runs an open source Linux platform.
It’s the bake off you’ve been waiting for; a five-month real life test of a Ubiquiti ERPro-8 (EdgeRouter Pro) and a tub of Play-Doh™! Over a period of five months I carefully evaluated these two very useful items and discovered their good and bad points. But after five months, which will I choose as the ultimate winner?
The first item to be evaluated is the tub of Play-Doh™. I didn’t skimp on quality, and bought genuine Play-Doh™ as part of a set which included tubs of both light blue and red. Accessories in the box included a roller, a plastic cutting knife, four shaped cutters and an extruder with four built-in shapes as well as four interchangeable extrusion heads.
The entire kit Continue reading
The Internet of Things (IoT) is not just a device connected to the Internet - it is a complex, rapidly evolving system. To understand the implications, analyse risks, and come up with effective security solutions we need to look ahead and take into account other components, such as Big Data and Artificial Intelligence (AI).
The post Worth Reading: We are all groot appeared first on rule 11 reader.
By matching compute, storage, and networking resources for optimal utilization, the cluster-in-a-box wastes nothing.
We all make mistakes. We type the wrong command. We use the wrong verb tense in an article. We leave out a critical step when explaining a process. It’s something that happens all the time. It’s avoidable through careful planning, but how do you handle things when the avoidable becomes unavoidable?
Once a mistake is out in the open and noticeable, it’s done. You can’t pretend it didn’t happen or that it’s not affecting things. That’s when you need to own up to what happened and fix it. Sometimes that’s not always easy. Even the best person is reticent to admit to being fallible. So the process for fixing a mistake isn’t always easy. But it is important.
Mitja Robas started his PowerShell for Networking Engineers presentation with a brief introduction to PowerShell and a few simple hands-on examples. Enjoy the videos ;)
NetCraftsmen's Peter Welcher offers his take on the networking skills that will be critical in the future.
We collect the top expert content in the infrastructure industry and fire it along the priority queue.
Been a while since my last update, been quite busy! but I thought I’d do a post on something BGP related, as everyone loves BGP!
There’s an interesting addition to BGP route-reflection that’s found it’s way into a few trains of code on Juniper and Cisco, (I assume it’s on others too) that attempts to solve one of the annoying issues that occurs when centralised route-reflectors are used.
It all boils down to the basics of path selection, in networks where the setup is relatively simple and identical routes are received, at different edge routers within the network – similar to anycast routing.
Consider the below lab topology;
The core of the network is super simple, basic ISIS, basic LDP/MPLS with ASR-9kv as an out-of-path route-reflector, with iBGP adjacencies configured along the green arrows, the red arrows signify the eBGP sessions, between AS 100-200 and AS 100-300, where IOSv-7 and IOSv-8 advertise an identical 6.6.6.6/32 route. IOSv-3 and IOSv-4 are just P routers running ISIS/LDP only, for the sake of adding a few hops.
With everything configured as defaults, lets look at the path selection;
iosv-1#show ip bgp
BGP table version is 6, local router ID is Continue reading