After a long wait of 4.5 years, the 29th edition of SANOG came back to Pakistan, this time in the countrys capital, Islamabad. The Pakistan Telecom Authority (PTA) and the Higher Education commission of Pakistan (HEC) came forward to jointly host the event at the HEC headquarters.
SANOG 29 consisted of two days of conference, one day of tutorial alongside the Internet Society's ION Conference, and the usual five days of workshops with three parallel tracks. Eight days of action-packed agenda was good enough to attract a lot of audiences.
There is no excerpt because this is a protected post.
What’s more likely to spawn change and innovation in networking? A highly-concentrated team working on a small project, or a multi-disciplinary team working on a massive project? Multiple small teams working on 100’s of projects around the globe, or one big massive team banking on a single idea? These questions and more are posed by Bruce Davie, the recently appointed CTO for Asia Pacific and Japan at VMware, and a long time contributor, collaborator, and friend of the Packet Pushers (Greg Ferro and Ethan Banks).
In a brand new Packet Pushers podcast, Bruce, Greg and Ethan take you along for an in-depth look at various networking approaches, and the changes in store for networking as a whole Hear how networking will continue to evolve: namely, how distributed application architectures and other factors are driving big-time industry shifts. Every topic is fair game, and these networking stalwarts aren’t afraid of challenging status quo thought processes to uncover new theories. So, prepare yourself for a lively discussion and debate that transcends the present, and heads straight into the future of networking.
For those who haven’t already hurried to plug in, here’s a preview of a couple topic areas Continue reading
Details on the company's turnaround strategy are vague so far.
It’s funny, in my exerperience, OSPF is the most widely used interior gateway protocol because it “just works” and it’s an IETF standard which means it interops between different vendors and platforms. However, if you really start to look at how OSPF works, you realize it’s actually a highly complex protocol. So on the one hand you get a protocol that likely works across your whole environment, regardless of vendor/platform, but on the other you’re implementing a lot of complexity in your control plane which may not be intuitive to troubleshoot.
This post isn’t a judgement about OSPF or link-state protocols in general. Instead it will detail five functional aspects of OSPF in order to reveal–at least in part–how this protocol works, and indirectly, some of the complexity lying under the hood.
Ever looked closely at OSPF routes in the show ip route
output? You’ll notice flags such as O
or O IA
beside the route.
O 10.1.14.0 255.255.255.0
[110/21] via 123.1.0.18, 00:00:07, Ethernet0/0
O IA 11.11.11.0 [110/20] via 123.1.0.18, 00:00:07, Ethernet0/0
O IA 123.1. Continue reading
The goal is to be able to orchestrate services across multiple networks.