Grass Valley iControl V.4.43 - Manual (Page 42)

Getting Started with iControl
Examples: Service and Alarm Discovery Scenarios
32
Application Server (the server hosting the lookup service where the target GSM is registered)
in the Alarm publication table of the iControl Lookup locations page.
Figure 2-3: Populated Alarm publication table (circled)
Examples: Service and Alarm Discovery Scenarios
The way in which lookup services are configured varies from one installation to another. The
examples on the following pages demonstrate the basic concepts, and can serve as a guide as
you set up your own iControl network.
Example 1 — Single Application Server
In a typical, basic iControl configuration, only one Application Server is needed to handle all of
the iControl functions. Any TCP/IP devices associated with the Application Server are on the
same subnet.
IMPORTANT: System behavior
If the Alarm publication table of Application Servers is empty, the Densité
Manager on the local Application Server publishes its alarms exclusively on the
local GSM and active GSMs on Application Servers within the subnet.
If the Alarm publication table is populated with the IP address of a non-local
Application Server (illustrated in
"Figure 2-3" ), and you would like the local GSM
to see alarms originating from the local Densité Manager, you must also include
the IP address of the local Application Server.
See also
For more information, see:
• "Examples: Alarm Publication Lookup Scenarios" , on page 37
• "About the Alarm Publication Lookup Table" , on page 42