Installing PeerMaster LAN Software
Novell NetWare servers poll idle workstations every 15 minutes.
Thus, an aging duration of 30 minutes (N=1800) would safely
prevent unlearned traffic due to idle workstations. In very large
networks, however, a duration of this length might result in the
overflow of the forwarding database.
Adjusting Transmit and Receive Resources
Various transmit and receive control blocks and buffers exist to
support the bus-master interface between the PeerMaster adapter
and the host-based device driver. The number of transmit and
receive packets that the interface can handle is controlled by the
number of these resources. Increase the number of these resources
only if you have determined that packets are being lost due to lack
of resources.
The TXCOUNT keyword is used to allocate the amount of resources
allocated to transmit packets to the adapter, as follows:
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=11 TXCOUNT=nnn
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=12
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=13
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=14
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=21 TXCOUNT=nnn
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=22
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=23
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=24
:LOAD C:\PATH\VNET.LAN TXCOUNT=nnn
(where C: is the primary drive and PATH is the directory)
The parameter nnn is a 3-digit decimal number that specifies the
number of control blocks. The first port that is loaded on a
PeerMaster adapter sets the TXCOUNT of resources for that
adapter. The TXCOUNT keyword for subsequent loads of the same
PeerMaster adapter is ignored by the device driver. The keyword
must be specified on the load command line for MXPCI4BT.LAN
and VNET.LAN. The value of TXCOUNT for VNET.LAN must
equal the sum of all PeerMaster adapters included in the VNET.
For instance, the value of TXCOUNT for VNET.LAN in the previous
example is 40 if the values for slots 11 and 21 were each specified as
20.
60 PC Server 520 User's Handbook for PCI/EISA
To Next Page
Loading...
