Administrator Guide

Example of Configuring Another Monitoring Session with a Previously Used Destination Port
Dell(conf)#mon ses 300
Dell(conf-mon-sess-300)#source tengig 0/17 destination tengig 0/4 direction tx
%Unable to create MTP entry for MD tenG 0/17 MG tenG 0/4 in stack-unit 0 port-pipe 0.
Dell(conf-mon-sess-300)#
Dell(conf-mon-sess-300)#source tengig 0/17 destination tengig 0/1 direction tx
Dell(conf-mon-sess-300)#do show mon session
SessionID Source Destination Direction Mode Type
--------- ------ ----------- --------- ---- ----
0 Te 0/13 Te 0/1 rx interface Port-based
10 Te 0/14 Te 0/2 rx interface Port-based
20 Te 0/15 Te 0/3 rx interface Port-based
30 Te 0/16 Te 0/37 rx interface Port-based
300 Te 0/17 Te 0/1 tx interface Port-based
Dell Networking OS Behavior: The switch continues to mirror outgoing traffic even after an MD participating in spanning tree protocol
(STP) transitions from the forwarding to blocking.
Configuring Port Monitoring
Port monitoring (also referred as mirroring) monitors network traffic by forwarding a copy of incoming and outgoing packets from a
source port to a destination port on the same network router To configure port monitoring on the port extender, use the following
commands.
1. Display the running configuration of an interface.
EXEC Privilege mode
show running-config monitor session
2. Create a monitoring session using the command monitor session from CONFIGURATION mode, as shown in the following example.
MONITOR SESSION mode
monitor session [session-ID] source interface | range destination interface direction {rx |
tx | both}
3. Specify the source and destination port and direction of traffic, as shown in the following example.
MONITOR SESSION mode
monitor session 1 source TenGigabitEthernet 0/2 destination TenGigabitEthernet 0/4 direction
rx
Parameters
monitor session id type rpm — The id needs to be unique and not already defined in the box specifying type as rpm defines an
RPM session. type is an optional keyword, required only for rpm and erpm.
Specifies one of the following types:
• rpm — Creates a remote port monitoring (rpm) session.
• erpm — Creates an encapsulated remote port monitoring (erpm) session.
source interface interface | range — Specify the port or list of ports that needs to be monitored
Enter the one of the following keywords and slot/port information:
• For a 10–Gigabit Ethernet interface, enter the keyword TenGigabitEthernet, then the slot/port information.
• For a 40–Gigabit Ethernet interface, enter the keyword fortyGigE, then the slot/port information.
• For a port extender (PE) Gigabit Ethernet interface, enter the keyword peGigE then the pe-id/stack-unit /port-idinformation.
• For a port extender 10-Gigabit Ethernet interface, enter the keyword peTenGigE then the pe-id/stack-unit /port-id information.
• For a VLAN interface, enter the keyword VLAN then a vlan-id number. The range is from 1 to 4094.
NOTE: VLAN 4092 and VLAN 4093 are reserved VLANs. You cannot configure these VLANs.
• For a remote VLAN interface, enter the keyword Remote-VLAN then a vlan-id number. The range is from 1 to 4094.
NOTE: VLAN 4092 and VLAN 4093 are reserved VLANs. You cannot configure these VLANs.
• For a port channel interface, enter the keyword port-channel then the port-channel ID.
destination — Enter the keyword destination to specify the destination interface monitor ingress/egress or both ingress and
egress packets on the specified port Enter the keyword direction then one of the packet directional indicators.
• rx: to monitor receiving packets only.
706
Port Monitoring