When I started with my first Cisco router back in 1995, I never would have imagined I would someday be the technology lead for an ice arena of an NHL team. I also would never have predicted the impact that having a Cisco certification would have on being recruited to that position.
Most of my career up until now was spent working in the small and medium business space, primarily on ISP and telecom space working with voice and networks with some software and infrastructure design in the middle. Cisco was a large part of everything that I did from routing and switching to voice over frame relay followed by voice over IP, with a large emphasis on small bandwidth efficiency and signalling. I’m even the lead inventor on an issued patent relating to intelligent rerouting of fax traffic on VoIP systems.
I never thought much about certifications. I have a BA in Economics which has served me well as a business owner and largely found all my work via word of mouth. There were not a lot of people who understood VoIP payload and signalling tuning, starting from the MC3810 and up through the as5300/as5800 series. This was primarily in international carrier / wholesale VoIP traffic and engineering.
As VoIP became more of a commodity good and the cost of equipment came down, this market dried up. In hindsight, I should have paid more attention to Cisco exiting that market, which proved to be a good decision. As my clients and partners moved on to other ventures and I was forced to begin prospecting.
Suddenly, here I was with 30 years since I’d written my first program and roughly 20 years of internet and Cisco experience and I was struggling. I had a lot of experience, but didn’t have a portfolio of work that included any big names, mostly small businesses that no one had heard of. I needed a way to give new clients the confidence to call me. I knew that once I started the conversation, I could close the deal. Before that, however, I needed to actually get that call or email. Read More »
Tags: #ciscochampion, CCNP, certification, Cisco Certification
If you are a technology professional, then chances are that you are aware (maybe to the point of annoyance) that everything is getting defined in software these days. We have Software-Defined Networking (SDN), Software-Defined Data Center (SDDC), Software-Defined Storage (SDS), and the list goes on and on. Software defining anything has become such a powerful trend that we now have a generally accepted name and acronym for just that: “Software-Defined Anything” or SDx for short.
Despite the widespread nature of the trend, Software-Defined Contact Center (SDCC) is nowhere to be found amongst the Software-Defined goodness that floods our social media feeds on a daily basis. Software-Defined Contact Center is so absent from the online world that if you search Google for the term you get only articles that reference Software-Defined Data Center, seemly because 3 out of the 4 words are common to both. If you search for the #SDCC hash tag on Twitter you will find yourself at the official account of the San Diego Comic Con. This raises the question, why isn’t SDCC “a thing?” This question is particularly relevant since Cisco’s Intelligent Contact Management (ICM) has been allowing us to build Software-Defined Contact Centers since the late 1990s. Let’s take a look at how ICM delivers on the Software-Defined paradigm for Contact Centers. Read More »
Tags: #ciscochampion, Cisco SDN, ICM, ISDN, IVR, PBX, SDN
IoT, The Oppressed Project
We are now in the era of IoT “Internet of Things”. It’s a concept that not only has the potential to impact how we live but also how we work. And as things become more connected, people become more concerned about their security and privacy. I have gone through a lot of technical conversation about IoT and realized how paranoid people are about their connected devices and appliances.
The future Internet will be an IPv6 network interconnecting traditional computers and a large number of smart objects or networks such as Wireless Sensor Networks (WSNs). By 2020 there will be over 26 Billion connected devices and some estimate this number to be more than 100 Billion connected devices. This includes mobile phones, Smart TVs, washing machines, wearable devices, Microwave, Fridges, headphones, door locks, garage door openers, scales, home alarms, hubs for multiple devices, remote power outlets and almost anything else you can think of like your car and airplane jet engines.
Ways of securing the traditional Internet networks have been established and tested. The IoT is a hybrid network of the Internet and resource-constrained networks, and it is, therefore, reasonable to explore the options of using security mechanisms standardized for the Internet in the IoT.
What will we do about managing the usernames and passwords of every single connected device? What about our privacy? What if some hacker was able to control our video cameras? More and more questions are being asked and more security concerns are being escalated. Do we really have to be paranoid about IoT? Read More »
Tags: #ciscochampion, internet of things, IoT, privacy, security
Here’s the scenario: you have a remote branch office in Miami that has been running smoothly for months. Today you are getting complaints from the site that relate to phone calls dropping, email and network connectivity being intermittent. Management is pushing your team to get it fixed.
You start by looking closely at the WAN circuit going into the site. You use a program that Cisco introduced called NetFlow. By using this program you are able to determine that the WAN link is being saturated by a particular server to server file transfer. You need a quick fix to this issue. You could go with QoS but that could take some time and input from the site to gather statistics on the critical traffic. Instead you decide to utilize Rate-Limiting on the WAN interface.
Tags: #CiscoChampion, #CiscoEnterprise, #NetworkEngineer
Read the full article here.
A new problem has arisen in CCNA class: We have a lab that asks the students to enable a debug command; the debug overruns the console buffer to the extent that commands cannot be entered, and this goes on for more than an hour!
In my 15 years of teaching CCNA classes, we have always taught the dangers of using debug commands on production equipment. To demonstrate this, we would have the students run the debug ip packet command, let it run for 30 seconds, and then turn it off. Of course, turning off the debug is challenging, so we would teach the trick of turning the debug off before we would turn it on: adding the undebug all command to our command history buffer.
Running this test on the 2500 series and 2600 series routers would usually cause a crash and a forced reboot. After we changed the lab equipment to the newer ISR 2800 series, the same demonstration no longer resulted in a router crash; however, it introduced a new problem: loss of control of the command line.
The sheer amount of debug messages would cause the command line to be unusable. The debug messages continued to overrun the console buffer for over an hour before we would finally run out of patience and power cycle the router. In a lab scenario, this causes the students to take an excessive amount of time to finish their lab, and for people studying for certifications, it wastes precious study time. A better way to manage debugs is needed. We would like to see the debug messages (they can be very helpful in both troubleshooting and understanding how protocols function), but we would also like to retain control of the command line. Read More »
Tags: #ciscochampion, CCNA, Cisco ISR