Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Monitor session can only capture one direction traffic

my config

On the dst port i can only see one direction (tx) traffic to the source port. Why would that be?


M1# show running-config interface ethernet 1/19

!Command: show running-config interface Ethernet1/19
!Time: Fri Sep 12 13:57:45 2014

version 6.0(2)N1(2)

interface Ethernet1/19
  description ""
  switchport monitor
  speed 1000


M1# show running-config monitor all

!Command: show running-config monitor all
!Time: Fri Sep 12 13:57:04 2014

version 6.0(2)N1(2)
monitor session 10 type local
  no description
  source interface Ethernet103/1/13 both
  destination interface Ethernet1/19


M1# show monitor
internal   session
M1# show monitor session 10
   session 10
type              : local
state             : up
source intf       :
    rx            : Eth103/1/13
    tx            : Eth103/1/13
    both          : Eth103/1/13
source VLANs      :
    rx            :
source VSANs      :
    rx            :
destination ports : Eth1/19

Legend: f = forwarding enabled, l = learning enabled

  • LAN Switching and Routing
Cisco Employee

Hi, not able to understand



not able to understand exact query, but what i understand you are monitoring rx/tx traffic of port Eth103/1/13 and copy of that traffic sending on port Eth1/19 over which you must have connected a laptop with wireshark installed.


In such case on port Eth1/19, we will se Tx traffic only. Please correct me if i did not understand your query properly.


--Pls rate helpful posts--



New Member

Yes that is correct Akash. My

Yes that is correct Akash.


My expectation was as I am capturing tx and rx on port  Eth103/1/13. 

I should see on port 1/19 which is monitor port.

If that wouldn't not be the case what should I do to capture both tx and rx packets.