In the last post on SDNs, I spent a little time discussing just a bare minimum of some internal router architecture—specifically the difference between the RIB and the FIB, and thinking a little about management. In this post, I want to add one more dividing point to the mix, and then start thinking about how we can classify various “software defined” solutions in a way that makes more sense out of the field of options.
There is tremendous interest in Network Functions Virtualization (NFV) in large part because it holds the promise of enabling organizations to deploy new functionality in notably less time than it currently takes. However, no organization will implement a new technology or a new architecture if it can’t be effectively managed. With that in mind, I will use this blog to identify whether or not NFV introduces new management challenges and if it does, what are some of those challenges?
When it comes to unifying a network management system (NMS), does less really equal more? This topic has re-emerged since the market downturn, which – as we all know at this point – has led telcos to look for any opportunity to save costs, either capex, opex or both.