During the test with 40G LAN interfaces at both IXIA and DUT side, it has been found, that VSPERF is not able to bring up 40G LAN interfaces at IXIA side. It is visible, that interfaces are firstly configured from 40G to 10G. After that reconfiguration back to 40G is performed, but interfaces are never brought up. As a result initialization of IxNet is not successful and VSPERF TC execution fails.

Technical details:
VSPERF currently uses TCL script (tools/pkt_gen/ixnet/ixnetrfc2544.tcl) to configure IxNetwork TCL server and execute the test. The original TCL script used by VSPERF has been exported from IxNetwork after manual configuration of Quicktest. This exported file has been later modified to allow changes of frame size, type of the test (throughput/back2back/continuous), etc.

The type of the IXIA port is hard coded inside the script to 10G (i.e. tenGigLan) on many places, e.g.:

    set sg_vport [ixNet add $ixNetSG_Stack(0) vport]
    ixNet setMultiAttrs $sg_vport \
     -transmitIgnoreLinkStatus False \
     -txGapControlMode averageMode \
     -type tenGigLan \
     -connectedTo ::ixNet::OBJ-null \
     -txMode interleaved \
     -isPullOnly False \
     -rxMode captureAndMeasure \
     -name {10GE LAN - 001}
    ixNet setMultiAttrs $sg_vport/l1Config \
     -currentType tenGigLan
    ixNet setMultiAttrs $sg_vport/l1Config/tenGigLan \

After some debugging it has been confirmed that 40G IXIA interfaces are analogically referred as fourtyGigLan inside TCL, but it is not enough to replace tenGigLan by fourtyGigLan at all places. Some of the configuration properties used by tenGigLan settings are not available for fourtyGigLan. So it must be investigated in more detail. The same would apply for 100G and 1G interfaces.