• Source port (MD) can be a VLAN, where the VLAN traffic received on that port pipe where its members are present is monitored• Single MD can be monitored on max. of 4 MG ports.Port MonitoringPort monitoring is supported on both physical and logical interfaces, such as VLAN and port-channel interfaces. The source port (MD) withmonitored traffic and the destination ports (MG) to which an analyzer can be attached must be on the same switch. You can configure upto 128 source ports in a monitoring session. Only one destination port is supported in a monitoring session. The platform supports multiplesource-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 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 newdestination (for example, 1/4). If you attempt to configure another destination (to create 5 MG port), this message displays: % Errorwill be thrown in case of RPM and ERPM features.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 fourdifferent 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 configure another destination (to create 5 MGport), the system displays an error message.Example of Changing the Destination Port in a Monitoring SessionDell(conf-mon-sess-5)#do show moni sessionSessID Source Destination Dir Mode Source IP Dest IP DSCP TTL Drop Rate Gre-ProtocolFcMonitor------ ------ ----------- --- ---- --------- -------- ---- ---- ---- ----------------- ---------100 Te 1/1/1/1 Te 1/1/4/1 rx Port N/A N/A N/A N/A No N/A N/A yes200 Te 1/1/1/2 Te 1/1/4/2 tx Port N/A N/A N/A N/A No N/A N/A yes300 Te 1/1/1/3 Te 1/1/4/3 rx Port N/A N/A N/A N/A No N/A N/A yes400 Te 1/1/1/4 Te 1/1/4/4 rx Port N/A N/A N/A N/A No N/A N/A yesDell(conf-mon-sess-5)#Example of Configuring Another Monitoring Session with a Previously Used Destination PortDell(conf)#mon ses 300Dell(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 SessionDell#show running monitor session!monitor session 100source TenGigabitEthernet 1/1/1/1 destination TenGigabitEthernet 1/1/4/1 direction rx!monitor session 200source TenGigabitEthernet 1/1/1/2 destination TenGigabitEthernet 1/1/4/2 direction tx!monitor session 300source TenGigabitEthernet 1/1/1/3 destination TenGigabitEthernet 1/1/4/3 direction rx!monitor session 400source TenGigabitEthernet 1/1/1/4 destination TenGigabitEthernet 1/1/4/4 direction rx!Dell Networking OS Behavior: All monitored frames are tagged if the configured monitoring direction is egress (TX), regardless of whetherthe 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 theVLAN 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 3660 Port Monitoring
