Cisco Blogs


Cisco Blog > Perspectives

#CiscoChampion Radio S2|Ep 36: stuff that makes your network life easier

CiscoChampion200PXbadge#CiscoChampion Radio is a podcast series by Cisco Champions as technologists. Today we’re talking with Cisco Champions about their favorite gadgets and networking tools that help them at work.*

Get the Podcast
Listen to this episode
Download this episode (right-click on the episode’s download button)
View this episode in iTunes

Cisco Champion SMEs
Korey Rebello, @koreyrebello, Principal Network Engineer
Kweku Folson, @ielabgh, Network/IP Specialist

Moderator
Rachel Bakker (@rbakker) Read More »

Tags: , ,

Zombie and Non-Zombie Technologies and What We Should Be Teaching in Basic Networking Classes

In the networking field, there are a number of technologies that should be dead but that still linger on, at least in our folklore and training, if not actually installed in modern networks. There are also concepts and technologies that are extensively used in modern networks, but that aren’t taught in most basic networking classes.

zombie tech Read More »

Tags: , , ,

#CiscoChampion Radio S2|Ep 39: Cisco Emergency Response & Emergency Calling

CiscoChampion200PXbadge#CiscoChampion Radio is a podcast series by Cisco Champions as technologists. Today we’re talking about Cisco Emergency Response (CER) and Emergency Calling with Cisco Technical Marketing Engineer Dan Keller.

Get the Podcast
Listen to this episode
Download this episode (right-click on the episode’s download button)
View this episode in iTunes

Cisco SME
Dan Keller, Cisco Technical Marketing Engineer

Cisco Champion Guest Hosts
Josh Warcop, @Warcop, Senior Consultant

Moderator
Brian Remmel (@bremmel)

Highlights
What does it mean to be ready for emergency response?
Mobile and emergency calling
CER and device mobility
CER updates and device support
Advantages of CER over native emergency handling of communications manager
Tips for emergency call routing

Resources – online Cisco Live sessions
Emergency Calling and Cisco Unified Communications
On-Site Emergency Call Notification
Extension Mobility – Cross Cluster

Tags: , ,

The complexity required for robustness, often goes against robustness

In the past few months we have seen major outages from United Airlines, the NYSE, and the Wall Street Journal. With almost 5,000 flights grounded, and NYSE halting trading the cost of failure is high. When bad things happen IT personal everywhere look at increasing fault tolerance by adding redundancy mechanisms or protocols to increase robustness. Unfortunately the complexity that comes with these additional layers often comes with compromise.

The last thing your boss wants to hear is, “The network is down!”. Obviously it’s your job to prevent that from happening, but at what cost? Many of us enjoy twisting those nerd knobs, but that tends to only harbor an environment with unique problems. I too fear the current trend of adding layer after layer of network duct tape to add robustness, or worse, to try and fix shortcomings in applications. NAT, PBR, GRE, VXLAN, OTV, LISP, SDN… where does it end!?

The greater the complexity of failover, the greater the risk of failure. We often forget the lessons of our mentors, but keeping the network as simple as possible has always been best practice. As Dijkstra said, “Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better”. This is a fundamental design principle that is often overlooked by enthusiastic network engineers or, even worse, sales or marketing engineers who are trained to sell ideas that only work in PowerPoint. When planning out your latest and greatest network design each and every knob that you tweak puts you farther and farther into uncharted territory. While it may work, for now, you’ll be the only one running anything close to those features in unison. And when, not if, you have to call TAC, they have to understand the fundamental design of the network BEFORE they can troubleshoot it. Validated designs do exist for a reason.

simplicity

At this point in time I would encourage you to read up on a couple infamous network outages including Beth Israel Deaconess Medical Center in Boston, whose spanning tree problem took the network down for four days, and the story about how the IT Division of the Food and Agriculture Organization of the United Nations recently had a rather serious, but brief, four hour outage…

While both of these outages were simple in nature, the complexity of the growing network was key in causing the failure. A lack of continuous design, periodical review, and most important failover testing inherently nurture failure.

#CiscoChampion Radio S2|Ep 35: the latest in IWAN

CiscoChampion200PXbadge#CiscoChampion Radio is a podcast series by Cisco Champions as technologists. Today we’re talking about the latest in IWAN with Cisco Technical Marketing Engineer Jake Sacharok.

Get the Podcast
Listen to this episode
Download this episode (right-click on the episode’s download button)
View this episode in iTunes

Cisco SME
Jake Sacharok, Cisco Technical Marketing Engineer

Cisco Champion Guest Hosts
Bill Carter, @ccie5022, Senior Business Communications Analyst
Eric Perkins, @perk_zilla,Principal Solutions Architect

Moderator
Lauren Friedman, @lauren

Highlights
Overview of IWAN CVD and SD-WAN Solutions
Benefits of the IoS Authority Certificate Solution
Cisco Prime and monitoring IWAN network
Why no IWAN question is too small for Cisco customers and partners
Industry wish list for IWAN Solution
APIC and IWAN integration
Behind the scenes with CVDs

Resources
Intelligent WAN Technology Design Guide

Tags: , , ,