Dell PowerEdge VRTX - Manual (Page 274)

274
FILE LOCATION: C:\Users\gina\Desktop\Checkout_new\Dell Plasma\User
Guide\Plasma_UGSwitching_Ports.fm
D E L L C O N F ID E N T IA L – P R E L IM I N A RY 4 / 1 8 /1 3 - F O R P R O O F O N LY
It is possible to specify several source ports to be monitored by a single target
port. However, in this case, the traffic sent to the target port is placed in the
target port's queues on a first come, first served basis, and any excess traffic is
silently discarded. This may mean that the traffic actually seen by any device
attached to the target port is an arbitrarily selected subset of the actual traffic
going through the source ports.
Port mirroring is only relevant to physical ports. Therefore, if you want a LAG
to function as the source of a port mirroring session, the member ports must
be individually specified as sources.
Up to eight sources can be mirrored. This can be any combination of eight
individual ports.
Before configuring Port Mirroring, note the following:
• Monitored ports cannot operate faster than the monitoring port.
• All Rx/Tx packets should be monitored to the same port.
Destination Port Restrictions
The following restrictions apply to destination ports:
• Destination ports cannot be configured as source ports.
• Destination ports cannot be a member of a LAG.
• IP interfaces cannot be configured on the destination port.
• GVRP cannot be enabled on the destination port.
• The destination port cannot be a member of a VLAN.
• Only one destination port can be defined.
• All QoS/CoS rules that apply to the destination port, as an egress, such as
traffic shaping, are suspended for the duration of the mirroring session.
Any such settings, configured on the port during the mirroring session,
take effect only after the port is no longer a destination port for a
mirroring session.
• Ingress mirrored packets may arrive at the ingress port either with an
802.1q tag or without. When the packets are mirrored to a port analyzer,
they should be transmitted as they are received on the ingress port.
However, in the device, the packet is transmitted out of the port analyzer
as always tagged or always untagged (user configurable), regardless of the
input encapsulation.