cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1943
Views
0
Helpful
4
Replies

Monitor session Physical and sub-interface

poppy_dinh
Level 1
Level 1

Hi all,

I make 1 monitor session on ASR9K, with source int te0/2/0/0, and 12 sub-interface of int te0/2/0/0, dest int Gi 0/6/0/0

But, monitor session is working with sub-interface, show monitor session counter dont have rx, tx in physical int te0/2/0/0.

 

RP/0/RSP0/CPU0:PE_ASR9-#sh monitor-session test counters

Monitor-session test
TenGigE0/2/0/0
Rx replicated: 0 packets, 0 octets
Tx replicated: 0 packets, 0 octets
Non-replicated: 0 packets, 0 octets
TenGigE0/2/0/0.10
Rx replicated: 428171577 packets, 77388484016 octets
Tx replicated: 113597100 packets, 18275176456 octets
Non-replicated: 0 packets, 0 octets
TenGigE0/2/0/0.11
Rx replicated: 72867584 packets, 15796983181 octets
Tx replicated: 10062963 packets, 8657119779 octets
Non-replicated: 0 packets, 0 octets
TenGigE0/2/0/0.12
Rx replicated: 175146994 packets, 30982086306 octets
Tx replicated: 209965557 packets, 30698646702 octets
Non-replicated: 0 packets, 0 octets
TenGigE0/2/0/0.13
Rx replicated: 53313455 packets, 6379570832 octets
Tx replicated: 54060042 packets, 6280426700 octets
Non-replicated: 0 packets, 0 octets
TenGigE0/2/0/0.14
Rx replicated: 2905720 packets, 293298344 octets
Tx replicated: 2906872 packets, 234408704 octets
Non-replicated: 0 packets, 0 octets

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Pls help me find out what happened with this issue

1 Accepted Solution

Accepted Solutions

poppy_dinh
Level 1
Level 1

I find the answer to this issue.

The span port will capture traffic on the port, but the span has just captured the port to have real traffic. 

In this case, The physical interface don't have real traffic, the traffic in sub-bundle

View solution in original post

4 Replies 4

balaji.bandi
Hall of Fame
Hall of Fame

But we can see that the associated sub-interface has RX and TX.

 

show interface x/x show you real consolidated. information.

show monitor-session status

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Hi BB,

Yes, the sub-inter has RX, Tx. I don't know why the physical interface doesn't have Rx, TX.

This is output of the command:

RP/0/RSP0/CPU0:PE_ASR9#sh monitor-session test status
Mon Dec 6 10:20:49.754 GMT
Monitor-session test
Destination interface GigabitEthernet0/6/0/0
================================================================================
Source Interface Dir Status
--------------------- ---- ----------------------------------------------------
Te0/2/0/0 Both Operational
Te0/2/0/0.10 Both Operational
Te0/2/0/0.11 Both Operational
Te0/2/0/0.12 Both Operational
Te0/2/0/0.13 Both Operational
Te0/2/0/0.14 Both Operational


RP/0/RSP0/CPU0:PE_ASR9#sh int TenGigE0/2/0/0

TenGigE0/2/0/0 is up, line protocol is up
Interface state transitions: 1
Hardware is TenGigE, address is xxxxxx
Layer 1 Transport Mode is LAN
Description: XXXX
Internet address is Unknown
MTU 1514 bytes, BW 10000000 Kbit (Max: 10000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 10000Mb/s, SR, link type is force-up
output flow control is off, input flow control is off
Carrier delay (up) is 10 msec
loopback not set,
Last link flapped 48w4d
Last input 00:00:00, output 00:00:00
Last clearing of "show interface" counters never
5 minute input rate 13521000 bits/sec, 7458 packets/sec
5 minute output rate 8505000 bits/sec, 6070 packets/sec
185319494575 packets input, 52572366292255 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 115631 broadcast packets, 34346127 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
134266740094 packets output, 21413093856583 bytes, 0 total output drops
Output 2893 broadcast packets, 36181738 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions

 

Hello,

 

I wonder if that is not the default behavior. I seem to recall that the packets for the physical interfaces just show up on the destination interface.

 

I could be wrong. Will do some testing...

poppy_dinh
Level 1
Level 1

I find the answer to this issue.

The span port will capture traffic on the port, but the span has just captured the port to have real traffic. 

In this case, The physical interface don't have real traffic, the traffic in sub-bundle