ADDERLink INFINITY dual 2020 Manual v30

							40
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
Configuring the switches and devices
The layout is vital but so too is the configuration:
• Enable IGMP Snooping on all L2 switches.
• Ensure that IGMP Fast-Leave is enabled on all switches with ALIF units connected 
directly to them.
• Enable the L3 switch as an IGMP Querier.
• Enable Spanning Tree Protocol (STP) on all switches and importantly also enable 
portfast (only) on all switch ports that have ALIF units connected. 
• If any hosts will use any video resolutions using 2048 horizontal pixels (e.g. 2048 x 
1152), ensure that Jumbo Frames are enabled on all switches.
• Choose an appropriate forwarding mode on all switches. Use Cut-through if available, 
otherwise Store and forward.
• Optimize the settings on the ALIF transmitters:
• If moving video images are being shown frequently, then leave Frame Skipping at a 
low percentage and instead reduce the Peak bandwidth limiter.
• Where screens are quite static, try increasing the Background Refresh interval and/
or increasing the Frame skipping percentage setting.
 Make changes to the ALIF transmitters one at a time, in small steps, and view typical 
video images so that you can attribute positive or negative results to the appropriate 
control.
• Ensure that all ALIF units are fully updated to the latest firmware version (at least 
v2.1).   
						

							41
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
APPENDIX D - Troubleshooting
Problem: The video image of the ALIF receiver shows horizontal lines across 
the screen. 
This issue is known as Blinding because the resulting video image looks as though you’re 
viewing it through a venetian blind. 
When video is transmitted by ALIF units, the various lines of each screen are divided up 
and transmitted as separate data packets. If the reception of those packets is disturbed, 
then blinding is caused. The lines are displayed in place of the missing video data packets. 
There are several possible causes for the loss of data packets:
• Incorrect switch configuration. The problem could be caused by multicast flooding, 
which causes unnecessary network traffic. This is what IGMP snooping is designed to 
combat, however, there can be numerous causes of the flooding. 
• Speed/memory bandwidth issues within one or more switches. The speed and 
capabilities of different switch models varies greatly. If a switch cannot maintain pace 
with the quantity of data being sent through it, then it will inevitably start dropping 
packets.
• One or more ALIF units may be outputting Jumbo frames due to the video resolution 
(2048 horizontal pixels) being used. If jumbo frames are output by an ALIF unit, but 
the network switches have not been configured to use jumbo frames, the switches 
will attempt to break the large packets down into standard packets. This process 
introduces a certain latency and could be a cause for dropped packets.
• One or more ALIF units may be using an old firmware version. Firmware versions 
prior to v2.1 exhibited an issue with the timing of IGMP join and lea ve commands that 
caused multicast flooding in certain configurations.
Remedies: 
• Ensure that IGMP snooping is enabled on all switches within the subnet.
• Where each ALIF unit is connected as the sole device on a port connection to 
a switch, enable IGMP Fast-Leave (aka Immediate Leave) to reduce unnecessary 
processing on each switch.    
• Check the video resolution(s) being fed into the ALIF transmitters. If resolutions using 
2048 horizontal pixels are unavoidable then ensure that Jumbo frames are enabled on 
all switches.
• Check the forwarding mode on the switches. If Store and forward is being used, try 
selecting Cut-through as this mode causes reduced latency on lesser switch designs.  
• Ensure that one device within the subnet is correctly configured as an IGMP Querier, 
usually a layer 3 switch or multicast router.
• Ensure that the firmware in every ALIF unit is version 2.1 or greater.
• Try adjusting the transmitter settings on each ALIF to make the output data stream as 
efficient as possible. See ALIF transmitter video settings for details.
continued   
						

							42
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
Problem: The mouse pointer of the ALIF receiver is slow or sluggish when 
moved across the screen.
This issue is often related to either using dithering on the video output of one or more 
transmitting computers or using VGA-to-DVI video converters.
Dithering is used to improve the perceived quality and color depth of images by diffusing 
or altering the color of pixels between video frames. This practice is commonly used 
on Apple Mac computers using ATI or Nvidia graphics cards. VGA-to-DVI converters 
unwittingly produce a similar issue by creating high levels of pixel background noise.
ALIF units attempt to considerably reduce network traffic by transmitting only the pixels 
that change between successive video frames. When dithering is enabled and/or VGA-to-
DVI converters are used, this can have the effect of changing almost every pixel between 
each frame, thus forcing the ALIF transmitter to send the whole of every frame: resulting 
in greatly increased network traffic and what’s perceived as sluggish performance.
Remedies:
•  Linux PCs 
 Check the video settings on the PC. If the Dither video box option is enabled, disable it.
•  Apple Mac with Nvidia graphics
 Use the Adder utility for Mac’s – Contact technical support.
•  Apple Mac with ATI graphics
 Enable the Magic Eye dither removal feature.
•  Windows PCs
 If you suspect these issues with PC’s, contact technical support for assistance.
• Replace old VGA adapters on host computers with DVI video cards.
Problem: My monitor is displaying a pink screen
It is possible that the source computer and ALIF transmitter are sending a high resolution 
Dual Link signal in response to a request from your Dual Link monitor. However, your 
ALIF receiver is unable to correctly process the signal, causing the pink screen issue (DVI 
resolutions above 1920 x 1200 are generally Dual Link).  
ALIF2002T and 2112T transmitters are able to send Dual Link video when requested, 
however, an ALIF2000R receiver is required to process the higher resolution signal fully 
at the other end. Other receivers, such as the ALIF1000R, 1002R and 2020R units cannot 
process Dual Link DVI as they are Single Link devices.
Ensure that the ALIF transmitter is set to supply a Single Link EDID to the graphics card. 
When the video source is changed to a Single Link video resolution, the pink screen 
should disappear and the video should be displayed normally. Alternatively, change the 
monitor to a Single Link DVI monitor.
It is important not to mix Dual Link Transmitters with Single Link Receivers.
On an A.I.M. controlled system, ensure that the Video compatibility check is enabled as 
this ensures that the correct video mode is displayed for the monitor being used.
Problem: The audio output of the ALIF receiver sounds like a scratched re-
cord.
This issue is called Audio crackle and is a symptom of the same problem that produces 
blinding (see previous page). The issue is related to missing data packets.
Remedies: 
As per blinding discussed previously. 
Problem: A.I.M. cannot locate working ALIF units.
There are a few possible causes:
• The ALIF units must be reset back to their zero config IP addresses for A.I.M. 
discovery. If you have a working network of ALIF’s without A.I.M. and then add A.I.M. to 
the network A.I.M. will not discover the ALIFs until they are reset to the zero config IP 
addresses. 
• This could be caused by Layer 2 Cisco switches that have Spanning Tree  Protocol 
(STP) enabled but do not also have portfast enabled on the ports to which ALIF units 
are connected. Without portfast enabled, ALIF units will all be assigned the same 
zero config IP address at reboot and A.I.M. will only acquire them one at a time on a 
random basis. 
 You can easily tell whether portfast is enabled on a switch that is running STP: When 
you plug the link cable from a working ALIF unit into the switch port, check how long 
it takes for the port indicator to change from orange to green. If it takes roughly one 
second, portfast is on; if it takes roughly thirty seconds then portfast is disabled.             
Remedies: 
• Ensure that the ALIF units and the A.I.M. server are located within the same subnet 
because A.I.M. cannot cross subnet boundaries.
• Manually reset the ALIF units to their zero config IP addresses. 
• Enable portfast on all switch ports that have ALIF units attached to them or try 
temporarily disabling STP on the switches while A.I.M. is attempting to locate ALIF 
units.   
						

							43
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
APPENDIX E - Glossary
Internet Group Management Protocol
Where an ALIF transmitter is required to stream video to 
two or more receivers, multicasting is the method used. 
Multicasting involves the delivery of identical data to 
multiple receivers simultaneously without the need to 
maintain individual links. When multicast data packets enter 
a subnet, the natural reaction of the switches that bind 
all the hosts together within the subnet, is to spread the 
multicast data to all of their ports. This is referred to as 
Multicast flooding and means that the hosts (or at least 
their network interfaces) are required to process plenty of 
data that they didn’t request. IGMP offers a partial solution.
The Internet Group Management Protocol (IGMP) is 
designed to prevent multicast flooding by allowing Layer 
3 switches to check whether host computers within 
their care are interested in receiving particular multicast 
transmissions. They can then direct multicast data only to 
those points that require it and can shut off a multicast 
stream if the subnet has no recipients.
There are currently three IGMP versions: 1, 2 and 3, with 
each version building upon the capabilities of the previous 
one: 
• IGMPv1 allows host computers to opt into a multicast 
transmission using a Join Group message, it is then 
incumbent on the router to discover when they no 
longer wish to receive; this is achieved by polling them 
(see IGMP Querier below) until they no longer respond.
• IGMPv2 includes the means for hosts to opt out as well 
as in, using a Leave Group message. 
• IGMPv3 encompasses the abilities of versions 1 and 2 
but also adds the ability for hosts to specify particular 
sources of multicast data. 
AdderLink Infinity units make use of IGMPv2 when 
performing multicasts to ensure that no unnecessary 
congestion is caused.
IGMP Snooping
The IGMP messages are effective but only operate at 
layer 2 - intended for routers to determine whether 
multicast data should enter a subnet. A relatively recent 
development has taken place within the switches that 
glue together all of the hosts within each subnet: IGMP 
Snooping. IGMP snooping means these layer 2 devices now 
have the ability to take a peek at the IGMP messages. As a 
result, the switches can then determine exactly which of 
their own hosts have requested to receive a multicast – 
and only pass on multicast data to those hosts. 
IGMP Querier
When IGMP is used, each subnet requires one Layer 3 
switch to act as a Querier. In this lead role, the switch 
periodically sends out IGMP Query messages and in 
response all hosts report which multicast streams they 
wish to receive. The Querier device and all snooping Layer 
2 switches, then update their lists accordingly (the lists are 
also updated when Join Group and Leave Group (IGMPv2) 
messages are received).  
IGMP Fast-Leave (aka Immediate Leave)
When a device/host no longer wishes to receive a 
multicast transmission, it can issue an IGMP Leave Group 
message as mentioned above. This causes the switch to 
issue an IGMP Group-Specific Query message on the port 
(that the Leave Group was received on) to check no other 
receivers exist on that connection that wish to remain a 
part of the multicast. This process has a cost in terms of 
switch processor activity and time. 
Where ALIF units are connected directly to the switch 
(with no other devices on the same port) then enabling 
IGMP Fast-Leave mode means that switches can 
immediately remove receivers without going through 
a full checking procedure. Where multiple units are 
regularly joining and leaving multicasts, this can speed up 
performance considerably. 
Jumbo frames (Jumbo packets)
Since its commercial introduction in 1980, the Ethernet 
standard has been successfully extended and adapted to 
keep pace with the ever improving capabilities of computer 
systems. The achievable data rates, for instance, have risen 
in ten-fold leaps from the original 10Mbit/s to a current 
maximum of 100Gbit/s. 
While data speeds have increased massively, the standard 
defining the number of bytes (known as the Payload) 
placed into each data packet has remained resolutely stuck 
at its original level of 1500 bytes. This standard was set 
during the original speed era (10Mbits/s) and offered the 
best compromise at that speed between the time taken to 
process each packet and the time required to resend faulty 
packets due to transmission errors. 
But now networks are much faster and files/data streams 
are much larger; so time for a change? Unfortunately, a 
wholesale change to the packet size is not straightforward 
as it is a fundamental standard and changing it would mean 
a loss of backward compatibility with older systems.
Larger payload options have been around for a while, 
however, they have often been vendor specific and at 
present they remain outside the official standard. There 
is, however, increased consensus on an optional ‘Jumbo’ 
payload size of 9000 bytes and this is fully supported by 
the AdderLink Infinity (ALIF) units.
Jumbo frames (or Jumbo packets) offer advantages for 
ALIF units when transmitting certain high resolution video 
signals across a network. This is because the increased data 
in each packet reduces the number of packets that need to 
be transferred and dealt with - thus reducing latency times.
The main problem is that for jumbo frames to be possible 
on a network, all of the devices on the network must 
support them.   
						

							44
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
Spanning Tree Protocol (STP)
In order to build a robust network, it is necessary 
to include certain levels of redundancy within the 
interconnections between switches. This will help to 
ensure that a failure of one link does not lead to a 
complete failure of the whole network.
The danger of multiple links is that data packets, especially 
multicast packets, become involved in continual loops as 
neighbouring switches use the duplicated links to send and 
resend them to each other. 
To prevent such bridging loops from occurring, the 
Spanning Tree Protocol (STP), operating at layer 2, is 
used within each switch. STP encourages all switches 
to communicate and learn about each other. It prevents 
bridging loops by blocking newly discovered links until it 
can discover the nature of the link: is it a new host or a 
new switch? 
The problem with this is that the discovery process can 
take up to 50 seconds before the block is lifted, causing 
problematic timeouts.
The answer to this issue is to enable the portfast variable 
for all host links on a switch. This will cause any new 
connection to go immediately into forwarding mode. 
However, take particular care not to enable portfast on 
any switch to switch connections as this will result in 
bridging loops.
Forwarding modes
In essence, the job of a layer 2 switch is to transfer as 
fast as possible, data packets arriving at one port out to 
another port as determined by the destination address. 
This is known as data forwarding and most switches offer 
a choice of methods to achieve this. Choosing the most 
appropriate forwarding method can often have a sizeable 
impact on the overall speed of switching:
• Store and forward is the original method and requires 
the switch to save each entire data packet to buffer 
memory, run an error check and then forward if no 
error is found (or otherwise discard it).
• Cut-through was developed to address the latency 
issues suffered by some store and forward switches. 
The switch begins interpreting each data packet as it 
arrives. Once the initial addressing information has been 
read, the switch immediately begins forwarding the 
data packet while the remainder is still arriving. Once 
all of the packet has been received, an error check is 
performed and, if necessary, the packet is tagged as 
being in error. This checking ‘on-the-fly’ means that 
cut-through switches cannot discard faulty packets 
themselves. However, on receipt of the marked packet, a 
host will carry out the discard process.     
• Fragment-free is a hybrid of the above two methods. 
It waits until the first 64 bits have been received before 
beginning to forward each data packet. This way the 
switch is more likely to locate and discard faulty packets 
that are fragmented due to collisions with other data 
packets.  
• Adaptive switches automatically choose between the 
above methods. Usually they start out as a cut-through 
switches and change to store and forward or fragment-
free methods if large number of errors or collisions are 
detected. 
So which one to choose? The Cut-through method has the 
least latency so is usually the best to use with AdderLink 
Infinity units. However, if the network components and/
or cabling generate a lot of errors, the Store and forward 
method should probably be used. On higher end store and 
forward switches, latency is rarely an issue.
Layer 2 and Layer 3: The OSI model
When discussing network switches, the terms Layer 2 and 
Layer 3 are very often used. These refer to parts of the 
Open System Interconnection (OSI) model, a standardized 
way to categorize the necessary functions of any standard 
network. 
There are seven layers in the OSI model and these define 
the steps needed to get the data created by you (imagine 
that you are Layer 8) reliably down onto the transmission 
medium (the cable, optical fiber, radio wave, etc.) that 
carries the data to another user; to complete the picture, 
consider the transmission medium is Layer 0. In general, 
think of the functions carried out by the layers at the top 
as being complex, becoming less complex as you go lower 
down. 
As your data travel down from you towards the 
transmission medium (the cable), they are successively 
encapsulated at each layer within a new wrapper (along 
with a few instructions), ready for transport. Once 
transmission has been made to the intended destination, 
the reverse occurs: Each wrapper is stripped away and the 
instructions examined until finally only the original data are 
left.
So why are Layer 2 and Layer 3 of particular importance 
when discussing AdderLink Infinity? Because the successful 
transmission of data relies upon fast and reliable passage 
through network switches – and most of these operate at 
either Layer 2 or Layer 3.
The job of any network switch is to receive each incoming 
network packet, strip away only the first few wrappers to 
discover the intended destination then rewrap the packet 
and send it in the correct direction. 
continued   
						

							45
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
In simplified terms, the wrapper that is added at Layer 2 
(by the sending system) includes the physical address of 
the intended recipient system, i.e. the unique MAC address 
(for example, 09:f8:33:d7:66:12) that is assigned to every 
networking device at manufacture. Deciphering recipients 
at this level is more straightforward than at Layer 3, where 
the address of the recipient is represented by a logical IP 
address (e.g. 192.168.0.10) and requires greater knowledge 
of the surrounding network structure. Due to their more 
complex circuitry, Layer 3 switches are more expensive 
than Layer 2 switches of a similar build quality and are 
used more sparingly within installations.   
						

							46
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
General specifications
Casing (w x h x d):  198mm (7.92”) x 44mm (1.76”) x 150mm (6.0”)
Construction:    1U compact case, robust metal design 
Weight:     1.1kg (2.4lbs)
Mount kits:    Rack mount - single or dual units per 1U slot.
     VESA monitor / wall mount chassis.
Power to adapter:  100-240VAC 50/60Hz, 0.8A, 
Power to unit:   5VDC 20W
Operating temp:     0ºC to 40ºC (32ºF to 104ºF)
Approvals:    CE, FCC
9pin D-type  female9pin D-type female
Supported video modes
ALIF units support all VESA and CEA video modes.
RS232 ‘null-modem’ cable pin-out
APPENDIX F - Cable pinouts, video modes and general specifications   
						

							47
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
APPENDIX G - Fiber modules and cables
To suit your installation layout, two fiber modules are available for the ALIF dual units 
to suit various fiber optic cables. The specifications for all are summarized in the table 
below:   
Fiber TypeFiber sizeFiber Type CodingDistance  
at 
1Gbps
Adder part 
number for 
SFP module
Bar  
color
Conn.  
type
Normal 
Applications
Military 
Applications
Suggested Print 
Nomenclature
OM1(62.5/125) Multimode  
(TIA-492AAAA)
OrangeSlate62.5/125220mSFP-MM-LCBlackLC
OM2(50/125)Multimode   
(TIA-492AAAB) 
OrangeOrange50/125550m“““
OM3(50/125)Multimode  
(850 nm Laser-optimized)  
(TIA-492AAAC) 
AquaUndefined850 LO 50 /125550m“““
OM4(50/125)Multimode   
(850 nm Laser-optimized)  
(TIA-492AAAC) 
AquaUndefined850 LO 50 /125550m “““
OS1 and OS2(9/125)Single-mode  
(TIA-492C000 / TIA-492E000)
YellowYellowSM/NZDS, SM10KmSFP-SM-LCBlueLC   
						

							48
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
Single unit rack brackets
The optional single unit brackets (plus four screws), allow 
a unit to be secured within a standard rack half width slot. 
IMPORTANT - allow space for airflow
The ALIF units and their power supplies generate heat when 
in operation and will become warm to the touch. 
Do not place them in locations where air cannot circulate 
to cool the equipment. When mounting units within a rack 
chassis, allow a 1/3rd U space (1.5cm) between rows of devices:    
Do not operate the equipment in ambient temperatures 
exceeding 40oC. Do not place the products in contact with 
equipment whose surface temperature exceeds 40oC .  
1/3 U 
(1.5cm) 
space for 
cooling
APPENDIX H - Mounting options
There are several mounting methods for transmitter and receiver units:
• The supplied four self-adhesive rubber feet
• Optional single unit rack brackets - this page
• Optional dual unit rack brackets
• Optional VESA bracket mount   
						

							49
INSTALLATION
CONFIGURATION
OPERATION
FURTHERINFORMATION
INDEX
Double unit rack brackets
This optional kit comprises four brackets (plus twelve screws) 
and allows two ALIF units to be mounted side by side and 
fitted into a 1U rack slot.   
IMPORTANT - allow space for airflow
The ALIF units and their power supplies generate heat when 
in operation and will become warm to the touch. 
Do not place them in locations where air cannot circulate 
to cool the equipment. When mounting units within a rack 
chassis, allow a 1/3rd U space (1.5cm) between rows of devices:    
Do not operate the equipment in ambient temperatures 
exceeding 40oC. Do not place the products in contact with 
equipment whose surface temperature exceeds 40oC .  
1/3 U 
(1.5cm) 
space for 
cooling