For a few of us in the Cisco Brussels office the last weekend of January always marks a special occasion.
The weekend is dedicated to the Free and Open-source Software Developers’ European Meeting (FOSDEM) conference in Brussels, with around 5,000 visitors attending. The event happens at the ULB (Université libre de Bruxelles) campus, but traditionally uses its own network infrastructure, sponsored by Cisco. And we, who are Cisco employees, volunteered our time to help the community as well as meet some new friends and get extra hands-on experience with a sizable network.
What was different this year was that just before the official start of the conference I finally figured out how NAT64 works, gave a 5 minute warning on twitter (image below), and then disabled IPv4 on the main network (simply stated I removed the IPv4 address of the router on the client interface so that only the IPv6 address remained).
That meant that visitors would only get an IPv6 address Read More »
Tags: cisco live, disabling IPv4, FOSDEM, IPv6, IPv6-only SSID, NAT64
That is it, Cisco Live Milan is over! The “before” of anticipation, seemingly a moment ago, is replaced by the “after” of takeaways and accomplishments for the week. Some passed their CCIE certification, some met a new business partner, but it’s likely that everyone learned something new. I am not an exception.
During the week, I presented at two different technical breakout sessions (BRKRST-2304 -- Hitchhiker’s Guide to Troubleshooting IPv6 and BRKEWN-2666 -- IPv6 on WiFi: You talk too much! NOT anymore) and spent my remaining time working with everyone in the Network Operations Center (NOC) to ensure that IPv6 is a smooth ride for all of the 9,000+ devices on the network. Not only did I learn a lot, but this year at Cisco Live Milan was a year of “firsts” for me.
- For starters, it was the first time I shared details about my experience with large-scale IPv6 WiFi setups with Cisco Live attendees in the form of a breakout session. After talking with attendees, my main takeaway -- Read More »
Tags: #CLEUR, #IPV6ONLYEXP, Cisco Live Milan, Cisco Live NOC, IPv6, IPv6-only WiFi, NOC
As Cisco Live Europe 2014 draws to a close I wanted to reflect on what has (for me) been a personal campaign to raise the visibility of IPv6 in the World of Solutions / WoS (the demonstration / show floor of the event)
Last year at Cisco Live London I heard some comments that there was not enough IPv6 in the WoS. I decided to see if I could encourage Cisco Business Units and Partners to enable demonstrations for Dual Stack operation and highlight that fact. I wrote previously we would be “awarding” an “IPv6 Enabled Logo” to all Cisco and Partner demonstrations that took the step of enabling Dual Stack and highlighting the same fact.
How did we fare ? Cisco Live 2014 Milano showcased over 15 IPv6 enabled demonstrations including two which were enabled as “IPv6 only”. These were spread between Cisco and Partner booths and were mainly marked with the newly created green “IPv6 Enabled Logo”.
I personally visited a number:
Read More »
Tags: autonomic networking, Cisco, cisco live, first hop security, IPv6, LISP
I am not qualified to discuss it much, but can you guess what this does?
ne = NetworkElement("172.16.66.1", "JasonsApp")
conn = ne.connect("admin", "cisco", sc)
intf1 = ne.get_interface_by_name("FastEthernet0/1")
If you guessed that it logs into a switch at 172.16.66.1 and disables interface F0/1 for 5 seconds and re-enables it, then you guessed right.
Let us talk a little about putting the “ability” in programmability. Did I code in college? Yes. Was I good at it? Not really. Dijksta’s algorithm (the actual coding bit) drove me crazy, however, actually using and operating networks quickly became my cup of tea. I became a network geek. Subnets? Awesome! Cisco CLI? Sweet. Using Enhanced Interior Gateway Routing Protocol (EIGRP)? Yay! AVVID? Even better. But I never wanted to see C++ or another “program” again.
Fast forward to 2014. I’m still a networking guy but now I’m seeing code again. The good news is, maybe like you, I hang out with some really cool people. I challenged a couple of them to help me demonstrate program “ability” to networking people on the show floor at CiscoLive Milan…with me as the test subject! Read More »
Tags: #CLEUR, Cisco Live Milan, Cisco ONE, networking, onePK, programmability, Programming with Python, python
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