
•
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.
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..
•
By default, ingress traffic on a destination port is dropped.
Restrictions
When you configure remote port mirroring, the following
restrictions
apply:
•
You can configure the same source port to be used in multiple source sessions.
•
You cannot configure a source port channel or source VLAN in a source session if the port channel or VLAN has a member port
that is configured as a destination port in a remote-port mirroring session.
•
A destination port for remote port mirroring cannot be used as a source port, including the session in which the port functions as
the destination port.
•
A destination port cannot be used in any spanning tree instance.
•
The reserved VLAN used to transport mirrored traffic must be a L2 VLAN. L3 VLANs are not supported.
•
On a source switch on which you configure source ports for remote port mirroring, you can add only one port to the dedicated
RPM VLAN which is used to transport mirrored traffic. You can configure multiple ports for the dedicated RPM VLAN on
intermediate and destination switches.
Displaying Remote-Port Mirroring Configurations
To display the current configuration of remote port mirroring for a specified session, enter the
show config
command in
MONITOR
SESSION
configuration mode.
Dell(conf-mon-sess-2)#show config
!
Port Monitoring
651
Summary of Contents for S4048-ON
Page 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Page 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Page 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Page 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Page 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Page 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Page 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Page 633: ...Policy based Routing PBR 633 ...
Page 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Page 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...