Garland Technology ensures complete packet visibility by delivering a full platform of network TAP (test access point), inline bypass and packet broker products.
Garland Technology is committed to educating the benefits of having a strong foundation of network visibility and access. By providing this insight we protect the security of data across your network and beyond.
Garland Technology's resource library offers free use of white papers, eBooks, use cases, infographics, data sheets, video demos and more.
The TAP into Technology blog provides the latest news and insights on network access and visibility, including: network security, network monitoring and appliance connectivity and guest blogs from Industry experts and technology partners
Our extensive technology partnership ecosystem solves critical problems when it comes to network security, monitoring, application analysis, forensics and packet inspection.
Garland Technology is dedicated to high standards in quality and reliability, while delivering the greatest economical solutions for enterprise, service providers, and government agencies worldwide.
I love testing out configuration myths.
OK, to be fair they are probably not myths - but many of these suggestions work in very specific situations. I try to caution my friends and clients that blindly following a configuration suggestion can lead to more problems. In other words, your mileage will vary.
When I see a tip or trick that will improve performance, I try to understand what the issue was for the author, what impact the change had and what was their testing methodology.
Ideally I would like to reproduce the test and results to prove that this either worked or that this change made no difference. The last scenario would be if this caused more issues and to back out, but that should be an obvious conclusion and procedure.
In this example I remember reading about Cisco’s ip dns configuration command which turns your Cisco router into a DNS proxy or sorts. This is helpful if you do not have a DNS server locally and if your DNS lookups take a considerable amount of time (i.e. 30ms and higher).
Here’s how a sample configuration looks:
Router1# configure terminal
Router1(config)# ip dns server
Router1(config)# ip domain-lookup
Router1(config)# ip name-server 184.108.40.206
Now the fun part: I captured packets of the following scenarios:
From my Windows computer, I executed the following commands:
Watch the video here:
Tony Fortunato, CCNA, CFNI, CWI
Sr Network Performance Specialist
The Technology Firm
Getting things to work better - bit by bit-
Linkedin Profile http://ca.linkedin.com/in/fortunat
Lovemytool Blog: http://www.lovemytool.com/blog/tony-fortunato/
Youtube Channel: http://www.youtube.com/user/thetechfir
Google Plus: http://plus.google.com/+Thetechfirmplus
Certified Wireshark and Fluke Instructor
Want to learn more about the many network tools that help you manage your network? Download What Your Network Is Missing: 7 Tools To TAP
Tony Fortunato is a Senior Network Performance Specialist with experience in design, implementation and troubleshooting networks since 1989. Tony will teach or troubleshoot on your live network as part of his customized onsite training service for your staff.