Original content from Roger's CCIE Blog Tracking the journey towards getting the ultimate Cisco Certification. The Routing & Switching Lab Exam
As your network grows bigger and your internet traffic grows, it starts to make sense to peer directly with other networks rather than simply pay an ISP to deliver all that traffic. Peering is one of the areas in life where the Pareto principle, also known as the 80-20 rule applies: 20% of your potential... [Read More]
Post taken from CCIE Blog
Original post Peering with Route Servers
Segment routing is a source routing mechanism which provides Traffic Engineering , Fast Reroute, MPLS VPNs without LDP or RSVP-TE. Very simple but powerful solution,when you read the post you will ask more information, because it solves the complex problems with some extensions to existing protocols. MPLS provides BGP free core, VPN services (Layer2 and… Read More »
The post SEGMENT ROUTING appeared first on Network Design and Architecture.
IoT: Don't fret about the world of tomorrow
The Internet of Things is a big deal. But – as CIMI Corp. President Tom Nolle wrote in a recent blog post titled “My Thermostat Doesn’t Want to Talk to You” – it is probably not going to be a big deal for network management.
We’ve heard all sorts of applications of smart technology, such as refrigerators that know when you’re running low on milk and can send a text to your smartphone when you’re in the vicinity of a supermarket; thermostats that know when you’re working late at the office so you don’t have to have the heat turned on exactly at 6pm, etc. Early adopters already have all these things. But other than the basic Internet connectivity needed to send these little pieces of data back and forth, network management – as an industry and as a profession – is probably going to be almost unaffected by it.
Think about it. For many purposes, the Internet of Things provides the most value coordinating between different items in your home.
In our “world’s fair house-of-the-future,” much of Continue reading
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
Voice over IP uses the session initiation protocol (SIP) to convert phone conversations to data and send it through a public or private IP network instead of using telephone lines or fixed bandwidth T1 and T3 options. This can be a brilliant way to cut costs, gain flexibility and more efficiently use existing resources, but consider these issues to ensure successful implementation:
* Native SIP. Ask your carrier if their network was designed to deliver SIP end-to-end and the size of their local telephone number footprint. SIP is an open standard protocol used to enable VoIP. Make sure your carrier isn’t patching together multiple networks, which may or may not use SIP and could cause quality degradation and make troubleshooting issues more difficult.
To read this article in full or to leave a comment, please click here
The more debate I hear over protocols and product positioning in the networking market today, the more I realize that networking has a very big problem with myopia when it comes to building products. Sometimes that’s good. But when you can’t even see the trees for the bark, let alone the forest, then it’s time to reassess what’s going on.
Sit down in a bar in Silicon Valley and you’ll hear all kinds of debates about which protocols you should be using in your startup’s project. OpenFlow has its favorite backers. Others say things like Stateless Transport Tunneling (STT) are the way to go. Still others have backed a new favorite draft protocol that’s being fast-tracked at the IETF meetings. The debates go on and on. It ends up looking a lot like this famous video.
But what does this have to do with the product? In the end, do the users really care which transport protocol you used? Is the forward table population mechanism of critical importance to them? Or are they more concerned with how the system works? How easy it is to install? How effective it is at letting them do their jobs?
The Continue reading
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
Web advertisers and many others have long appreciated the volumes of information they can collect on us based only on our web browsing patterns. The data can be quite telling, revealing our locations, incomes, family status, interests and many other facts that advertisers can use to target you.
Understandably, most of us would prefer that “big brother like” advertising networks aren’t always watching over our shoulder, while going about regular activities including product research and purchase option exploration and especially not while investigating medical or other highly sensitive topics.
To read this article in full or to leave a comment, please click here
“The only way to deal with an unfree world is to become so absolutely free that your very existence is an act of rebellion.” – Albert Camus
In my role as a Customer Solutions Engineer (affectionately known as CSE) at Cumulus Networks, I am on the frontlines discussing customer requirements, use cases and networking architectures. A frequent question that customers ask me is “what can an open network operating system (OS) do for me?”
Most customers have lived in the world of black boxes where the OS and hardware are vertically integrated and your vendor keeps you in a sandbox that controls what you can and cannot do. In the black box world, if you want a new feature, application or a different operational model, you have to request it from your account team and wait while the vendor decides if your use case is important enough or you are a big enough customer.
The idea of having direct access to the different operational aspects of the OS is a foreign concept Continue reading