tns_server_setup(1) — Commands

NAME

tns_server_setup − Tool to configure the TNS Server.

SYNOPSIS

tns_server_setup

DESCRIPTION

The tns_server_setup tool is used to configure the TeMIP Name Service (TNS) Server/Clerk on a system. There are 8 options from which to choose. The following describes functionalities provided by each of these menu options.

Option 0 is to exit.

Option 1 allows you to change the TNS Clerk default namespace.

This option displays the list of namespace nicknames available. This list contains all known namespaces for this clerk, including all the namespaces being advertised by servers on the clerk’s own local area network (LAN) as well as off-LAN namespaces made known to the clerk through the use of configuration menu option 2 (Establish communications with an off-LAN server). Enter the namespace nickname corresponding to namespace that you want to be your default. After you make a selection, the tns_server_setup tool configures the TNS Clerk using the default namespace you have selected, and try to check the connection with the TNS Server.

Option 2 is for establishing communication with a namespace over
a WAN network.
A clerk learns about all namespaces on its own LAN by listening to advertisements from servers on the same LAN. Because server advertisements do not span wide area network (WAN), a clerk cannot automatically learn about namespaces that exist outside the clerk’s own LAN. For a clerk to make an initial connection to an off-LAN server, you must provide the clerk with the server’s IP address This information is saved in the clerk’s cache and is used to make subsequent connections to the off-LAN server.

To establish an initial connection to a server in an off-LAN namespace, you have to contact the namespace administrator of the off-LAN namespace and obtain the internet name of the TNS Server you want to connect to.

Option 3 configures a new TNS namespace and the local system as the initial TNS server.

When you create a new namespace, you must supply both a namespace nickname and a clearinghouse name. Choose a short and simple namespace nickname. However, the namespace nickname still appears in command output, and even though the nickname can be as long as 255 characters, it makes sense to keep it short.

Because a namespace has no relationship to any individual node, you should give the namespace a nickname that is meaningful to users network-wide. Choose the namespace nickname carefully; it is inconvenient to change it. Do not give a test namespace a nickname that you eventually want to use for a network-wide namespace. Namespace nicknames are difficult to reuse once they have been established in clerk caches throughout the network.

Using this option some specific entries are added/created in the namespace to use TemIP.

These entries are :

- Create the .temip_users group

- Add ∗... as a member of the .temip_users group

- Add .temip_users as a group of the root directory

- Add access right in the clearinghouse object for the temip_users group

- Create the directory .MCC_SNMP_BackTranslation

- Create the directory .MCC_Sample_BackTranslation

- Create the directory .MCC_Station_BackTranslation

- Create the directory (default .temip) to store TeMIP
managing directors

If you wish to manage DECnet node over TeMIP (only on the DUNIX Version)

- Create the directory .DNA_Backtranslation

- Create the directory .DNA_Backtranslation.%XIDP

- Create the directory .DNA_Backtranslation.%XIDP.%XArea directories creation.

Option 4 configures the local system as a TNS server in an existing namespace.

You should consider configuring at least one additional server on another stable system whose connectivity to your network is reliable. By maintaining your namespace on two servers (two clearinghouses), you create a real-time backup of namespace data and ensure that a failure on one of the servers will not interrupt TNS service. As your namespace and network expand, you may want to configure additional servers to distribute namespace information around the network.

Option 5 reuse an existing Clearinghouse (DNS or TNS)

This option is specially dedicated to a migration mode in the case where you don’t need to communicate with other DECdns servers. If you are already using a namespace (a DNS or a TNS namespace), you may want to convert one or more of your existing clearinghouses to TNS format. By doing so, you can continue to use your existing namespace rather than having to abandon it and create a new namespace when you upgrade your TeMIP product version. You perform a clearinghouse conversion as part of the TNS configuration tool performed by option 5.

Option 6 : Stop the TNS Server and the TNS Clerk

(see tns_server_stop(1) and tns_clerk_stop(1) )

Option 7 : Start the TNS Clerk and the TNS Server

(see tns_clerk_start(1) and tns_server_start(1) )

RESTRICTIONS

tns_server_setup can only be run under super-user.

FILES

/usr/sbin/tns_server_setup

Museum