ADDER A.I.M. User's Guide Page 29

  • Download
  • Add to my manuals
  • Print
  • Page
    / 61
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 28
28
INSTALLATIONCONFIGURATIONOPERATION
FURTHER
INFORMATION
INDEX
THE SERVERS TAB
The Servers tab shows a table of all servers within the A.I.M. network.
Click the SERVERS tab to view the page.
For installations that require greater redundancy, it is possible to have two AIM servers
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:
Uncongured 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 A.I.M. All A.I.M. servers with rmware
below 3.0 will be in this state. If there is only going to be one A.I.M. on the subnet, this
is the Role that will be used.
Primary The server is congured as a fully functional A.I.M. from which a back-up
server can be slaved.
BackUp This server is congured 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 A.I.M. server and is administering ALIF devices.
Primary or Solo servers with this status are fully functional A.I.M. servers that will
accept network conguration changes. A backup server with this status is functioning
as an Active Primary. It will execute channel changes, but will not accept network
conguration changes.
Standby This server is currently maintaining its database as a copy of the primary in
readiness to take over if necessary.
Ofine 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 congured role. i.e. two servers are
congured as a primary on the same subnet.
Failed This server has suffered a serious internal failure.
Servers > Congure Server
When you click for a particular server, this page lists information about the unit and
allows several basic settings to be congured.
Rôle
Allows you to change the server’s function between primary and solo (see descriptions
left).
Device Name, Description and Location
These are useful identiers 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 view 28
1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 60 61

Comments to this Manuals

No comments