Current differences in app development on devices and controllers disappear. Devices and controllers will share a common programming environment – offering a unified development and deployment experience.
While SDN is moving from concept to reality, we notice that many deployments which focus on creating new network features interpret the role of the “controller” very pragmatically. In these deployments, the controller is not used as an independent layer of software which abstracts the entire underlying infrastructure as in the traditional view of SDN (see for example ONF’s SDN Definition). The pragmatic approach to network programming simply extends the distributed development environment of the network devices using a set of qualities offered by the controller. Developers move those components of their distributed apps to the controller that benefit from the logical centralization or the enhanced resources (CPU, memory) that a controller typically offers while keeping other components on the network devices. Example use cases fall into the categories of distributed network analytics, DDoS thread mitigation, or routing optimization based on performance measurements. What does this mean for our development environment?
Read More »
Tags: controller, Network programmability, onePK, SDN
Welcome to Milano!
Wow, what an activity on the first day at the Cisco Campus / World of Solutions. It’s great to see all these people thirsty for knowledge, and all these people looking for intelligent solutions for their business needs.
One of those business needs is removing complexity from networks by making networks self-managing, or in other words Autonomic Networking. 2014 will be the year that we are shipping the first sets of functionality in this space, so that makes us really exited. After all we have been working on this for more than 3 years internally, and its great to finally see the fruits of that hard work.
Michael has explained in his blog that Autonomics is all around us, but until now there wasn’t a solution that allowed other applications to leverage a common autonomic infrastructure. Finally it is here! The Autonomic Networking Infrastructure allows Service Providers to bootstrap new devices completely zero touch, in a secure fashion, without pre-staging the devices and/or a back-end DHCP Server, and this totally topology independent! Just plug in the device, and watch it getting authenticated, receiving a Domain Certificate, joining the Autonomic Domain, and joining the Autonomic Control Plane, which provides indestructible IPv6 end-to-end connectivity! If an mdns-enabled TFTP server is connected to the network, it will leverage the Autonomic Control Plane to announce its service, upon which the devices will pull in their configuration! Read More »
Tags: #ANI, #CLEUR, Autonomic, autonomic networking, cisco live, Cisco Live Milan, Complexity, self-management, Self-Organizing Networks, SON
Those of you who follow me know that one of the milestones I have for SDN is when we start turning those unicorns into plough horses. While I don’t think we are quite there yet, the partner demos you can check out on the floor in Milan show that we are certainly moving the needle with SDN: Read More »
Tags: #CLEUR, cisco live 365, Cisco Live Milan, SDN, unicorns
Two weeks ago, I presented a webinar on Dynamic Fabric Automation (DFA) and went over the allocated 1 hour to cover the content. Yesterday, as I was doing follow up with a hands-on demo, I went over time too. This illustrates how rich DFA is, and how much there is to say about it! Dynamic Fabric Automation is an environment for data center automation that is centered on the CPOM (Central Point of Management), a set of services that are provided with the new Data Center Network Manager (DCNM) release 7.0(1).
The services available on the CPOM provide the following:
- Power On Auto Provisioning (POAP)
- Inter-switch link connection verification
- A single console for configuration
- Network Auto-Config Profile provisioning
- Message processing for external orchestrator
- Automatic host provisioning
- Embedded management for network monitoring and data collection
All of these services are provided using standard protocols and applications. For example, the POAP service uses DHCP, TFTP and SCP/SFTP, but using a combination of templates and a very intuitive and easy-to-use GUI, DCNM provides a simplified and systematic way of bringing up your data center fabric. The inter-switch link validation or cable consistency check allows the operator to verify the fabric connections against a predefined template and prevent unexpected connections to come up.
The Jabber process provides the single console for configuration, statistics and troubleshooting. Using any XMPP client, an operator can “chat” with the fabric devices; this approach offers the possibility to organize devices in chat groups that match their role, their location or simply some administrative set. With XMPP, a single command can be sent to multiple devices in a secure way.
The most important element of the CPOM is certainly the network profile provisioning. Read More »
Tags: #CLEUR, BGP, Cisco, Cisco Live Milan, Cloud Computing, datacenter, FabricPath, OpenStack, orchestration, VMware vCloud Director
Yep, that’s what we did, and yes we are shipping it today!
As Michael’s blog explained, autonomics are all around us, both in feature implementation (e.g. a routing protocol like OSPF) as well as in architectural frameworks like GANA. But while the former has created isolated, per feature domains of autonomicity, the latter has never really resulted into a useable implementation used by a network engineer to date!
Lets go back to what we said out the vision of Autonomic Networking was going to be, as in the below figure, which I essentially repeated from my DON’T PANIC blog. The observant reader will notice that I changed the term ‘simple management tools’ into ‘SDN/NMS Controller across a simplified northbound interface’. After all we can’t ignore markets trends like SDN.
The vision remains the same whether you use an iPAD versus a super-duper controller though: you ingest a network wide behavior into the network, as we can model the totality of the network in an abstract, location-independent, network-wide manner. Autonomic Processes turn this network wide behavior into local state, and might invoke control loops between nodes to do this effectively. This ultimately results into the good-ole legacy network protocols to become self-managing, without changing the protocols themselves. Genius! But how do we get there in practice? And can customers trust us to do the right thing from day 1? Read More »
Tags: #ANI, Autonomic, autonomic networking, Complexity, self-management, Self-Organizing Networks, SON