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.
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: access, aireOS, blade, Cisco, client, controller, deployment, design, device, diagnostic, equipment, health care, healthcare, High Availability, hospital, IOS, johns hopkins, LAN, mdf, medical, Mission Critical, mobility, NCV, network, patient, re-authentication, release, text, unified, Voice, voip, vss, wi-fi, wifi, wireless, WiSM2, wlan
Previously I have blogged about No SSID Outage and No Client Reauthentication whereby even if your Cisco Wireless Controllers were to fail due to any reason, the clients will NOT experience any downtime due to Stateful Failover functionality to a Standby Controller. What could be better than that? Controllers that never go down!
A picture is worth a thousand words! As you can see the above the WEBGUI on a 5508 series wireless controller shows that, it is running 7.0 code which was an MD release, has been operational for over a thousand days or over three years! Read More »
Tags: access, Cisco, client reauthentication, controller, downtime, failover, functionality, health, hospital, MD, operational, patient, product, release, services, solution, SSID, standby, stateful, voice-over, webgui, wi-fi, wifi, wireless
As the famous saying goes, “Good things come to those who wait”. Delayed gratification -- person’s ability to forgo a smaller reward now for a larger reward in the future -- has been linked to better life outcomes as demonstrated by the often cited Stanford Marshmallow experiment and others. In most cases though, it requires a degree of self-control not easily achievable in today’s fast paced, ever-changing world with new mobile devices, protocols and technologies.
If you are one of the Cisco Wireless customers currently deploying Release 7.0 MD and waiting for the next Cisco Wireless Software Maintenance Deployment Release, the wait is over!
Release 188.8.131.52 has achieved Maintenance Deployment (MD) status.
Release 184.108.40.206 is the recommended MD release for all non-802.11ac deployments. For 802.11ac deployments, Release 220.127.116.11 (Release 7.6 Maintenance release 1) is the recommended release.
For additional details on Software Release Recommendations and Guidelines, see Guidelines for Cisco Wireless Software Release Migration
Below are top 10 reasons (in no particular order) to upgrade from the current 7.0 MD release to the latest 7.4MD Release.
10. FlexConnect (improved and rebranded H-REAP) with efficient AP upgrade across WAN, BYOD policies support, Flex ACLs and split tunneling. Read More »
Tags: 11ac, 802., 802.11, access point, ACL, analytics, AP, App, Apple, application, Bonjour, byod, Cisco, client, controller, customer behavior, deploy, device, flex, flexconnect, guideline, H-REAP, High Availability, hop security, IPv6, L3 domain, licensing, maintenance deployment, management, MD, migration, mobile, mobility, network, onboarding, outage, Packet, packet optimization, policies, policy, protocol, recommend, release, scale, security, services, SKU, software, split tunneling, standby, stateful switchover, support, technology, tunneling, upgrade, virtual, virtual footprint, WAN, wi-fi, wifi, wireless, WLC
The University of Nevada, Las Vegas (UNLV), founded in 1957, is located in the heart of showbiz industry in Las Vegas. The school offers higher education programs ranging from business, engineering, fine arts and music, and science, and professional schools such as dental medicine and law.
The school’s mascot, Hey Reb, was recently featured on Hulu’s “Behind the Mask,” and you may recognize the Southern Gym during the dance scene between Elvis Presley and Ann-Margret Olsson in the movie Viva Las Vegas.
With over 24,000 unique WLAN users per day, 1.1 gigabytes of throughput per second, and more than 50 wireless access locations across campus providing WLAN coverage, this educational institute demands a massive Wi-Fi network.
In the previous blog, we highlighted some of the Bonjour enhancements of the 7.5 software release and the deployment of Bonjour at St. Margaret’s Episcopal School, a K-12 school. In this blog, we will describe details about UNLVs WLAN deployment, how they use Bonjour services, and give you an insight into rapid pace of innovation necessary to support this technology in the education arena. Read More »
Tags: 11ac, access point, administrator, aireOS, AP, App, Apple, application, AVC, Bonjour, Cisco, cleanair, control, controller, deployment, EFT, EFT code, freeradius, granularity, High Availability, ip, location, network, openldap, policy, release, service, SSID, standby, Stateful Switch Over, sub-second, technology, UNLV, user group, vegas, visibility, VLAN, webgui, wi-fi, wifi, wlan
Following the last MSE blog on CleanAir, today I wish to explain how we prioritize the Mobility Service Engine’s user experience.
Listening to customers and implementing changes/features based on customer feedback has been a great strength of Cisco products. We from the Mobility Services Engine team strongly believe in this principle and make sure that we reach out to each and every customer who has provided a feedback on Cisco MSE and take their experience with MSE into consideration when designing future features and enhancements.
After analyzing the feedback we received during the MSE 7.4 release, I am pleased to announce that we have decided to implement the following two features as part of series of enhancements that we believe will improve the customer’s user experience with MSE.
Convenient Backup and Restore
Until the 7.4 release, MSE users had limited options in backing up their MSE data. The only supported option was to use the NCS FTP server as the destination for MSE data backups. Due to the limited disk capacity on NCS, as well as sharing of the disk space with other network elements, disk space limitations prevented MSE users from regularly backing up their data. If you are one of those users who always wished you could regularly backup MSE data without running into NCS disk space limitation, or if you wish you could back up your MSE data to non-NCS devices, we have some good news for you.
In the latest MSE 7.5 release, we have added the option to backup and restore your MSE data on remote FTP servers, provided there is connectivity between the MSE and the FTP server. Similar to NCS Backups, MSE data can be backed up to configured repositories (internal or external FTP servers). Love the command shell? We will also be coming up with CLI to backup MSE data. You can now start MSE backup using just a single command.
Read More »
Tags: backup, Cisco, configuration, customer, data, design, device, enhancement, feedback, ftp, location, mse, release, restore, server, setup, technology