Geek Toys – The future of Apple TV

As WWDC approaches, I once again hope for a new Apple TV. The Apple TApple TVV has so much potential, and so much disappointment associated with it. Will WWDC be the time when we finally see an update? The bigger question is, with such strong competition from other products, has Apple already missed the boat?
I’ve spent quite a bit of time thinking about what I would like to see in a new Apple TV. There has been a lot of change in the last few months around home entertainment, and if Apple really wants to own the space, it has to adapt to compete. There are some key features that I think could make Apple TV ready to own the space again.

Siri

When I hear people discuss using Siri on an Apple TV, I rolled my eyes. I hate Siri. I refuse to use Siri. However, that changed just a little when I received an Amazon Echo. Amazon has knocked voice recognition out of the park! Alexa is fast, error free, and simply amazing. It is so good, I actually caught myself preparing to say “Thank you” to a piece of hardware! Each morning I ask Alexa for the news and my commute information. I use it when cooking for timers. Alexa is the only reason I use Prime Music. Let me repeat that. I began using Amazon Prime Music only because Alexa made it so easy. Make Siri that good on an AppleTV, and I get it now.

Facetime HD camera and mic

I do not understand why this hasn’t happened before. An Apple TV that could connect via FaceTime, is a no brainer in my opinion. Besides the ability to talk with relatives and friends through a TV, a camera could provide a lot of other features. The camera or mic could be used as a detector for HomeKit automation. Add some face recognition, and use it to choose the profile, and permit or deny content based on age restrictions. The list goes on and on.

HomeKit Integration

Imagine the Apple TV turning on lights when motion or sound is detected. It could also provide the remote view capabilities required by those of us who regularly travel and would like to check on our homes. This would be an easy way to integrate HomeKit and directly compete with the existing products on the market from Belkin and Wink and many other companies. I love my Wink Hub and the attached lights, sensors, and outlets. I hope that Apple gets the integration right.

4K

Apple has built the 5K iMac to encourage 4K content creation. 4K content only becomes valuable once there is an easy way to consume that content. Apple TV should be that avenue.

Glances and notifications

The notifications on Watch are the reason I love my watch. There is no reason why this same thing shouldn’t work as a pop-up on the Apple TV.

A decent remote!

Apple works hard to refine every detail of their products, which leads me to ask. What happened? The AppleTV Remote is simple, small, and sleek. It is also the worst of the worst of the entertainment hub remotes. It uses IR, which means it must be in direct line of site of the AppleTV. Anyone who has used both an Apple TV and a Roku or Amazon Fire TV understands what I am talking about. The Roku and Fire TV remotes can be oriented in any direction, and yet they still work. The devices themselves can be hidden behind TVs or in closets and they still work. Not so for the AppleTV. It is time to move to BluetoothLE for the remote and show IR the door.

Games, apps, blah blah, blah.

I don’t play games. I try to care…but I don’t.

Cisco Live US 2014 – Return to Camp

In May, I made my way to San Francisco for CLUS 2014. I had very fond memories from last year, and was looking forward to catching up with all of the great people that I met in Orlando.

This year was a little different for me. I purchased a full pass, paid for airfare, and my hotel all out of my own pocket. The ultimate question this year was going to be answered. How much is CLUS worth? Is the experience equally important when thousands of dollars come out of my pocket to experience it.

First, the most obvious difference this year was how crowded the experience was. Moscone was simply not big enough for 26,000 people. I recognized on day one, as I was looking for a place to sit for breakfast, that when San Francisco was chosen 5 years ago, the conference was much smaller. Conferences book their locations years in advance, and in this case the attendee base grew faster then they expected.

The large crowds definitely affected the experience. The World of Solutions reception on Monday was so crowded that I spent only 15 minutes there, and the majority of that time was trying to get back out. The crowds also affected the on-site meals. Lunch each day consisted of a boxed meal, breakfast was carb heavy, and the days that I went into the dining hall, it was extremely crowded.

On Thursday, I had an opportunity to talk with Kathleen Mudge, who manages the Social Media Team, and Kathy Doyle, the Director of Cisco Live, about the scale of the conference. Kathy mentioned that there were over 6,000 people who registered for Cisco Live at the conference. That is an incredible 23% of the attendees that could not be accounted for until the first day.

With that in mind, I can’t fault the conference. In-fact, I am surprised that the conference was able to absorb that many people and function at all. That is an amazing feat.

The next few years are in bigger venues, so I expect the conference won’t experience these growing pains again.

The sessions that I attended were all excellent, and allowed me to expand my knowledge in a few key areas that I had identified as needing more work. I didn’t attend as many sessions as I had planned, but that was simply a matter of not having enough time.

As for the social side of CLUS, it was everything I was hoping for. I was able to reconnect with friends made at CLUS 2013, and made many more. The Social Media Hub (which we quickly renamed the Social Media Routed Bridge) was in a great location. Power was easily available for recharging devices. The arrival Tweetup was well attended, and we were able to gather on Thursday for the final picture by the Cisco Live sign.

The Cisco Live Social Media Team at CLUS is always on top of the game. They work incredibly hard to help anyone who ask. They also keep things interesting with various games and prizes. I can’t say enough about the team, and how their work affects the positive experiences of so many attendees.

The parties and the Customer Appreciation Event were all excellent. I was able to participate in three Tech Field Day events, attended the CCIE party again as a non-CCIE, and participated in multiple Cisco Champion events. They were all opportunities to meet more people, and hang out with this huge group of engineers that I get to call friends.

Now for the question. Was attending CLUS on my own dime worth it? If my Cisco Live 2014 experience only included the standard CLUS sessions, the Customer Appreciation Event, and the World of Solutions, I would have to say “no”.

However, Cisco Live is much more than sessions, expo, and parties to attend. Cisco Live is a gathering of people who are passionate about technology and life. Cisco live is space camp, or as Denise Fishburne has begun calling it, simply “Summer Camp”.

Was Cisco Live worth it? Oh yeah. I’ll be back.

The Internet of Things begins to mature with Apple HomeKit

One statement that I have repeated many times is that the Internet of Things (IoT) will not mature until a non-technical person can buy a myriad of devices and configure them all through a common interface. Apple HomeKit seems to be that interface. There are a few things that I like about the announcement:

  • Apple isn’t going to make outlets, switches, and thermostats. They are leaving that up to the experts. 
  • Apple makes great interfaces, and I believe they are capable of doing the same for Home Automation.
  • The IOS user base is large enough to make this market explode. With an increased user base, comes more products.

Again, if you didn’t read it correctly the first time. This market is about to explode. 

One last thought. Apple started with the user, just like they did with iPhones. How many iPhones are now in our corporate environments? What happens when HomeKit migrates into the office?

Cisco Live Guest Keynote Speaker Announced – KHAN!!!

Salman Khan was just announced as the Guest Speaker for the Closing Keynote at Cisco Live US. If the name seems familiar, you have probably heard of the Khan Academy.

Picture of Salman Khan of the Khan Academy

Salman Khan of the Khan Academy

The Khan Academy uses technology to create online training which can be used anywhere in the world that has internet available. They have an incredible vision, and the backing to make it happen. I am really excited about hearing Salman speak. In my mind, the Khan Academy is the power of the internet put into practice, I might even call it a redeeming quality. Every time I see a tweet of Justine Bieber’s blowing the internet up, I simply have to remind myself that people like Salman Khan are countering the idiocracy with knowledge.

If you haven’t registered for Cisco Live US yet, now is the time to do so.

Geek Toys – Jabra Motion UC

Last week, I reviewed the Jabra Speak 450, which was provided by Jabra for a review.

Jabra Motion UC

Jabra Motion UC

This week, brings a review of the Jabra Motion UC. You will notice there is no disclaimer this week, as my Jabra Motion UC was supplied by my employer for testing, not by Jabra directly.

The obvious question is, why am I reviewing a product, when I have no obligation to do so? The answer is simple, because I REALLY like this bluetooth headset.

The model that I received included a dock/case, Jabra Link 360, and charging cable. The dock/case is quite ingenious, making it easy to store and travel with all of the accessories, while also providing a dock when at your desk. The case has traveled with me for a couple of trips, and has held up extremely well.

Battery Life

My average Tuesday is packed with meetings. I regularly have 8-10 meetings in a single day, all of them via phone, Lync, or Webex. With this schedule, the only time the headset goes into the charger is during lunch. The specs report 7 hours of talk time. While I have never tracked talk-time for a charge cycle, I have never found myself without battery.

Audio Quality

The loudness and clarity of the headset is very good. The noise rejection is also very good. The headset has two mics, which are back-to-back. With this setup, one mic is always used to pickup voice, the other is used for noise identification and isolation.

Comfort

The headset fits behind and over the ear. Its fit and weight make it very comfortable. Once I adjusted to the fact that it never felt tight on my ear, I was suprised by how well it held on. Short of head banging to an 80’s hairband, its going to stay with you.

Improvement Needed

There are two things that I would like to see improvement in. The first is the way the headset is switched from ear to ear. The process requires spinning the rubber earpiece on it’s mounting surface. This isn’t easy to describe, and it isn’t easy to do. The second issue has to do with the volume control. The touch control sometimes requires multiple swipes before it responds; other times, a simple bump is all that is required.

Wrap-Up

Despite the two areas that I would like to see improvement in, this is the best bluetooth headset that I have owned out of nearly a dozen units. It is comfortable, the battery last long enough for an entire day, and the range is exceptional. Ultimately, if I were to leave my current employer tomorrow, I would buy a Jabra Motion UC.

Geek Tools – OpenGear ACM5004 Console Servers

While I was at Cisco Live, I was invited to sit in on a Tech Field Day event with OpenGear. This was my first Tech Field Day, and hopefully not my last. You can see the full video here: http://techfieldday.com/event/clus13/

Additionally, you can see a great blog post, written by Bob McCouch,
about the event here:
http://herdingpackets.net/2013/07/13/openly-passionate/

and Blake Krone’s take on the event here:
http://blakekrone.com/2013/07/09/one-console-to-rule-them-all

In short, OpenGear did a awesome job presenting a new product, the IM7200. They asked us about use cases, answered all of our questions, and impressed quite a few of us in the room.

After the event, I ended up speaking with their team about a couple of ideas that I had for their product. Based on that conversation, they were nice enough to make a unit available for testing. I received it a couple of weeks after Cisco Live, set it up on my network, and began playing.

For the past three to four weeks, I have been using the console server on my network, and trying to figure out what I wanted to write about it. I’ve started this post at least three different times, and each time scrapped the post after an hour of work. Why was it so hard to write about you ask?

Because this is one loaded device! This thing has EVERYTHING you could want on your network.

WHAT IS GOOD?
-RJ45 ports for connecting to console ports. No special cables, no adapters in most cases, no rollover cables. Plug one end of a straight-through cable into the console sever, and the other end into the console port of a switch or router, and away you go.
-In addition to standard console ports, the ports can be configured in a number of various ways. This should allow for connection to almost any device in your network.
-SSH, Telnet, FTP, TFTP, HTTP, HTTPS, DHCP, NTP, SNMP, DNS Server/Relay, and the list goes on.
-Once you have devices connected, you can access them various ways. SSH, Telnet, no surprises, right? How about a web terminal? Yes, it is that awesome.
-I/0 ports. These ports can be sensed (door sensors, environmental monitoring, etc) or set (activate a relay to release a door.) Imagine with me working on a remote site, you ask the user on the phone to walk over to the door. You unlock the door for them, and see when the door is ajar. You ask them to complete your task, and then to close the door. Does the user close the door, or hang out and play in your IDF? Well, now you know.
-USB Port. The usb port can be used for flash storage, or it can be used to connect to devices which only support USB console devices.
-Easy to set firewall rules. Do you only want SSH allowable outside of the trusted network? No problem. Settings are made with a checkbox.

I could keep going. I could mention the IPSec, OpenVPN, and DDNS options…but I won’t.

WHAT COULD USE WORK?
My gripes are pretty small with this device.
-The documentation and product CD push additional software (SDT Connector) for creating connections. Really, I don’t see the purpose. Connections to the ports are easily made over SSH (or Telnet if you like living on the edge) by specifing the correct tcp port; 300X for SSH and 200X for telnet, where X is the console port number.
-Because this device has SO MANY OPTIONS, I think some default options would make setup faster and easier. If you could select a group of ports and assign a Cisco Console Profile to them, and choose another group and assign a APC Environmental Monitoring Profile to those, setup would go much easier.

Ultimately, what you need to know is that this device is a Linux server. It is capable of doing anything that a small Linux server can do. What makes this such a compelling product is that Opengear has packaged all of the daemons and services that can be used in a network into a single simple to use form-factor. Let’s face it, we spend our day configuring complex network services. Our network and device management shouldn’t be
difficult.

This isn’t the last that you will hear about my impressions with the Opengear ACM5004. I’m currently working on a use-case at work which I will write up in the near future. If you have any questions, let me know in the comments.

***Opengear provided an ACM5004 for this review. No other services or payment were received.***

Wireshark: Capture CDP and LLDP

A couple of years ago, I wrote a short piece about filtering CDP and LLDP packets using Wireshark. Since that time, I have simplified the way that I filter these packets, and based on feedback, and additional use of that information, I wanted to post an update. This will hopefully guide people to the best answer immediately. 

CDP

CDP sends all packets to the L2 multicast address of 01:00:0C:CC:CC:CC. Therefore, our filter can be:

ether host 01:00:0c:cc:cc:cc

However, VTP (VLAN Trunking Protocol) also sends packets to this address. Since the default timer for VTP is 300 seconds, and the default timer for CDP is 60 seconds, this shouldn’t be an issue. Additionally, since VTP packets are only sent out trunk ports, if you see VTP packets on a port that a user should be connected to, you may have just found your problem.

 LLDP

Link Layer Discovery Protocol, AKA 802.1AB, is an IEEE standard. While Cisco doesn’t support LLDP out of the box, it can be enabled on your Cisco gear. HP, Juniper, Dell, and everyone else that I have ever worked with supports LLDP by default. The L2 multicast address for LLDP is: 01:80:C2:00:00:0E. However, LLDP has the benefit of a unique EtherType. That type is: 0x88cc. Based on that information, we can filter with either:

ether host 01:80:C2:00:00:0E

OR

ether proto 0x88cc

The default timer for LLDP seems to vary across vendors, although 30 seconds is the default for Cisco and quite a few others.

Wireshark Portable

If you are the roving type that walks out to the users desk, Wireshark can be ran as a portable app from a USB device.

Cisco IP Phones

Cisco IP Phones will send out CDP packets onto the PC port. What good does this do? I don’t know. However, hit the webpage hosted on the phone and you can find the CDP and LLDP info on the Network Statistics >Network page.

Firewalls

Embarrassing story time. Like a lot of engineers, I regularly use Wireshark to look at packet captures from other devices. After doing this for months, I needed to use Wireshark on my local LAN port. I started by spending 20 minutes trying to figure out why I wasn’t seeing CDP packets. Of course, once I remembered that I had a local firewall to contend with, I quickly fixed the issue, and haven’t made that mistake since. Don’t make that mistake. Disable the local firewall.

Finding new coworkers

We have once again started the process of expanding our team at my workplace. We always bring new employees in as a contractor first, and if things work out, the contractor is usually offered a full time position.

Our interview process is fairly hard. First, all recruiters are provided with 10 questions, of which each candidate must answer 8 out of 10.These are all basic CCNA level questions.

Next, we schedule a phone screening, where we ask more specific questions that are broken up into different areas. Layer 2, Layer 3, OSPF, and QOS are all on tap for this portion of the interview process. If we feel that the person was able to answer enough questions correctly without frantically searching for answers to recite back to us on the internet, we move them onto the third phase.

In the third phase, the person comes into our offices, and we provide them with equipment and instructions. They have 2.5 hours to configure a router, switch, and an AP per our instructions and answer a few questions based on those configurations. Once they have completed the configuration, we move into a Q&A portion of the interview, where we ask off the wall questions, mixed with troubleshooting scenarios of increasing complexity.

Every person who has ever left an interview felt well abused. If they paid attention, they know their weaknesses, and could use it to start a personal improvement plan. We in-turn, have a solid read on each candidates abilities, strengths, and weaknesses, and whether they would make a good addition to the team.

This process is long and arduous; the last time we went through this process, we started the interview process on almost 60 people before we found three we liked. 

I can’t knock our process though. In-fact, our team is so strong that I have turned down multiple offers at other positions, which payed more, simply because I like my teammates in my current role.

It seems that every time I consider taking a different role, I get pulled into interviewing more candidates, and am reminded what it is like out there in the rest of the world. Case-in-point, here is an email excerpt from a potential job candidate:

What did I say about scheduling issues earlier in one of your calls.  All day long not a single trouble call comes in.  5 minutes before the time for the phone interview I get a call and 3 tickets logged into our dell kace service desk.  Figured since I was finally done withe the remote assistance calls working from my terminal I would drop you a line while I am on the phone with one of the users that is having problems at the entire locationlocations that is having a problem that I am trying to get through to them it is sunding like a provider problem to let me let them go and get a hold of the provider.  Always love a network that uses back up internet connections that are all from the same cable provider(comcast) so come off the same pole and think that it is a gfood redundancy feature.  Not the one I am working with but we have one service center location that has all 3 retail branches of our company and instead of  getting an upgrade on the connection type with 3 static ips for the way they like to do things but really makes no sense what so ever they have 3 cable modems all coming off the same pole so that they can supposedly have a better more stable connection makes me have nightmares about wasted money and the stupidity of the outside consultants that engineered this network.  

After speaking to you prior to the interview time and you mentioning questions about switch configurations I will kinda admit you got me thinking it has been almost 10 years since I have programmed a true cisco switch do little netgear knock offs almost weekly and switches had always been my weak point give me a router or a pix device and I could make it sing but even on those I am rusty.  Put me in a lab environment and it would be just like riding a bicycle but just giving me verbal questions I would be stumbling all over myself.  Which looking at things makes me belive that this wouldn’t be the right position for me until I get back into the game and work away some of this rust.

If you don’t feel sick after reading that email, then a part of your soul is dead already.

Hey Apple, Help Us, Help You!

When the iPhone debuted on the AT&T network, AT&T was clearly not expecting the demand that was created. They were caught off-guard by the influx of customers, and more importantly they were surprised by the data consumption of users, who had purchased a device created to consume data. Problems were reported at a ridiculous rate, and rumors abounded everywhere within the Tech blogs that Apple was threatening to take their ball phone and go home to Verizon if AT&T didn’t do something fast.

In the mean time, Apple began working on ways of optimizing the iPhones use of the carriers network, and kept pushing AT&T for improvements. It took AT&T a couple years, and a LOT of money to build their network up. Some people will argue that if the iPhone had not been made available on other carriers that AT&T would still be having issues.

Apple studies, lives and dies by user experience. They knew that a poorly performing network would reflect on their device. It was not enough to simply blame the network. If the network wasn’t available, then features of their phone weren’t available either.

With that in mind… Apple DOES NOT provide developer access to wireless API’s in IOS. Troubleshooting WLAN issues for IOS devices can only be accomplished from the infrastructure side. Without jailbreaking an iPhone, there is no way to access RSSI, SNR, or other WLAN statistics.

Which device is best for troubleshooting iPad connectivity issues on a WLAN? If you answer anything other than “another iPad”, go directly to jail, do not pass go, and do not collect $200. This is an oversight decision that Apple needs to quickly reconsider.

Apple, we are the network. Without WLAN Engineers, iPads and iPhones won’t function correctly on corporate networks. Without the proper tools, WLAN engineers cannot support IOS devices when there are issues on the WLAN. Without tools, our network problems reflect on your devices. Help US, help YOU.

Supporting Apple devices on the WLAN

Since the iPad was released, it has received a mixed welcome within Enterprise environments. While a lot companies have at least some plan to move forward with iPads, these drivers are usually coming from the business side, instead of IT. In-fact, most IT shops are being dragged into IOS support with strong reluctance.

The broad questions which are causing resistance can be summed up in one word: SUPPORT. IT departments must figure out how to support the device in multiple areas. Information integrity and control, end-user support, and connectivity support all must be dealt with. Since this is a networking blog, I want to deal with the last one; and will do so in the next two articles.

Supporting iPads on the network is more complex than connecting them to an SSID and providing login credentials. If we look at the standard iPad user in most organizations, we see a highly mobile user, users who also have laptops. Most of these users requested an iPad after having a positive experience with their company issued iPhones. That translates to a user having three wireless devices at there desk at any given time: their laptop, their iPhone and their iPad.

To understand the problem this creates, let’s look at how we survey for a wireless network. There are two considerations: coverage and capacity.

Wireless Coverage
A survey can be  based on square footage, and provide a certain RSSI from wall-to-wall. This is a perfectly acceptable way to survey if everyone has their own office. However in Cube-ville, a single AP may cover 100 desk or more. If each desk has one wireless device, you now have a physical medium (the channel or airspace) that is incapable of supporting all of the connected clients.

Wireless Capacity
The other way to perform a wireless survey is based on capacity. In a high capacity environment, the wireless spectrum, not the AP is the bottleneck. More on this later…

In a capacity based scenario, a number of desk are chosen, lets say 25. For every 25 desk, there is an AP. Those AP’s are placed based on coverage area, and in to minimize channel overlap. For the same 100 desk in Cube-ville, you now have 4 AP’s. Since there will be channel overlap, the radios are turned way down, and in general, the physical medium is now capable of handling the number of clients.

Taking this environment to the next step, each desk gets an iPhone, and a few months later, 1 in 4 request an iPad. We can safely assume that complaints will begin coming into IT about the wireless network. The AP airspace that was previously servicing 25 clients now contends with 62 per AP. Time for another wireless survey and at least twice as many AP’s!

Now we can see the problem that many companies are facing. The i-devices are here, and businesses seem to love them. The network team must begin planning and building now. I would like to make a few suggestions which might keep network teams from finding themselves behind the eight  ball.

  • Budget to begin surveying your high density environments now.
  • Develop a plan for support, complete with timelines and cost. Present this to the highest management level you can reach, so that it can be considered as the business begins planning device deployments.
  • If your company has a charge-back system for devices, be certain a cost is associated with each IOS device to support the wireless network going forward.
  • Be certain to include a survey and additional equipment as a cost of any iPad rollout projects, make certain the business can see the total cost of deploying iPads and iPhones.
  • Finally, be first in line to get an iPad if you don’t already have one. You can’t support what you don’t understand; besides, it really is a great device.

I realize that there are other options out there other than the “i” devices. However, I haven’t heard of, or seen, a single enterprise level roll out. However, these rules apply to the world of Android and Windows too. More devices per square foot equals more demand on the wireless network.