Cisco worked with the cloud titans, but it had to do most of the heavy lifting.
Moving from an outsourcing to an insourcing model helped boost agility and reduce operational costs.
Recently, I published Self Paced Service Provider Training Course. I didn’t make an Internet wide announcement yet as I still upload the content to the course. Though I haven’t announced it yet, some people have already purchased it and the previous Instructor Led Service Provider course attendees got the access to the self paced […]
The post Network Interconnection videos have been added into Self Paced SP Training appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
Eyvonne Sharp wrote an interesting blog post describing the challenges Cisco might have integrating Viptela acquisition, particularly the fact that Viptela has a software solution running on low-cost hardware.
Guess what… Cisco IOS also runs on low-cost hardware, it’s just that Cisco routers are sold as a software+hardware bundle masquerading as expensive hardware.
Read more ...In a previous article, I explained how Linux implements an IPv6 routing table. The following graph shows the performance progression of route lookups through Linux history:
All kernels are compiled with GCC 4.9 (from Debian Jessie). This version is
able to compile older kernels as well as current ones. The kernel configuration
is the default one with CONFIG_SMP
, CONFIG_IPV6
,
CONFIG_IPV6_MULTIPLE_TABLES
and CONFIG_IPV6_SUBTREES
options enabled. Some
other unrelated options are enabled to be able to boot them in a virtual machine
and run the benchmark.
There are three notable performance changes:
struct rt6_info
(commit 887c95cc1da5). This should have lead to
a performance increase. The small regression may be due to cache-related
issues.TL;DR: With its implementation of IPv6 routing tables using radix trees, Linux offers subpar performance (450 ns for a full view — 40,000 routes) compared to IPv4 (50 ns for a full view — 500,000 routes) but fair memory usage (20 MiB for a full view).
In a previous article, we had a look at IPv4 route lookup on Linux. Let’s see how different IPv6 is.
Looking up a prefix in a routing table comes down to find the most specific entry matching the requested destination. A common structure for this task is the trie, a tree structure where each node has its parent as prefix.
With IPv4, Linux uses a level-compressed trie (or LPC-trie), providing good performances with low memory usage. For IPv6, Linux uses a more classic radix tree (or Patricia trie). There are three reasons for not sharing:
It’s using Dell, Nutanix, VMware, and CA Technologies.