The problem with this approach is that when a trace is taken, it must be from a port which gets copied on all frames. This is often called port monitoring. Although the frame is not destined for this port, the switch copies it to the specified port anyway. Higher end switches will have this feature. Most low end switches will not have this feature. If a trace needs to be taken on a switch which does not have this feature, the trace must be taken from one of the end points of the communication flow of interest. It is essential to consult environment specific LAN hardware references for details on switch configuration for tracing. Each manufacturer implements this feature in a proprietary manner, if at all.
The key objective is to ensure that the port on which tracing is to occur is configured to receive non-directly addressed frames.
The following examples are using Cisco equipment. In Cisco (TM) switches this feature is often called "SPAN" for Switched Port Analyzer. Sometimes Cisco calls this "monitoring".
From the "Main" menu, disable "half-duplex back pressure". Monitoring cannot be enabled unless this happens.
Logon into "enable" mode. From the command line the status of SPAN can be seen by using the command:
show span
To enable SPAN:
set span enable
To associate a specific VLAN with a specific SPAN port (forces all traffic for the VLAN to be copied to the SPAN port):
set span vlan# spanMODULE/spanPORT both
This switch allows a broader range of options including only copying on receive or transmit (we specified "both" here). Likewise, the ports to monitor can be just specific ports or can be an entire VLAN.