cisco-system-traffic-generator / trex-java-sdk Goto Github PK

Due to this issue, #636 there was a need to change the major API version to 5.0 (STL)

I will add the commit once it will be ready.

The high level changes from client side are:

1. Client should keep the ZMQ SUB/PUB but there is no need to read from it the information. The events shoudl be read using REQ/RES channel
2. Client must use a thread that pool the events using a new API get_async_events with session_id as an input. Each session will have a seperate queue for events. session_id is a unique number per session
3. Python client pool every 200msec the events queue
4. There is a new field in each event json called seq from type ```uint32``. Client could check that there is no missing events using this counter.

when i use the TrexClient method stopTraffic(int portIndex) i get JSON error respons from server(v2.29):
INFO : Call stop_traffic method.
INFO : JSON Req: {"method":"stop_traffic","id":"aggogxls","jsonrpc":"2.0","params":{"api_h":"Ptr5c4Rb","port_id":1}}
INFO : JSON Resp: [{"error":{"code":-32602,"message":"Bad paramters for method","specific_err":"field 'handler' is missing"},"id":"aggogxls","jsonrpc":"2.0"}]

Have i done something wrong or have something changed in recent version of trex or sdk?

Hi,
Current trex-java-sdk can supports stateless mode only.
But, we need to use java based ASTF APIs.

Q1. Do you have plan to support ASTF APIs in trex-java-sdk?
Q2. Do you have any additional information about ASTF RPC commands?
Current ASTF RPC command manual is not enough for us and referring the existing Python based ASTF API library code is time consuming job.

Thanks

Best Regards
Gwangmoon

Hi,
Im not sure if this should be here because it is not a issue more of a question how to use the packet capture in the sdk. Maybe i should ask this in the google trex group instead?
My problem is that i can't figure out or find any info how to use trex java sdk to get captured packets and do anything with them, this is how far i got:
CapturedPackets captureStream = trex.stopCapture(rxPort, captureId);
List capturedPackets = captureStream.getPkts();
System.out.print("First captured packet origin:" + capturedPackets.get(1).getOrigin());

But i want to see the complete packet and do checks on it like if it had expected vlan header.
How do i accomplish this?

I couldn't find this library deployed to any remote repository like maven central: http://central.maven.org/maven2/

Example: https://mvnrepository.com/search?q=trex-java-sdk
while other trex libraries do exist: https://mvnrepository.com/search?q=trex

What I would like to achieve is to use this library simply by including it in my maven pom file or my gradle file and avoid building an jar myself

(Am I just stupid who are not able to find it? )

Hi @hhaim
After major version update, Java API and TRex should have exactly same version.
It's really picky issue because we have too many Java client users with various versions of TRex server and Java APIs.
Currently, with this major update, the version of all Java client and TRex server should be synchronized at the same time.
It's hard to handle for large scaled distributed users.
We need temporary coexisting period before uplifting peers.
Maybe 2 options would be possible,

1. Java API to support both(4.x, 5.x) versions according to the peer TRex server version.
2. Allow option in TRex server to ignore mismatched version in TRex server side - of course, Java client should have no issue to connect any TRex server versions. If old Java client does not use async port, it'll have no issue to connect to new version of TRex server if TRex server do not reject old client versions.

Do you have any suggestion regarding this issue?

Hi,
Can you provide a simple example of how to use VM Instruction in Stream using SDK?
Thanks.