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

Getting Started with iControl
About the Alarm Publication Lookup Table
42
Example — Forced Unicast with Lookup Service OFF
About the Alarm Publication Lookup Table
In a basic iControl configuration, services such as the Densité Manager or the Imagestore
Manager will automatically detect—and begin publishing alarm status information to—the
GSM(s) on their own subnet.
If, however, you wish to have these services connect to GSMs running on Application Servers
on other subnets, you must explicitly specify the GSM locations. You do this by typing the
IP address of the target Application Server (on the remote subnet) in the Alarm publication
lookup table of the Application Server running the Densité, Imagestore, or other service on
the local subnet.
If the remote GSM is registered in a lookup service on another Application Server in its subnet,
you can use the IP address of that server instead.
For example, let’s say you want a Densité frame to publish its alarms and status information to
GSMs on two different subnets. The table below describes a possible configuration:
Note: The current version of iControl has a built-in feature called multi-GSM that
eliminates the need for specifying alarm publication lookup locations. The
description below and procedures being kept in this User Guide in support of legacy
iControl installations. Please consult with Grass Valley Technical Support before
making any modifications to your Alarm publication lookup table.
Service And Alarm Discovery locations on
10.10.81.10
Connections made by iC Navigator opened
from 10.10.81.10
Typing the Application Server’s own IP address
here means that applets launched from this
Application Server will only unicast to this
server.
Forced unicast finds the Application Server
from which iC Navigator was opened. Plain
text indicates no lookup service is running.
No devices or
services visible
NOTE: In this example, the Application
Server’s Lookup Service has been
turned OFF.