Port Mirroring Remote SPAN and Encapsulated Remote SPAN Sample Port Mirror Configurations Cisco Nexus v1000 Virtual Switch SPAN VMware ESXi Distributed vSwitch Port Mirroring Versus Promiscuous Mode select ports or select VLANs from a device to a monitoring port. all ports or all VLANs from the device to a monitoring port. Figure 4‑1 shows a monitoring configuration in which you detect traffic among all local servers. By monitoring an uplink port or VLAN, in addition to the local ports or VLANs, you can also detect traffic between all external hosts to the local hosts. The NetShark supports up to eight monitoring ports that enable you to duplicate this configuration multiple times using the same NetShark.Figure 4‑1. SPAN ConnectivityFor most monitoring and troubleshooting, you want to collect both sides of the conversation on a single monitor interface. This means that if you are capturing only a single port, you must mirror both directions—ingress and egress. If you are monitoring all ports or all communicating VLANs, you can capture ingress and egress only. Capturing ingress and egress on all ports or all VLANs is redundant, and the duplicate traffic is deduplicated on the NetShark. When you set up port mirroring, you must follow best practices according to your switch vendor. Because many architectures use nonblocking methods that drop overages if you overrun a port mirror (for example, by sending multiple gigabits per second worth of packets from a single gigabit port), depending on the switch you use, there can be an adverse effect on traffic or switch performance. For large applications across numerous switches, you can use third-party port monitor aggregators for flexible configurations. Vendors that supply port monitor aggregators include, but are not limited to, Anue Systems, NetOptics, Gigamon, cPacket Networks, and VSS Monitoring. Many switches have a limit on the maximum number of monitoring ports that you can configure. This limit is often two monitoring ports. If the limit is a problem in your environment, you can add a TAP to an existing monitoring port (essentially making a copy of the traffic already being monitored by another device), or you can use VLAN access control lists (VACLs) to configure what amounts to an additional SPAN port, provided that your equipment supports VACLs. For more information, see VACL Configuration Examples. RSPAN ERSPAN Figure 4‑2 shows a monitoring configuration in which you detect traffic to and from local servers on two different switches. The monitoring port is on an upstream switch. The NetShark and NetExpress have two or more monitoring ports that enable you to duplicate this configuration multiple times using the same NetShark or NetExpress.Figure 4‑2. RSPAN ConnectivityFigure 4‑3 shows a monitoring configuration that enables you to detect traffic to and from local servers on two different switches when the monitoring port is on an upstream switch over a routed network. The NetShark and NetExpress have two or more monitoring ports that enable you to duplicate this configuration multiple times using the same NetShark or NetExpress.Figure 4‑3. ERSPAN ConnectivityCisco Nexus v1000 Virtual Switch SPAN Cisco Catalyst 6500 SPAN Cisco Nexus 5000 SPAN Cisco Nexus 1000V ERSPAN to Cisco Catalyst 6500 For details about Cisco switch configuration examples, go to http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml.Figure 4‑4 shows an example Cisco Nexus v1000 virtual switch environment.Figure 4‑4. Cisco Nexus v1000 Virtual Switch SPANYou can configure a maximum of 64 SPAN sessions (Local SPAN plus ERSPAN) on the virtual supervisor module (VSM). A maximum of 32 source VLANs are allowed in a session. A maximum of 128 source interfaces are allowed in a session. You can configure a port in a maximum of four SPAN sessions. You cannot use the destination port in one SPAN session as the destination port for another SPAN session. You cannot configure a port as both a source and destination port. SPAN sessions are created in the shut state by default. When you create a SPAN session that already exists, any additional configuration is added to that session. To make sure the session is cleared of any previous configuration, you can delete the session first. Can be any physical or virtual Ethernet port or a port channel. Cannot be a source port. Is excluded from the source list and is not monitored if it belongs to a source VLAN of any SPAN session. Receives copies of transmitted and received traffic for all monitored source ports. If a destination port is oversubscribed, it can become congested. This congestion can affect traffic forwarding on one or more of the source ports. Must be on the same host (line card) as the source port. In Local SPAN, the source interface and destination interface are on the same device. For additional information about Cisco Nexus 5000 and NetShark, see http://supportkb.riverbed.com/support/index?page=content&id=S24538.
1.
1.Gigamon (Header/Trailer/Trailer X12-TS) Anue (requires Advanced Packet Processing module) cPacket VSS (Time stamp Only and Port ID & Time stamp) Arista Packet Broker (Series 7150)