If you run any type of network monitoring system you will know the pain of log management. The firewall team needs one view, the WAN team & DC team need different views. There is a category of software that I call “log and alert routing” and Flapjack is one of those systems Flapjack will […]
SDN/OpenFlow is about Network Management, at least, in part. But the rich tools for software control dont’ exist. I also think don’t think that todays management _platforms_ (such as Tivoli, OpenView and BMC) are suitable for network orchestration in the future.
In this blog post, Calle Moberg (from Tail-F Systems who makes NETCONF software) highlights that the ONF has embraced NETCONF as mandatory for configuration of OpenFlow enabled devices. I didn’t know this was coming: […] OF-CONFIG1.0 requires that devices supporting OF-CONFIG 1.0 MUST implement NETCONF protocol as the transport. This in turn implies as specified […]
Over the last few months I’ve been looking at Network Management options that are not OpenFlow or SNMP based. This led to NETCONF & YANG and these are my working notes from some time spent reading and researching.
I’m responding to Brad Hedlund’s post “On optimizing traffic for network virtualization” where he seems to missed a key point. It’s about cost of ownership in terms of ability to troubleshoot.