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 »
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 »
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 »
It’s that time of the year again -- time for some computer and human networking at Cisco Live Milan! This year I’m taking the unusual and somewhat risky step of blogging about the network infrastructure before the event. This is because we’re going to try something interesting for the networking folks. We are going to try and get rid of the Legacy IP, otherwise known as IPv4.
Before you get too worried -- no, the dual stack network setup does not disappear. Lots of critical parts of our everyday lives still need the old and proven protocol to successfully operate, so removing it would be irresponsible to say the least. But some of you may be interested to try (in a controlled fashion) exactly how strong the ties to the old good legacy. If you are one of these people, this post is for you -- because this blog entry is one of the few places, if not the only one, to find the IPv6-only SSID name and access credentials.
First of all, what’s the big deal with IPv6-only access network, wasn’t this tried before?
Sure, it is not all new. The first time we tried an IPv6-only network was at IPv6 World Congress conference in Paris, early spring 2012. We also had an IPv6-only SSID in one of the Cisco Live US conferences. We discovered that the subset of the operating systems that could successfully operate in this kind of environment was pretty small. But as time passed, evidence suggests the situation was slowly improving. Read More »
IPv6 deployment is accelerating at a fast pace. It’s exciting to see that the global IPv6 deployment figures show a continuing upward trend:
We are also showcasing our IPv6 deployment adoption later this month at the annual Cisco Live Europe event in Milan. We are proud to announce that IPv6 content and demonstrations will be key features at our event from the show room floor to technical sessions, breakouts, panels, labs, and more. Read More »