Table of Contents
Advertisement
local (LLB) and global (GLB) entries. The LLB entries of the Server list are derived.
The GLB entries of the Server list are built from the content of the KDCSSITE
member of RKANPAR. Shown below are two server lists. The first Server List is
for a Tivoli Enterprise Monitoring Server hub, the second Server List is for a
remote Tivoli Enterprise Monitoring Server. See the following example:
(Server list for a HUB CMS)
LLB entry 1 is ip:#10.248.16.1.1918.
LLB entry 2 is sna:#ATOOEN01.K10DSLB.CANCTDCS.SNASOCKETS.135.
GLB entry 1 is ip:#10.248.16.1.1918.
GLB entry 2 is sna:#ATOOEN01.K10DSLB.CANCTDCS.SNASOCKETS.135.
GLB entry 3 is ip:#10.248.16.1.1918.
GLB entry 4 is sna:#ATOOEN01.K10DSLB.CANCTDCS.SNASOCKETS.135.
(Server list for a REMOTE CMS)
LLB entry 1 is ip:#10.248.17.2.1918.
LLB entry 2 is sna:#ATOOEN01.K20DSLB.CANCTDCS.SNASOCKETS.135.
GLB entry 1 is ip:#10.248.16.1.1918.
GLB entry 2 is sna:#ATOOEN01.K10DSDS.CANCTDCS.SNASOCKETS.135.
GLB entry 3 is ip:#10.248.17.2.1918.
GLB entry 4 is sna:#ATOOEN01.K20DSLB.CANCTDCS.SNASOCKETS.135.
Confirming the Server list is correct: In general, the first half of the GLB server
list always points to the Tivoli Enterprise Monitoring Server hub. The first half of
the GLB entries in the Server list are taken from member KDCSSITE of RKANPAR.
If the LLB entries are derived (implicitly) and the GLB entries are explicitly
configured in the KDCSSITE member, you can diagnose and repair the errors in
KDCSSITE.
v The number of LLB entries must be half the number of GLB entries. If this is not
the case, then there might be a mismatch between the number of transports
services configured to this Tivoli Enterprise Monitoring Server (the
KDC_FAMILIES environment variable) versus the number of transports
configured for the hub Tivoli Enterprise Monitoring Server (KDCSSITE).
v For a hub Tivoli Enterprise Monitoring Server, each LLB entry must be identical
to the corresponding GLB entry in the Server list. As in the Server list for a hub
Tivoli Enterprise Monitoring Server example, LLB entry 1 is the same as GLB
entry 1 and LLB entry 2 is the same as GLB entry 2.
v For a remote Tivoli Enterprise Monitoring Server, the opposite is true: each LLB
entry must be different than the corresponding GLB entry in the Server list. As
in the example (Server list for a REMOTE Tivoli Enterprise Monitoring Server),
LLB entry 1 is different than GLB entry 1, LLB entry 2 is different than GLB
entry 2.
Repairing errors in the Server list: Errors in SNA initialization might be name
mismatches. Examine the LLB entries and the GLB entries for the Omegamon
Platform address space for typographical errors. The VTAM
of frequent error. Typically the VTAM network ID (the first component of the SNA
socket address, ATOOEN01 in the example above) is the same for ALL entries.
While it CAN differ, typically, it does not. A difference between the LLB VTAM net
ID and the GLB VTAM net ID is often an error in member KDCSSITE of
RKANPAR.
Local Location Broker service initialization
An intrinsic part of Remote Procedure Call architecture is the location broker. RPC
servers (callers of rpc__listen) publish their service and the address of this service
in a location broker. RPC clients (callers of rpc__sar) use the location broker to
obtain the address of a server prior to making a call to that server. Use of the
location broker is well-defined by the lb__lookup() Remote Procedure Call. It is
also appropriate to mention that there are two types of location brokers: the local
Chapter 5. Installation and configuration troubleshooting
®
network ID is victim
101
Advertisement
Table of Contents
Troubleshooting
