Hi, Guys,
A stupid question.
we are using Fortigate 600E with FortiOS V7.0.3.
A extranet infrastructure; we have a Fortigate connected private link (VLAN886-10.10.10.0/24) connecting to the 3rd party network, and their IPERF server/Linux system (192.168.1.0/24) is behind the link (test to the IPerf server; pingtest OK, routetable OK, from the Fortigate interface/10.10.10.1):
1. the Fortigate link inteface = 10.10.10.1
2. the IPERF server = 192.168.1.10
We got the following problem:
Forti600E_03 # diag traffictest server-intf Vlan886
server-intf: ha
Forti600E_03 # diag traffictest client-intf Vlan886
client-intf: mgmt
Forti600E_03 # diag traffictest port 5201
port: 5201
Forti600E_03 #
Forti600E_03 # diag traffictest run -c 192.168.1.10
Can not find ip (ha)
Command fail. Return code -1
Forti600E_03 #
Any suggestion/recommendation. thx ?
Benson
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hello Benson,
Please refer the below , hope this helps
https://fusecommunity.fortinet.com/blogs/yuri1/2020/10/30/fortigate-built-in-iperf-tool-network-diag...
Best regards,
Rathan Subbaiah
Fortinet EMEA TAC Engineer
NSE 4,7
To contact support by phone:
http://www.fortinet.com/support/contact_support.html
Helpful links:
https://community.fortinet.com
http://support.fortinet.com
http://docs.fortinet.com
Hi, Rathan_FTN.
Pingtest OK, telnet port OK, traceroute OK.
but "diag traffictest run -c" failed, and the returned code is same:
Can not find ip (ha)
Command fail. Return code -1
I think:
"Can not find ip (ha)" ..... means the Fortigate built-in iperf client can not find the Iperf3 server, due to the iperf3 server is not connected to Fortigate interfaces subnet ?
Thanks
Benson
Very late, but for anybody coming here with the same error.
I found you need to set the server interface to a configured interface (e.g. with an IP). Default this is the HA port, which may not be active in every setup.
It also echoes back the set interface when setting it. If it is something different then you asked for, then it didn't work, probably a typo or non-existing interface. (As shown in the earlier posts.)
So you need these commands to run a test successfully:
diagnose traffictest port 5200
diagnose traffictest proto 0
diagnose traffictest client-intf port15
diagnose traffictest server-intf port15
diagnose traffictest run -c x.x.x.x
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1710 | |
1093 | |
752 | |
446 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.