Packet drops.

[Alexander Kovalev]

Hi guys, thanks for the T-Rex :)

I have few nexus switches on the test, and I decided to test them with trex.
I read manual https://trex-tgn.cisco.com/trex/doc/trex_manual.html
Installed trex on the HW server with two 10G ports NIC - "Intel Corporation 82599ES 10-Gigabit SFI/SFP+"
And successfully run loopback test (./t-rex-64 -f cap2/dns.yaml --lm 1 --lo -l 1000 -d 100), connecting two 10G ports with DAC.
Then I tried to connect ports via Nexus C9396PX.

Here is my network interfaces:
# ./dpdk_nic_bind.py -s

Network devices using DPDK-compatible driver
============================================
0000:03:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,uio_pci_generic
0000:03:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe,uio_pci_generic

Here is my trex_cfg.yaml
# cat /etc/trex_cfg.yaml
- port_limit : 2 # this option can limit the number of port of the platform
version : 2
interfaces : ["03:00.0","03:00.1"] #the interfaces using ./dpdk_setup_ports.py -s
port_info : # set eh mac addr
- dest_mac : [0x00,0x00,0x02,0x00,0x00,0x00] # router mac addr should be taken from router
src_mac : [0x00,0x00,0x01,0x00,0x00,0x00] # source mac-addr - taken from ifconfig
- dest_mac : [0x00,0x00,0x01,0x00,0x00,0x00] # router mac addr taken from router
src_mac : [0x00,0x00,0x02,0x00,0x00,0x00] #source mac-addr taken from ifconfig

Here is Nexus config:
test-nx1# sh run interface ethernet 1/15-16

!Command: show running-config interface Ethernet1/15-16
!Time: Wed Jun 8 13:27:10 2016

version 7.0(3)I4(1)

interface Ethernet1/15
switchport access vlan 25

interface Ethernet1/16
switchport access vlan 25

Also I configured static mac on the Nexus:
test-nx1# sh run | i mac
mac address-table static 0000.0100.0000 vlan 25 interface Ethernet1/15
mac address-table static 0000.0200.0000 vlan 25 interface Ethernet1/16

Strange thing is that after around 30 seconds of test, RX counters starting to grow.

Here is summary stats:
summary stats
--------------
Total-pkt-drop : 31064 pkts
Total-tx-bytes : 6600792 bytes
Total-tx-sw-bytes : 6600792 bytes
Total-rx-bytes : 4550568 byte

Total-tx-pkt : 100012 pkts
Total-rx-pkt : 68948 pkts
Total-sw-tx-pkt : 100012 pkts
Total-sw-err : 0 pkts
maximum-latency : 34 usec
average-latency : 5 usec
latency-any-error : ERROR

[hanoh haim]

Hi Alexander, 

I suspect that this issue is related to the Spanning Tree feature in the Switch. try to disable it and send us how you did it. 

Every Switch has a different way to do that.

It is not clear from your email if you want to test the switch (Stateless) or you want to test some Stateful service ( using TRex Stateful feature)

if you need Stateless, you should TRex differently and this SPT issue won’t be there because the link will always be up

 

If you need Stateful, another thing that could help is the CLI option (-k)

Try to add -k 10

 

Hanoh

--
You received this message because you are subscribed to the Google Groups "TRex Traffic Generator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trex-tgn+u...@googlegroups.com.
To post to this group, send email to trex...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trex-tgn/7641dfa7-03a5-4948-9a1e-8a17ff77e680%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Hanoh

Sent from my iPhone

[Alexander Kovalev]

Hi Hanoh,

You are absolutly right. The problem was in STP. After I configure:

spanning-tree port type edge

on the Nexus ports I started seeing RX packets from the beginning of the test.

Thanks for your help!

I run trex  statefully