dSnake issue – fibre link

[Anonymous]

Anyone used a fibre link for dSnake – getting a connection failure atm…

Any clues on frame size etc?

[Anonymous]

Note – vlanning through a pair of net gear gs724, but won’t even bounce through one of them at the moment,

Cables confirmed good.

[Anonymous]

Single, error LED and clicking on channels with phantom

[Anonymous]

Ok, clicks on all channels.

I’m assuming that there is too much jitter/latency. We’re about to try a different VLAN confit (not trucked over two fibres)

[Andreas]

Switching from one media to another indeed may impose too much latency. Not sure if switching between copper and fiber will work without store&forward.

[Nicola A&H]

This document refers to ACE but the same recommendations apply to dSNAKE:
https://www.allen-heath.com/media/ACE_over_FibreOptic_201210.pdf

Also see this article: https://allen-heath.helpserve.com/Knowledgebase/Article/View/703/0/can-i-run-dsnake-through-a-network-switch

[Anonymous]

Sorted… LLDP was one issue, Aggregation was another.

[Anonymous]

The setup is now as follows…

QU16 connected via ~20m of cat6 (two patch cables and one infrastructure) into a switch.
Vlanned (over a single fibre) to an identical switch, through another set of patch/infrastructure/patch cables to the AR24.

The fibre is about another 15m strung across the road.

The same switches are handling a low latency bidirectional video feed, now tied to the other fibre (it was less fussy about the aggregation).

Without the switches trying to do aggregation or protocol discovery it works – just as it should do.

[Anonymous]

Wow – that was a show and a half – just been to the final night.

The mixer, and dSnake, have been rock solid throughout – would I expect anything less?

[Author]

Posts