Telefónica Selects Huawei for Virtual EPC Network in 13 Countries
Fulfilling its promise to work with a variety of virtualization vendors.
Fulfilling its promise to work with a variety of virtualization vendors.
For the last few years, I’ve been sharing my list of projects for each year (here’s the list for 2012, the list for 2013, 2015’s list, and last year’s list—I didn’t do a list for 2014). Toward the end of each year, I also publish a “report card” assessing my performance against that year’s list (here’s the 2016 assessment). In this post, I’m going to share my list of planned projects for 2017.
Without further ado, here’s the list for 2017:
Finish the network automation book. One way or another, the network automation book I’m writing with Jason Edelman and Matt Oswalt is getting finished in 2017. (It’s available now as an Early Access edition if you’d like to give it a look and provide some feedback.)
Launch an open source book project. This is something I’ve been tossing around for a while now. Since my efforts at making code contributions to an open source project aren’t going so well (though I’m going to keep moving in that direction), I figured I’d contribute in a way I know I can do. This is going to be a “cookbook”-style book, and the goal I’m setting Continue reading
François Locoh-Donou has an optical networking background.
As we’ve progressed through the Segmenting Layer 3 Networks with VRFs series, we have continued to build out a network that looks more like what we would see within an enterprise environment. This post takes it one step further and leverages the DMVPN (dynamic multipoint VPN) functionality to extend the network securely over the public
Internet. In the examples here, we actually go one step beyond a typical DMVPN and map VRFs to tunnels using the tunnel key. This allows the pci and data VRFs to maintain isolation across the VPN.
One more thing that we will do that isn’t related to the core requirement of segmenting pci from data is leveraging a F-VRF (or front side vrf) on the DMVPN routers to isolate the Internet facing interfaces that connect them to the public cloud. This is my preferred method for DMVPN deployment if I’m not doing split tunnelling (i.e. I am back-hauling all traffic to a central location).
As a prerequisite, I will go ahead and build out the Internet router and the interface on Main that connects to DMVPN-hub.
hostname Internet interface gig2 description to DMVPN-hub ip address 1.1.1.1 255.255.255. Continue reading
Ixia fills a portfolio gap for Keysight.