Users 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 trac and the destination ports (MG) to which an analyzer can be attached must be on the same switch. You can congure 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).
In the following examples, ports Te 1/1/1/1, Te 1/1/1/2, Te 1/1/1/3, and Te 1/1/1/4 all belong to the same pipeline. They are pointing to four
dierent destinations: Te 1/1/4/1, Te 1/1/4/2, Te 1/1/4/3, and Te 1/1/4/4. If you attempt to congure another destination (to create 5 MG
port), the system displays an error message.
Example of Changing the Destination Port in a Monitoring Session
Dell(conf-mon-sess-5)#do show moni session
SessID Source Destination Dir Mode Source IP Dest IP DSCP TTL Drop Rate
------ ------ ----------- --- ---- --------- -------- ---- ---- --- -----
100 Te 1/1/1/1 Te 1/1/4/1 rx Port N/A N/A N/A N/A No N/A
200 Te 1/1/1/2 Te 1/1/4/2 tx Port N/A N/A N/A N/A No N/A
300 Te 1/1/1/3 Te 1/1/4/3 rx Port N/A N/A N/A N/A No N/A
400 Te 1/1/1/4 Te 1/1/4/4 rx Port N/A N/A N/A N/A No N/A
Dell(conf-mon-sess-5)#
Example of Conguring Another Monitoring Session with a Previously Used Destination Port
Dell(conf)#mon ses 300
Dell(conf-mon-sess-300)#source TenGig 1/1/7/1 destination TenGig 1/1/4/1 direction tx
% Error: Exceeding max MG ports for this MD port pipe.
Example of Viewing a Monitoring Session
Dell#show running monitor session
!
monitor session 100
source TenGigabitEthernet 1/1/1/1 destination TenGigabitEthernet 1/1/4/1 direction rx
!
monitor session 200
source TenGigabitEthernet 1/1/1/2 destination TenGigabitEthernet 1/1/4/2 direction tx
!
monitor session 300
source TenGigabitEthernet 1/1/1/3 destination TenGigabitEthernet 1/1/4/3 direction rx
!
monitor session 400
source TenGigabitEthernet 1/1/1/4 destination TenGigabitEthernet 1/1/4/4 direction rx
!
Dell Networking OS Behavior: All monitored frames are tagged if the congured 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 conguration source TenGig 11/6/1 destination
TeGig 11/6/2 direction tx, if the MD port TenGig 11/6/1 is an untagged member of any VLAN, all monitored frames that the MG port TeGig
11/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 dierence between the number of egress packets on the MD port and monitored
packets on the MG port.
Dell Networking OS Behavior: The platform continues to mirror outgoing trac even after an MD participating in spanning tree protocol
(STP) transitions from the forwarding to blocking.
Port Monitoring
611