Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1455
Views
0
Helpful
6
Replies

no Rx/Tx unicast packets on show interface

Go to solution
BorislavPenchev0962
Level 3
Level 3

‎08-11-2022 03:52 AM - edited ‎08-14-2022 09:19 PM

Hi,

we have an issue with monitor port (Mirror of trunked Switchport) where no Rx/Tx packets coming, while on source port we see packets;

output source OK:

 

 

# sh int eth125/1/15 (monitor source)
Ethernet125/1/15 is up

  Hardware: 100/1000/10000 Ethernet, 
 
  MTU 1500 bytes,  BW 10000000 Kbit, DLY 10 usec
  reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, medium is broadcast
  Port mode is trunk
  full-duplex, auto-speed
  Beacon is turned off
  Input flow-control is off, output flow-control is on
  Switchport monitor is off
  EtherType is 0x8100
  Last link flapped 3week(s) 3day(s)
  Last clearing of "show interface" counters never
  27 interface resets
  30 seconds input rate 11641512 bits/sec, 2743 packets/sec
  30 seconds output rate 27105688 bits/sec, 3055 packets/sec
  Load-Interval #2: 5 minute (300 seconds)
    input rate 17.78 Mbps, 3.57 Kpps; output rate 29.11 Mbps, 3.45 Kpps
  RX
    58074751993 unicast packets  58052 multicast packets  24593 broadcast packets
    58074834638 input packets  41577019301419 bytes
    21339482833 jumbo packets  0 storm suppression bytes
    0 runts  0 giants  0 CRC  0 no buffer
    0 input error  0 short frame  0 overrun   0 underrun  0 ignored
    0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
    0 input with dribble  0 input discard
    0 Rx pause
  TX
    45820438657 unicast packets  192364680 multicast packets  220950033 broadcast packets
    46233753370 output packets  16741135795528 bytes
    3604995411 jumbo packets
    0 output error  0 collision  0 deferred  0 late collision
    0 lost carrier  0 no carrier  0 babble 0 output discard
0 Tx pause

 

 

output destination:

 

 

 sh int eth125/1/23 (monitor destination)
eth125/1/23 is up

  Hardware: 100/1000/10000 Ethernet, 
  MTU 1500 bytes,  BW 1000000 Kbit, DLY 10 usec
  reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, medium is broadcast
  Port mode is access
  full-duplex, auto-speed
  Beacon is turned off
  Input flow-control is off, output flow-control is on
  Switchport monitor is on
  EtherType is 0x8100
  Last link flapped 7d
  Last clearing of "show interface" counters 12:24:14
  0 interface resets
  30 seconds input rate 0 bits/sec, 0 packets/sec
  30 seconds output rate 160 bits/sec, 0 packets/sec
  Load-Interval #2: 5 minute (300 seconds)
    input rate 0 bps, 0 pps; output rate 144 bps, 0 pps
  RX
    0 unicast packets  0 multicast packets  0 broadcast packets
    0 input packets  0 bytes
    0 jumbo packets  0 storm suppression bytes
    0 runts  0 giants  0 CRC  0 no buffer
    0 input error  0 short frame  0 overrun   0 underrun  0 ignored
    0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
    0 input with dribble  0 input discard
    0 Rx pause
  TX
    0 unicast packets  2009 multicast packets  272 broadcast packets
    2281 output packets  812051 bytes
    0 jumbo packets
    0 output error  0 collision  0 deferred  0 late collision
    0 lost carrier  0 no carrier  0 babble 0 output discard
0 Tx pause

 

 

we have the latest NXOS version 7.3(8)N1(1)

monitor session

 

 

sh monitor session 6
   session 6
---------------
description       : rebgh
type              : local
state             : up
acl-name          : acl-name not specified
source intf       :
    rx            : Eth125/1/15
    tx            : Eth125/1/15
both          : Eth125/1/15
source VLANs      :
    rx            :
source VSANs      :
    rx            :
destination ports : Eth125/1/23

Legend: f = forwarding enabled, l = learning enabled

 

 

may you advise if this is a bug or we did some missconfiguration ?

Best Regards

Borislav

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
BorislavPenchev0962
Level 3
Level 3

‎10-18-2022 10:22 PM

hello,

just to clarify to what conclusion we got on this topic -

 

[+] With the current running configuration for the span sessions, we are hitting multiple limitations as per the following link:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/system_management/521_n1_x/b_5k_System_Mgmt_Config_521N1x/b_5k_System_Mgmt_Config_521N11_chapter_010000.pdf

 

[+] If we are using some fex ports as source interface we should not use the other in another span session, so we removed the other 2 session and it’s working now but again we should not use the fex interface as a destination port

 

[+] The available solution here is to use a physical switch interface as a destination port and as per our discussion, you can connect 10 gig only with your capturing tool.

[+] All interfaces on the nexus 5k are 40 gigs, and we can convert it using the breakout command but you need to change all ports within the same ASIC

 

switch(config)# interface breakout slot x port port-range map 10g-4x

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus6000/sw/interfaces/6x/b_6k_Interfaces_Config_Guide_Release_6x/b_6k_Interfaces_Config_Guide_Release_602N12_chapter_0101.html

View solution in original post

0 Helpful
6 Replies 6

Go to solution
BorislavPenchev0962
Level 3
Level 3
In response to balaji.bandi

‎08-11-2022 04:07 AM

Hi, this is Nexus 5624Q 

 

0 Helpful

Go to solution
BorislavPenchev0962
Level 3
Level 3
In response to balaji.bandi

‎08-11-2022 05:25 AM - edited ‎08-14-2022 09:38 PM

here the port output:

 

# sh run int ethernet 125/1/23

!Command: show running-config interface Ethernet125/1/23
version 7.3(8)N1(1)

interface Ethernet125/1/23
  switchport monitor

interface Ethernet125/1/15
  switchport mode trunk
  switchport trunk native vlan 1234
  switchport trunk allowed vlan 1, 33, 55, 77, 1000-1115
  duplex full

 

SPAN Monitor was deleted and newly configured with different destination Ports - same result

have setup the source monitor port on rx (ingress) only, but result is the same

0 Helpful

Go to solution
BorislavPenchev0962
Level 3
Level 3
In response to balaji.bandi

‎08-12-2022 12:29 AM - edited ‎08-14-2022 09:52 PM

SPAN Config:

Session State Reason Description
------- ----------- ---------------------- --------------------------------
1 up The session is up
2 up The session is up
3 up The session is up

session 1
---------------
description :
type : local
state : up
acl-name : acl-name not specified
source intf :
rx : Eth125/1/23
tx : Eth125/1/23
both : Eth125/1/23
source VLANs :
rx :
source VSANs :
rx :
destination ports : Eth125/1/15

Legend: f = forwarding enabled, l = learning enabled

sh int Eth125/1/23 | i uni
11229792 unicast packets 132 multicast packets 0 broadcast packets
9213861 unicast packets 21941 multicast packets 7972 broadcast packets

sh int Eth125/1/15 | i uni
0 unicast packets 0 multicast packets 0 broadcast packets
1 unicast packets 31048 multicast packets 77330 broadcast packets

Monitor Konfig:
monitor session 1
source interface Ethernet125/1/23 both
destination interface Ethernet125/1/15
no shut

Int Konfig und Status:
interface Ethernet125/1/23
switchport mode trunk
switchport trunk native vlan 1234
switchport trunk allowed vlan 1, 33, 55, 77, 1000-1115

Eth125/1/23 - connected trunk full a-10G 1G/10G

interface Ethernet125/1/15
switchport monitor

Eth125/1/15 - connected 1 full a-1000 1G/10G

0 Helpful

Go to solution
BorislavPenchev0962
Level 3
Level 3

‎10-18-2022 10:22 PM

hello,

just to clarify to what conclusion we got on this topic -

 

[+] With the current running configuration for the span sessions, we are hitting multiple limitations as per the following link:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/system_management/521_n1_x/b_5k_System_Mgmt_Config_521N1x/b_5k_System_Mgmt_Config_521N11_chapter_010000.pdf

 

[+] If we are using some fex ports as source interface we should not use the other in another span session, so we removed the other 2 session and it’s working now but again we should not use the fex interface as a destination port

 

[+] The available solution here is to use a physical switch interface as a destination port and as per our discussion, you can connect 10 gig only with your capturing tool.

[+] All interfaces on the nexus 5k are 40 gigs, and we can convert it using the breakout command but you need to change all ports within the same ASIC

 

switch(config)# interface breakout slot x port port-range map 10g-4x

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus6000/sw/interfaces/6x/b_6k_Interfaces_Config_Guide_Release_6x/b_6k_Interfaces_Config_Guide_Release_602N12_chapter_0101.html

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card