Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Dell EMC Configuration Guide for the S4048T–ON System 9.14.2.4

PDF

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 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.

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
  ------  ------         -----------         ---  ----  ---------      --------   ----  ---   ----  ----    -----------  ---------
     1   Te 1/1            Te 2/1            both Port     N/A            N/A      0     0    No    N/A        N/A        yes
     2   Te 1/1            Te 2/2            both Port     N/A            N/A      0     0    No    N/A        N/A        yes
     3   Te 1/1            Te 2/3            both Port     N/A            N/A      0     0    No    N/A        N/A        yes
     4   Te 1/1            Te 2/4            both Port     N/A            N/A      0     0    No    N/A        N/A        yes
     5   Te 1/1            Te 2/5            both Port     N/A            N/A      0     0    No    N/A        N/A        yes
DellEMC(conf-mon-sess-5)#
DellEMC(conf)#mon ses 300
DellEMC(conf-mon-sess-300)#source tengig 1/17 destination tengig 1/4 direction tx
% Error: Exceeding max MG ports for this MD port pipe.
DellEMC(conf-mon-sess-300)#
DellEMC(conf-mon-sess-300)#source tengig 1/17 destination tengig 1/1 direction tx
DellEMC(conf-mon-sess-300)#do show mon session
SessID  Source      Destination    Dir  Mode       Source IP      Dest IP         DSCP  TTL   Drop  Rate    Gre-Protocol FcMonitor
------  ------      -----------    ---  ----       ---------      --------        ----  ---   ----  ----    -----------  ---------
   0    Te 1/13      Te 2/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   10   Te 1/14      Te 2/2        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   20   Te 1/15      Te 2/3        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   30   Te 1/16      Te 2/7        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   300  Te 1/17      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
  DellEMC#

Example of Configuring Another Monitoring Session with a Previously Used Destination Port

DellEMC(conf)#monitor session 300
DellEMC(conf-mon-sess-300)#source TenGig 1/17 destination TenGig 1/4 direction tx
% Error: Exceeding max MG ports for this MD port pipe.
DellEMC(conf-mon-sess-300)#
DellEMC(conf-mon-sess-300)#source TenGig 1/17 destination TenGig 1/1 direction tx
DellEMC(conf-mon-sess-300)#do show mon session
SessID  Source      Destination    Dir  Mode        Source IP     Dest IP         DSCP  TTL   Drop  Rate    Gre-Protocol FcMonitor
------  ------      -----------    ---  ----        ---------     --------        ----  ---   ----  ----    -----------  ---------
   0    Te 1/13      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   10   Te 1/14      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   20   Te 1/15      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   30   Te 1/16      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   300  Te 1/17      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
DellEMC#

Example of Viewing a Monitoring Session

In the example below, 0/25 and 0/26 belong to Port-pipe 1. This port-pipe has the same restriction of only four destination ports, new or used.

DellEMC(conf-mon-sess-300)#do show mon session
SessID  Source      Destination    Dir  Mode        Source IP     Dest IP         DSCP  TTL   Drop  Rate    Gre-Protocol FcMonitor
------  ------      -----------    ---  ----        ---------     --------        ----  ---   ----  ----    -----------  ---------
   0    Te 1/13      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   10   Te 1/14      Te 1/2        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   20   Te 1/15      Te 1/3        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   30   Te 1/16      Te 1/37       rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   100  Te 1/25      Te 1/38       rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   110  Te 1/26      Te 1/39       rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
   300  Te 1/17      Te 1/1        rx   interface   0.0.0.0       0.0.0.0          0     0    No    N/A        N/A        yes
DellEMC#

Given these parameters, the following illustration shows the possible port monitoring configurations.

Figure 1. Port Monitoring Configurations
Illustration of port monitoring configurations.

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 6/1 destination TeGig 6/2 direction tx, if the MD port TenGig 6/1 is an untagged member of any VLAN, all monitored frames that the MG port TeGig 6/2 receives are tagged with the VLAN ID of the MD port. Similarly, if BPDUs are transmitted, the MG port receives them tagged with the VLAN ID 4095. This behavior might result in a difference between the number of egress packets on the MD port and monitored packets on the MG port.

Dell EMC Networking OS Behavior: The platform continues to mirror outgoing traffic even after an MD participating in spanning tree protocol (STP) transitions from the forwarding to blocking.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\