How does an IT operator approach this problem? The 'Old Way' involves a tedious, error-prone, multi-step workflow to validate that the network is behaving as intended.ДЇirst, the leaf switches that have the problematic source and destination device attached must be identified. That leads to the question: 'How do you quickly and definitively identify the issue?'ДЄfter ruling out the obvious, and some not-so-obvious, signs of a network issue-things like drop counters massively incrementing on an interface, incorrectly applied QoS or security policies, or insidious microbursts -the IT operator is often left with nothing else to do than delve deep into the guts of the network fabric to ensure that all devices and paths between a source and a destination have proper network state, in both the control plane and the data plane. Any number of possible culprits across a variety of different devices could be wholly or partially contributing to an issue. Most IT operations folks are familiar with vaguely worded statements like 'My application performance is bad,' 'The network is slow,' and 'Sometimes it works but sometimes it doesn't.' Often, there's very little concrete information to work with when attempting to diagnose network performance problems.

Flowstate inc.