Használati útmutató Adder Link Infinity Manager

Adder nincs kategorizálva Link Infinity Manager

Olvassa el alább 📖 a magyar nyelvű használati útmutatót Adder Link Infinity Manager (154 oldal) a nincs kategorizálva kategóriában. Ezt az útmutatót 8 ember találta hasznosnak és 2 felhasználó értékelte átlagosan 4.5 csillagra

Oldal 1/154
AdderLink Innity Manager
User Guide
Experts in
Connectivity
Solutions
INSTALLATION
1
CONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Introduction
Local feed through 3 ...............................................................................................
A.I.M. basics 4 ...........................................................................................................
Supplied items 6 .......................................................................................................
Installation
Connections 7 ..........................................................................................................
Installation requirements 8 ....................................................................................
Tips for a successful implementation 8 ...............................................................
Mounting the A.I.M. server 9 .................................................................................
Conguration
Supported browsers 10 ..........................................................................................
Login for admin users 10 ........................................................................................
Important rst conguration steps ................................................................11
Adding AdderLink Innity units ......................................................................12
The Dashboard tab 13 ............................................................................................
Enabling Remote Support 25 ...................................................... ...........................
The Channels tab 27 ...............................................................................................
The Receivers tab 30 ..............................................................................................
The Transmitters tab .........................................................................................34
The C-USB LAN tab 37 .........................................................................................
The Servers tab 38 ..................................................................................................
The Users tab 39 .....................................................................................................
The Presets tab 43 ...................................................................................................
The Statistics tab 45 ................................................................................................
Operation
Logging in 46 .............................................................................................................
The Local OSD screen 47 ......................................................................................
Listing C-USB LAN transmitters 48 ..............................................................
Using the Remote OSD feature 49 ................................................................
Further information
Lithium battery ...................................................................................................50
Getting assistance 50 ..............................................................................................
Appendix A - Tips for success when networking ALIF units 51 ...................
Appendix B - Troubleshooting 53 .........................................................................
Appendix C - Redundant servers: Setting up and swapping out 54 .............
Setting up A.I.M. server redundancy .........................................................54
Operation of Redundancy ..........................................................................54
Swapping out an A.I.M. server....................................................................55
Appendix D - Upgrade license 56 ........................................................................
Appendix E - Glossary ......................................................................................57
Appendix F - A.I.M. API .....................................................................................60
Appendix G - DHCP server requirements for ALIF support 72 ..................
Using DHCP Option 125 73 ...........................................................................
Appendix H - Technical specications ...........................................................74
Index
Contents
INSTALLATION
2
CONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
AdderLink Innity transmitter and receiver units allow multiple remote users to access
host computers in a very exible manner. Such exibility requires management and
coordination – that is where A.I.M. (AdderLink Innity Manager) becomes vital.
A.I.M. is designed to promote the most efcient use of AdderLink Innity (ALIF) units
by allowing central control over any number of transmitters and receivers. Using the
intuitive A.I.M. web-based interface, one or more administrators can manage potentially
thousands of users who are interacting with an almost unlimited number of devices.
A.I.M. operates as a self-contained compact server (including its own DHCP server) unit
that can be situated anywhere within your network of ALIF devices:
The A.I.M. server is supplied pre-loaded and is straightforward to deploy, requiring only a
network connection and a power input to begin operation.
All conguration of your AdderLink Innity transmitters (channels), receivers and users
are performed using the intuitive A.I.M. browser interface via a network connected
computer.
The A.I.M. server front panel
The A.I.M. server rear panel.
In normal use only the network and power connectors are used (ringed in red).
The A.I.M. server connects to your network and provides administrative
control over the various AdderLink Innity transmitters, receivers and their users.
Note: Although the AdderLink Innity units require Gigabit Ethernet connections, in its
administrative role, the A.I.M. server requires only a 10/100Mbps connection
to the network.
Please see the section Basic steps for a new conguration for assistance with
creating A.I.M. installations.
Introduction
Green
indicator:
Power
Red
indicator:
Drive
activity
INSTALLATION
3
CONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
LOCAL FEED THROUGH
ALIF receivers which are equipped with dual IP network ports (ALIF1002, ALIF2000 and
ALIF2020) can be congured to support a local link to a host PC in addition to the main
link to the network. The locally linked PC remains completely isolated from the main
network.
To congure this arrangement, ensure that the IP port that is used for the local link is
not allocated an IP address.
Note: For the local feed through feature to operate, the A.I.M. server must be at version 4.8 or
greater while the endpoints must be at version 4.6 or greater.
In operation, the user of the console at the ALIF
receiver can use the following hotkey combination
to toggle between the network and local links:
CTRL + ALT + L
(this feature is programmable via the A.I.M. server)
ww ad d e r. co mw.
AdderLink
NET SER AUD US B DVI PWR
R E C E I V E R
ALIF TX
ALIF TX ALIF TX
ALIF TX
Link local
Hotk ol:ey switching contr
CTRL + ALT + L
Gigabit
Ethernet
ADMIN
www der.com.ad
AdderLink
MANA GEMEN T S ERVER
1
O
INSTALLATION
4
CONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
A.I.M. BASICS
Channels
Think of a channel as a ‘virtual transmitter’. It is virtual because the video, audio and
USB streams of a channel do not necessarily have to originate from the same physical
transmitter unit, although in most cases they will. For instance, you could arrange for
video and USB streams to be received from one host computer, while the audio stream
came from an alternative source. Alternatively, two channels could be congured for the
same host computer, each with different access rights to suit particular situations.
Groups
In order to accommodate potentially large numbers of users and devices, A.I.M. uses
a system of groups: User Groups, Receiver Groups and Channel Groups. Groups
allow the administrator to apply collective settings to all members and also to take
full advantage of Inheritance. Inheritance allows members of a group to benet from
settings and permissions made within other groups to which their group is linked. This
saves administration time because members do not need to be individually altered. For
instance, if Sam is in User Group 1, all Channels accessible to User Group 1 will be
available to Sam.
User types
This guide refers to the two main categories of users involved with the A.I.M. system:
An accesses the A.I.M. system via a network-linked Admin (administrator) user
computer running an Internet browser. Once the necessary username and password
have been entered, Admin users can make changes to the operation of the A.I.M.
system.
A has a keyboard, video monitor and mouse (plus speakers where Regular user
appropriate) attached to an AdderLink Innity receiver unit and can access one or
more computers that are linked to AdderLink Innity transmitters. The AdderLink
Innity receiver provides an On-Screen Display (OSD) that lists all accessible
computers and allows easy access to them.
Security
Security considerations form a major part of A.I.M. operation, ensuring that users have
rapid access only to the systems for which they have permission. At its core, A.I.M.
manages an important three-way relationship between the users, the AdderLink Innity
receiver(s) and the channels from the host computers.
The diagram shows a representation of the three-way relationship which exists between
users, receivers and channels.
To successfully gain access to a channel:
The user requires permission to use the receiver,
The receiver requires permission to connect with the channel,
AND
The user must have permission to access the channel.
In most cases, the need for three access permissions per connection is unnecessary and
raises administration overheads. Hence, by default, A.I.M. grants open access for the user
to the receiver and the receiver to the channel while restricting the nal, most crucial
piece of the puzzle. For those who require it, the lock upon the user to receiver stage
can be applied individually or globally.
See Permissions on the next page for more details.
continued
INSTALLATION
5
CONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Active Directory
To streamline administration even further, A.I.M. supports Active Directory. By
synchronizing with an LDAP/Active Directory server, details of users (including their
usernames and group memberships) can be securely synchronised from existing
databases in order to both minimize the initial conguration as well as streamline
ongoing updates.
A.I.M. interface
A.I.M. appears in two main ways depending on whether you are an administrator or a
regular user.
For administrators, full access to the AdderLink Innity Manager Suite is granted.
This comprehensive application shows nine main tabbed areas: Dashboard, Channels,
Receivers, Transmitters C-USB LAN Servers Users Presets Statistics, , , , and , each of
which contains numerous related pages of settings and options. The Dashboard
provides a central location from which the administrator can view overall operation,
make various changes, database backups and also upgrade the rmware of any linked
AdderLink Innity unit.
For regular users, an efcient page layout provides for which you
a list of all channels
have permission to visit. Against each selectable channel name and description, a series
of icons provide clear feedback about current availability.
Permissions
Permissions exist between Users, Receivers, and Channels.
By default, all users are granted permission to access ALL receivers.
By default, all receivers have permission to connect to ALL channels.
As shown in the introductory diagram, the missing part is the permission for a user to
access each channel.
Permissions between a user and a receiver can be applied in any of the following ways:
User à Receiver
User à User Group à Receiver
User à User Group à Receiver Group à Receiver
User à Receiver Group à Receiver
Thus, a very indirect way of granting permissions could be:
User1 is in UserGroup1,
UserGroup1 has access to ReceiverGroup1,
ReceiverGroup1 contains Channel1,
Therefore, User1 has access to Channel1 indirectly.
INSTALLATION
6
CONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
SUPPLIED ITEMS
A.I.M. server unit
with integral rack brackets
12V, 5A Power supply plus
country-specic mains cable
Information wallet
containing:
Four self-adhesive rubber feet
Safety document
Replacement power adapter
with locking connector
Part number: PSU-IEC-12VDC-5A
Country-specic power cords
CAB-IEC-AUS (Australia)
CAB-IEC-EURO (Central Europe)
CAB-IEC-UK (United Kingdom)
CAB-IEC-USA (United States)
CAB-IEC-JAPAN (Japan)
7
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
CONNECTIONS
The A.I.M. server unit is supplied fully pre-loaded and permits no local user interaction.
All conguration takes place remotely via the network connections and as a result only
two connections are required: Network and power.
Note: If an existing A.I.M. server must be replaced, follow the important advice given within
Appendix C (Swapping out an A.I.M. server).
Note: The A.I.M. server is supplied with the front panel USB connections blanked off. There is
no need to connect a keyboard or mouse to the unit as conguration takes place across the
network connection.
Network connections
The A.I.M. server has two network connections on the rear panel: port on the left 1
and port on the right. These allow the unit to be connected to internal and external 2
network connections (respectively) as required. The external network connection allows
admin users located away from the internal network to be able to login. Network port 2
supports DHCP, however, port 1 does not and needs to be congured manually.
To connect the internal IP network port
1 Run a category 5e or 6 link cable from the
appropriate hub or router to the A.I.M. server
unit.
2 Connect the plug of the link cable to the left IP
port (1) on the rear panel of the A.I.M. server
unit.
Category 5e or 6 cable from
LAN / network switch
Power supply connection
IMPORTANT: Please read and adhere to the electrical safety information given within the
Safety information section of this guide. In particular, do not use an unearthed power socket or
extension cable.
Note: The A.I.M. server can also be powered from the optional RED-PSU managed power supply
system using a VSC 48 cable.
To connect the power supply
1 Attach the output connector of the power
supply to the power input socket on the left
side of the rear panel.
2 Connect the main body of the power supply to a nearby earthed mains outlet.
To switch on the A.I.M. server unit, click the power
switch on the front panel. Allow 3 minutes for the
booting process to complete.
Installation
Note: The precise operation of the two ports are determined within the A.I.M. server
Management Suite, particularly the Dashboard > Settings > Network page.
8
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
INSTALLATION REQUIREMENTS
The minimum permissible rmware versions for ALIF units linked with the A.I.M.
server depend upon the rmware version that is running on the A.I.M. server itself.
Note: A.I.M. servers with rmware v4.1 or above no longer support the original ALIF1000.
A.I.M. server: v4.0 is intended for use with ALIF endpoints at v3.7
A.I.M. server: v4.1 is intended for use with ALIF endpoints at v4.1
A.I.M. server: v4.2 is intended for use with ALIF endpoints at v4.2
A.I.M. server: v4.3 is intended for use with ALIF endpoints at v4.3
A.I.M. server: v4.4 is intended for use with ALIF endpoints at v4.3 or v4.4*
A.I.M. server: v4.5 is intended for use with ALIF endpoints at v4.5§
A.I.M. server: v4.6 is intended for use with ALIF endpoints at v4.5 or v4.6
A.I.M. server: v4.7 is intended for use with ALIF endpoints at v4.5 or v4.6
A.I.M. server: v4.8 is intended for use with ALIF endpoints at v4.5 to v4.8
* Due to the changes made to ALIF v4.4 endpoint code to support 4 bit Flash
error checking, it is not possible to downgrade from v4.4 endpoint code.
Therefore, v4.4 A.I.M. has been designed to run with both v4.3 and v4.4 endpoint
code. These are both identical in functionality, but v4.4 endpoint code uses 4-bit
ECC ash and v4.3 uses 1-bit ECC ash.
§ To upgrade to v4.5 endpoint code, it is necessary to rst upgrade to v4.4. Once
at v4.4, it is not possible to downgrade. However, v4.5 does allow a downgrade
to v4.4.
Portfast needs to be enabled on the network switch to ensure that the ALIF to A.I.M.
communication happens in a timely manner. Note that Cisco uses the term edge port’
rather than port fast’. The option is enabled on each port to which an A.I.M. unit is
connected. Where portfast is not enabled, if a second A.I.M. is added for redundancy,
this could result in a mis-congured Backup server.
If an existing A.I.M. server must be replaced, follow the important advice given within
Appendix C (Swapping out an A.I.M. server).
When conguring the installation for multicasting (and to improve overall
performance), the network switch(es) being used must support a minimum of IGMP v2
snooping. For faster performance use switches that support IGMP v3.
In order to display video resolutions that use a horizontal video resolution of 2048
pixels, the network switch must have support for Jumbo packets.
Please also see Appendix A - Tips for success when networking ALIF units.
Compatibility matrix
For a full summary of ALIF models and their compatibility with A.I.M. rmware versions,
please go to https://www.adder.com/compatibility
TIPS FOR A SUCCESSFUL IMPLEMENTATION
Installations based upon the Adderlink Innity modules vary widely in their scope and
complexity. Each implementation is distinct, however, there are numerous tips and best
practice recommendations available on the Adder website. Many tips are concerned with
the correct selection and conguration of network switches plus the choice of network
topology.
Please go to http://www.adder.com/alif-successful-implementation
9
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
MOUNTING THE A.I.M. SERVER
The A.I.M. unit is designed to be easy to mount within a standard 19” rack, but is also
suitable for free standing use on the desktop. The server chassis requires just a 1U space
within the rack.
To mount the A.I.M. server within a rack mount
1 Slide the A.I.M. server into the vacant 1U space within the rack mount.
2 Secure each bracket to the rack using two screws per side as shown below:
10
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
This section covers conguration of the AdderLink Innity Manager Suite for administrators.
For details about the regular user interface, please see the section.
Operation
SUPPORTED BROWSERS
The A.I.M. admin interface requires an A-grade browser with Javascript enabled.
For best results always use the latest version of any browser used.
Google Chrome
Firefox
Edge*
Safari for Mac OS*
* The most intensive testing has been carried out using Chrome and Firefox. MS Edge
and Safari are known to work but testing with these browsers has been limited by
comparison.
LOGIN FOR ADMIN USERS
1 Ensure that the A.I.M. server is powered on (allow 3 minutes before accessing).
2 Using a computer located anywhere within the local network open a web browser
(see Supported browsers list opposite) and enter the default IP address for the A.I.M.
server: 169.254.1.3
The Login page will be displayed:
3 Enter your Username and Password and click the Login button.
The default username is and the default password is admin password.
You are strongly recommended to change the default admin password as one of your
rst actions: Go to Dashboard>Users. Click on the furthest right icon in the admin row
(congure users) and change the password for the admin user.
If you check the Remember Me box, a cookie will be stored on the computer,
allowing you to access the admin section without having to log in each time. The
cookie will survive for up to the A.I.M. Admin Timeout period. If you do not check the
Remember Me box, you will remain logged in only for the duration of your browser
session.
4 Continue to the section on the next page.
Important rst conguration steps
Forgotten password
If necessary, click the Forgotten password link to display an assistance page where a
secret code will be given. Provide the secret code to Adder support or your distributor
to obtain an unlock code which can then be entered to reset your password and gain
access.
Conguration
11
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
IMPORTANT FIRST CONFIGURATION STEPS
There are several important conguration steps that must be carried out when starting a
new A.I.M. server for the rst time.
To determine the A.I.M. server’s rôle and main IP address
1 Switch on and log in to the A.I.M. server; you will be presented with the Servers page.
2 Within the Server page, choose the Rôle of this new A.I.M. server:
- This will be the only A.I.M. server on the network (with no redundancy and Solo
failover), or
Primary - This server will be used as part of a redundant cluster of A.I.M. servers,
where it will be the main server used to manage the ALIF units.
3 Click the Save button. You will next be presented with the Dashboard > Settings >
Network page.
4 See the warning below - do not carry out this step while the system is in operation.
Within the section at the top of the page, change the default Ethernet Port 1 A.I.M. IP
Address Netmask) (and options to settings that suit your network conguration and
which will be used henceforth for this server.
IMPORTANT: The Ethernet Port 1 A.I.M. IP Address and Netmask settings
must NOT be changed during operation of the system. Changing these will
invalidate the system’s security and require intervention from the Adder
technical support staff to restore to a working state.
5 You can now either:
Continue with other settings on the same page (See To choose how IP addresses are
applied to ALIF units right), or
Click the Save button. After a short delay the web browser will automatically
redirect itself to the new IP address so that you can continue administering the
A.I.M. server.
Note: Ensure that your computer can view the new IP address, otherwise the A.I.M. server
will appear to be ofine. Depending on your network conguration and that of the computer,
you may need to change the computer’s conguration to be able to see A.I.M. server’s new
network address.
IMPORTANT
Note: If an existing A.I.M. server must be replaced, follow the important advice given within
Appendix C (Swapping out an A.I.M. server).
To choose how IP addresses are applied to ALIF devices
1 Login again to the A.I.M. server and choose the Dashboard > Settings > Network page.
2 The Subnet Operation option may, or may not, be presented at the top of the page.
Note: If Subnet Operation is not present, the A.I.M. server will operate as per the Off setting
described below.
When the Subnet Operation option is present, you have the following choices:
- A.I.M. can administer a single subnet and will use its own DHCP (Dynamic Off
Host Conguration Protocol) server to automatically assign IP addresses to new
ALIF devices, drawing upon a pool of spare addresses dened by you.
- A.I.M. can administer devices across multiple subnets, but will rely upon an On
external DHCP server to assign valid IP addresses to new ALIF devices.
3 If you chose the setting, you now need to dene the boundaries of the IP address Off
pool that will be used by the internal DHCP server. Enter valid start and end addresses
to the IP Pool Lower Limit IP Pool Upper Limit and options.
Note: If you chose the On setting, you will need to perform a similar operation within the
external DHCP server. For details about DHCP server requirements, see .
Appendix G
For further details about other options within this page, see Dashboard > Settings >
Network.
4 When all options have been set, click the button.Save
5 If you need to change the operation of A.I.M. from single subnet to multi-subnet (or
back again) this option only appears after a successful factory reset of A.I.M.
IMPORTANT: To use subnet operation, you must have a DHCP server
within your network in order to assign IP addresses to the A.I.M. and
ALIF endpoints. If subnet operation is used without a DHCP server, the
ALIF endpoints will not communicate with A.I.M. As a result, the A.I.M.
will need a factory reset in order to be able to revert it back to single
subnet mode.
12
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
ADDING ADDERLINK INFINITY UNITS
When new ALIF transmitters and receivers are added to a network, they are designed to
automatically announce themselves* to the A.I.M. server. Once the A.I.M. server receives
their announcement(s), the ALIF units will be added to the administrator’s view of the
Dashboard. From here you can then begin to congure each new ALIF unit.
* ALIF units can be congured either from their own browser-based conguration utility or via
the A.I.M. server. Once an ALIF unit has been congured in one way, it cannot be recongured
using the other method without undergoing a factory reset. This policy is in place to help prevent
accidental overwriting of congurations. It also means that once an ALIF unit has been locally
congured, it will not announce itself to the A.I.M. server upon being added to a network. Please
see right for details about resetting an ALIF unit.
When new ALIF devices announce themselves, depending upon how it was initially
congured (see ), the A.I.M. server will either assign Important rst conguration steps
IP addresses to new ALIF units automatically, or will rely upon an external DHCP server
to do the same. Either way, providing each ALIF device is not already congured and
announces itself to the A.I.M. server (see below for potential issues that can prevent this),
they will be automatically provided with a suitable IP address so that they may operate
within the network. Once ALIF units have been added, you can use the A.I.M. server
Dashboard to select and further congure any or all of them.
If an ALIF unit is not located
There are several reasons why an ALIF unit might not be located by A.I.M.:
The ALIF unit has been locally congured or is otherwise not using its factory default
setting. Try performing a factory reset on an ALIF that is not being located.
The ALIF unit is not located in the same Ethernet segment as the A.I.M. server. Double
check connections and move units where necessary, so that all reside within the same
Ethernet segment.
There is a potential cabling problem between the ALIF and A.I.M. units. Check and
where necessary, replace faulty cables.
AdderLink Innity manual factory reset
Where a previously congured ALIF unit is being added to a network for control by an
A.I.M. server, you can use this method to reset the unit to its default conguration.
To perform a manual factory reset
1 Remove power from the ALIF unit.
2 Use a narrow implement (e.g. a straightened-out paper clip) to press-and-hold the
recessed reset button on the front panel. With the reset button still pressed, re-
apply power to the unit and then release the reset button.
After roughly eight seconds, when the factory reset has completed, ve of the front
panel indicators will ash for a period of three seconds to indicate a successful reset
operation.
Use a straightened-out paper clip to press the reset button
while powering on the unit
www.adder.com
ALIF
AdderLink
ALIF dual or
ALIF dual VNC
Further information
Please also see:
Appendix A - Tips for success when networking ALIF units
Appendix B - Troubleshooting
Appendix C - Redundant servers: Setting up and swapping out
Appendix D - Upgrade license
Appendix E - Glossary
Appendix F - A.I.M. API
Appendix G - DHCP server requirements for ALIF support
Appendix H - Technical specications
Note: For ALIF 100T models, please refer to the ALIF100T manual for details
about performing a manual factory reset.
13
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
THE DASHBOARD TAB
The Dashboard is your main point of contact for checking and changing the general
status of all A.I.M. operations.
Click the DASHBOARD tab to view its initial home page.
The various other Dashboard pages (e.g. Settings, Backups, Updates, etc.) are selectable
within the blue section located just below the tabs.
Dashboard > Home
Shutdown button - Allows the admin user to shut down the A.I.M. server. The OSD
will no longer work on Receivers. The A.I.M. server will need to be manually started
again when next required.
Restart - The admin user can reboot the A.I.M. server. The and admin section
OSD
will be unavailable while the server is rebooting. The time for a reboot can vary
signicantly depending upon settings such as ETH1 obtaining an IP adress by DHCP, or
whether or not the clock is maintained by NTP.
Within the Home page*, the different sections provide a variety of information:
Warning messages - Live alerts are displayed concerning any devices that are ofine,
rebooting, recently added or uncongured.
- shows the ve most recent active sessions, detailing Latest Active Connections
for each: When the session started; which user/receiver/channel is involved; the
connection type (icons show audio, video, serial, USB, exclusive) and IP addresses
in use. The red unplug icon on the far right allows the admin user to disconnect a
connection.
Event Log - shows all actions performed by the admin or end-users within the A.I.M.
system. See also the Event Log page.
- shows the last ve channels created within the Latest Channels Created
A.I.M. system. A channel is created by default when a new transmitter is added and
congured. The edit icon next to a channel allows the admin user to congure the
channel.
- shows the last ve users who logged in (either to the A.I.M. Latest OSD Logins
admin or at an AdderLink Innity Receiver).
- shows the last ve users added to the A.I.M. system, Latest User Registrations
with a link to edit the user’s details/permissions.
- shows the last ve users who changed a channel, either Latest Channel Changes
while using the on-screen display (OSD) at an AdderLink Innity Receiver, or via the
A.I.M. admin control panel.
- shows the last ve receivers to be added and congured Latest Receivers Added
within the A.I.M. network. Click to congure a receiver; click to connect to a
channel; or click to disconnect an existing connection.
Latest Transmitters Added - shows the last ve transmitters to be added and
congured within the A.I.M. network. Click to congure a transmitter.
* The Home page is auto-refreshed every thirty seconds to ensure that the latest
information is always available.
14
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Settings
Click the option below the Dashboard tab.Settings
The Settings section contains global conguration options for the A.I.M. system and is
divided into eight pages, each accessible by clicking the relevant button located below the
blue options bar:
Grant All Users Remote OSD Access
If enabled, allows receivers to be switched remotely from another receivers OSD menu.
Allowed Connection Modes
Determines the global setting that will be applied to all new channels concerning
connection modes. The setting made here is only applied as a default and can be
overridden at the channel level, where necessary. Options are:
Video-Only: Allows users only to view the video output, the USB channel is denied.
Shared:* Allows users to control a system in conjunction with other users.
Exclusive: Grants exclusive control to one user while all others can simultaneously
view and hear, but not control, the output.
: Allows a user to gain private access to a system, while locking out all others. Private
Note: By default, all new channels are set to inherit this global value. So it’s easy to change all
channel connection modes simply by changing the global setting. If a channel has its own setting,
the global setting has no effect on that channel.
* If USB is disabled, Shared mode will not be available as an option.
Rows per page
The number of rows to display in all paginated tables in the admin section.
Locale
Determines the language shown on the OSD menus of the receivers. Note the admin
conguration web pages remain in English.
Debug Level
This allows information to be collected for diagnostic purposes. Do not use the full level
unless advised by an Adder FAE.
API Login required
If enabled, the anonymous use of the A.I.M. API will be disallowed.
Anonymous user
Determines the user permissions to be used when the API is accessed without logging in.
Supported Devices - Indicates the limits of the current license.
Upgrade License - (see Appendix D for details)
Displays information about the number of devices that can be connected to the A.I.M. server.
Licensed Features - Displays the level of operation permitted under the current
license. Click view/change to see more detail and gain a unique identier that can be
declared to Adder when upgrading a license.
GeneralTransmitters Receivers Servers Network Time • Mail Active Directory
For conguration options that affect individual receivers, users channels, etc., see the
sections dealing with those tabs.
Dashboard > Settings > General
Receiver OSD Timeout
Determines the time period of inactivity within the OSD after which a standard user will
be automatically logged out.
A.I.M. Administrator Timeout
Determines the time period of inactivity within the A.I.M. cong pages after which an
admin user will be automatically logged out.
Anonymous User
Determines which user is shown in the log when a receiver is set to ‘No login required.
Disable password Reset
This prevents the password reset button from appearing on the login page.
Hide Dormant Devices
If enabled, devices that have been ofine for more than 24 hours will be hidden.
Grant All Users Private Access
Determines whether a user can connect to a channel privately and thus prevent any other
users from simultaneously connecting to that channel. If not set, users can only connect in
Video-Only mode or Shared mode. Settings that are applied specically to a user will override
settings applied to user groups theyre in, which in turn override this global setting.
Note: If a user has Private Access mode granted or NOT granted at user level, then it doesn’t
matter what settings there are above (usergroups or global).
If a user is set to inherit “Allow Private? mode from their user groups, if any one of their user
groups has “Allow Private?” mode granted, then the user will have it granted, even if the rest
of the user’s usergroups have private mode not granted.
If a user is set to inherit “Allow Private? mode from their user groups, and one of the user
groups is set to inherit from the global setting - if that global setting is “Allow Private? mode,
then effectively the user group is “Allow Private?” mode so the user will be allowed private
mode.
15
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Settings > Transmitters
This page applies a standard global conguration to all transmitters.
Magic Eye
Determines whether the Magic Eye feature should be enabled on ALIF (1002T, 2002T,
2020T or 2112T models only) transmitters. Magic Eye works to overcome the issues
with increased bandwidth usage caused by ‘dithering’ techniques used on some
computers, such as Apple Macs. See the ALIF dual user guide for more details.
DDC
Determines whether video conguration details should be harvested from connected
display screens or a static xed EDID report should be used. Care must be taken when
selecting a Dual Link Video resolution as only ALIF dual units support a Dual Link Video
resolutions. In the case of a Dual Link EDID being set in the Global settings, no EDID will
be set on Video port 2 of the ALIF dual transmitters.
EDID optimisation
When this option is ticked, the Transmitters will compare the native resolution settings
of their monitors when switching. If the monitor has the same native resolution as the
previous one, the new EDID is not sent to the graphics card. This speeds up switching
as the graphics card does not have to go through a hotplug detect routine when a new
receiver is switched to that channel. If the new receiver has a monitor with a different
native resolution, then the EDID will be updated to allow for a change in video mode.
Hot Plug Detect Control
Determines whether to enable hot plug detection for monitors. By default this is enabled.
Hot Plug Detect Signal Period
By default this is set at 100ms, which is sufcient for most graphics cards. Occasionally it
may be necessary to adjust this. An Adder FAE will advise if necessary.
Background Refresh
The number of frames between sending an entire frame of video data. Setting this to a
longer period or disabling this will reduce the bandwidth required.
Compression Level
The newer AFZ+ codec complements the existing AFZ codec by providing greater
compression for increased speed where pixel perfect results are not the primary
focus. The transmitter video conguration page allows you to choose the required
compression mode. Choices are:
‘Pixel perfect’ - only uses pixel perfect AFZ,
‘Adaptive’ - guarantees frame rate, builds to pixel perfect,
‘Smoothest video’ - forces the maximum compression, or
‘Advanced’ - allows you to choose the mode:
1 ‘AFZ only (pixel perfect),
2 ‘AFZ+ Minimum compression’,
3 ‘AFZ+ Middle compression’, or
4 ‘AFZ+ Maximum compression’.
USB Speed
Select Low/full speed or High speed USB operation.
USB Hub Size
Select either a 13 or 7 port USB hub. This determines the number of USB devices that
can be connected to a single Transmitter.
Note: In order to access the BIOS on some host machines it is necessary to change this setting
to 7 ports.
Enable Dummy Boot Keyboard
It is often necessary to have a keyboard reported at start up. This setting means that a
“Virtual Keyboard” is always reported to the USB host. It may be necessary to disable
this for use with some KVM switches.
Reserved USB ports
This setting lets you set aside a specic number of USB ports (up to 8) on the
transmitter that can be made available for certain USB devices which require a quirk
setting under advanced USB features, connected to a receiver.
Note: This setting can only be applied globally it is not found with individual transmitter
congurations because all receivers need to know how many USB ports are available for the
advanced USB features.
Serial port options
These allow you to match the serial conguration being used by the attached PC host.
16
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Settings > Receivers
This page applies a standard global conguration to all receivers.
OSD Hotkeys
Determines whether the OSD hotkeys are enabled or disabled.
Connection Hotkeys
Determines whether the channel switching hotkeys are enabled or disabled.
Hotkey settings
These determine the Hotkeys that can be used to invoke certain functions. It is possible
to select mouse keys to perform these functions, though it is not possible to use both
mouse switching and a hot key combination. It is also not possible to mix left and right
function keys. Left Ctrl and Left ALT are the default settings.
Login required
Determines whether it is necessary to log into the receiver.
OSD Login Message
Text entered in this box will be displayed as a message on the OSD screen.
Enable Receiver OSD Alerts
Determine the required setting for pop up OSD alerts: No or Yes.
Show current channel
When enabled, displays the channel name on the OSD overlay.
Video Compatibility Check
This reads the EDID from the attached monitor and determines whether the monitor is
capable of displaying the selected video mode before connecting a channel. This prevents
the receiver showing a black screen and the user being locked out because a dual link
resolution has been selected to display on a single link monitor.
Force 60Hz
If enabled, the receiver frame rate is held at 60Hz regardless of the video input frame
rate. The Video Switching options (below) cannot be altered when this option is enabled.
Video switching
Provides two options for video switching:
Fast Switching (default state) - Retains the same frame rate (at either 50Hz or 60Hz)
depending upon which video resolution was displayed rst.
- Follows the source frame rate and will change the frame rate every Match Frame Rate
time this changes even if the video resolution doesn’t change. If you have one receiver
switching between 1920x1080@60Hz and 1920x1080@50Hz then this setting will
change the frame rate from 60Hz to 50 Hz every time that you switch.
Receiver Keyboard Country Code
Select the country code of the keyboard connected to the receiver.
Audio Input Type
Select the required audio input type.
USB Settings
HID only
If enabled, allows only HID (mice and keyboards) devices to be connected to the
receivers.
Disable Isochronous Endpoint Alerts
When an isochronous USB device is connected to the receiver there will no longer be a
warning message. ALIF units do not support isochronous devices.
Enable Isochronous Endpoint Attach
Some USB devices combine many USB devices behind a USB hub. e.g a keyboard with
audio support. By enabling this option, devices will be allowed to connect to ALIF
receivers, however, the isochronous part (e.g. the audio component) of the devices will
not work.
Advanced Port Features
This section allows you to determine USB port behaviour for use with certain USB
devices.
The default is no reserved ports, Merging enabled and no feature code (or Quirk) set.
It is recommended that these are left at the default settings and are only changed under
advice from an Adder FAE.
For each of the four USB ports on the receiver, certain rules can be applied depending
upon the USB device connected.
If you have reserved USB ports on the transmitter, you can select which USB port to use
for a particular device.
You can turn off USB merging for a particular port. This will slow down switching as the
USB device will be enumerated every time that you switch.
You can also enter an advanced feature if it is necessary for your USB device. The drop
down lists the feature codes for some known USB devices. Otherwise please contact
your local FAE for advice.
17
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Settings > Servers
This page is used to congure redundant operation for the A.I.M. servers.
Two or more servers can be added onto the same subnet or Vlan. One A.I.M. box is the
Primary (or Master) the other is the Backup (or Slave). If the Primary server fails for
any particular reason then the Backup will take over until the Primary is repaired. This
functionality is only possible if the licenses of the both A.I.M. units match. Both A.I.M.
units need to be able to control the same number of endpoints.
When in Multi-subnet mode it is possible to place additional servers on a different
subnet or Vlan. These servers are reffered to as satellites.
Primary Timeout
The time (in seconds) for the Primary server to be unavailable before the Backup takes
over.
Quiescent Timeout
The time after which an inactive (Quiescent) server is assumed to have disappeared.
Backup Check Interval
The interval between the Primary server querying its backups to determine if they are all
on-line.
Backup Timeout
The period of time that a backup server can be off line or uncontactable before it is
treated as a failed server.
Require Authentication
If set to Yes’, then a new, uncongured A.I.M. server will be unable to join the cluster
automatically; it’s behaviour will be to report itself as uncongured and quiescent, and
request a password. Entering the cluster password will then allow it to join the cluster as
a Backup.
Cluster Password
This is the password that is used for A.I.M.-to A.I.M. https queries, if the Require
Authentication option is enabled.
Dashboard > Settings > Network
This page applies global network parameters to the A.I.M. network.
A.I.M. Connectivity
Require SSL for Web
If set to yes, a certicate needs to be downloaded and all connections will then take
place using HTTPS:// connections rather than the default HTTP:// connection types.
Gateway IP Address
Denes the IP address of an optional gateway device.
Note: Only a single gateway can be specied within an A.I.M. server. If both Ethernet ports are
to be used in multi-subnet mode, it is important to specify a single gateway IP address that suits
both Ethernet ports. Communications between A.I.M. and the ALIF endpoints on the different
subnets will be affected if using multi-subnet mode without a jointly valid gateway.
Ethernet Port 1
The primary A.I.M. server Ethernet port can only be congured using a static IP address. Use
the three options provided to congure the IP address, netmask and DNS server address.
Ethernet Port 2
The Backup A.I.M. server Ethernet port can be congured to either: gain its details via a
DHCP server; use a Static IP address, netmask and DNS server address, or alternatively be
set to operation, whereupon three further Bonded Bonding Mode options are displayed:
Active-Backup - This can be used when both of the A.I.M. server’s network
connections are linked to the same network switch. This option provides a fail-over to
cater for the possibility of hardware failure or connectivity failure between the A.I.M.
server and the switch.
In this mode, one of the A.I.M. server’s network ports will be active while the other
remains dormant. If the active port experiences a failure, such as a loss of connection,
its conguration is automatically transferred to the Backup port. Once the original
primary port resumes connectivity, this will become the backup and be placed into a
dormant mode.
continued
18
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Broadcast - This option would be used when the twin ports of the A.I.M. server and
all attached ALIF devices are split between duplicate networks:
Device connectivity
IP Pool Lower/Upper Limits (not shown in multi-subnet mode)
When the A.I.M. server is used in single subnet mode, these two elds are used to dene
the range (pool) of IP addresses that the A.I.M. server can automatically assign to new
ALIF endpoint devices. The A.I.M. server contains its own DHCP server with which it
applies the available IP addresses to ALIF endpoint devices.
When used in multi-subnet mode, the internal DHCP server with the A.I.M. is disabled
and instead the A.I.M. server will rely upon an external DHCP server to provide valid IP
address details.
Multicasting
Multicast IP Base
The start address for the multicast IP addresses to be used. Multicast IP addresses are
in the range 237.1.1.1 to 239.255.255.255. This setting lets you adjust this range of IP
Multicast addresses. It is important to allow sufcient addresses for your system. For
instance, if the multicast IP address base was set to 239.255.255.252 there would only be
4 multicast addresses available.
Always Multicast
Determines whether multicast addressing is always used for video and audio streams.
This should be used for most installations as it provides the most efcient way to deliver
video and audio to multiple destinations.
IGMP Version
By default, force IGMPv2 is enabled. However, if your network supports IGMPv3 you can
take advantage of the IGMPv3 features by applying the force IGMPv3.
Interfaces
Device network port
This lets the admin specify which port on A.I.M. to use for ALIF control. This is either
ETH1 the default or Both ports if the A.I.M. has ETH1 and ETH2 connected to the ALIF
network.
Separate Device Networks
When this option is set to ‘Yes, the ALIF devices within the network will be instructed to
promote a further level of network resilience by treating their copper and ber/teaming
connections as independent links via separate switches (in conjunction with dual independent
cabling schemes) see the diagram on next page. If one connection route is compromised, the
other will continue unaffected. During normal operation, when both connection routes are
operating, transfer speeds are boosted by the copper and ber links working in parallel.
The two Ethernet ports of the A.I.M. server can be connected to the two separate
network switches to ensure that A.I.M. control remains in place if one network switch
should become unavailable.
The ‘Separate Device Networks’ option mentioned earlier would be enabled on the
A.I.M. server and the respective network connections on the endpoints are connected
accordingly (e.g. copper to copper on only switch 1 and SFP to SFP only on switch 2).
In Broadcast mode, both of the A.I.M. server network connections mirror each other,
i.e. duplicate network trafc is sent out on both connections. It is assumed that the
connected devices will only listen to the network trafc intended for themselves
and drop/ignore all other trafc intended for other devices. This mode is robust but
inefcient because half of the packets are discarded.
- This mode uses a similar topology to 802.3ad Active-Backup, (i.e. both network ports
connected to the same switch) but has two important differences: Both of the A.I.M.
server network ports are used simultaneously, and the network switch must support
LACP (Link Aggregation Control Protocol).
The A.I.M. server will ‘merge’ (aggregate) the two connections and treat them as
one. The only exception to this would be on ‘multi-Subnet racks’ where it would be
possible to have each network connection on different switches.
This mode provides the benet of increased bandwidth availability between the A.I.M.
server and the network, but also provides a layer of redundancy. If one of the network
connections is lost, the remaining connection would take over until the link is restored.
The network trafc is not split on a packet by packet basis between the connections;
it operates on a connection basis. When a connection is established between the A.I.M.
server and one of the ALIF endpoints, this would travel via one port. When a second
connection to another endpoint is established, this could use the same port or it may
use the other. There is no order to which network port is used for any connection.
Note: When changing between bonded and any other mode, a warning message will be
displayed and, when the Save button is clicked, will cause the A.I.M. server to be rebooted.
19
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Route of Last Resort
This option is appropriate when the A.I.M. server is used in multi-subnet mode. In such
cases, it is possible that the A.I.M. server is not directly connected to the same sub-
network as some or all of the ALIF endpoints. Therefore, it will be necessary for the
ALIF unit(s) to communicate back to the A.I.M. server via a gateway device (see Gateway
IP Address above). This option is used to indicate which interface has the gateway
congured.
Monitoring
Packet loss monitoring is available if Statistics are enabled on one or more of the
receivers being monitored (see
The Statistics Tab). You will need to set up an Simple
Network Management Protocol (SNMP) trap (see below) and/or declare a suitable email
account (see Dashboard > Settings > Mail) to receive notication when packet loss
drops below the chosen threshold/time frame:
Packet-Loss Alert Threshold
Determines when to issue a trap/alert based upon a threshold percentage of video
packets that have been dropped at the receiver.
Packet-Loss Alert Window
Determines the sampling period (in seconds) in determining the packet-loss threshold
(see above).
Syslog Enabled
Determines whether Syslog should be used to record log data to an external Syslog
server.
Syslog IP Address
The address of the external syslog server.
Note: Ensure that this is not set to the A.I.M.s IP adress as A.I.M. cannot log its own syslog
messages.
SNMP
This option allows the A.I.M. to connect to an external SNMP (Simple Network
Management Protocol) server. If SNMP is enabled, there are three connection modes:
Authentication + privacy
Authentication only
No authentication
There are two authentication types SHA or MD5 and two Privacy types AES or DES.
The MIB le can be downloaded from http://<IP>/AIM-MIB.txt
The response is split into three sections:
The rst reports status of each individual endpoint:
deviceIndex,
deviceType, (ALIF type i.e ALIF2002R)
deviceFirmware, (rmware revision)
deviceName,
deviceIdentier,
deviceIP1,
deviceMAC1,
deviceIP2,
deviceMAC2,
deviceSerialNum,
deviceStatus,
deviceLock,
deviceEth1Status,
deviceEth2Status,
The second part is returned from AIM:
numRx, (Number of RX units on system)
numTx, (number of Tx units on system)
numActiveConnexions,
serverCPULoad,
serverMemoryUsage,
serverSoftwareVersion,
serverDiskSpace,
The third part is the reporting of lost packets:
rxHead, (Which video head you are monitoring)
packetsSent,
packetsDropped
20
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Settings > Time
This page deals with all time related settings for the installation and allows up to three
external NTP servers to be dened.
NTP Enabled
Determines whether one or more external Network Time Protocol servers should be
used to provide timing for the installation.
Server 1/2/3 Address
Enter the IP address of the NTP server(s).
NTP Key Number(s)/NTP Key(s)
If you wish to use Symmetric key authentication for the server, enter an appropriate NTP
key number and key.
If you need to add more NTP servers, click the Set option next to the NTP Server 2 or
3 entries.
Time Zone Area and Time Zone Location
Use these entries to pinpoint the current location of the installation.
Dashboard > Settings > Active Directory
This page sets up the active directory server, if there is one on your network, and to use
active directory to maintain the user database.
Note: Active Directory groups with more than 1500 members will be downloaded as empty.
AD Enabled?
Determines whether Active Directory features will be used.
Account Sufx
Enter the account sufx for your domain.
Base DN
Specify the Distinguished Name for the top level of the directory service database base
that you wish to access.
Domain Controller
Enter the IP address or name of the server that holds the required directory service.
Username, Password
Enter the username and password for the domain account.
Sync Schedule
Choose the most appropriate synchronization schedule, from hourly intervals to daily or
weekly.
Dashboard > Settings > Mail
This page sets up the email functionality of the A.I.M. server if required. An external Email
server is required to sit on the network if this functionality is to be used.
Mail Enabled?
Determines whether the mail features of A.I.M. should be invoked.
SMTP Domain name/IP
Enter the name or IP address of the external SMTP server that will be used to process
all outgoing mail.
SMTP Port
Enter the appropriate port on the SMTP server.
Username, Password
Enter the appropriate username and password for access to the SMTP server.
Email Address for Alerts
Enter the email address to which alert messages should be sent.
From Address
Enter the email address that will be listed as the sender of alert messages.
Suppress Similar Alerts
Allows you to optionally dene a time period within which similar alerts to one already
received will be suppressed.
21
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Backup
You can schedule backup copies of the A.I.M. database (containing all devices, users,
channels and logs) to be made on a recurring basis and you can also perform backups on
demand, as required.
IMPORTANT: You are strongly recommended to arrange regular scheduled
backups of your A.I.M. database. Adder cannot be held responsible for any loss
of data, however caused.
Backup Options
Download to your computer: If this option is checked, when you click the “Backup
Now” button, the backup le will be saved to the server and then will be presented as a
download in your browser, so that you may save a local copy of the backup le.
Email backup: If this option is checked, a copy of the backup le will be sent to the
email address specied in the “Email Backup To” eld. The backup le will be emailed
either when you click “Backup Now” and/or according to the option selected in the
Schedule section.
Note: Use of the Email backup option requires a valid email address to be stored within the
Dashboard>Settings page.
Note: Emailed backups are encrypted, and these backup les are automatically decrypted by
the A.I.M. server when they are used.
Schedule: Determines how often a backup should be created. There are set periods for
the various options:
Hourly backups are executed on the hour (or quarter past).
Daily backups are executed at 2am (or quarter past).
Weekly backups are executed every Sunday at 3am (or quarter past).
Backups on the Server
All backups (whether initiated manually or by schedule) are saved on the server together
with a time-stamp of when the backup was run. If required, you can select a previous
backup and restore its contents. Alternatively, you can download the backup le to
another location.
IMPORTANT: It is advisable to make a backup of the current state of the A.I.M. system before
restoring a previous backup. Restoring the contents of a backup le will overwrite ALL data in
the A.I.M. system, with the data within the backup le. This includes congured devices, channels,
users, connection logs and action logs.
Downloaded Backups
Use this option to upload a backup le that you have previously downloaded or received
by email. This will overwrite the contents of the current A.I.M. system therefore it is
advisable to make a backup of the current state of the A.I.M. system before restoring a
previous backup.
Archive Log to CSV File
You can archive connection or log data to a CSV le and, at the same time, remove old
log data from the database.
Click “Archive” to save a CSV le to the server.
Download CSV Archive
You can download any CSV archive that was created in the archive step (described
above) by selecting from the archives saved on the server.
The CSV archive can be opened in Microsoft Excel (or similar) to perform detailed
analysis of actions and connections within the A.I.M. system.
Download Debug File
The purpose of the “Download Debug File” is to prove support with a copy of the
internal log les for diagnostics. The le is encrypted and can only be open by Adder.
22
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Updates
Upgrade A.I.M. Software
This option allows you to upgrade (or downgrade, if required) the A.I.M. server rmware
while preserving all conguration data. Firmware les are encrypted and digitally-signed
for A.I.M.-server integrity.
Please see Upgrading (or downgrading) A.I.M. rmware on the next page
Note: There is no longer any support for ALIF1000 units within A.I.M. rmware version 4.1
onwards.
Reset A.I.M. Conguration
This option can be used to reset A.I.M. to its initial conguration or a previous upgrade.
When the A.I.M. server is reset, all devices, channels, presets, users, groups and logs will
be removed. Note: You are recommended to take a backup onto an external device before
starting the upgrade process.
If one or more previous upgrades have been installed on this system, you will be given the
option to choose either the original factory image or the last upgrade image. They will be
listed by version number - click the appropriate radio button to select.
Two other options are available within this section:
Also reset the server IP address - When ticked, the IP address will be reset to the default:
169.254.1.3 and you will be reminded to manually navigate to that address.
Also delete security certicates and keys - When ticked, all certicates and keys held within
the server will be removed.
When the required options have been chosen, click the Reset A.I.M. Conguration
button to commence.
Upload New TX/RX Firmware
Allows you to upload a rmware le to the A.I.M. server, which can then be used to
upgrade ALIF TX and RX units.
Install Firmware onto Devices
Allows you to determine various upgrade settings and then commence the upgrade
process.
Please see Upgrading ALIF rmware globally >>
Upgrading ALIF rmware globally
This method allows the A.I.M. admin user to upgrade rmware on receivers and
transmitters, wherever they are located.
1 Use the “Upload New TX/RX Firmware” section to place new transmitter and/or
receiver rmware le(s) onto the A.I.M. server. Once uploaded, the stored rmware
les are listed within the relevant “Available rmware” drop-down boxes within the
sections below.
2 Within the “Install Firmware onto Devices” section, choose either the Device Type
(RX or TX) or Firmware Type (Main or Backup copies).
3 Click the Available rmware drop-down box and select the required new rmware
version.
Note: There is no longer any support for ALIF1000 units within A.I.M. rmware version 4.1
onwards.
4 Click the “Install” button to apply the chosen rmware to the devices.
5 On the right side of the list, you can:
Individually select the devices to which the rmware upgrade will be applied by
checking the “Upgrade” boxes next to each device, or
Use the “Upgrade All” option to apply rmware globally to all devices.
6 Click the “Upgrade Selected...” button to create a queue of devices to be upgraded. If
there are many devices to upgrade, this may take some time.
The status of devices during the upgrade process should be shown in near-real time
on the receivers/transmitters pages and on the device’s own page. The page will show
whether the device is still being upgraded or if it is in the process of rebooting with
the new rmware. Note that the process of applying rmware to a device and enacting
a reboot takes several minutes to complete.
23
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Upgrading (or downgrading) A.I.M. rmware
In certain circumstances it may be necessary to upgrade or downgrade the rmware of
an A.I.M. unit to take advantage of particular features. The Upgrade A.I.M. Software option
changes the rmware without affecting conguration data such as devices, channels,
presets, users, groups and logs.
Notes:
Although conguration details are not affected during the rmware upgrade process,
you are recommended to take a backup onto an external device before starting the
upgrade process.
When changing the A.I.M. rmware, it will be necessary to reboot the unit in order to
apply the changes.
There is no longer any support for ALIF1000 units within A.I.M. rmware version 4.1
onwards.
If you have any ALIF1000 endpoints and upgrade the A.I.M.rmware above version
4.0, you can use the ‘Replace Device’ feature in order to swap them for ALIF1002
endpoints.
It is not possible to downgrade from rmware version 4.4
If you have any ALIF1000 endpoints and you want to upgrade your A.I.M. system these
need to be swapped out for ALIF1002 endpoints. Ensure that your A.I.M. is running
4.0.40623. If your A.I.M. has a 4.0 version below this, it must be upgraded rst. Upgrade
your ALIF1000s to rmware version 3.7. Ensure the ALIF1002s are running 3.7. This is
essential to ensure that the replace device feature works.
It is not possible to downgrade ALIF endpoint rmware from below 4.4. The A.I.M. can
be downgraded to below 4.4
To upgrade/downgrade the A.I.M. unit rmware
Note: If there are any Backup or Satellite servers then these must be upgraded or downgraded
to be on the same software version before applying any ALIF rmware updates.
1 Download the appropriate rmware le from the Adder website or technical support.
2 Visit the Dashboard > Updates page of the A.I.M. unit and within the Upgrade A.I.M.
Software’ section, click the Browse... button to locate the downloaded rmware le.
3 When you are ready to proceed, click the Upload button. The le will be uploaded,
checked and applied to the secondary partition within the A.I.M. unit. A conrmation
message will be displayed and you will also be prompted to reboot the A.I.M. unit.
4 When it is appropriate to do so (dependent on the current activity of the A.I.M. unit),
click OK and then click the Reboot Now button. The A.I.M. unit will reboot using the
new rmware partition.
24
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Dashboard > Event Log
This page lists events that have occurred within the A.I.M. system. A drop-down list box
is available at the top of the page that allows you to lter log page entries to show only
particular categories, as follows:
All: Lists all events
: Lists automatic events and/or those performed by the admin user (including: Admin
backup, scheduled backup, backup restored, updating A.I.M. settings, adding/removing/
updating channels/users/devices, Active Directory Sync, Firmware upgrades, A.I.M.
upgrades, etc).
: Lists events performed by regular users (including: login, logout, channel Users
connections, disconnects, etc).
Login: Lists login and logout events, whether performed via the admin console or
receiver devices.
: Lists only channel changes (connections & disconnects).Channel Changes
Device Status: Lists new devices that are added to the A.I.M. network, get restarted/
rebooted or go online/ofine
You can archive Event Log data to a CSV le via the “Archive log data” link, which jumps
to the relevant section within the page.
Dashboard > Backups
Dashboard > Remote Support
The remote support feature grants a member of the technical support team remote
access to the A.I.M. unit. This page shows the current state of remote support, whether
currently enabled or disabled, plus a button to change the remote support state.
For further details, please see Enabling Remote Support.
Note: Before enabling remote support contact Adder technical support.
Dashboard > Active Connections
Shows only connections that are currently active within the A.I.M. network. Please refer
to the Connection Log page section below.
Dashboard > Connection Log
Shows all connections that have occurred within the A.I.M. network. The most recent
connections are shown at the top, and the log is paginated (the number of rows per
page can be set from the Dashboard > Settings page). The log can be ltered to show
all connections, or only currently active connections. Current connections have no “end
time” and a disconnect icon ( ).
The “Audio Broadcast IP” and “Video Broadcast IP” columns show whether the audio
and video are being sent directly from the transmitter to the receiver or broadcast to
a multicast group. Direct links are denoted by the receiver’s IP address only; whereas
multicast broadcasts are indicated by the multicast icon ( ) and the common multicast
IP address (the address will be in the range specied within the “Multicast IP Address
option of the Dashboard > Settings page).
Actions that you can take within this page include:
Hover the mouse over the receiver, user or channel names to show more information
about each item.
Hover the mouse over the ve “Info” icons to see descriptions (audio on/off; video on/
off; USB on/off; shared/exclusive mode; serial on/off).
Click to end a connection between a receiver and a channel.
25
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
ENABLING REMOTE SUPPORT
The AIM manager has a remote support feature that allows technical support to connect
should the need arise. It works by establishing a secure SSL connection with a managed
secure server hosted on the internet. Using a reverse tunnel, technical support can
connect to the manager via the secure server. Each support representative has their own
unique SSL keys for full traceability when making a remote connection. To protect the
manager against unauthorised access, Remote Support is disabled by default. Access is
only granted by Enabling Support and giving the support representative a unique one-
time password which is automatically generated each time it is enabled.
Below is a diagram that shows how the feature works:
The manager must be connected to a network which has internet access using
Ethernet Port 2.
On the manager, navigate to Dashboard -> Settings -> Network. You will need to
congure an IP address, gateway and DNS for Ethernet Port 2.
For managers running rmware versions 4.4 and below, the manager connects to the
remote server over port 22. You will need to ensure that outbound port 22 is not
blocked by the rewall or router to the internet. Managers running 4.5 and above, you
can choose other ports such as 80, 443, 53, 2222, 1022.
Navigate to the Dashboard -> Remote Support tab on the AIM admin Web UI and
click on the Enable Remote Support button.
NOTE: AIM rmware versions 4.0, 4.1 and 4.2 do not show the port number or
password when enabling Remote Support.
Note: There have been different versions of this Remote Support feature where the behaviour
varies slightly. We recommend that you have the latest rmware installed.
The AIM will show a port number and one-time password (OTP) which are required
to remotely access the manager.
If the port number changes after 1 minute, this means that either 1) The port is used
by another Remote session or 2) The manager has been unable to access the remote
server. If port number continues to change, please check your network and rewall
settings.
Please contact support@adder.com, stating the port number and one-time password
that you have been given. If you have changed the admin password from the default,
then please could you create a temporary administrator account so that we can access
the web interface if required.
26
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Web Interface Access
During the Remote Support session, we may need access to the AIM’s web interface. So
that you do not need to reveal or change your Admin password, please could you create
a temporary user and set it as an AIM Administrator. Please let us know the user and
password that you have created.
Troubleshooting
In the event that you do not see a port number when running AIM 4.3 and above then
check the following:-
You have outbound port enabled on your rewall, typically 22 or on 4.5 it can be 443,
53, 2222, 1022.
There is only one gateway on the AIM Manager, make sure that the gateway is correct.
If you set the Ethernet port 2 to DHCP, the gateway from the DHCP server is not
used.
Try manually assigning an IP address, subnet mask, gateway and DNS Setting to
Ethernet Port 2.
27
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Channels > View Channels
This page lists all channels that currently exist within the A.I.M. system. A channel is
automatically created for every transmitter when it is added and congured within the
A.I.M. network. The new default channel for each added transmitter will inherit the name
of the transmitter. Such default names can be altered at any time and additionally, you can
also create new channels manually, if necessary.
Within the list of channels, the Allowed Connections column indicates how each channel
may be accessed by users. By default, these settings are inherited from the global setting
(congurable within the page), however, each channel can be
Dashboard > Settings
altered as required. The icons denote the following connection rules:
Connection details inherited from the global setting
Video-Only
Shared
Exclusive
Private
The Channel Groups column shows to how many channel groups each channel belongs.
The Users column indicates how many users have permission to view each channel.
Actions that you can take within this page include:
Create a new channel: Click the “Add Channel” option.
Create a new channel group: Click the “Add Channel Group” option.
Congure an existing channel: Click for the required channel.
Clone an existing channel: Click to use the settings for the current channel as
the basis for a new channel entry.
Delete a channel: Click for the required channel.
: Click the “Turn Batch Delete Mode On” button, the Delete multiple channels
icons for all channels are replaced with tick boxes. Tick the boxes of the channels
that need to be deleted and then click the Delete selected channels” button which
appears at the bottom of the page. When you are nished, click the “Turn Batch Delete
Mode Off” button.
View a channel group: Click the “View Channel Groups” button.
THE CHANNELS TAB
The Channels tab provides access to all settings and options related directly to the video,
audio and USB streams, collectively known as channels, emanating from any number of
transmitters.
Click the CHANNELS tab to view the initial View Channels page.
The various other Channels pages (e.g. Add Channel, View Channel Groups, etc.) are
selectable within the blue section located just below the tabs.
Search lters
The key elds (Name, Description and Location) all provide a
search lter to locate particular items within long lists. Enter a full
or partial search string into the appropriate lter box and then
click to start the search. Optionally use the buttons to
invert the order of the listing.
The page will reload with the same pagination/sort order, but with the added search
lter. It’s possible to lter by several columns at once (e.g. search for all entries with
“mac” in the name, and “mixed” in the description). Search terms are case-insensitive. You
can re-sort and paginate on ltered results without losing the lters.
To remove a lter, click the red cross next to the relevant lter, (you can also empty the
search box and click again).
28
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Channels > Add or Congure a Channel
From the View Channels page, you can add a new channel or congure an existing
channel:
To create a new channel: Click the “Add Channel” option.
To congure an existing channel: Click for a channel.
The Add and Congure pages are similar in content.
Channel Name, Description and Location
These are all useful ways for you to identify the channel and its origins. A consistent
naming and description policy is particularly useful in large installations.
Video, Audio, USB and Serial
These drop down boxes list all of the available streams from installed transmitters. When
creating a channel, you can choose to take all four streams from the same transmitter or
from different ones, as required.
Notes: Where necessary, channels can be created without video, audio, USB and/or serial.
Only one receiver can use a transmitter’s serial port at any time.
Sensitive
This will mark the channel as sensitive within the OSD channels list.
Allowed Connection
This section allows you to dene the types of connection that you wish to permit users
to make. You can dene particular individual or combined connection types to suit
requirements.
Note: This setting for each channel acts as the nal arbiter of whether exclusive access can
actually be achieved. If you deny exclusive access rights within this setting, then exclusive access
for any user cannot take place for this channel, regardless of settings made elsewhere.
Inherit from global - uses the setting of the “Allowed Connection Modes” option
within the page.
Dashboard > Settings
Video-Only: Allows users only to view the video output, the USB channel is denied.
Shared: Allows users to control a system in conjunction with other users.
Exclusive: Grants exclusive control to one user while all others can simultaneously
view and hear, but not control, the output.
Private: Allows a user to gain private access to a system, while locking out all
others.
Group Membership
Groups provide a quick and easy way to manage settings for channels. By making a
channel part of a particular group, the channel automatically inherits the key settings of
that group.
The group membership section displays existing channel groups in the left list (to which
the current channel does not belong) and the channel groups in the right list to which it
does belong.
To add the channel to groups: Highlight one or more (use the CTRL key if selecting
more than one) group names in the left list and then click to add the name(s) to the
right list.
Note: You can also include or exclude individual channels by double clicking on them.
To add the channel to all groups: Click to move all group names from the left to
the right list.
To remove the channel from groups: Highlight one or more (use the CTRL key if
selecting more than one) group names in the right list and then click to move the
name(s) back to the left list.
To remove the channel from all groups: Click to move all group names from the
right to the left list.
Permissions
This section allows you to determine which users and user groups should be given
access to this channel. Individual users and user groups are handled within separate sub-
sections, but both use the same method for inclusion and exclusion.
To include one or more users (or groups): Highlight one or more (use the CTRL
key if selecting more than one) user/group names in the left list and then click to add
them to the right list.
To include all users (or groups): Click to move all user/group names from the left
to the right list.
To remove one or more users (or groups): Highlight one or more (use the CTRL
key if selecting more than one) user/group names in the right list and then click to
move them back to the left list.
To remove all users (or groups): Click to move all user/group names from the
right to the left list.
29
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Channels > Add or Congure Channel Group
Channel groups allow easy permission-granting for several channels at once. Permissions
can be set to determine which users can access channels within a channel group.
From the View Channels page, you can add a new channel group or congure an existing
channel group:
To create a new channel: Click the “Add Channel Group” option.
To congure an existing channel: Click “the View Channel Groups” option and then
click for a group.
The Add and Congure Channel Group pages are similar in content.
Channel Group Name and Description
These are all useful ways for you to identify the channel and its origins. A consistent
naming and description policy is particularly useful in large installations.
Group Membership
Allows you to determine which channels should be members of the group. By making
a channel part of the group, each channel automatically inherits the key settings of the
group.
To add a channel to the group: Highlight one or more (use the CTRL key if selecting
more than one) channel names in the left list and then click to add the name(s) to the
right list.
Note: You can also include or exclude individual channels by double clicking on them.
To add all channels to the group: Click to move all channel names from the left
to the right list.
To remove a channel from the group: Highlight one or more (use the CTRL key if
selecting more than one) channel names in the right list and then click to move the
name(s) back to the left list.
To remove all channels from the group: Click to move all channel names from
the right to the left list.
Permissions
This section allows you to determine which users and user groups should be given
access to channels within this group. Individual users and user groups are handled within
separate sub-sections, but both use the same method for inclusion and exclusion.
To include one or more users (or groups): Highlight one or more (use the CTRL
key if selecting more than one) user/group names in the left list and then click to add
them to the right list.
To include all users (or groups): Click to move all user/group names from the left
to the right list.
To remove one or more users (or groups): Highlight one or more (use the CTRL
key if selecting more than one) user/group names in the right list and then click to
move them back to the left list.
To remove all users (or groups): Click to move all user/group names from the
right to the left list.
30
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
THE RECEIVERS TAB
The Receivers tab shows a paginated table of all receiver devices within the A.I.M.
network.
Click the RECEIVERS tab to view the initial View Receivers page.
The other Receivers pages (e.g. View Receiver Groups, Add Receiver Group, etc.) are
selectable within the blue section located just below the tabs.
Receivers > View Receivers
The table shows the following information for each receiver:
Name Online status
IP address Firmware revision of receiver unit
Description & Location Manage (admin options - see below)
The Manage icons are as follows:
(Note: You can hover your mouse pointer over any icons to reveal additional information):
Congure device: Displays the Congure Receiver” page.
Reboot device: Allows you to reboot or reset a unit to its factory settings. A
popup will ask which task you wish to carry out. A reboot is useful if a device enters
an unknown state. A reset will return the unit to its factory default state and reset
its IP address (the unit will retain any rmware updates that have been applied).
Identify unit: Causes the LED lights to ash on the front of the selected unit. An
alert will be shown if the unit cannot be contacted (e.g. if it is ofine).
Delete device: Conrmation will be requested. You will need to factory-reset any
devices that you wish to re-congure to work with A.I.M..
: A list of available channels is shown, along with connection Connect to a channel
modes (Video-Only/Shared/Exclusive/Private). The admin user can thus remotely
change channel on any receiver.
Disconnect: If a receiver is currently connected to a channel, clicking the
disconnect icon will end the connection, regardless of who is connected. Hovering
over the icon will show which user is connected, which channel they are connected
to, and when the connection was created.
Search lters
The key elds (Name, Description and Location) all provide a
search lter to locate particular items within long lists. Enter a full
or partial search string into the appropriate lter box and then
click to start the search. Optionally use the buttons to
invert the order of the listing.
The page will reload with the same pagination/sort order, but with the added search
lter. It’s possible to lter by several columns at once (e.g. search for all entries with
“mac” in the name, and “mixed” in the description). Search terms are case-insensitive. You
can re-sort and paginate on ltered results without losing the lters.
To remove a lter, click the red cross next to the relevant lter, (you can also empty the
search box and click again).
31
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
Receivers > Congure Receiver
From the View Receivers page, you can congure details for a receiver:
Click for a receiver.
Note: If the IP address of the receiver is changed, the device will need to reboot itself.
Device ID / Type - Identity of the receiver.
Device Name, Description and Location
These are all useful ways for you to identify the receiver and its origins. A consistent
naming and description policy is particularly useful in large installations.
Main/Backup Firmware - The current rmware versions contained within the unit.
Online? - Current status.
MAC Address / 2 - Lists the xed network identiers for the single or double ports.
IP Address / 2 - Lists the single or dual IP addresses for the unit. If the DHCP options
are ticked then the elds will be grayed out.
Allow Local Feed through - When selected, allows the receiver to connect directly to
a local source. The receiver must have a free interface, i.e. no IP address.
Login Required
: When selected, anyone can use a receiver terminal and connect to a channel. The No
channels/permissions displayed to this anonymous user are those that are set for the
“anonymous user” that is dened within the Dashboard > Settings page.
Inherit from Receiver Groups: When selected, the requirement for user login will
be determined by the “Login Required” settings within the Receiver Groups to which
this unit belongs:
If ANY of the receiver groups (to which this receiver belongs) are set as “Login
Required = Yes”, this receiver will require login.
If ANY of the receiver groups (to which this receiver belongs) are set as “Login
Required = Inherit...” and the global setting is “login required = yes”, then this
receiver will require login.
If ALL receiver groups (to which this receiver belongs) are set as “Login Required =
No”, then this receiver will NOT require login.
: When selected, a user will need to login with the username and password dened Yes
in the “Users” section. They will only be allowed to login if they have been granted
permission to access that particular receiver.
Receiver OSD Alerts
Determine the required setting for pop up OSD alerts: Inherit, No or Yes.
Show Current Channel
When selected, shows the currently connected channel as an overlay.
Keyboard Country
Select the country code of the keyboard connected to the receiver.
Audio Input Type
Select the required audio input type.
USB settings - see next page for details.
Video Compatibility Check
This reads the EDID from the attached monitor and determines whether the monitor is
capable of displaying the selected video mode before connecting a channel. This prevents
the receiver showing a black screen and the user being locked out because a dual link
resolution has been selected to display on a single link monitor.
Force 60Hz
If enabled, the receiver frame rate is held at 60Hz regardless of the video input frame
rate. The Video Switching options (below) cannot be altered when this option is enabled.
Video switching
Provides two options for video switching:
Fast Switching (default state) - Retains the same frame rate (at either 50Hz or 60Hz)
depending upon which video resolution was displayed rst.
- Follows the source frame rate and will change the frame rate every Match Frame Rate
time this changes even if the video resolution doesn’t change. If you have one receiver
switching between 1920x1080@60Hz and 1920x1080@50Hz then this setting will
change the frame rate from 60Hz to 50 Hz every time that you switch.
Group Membership
To facilitate collective permission-granting for numerous receivers, a receiver can
belong to one or more receiver groups. Any permissions applied to the receiver group
are inherited by all receivers that are included within the receiver group. For example,
multiple receivers can be made available to a user by placing them all in a receiver group
and then granting the user permission to use that receiver group.
Permissions
This is hidden by default as, by default, all users have access to all receivers. You can deny
access to particular receivers for a user in this section. However, be aware that users
who are included within user groups may have access to the same receivers via their
groups.

Termékspecifikációk

Márka: Adder
Kategória: nincs kategorizálva
Modell: Link Infinity Manager

Szüksége van segítségre?

Ha segítségre van szüksége Adder Link Infinity Manager, tegyen fel kérdést alább, és más felhasználók válaszolnak Önnek




Útmutatók nincs kategorizálva Adder

Útmutatók nincs kategorizálva

Legújabb útmutatók nincs kategorizálva

MOZA

MOZA SR-P Útmutató

10 Április 2025
CaterChef

CaterChef 445001 Útmutató

9 Április 2025
IFM

IFM E40581 Útmutató

9 Április 2025
Livn

Livn Bolt Útmutató

9 Április 2025
Livn

Livn Beats Útmutató

9 Április 2025
IFM

IFM O3R252 Útmutató

9 Április 2025