cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1554
Views
1
Helpful
6
Replies

Error when using frame size increase

yufenwan
Level 1
Level 1

Hi experts,

I'm using TRex STL API.

There's only one stream added on my trex port.

Here is the json data I get by the get_stream API in trex_stl_port.py before starting the traffic.

{'mode': {'type': 'continuous', 'rate': {'value': 100, 'type': 'pps'}}, 'enabled': True, 'isg': 0, 'vm': {'instructions': [{'init_value': 64, 'step': 1, 'size': 2, 'max_value': 256, 'name': 'pkt_len', 'op': 'inc', 'type': 'flow_var', 'min_value': 64}, {'name': 'pkt_len', 'type': 'trim_pkt_size'}, {'is_big_endian': True, 'type': 'write_flow_var', 'add_value': -14, 'name': 'pkt_len', 'pkt_offset': 16}]}, 'name': 'test_stream', 'action_count': 0, 'flags': 3, 'self_start': True, 'flow_stats': {'enabled': False}, 'packet': {'meta': '', 'binary': '9E4FOimSoDafjQuOCABFAAAoAAEAAEAGIaIhCwsMIgsLDAQBBAEAAff6AAAAAFAABAAAAAAA'}}

The following error raised when I'm tring to start the traffic.

Exception stack (most recent call last):

#2     Client.py:512                    - 'synchronized=synchronized,'

#1     trex_stl_client.py:1236          - 'ret = f(*args, **kwargs)'

#0     trex_stl_client.py:2719          - 'raise STLError(rc)'

Summary error message:

Port 2 : *** *** error: instruction id '0' min packet size 60 is bigger or eq to max packet size 60

I'm really confused about this error.

Could you help look into this issue?

6 Replies 6

hhaim@cisco.com
Cisco Employee
Cisco Employee

Packet size should be bigger than trim instruction var size.

Packet with len 60 can’t be trim to be 256

Thanks.

Hanoh

Hi Hanoch,

Should I modify something?

I read the code in trex_stl_hltapi.py and did the same way according to that.

Thanks,

Yufeng.

Please send to our mailer the full script

Hanoh

Sent from my iPhone

Hi Hanoch,

What's the mailer name?

Thanks,

Yufeng.

https://trex-tgn.cisco.com/trex/doc/index.html

See the forum link

Hanoh

Sent from my iPhone

Hi Hanoch,

Thanks for your help.

The above issue has been solved and is caused by payload data.