Follow

10gb Marvell/Aquantia NIC Troubleshooting for TC2Elite, TC1 and 3P2

With the recent development of 10GB NIC technology, NewTeks implementation is ahead of industry standards.  What we have noticed is that there is complexity that can arise with their integration and we've found that there are certain parameters that need to be checked and considered if issues arise.  Most customers won't need to consider the following troubleshooting steps, but if an issue arises that is specific to the 10gb connection (and is not occurring on the 1gb connection), these article outlines the checks we look for:

 

Points to consider:

- Aquantia is a part of the Marvell corporation.
- Issues with 10Gbe NDI transmission are rare and in the few instances, we have seen issues arise they are usually caused by network environments and implementation of NDI Transport mode.

 

Diagnose symptoms:


1) Is the issue on NDI Input (Receive) or NDI Output (Send)


2) Describe what is being seen: Dropped frames (represents as a “stutter” and unsmooth
motion) or pixelization/distortion (may be described as “pixel moshing” or “melting”)


Physical checks (layer 1):


3) Exit the TriCaster to Windows – open Network Adapter Options and open the 10gbe NIC,
click on details – what link speed is being stated?


4) Network: Make, model, and firmware of switch


5) Verify that Cat 6a or Cat 7 cabling is being utilized for 10Gbe


6) How is the 10Gbe connected to the switch? RJ45 or is a SFP+ to RJ45 in use?


7) If using an SFP+ adapter, please note make and model – is it compatible with the switch?


8) Are the 10Gbe and 1gbe network ports connected to the same switch or network?

If yes to q8:

- Are they on separate physical networks?
- Are they on separate VLANS?
- Is NDI blocked on the 1Gbe link (ports 5960 and above, mDNS disabled)?

mceclip0.png

Strip back:

9) Set up a clean session with a single source as input and set up a single receiver (Studio
monitor, Spark Plus IO)


10) Does the issue occur on send or receive? If visual symptoms are visible in the Multiviewers/SDI
Output then this a “TriCaster receive issue”. If visual symptoms are only on the NDI Receiver this is a “TriCaster send” issue.


THIS DOES NOT NECESSARILY MEAN THE TRICASTER ITSELF IS AT FAULT BUT THE ENVIRONMENT/NETWORK IS LIKELY THE CAUSE AT THIS STAGE.

 

If an NDI input issue:


11) If on input (receive) try alternative traffic modes under add ons: Access Manager: Advanced.
Typically Prefer-UDP or Prefer-Single TCP should resolve the issue.


12) If not run iPerf test over the link and share results

If an NDI Output issue:

13) Check receiver cabling
14) Check receiver firmware/software is up to date
15) If possible, set receive mode to UDP or Single TCP
16) Does this resolve?


iPerf Testing Steps


a) Download the iperf utility. A copy can be found at iperf.fr
On the server that will be receiving data open an elevated command window and run the
following command:

 iperf.exe –s


b) On the server that will be sending data open an elevated command window and run the
following command:

 iperf –c x.x.x.x –w 2m –t 30s –i 1s


c) Replace the x.x.x.x with the IP address of the server from step 2.
d) Review the data returned on the server from step 3. The output should look similar to the
below text:

mceclip1.png


NDI Analysis Steps


a) Exit to windows from TriCaster and run NDI Analysis Beta (from www.ndi.tv/tools)


b) Run analysis on either sending source or receiver


c) Make sure Video Send and Video Receive AVG numbers are at or below the ms timing for
the corresponding framerate with the expected format, with a +/- Jitter that in total does
not exceed 1.0ms over the metric:


d) 60p (60 Hz) = 16.66 ms


e) 59.97p (59.97 Hz) = 16.67 ms


f) 50p (50 Hz) = 20 ms


g) 30p (30 Hz) = 33.33 ms


h) i60/29.97p (29.97 Hz) = 33.36 ms


i) i50/25p (25 Hz) = 40 ms

- It is ok if frames arrive early on Video Send or Video Receive.
- The focus should be on late packets/frames.

j) Copy and paste as a text file into your support ticket.


Update 10Gbe NIC driver:


a) Marvell/Aquantia released a new driver for the AQC-107 in Aug of 2020, and MSI has updated their official release to Feb of 2021. If all the above produces no improvement
and we are confident that there are no other physical or software issues, then update
the driver to version 2.2.1.0.

- https://www.msi.com/Motherboard/support/Creator-X299#downdriver&Win10%2064

b) After updating, go back to the Advanced Driver settings (these are reset after driver
update)


c) Disable IPv6 in the NIC properties10Gbe Troubleshooting for 2 Elite, TC1, 3Play 3P1 and 3P2


mceclip3.png


d) Disable Downshift retries


e) Disable Recv Segment Coalescing (IPV4)


f) Disable Recv Segment Coalescing (IPV6)10Gbe Troubleshooting for 2 Elite, TC1, 3Play 3P1 and 3P2

g) Ensure Energy Efficient Ethernet is disabled.10Gbe Troubleshooting for 2 Elite, TC1, 3Play 3P1 and 3P2

h) Set Transmit Buffer size to 4096


i) Set Receive Buffer size to 409610Gbe Troubleshooting for 2 Elite, TC1, 3Play 3P1 and 3P2


After updating the driver:


1) Re run NDI Analysis
2) rerun iperf tests.
3) Check simplified set up – one NDI input, one NDI output
4) Repeat earlier steps if required

 

If you require assistance beyond this documentation we recommend contacting our Professional Services Team for technical consultation.

 

*Current as of 4/29/2022.  Prepared by NewTek Professional Services.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.