Cisco CMX Mobility Developer Challenge is under way at topcoder. CMX Mobile Application SDK can be leveraged in a mobile application to provide indoor location and navigation for users. The SDK will connect with the CMX Mobile App Server to determine a user’s location, downloading maps, venues, point of interests, and determine routes for a selected point of interest. The CMX Mobile Application SDK can also receive a mobile push notification when application is not running. When notified, the application can be launched and include message how to join the customer network when first initiated. The core feature is the indoor location which displays current location of device on the map. The location updated as a user moves through a venue and can help navigate the user to some defined location.
The topcoder challenge is to use the CMX Mobile Server SDK to create a new app using a simulated environment for a meeting host to automatically launch a WebEx conference, based on the location of the conference room where the meeting is scheduled.
The SDK is composed of several modules to allow for varying types of application integration. The CMXClient is the core module for getting client and venue information. Read More »
Tags: API, App, Cisco, client, cmx, coder, Conference, core module, develop, developer, device, location, map, mobile, notification, program, programmer, sdk, server, simulator, software, technology, topcoder, venue
For those of you who follow the Cisco Data Center blog in general and my blogs in particular, you’re probably thinking it is time I updated you on this topic. You’re right! But it is almost time for Cisco Live and I will be presenting it there. Read More »
Tags: B-Series, blade, C-Series, capex, opex, rack, ROI, server, tco, UCS
As the year comes to a close, I wanted to revisit the economics of Cisco Unified Computing System (UCS).
Cisco UCS has fantastic technology. Technology that technical decision makers are demanding. But what about business decision makers? The question for them is how will UCS save them money? Read More »
Tags: blades, Cisco UCS, rack, ROI, server, tco, UCS, x86
I recently wrote a blog titled Blade Server TCO and Architecture – You Cannot Separate Them and thought a little more on the architecture side would be a good thing.
With so much misinformation (dis-information?) about UCS running around in the ether, I thought the straight forward comparison offered here would be valuable. It is important to dispel myths and analyze reality before making the important decisions around server and networking refreshes / upgrades, which by necessity affect long term data center architecture. I hope you will find this presentation -- Cisco UCS, HP and IBM -- A Blade Architecture Comparison, useful in your decision making process.
For me, there are three primary drivers that differentiate the Cisco UCS architecture from everyone else’s designs and they can be divided into the buckets below:
You could, and probably should, ask what is left out? That’s pretty easy. I did not specifically call out Performance and TCO, for a good reason. If you can execute on the three bullets above like Cisco UCS does, Performance and TCO are the natural derivatives. You shouldn’t have to target them separately. It’s kind of a “If you build it, they will come” scenario. That’s why I made the statements in the TCO and Architecture blog that “…Server cost is irrelevant (to OpEx) because: changing its contribution to total TCO has a vanishingly small impact….” and “…It [architecture] is the single most important component of OpEx…” For more on this and how server cost and TCO intersect, please check out this blog -- Blade Server TCO and Architecture – You Cannot Separate Them. It takes a look at the OpEx and CapEx components of TCO, and how altering either of them effects the actual total 3-year TCO. You may be surprised.
Cisco is providing trade-in credits for customers’ old generation servers and blade chassis, helping ease the transition and upgrade to a new UCS blade architecture. The UCS Advantage presentation below has more details on this fantastic program that can further enhance the already compelling TCO benefit of upgrading to Cisco UCS.
Special note: For more on the benefit that Cisco UCS delivers for I/O and throughput, I suggest a great blog by Amit Jain -- How to get more SAN mileage out of UCS FI. Amit does an excellent compare / contrast of FC and FCoE technologies (“…8 Gb FC yields 6.8 Gb throughput while 10 Gb FCoE yields close to 10 Gb throughput…”).
Tags: blade architecture, blade architecture comparison, blade server, blade server architecture, blade server TCO, capex, Cisco, Cisco UCS, data center, data center TCO, HP blades, HP BladeSystem, IBM blades, IBM Flex Fabric, opex, server, server TCO, tco, technology, UCS
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