VirtualWisdom Aids the Use of Protocol Analyzers
I was talking with one of our senior analysts the other day and he shared an observation about how VirtualWisdom makes protocol analyzers more useful, and I thought I’d share through this blog.
It’s pretty typical that when a user reports a problem, the SAN admin turns to switch logs and tracedumps for clues. The use of VirtualWisdom almost always eliminates this need because we get right to the root cause of physical layer problems without resorting to analyzing dump logs. Having said that, there are things VirtualWisdom can do to help in the rare case when you do use a protocol analyzer.
With VirtualWisdom, you can make sure that you’re placing the analyzer on the correct link, and that you’re actually capturing the incident. It can be hard to trigger a protocol analyzer for a specific issue. For instance, if there’s a slow exchange, there’s no way for an analyzer to trigger on that. It’s not monitoring the exchange, but VirtualWisdom does, and it can trigger the analyzer to capture the trace. Has this ever happened to you? Share your experiences and any questions in the section below.
