![](https://static.wixstatic.com/media/b2cc1d_5b3f8b9ffdeb4b27a01d75c936d8480e~mv2.jpg/v1/fill/w_482,h_302,al_c,q_80,enc_auto/b2cc1d_5b3f8b9ffdeb4b27a01d75c936d8480e~mv2.jpg)
There was a time when capturing packets was straightforward; set up a mirror or SPAN port, connect the analyzer to the destination and away we go. Now life is much more complex.
There was a time when capturing packets was straightforward; set up a mirror or SPAN port, connect the analyzer to the destination and away we go. Now life is much more complex.
We have blade servers that include switches, VMs chatting via Virtual Switches and the older issue of capturing traffic between two programs running on the same operating system. In this session, we cover the tips and tricks that enable us to get those lovely network packets. We look at what works in an enterprise environment and what you should avoid.
Author Profile - Paul Offord has had a 37-year career in the IT industry that includes roles in hardware engineering, software engineering and network management. Prior to founding Advance7, he worked for IBM, National Semiconductor and Hitachi Data Systems.
Paul and the problem analysts at Advance7 help IT support teams in many business sectors to troubleshoot difficult performance and stability problems. Paul played a key role in the development of the RPR problem diagnosis method and is currently leading the TribeLab project to explore new ways to help IT support people learn troubleshooting skills.