Using clustering algorithms, Datadog can spy cloud servers that aren't performing optimally.
Kheradpir sticks to the telecom world after his adventure at Juniper.
Hurry up! It's your last chance to sign up for the ONF-sponsored panel discussion!
One of the known issue for anyone preparing for a Cisco exam is that the solutions available today don’t support all the needed features. Cisco VIRL supports L2 switching out of the box, whereas GNS3 does not. GNS3 supports the configuration of serial interfaces on routers whereas Cisco VIRL does not. For someone starting out in this […]
The post Bridging Between Cisco VIRL and GNS3 for L2 and Serial Support appeared first on Packet Pushers.
Someone needs to unify all those enterprise security tools, the startup reckons.
The power behind a Shopping Director.
Generic Routing Encapsulation - GRE is a tunneling protocol originally developed by Cisco that encapsulates various network protocols inside virtual point-to-point tunnel. It transports multicast traffic via GRE tunnel so it allows passing of routing information between connected networks. As it lacks of security it is very often used in conjunction IP SEC VPN that on the other hand is not capable to pass multicast traffic.
The goal of the tutorial it to show configuration of GRE tunnel on a Cisco router and a device with OS Linux. I have created GNS3 lab consisting of two local networks - 192.168.1.0/24 and 192.168.2.0/24 connected via GRE tunnel. GRE tunnel interface is configured on router R1 (Cisco 7206VXR) and Core Router (Core Linux with Quagga routing daemon installed). The both routers have their outside interfaces connected to a router R3 that is located in the "Internet". To prove that GRE tunnel is working and transporting multicast traffic, the OSPF routing protocol is started on R1 and Core routers and configured on tunnel interfaces and interfaces pointing to local networks.
Note: The Core Linux vmdk image is available for download here.
1. Initial Configuration
First we assign hostnames and Continue reading
For all those who think opensource is going to take over the world, cleaning up (and destroying) the mess open standards have made, there is a lesson in here.
It won’t.
The problem isn’t open standards. The problem isn’t open source. We have met the problem, and it is… us. We are the problem here. What we keep thinking is that we can “solve” complexity in some way. Each time a new unicorn comes on the scene, we think, “here, at least, is the magical unicorn that will make the physical world work the way I always wanted it to.” But like real life unicorns, you won’t find one in your rose garden. Or any other garden, for that matter. Unicorns don’t exist. Get over it.
Instead of looking for the next magical unicorn, we need to get to work figuring out which problems need to be solved, which ones Continue reading
If you’ve listened to a technology presentation in the past two years that included discussion of cloud computing, you’ve probably become embroiled in the ongoing war of the usage of the word premises or the shift of people using the word premise in its stead. This battle has raged for many months now, with the premises side of the argument refusing to give ground and watch a word be totally redefined. So where is this all coming from?
The etymology of these two words is actually linked, as you might expect. Premise is the first to appear in the late 14th century. It traces from the Old French premisse which is derived from the Medieval Latin premissa, which are both defined as “a previous proposition from which another follows”.
The appearance of premises comes from the use of premise in legal documents in the 15th century. In those documents, a premise was a “matter previously stated”. More often than not, that referred to some kind of property like a house or a building. Over time, that came to be known as a premises.
Where the breakdown starts happening is recently in technology. We live Continue reading
The post Worth Reading: Negative vibes on the ICANN transition appeared first on 'net work.
Riverbed’s entry –or perhaps “expansion”– into the SD WAN market is interesting to me primarily because the approach being taken is a little different from the other solutions I have seen so far.
The solutions I’ve seen from vendors like Viptela, Silver Peak, Cisco, CloudGenix and VeloCloud mainly focus on providing reliable and optimized transport from spoke site to hub site, and in some cases also from spoke to spoke, and in fewer still, spoke to Internet. The underlying approach is to monitor various statistics for each of the available WAN links, and intelligently route data flows over the link that will best meet the application’s needs. Some solutions add error correction and/or packet duplication techniques to overcome packet corruption and loss as well. Let’s call this Link Selection, noting that both links are used so it’s not a “one or the other” kind of thing.
Riverbed has come at this problem from the angle they know best, WAN optimization. The presentation Riverbed gave at Networking Field Day 10 was not about how to choose which link to use, but more about how to effectively manage a hybrid WAN (say, MPLS for corporate access in Continue reading