Deployment Guide

Port Monitoring
Port monitoring is supported on both physical and logical interfaces, such as VLAN and port-channel interfaces. The source port
(MD) with monitored traffic and the destination ports (MG) to which an analyzer can be attached must be on the same switch.
You can configure up to 128 source ports in a monitoring session. Only one destination port is supported in a monitoring session.
The platform supports multiple source-destination statements in a single monitor session.
The maximum number of source ports that can be supported in a session is 128.
The maximum number of destination ports that can be supported depends on the port mirroring directions as follows:
● 4 per port pipe, if the four destination ports mirror in one direction, either rx or tx.
●
2 per port pipe, if the two destination ports mirror in bidirection.
● 3 per port pipe, if one of the destination port mirrors bidirection and the other two ports mirror in one direction (either rx or
tx).
Example of Changing the Destination Port in a Monitoring Session
In the following examples, ports 1/13, 1/14, 1/15, and 1/16 all belong to the same port-pipe. They are pointing to four different
destinations (1/1, 1/2, 1/3, and 1/37). Now it is not possible for another source port from the same port-pipe (for example, 1/17)
to point to another new destination (for example, 1/4). If you attempt to configure another destination (to create 5 MG port),
this message displays: % Error will be thrown in case of RPM and ERPM features.
In the following examples, ports Te 1/1/1, Te 1/1/2, Te 1/1/3, and Te 1/1/4 all belong to the same pipeline. They are pointing
to four different destinations: Te 1/4/1, Te 1/4/2, Te 1/4/3, and Te 1/4/4. If you attempt to configure another destination (to
create 5 MG port), the system displays an error message.
DellEMC(conf-mon-sess-5)#do show moni session
SessID Source Destination Dir Mode Source IP Dest IP DSCP TTL Drop Rate
Gre-Protocol FcMonitor
------ ------ ----------- --- ---- --------- -------- ---- ---- ---- -----
------------ ---------
100 Te 1/1/1 Te 1/4/1 rx Port N/A N/A N/A N/A No N/A N/A
yes
200 Te 1/1/2 Te 1/4/2 tx Port N/A N/A N/A N/A No N/A N/A
yes
300 Te 1/1/3 Te 1/4/3 rx Port N/A N/A N/A N/A No N/A N/A
yes
400 Te 1/1/4 Te 1/4/4 rx Port N/A N/A N/A N/A No N/A N/A
yes
DellEMC(conf-mon-sess-5)#
Example of Configuring Another Monitoring Session with a Previously Used Destination Port
DellEMC(conf)#mon ses 300
DellEMC(conf-mon-sess-300)#source TenGig 1/17/1 destination TenGig 1/4/1 direction tx
% Error: Exceeding max MG ports for this MD port pipe.
Example of Viewing a Monitoring Session
DellEMC#show running monitor session
!
monitor session 100
source TenGigabitEthernet 1/1/1 destination TenGigabitEthernet 1/4/1 direction rx
!
monitor session 200
source TenGigabitEthernet 1/1/2 destination TenGigabitEthernet 1/4/2 direction tx
!
monitor session 300
source TenGigabitEthernet 1/1/3 destination TenGigabitEthernet 1/4/3 direction rx
!
monitor session 400
source TenGigabitEthernet 1/1/4 destination TenGigabitEthernet 1/4/4 direction rx
!
Dell EMC Networking OS Behavior: All monitored frames are tagged if the configured monitoring direction is egress (TX),
regardless of whether the monitored port (MD) is a Layer 2 or Layer 3 port. If the MD port is a Layer 2 port, the frames are
tagged with the VLAN ID of the VLAN to which the MD belongs. If the MD port is a Layer 3 port, the frames are tagged with
VLAN ID 4095. If the MD port is in a Layer 3 VLAN, the frames are tagged with the respective Layer 3 VLAN ID. For example,
in the configuration source TenGig 1/6/1 destination TeGig 1/6/2 direction tx, if the MD port TenGig 1/6/1 is an untagged
member of any VLAN, all monitored frames that the MG port TeGig 1/6/2 receives are tagged with the VLAN ID of the MD port.
Port Monitoring
659