Response: The How and Why of Flapjack | Fractional

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 […]

ONF Extends their SDN to Embrace NETCONF and YANG

network-operations-protocol-stack-1

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 […]

Tech Review: NETCONF and YANG

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.

RFC 6244 – Network Management Using NETCONF and YANG

I’ve been watching NETCONF and YANG for about four years and it seems that it might be breaking through the noise to set a new standard for Network Management data exchange. In short, SNMP isn’t working and the next generation of “blah blah Cloud” will require more sophisticated communication than SNMP can handle. In the last four years, NETCONF has matured and slowly percolated its way through the industry. Now that is has teamed up with YANG we have something that looks like it’s about to burst into the mainstream.

Network Monitoring: SNMP knows stuff

Some packet generator are more important than others and indeed while a packet is just a packet for us network people if the packets stop moving around the network the way they should it can be a great cause for alarm. I have a customer with such a packet generating devices and it chucks out a 600k udp multicast stream (a single UDP payload) every 5 seconds and if this screws up for any reason then the application is not happy and hundreds of users are very upset. If the packets stop for any length of time then a Severity 1 incident is raised and the customer needs an ass to kick.