|
|
The Token Ring Network Interface Configuration screen (#88) in
Figure 8-3 "Token Ring Network Interface
Configuration Screen" is displayed when you select an NI name and the NI
type TOKEN at the Network Interface Configuration screen
(Figure 8-2 "Network Interface Configuration
Screen") and press the [Add] or [Modify] function key. It is
also displayed when you type the path name:
@NETXPORT.NI.NIname
in the Command window of any screen and press the [Enter] key, where
NIname is a configured Token Ring NI name.
Figure 8-3 Token Ring Network Interface Configuration Screen
The Token Ring network interface (NI) module serves to interface the upper
layers of the transport product to the link layer. This screen supplies the
information required for that interface. All of the fields are used for
internal resource allocation.
Press the [Save Data] function key to transfer the data displayed on the
screen to the configuration file you are creating or modifying. Verify that the
data record has been created by checking that the Data flag is set to
Y. From this screen you proceed to the screens used to configure the
network layer protocols, the Token Ring network interface link, and
internetwork routing.
Fields
- Network segment size
This field specifies the largest packet that will be sent by the Token
Ring device. The only reason for entering a value smaller than 1984 is to
make better use of memory for those systems where it is known that upper
layer services will always send shorter messages. Note that whenever
packets larger than the network segment size are sent, they will be
fragmented to the network segment size, thus incurring fragmentation
overhead at the source and assembly overhead at the destination node.
Default value: 1984 bytes
Range: 300-1984
- Number of outbound buffers
This field specifies the number of buffers to be allocated for
outbound data. Outbound buffers are used for outbound data packets and
are held by the transport until they are acknowledged by the destination
node. Underallocation may adversely affect TCP throughput. Overallocation
may waste core memory.
Related screen:
Default value: 128
Range: 128-4096
- Load network directory mapping? (Y/N)
Specifies whether or not the system should load mappings from the
network directory at network startup. If you have nodes on the Token Ring
that do not support the ARP protocol, you must enter these nodes into the
network directory and set load network directory mapping to Y. HP nodes
support the ARP protocol.
HP recommends the default unless it is for the situation describe above.
Refer to Chapter 13 "Network Directory" for
information about the network directory.
Default value: N
Range: Y or N
|