Troubleshooting networks can be a difficult, frustrating experience, one that, for the most part, has received little attention from vendors. Network troubleshooting can sometimes be like peeling an onion, with each layer revealing more problems until the core issue can be found. Unfortunately, modern network operators are mostly still hobbled by those ancient warhorses ping and traceroute for troubleshooting.
Dinesh Dutt explores network troubleshooting and explains how to avoid common network problems ranging from misconfigured cabling to misbehaving protocols, how a modern networking tool chest can help simplify network configurations, and how automation is improving troubleshooting turnaround times to minimize downtime. Dinesh covers everything from how to choose the right network architecture and ensuring the physical network is well designed to new tools that not only help troubleshoot deeper network problems but also provide a platform for automating troubleshooting. You’ll leave ready to troubleshoot any data center networking challenges that come your way.
Dinesh Dutt is chief scientist at Cumulus Networks. Dinesh has been in the networking industry for 15 years, most of it spent at Cisco Systems, where he was involved in enterprise and data center networking technologies, including the design of many of the ASICs that powered Cisco’s megaswitches, such as Cat6K and the Nexus family of switches. He also has experience in storage networking from his days at Andiamo Systems and in the design of FCoE. Dinesh is a coauthor of TRILL and VxLAN and has filed over 40 patents.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com