Table of Contents
Advertisement
iPATH Agility Controller
4.8 The Servers tab
The Servers tab shows a table of all servers within the iPATH Agility Controller network.
Click the SERVERS tab to view the page.
For installations that require greater redundancy, it is possible to have two iPATH Agility Controllers running on the same subnet. If
the primary server fails then a secondary server with the same database can take over until the primary unit recovers.
Each server entry will have one of four possible states within the Rôle column:
• Unconfigured The server is a factory fresh device or has performed a full factory reset. This does not yet have a proper role.
• Solo This is a server acting as a standalone iPATH Agility Controller. All iPATH Agility Controllers with firmware below 3.0 will
be in this state. If there is only going to be one iPATH Agility Controller on the subnet, this is the Rôle that will be used.
• Primary The server is configured as a fully functional iPATH Agility Controller from which a back-up server can be slaved.
• BackUp This server is configured to serve as a back up to the Primary.
Each server entry will also show one of six entries within the Status column:
• Active This server is functioning as an iPATH Agility Controller and is administering Agility devices. Primary or Solo servers with
this status are fully functional iPATH Agility Controllers that will accept network configuration changes. A backup server with
this status is functioning as an Active Primary. It will execute channel changes, but will not accept network configuration
changes.
• Standby This server is currently maintaining its database as a copy of the primary in readiness to take over if necessary.
• Offline This server should be maintaining a copy of the primary's database, but is not doing so.
• Initialising This is the initial status upon start up. This should not persist beyond the initial start up procedure.
• Quiescent This is an inactive server on the network. It will not function without remedial action from its system administration.
A typical reason for this is the presence of another server on the network blocking its configured role. i.e. two servers are
configured as a primary on the same subnet.
• Failed This server has suffered a serious internal failure.
4.8.1 Servers > Configure Server
When you click
for a particular server, this page lists information about the unit and allows several basic settings to be
configured.
Rôle
Allows you to change the server's function between primary and solo (see descriptions above).
Device Name, Description and Location
These are useful identifiers for the server unit and its exact location. These become even more valuable as the number of servers
within the system increases.
For details about setting up server redundancy, please see Appendix C - Redundant servers: Setting up and swapping out.
Page 50
724-746-5500 | blackbox.com
Advertisement
Table of Contents
