By Gina Nienaber, Marketing Manager, SP Product and Solutions Marketing
Cisco estimates over 50 billion new devices will be connected to the Internet by 2020. To support the Internet of Everything, service providers must undergo an infrastructure transformation. The network needs to become more open, programmable, automated, adaptive, and agile. To guide this transformation, the Cisco open network strategy for service providers is depicted as three interwoven layers: the Evolved Programmable Network (physical and virtual network Infrastructure), the Evolved Services Platform (for orchestration of resources) and Applications and Services layer to enable virtualized services such as Cloud VPN and Security. With these three layers working together, providers can begin to realize the benefits of an open network that is readily open to new devices, open for quickly enabling new services, and open to endless possibilities.
Last week, Cisco announced two Read More »
Tags: Cisco Evolved Programmable Network, control, epn, esp, evolved services platform, IPv6, NFV, open network architecture, open network strategy, programmability, SDN, Service Provider, SP, virtualization
Network Consulting Engineer
Customers reach out to Cisco Services because they have confidence in our skills and abilities. One way we build that confidence for our customers—and for ourselves—is through certifications and specialization.
- As we study for certifications, we gain confidence in our understanding and abilities to execute in our areas of study.
- As we test our knowledge against known standards, we prove competency, which also improves our self-confidence.
As the networking industry evolves, the role of the Network Consulting Engineer (NCE) also must evolve. Gone are the days of configuring and managing a large-scale network via command-line interface. Read More »
Tags: certifications, evolution, NCE, programmability, services, skills
When last we left our hero, he (that is, me, or I) was getting a crash course in Nexus programmability and trying to understand what all of this stuff meant. I had plied Jim* with beer in order to get him to explain to me – using the available napkins in the bar – what the technology was, what it meant, and why I should care. Read More »
Tags: Chef, nexus, onePK, programmability, Puppet, python, Ruby
I know that I take a different approach to learning new things than most people. At least, I know my approach is different than the way people present them. The good news is that when I get something, I really get it. However, when looking at the juggernaut that is “Software-Defined X,” or even “programmability,” I know that I’m still a long, long way away from feeling like I have a handle on it.
When I wrote the previous blog post on some of the key “Open” terms were in programmability, I was overjoyed to find out that there were a few people who also had difficulty getting a grip on this too.
In other words, I’m not alone!
There is still a bewildering amount of information that I still need to learn, however, and it seems to me that if I resonated with a few people about these high-level topics, there are probably a few more who are curious about what lies beneath as well. Fortunately I work for a company (and with a lot of people) who have been willing to help me. Read More »
Tags: CLI, netconf, nexus, programmability, python, SDN
By Greg Nehib, Senior Marketing Manager, Cisco
Part 2 – Virtualized Services in an EPN World?
In part one of this series Gina covered the basic definition of an Evolved Programmable Network or EPN and its linkage to the Cisco Evolved Services Platform (ESP). Figure 1 offers a quick visual recap.
Figure 1: Cisco’s Open Network Strategy
And here’s a link to part one of this blog series if you need to play catch up.
In this segment we Read More »
Tags: Cisco EPN, Cisco Evolved Programmable Network, control, epn, esp, evolved services platform, IP and Optical Convergence, IPv6, NFV, ONE, programmability, SDN, Service Provider, SP open network environment, virtualization