When setting up an Infinity digital matrix for the first time, if you connect a Transmitter or Receiver to a simple single VLAN network and find that the AIM Manager is not automatically recognising them, then check the following:-
- The AIM Manager can be set in two modes, either single or multi-subnet mode. This option is only available when you configure its network settings for the first time, and is called Subnet Operation which can either be set as On or Off.
- With Subnet Operation Off, the AIM Manager will not act as a DHCP Server, which means the endpoints (Transmitters and Receivers) will not be issued with IP addresses and therefore will not find the AIM Manager. Unless you have an external DHCP configured on the network that both offers the endpoints their IP address settings and DHCP Option 125.
- With Subnet Operation On, the AIM Manager will run a DHCP Server and will provide the network configuration to the endpoints,
- To determine which mode the AIM is running, navigate to Dashboard -> Settings -> Network. Scroll down the Network settings and look for IP Pool Lower and IP Pool Upper fields. If these are missing then the Subnet Operation mode is set to On and an external DHCP server is required.
- To change the Subnet Operation mode, you must perform a Full Factory Reset.
- Check your switch configuration. Make sure that you have portfast enabled, If you are using Cisco switches, make sure that on each port where an Infinity endpoint resides has switchport mode access and spanning-tree portfast set.
Assuming that you are not going over the limit of your AIM's endpoint license and that the AIM is set in single subnet mode, then check the following:-
- Navigate to Dashboard -> Settings -> Network
- Scroll down the Network Settings page and look for IP Pool Lower and IP Pool Upper fields.
- Make sure that the IP range that has been set is sufficient to accommodate the number of endpoints you require.
A new or factory reset AIM Manager has a fixed link-local IP address of 169.254.1.3. When you configure the AIM's IP address, it will no longer be available on default link-local address. However, if you forget the IP address that you set, it is still possible to access a Primary AIM on link-local address 169.254.1.2 instead. A backup AIM's IP link-local IP address will be available between 169.254.1.4 and 169.254.1.10, depending on how many you have on the network.
An acting Primary AIM server is a Backup or Satellite AIM that has taken over control in the absence of a Primary AIM.
- Allow endpoints to still make channel changes.
- Issue DHCP addresses (single-subnet mode only)
It can not:
- Make changes to the configuration, such as add or edit channels.
- Accept new or factory reset endpoints
In the event of a Primary AIM failure, the Backup AIM can be promoted to a Primary AIM Manager.
The flashing indicates that the unit is running in Backup mode which is used to recover the product if there is a problem. This can be for a couple of reasons:-
- On the back of the unit is a dip switch that is located next to the power socket. If dip switch 1 is ON (down) then this starts the unit in Backup mode. Simply set dip switch to OFF and re-power the endpoint to boot normally.
- The boot strap loader has detected that the main firmware is corrupt. Reloading the firmware should resolve the problem. See Upgrading the Firmware directly for instructions. If you are running firmware older than 3.7 or 4.4 then please read the Longevity Upgrade page.
A common mistake when setting up Channels is to include the serial port when it is not necessary. A serial connection can only operate in a point to point mode due to the limitation of the serial protocol. This means that once someone has established the channel, subsequent connections can only be view-only.
When I try to change Channel, I receive a message saying that the receiver is in use by another user.
Only the person who established the channel connection on a receiver is able to change it. However, this can be overridden by the Administrator either by logging into the receiver, using this AIM web interface or using the API. This message typically appears if the OSD login has timed out and a different user logs into the OSD and proceeds to use it whilst the receiver is already connected to a channel.
To avoid this problem, either make sure that you disconnect the channel before leaving the receiver or set the timeout period on the OSD to a longer duration.
On the first of the month, the AIM automatically archives any Event and Connections logs that are older than a month. Those log are accessible on the Backup page (Dashboard -> Backups).
When a transmitter is added to the AIM, the AIM issues the multicast addresses starting from the custom multicast base address in the network settings. The default multicast based address is 188.8.131.52. The base address can be changed under the Dashboard -> Settings -> Network page and Multicast IP Base.
There are a couple of reasons why this may be occurring. 1) The video cable is faulty 2) The graphics card is outputting YCBr instead of RGB.