I was first introduced to NetBeez at Networking Field Day 9, where I saw an interesting monitoring product using Raspberry Pi-based agents and a cloud-based management and reporting console. That was back in February 2015, but I met with NetBeez a second time at Networking Field Day 12 in September 2016. Eighteen months is plenty of time to make some significant updates, so I’m going to look at the current product from a capabilities perspective and also see how it works when using it in anger. As background it may be worth reading my review of NetBeez from June 2015 first.
By way of a refresher, the NetBeez product is made of two parts:
Beez, which always sounds odd to say because
Beezsounds like it should be the plural form of the noun);
We collect the top expert content in the infrastructure community and fire it along the priority queue
Open unified communications and collaboration platforms can enable companies to evolve their legacy patchwork deployments.
We did several podcasts describing how one could get stellar packet forwarding performance on x86 servers reimplementing the whole forwarding stack outside of kernel (Snabb Switch) or bypassing the Linux kernel and moving the packet processing into userspace (PF_Ring).
Now let’s see if it’s possible to improve the Linux kernel forwarding performance. Thomas Graf, one of the authors of Cilium claims it can be done and explained the intricate details in Episode 64 of Software Gone Wild.
Read more ...There is a lot of buzz around network APIs such as NETCONF and RESTCONF. Here we’ll take a quick a look at these APIs on Cisco IOS XE. On the surface, it seems Cisco IOS XE is the first network device platform that supports NETCONF and RESTCONF both driven from YANG models.
Technically, RESTCONF isn’t officially supported or even seen in the CLI to enable it, but more on that later.
When APIs are model driven, the model is the source of truth. If done right, all API documentation and configuration validation could occur using tooling built directly from the models. YANG is the leading data modeling language and as such, all API requests using RESTCONF/NETCONF are directly modeled from the YANG models IOS XE supports. For this post, we’ll just say the models can easily be represented as JSON k/v pairs or XML documents. We’ll cover YANG in more detail in a future post.
You can directly access the NETCONF server on IOS XE using the following SSH command (or equivalent from a SSH client).
The NETCONF server is a SSH sub-system.
$ ssh -p 830 ntc@csr1kv -s netconf
The full response from the IOS XE NETCONF Continue reading
There is a lot of buzz around network APIs such as NETCONF and RESTCONF. Here we’ll take a quick a look at these APIs on Cisco IOS XE. On the surface, it seems Cisco IOS XE is the first network device platform that supports NETCONF and RESTCONF both driven from YANG models.
Technically, RESTCONF isn’t officially supported or even seen in the CLI to enable it, but more on that later.
When APIs are model driven, the model is the source of truth. If done right, all API documentation and configuration validation could occur using tooling built directly from the models. YANG is the leading data modeling language and as such, all API requests using RESTCONF/NETCONF are directly modeled from the YANG models IOS XE supports. For this post, we’ll just say the models can easily be represented as JSON k/v pairs or XML documents. We’ll cover YANG in more detail in a future post.
You can directly access the NETCONF server on IOS XE using the following SSH command (or equivalent from a SSH client).
The NETCONF server is a SSH sub-system.
$ ssh -p 830 ntc@csr1kv -s netconf
The full response from the IOS XE NETCONF Continue reading
Young startups and seasoned seven-year-olds are moving into Gartner's Magic Quadrant on Integrated Systems