• Mirrored traffic is transported across the network using 802.1Q-in-802.1Q tunneling. The source
address, destination address and original VLAN ID of the mirrored packet are preserved with the tagged
VLAN header. Untagged source packets are tagged with the reserve VLAN ID.
• You cannot configure a private VLAN or a GVRP VLAN as the reserved RPM VLAN.
• The RPM VLAN can’t be a Private VLAN.
• The RPM VLAN can be used as GVRP VLAN.
• The L3 interface configuration should be blocked for RPM VLAN.
• The member port of the reserved VLAN should have MTU and IPMTU value as MAX+4 (to hold the VLAN
tag parameter).
• To associate with source session, the reserved VLAN can have at max of only 4 member ports.
• To associate with destination session, the reserved VLAN can have multiple member ports.
• Reserved Vlan cannot have untagged ports
In the reserved
L2 VLAN
used for remote port mirroring:
• MAC address learning in the reserved VLAN is automatically disabled.
• The reserved VLAN for remote port mirroring can be automatically configured in intermediate switches
by using GVRP.
• There is no restriction on the VLAN IDs used for the reserved remote-mirroring VLAN. Valid VLAN IDs
are from 2 to 4094. The default VLAN ID is not supported.
• In mirrored traffic, packets that have the same destination MAC address as an intermediate or
destination switch in the path used by the reserved VLAN to transport the mirrored traffic are dropped
by the switch that receives the traffic if the switch has a L3 VLAN configured.
In a
source session
used for remote port mirroring:
• You can configure any port as a source port in a remote-port monitoring session with a maximum of
three source ports per port pipe.
• Maximum number of source sessions supported on a switch: 4
• Maximum number of source ports supported in a source session: 128
• You can configure physical ports and port-channels as sources in remote port mirroring and use them
in the same source session. You can use both Layer 2 (configured with the switchport command) and
Layer 3 ports as source ports. You can optionally configure one or more source VLANs to specify the
VLAN traffic to be mirrored on source ports.
• You can use the default VLAN and native VLANs as a source VLAN.
• You cannot configure the dedicated VLAN used to transport mirrored traffic as a source VLAN.
• Egressing remote-vlan packets are rate limited to a default value of 100 Mbps. To change the mirroring
rate, configure rate-limit within the RPM session.
In a
destination session
used for remote port mirroring:
• Maximum number of destination sessions supported on a switch: 64
• Maximum number ports supported in a destination session: 64.
• You can configure any port as a destination port.
• You can configure additional destination ports in an active session.
• You can tunnel the mirrored traffic from multiple remote-port source sessions to the same destination
port.
• By default, destination port sends the mirror traffic to the probe port by stripping off the rpm header. We
can also configure the destination port to send the mirror traffic with the rpm header intact in the
original mirror traffic..
Port Monitoring
799
Summary of Contents for S4048T
Page 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Page 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Page 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Page 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Page 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Page 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Page 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Page 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Page 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Page 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...