Diag Traffictest

[raphaejaoliveira]

Hi.

I am need test the MPLS bandwidth. For this I am use diagnose traffic test, in fortigate 100E and 200e the test was wll, but when a tried from fortigate 60E or 40F the test fail.

When a execute "diag traffic -c x.x.x.x

[image][/image]

How can I use traffictest when the interface name is "internalX" and not "portX"??

[brycemd]

No, I am saying you specify both your ingress and egress ports.

diag traffictest client-intf

and 

diag traffictest server-intf

For example if you do a:

diag traffictest show

It will show you the settings it will use. You can see port1 listed if you don't specify something else

[Toshi_Esumi]

Ah, I never thought I could put the same interface on both client and server. Thanks Ken.

Toshi

[emnoc]

So you're saying to test with an external iperf server, the FGT model needs to have "port1" like upper models (3 digit models or higher)?

corrrect, ports are defined that you  need override or bind to another.

e.g FG100E

SANGAMONIL01 # diag traffictest show server-intf: port1 client-intf: port3 port: 162 proto: TCP

you have to set the ports and port-proto

diag traffictest  client-intf wan2

diag traffictest server-intf wan2

SANGAMONIL01 # diag traffictest port 5201 port: 5201

SANGAMONIL01 # diag traffictest run -c 45.33.39.39 Connecting to host 45.33.39.39, port 5201 [ 9] local xxxxxxx port 15275 connected to 45.33.39.39 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 9] 0.00-1.01 sec 1.05 MBytes 8.70 Mbits/sec 0 137 KBytes [ 9] 1.01-2.01 sec 3.28 MBytes 27.5 Mbits/sec 0 318 KBytes [ 9] 2.01-3.01 sec 5.91 MBytes 49.6 Mbits/sec 0 472 KBytes [ 9] 3.01-4.00 sec 7.78 MBytes 65.7 Mbits/sec 0 587 KBytes [ 9] 4.00-5.01 sec 9.10 MBytes 75.8 Mbits/sec 0 747 KBytes [ 9] 5.01-6.01 sec 12.1 MBytes 101 Mbits/sec 0 909 KBytes ^Ciperf3: interrupt - the server has terminated [ 9] 6.01-6.63 sec 8.60 MBytes 116 Mbits/sec 0 1.01 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 9] 0.00-6.63 sec 47.8 MBytes 60.4 Mbits/sec 0 sender [ 9] 0.00-6.63 sec 0.00 Bytes 0.00 bits/sec receiver iperf3: interrupt - the client has terminated

Again the iperf client is not reliable or documented very good

Ken Felix

[raphaejaoliveira]

Yes Toshi.

When I use the Diag Traffitest on Fortigate that use "internal" and not "port" the command retur with error.