Cisco’s secret weapons are our engineers and our commitment to innovation that solves our customers’ business problems.
When we committed ourselves to being the leader in networking virtualization in the service provider industry, our team has been maniacally focused on Network Function Virtualization (NFV) to enable our customers to transform their network architectures and prepare their businesses for the future.
We doubled the number of virtualized functions last year, and have done the same again this year, to reach more than 100 – a number that represents the breadth of our portfolio and the scope of the opportunity this new approach to networking brings to service providers.
AT&T is utilizing Software Defined Networking (SDN) and NFV technologies to create dynamic, on-demand services. In March, we announced our joint efforts with virtualization to connect cars in Europe, and are pleased that we can work again with our long-standing partner, as they lead the shift to next-generation networking by providing customers more flexible and scalable services and experiences.
AT&T and other trailblazing service providers are in an enviable position, bringing together people, processes, data, and things to make networked connections more relevant and valuable than ever before.
By combining Cisco’s expertise and industry-leading portfolio with AT&T’s vision and industry leadership, together we are working to capture new business opportunities that deliver on the promise of virtualization.
It seems people sometimes have this view of SDN as addressing rather esoteric use cases and situations. However, the reality is that while there are instances of ‘out there stuff’ happening, there are many situations where we see customers leverage the technology to address pretty straightforward issues. And these issues are often similar across different business/vertical/customer types.
Aftab Rasool is Senior Manager, Data Center Infrastructure and Service Design Operations for Du. I recently had the chance to talk with him about Cisco’s flagship SDN solution – Application Centric Infrastructure (ACI) – and Du’s experience with it. I found there were many instances of Du using ACI to simply make traditional challenges easier to deal with.
Du is an Information & Communications Technology (ICT) company based in Dubai. They offer a broad range of services to both consumer and business markets, including triple play to the home, mobile voice/data, and hosting. The nature of their business means the data center, and thus the data center network, is critical to their success. They need a solution to effectively handle challenges of both deployment, as well as operations…and that’s where ACI comes in.
I’ll quickly use the metaphor of driving to summarize the challenges Aftab covers in the video. He addresses issues that are both ‘in the rear view mirror’ as well as ‘in the windshield’ – with both being generalizable to lots of other customers. What I mean is that there are issues from the past that, though they are largely behind the car and visible in the mirror, still impact the driving experience. There are also issues on the horizon that are visible through the windshield, but are just now starting to come into focus and have effect.
Rear view mirror issues – These are concepts as basic as scalability associated with spanning tree issues, or sub optimal use of bandwidth, also due to spanning tree limitations. These issues are addressed with ACI, as there is no spanning tree in the fabric, and the use of Equal Cost Multi Pathing (ECMP) allows use of all links. Additionally, use of BiDi allows use of existing 10G fiber plant for 40G upgrades, thus obviating the expense and hassle of fiber upgrades. As a result, the ACI fabric, based on Nexus 9000’s, provides all the performance and capacity Du needs.
Windshield issues – These are represented by a range of things that result from business’s need for speed, yet are diametrically opposed by the complexity of most data centers. The need for speed through automation is becoming more and more critical, as is simplifying the operating environment, particularly as the business must scale. Within this context, Aftab mentioned both provisioning and troubleshooting.
Provisioning: Without ACI, provisioning involved getting into each individual switch, making requisite changes – configuring VLANs, L3, etc. It also required going into L4-7 services devices to assure they were configured properly and worked in concert with the L2 and L3 configurations. This device by device configuration not only was time consuming, but created the potential for human error. With ACI, these and other types of activities are automated and happen with a couple of clicks.
Troubleshooting: Before ACI, troubleshooting was complicated and time consuming, in part because they had to troll through each switch, look at various link by link characteristics to check for errors, etc. With ACI, healthscores make it easy and fast to pinpoint where the challenge is.
Please take a few minutes to check out what Aftab has to say about these, and other aspects of his experience with ACI at Du.
Guest Blog by Igor Dayen, SP Product and Solutions Marketing
In an age of agile service creation with a virtualized IT infrastructure, the delivery of services by cable operators is undergoing a transformation. Two key technologies that are fueling this change are Software Defined Networking (SDN) and Network Function Virtualization (NFV). In this blog, we will examine how SDN is transforming service delivery for cable operators.
SDN offers much promise to cable operators. It changes how networks are designed, operationalized, and monetized, making them far more agile and responsive to customers. In traditional switch and router system architectures, the control plane is implemented in software running on a general-purpose CPU and the data plane is implemented with specialized hardware such as an ASIC. What SDN does is remove the Read More »
Are you looking to deliver an intelligent, dynamic and highly optimized programmable network where applications have control in how they explicitly traverse the end-to-end network?
If so, you have probably been watching the Application Engineered Routing story unfold since it was launched in March 2015. For those of you following this developing chapter in the end-to-end application control play book, you might have read the past few blogs by my colleague, Frederic Trate (here and here) or even watched Dave Ward, Cisco CTO and Chief Architect, present on engineering the network for applications on the main stage at MPLS World Congress 2015 earlier this year (see Featured Content).Read More »
I was reading the latest ACG Research report on Mobile IP Infrastructure and reflecting how the importance of the IP Packet Core has evolved, and how the technology leaders in this area have also evolved.
Back in the “3G era” the Packet Core sat alongside the Voice Core, and was considered an adjunct to the Radio Access Network. The traditional RAN vendors would often bundle the core as part their end-to-end contract. Since initial data services where Mobile Broadband, and monetisation was just based on volume, 3G Packet Cores were all about “feeds and speeds”.
With 4G/LTE the all-IP nature makes the Packet Core the heart of Read More »