Configuring the Network Directory
Add Nodes to Network Directory File
Fields | Node name | The name of the node for which you want network |
|
| directory information. The node name field must |
|
| contain a fully qualified node name, in the form |
|
| nodename.domain.organization, when used to add, |
|
| modify, delete, or rename a node. |
|
| The node name field when used with the Prev Page |
|
| and Next Page function keys allows you to browse |
|
| through a specified part of the network directory. You |
|
| can enter part of a node name in this field to designate |
|
| which node names you want displayed. For example, if |
|
| you enter the value NIK, and press the [Next Page] |
|
| function key, the list of nodes will begin with the first |
|
| matching node name, for example |
|
| NIKOLAI.FINANCE.IND, and continue through the rest |
|
| of the alphabet until all node names between the letters |
|
| NIK and Z are listed. |
| Global? | The global/local setting for node name. The acceptable |
|
| values are Y or N. When the Prev Page and Next Page |
|
| function keys are used, only node names whose |
|
| global/local setting matches the value in this field are |
|
| displayed. |
|
| Entries can be configured as either global or local in the |
|
| network directory. Global entries (the default) can be |
|
| merged into other directories using the MERGEDIR |
|
| command. Local entries are not merged into other |
|
| network directories. The local entries are used for |
|
| configuring localized network directory entries, thus |
|
| providing a mechanism to restrict directory data from |
|
| being propagated throughout the network. |
|
| A situation where this type of restriction could be |
|
| useful is when you want to change the configuration for |
|
| users on a single host, but not for everyone else. You |
|
| can configure two network directory entries: one local, |
|
| used by host users, and one global, used by everyone |
|
| else when establishing connections to the host. For |
|
| example, suppose Node A sets up a new link to Node C, |
|
| but Node A does not want other nodes (already |
|
| connected to A) to know about Node C until the new |
|
| link is tested. Users on Node A can configure a local |
|
| entry, which contains information about the new link |
|
| not included in the global entry configured for users on |
|
| other nodes. |
|
| Other uses of local entries include restricting certain |
|
| nodes from communicating with the internet, or being |
|
| able to direct which way to access remote nodes |
|
| depending on your configuration of local entries. When |
158 | Chapter 11 |