Hello,
NTA "Add Device" with the sFlow Setting Disabled generally means that you do not need NTA to configure sFlow for you on the devices. Enabled implies that when you deploy the server (on the Server Settings, checking the box for the device and clicking Deploy) with the device, it will attempt to use SNMP SET to configure an sFlow instance on the device. This only works on some device models that support it and is normally not required to get sFlow working.
Please ignore FTP Username and Password. This is not necessary here, and would require that you install and configure a third-party FTP Server (such as FileZilla) on the IMC server, then configure a folder and username + password, that you will enter here. FTP is only needed when you are using the NTA Probes, which are essentially a software that can be used to capture mirrored traffic on a network where it is not possible to use sFlow or NetFlow/NetStream. Otherwise it can be left blank.
Your sFlow configuration looks fine based on your output. Although you are using the NetStream port 9020 instead of 6343 for sFlow on Comware and that is unusual. As for the ProCurve, could it be that sFlow is not enabled with the correct IP to reach IMC? Datagrams sent = 0
Here are sample CLI Scripts for sFlow configuration on ProCurve and Comware 5 switches that could be used in IMC (Configuration Center > Configuration Templates > Add CLI Script). Variables added where appropriate. If running the commands manually, please manually replace all variables like ${agent-ip} below.
Comware 5:
sflow agent ip ${agent-ip}
sflow collector ${collector-id (1-3)} ip ${nta-ip} description imcserver
interface ${interface (like G1/0/3 or Ten2/0/4)}
sflow flow collector ${collector-id (1-3)}
sflow sampling-rate ${sampling-rate (1000-5000)}
sflow counter collector ${collector-id (1-3)}
sflow counter interval ${counter-interval (in seconds, 2-86400)}
quit
ProCurve/ArubaOS:
configure
sflow ${collector-id (1-3)} destination ${nta-ip} 6343
sflow ${collector-id (1-3)} sampling ${sample-interfaces (enter the port range or 'all')} ${sampling-rate (50-16441700)}
sflow ${collector-id (1-3)} polling ${polling-interfaces (enter the port range or 'all')} ${polling-interval (in seconds, 20-2147483647)}
You could try deploying these on your switches as needed and see if that helps. The Comware template only includes a single interface but could be edited and expanded with more interfaces or interface-range as needed.