Revision as of 08:15, 26 August 2009 edit Welsh (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers 124,550 edits m clean up using AWB ← Previous edit		Revision as of 11:38, 26 August 2009 edit undo MrOllie (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 255,671 edits →Function: rv editor 'citing' his company website Next edit →
Line 16: In addition to directing monitoring traffic, data monitoring switches are capable of filtering traffic by Layer 2 to Layer 4 protocol criteria such as protocol and IP address, enabling only traffic of interest to be sent to specific tools. This capability can prevent tool oversubscription and facilitate drilling down on issues. Additional capabilities found in some data monitoring switches include load balancing across multiple tool ports, filtering on patterns in packet payloads, and converting media and data rates so tools can be used to monitor traffic from dissimilar links.<ref>[http://www.gigamon.com/GigamonU/GU06112017WAN.DAN.DAN.pdf Gigamon DAN]</ref> Beyond this, some data monitoring switches support stacking, which allows them to be architected as a traffic capture system configured as a fully distributed mesh.<ref>[http://www.vssmonitoring.com/customers/stacking.asp VSS vStack+]</ref> == Device Management ==

Data monitoring switch: Difference between revisions