Data monitoring switch: Difference between revisions

Revision as of 22:43, 15 October 2019

Revision as of 06:58, 23 May 2020

Line 1:

A '''data monitoring switch''' is a networking hardware appliance that provides a pool of monitoring tools with access to traffic from a large number of network links. It provides a combination of functionality that may include aggregating monitoring traffic from multiple links, regenerating traffic to multiple tools, pre-filtering traffic to offload tools, and directing traffic according to one-to-one and many-to-many port mappings<ref>{{Cite web|title=Arista EOS® Precision Data Analysis with DANZ|url=https://www.arista.com/en/solutions/precision-data-analysis-of-network-traffic|last=Sabeesh|date=2017-10-24|website=Arista Networks|language=en-gb|access-date=2020-05-23}}</ref>.

Data monitoring switches enable organizations to use their monitoring tools more efficiently, to centralize traffic monitoring functions, and to share tools and traffic access between groups. Some of these devices also provide functionality that helps justify tool purchases and simplify deployment and management of the device itself.

Line 52:

== Disadvantages ==

* Data monitoring switches take a simple concept, the passive network Tap, and make it an expensive, complex device that requires configuration and management.

* They are non-standard – different vendor devices operate and are managed differently.

* Entry-level pricing is expensive – if just a few links or tools need to be instrumented, price per port will be high.

* Advanced functionality on some products can be very cumbersome to activate and maintain over time.

* Command Line interfaces are often required for the vast majority of the functions, even on many boxes that also offer a GUI. While CLI offers a great deal of control over the operations of the box, only the utmost of advanced users will be able to configure filtering and connections using CLI without overlooking problems such as filter overlaps, replication and accuracy checks, and ongoing active system management.

== See also ==