Use the kdclbad command to list the contents of the Global Location Broker (GLB) on a monitoring server. Many problems come down to knowing what protocol and IP addresses are stored for a particular remote monitoring server or monitoring agent within the GLB. The following information shows how to use the kdclbad command to invoke the interactive lb_admin interface to list the contents of the GLB. First, regardless of whether the hub monitoring server is on a Windows® system or a UNIX® or Linux® system, the following two variables need to be exported within your shell:
On Windows systems, values for these can be obtained by searching the registry for similarly named keys under HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KMS\CMS\TEMS*\Environment. On UNIX and Linux systems, they can be grepped out of the CandleHome/config/host_ms_monitoring_server.config file. On UNIX systems, issue the following commands within either a bash or korn shell, where "config_file" is the aforementioned CandleHome/config/host_ms_monitoring_server.config file:
export KDC_GLBSITES=`grep KDC_GLBSITES config_file | cut -d'=' -f2 |
awk -F"'" '{print $2}'`export KDC_FAMILIES=`grep KDC_FAMILIES
config_file | cut -d'=' -f2 | awk -F"'" '{print $2}'`
On Windows systems, get the values from the registry and then do the following:
When this is done, either add the kdclbad command to the PATH variable, or cd to the directory where it exists. On Windows systems, this is in %CANDLE_HOME%\cms and on UNIX and Linux systems, it is under $CANDLEHOME/tmaitm6/arch/bin, where arch is the monitoring server architecture type. Then, issue the kdclbad command to get into the interactive "lb_admin:" prompt. The "h" or "?" character can be used to obtain a listing of possible commands to use, however it's recommended to only use the "l" (lower case "L" denoting "lookup") to list the contents of the GLB.
The following is an example of using this command:
# kdclbad lb_admin:
Return to Table 7.
[ Top of Page | Previous Page | Next Page | Contents | Index ]