Cisco Blogs


Cisco Blog > Mobility

Non-stop Wireless at Johns Hopkins Hospital

June 30, 2014 at 10:42 am PST

Johns Hopkins Medicine is one of the leading health-care providers in the US. The Johns Hopkins University School of Medicine is consistently ranked as one of the top Medical Schools in the US and the Johns Hopkins Hospital is consistently ranked #1 in the US for 21 years in a row! In a previous blog in 2012, we described how the Cisco Wireless LAN controller 7.5 release enables wireless networks to recover with no client re-authentication in the event of a primarily controller failure. In this blog, I will share more details about unified access deployment at the Johns Hopkins Hospital with particular focus on the High Availability design.

jhu1

Patients are the focus at Johns Hopkins Hospital. Johns Hopkins uses state-of-the-art technology in their hospitals to ensure that patients get the latest advances from surgical tools, radiologic imaging suites with the best diagnostic capabilities to something as humane as sound-absorbing private rooms for each patient. Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Mobile Location Based Services Trends of 2013

The holiday season which began with Cyber Monday on December 2nd 2013 has just ended and analyzing the impact on mobile commerce sales and location based services unveils some very interesting trends.

Firstly, at the macro level:

  • Online shopping increased in the USA in 2013 by over 16% compared to 2012.
  • From a mobility perspective, almost a third of all online sales (29%) were made from Smartphones or Tablets.

Clearly there are changes in the online marketplace, but in order to examine this a little further, let’s look at a few key questions to help understand what is happening in this marketplace:

  1. What are the major trends?
  2. Is mobile commerce just a US phenomenon?
  3. What impact does location based services have?
  4. Where are the main benefits coming from analytics?
  5. How is privacy fitting in to all this and how is the attitude of mobile consumers evolving?

Trends 2013:  Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

How Does Enterprise IT Respond to Consumerization? To Mac, BYOD, and Whatever Comes Next?

There’s a new force changing the way Cisco IT operates, the way we plan and develop new services, and the way we support our employees. Consumerization is showing us how to help our employees to be more productive and more satisfied – if we can learn to listen and respond. Read More »

Tags: , , , , , , , , , , , ,

A Culture of Transparency

Many Cisco customers with an interest in product security are aware of our security advisories and other publications issued by our Product Security Incident Response Team (PSIRT). That awareness is probably more acute than usual following the recent Cisco IOS Software Security Advisory Bundled Publication on September 25. But many may not be aware of the reasoning behind why, when, and how Cisco airs its “dirty laundry.”

Our primary reason for disclosing vulnerabilities is to ensure customers are able to accurately assess, mitigate, and remediate the risk our vulnerabilities may pose to the security of their networks.

In order to deliver on that promise, Cisco has has made some fundamental and formative decisions that we’ve carried forward since our first security advisory in June 1995.

Read More »

Tags: , , , , , ,

Cisco’s onePK Part 2: Reaching out to a Network Element

Exordium

In the previous installment of the onePK series, you received a crash course on Cisco’s onePK. In this article, you’ll take the next step with a fun little exposé on onePK’s C API. You will learn how to write a simple program to reach out and connect to a network element. This is staple onePK functionality and is the foundation upon which most onePK applications are built.

Preambling Details

The following short program “ophw” (onePK Hello World), is a fully functional onePK application that will connect to a network element, query its system description, and then disconnect. It doesn’t do anything beyond that, but it does highlight some lynchpin onePK code: network element connection and session handle instantiation. This is the foundational stuff every onePK application needs before useful work can get done. Read More »

Tags: , , , , , , , , , , ,