ONS summit 2014 starts Monday March 3, and for me it is my first time here. It hardly feels that way. For us in Cisco ACI (Application Centric Infrastructure) team, it is busy last few days as we are putting final touches to showcase our exciting ACI solutions, demos and presentations to customers at this premier SDN event. Early in 2014, Cisco ACI expert Mike Cohen has made insightful predictions on what awaits SDN in 2014 – Read his Blog
Mike zeroes in on key Data Center use cases for SDN, starting with Application Deployment Acceleration securely and at scale. No one can disagree with this. L4-L7 services chaining for physical and virtual devices is another killer use-case Mike enlightens the reader with, and at the ONS Solutions Expo this year, we are showing exciting demos to illustrate service automation using dynamic L4-L7 service chaining. Do not miss out our demos at Cisco Booth 302. We are also showing demos focused on Open Stack integration with ACI, another area of growing interest.
I strongly recommend you to attend Mike’s Theater presentation titled, “Role of Policy in SDN” on March 5, 12.40 PM. Learn all the benefits and value-props that a declarative policy based ACI approach brings to network operations that is today crippled by imperative management, lack of scalability and flexibility. You will be excited to discover how our Cisco ACI team is working with Open Stack, Open Daylight initiatives and driving an open eco-system. Mike will also touch on how ACI helps bring visibility across both physical and virtual infrastructures, and how today’s SDN network overlay problems can be overcome. Shashi Kiran posted a fantastic blog on SDN overlays in ACI deployments, last week, and it makes compelling read in the context of Mike’s session.
We wish you a great ONS summit this year and look forward to seeing you at Cisco Booth 302
Tags: ACI, Cisco ACI, Cisco APIC, L4-L7 service chaining, Open Daylight, Open Stack, SDN
The proliferation of different types of device interfaces places a significant burden on application developers and equipment providers alike. One of the reasons for the rise of Software Defined Networking (SDN) is its promise to simplify management by providing a single point through which the entire network can be managed and administered. This raises the question whether this promise extends towards dramatic simplification of the device interface landscape as well, specifically, whether SDN can put an end to device interface proliferation and in the future a single management and control interface may be all that is required. Unfortunately, it turns out that this particular hope is unsubstantiated. Here is why.
The Promised SDN Land of Interface Simplification
Much has been made of the need to align the various interfaces through which networking devices can be managed and controlled. It has been difficult enough to just keep SNMP implementations consistent. Throw CLI, syslog, and Web Services into the mix, and the task becomes daunting indeed. One reason why different interfaces have to be supported has to do with customer preferences, of course. Chef is the new paradigm to support? Sure, we’ll add that. ReST is becoming en-vogue? We’ll support that too.
In the middle of all this, along comes SDN. “Don’t bother with individual devices and their legacy interfaces” is the siren call. “Use a controller to orchestrate the network instead” – a single point of control through which the network can be operated and maintained, an enticing value proposition indeed. Early SDN technology such as OpenFlow made a big splash and gained a lot of mind share this way. Rather than messing with the hodgepodge of existing interfaces, a single interface was introduced to control OpenFlow switches. Just support this one interface, or so the message went, and your equipment can join the New World of Software-Defined Networking, leaving the Old World of fragmented interfaces behind, much like early European settlers coming to America hoped for freedom and a better life, leaving behind constantly quarreling fiefdoms and many centuries of historical baggage. Read More »
Tags: Cisco SDN, control interfaces, device management, SDN
On February 18, Cisco announced the evolution of service provider (SP) networks. It is probably a good idea to step back, just a little, and explain how Cisco sees the challenges ahead and how we intend to continue to provide our mobile service provider customers with the strongest portfolio of solutions in the industry. That’s the reason I am writing this blog post. In it, I hope to share with you some of our learnings from the past year and also, explain a little bit about the rationale for our announcement.
We are virtualizing our entire SP portfolio. The year 2013 is one where the concept of “Network Function Virtualization” (NfV) caught the industry by storm. In NfV, virtualized network functions are software appliances executing on virtual machines delivered in a telco cloud environment. In a nutshell, NfV is attractive to our customers because it allows them to clearly delineate the respective values of software, hardware and professional services for total solution integration. Practices based on data center techniques promise to reduce the cost of operating the network and simplify work processes through the agility we are seeing today in the cloud environment. And none of this evolution will compromise the ability of service providers to deploy multi-vendor solutions though it is fair to state, procurement practices will need to re-align to this brave new world. For example, rather than procure integrated network functions to be assembled into a network, service providers may have to separate out layers Read More »
Tags: dpi, Gi-LAN, network function virtualization, NFV, RAN, SDN, Service Provider, virtualization
As I was thinking about how best to advise you on how to “experiment” with SDN technologies, and more specifically why you should run a formal pilot to evaluate SDN technology options (a topic I covered in my previous blog), I was reminded of this “wipeout” picture I took last year at a “freeride” competition – the “Coe Cup” – at my local ski mountain, Glencoe Moutain Resort, here in the UK. Let me tell you why!
Why you may want to “pilot” new technology adoption!
Tags: ACI, Cisco onePK, cisco_services, network virtualization, OpenFlow, SDN, software defined network
In the announcement of the Cisco Evolved Services Platform last week, we not only highlighted our initial service offers in mobility and video and the business benefits it enables, but also that it was open, extensible and elastic. Openness is critical for providers by nature of the fact that their networks – often global in scope and mind-boggling in scale – require all the different technologies and often from different vendors installed to create the network experience desired actually can work together. If not, it limits the offers they can take to market or requires operational contortions to make work, either of which would affect the provider’s ability to do business.
That’s why our engineering teams are so focused on making the Evolved Services Platform so Open. They have incorporated Openstack and Open Daylight (SDN) protocol suite; they’ve made it fully compliant with ETSI NfV (MANO), 3GPP Gi-LAN and more. In fact, their efforts in the more than 60 standards bodies helps us to factor into our roadmaps the latest understanding of the current standards and, just as importantly, where they are going.
But in addition to standards, the Cisco Evolved Services Platform needs to also be multi-vendor. And on the first day of our largest tradeshow of the year, Mobile World Congress in Barcelona, where pleased to highlight Broadsoft, Intel and Mavenir are joining in their endorsement of our approach. Here’s what they said:
“At BroadSoft we are the leading application provider and working toward the NFV implementation with an open eco-system. We share an open platform strategy with Cisco around virtualization, orchestration and automation that provides an environment where customers, partners, and independent developers can freely innovate and develop integrated applications that offer greater value to users. We are excited to work with Cisco to provide a virtualized/orchestrated VoLTE solution on the Cisco Evolved Services Platform.”, said Scott Hoffpauir, Chief Technology Officer, BroadSoft.
“With the virtualization capabilities enabled with the Evolved Services Platform, Cisco is able to address industry requirements for orchestration of services across both virtual and physical infrastructure,” said Rose Schooler, Vice President and General Manager of the Intel Communications and Storage Infrastructure Group. “By utilizing the advanced features of the Intel Xeon server platform, Cisco is able to deliver solution architectures that are enabling the performance agility on fully open compute systems that service providers need to quickly scale new services, more customized to customer needs, with a faster time to market.”
“Virtualization is transforming our business by providing the agility, flexibility and profitability for service innovations. More importantly, providing a cloud platform that is open, extensible and elastic for mobile solution providers is a key step toward realizing this direction. We are pleased to see Cisco making this vision a reality to the industry and its partners by providing the Cisco Evolved Services Platform.”, said Bahram Jalalizadeh, EVP of Business Development, Mavenir Systems
These, along with Openwave Mobility and Metaswitch, make up the initial members of the Cisco Evolved Services Platform Ecosystem, to help avoid making multi-vendor environment hamper a SP operations but rather to help give the service provider flexibility to pursue even more opportunities as they stay Open for business.
Tags: broadsoft, cisco esp, evolved services pkatform, Intel, mavenir, OpenStack, SDN, Service Provider, virtualization