Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
System Administration Commands: Section 1M (Ref Pages Vol 2) > l

lb_admin(1M)

» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

NAME

lb_admin — Location Broker administrative tool

SYNOPSIS

/usr/sbin/ncs/lb_admin [-nq] [- version]

DESCRIPTION

lb_admin administers the registrations of NCS-based servers in Global Location Broker (GLB) or Local Location Broker (LLB) databases. A server registers Universal Unique Identifiers (UUIDs) specifying an object, a type, and an interface, along with a socket address specifying its location. A client can locate servers by issuing lookup requests to GLBs and LLBs. lb_admin can be used to look up information, add new entries, and delete existing entries in a specified database.

lb_admin is useful for inspecting the contents of Location Broker databases and for correcting database errors. For example, if a server terminates abnormally without unregistering itself, use lb_admin to manually remove its entry from the GLB database.

In accepting input or displaying output, lb_admin uses either character strings or descriptive textual names to identify objects, types, and interfaces. A character string directly represents the data in a UUID in the format xxxxxxxxxxxx. xx. xx. xx. xx. xx. xx. xx. xx, where each x is a hexadecimal digit. Descriptive textual names are associated with UUIDs in the uuidname.txt file.

lb_admin examines or modifies only one database at a time, refered to as the ``current database''. The use_broker command selects the type of Location Broker database, GLB or LLB. The set_broker command selects the host whose GLB or LLB database is to be accessed. Of course, if you modify one replica of a replicated GLB database, the modification is propagated to the other replicas of that database.

On HP-UX 10.x systems, though the DCE rpcd daemon provides both NCS LLB service and DCE RPC Endpoint Map service, lb_admin administers only the LLB database, not the Endpoint Map.

Options

lb_admin recognizes the following options:

-nq

Do not query for verification of wildcard expansions in unregister operations.

-version

Display the version of NCK that this lb_admin belongs to, but do not start the tool.

Commands

In lookup, register, and unregister commands, the object, type, and interface arguments can be either character strings representing UUIDs or textual names corresponding to UUIDs, as described earlier.

a[dd]

Synonym for register.

c[lean]

Find and delete obsolete entries in the current database.

With this command, lb_admin attempts to contact each server registered in the database. If the server responds, the entry for its registration is left intact in the database. If the server does not respond, lb_admin tries to look up its registration in the LLB database at the host where the server is located, displays the result of this lookup, and asks whether to delete the entry. If a server responds, but its UUIDs do not match the entry in the database, lb_admin displays this result and asks whether to delete the entry.

There are two situations in which it is likely that a database entry should be deleted:

  • The server does not respond, lb_admin succeeds in contacting the LLB at the host where the server is located, and the server is not registered with that LLB. The server is probably no longer running.

  • A server responds, but its UUIDs do not match the entry in the database. The server that responded is not the one that registered the entry.

Entries that meet either of these conditions are probably safe to delete and are considered eligible for "automatic deletion" (described in the next paragraph). In other situations, it is best not to delete the entry unless you can verify directly that the server is not running (for example, by listing the processes running on its host).

When lb_admin asks whether you want to delete an entry, you have four ways to respond. y[es] deletes the entry. n[o] leaves the entry intact in the database. After a yes or a no, lb_admin proceeds to check the next entry in the current database. g [ o ] invokes automatic deletion in which all eligible entries are deleted and all ineligible entries are left intact without your being queried, until all entries have been checked. q[uit] terminates the clean operation.

d[elete]

Synonym for unregister.

h[elp] [command] or ? [command]

Display a description of the specified command or, if none is specified, list all of the lb_admin commands.

l[ookup] object type interface

Look up and display all entries with matching object, type, and interface fields in the current database. You can use asterisks as wildcards for any of the arguments. If all the arguments are wildcards, lookup displays the entire database.

q[uit]

Exit the lb_admin session.

r[egister] object type interface location annotation [flag]

Add the specified entry to the current database. Use an asterisk to represent a nil UUID in the object, type, and interface fields.

The location is a string in the format family:host[port], where family is an address family, host is a host name, and port is a port number. Possible values for family include ip and dds. Use a leading # to indicate that a host name is in the standard numeric form. For example, ip:vienna[1756], ip:#192.5.5.5[1791], dds://salzburg[515], and dds:#575d.542e[452] are all acceptable location specifiers. (All HP-UX hosts have ip as the family.)

The annotation is a string of up to 64 characters annotating the entry. Use double quotation marks to delimit a string that contains a space or contains no characters. To embed a double quotation mark in the string, precede it with a backslash.

The flag is either local (the default) or global, indicating whether the entry should be marked for local registration only or for registration in both the LLB and GLB databases. The flag is a field that is stored with the entry; it does not affect where the entry is registered. The set_broker and use_broker commands select the particular LLB or GLB database for registration.

s[et_broker] [broker_switch] host

Set the host for the current LLB or GLB. If you specify global as the broker_switch, set_broker sets the current GLB; otherwise, it sets the current LLB. The host is a string in the format family:host, where family is an address family and host is a host name. Possible values for family include ip and dds. Use a leading # to indicate that a host name is in the standard numeric form. For example, ip:prague, ip:#192.5.5.5, dds://linz, and dds:#499d.590f are all acceptable host specifiers. (All HP-UX hosts have ip as the family.)

Issue use_broker, not this command, to determine whether subsequent operations will access the LLB or the GLB.

set_t[imeout] [short | long]

Set the timeout period used by lb_admin for all of its operations. With an argument of short or long, set_timeout sets the timeout accordingly. With no argument, it displays the current timeout value.

u[nregister] object type interface location

Delete the specified entry from the current database.

location is a string in the format family:host [port] , where family is an address family, host is a host name, and port is a port number. Possible values for family include ip and dds. Use a leading # to indicate that a host name is in the standard numeric form. For example, ip:vienna[1756], ip:#192.5.5.5[1791], dds://salzburg[515], and dds:#575d.542e[452] are all acceptable location specifiers. (All HP-UX hosts have ip as the family.)

Use an asterisk as a wildcard in the object, type, and interface fields to match any value for the field. Unless lb_admin -nq was used to suppress queries, unregister asks whether to delete each matching entry. y[es] deletes the entry. n[o] leaves the entry in the database. g[o] deletes all remaining database entries that match, without further interaction. q[uit] terminates the unregister operation without deleting any more entries.

us[e_broker] [broker_switch]

Select the type of database that subsequent operations will access, GLB or LLB. The broker_switch is either global or local. If broker_switch is not specified, use_broker tells whether the current database is global or local.

Use set_broker to select the host whose GLB or LLB is to be accessed.

SEE ALSO

drm_admin(1M), glbd(1M), rpcd(1M), uuidname.txt(4).

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.