Grass Valley iControl V.6.02 - Manual (Page 40)

Getting Started with iControl
Service and Alarm Discovery Lookup Table
30
By default, each Application Server runs a lookup service that registers and makes available
information about the devices on its network. It will also register with all lookup services that
are running on other Application Servers on the same LAN.
When client PCs are on different subnets, or when multiple Applications Servers are involved,
the locations of lookup servers must be properly specified in order for operators to be able to
(a) access iControl monitoring Web pages using iC Web, and (b) use iC Navigator to view
iControl alarms and control panels.
On the iControl Lookup locations page, there are two areas representing two distinct lookup
tables.
Service and Alarm Discovery Lookup Table
As a default, an Application Server’s client applications, such as iC Navigator and iC Web,
discover services and alarms originating from Application Servers on the local subnet. Leaving
the Service and alarm discovery table empty results precisely in this behavior with no need
for further configuration.
If, however, you would like an Application Server’s client applications to see services and
alarms from Application Servers OUTSIDE the local subnet, you must include the IP addresses
of these external servers in the Service and alarm discovery table.
Note: Displaying more than 10,000 messages in the Log Viewer may require system
adjustments to maintain acceptable performance levels.
IMPORTANT: System behavior
If the Service and alarm discovery table of Application Servers is empty, client
applications on the local Application Server can see services and alarms coming
from the local GSM and all active GSMs on Application Servers within the
subnet.