FDDI Network Interface Configuration [ NS3000/iX NMMGR Screens Reference Manual ] MPE/iX 5.0 Documentation
NS3000/iX NMMGR Screens Reference Manual
FDDI Network Interface Configuration
The FDDI Network Interface Configuration screen (#200) in figure 9-3 is
displayed when you select an NI name and the NI type FDDI at the Network
Interface Configuration screen (figure 9-2) 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 FDDI NI name.
Figure 9-3. FDDI Network Interface Configuration
The FDDI 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 FDDI network interface link and internetwork routing.
Choose the item you wish to configure, and press the corresponding key.
Fields
Network segment size This field specifies the largest packet that
will be sent by the FDDI device. The only
reason for entering a value smaller than 4032
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: 4032 bytes
Range: 256-4600
Number of outbound This field specifies the number of buffers to
buffers be allocated for outbound data. Outbound
buffersare 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:
* NETXPORT.GPROT.TCP
The maximum number of connections is
configured here. If it is increased,
consider increasing the number of
outbound buffers also.
Default value: 128
Range: 128-4096
Load network directory Specifies whether or not the system should load
mapping? (Y/N) mappings from the network directory at network
startup. If you have non-HP nodeson the FDDI
(nodes 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 recommends the default unless non-HP nodes
are on the network and the network directory
has been successfully completed. Refer to
chapter 13 for information about the network
directory.
Default value: N
Range: Y or N
MPE/iX 5.0 Documentation