Black Box ACR1000A-CTL-192, ACR1000A-CTL-ULT, ACR1000A-CTL-288, ACR1000A-CTL-96, ACR1000A-CTL-48 User Manual
USER GUIDE
ACR1000A-CTL-24 ACR1000A-CTL-48 ACR1000A-CTL-96
ACR1000A-CTL-192 ACR1000A-CTL-288 ACR1000A-CTL-ULT
™
iPATH
AGILITY
CONTROLLER
24/7 TECHNICAL SUPPORT AT 1.877.877.2269 OR VISIT BLACKBOX.COM
TRADEMARKS USED IN THIS MANUAL
Black Box and the Double Diamond logo are registered trademarks of BB Technologies, Inc.
Any other trademarks mentioned in this manual are acknowledged to be the property of the trademark owners.
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
We‘re here to help! If you have any questions about your application
or our products, contact Black Box Tech Support at 877-87 7-2269
or go to blackbox.com and click on “Talk to Black Box.”
You’ll be live with one of our technical experts in less than 60 seconds.
2
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
FEDERAL COMMUNICATIONS COMMISSION AND INDUSTRY CANADA RADIO FREQUENCY INTERFERENCE
STATEMENTS
This equipment generates, uses, and can radiate radio-frequency energy, and if not installed and used properly, that is, in strict
accordance with the manufacturer’s instructions, may cause inter ference to radio communication. It has been tested and
found to comply with the limits for a Class A computing device in accordance with the specifications in Subpart B of Part 15 of
FCC rules, which are designed to provide reasonable protection against such interference when the equipment is operated in a
commercial environment. Operation of this equipment in a residential area is likely to cause interference, in which case the user
at his own expense will be required to take whatever measures may be necessary to correct the interference.
Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to
operate the equipment.
This digital apparatus does not exceed the Class A limits for radio noise emis sion from digital apparatus set out in the Radio
Interference Regulation of Industry Canada.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques
de la classe A prescrites dans le Règlement sur le brouillage radioélectrique publié par Industrie Canada.
Disclaimer:
Black Box Network Services shall not be liable for damages of any kind, including, but not limited to, punitive, consequential or
cost of cover damages, resulting from any errors in the product information or specifications set forth in this document and Black
Box Network Services may revise this document at any time without notice.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
3
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
INSTRUCCIONES DE SEGURIDAD
(NORMAS OFICIALES MEXICANAS ELECTRICAL SAFETY STATEMENT)
1. Todas las instrucciones de seguridad y operación deberán ser leídas antes de que el aparato eléctrico sea operado.
2. Las instrucciones de seguridad y operación deberán ser guardadas para referencia futura.
3. Todas las advertencias en el aparato eléctrico y en sus instrucciones de operación deben ser respetadas.
4. Todas las instrucciones de operación y uso deben ser seguidas.
5. El aparato eléctrico no deberá ser usado cerca del agua—por ejemplo, cerca de la tina de baño, lavabo, sótano mojado o cerca
de una alberca, etc.
6. El aparato eléctrico debe ser usado únicamente con carritos o pedestales que sean recomendados por el fabricante.
7. El aparato eléctrico debe ser montado a la pared o al techo sólo como sea recomendado por el fabricante.
8. Servicio—El usuario no debe intentar dar servicio al equipo eléctrico más allá a lo descrito en las instrucciones de operación.
Todo otro servicio deberá ser referido a personal de servicio calificado.
9. El aparato eléctrico debe ser situado de tal manera que su posición no interfiera su uso. La colocación del aparato eléctrico
sobre una cama, sofá, alfombra o superficie similar puede bloquea la ventilación, no se debe colocar en libreros o gabinetes
que impidan el flujo de aire por los orificios de ventilación.
10. El equipo eléctrico deber ser situado fuera del alcance de fuentes de calor como radiadores, registros de calor, estufas u otros
aparatos (incluyendo amplificadores) que producen calor.
11. El aparato eléctrico deberá ser connectado a una fuente de poder sólo del tipo descrito en el instructivo de operación, o como
se indique en el aparato.
12. Precaución debe ser tomada de tal manera que la tierra fisica y la polarización del equipo no sea eliminada.
13. Los cables de la fuente de poder deben ser guiados de tal manera que no sean pisados ni pellizcados por objetos colocados
sobre o contra ellos, poniendo particular atención a los contactos y receptáculos donde salen del aparato.
14. El equipo eléctrico debe ser limpiado únicamente de acuerdo a las recomendaciones del fabricante.
15. En caso de existir, una antena externa deberá ser localizada lejos de las lineas de energia.
16. El cable de corriente deberá ser desconectado del cuando el equipo no sea usado por un largo periodo de tiempo.
17. Cuidado debe ser tomado de tal manera que objectos liquidos no sean derramados sobre la cubierta u orificios de ventilación.
18. Servicio por personal calificado deberá ser provisto cuando:
A: El cable de poder o el contacto ha sido dañado; u
B: Objectos han caído o líquido ha sido derramado dentro del aparato; o
C: El aparato ha sido expuesto a la lluvia; o
D: El aparato parece no operar normalmente o muestra un cambio en su desempeño; o
E: El aparato ha sido tirado o su cubierta ha sido dañada.
4
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
CONTENTS
TECHNICAL
SUPPORT
1.877.877.2269
CONTENTS ................................................................................................................................. 5
CHAPTER 1: SPECIFICATIONS ..................................................................................................... 6
CHAPTER 2: WELCOME .............................................................................................................. 7
2.1 Local feed through ................................................................................................................................................................................9
2.2 iPATH basics ....................................................................................................................................................................................... 10
CHAPTER 3: INSTALLATION ..................................................................................................... 12
3.1 Connections ........................................................................................................................................................................................ 12
3.2 Installation requirements .................................................................................................................................................................. 14
3.3 Mounting the iPATH server ................................................................................................................................................................ 15
CHAPTER 4: CONFIGURATION .................................................................................................. 16
4.1 Supported browsers ........................................................................................................................................................................... 16
4.2 Login for admin users ........................................................................................................................................................................ 16
4.3 Important first configuration steps .................................................................................................................................................. 17
4.4 Adding Agility units ........................................................................................................................................................................... 18
4.5 The Dashboard tab ............................................................................................................................................................................. 19
4.6 Enabling Remote Support ..................................................................................................................................................................37
4.7 The Channels tab ................................................................................................................................................................................ 39
4.8 The Remotes tab ................................................................................................................................................................................43
4.9 The Locals tab ....................................................................................................................................................................................48
4.10 The Servers tab ................................................................................................................................................................................. 51
4.11 The Users tab .................................................................................................................................................................................... 52
4.12 The Presets tab ................................................................................................................................................................................. 56
4.13 The Statistics tab ..............................................................................................................................................................................59
CHAPTER 5: OPERATION ..........................................................................................................60
5.1 Logging in ............................................................................................................................................................................................60
5.2 Hotkey shortcuts ................................................................................................................................................................................ 61
5.3 The Local OSD screen ........................................................................................................................................................................ 62
5.4 Using the Remote OSD feature .......................................................................................................................................................... 63
APPENDIX A - TIPS FOR SUCCESS WHEN NETWORKING AGILITY ............................................ 65
APPENDIX B - TROUBLESHOOTING .......................................................................................... 68
APPENDIX C - REDUNDANT SERVERS ...................................................................................... 70
APPENDIX D - UPGRADE LICENCE ............................................................................................ 73
APPENDIX E - GLOSSARY ......................................................................................................... 74
APPENDIX F - iPATH API ........................................................................................................... 78
APPENDIX G - DHCP SERVER REQUIREMENTS ......................................................................... 96
APPENDIX H - USING DHCP OPTION 125 .................................................................................. 98
APPENDIX I - SAFETY INFORMATION ..................................................................................... 100
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
5
CHAPTER 1: SPECIFICATIONS
HARDWARE
Industrial specication server with solid state memory
SOFTWARE
Closed system with bespoke application preloaded
PHYSICAL DESIGN
1U short-depth (230mm) server
WxHxD: 16.93” x 1.75” x 9.05”
430mm x 44.5mm x 230mm
Weight: 5.95 lbs
2.7kg
POWER
Input rating of server: 12VDC 2.0A
POWER ADAPTER
Input: 100-240VAC 50/60Hz 1.5A
Output: 12VDC 5.0A
Connector: IEC input
Manufacturer: Stontronics model DSA-60PFB-12 1 120500 part number T5386DV
IMPORTANT: A defective power adapter MUST only be replaced with the correct unit from Black Box.
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
PERMITTED OPERATIONAL AMBIENT CONDITIONS
Operating temperature: 0 to 40ºC / 32 to 104ºF
Relative Humidity: 10-90% non-condensing
Permitted Altitude: <2000m
Approvals: CE, FCC
6
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
CHAPTER 2: WELCOME
TECHNICAL
SUPPORT
1.877.877.2269
Agility local and remote units allow multiple remote users to access host computers in a very flexible manner. Such flexibility
requires management and coordination – that is where iPATH becomes vital.
iPATH is designed to promote the most efficient use of Agility units by allowing central control over any number of locals and
remotes. Using the intuitive iPATH web-based interface, one or more administrators can manage potentially thousands of users
who are interacting with an almost unlimited number of devices.
iPATH operates as a self-contained compact server (including its own DHCP server) unit that can be situated anywhere within
your network of Agility devices:
The iPATH server connects to your network and provides administrative control over the various Agility locals,
remotes and their users.
Note: Although the Agility units require Gigabit Ethernet connections, in its administrative role, the iPATH server
requires only a 10/100Mbps connection to the network.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
7
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
The iPATH server is supplied pre-loaded and is straightforward to deploy, requiring only a network connection and a power input
to begin operation.
All configuration of your Agility locals (channels), remotes and users are performed using the intuitive iPATH browser interface
via a network connected computer.
1
AgilityHigh-PerformanceKVM
CONTROLLERiPATH
O
Green indicator:
Power
The iPATH server front panel
The iPATH server rear panel.
In normal use only the network and power connectors are used (ringed in red).
Red indicator:
Drive activity
8
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
ADMIN
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
2.1 LOCAL FEED THROUGH
Agility remotes which are equipped with dual IP network ports can be configured 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 configure 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 iPATH server must be at version 4.8 or greater while the endpoints must be
at version 4.6 or greater.
1
AgilityHigh-PerformanceKVM
CONTROLLERiPATH
Gigabit
Ethernet
O
In operation, the user of the console at the Agility
remote can use the following hotkey combination
to toggle between the network and local links:
To change from a network link to the local link:
enter CTRL+ALT+L
To change from the local link to a network link:
enter CTRL+ALT +C
to display the OSD and choose the required
connection.
Note: The L and C default hotkeys can be changed
within the iPATH control panel.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
9
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
2.2 iPATH BASICS
CHANNELS
Think of a channel as a ‘virtual local unit’. It is virtual because the video, audio and USB streams of a channel do not necessarily
have to originate from the same physical local 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 configured for the same host computer, each with different access rights to suit particular situations.
2.2.1 GROUPS
In order to accommodate potentially large numbers of users and devices, iPATH uses a system of groups: User Groups, Remote
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 benefit 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.
2.2.2 USER TYPES
This guide refers to the two main categories of users involved with the iPATH system:
• An Admin (administrator) user accesses the iPATH system via a network-linked computer running an Internet browser. Once
the necessary username and password have been entered, Admin users can make changes to the operation of the iPATH
system.
• A Regular user has a keyboard, video monitor and mouse (plus speakers where appropriate) attached to an Agility remote
unit and can access one or more computers that are linked to Agility locals. The Agility remote provides an On-Screen Display
(OSD) that lists all accessible computers and allows easy access to them.
2.2.3 SECURITY
Security considerations form a major part of iPATH operation, ensuring that users have rapid access only to the systems for
which they have permission. At its core, iPATH manages an important three-way relationship between the users, the Agility
remote(s) and the channels from the host computers.
The diagram shows a representation of the three-way relationship which exists between users, remotes and channels.
User
Access
permitted
by default
Access
denied by
default
iPATH
Remote Channel
Access always permitted
10
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
To successfully gain access to a channel:
• The user requires permission to use the remote,
• The remote 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, iPATH grants open access for the user to the remote and the remote to the channel while restricting the final,
most crucial piece of the puzzle. For those who require it, the lock upon the user to remote stage can be applied individually or
globally.
See Permissions below for more details.
2.2.4 ACTIVE DIRECTORY
To streamline administration even further, iPATH 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 configuration as well as streamline ongoing updates.
2.2.5 IPATH INTERFACE
iPATH appears in two main ways depending on whether you are an administrator or a regular user.
• For administrators, full access to the iPATH Suite is granted. This comprehensive application shows nine main tabbed areas:
Dashboard, Channels, Remotes, Locals, Servers, Users, Presets and Statistics, 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 firmware of any linked Agility unit.
• For regular users, an efficient page layout provides a list of all channels for which you have permission to visit. Against each
selectable channel name and description, a series of icons provide clear feedback about current availability.
2.2.6 PERMISSIONS
Permissions exist between Users, Remotes, and Channels.
By default, all users are granted permission to access ALL remotes.
By default, all remotes 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 remote can be applied in any of the following ways:
• User à Remote
• User à User Group à Remote
• User à User Group à Remote Group à Remote
• User à Remote Group à Remote
Thus, a very indirect way of granting permissions could be:
• User1 is in UserGroup1,
• UserGroup1 has access to RemoteGroup1,
• RemoteGroup1 contains Channel1,
• Therefore, User1 has access to Channel1 indirectly.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
11
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
CHAPTER 3: INSTALLATION
TECHNICAL
SUPPORT
1.877.877.2269
3.1 CONNECTIONS
The iPATH server unit is supplied fully pre-loaded and permits no local user interaction. All configuration takes place remotely via
the network connections and as a result only two connections are required: Network and power.
Note: If an existing iPATH server must be replaced, follow the important advice given within Appendix C (Swapping out an iPATH
server).
Note: The iPATH 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 configuration takes place across the network connection.
3.1.1 NETWORK CONNECTIONS
The iPATH server has two network connections on the rear panel: port 1 on the left and port 2 on the right. These allow the unit
to be connected to internal and external 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 configured 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 iPATH server unit.
2 Connect the plug of the link cable to the left IP port (1) on the rear panel of the iPATH server unit.
Category 5e or 6 cable from
LAN / network switch
Note: The precise operation of the two ports are determined within the iPATH server Management Suite, particularly the
Dashboard > Settings > Network page.
12
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
3.1.2 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.
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 iPATH server unit, click the power switch on the front panel. Allow 3 minutes for the booting process to complete.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
13
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
3.2 INSTALLATION REQUIREMENTS
• The minimum permissible firmware versions for Agility units linked with the iPATH server depend upon the firmware version
that is running on the iPATH server itself.
Note: iPATH servers with firmware v4.1 or above no longer support the original Agility model.
• iPATH server: v4.0 is intended for use with Agility endpoints at v3.7
• iPATH server: v4.1 is intended for use with Agility endpoints at v4.1
• iPATH server: v4.2 is intended for use with Agility endpoints at v4.2
• iPATH server: v4.3 is intended for use with Agility endpoints at v4.3
• iPATH server: v4.4 is intended for use with Agility endpoints at v4.3 or v4.4*
• iPATH server: v4.5 is intended for use with Agility endpoints at v4.5
• iPATH server: v4.6 is intended for use with Agility endpoints at v4.5 or v4.6
• iPATH server: v4.7 is intended for use with Agility endpoints at v4.5 or v4.6
• iPATH server: v4.8 is intended for use with Agility endpoints at v4.5 to v4.8
* Due to the changes made to Agility 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 iPATH 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 flash and v4.3 uses 1-bit ECC flash.
§
To upgrade to v4.5 endpoint code, it is necessary to first 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 Agility to iPATH 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
iPATH unit is connected. Where portfast is not enabled, if a second iPATH is added for redundancy, this could result in a misconfigured Backup server.
• If an existing iPATH server must be replaced, follow the important advice given within Appendix C (Swapping out an iPATH
server).
• When configuring 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 Agility.
§
14
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
3.3 MOUNTING THE IPATH SERVER
The iPATH 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 IPATH SERVER WITHIN A RACK MOUNT
1 Slide the iPATH 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:
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
15
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
CHAPTER 4: CONFIGURATION
This section covers configuration of the iPATH Suite for administrators. For details about the regular user interface, please see the
Operation section.
TECHNICAL
SUPPORT
1.877.877.2269
4.1 SUPPORTED BROWSERS
The iPATH 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.
4.2 LOGIN FOR ADMIN USERS
1 Ensure that the iPATH 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 iPATH server: 169.254.1.3
The Login page will be displayed:
*
Username
*
Password
™
MANAGER
Login
ServSwitchiPATH
BLACK
BOXIPACCESS
Login
Remember Me
3 Enter your Username and Password and click the Login button.
The default username is admin and the default password is password.
You are strongly recommended to change the default admin password as one of your first actions: Go to Dashboard>Users.
Click on the furthest right icon in the admin row (configure 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 iPATH 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 Important first configuration steps on the next page.
4.2.1 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 Black Box support or your distributor to obtain an unlock code which can then be entered to reset your password and
gain access.
16
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.3 IMPORTANT FIRST CONFIGURATION STEPS
There are several important configuration steps that must be carried out when starting a new iPATH server for the first time.
4.3.1 TO DETERMINE THE IPATH SERVER’S ROLE AND MAIN IP ADDRESS
1 Switch on and log in to the iPATH server; you will be presented with the Servers page.
2 Within the Server page, choose the Role of this new iPATH server:
• Solo - This will be the only iPATH server on the network (with no redundancy and failover), or
• Primary - This server will be used as part of a redundant cluster of iPATH servers, where it will be the main server used to
manage the Agility 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 Ethernet Port 1 section at the
top of the page, change the default iPATH IP Address (and Netmask) options to settings that suit your network configuration
and which will be used henceforth for this server.
IMPORTANT: The Ethernet Port 1 iPATH 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 Black Box 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 Agility 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 iPATH server.
Note: Ensure that your computer can view the new IP address, otherwise the iPATH server will appear to be offline. Depending
on your network configuration and that of the computer, you may need to change the computer’s configuration to be able to see
iPATH server’s new network address.
IMPORTANT: To use subnet operation, you must have a DHCP server within your network in order to assign IP addresses to the
iPATH and Agility endpoints. If subnet operation is used without a DHCP server, the Agility endpoints will not communicate
with iPATH As a result, the iPATH will need a factory reset in order to be able to revert it back to single subnet mode.
4.3.2 TO CHOOSE HOW IP ADDRESSES ARE APPLIED TO AGILITY DEVICES
1 Login again to the iPATH 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 iPATH server will operate as per the Off setting described below.
When the Subnet Operation option is present, you have the following choices:
• Off - iPATH can administer a single subnet and will use its own DHCP (Dynamic Host Configuration Protocol) server to
automatically assign IP addresses to new Agility devices, drawing upon a pool of spare addresses defined by you.
• On - iPATH can administer devices across multiple subnets, but will rely upon an external DHCP server to assign valid IP
addresses to new Agility devices.
3 If you chose the Off setting, you now need to define the boundaries of the IP address pool that will be used by the internal
DHCP server. Enter valid start and end addresses to the IP Pool Lower Limit and IP Pool Upper Limit 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 Save button.
5 If you need to change the operation of iPATH from single subnet to multi-subnet (or back again) this option only appears after
a successful factory reset of iPATH
IMPORTANT
Note: If an existing iPATH server must be replaced, follow the important advice given within Appendix C (Swapping out an iPATH server).
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
17
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.4 ADDING AGILITY UNITS
When new Agility locals and remotes are added to a network, they are designed to automatically announce themselves* to the
iPATH server. Once the iPATH server receives their announcement(s), the Agility units will be added to the administrator’s view of
the Dashboard. From here you can then begin to configure each new Agility unit.
* Agility units can be configured either from their own browser-based configuration utility or via the iPATH server. Once an Agility
unit has been configured in one way, it cannot be reconfigured using the other method without undergoing a factory reset. This
policy is in place to help prevent accidental overwriting of configurations. It also means that once an Agility unit has been locally
configured, it will not announce itself to the iPATH server upon being added to a network. Please see below for details about
resetting an Agility unit.
When new Agility devices announce themselves, depending upon how it was initially configured (see Important first configuration
steps), the iPATH server will either assign IP addresses to new Agility units automatically, or will rely upon an external DHCP
server to do the same. Either way, providing each Agility device is not already configured and announces itself to the iPATH 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 Agility units have been added, you can use the iPATH server Dashboard to select and
further configure any or all of them.
4.4.1 IF AN AGILITY UNIT IS NOT LOCATED
There are several reasons why an Agility unit might not be located by iPATH:
• The Agility unit has been locally configured or is otherwise not using its factory default setting. Try performing a factory reset
on an Agility that is not being located.
• The Agility unit is not located in the same Ethernet segment as the iPATH 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 Agility and iPATH units. Check and where necessary, replace faulty cables.
4.4.2 AGILITY MANUAL FACTORY RESET
Where a previously configured Agility unit is being added to a network for control by an iPATH server, you can use this method to
reset the unit to its default configuration.
TO PERFORM A MANUAL FACTORY RESET
1 Remove power from the Agility 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,
five of the front panel indicators will flash for a period of three seconds
to indicate a successful reset operation.
Note: For Agility Zero U models, please refer to the Agility Zero U manual
for details about performing a manual factory reset.
Agility
18
Use a straightened-out paper
clip to press the reset button
while powering on the unit
Agility Dual or
Agility Dual VNC
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5 THE DASHBOARD TAB
The Dashboard is your main point of contact for checking and changing the general status of all iPATH 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.
4.5.1 DASHBOARD > HOME
• Shutdown button - Allows the admin user to shut down the iPATH server. The OSD will no longer work on Remotes. The iPATH
server will need to be manually started again when next required.
• Restart - The admin user can reboot the iPATH server. The OSD and admin section will be unavailable while the server is
rebooting. The time for a reboot can vary significantly 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 offline, rebooting, recently added or
unconfigured.
• Latest Active Connections - shows the five most recent active sessions, detailing for each: When the session started; which
user/remote/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 iPATH system. See also the Event Log page.
• Latest Channels Created - shows the last five channels created within the iPATH system. A channel is created by default when
a new local is added and configured. The edit icon next to a channel allows the admin user to configure the channel.
• Latest OSD Logins - shows the last five users who logged in (either to the iPATH admin or at an Agility Remote).
• Latest User Registrations - shows the last five users added to the iPATH system, with a link to edit the user’s details/
permissions.
• Latest Channel Changes - shows the last five users who changed a channel, either while using the on-screen display (OSD) at
an Agility Remote, or via the iPATH admin control panel.
• Latest Remotes Added - shows the last five remotes to be added and configured within the iPATH network. Click to
configure a remote; click to connect to a channel; or click to disconnect an existing connection.
• Latest Locals Added - shows the last five locals to be added and configured within the iPATH network. Click to configure a
local.
* The Home page is auto-refreshed every thirty seconds to ensure that the latest information is always available.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
19
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5.2 DASHBOARD > SETTINGS
Click the Settings option below the Dashboard tab.
The Settings section contains global configuration options for the iPATH system and is divided into eight pages, each accessible
by clicking the relevant button located below the blue options bar:
General • Locals • Remotes • Servers • Network • Time • Mail • Active Directory
For configuration options that affect individual remotes, users channels, etc., see the sections dealing with those tabs.
4.5.3 DASHBOARD > SETTINGS > GENERAL
Remote OSD Timeout
Determines the time period of inactivity within the OSD after which a standard user will be automatically logged out.
iPATH Administrator Timeout
Determines the time period of inactivity within the iPATH config pages after which an admin user will be automatically logged
out.
Anonymous User
Determines which user is shown in the log when a remote 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 offline 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 specifically to a user will override
settings applied to user groups they’re 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).
• Ifauserissettoinherit“AllowPrivate?”modefromtheirusergroups,ifanyoneoftheirusergroupshas“AllowPrivate?”mode
granted, then the user will have it granted, even if the rest of the user’s usergroups have private mode not granted.
• Ifauserissettoinherit“AllowPrivate?”modefromtheirusergroups,andoneoftheusergroupsissettoinheritfromthe
globalsetting-ifthatglobalsettingis“AllowPrivate?”mode,theneffectivelytheusergroupis“AllowPrivate?”modesothe
user will be allowed private mode.
Grant All Users Remote OSD Access
If enabled, allows remotes to be switched remotely from another remote’s OSD menu.
Grant all users Force Disconnect
If enabled, permits any user logged in at a remote to disconnect a channel or preset established on that remote by another user.
20
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
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.
• Private: Allows a user to gain private access to a system, while locking out all others.
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 remotes. Note the admin configuration 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 a Black Box engineer.
API Login required
If enabled, the anonymous use of the iPATH 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 IPATH server.
Licensed Features - Displays the level of operation permitted under the current license. Click view/change to see more detail and
gain a unique identier that can be declared to Black Box when upgrading a license.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
21
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5.4 DASHBOARD > SETTINGS > LOCALS
This page applies a standard global configuration to all locals.
Magic Eye
Determines whether the Magic Eye feature should be enabled on Agility locals. 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 Agility dual
user guide for more details.
DDC
Determines whether video configuration details should be harvested from connected display screens or a static fixed EDID report
should be used. Care must be taken when selecting a Dual Link Video resolution as only Agility 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 Agility
dual locals.
EDID optimization
When this option is ticked, the Locals 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 remote is switched to that channel. If the new
remote 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 sufficient for most graphics cards. Occasionally it may be necessary to adjust this.
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 local video configuration 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.
22
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
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 Local.
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 specific number of USB ports (up to 8) on the local that can be made available for certain USB
devices which require a quirk setting under advanced USB features, connected to a remote.
Note: This setting can only be applied globally it is not found with individual local configurations because all remotes need to
know how many USB ports are available for the advanced USB features.
Serial port options
These allow you to match the serial configuration being used by the attached PC host.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
23
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5.5 DASHBOARD > SETTINGS > REMOTES
This page applies a standard global configuration to all remotes.
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 remote.
OSD Login Message
Text entered in this box will be displayed as a message on the OSD screen.
Enable Remote 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 remote 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 remote 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 first.
• Match Frame Rate - Follows the source frame rate and will change the frame rate every time this changes even if the video
resolution doesn’t change. If you have one remote 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.
Remote Keyboard Country Code
Select the country code of the keyboard connected to the remote.
Audio Input Type
Select the required audio input type.
24
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5.6 USB SETTINGS
HID only
If enabled, allows only HID (mice and keyboards) devices to be connected to the remotes.
Disable Isochronous Endpoint Alerts
When an isochronous USB device is connected to the remote there will no longer be a warning message. Agility 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 Agility remotes, 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 a Black Box reseller.
For each of the four USB ports on the remote, certain rules can be applied depending upon the USB device connected.
If you have reserved USB ports on the local, 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 Black Box reseller for advice.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
25
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5.7 DASHBOARD > SETTINGS > SERVERS
This page is used to configure redundant operation for the iPATH servers.
Two or more servers can be added onto the same subnet or Vlan. One iPATH 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 iPATH units match. Both iPATH 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, unconfigured iPATH server will be unable to join the cluster automatically; it’s behaviour will be to
report itself as unconfigured 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 iPATH-to iPATH https queries, if the Require Authentication option is enabled.
26
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
4.5.8 DASHBOARD > SETTINGS > NETWORK
This page applies global network parameters to the iPATH network.
4.5.8.1 IPATH CONNECTIVITY
Require SSL for Web
If set to yes, a certificate needs to be downloaded and all connections will then take place using HTTPS:// connections rather
than the default HTTP:// connection types.
Gateway IP Address
Defines the IP address of an optional gateway device.
Note: Only a single gateway can be specified within an iPATH 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 iPATH and the Agility
endpoints on the different subnets will be affected if using multi-subnet mode without a jointly valid gateway.
Ethernet Port 1
The primary iPATH server Ethernet port can only be configured using a static IP address. Use the three options provided to configure
the IP address, netmask and DNS server address.
Ethernet Port 2
The Backup iPATH server Ethernet port can be configured to either: gain its details via a DHCP server; use a Static IP address,
netmask and DNS server address, or alternatively be set to Bonded operation, whereupon three further Bonding Mode options are
displayed:
• Active-Backup - This can be used when both of the iPATH 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 iPATH server
and the switch.
In this mode, one of the iPATH 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 configuration 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.
• Broadcast - This option would be used when the twin ports of the iPATH server and all attached Agility devices are split
between duplicate networks:
The ‘Separate Device Networks’ option mentioned earlier would be enabled on the iPATH 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 iPATH server network connections mirror each other, i.e. duplicate network traffic is sent out
on both connections. It is assumed that the connected devices will only listen to the network traffic intended for themselves
and drop/ignore all other traffic intended for other devices. This mode is robust but inefficient because half of the packets are
discarded.
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
27
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
• 802.3ad - This mode uses a similar topology to Active-Backup, (i.e. both network ports connected to the same switch) but
has two important differences: Both of the iPATH server network ports are used simultaneously, and the network switch must
support LACP (Link Aggregation Control Protocol).
The iPATH 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 benefit of increased bandwidth availability between the iPATH 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 traffic 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 iPATH server and one of the Agility 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 iPATH server to be rebooted.
4.5.8.2 DEVICE CONNECTIVITY
IP Pool Lower/Upper Limits (not shown in multi-subnet mode)
When the iPATH server is used in single subnet mode, these two fields are used to define the range (pool) of IP addresses that
the iPATH server can automatically assign to new Agility endpoint devices. The iPATH server contains its own DHCP server with
which it applies the available IP addresses to Agility endpoint devices.
When used in multi-subnet mode, the internal DHCP server with the iPATH is disabled and instead the iPATH 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 sufficient 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 efficient 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 iPATH to use for Agility control. This is either ETH1 the default or Both ports if the
iPATH has ETH1 and ETH2 connected to the Agility network.
Separate Device Networks
When this option is set to ‘Yes’, the Agility devices within the network will be instructed to promote a further level of network
resilience by treating their copper and fiber/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 fiber
links working in parallel.
The two Ethernet ports of the iPATH server can be connected to the two separate network switches to ensure that iPATH control
remains in place if one network switch should become unavailable.
28
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
Route of Last Resort
This option is appropriate when the iPATH server is used in multi-subnet mode. In such cases, it is possible that the iPATH server
is not directly connected to the same sub-network as some or all of the Agility endpoints. Therefore, it will be necessary for the
Agility unit(s) to communicate back to the iPATH server via a gateway device (see Gateway IP Address above). This option is used
to indicate which interface has the gateway configured.
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 iPATH’s IP adress as iPATH cannot log its own syslog messages.
SNMP
This option allows the iPATH 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 file can be downloaded from http://<IP>/IPATH-MIB.txt
The response is split into three sections:
The first reports status of each individual endpoint:
deviceIndex,
deviceType,
deviceFirmware, (firmware revision)
deviceName,
deviceIdentifier,
deviceIP1,
deviceMAC1,
deviceIP2,
deviceMAC2,
deviceSerialNum,
deviceStatus,
deviceLock,
deviceEth1Status,
deviceEth2Status,
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
29
The second part is returned from iPATH:
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
NEED HELP?
LEAVE T HE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
30
1. 87 7. 8 77. 2 2 69 BLACKBOX.COM
Loading...