Using the Local Parameter Worksheet

Subnetwork Name

OTS uses a symbolic name you define to refer to each subnetwork. Use a name that is meaningful to you (for example, fddilan, site_8023, transpac).

Local NSAP

This value defines the NSAP (network address) that other systems on the network will use when establishing connections to your system. The value should be expressed as an even number of hexadecimal digits.

Local Network ID

This value is used in making routing decisions for addresses that have not been explicitly configured, and that do not broadcast End System Hellos. It is some initial set of digits of the NSAP that form a prefix for all systems reachable over this subnetwork. For example, if you have a Local Network ID of 0x490001, then this subnetwork is used for reaching the system with the address 0x490001223344 (assuming that no explicit configuration for this address exists). The use of this parameter is optional.

Subnetwork Type

Specify what network service and link type you will use for this subnetwork.

X.25

If this subnetwork uses the X.25 link, then regardless of whether CONS or CLNS is used, you must provide the information requested. Specifically, indicate all the X.25 cards being used and a subaddress value (or the keyword NULL). At least one subaddress/ programmatic access pair is required.Each card is identified by its programmatic access name. The programmatic access name is determined by the X.25 link configuration. The subaddress you provide is appended to the configured X.121 address. This defines the SNPA address that calling entities must specify to reach OTS.X.25 configuration files typically reside in /etc/x25. Run x25stat -d <x25 device file> -c to view the currently configured values for the corresponding device file that is running. The System Administrator Manager utility (SAM) can also be used to view the X.25 configuration.

CONS/X.25

Specify all of the X.25 facilities that you wish to use over this subnetwork.ISO 8878 Support - If true, this results in the use of the X.25 extended addressing facility, as described by ISO 8878 (use of X.25 to provide CONS). If you do not use this facility, your NSAP should match the X.25 address (X.121 + subaddress)X.25 Standard - This indicates which X.25 standard versions are supported by the system. At least one of these must be specified.The most flexibility is afforded by enabling all facilities supported by the network.

Device Interface Name

For LAN-based subnetworks, you need to provide the device interface name for the card. This is not necessarily the same as the device file name. Typically, the interface name will be "lanx" where x is the logical unit number or the select code.To view existing LAN card interface names, run the utility lanscan(1M).The encapsulation method must be IEEE802.3 to allow OSI to run over an 802.3 LAN. To determine if you have IEEE, type lanconfig lanX, where "X" is the LAN interface you wish to use. If the output does not show "IEEE", edit the /etc/rc.config.d/netconf file and add "ieee" to the LANCONFIG_ARGS[0] entry.

CLNP Subset

U.S. GOSIP requires the use of the full subset with NULL packets being discarded. This is the default.The NULL subset is used only when all destination OSI nodes are physically connected via the same LAN. It provides low overhead at the cost of internetworking. It also requires that the NSAP match the MAC address of the LAN card.Non-segmenting and Full subset (accept NULL) are less frequently used, but are supported by HP.

Routing Information

These describe how to reach systems that are not directly connected to your subnetworks, and require a router. For simple networks, you may not require any route entries.You can specify the route for specific destinations by using the full remote NSAP. Otherwise, you can specify a route for a set of destinations by using a Network ID (or prefix) that is common to all remote systems reachable through this route.You must also specify the NSAP of the Intermediate System that will act as the router for the destinations.