Protocol Analysis, Data Recorder, CALEA, Lawful Intercept, Application Performance, User Experience, Industrial Ethernet, Data Loss Prevention, Deep Packet Inspection, NetFlow, SOX, HIPAA and PCI Compliance, Switching and Routing, Forensics, VoIP, IPTV ... etc.
IPv6 could be awesome but it is getting scary, Why?
I do not dislike IPv6, but it seems a scary transition, at this time…It has some great attributes but it has gotten out of control – where IPv4 was easy to implement and was a few steps higher than the previous version, IP Before (IPv4 )as I call it …..
IPv6 is like stepping out of an airplane at 50000’ with no parachute - It is a VERY long drop!
Currently the landing is the killer! Where will it lead us?\
Starting I do not like the fact that from the network and processor views running dual stacks eats up processor, bus and network time and traffic not to mention adding complexity to all of our current applications and communications.
I was on the IPNG and IPv6 committee back in the 90’s and I was and am an advocate for IPv6 deployment, I do not feel we have a choice! That being said we have created a BIG MESS thus hindering any easy or even reasonable deployment for IPv6. I am sorry to say but all one has to do is look at the standards and there are a bunch of them to fully understand the impossible complexity to a successful and safe deployment. BUT - I still feel we have created a giant that is NOT movable and if we do not rethink it we may never see it deployed!
While teaching an OptiView XG course not long ago, an attendee asked a question about the "small" capture buffer available on the product. He wanted to know when it would go from 4GB to 8GB, 16, 32, or beyond.
The reasoning behind the question was that in a high-throughput environment like a data center, 4GB can fill up pretty quickly. Which, is true. If the XG is connected to a 1Gbps link that is 50% full, a 4GB buffer with no filtering will get just over a minute's worth of capture time.
Have you ever opened a 4GB trace file in a packet analyzer? Wireshark, ClearSight or otherwise?
Network trace analysis is a great way to investigate a slow response time problem. A technique that I've found useful is to breakdown a request-response transaction into a number of component parts. Using this concept it's possible to first find a slow transaction, and then study the individual parts to determine if we have a client, network or server issue.
In this video we cover the components of the response time and introduce some terms I'll use in future videos. I also demonstrate the concepts by analyzing a Wireshark trace to reveal the response times for individual database transactions.
When Denny and Tim invited me to blog on LMT my first thought was how do I get started? I've got plenty of ideas about subjects but how do I set the scene? Then I realized that the common theme for me and my colleagues at Advance7 is the Recurring Gray Problem. You may not recognize the term, but I guarantee that you've seen the problem.
In this context the word 'Problem' means poor performance, errors or incorrect output - no surprises there. Recurring - well obviously it means it keeps happening. Gray just means that we don't know which technology is causing the problem, and so it's impossible to allocate it to the correct support team.
So the problem just bounces from one team to another as each "proves" that their technology is not to blame. Of course, it must be the network, right?
Try this exercise when you get a few minutes. Grab a 100 piece puzzle, put on a blindfold, dump out the pieces on a table, and put the puzzle together.
Possible? Well, if we force the pieces to fit together we may technically be able to connect all the pieces, but once we lift the blindfold things may look a little messy.
This illustrates the situation that IT engineers of today may find themselves in. Network and application problems are increasing in their scope and complexity, and solving them requires complete client to back-end database visibility. Why? To answer that, let’s take a look at the life of a client request from client keystroke to server response to consider how many devices along the way are required to support it. Then we can determine if there are gaps in visibility in our own IT environment.
With such a large selection of enterprise network monitoring solutions to choose from, deciding on the correct choice for your organization’s needs can be daunting and time consuming. Recently, Russ Rothstein and colleagues founded IT Central Station to provide network and other IT professionals with unbiased real user reviews to help them make the best decisions for their organization, without vendor bias or spin.
They have been described as Yelp or TripAdvisor for IT enterprise solutions. Unlike other consumer review sites, all reviewers on IT Central Station are validated first with their LinkedIn profiles, so you can be sure they are 100% authentic.
For a sample for their user comments, please click here.