In the first few sessions of the Building Network Automation Solutions online course we used Ansible as the tool-of-choice because it’s the easiest automation tool to get started with. Now that we’ve established the baseline, it’s time to explore the alternatives.
In a live session on February 27th 2018, Mircea Ulinic will describe Salt, an open source, general-purpose event-driven automation framework that we briefly discussed in Episode 77 of Software Gone Wild podcast.
Read more ...Holy cow. Broadcom Tomahawk 3 is a 32 x 400G ASIC at lower power, latency and reduced cost/100G speed. Built for the cloud it signals the next generation of 200G/400G Ethernet is on its way.
The post BiB 20: Broadcom Tomahawk 3 Announced With 32x400G ports appeared first on Packet Pushers.
After the recent series of technical Best Current Operational Practices (BCOP) documents that we initiated and co-authored, it’s time for new one. This time on how to run an incoming email server on IPv6 and survive!
Back in 2010 we started the IPv6 series of BCOP documents, starting with the popular RIPE-501 that was superseded by the even more popular RIPE-554 that discusses how to specify IPv6 functionality and compliance when ordering ICT equipment. This document emerged from listening to the Internet community that is deploying IPv6, and figuring out the common problems in order to come up with recommendations on how to solve them.
The next most common issue that we heard about, was that helpdesks of network operators would melt down if they deployed IPv6 to their end customers as they don’t know anything about IPv6. So we built an online tool and wrote some helpdesk procedures on how to troubleshoot IPv6 issues when users call them – resulting in another useful document that was published as RIPE-631.
After addressing this, we then repeatedly heard questions about what size of IPv6 prefixes should be given to end-users and should it be assigned statically or dynamically. We therefore put Continue reading
Companies are using multiple tools, leading to vendor fatigue and complex security environments.
The disaggregated data center project developed its own switch called Pigeon.
Construction-technology firms have generated $10 billion in funding since 2011, a McKinsey report says.
The deal will add 10 new data centers in Australia.
FlexWare will act as a type of router for the 5G network.
From time to time, I run across (yet another) article about why BGP is so bad, and how it needs to be replaced. This one, for instance, is a recent example.
It seems the easiest way to solvet this problem is finding new people—ones who don’t make mistakes—to work on BGP configuration, building IRR databases, and deciding what should be included in BGP? Ivan points out how hopeless of a situation this is going to be, however. As Ivan says, you cannot solve people problems with technology. You can hint in the right direction, and you can try to make things a little more sane, and a little less complex, but people cannot be fixed with technology. Given we cannot fix the people problem, would replacing BGP itself really help? Is there anything we could do to make things better?
To understand the answer to these questions, it is important to tear down a major misconception about BGP. The misconception?
BGP is a routing protocol.
BGP was not designed to be a routing protocol. It was designed to provide a loop free path through a series of independently operated networks, each with its own policy and business goals. In the Continue reading
Hardware isn't going away. But software is where all the action is.
About 95% of Viptela employees joined Cisco.
The goal was better connectivity and improved efficiency.