Apart from sharing URIs and Patterns between clusters, ILS naturally shares UDS data, including home cluster.
In the example below, only a single _cisco-uds._tcp record can exist due to a shared dns zone, however using feature group templates to control the home cluster setting means the user will be “found” and home cluster information will be relayed with the request so the client finds it’s home.
I was asked to help come up with a Proof of Concept using DNA Center APIs for Cisco Live 2018. After a few days in the sandbox, my group decided on an app that gives granular data on power usage using energy wise along with actionable outcomes.
Along with granular cost analysis per IDF, per switch or per port, there is an included calculator for instant cost-benefit analysis. For instance, it takes 7.85kWh or $0.83/mo to power a Cisco 9971 phone but only 2.52kWh or $0.27 to power a newer, more efficient Cisco 8841 phone. At a cost of $250 per, over the span of 10 years, replacing 1,000 phones save $68,133 in power savings alone!
Since I didn’t think I could sit at my first Cisco Live and work a booth talking about charts all day, I decided to add a little “pizazz”. I made a IP Phone app that enrolls your desk phone to your cell phone as a paired device. Typically energy wise is smart enough to turn off your phones screen after 5PM or on the weekends, but with Meraki Scanning API and a location-aware network, phones (and other devices) can turn off and on as needed. Think of a stadium full of APs – leaving a couple on for probing new users and lighting up more as needed!
Pro Tip: When using Meraki Scanning API at an event like Cisco Live with 30,000 people, you may want to tune the power down on the AP, or be ready to re write the body-parser library to handle more throughput and to clean your laptop hard drive every 30 minutes 🙂
Camp Create is a part of Cisco’s DevNet Create conference and each year they pick about 30 people in groups of 5 and assign a topic. Think of it like a hackathon with some constraints to work with and a coach to guide you.
Since my wife is a teacher, I decided to pick the Education track, and our app “Roll Call” solved the challenge of both: taking roll, and gathering assignments through Cisco Spark and Cisco Meraki APIs.
Having worked with the Cisco Spark APIs, I took on making a bot that serves as the front end to gather assignments and take roll, but also guided the group around the design to make sure everything came together.
One of our group members did a talk on Microsoft’s Face API, and had the idea to use facial recognition to sign onto the WiFi. To track the user to the classroom, Meraki’s Scanning API sends the Device MAC address to a database that stores only the last 10 minutes, and flags those students as “online”
Once the bones were in place, taking roll and asking for assignments was simple.
When you change your dogs food, they get sick all over the place, they just can’t stomach change. As an IT professional, the dog food we know and love changes frequently.. The technology you spent all that time learning about last year is obsolete.
Don’t get mad, adapt! As a collaboration engineer, my title didn’t exist 20 years ago. During the TDM to VoIP migration, analog teleco guys were forced to adapt or find new work. When virtualization came on the map, the ability for one person to manage hundreds of servers meant that the early adopters got a new title and quite possibly a pay raise, while the ones late to the game found themselves no longer needed.
This blog is adapting, too. Let me throw out a few buzzwords: API, IoT, REST. Knowing what they mean and why they are important might save you from being the next casualty of change. It’s about asking more from technology. People don’t expect their GPS to just give them directions anymore. They want voice navigation with social networking that tells you where the cops are hiding, and they want it to predict when you’re leaving to go to work and tell you how to traffic is. From a development perspective, the GPS apps with the most APIs get the most love, and almost everything is OPEN, meaning you or I could “tap” into that technology, helping both parties.
I recently gave a presentation on coding along with the CTO of the company, Vinu Thomas. One of the points he made that really stuck was this: try to automate your own job. If you’re smart enough to do that, I promise you’ll be just fine.
I started asking during phone migrations: why do I have to tell the router what the new phone’s mac address is, if the switch already knows? Why can’t the switch and the router work this out between themselves? Why do call center agents have to login to their phone every day if they also login to their computers ? I think we’re almost there, if not already. Both of these use cases: extension mobility and ios-xe have APIs. So do yourself a favor, hang in there, and learn Python.. or Ruby or my favorite: Node.js