IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 121 / 310

Global Location Broker service initialization
The Global Location Broker (GLB) differs from the Local Location Brokers in one
important respect other than the name: there is only one GLB for the domain or
enterprise. By definition, there will be only one Local Location Broker which points
to the Global Location Broker for the domain. The RPC server LLB which points to
the GLB (and there will be only one of these in an enterprise) is, by definition, the
hub. The important thing to remember from all this discussion of local and global
brokers is this: For a process to locate the Tivoli Enterprise Monitoring Server hub,
the process must query (issue lb__lookup() RPC requests to) the list of candidate
Global Location Brokers in order as specified in the global site text file
(
glb_site.txt on distributed platforms and the KDCSSITE member of RKANPAR
for OS/390 and z/OS platforms). Below are the product communication messages
which enumerate the candidate GLB list (GLB entry 1, GLB entry 2, etc):
GLB entry 1 is ip.pipe:#9.42.46.26.21343.
GLB entry 2 is ip:#9.42.46.26.21343.
GLB entry 3 is sna:(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
GLB entry 4 is ip.pipe:#9.42.46.26.21343.
GLB entry 5 is ip:#9.42.46.26.21343.
GLB entry 6 is sna:(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
Connectivity between the Omegamon/XE and Tivoli Enterprise Monitoring Server
address space fails if this list is incorrect. The GLB entries display in the order in
which they are configured in the global site text file. Additionally, the address of
the local platform is appended to this list. This is an RPC architecture requirement.
It allows the local platform to be queried when the GLB list has been exhausted
and no hub is found.
Confirming the Global Location Broker service initialized:
The bind messages in the RKLVLOG indicate the success or failure of the GLB
service initialization. A message ID prefixes the GLB status messages and indicates
how the GLB service was started.
KDSNC008
is the message prefix issued on
successful GLB process initialization when the LLB is started internally by the
Tivoli Enterprise Monitoring Server.
Bind of global location broker complete= ip.pipe:#9.42.46.26.21343.
Bind of global location broker complete= ip:#9.42.46.26.21343.
Bind of global location broker complete= sna:
(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
Global Location Broker is active
Repairing errors in Global Location Broker service initialization:
GLB service
failures occur because there are errors in member KDCSSITE of RKANPAR. Each
socket address in KDCSSITE is assumed to be the socket address of the Tivoli
Enterprise Monitoring Server hub. If none of the entries in the
KDCSSITE
file are the
correct socket address of the Tivoli Enterprise Monitoring Server hub, this process
initialization fails.
Tivoli Enterprise Monitoring Server hub availability
The following message indicates the Tivoli Enterprise Monitoring Server hub is
available:
ko4locbr.cpp,731,"Mgr::locateEverbody") lbLookupHub returned error <0>,
ip<ip:#9.42.46.26.21343>
sna<> pipe <ip.pipe:#9.42.46.26.21343.>
Do the following if the Tivoli Enterprise Monitoring Server hub is not available:
v
Review the RAS1 log for the Tivoli Enterprise Monitoring Server to ensure it is
connected.
Chapter 5. Installation and configuration troubleshooting
103