Many of you take part in our annual satisfaction surveys. You share opinions, discuss challenges, and make valuable recommendations. More than 65,000 customers and partners responded to our survey during the first half of FY13. For this installment of the “We’re Listening” blog series, I asked Joe Pinto, Senior Vice President, Technical Services, to review these responses and what we’re doing to improve your Cisco experience.
By Guest Contributor Joe Pinto
While overall feedback from our customers and partners in FY13 has been positive, we know there is a continuous need for improvement. One of the questions you often ask is, “What is Cisco doing to make Cisco easier to do business with?” Here’s a sampling of areas you’ve asked us to address and progress we’re making in those areas: Read More »
“Applications?” I hear you say. ”Why are Cisco talking about application? They’re a networking company!?” If this is what you are thinking, I’m glad you are reading this blog. As we’ve broadened to be an IT company, we in Cisco Services have been quietly building our application migration capability for the past 2 years. And with cloud, as the leading designers of cloud IaaS infrastructure, we in Cisco Services are in a unique position to help you migrate applications to the cloud, where the skillsets required are not only application migration, but a deep understanding of how to enable your applications to genuinely exploit the capabilities of your cloud infrastructure.
Which takes me to the subject for this blog, Domain 8 in the Cisco Domain TenSM framework -- Applications, following on from my Domain 7: Platform discussion the other week. In our view in Cisco Services, (business) applications are the primary reason for the existence of the data center. Applications drive so many of the decision in the other facets of the data center. And when it comes to cloud (which is my theme for this Cisco Domain Ten series), there are additional considerations related to migrating applications to the cloud. Let’s discuss some of these in this blog.
Domain 7 in our Cisco Domain TenSM framework for data center transformation is what we call “Platform”. More specifically, this term refers to the “software platform” upon which your business applications will run. In short, this area is where we examine operating systems, databases and other types of middleware and help you figure out your strategy, architectural decisions and implementation plans in these areas, to help you drive a more successful cloud or data center project. Let’s discuss this area in more detail.
First, though, if you are new to the Cisco Domain Ten, please check out my “Cisco Domain Ten: The Story So Far” summary blog I published recently. Additionally, earlier this week, we ran a public webinar, where some of my colleagues in the Cisco Data Center and Cloud Services team gave their perspectives on Cisco Domain Ten. If you missed this and their very practical insights, please do catch up on the Cisco Domain Ten webinar recording.
Over the past 2 months or so, I’ve been blogging on Cisco Domain TenSM, Cisco Service’s framework to guide you on your path to data center and cloud transformation. We are just over half way through the discussion on Cisco Domain Ten, so I thought it worthwhile, especially for anyone reading about this concept for the first time, to write a quick refresher and summary of the articles I’ve written so far. So forgive the brevity and please do dive into the links/URLs for more information if indeed you missed these articles first time. And if you’ve read every article -- thanks!
My last post was all about finding IPv6 prefixes on the IPv6 Internet. I think the next natural question is “What about IPv6 traffic?” or more specifically, “What about IPv6 traffic on my network?” In this post, I’ll talk about some network tools, or instrumentation, that can be used to find and measure IPv6 traffic that is out on your network. Network instrumentation is going to be important whether you plan to integrate IPv6 into your network or not. “What?” you might ask, “why is instrumenting my network to detect IPv6 important if I’m not going to run IPv6 in my network?”