In December, Cisco introduced Cisco CloudVerse, a framework and set of solutions that combines the foundational elements needed to enable organizations to build, manage, and connect public, private and hybrid clouds. Cisco CloudVerse combines these key cloud elements – Unified Data Center, Cloud Intelligent Network, and Cloud Applications and Services – enabling businesses to realize all of the benefits of clouds: improved agility, better economics, enhanced security, and a dynamic, assured experience.
As a leading technology company, Cisco pushes the envelope in our traditional industries with innovative business transformations, as we did by entering the server market in 2009 with our Unified Computing System paired with our Nexus data center switching family. Competition in the marketplace is good for customers as competition accelerates innovation, creates new opportunities as old problems are attacked from new angles, and creates incentives for the various players in the industry to work together–and separately–toward better solutions.
But achieving the promise of this progress and innovation comes with a necessary step that I feel is often overlooked, rushed, or ignored: Testing. At Cisco, we perform intense testing as we develop our solutions whether the testing is in-house, with partners and customers, or via third-parties.
Over 70 percent of leading cloud providers are using Cisco CloudVerse on their journey to the cloud, and–in the latest example of our commitment to testing–third-party testing firm EANTC has validated those cloud providers’ commitment by affirming “Cisco has all the components one would need to offer cloud services”. For coverage, Light Reading has published the first report of the Cloud Mega Test results done by EANTC.
But let’s talk more about what was behind the test.
Read More »
Tags: cloud, cloudverse, customers, EANTC, light reading, Mega test, nexus, Testing, UCS
Widely deployed from the core to the edge, IP/MPLS has achieved huge success as a mature, standards-based technology now deployed by virtually every service provider worldwide. As a result, the industry has chosen to extend IP/MPLS and develop a transport profile called MPLS-TP (MPLS Transport Profile). MPLS-TP is the packet transport technology of choice being developed by the IETF to allow service providers to cost effectively migrate existing transport networks to packet based solutions.
Recently EANTC conducted an MPLS-TP Interoperability Event which focused on testing and demonstrating interoperability of key IP/MPLS and Carrier Ethernet features between multiple vendor platforms. This represented a critical technology demonstration for service providers as they begin their migration to packet transport networks.
Read More »
Tags: asr 9000, carrier packet transport, cpt, EANTC, ietf, interoperability, IP/MPLS, isocore, itu-t, MPLS OAM, MPLS-TP, p-ots, Service Provider, standards, Y.1731
There has been a lot of buzz recently about a second OAM (Operations, Administration, and Maintenance) solution for MPLS-TP that will cause interoperability problems between MPLS-TP and MPLS. It is accurate that there is an alternative OAM based on ITU-T Y.1731 (Ethernet OAM) proposed by a number of vendors and countries and indeed, it will cause interoperability issues. As a strong believer in standards, I certainly hope that a second approach does not occur because vendors and customers do not need the additional cost burden that a lack of interoperability causes. The fact is that only the draft recommendation for MPLS-TP OAM based on Y.1731 has begun the first step in a very long approval ITU process – but nothing more – and in my estimates will take well over a year and could easily take up to two years to standardize. IETF MPLS OAM is widely deployed in MPLS networks today and will simply be extended as MPLS-TP is deployed as a next generation transport solution. In fact, recent interoperability testing of MPLS-TP took place at the MPLS World Congress earlier this month in Paris.
I believe that after careful consideration most operators will see the benefit of having a single end-to-end methodology to operate and manage converged packet optical transport networks, which MPLS-TP using MPLS OAM provides. Operators who select another method that is perceived to meet their short term needs now my ultimately learn that it fails to provide everything they had expected, and that having multiple OAM methods (one for Ethernet and another for MPLS) is not cost effective. It will be interesting to see what happens moving forward. At the very least, operators should make an informed decision on which approach is right for them.
Read More »
Tags: EANTC, ietf, interoperability, isocore, itu-t, light reading, mpls, MPLS OAM, MPLS-TP, Service Provider, standards, Study Group 15, Y.1731, Y1731