Skip to main content
raphaejaoliveira
raphaejaoliveira
Visitor III
December 7, 2020
Question

Diag Traffictest

  • December 7, 2020
  • 2 replies
  • 20448 views

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"??

    2 replies

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    December 7, 2020

    My understanding based on this KB is "diag traffictest" runs iperf test between an ingress port to an egress port, inside of the FGT. It doesn't test against a circuit.

    https://kb.fortinet.com/kb/documentLink.do?externalID=FD45599

    What you need to have to test a circuit terminated at a FGT is a pair of iperf servers, one located on the other end of the circuit and one behind the FGT, then test performance anything in-between, which is difficult to do if you can't place anything inside of MPLS provider's network behind the PE.

     

    By the way, I don't see the "-c" option under diag traffictest. Maybe you're talking about a different command?

    xxx-fg1(6.2.6) # diag traffictest ? show           Traffic settings show run            Start traffic. server-intf    Server interface. client-intf    Client interface. port           TCP or UDP port number (0 - 65535). proto          0 for TCP or 1 for UDP (default = 0).

    raphaejaoliveira
    raphaejaoliveiraAuthor
    Visitor III
    December 15, 2020

    Hi Toshi.

     

    Is possible you use Diag Traffictest between fortigate and a remote desk top with Iperf how server.

    I used he and I have success.

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    December 15, 2020

    I tested with the way Ken suggested, and with iper3 server-side (means not-client-side) running on a Fedora machine. I was remotely operating it but the remote access didn't use the test path (out of band).

    Still that path, just a cable, showed only a half of the interface speed, while the sever to another server showed close to full speed.

    If you set up the environment carefully, you should be able to do the same to see what kind of number you can get.

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    December 7, 2020

    I didn't read the KB entirely.

    #diag traffictest run -c 89.84.1.222  was described. So you're saying changing client-interface name doesn't work?

    [size="2"]#diag traffictest client-intf interface_name [/size]

     

     

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    December 7, 2020

    I see what you're seeing. When I tried it on a 60E, it says:

    Can not find interface:port1

     

    I need to wait what others have to say about it too. Or need to open a ticket with TAC.

    brycemd
    brycemd
    New Member
    December 7, 2020

    You have to set both a server and client interface or else it defaults to port1

    Terms & ConditionsAccessibility statement