Fluke or similar network taps are really the suggested solution here. Either pay for a good one, or make your own, but either way you need something roughly the size of a tablet that can be an inline network tap and analisys device that you can send around easily. Any time you're relying on the questioned device, you could be getting bad data. Thankfully most interconnects are ethernet now, so this is much less the difficult task it used to be. One example of why you would need to is the packets hit the TX ring but then get dropped due to firmware bug: most devices would see them in the capture outbound, but an inline device directly in front would not, removing the ambiguity and finger pointing between you and the handoff. -Blake On Tue, Jun 17, 2014 at 7:43 PM, Alex Balashov <abalashov at evaristesys.com> wrote:
On 06/17/2014 04:16 PM, Carlos Alvarez wrote:
Our methodology for packet captures is to put an independent machine on a spanned port and capture on that. Then it doesn't matter what the devices are doing, you get a true network picture.
And also a more objective one, not mediated by the device's own potential failings in processing or parsing certain messages. It's best to really see what's on the wire.
-- Alex Balashov - Principal Evariste Systems LLC Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops