home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-386-Vol-2of3.iso
/
b
/
bmode.zip
/
PBURST.TXT
< prev
next >
Wrap
Text File
|
1992-04-28
|
9KB
|
281 lines
BURST MODE ONLINE MODULE (.TXT)
The Burst Mode NLM allows you to make high-performance
connections between workstations and file servers. Once a
connection has been made, packets of data are transmitted in
bursts, taking advantage of available bandwidth. The
following terms and background information further explain
the Burst Mode protocol.
Terms:
Burst is a multipacket unit that includes
o The IPX headers for each packet
o The Burst Mode headers for each packet
o The request or reply, with or without data
Fragments are the packets that make up the burst.
Burst transactions occur from the beginning of the burst
request to the end of the reply. For example, when a client
sends a request to read a file, the burst transaction
begins. The server sends a series of packets (a burst) to
the workstation, indicating the last packet with an End Of
Burst flag. A successful burst transaction is one with no
dropped packets; an unsuccessful burst transaction has
dropped packets.
Dropped packets (or missing fragments) are those that
prevent the completion of a burst transaction.
Service transaction is the completion of the entire request,
whether that entails just one burst and reply or many bursts
and the associated replies. If the client requests to read a
large file and the request requires many burst transaction
transmittals, the completion of all transmittals is a
service transaction.
System information is the process by which the server and
client exchange information about the packet data and its
transmission across the network. System information gives
additional information about the communication taking place
and is contained as a field in the burst header structure.
The End of Burst flag is considered system information.
Burst gap time is the amount of time between packet
deliveries to the wire; gap time is determined by the median
of the time between packet arrivals. Gap time is not
meaningful when bursts must cross a router.
Burst window size is the amount of data that is sent in the
current burst. The minimum window size is based on the
maximum physical packet size of the network media and the
number of workstation packet burst buffers.
Implementing Burst Mode
The current implementation of Burst Mode requires:
o The Burst Mode NLM to be loaded on the server
o Space in conventional memory at the workstation
o BNETX.COM loaded on each workstation
The amount of workstation memory needed is based on burst
mode parameters in the NET.CFG file and the capability of
the network hardware media. The BNETX shell determines, upon
loading, whether the workstation has enough memory, based on
the parameters in the .CFG file. If there is enough memory,
a Burst Mode connection is initiated with the server by the
client at connection/login time.
Maximum burst sizes are negotiated at connection time. The
Maximum Packet Size value is either the workstation's Packet
Buffer Size or the file server's Packet Buffer Size,
whichever is smaller. This is because the file server does
not know if routers between the workstation and the file
server can handle large packet sizes (see the Large Internet
Packet Exchange (LIPX.ZIP) NLM). Since Burst Mode is
established with each connection, it is possible to send
bursts with one server while not sending bursts with
another.
Once a Burst Mode connection is established between a
workstation and a file server, the NetWare workstation shell
uses the Burst Mode service whenever an application makes a
read or write involving more than 512 bytes of data. An
application doesn't have to be Burst Mode aware.
The following files are included in PBURST.ZIP:
Files:SizeVersionLast Updated
------------------------------------------------------------
--------
PBURST.NLM12938N/A1-17-922:36p
BNETX.COM58468N/A2-11-92 4:26p
PBURST.RME
Note: If you are using a non-Novell driver, check with the
manufacturer to see
that it has been certified to run with NetWare.
The following drivers were released with NetWare v3.11 and
are approved for use with Burst Mode:
Files:SizeVersionLast Updated
------------------------------------------------------------
--------
OS LAN DRIVERS:
3C503.LAN118561-21-91 6:39a
3C505.LAN216771-17-9111:49a
3C523.LAN122252-06-91 4:42p
NE1000.LAN113361-31-91 4:43p
NE2-32.LAN116391-21-91 6:38a
NE2.LAN115891-21-91 6:24a
NE2000.LAN116361-31-91 4:35p
NE3200.LAN230432-06-91 9:12a
PCN2L.LAN 98682-07-91 3:20p
TOKEN.LAN 99592-11-91 1:44p
TOKENDMA.LAN 81722-05-9112:13p
TRXNET.LAN 89551-07-91 2:59p
DISK DRIVERS:
DCB.DSK186132-12-919:08p
ISADISK.DSK104152-15-9111:31a
PS2ESDI.DSK 75642-12-918:39p
PS2MFM.DSK 87591-31-9111:01a
PS2SCSI.DSK 95772-12-919:03p
DOS ODI DRIVERS:
3C501.COM1183811-29-90 4:48p
3C503.COM1265511-29-90 4:59p
3C505.COM250691-11-91 3:09p
3C523.COM122061-15-9111:56a
EXOS.COM147002-04-91 4:39p
LANSUP.COM1331512-20-90 1:27p
NE1000.COM1268511-29-90 4:19p
NE2-32.COM1270511-29-90 4:58p
NE2.COM1299611-29-90 4:48p
NE2000.COM1279111-29-90 4:59p
PCN2L.COM135761-17-91 8:20a
TOKEN.COM155661-10-91 8:19a
TRXNET.COM1203712-10-90 7:45a
DEDICATED IPX DRIVERS:
S3C503.OBJ 631011-01-90 8:55a
S3C505.OBJ 95641-17-9110:24a
S3C523.OBJ 784112-07-90 2:50p
SLANSUP.OBJ 432710-31-90 4:29p
SNE1000.OBJ 546308-31-90 2:13p
SNE2.OBJ 478307-18-90 2:28p
SNE2000.OBJ 612907-18-90 2:25p
SPCN2.OBJ 586109-05-90 11:27a
STOKEN.OBJ 533710-22-90 12:10p
STRXNET.OBJ 704212-17-90 8:33a
OS/2 ODI DRIVERS:
3C501.SYS1780812-28-90 10:54a
3C503.SYS194881-23-91 3:09p
3C505.SYS181601-15-91 1:10p
3C523.SYS1704009-10-90 11:16a
NE1000.SYS194241-29-91 2:27p
NE2-32.SYS190562-06-91 9:44a
NE2.SYS199362-06-91 9:39a
NE2000.SYS194721-28-91 3:37p
PCN2.SYS125924-30-90 1:20p
PCN2L.SYS136322-04-91 2:25p
TOKEN.SYS226241-10-91 1:47p
TOKENEE.SYS382248-08-90 10:58a
TRXNET.SYS143682-01-91 4:10p
TRXNET2.SYS148802-01-91 4:05p
The following drivers were released after NetWare v3.11 and
are approved for use with Burst Mode. These drivers are
available either on NetWire or on NetWare Express:
Files:SizeVersionLast Updated
------------------------------------------------------------
--------
OS LAN DRIVERS:
3C503.LAN123707-26-91 9:17a
3C505.LAN217988-20-91 8:51a
3C527.LAN153557-17-91 2:28p
NE1000.LAN118577-25-91 12:02p
NE1500T.LAN1640610-09-91 4:35p
NE2.LAN1554811-11-91 11:19a
NE2-32.LAN121857-25-91 11:52a
NE2000.LAN123897-26-91 9:36a
NE2100.LAN1640510-9-91 4:36p
NE3200.LAN191981-15-92 11:24a
PCN2L.LAN104347-24-91 9:48a
TOKEN.LAN103249-09-91 11:30a
TOKENDMA.LAN 917710-25-91 9:25a
TRXNET.LAN116918-19-91 9:02a
DISK DRIVERS:
IDE.DSK13284 1-14-92 3:15p
PS2OPT.DSK2415610-15-91 4:06p
DOS ODI DRIVERS:
3C1100.COM1228811-12-91 10:42a
3C501.COM118383-19-91 10:21a
3C503.COM148216-14-91 9:14a
3C505.COM251177-29-91 9:30a
3C523.COM122387-29-91 9:35a
EXOS.COM2019411-08-91 3:14p
LANSUP.COM140944-30-91 10:32a
NE1000.COM127177-29-91 9:37a
NE1500T.COM2184010-11-91 5:09p
NE2.COM1921011-04-91 4:19p
NE2-32.COM127377-29-91 9:26a
NE2000.COM130186-03-91 1:25p
NE2100.COM2183610-11-91 5:10p
NE3200.COM192429-03-91 1:20p
PCN2L.COM141177-17-91 3:40p
TOKEN.COM156636-14-91 4:10p
TRXNET.COM121288-06-91 10:48a
DEDICATED IPX DRIVERS:
S3C503.OBJ 63196-14-91 9:22a
S3C505.OBJ 95345-08-91 12:46p
S3C523.OBJ 78412-26-91 11:52a
SLANSUP.OBJ 608010-18-91 6:24a
SNE2100.OBJ 48022-19-91 11:47a
SPCN2.OBJ 59115-03-91 2:53p
STOKEN.OBJ 66838-23-91 9:12a
OS/2 ODI DRIVERS:
3C501.SYS183206-24-91 1:44p
3C503.SYS265286-24-91 1:30p
3C505.SYS187368-15-91 9:14a
3C523.SYS185927-9-91 11:18a
CMGRLAN.SYS429763-26-91 9:32a
EXOS205.SYS2248011-27-91 3:21p
EXOS215.SYS2299211-27-91 3:21p
NE1000.SYS194246-24-91 1:41p
NE1500T.SYS2100812-13-91 9:28a
NE2.SYS204486-24-91 1:40p
NE2-32.SYS195686-24-91 1:43p
NE2000.SYS2115211-27-91 11:10a
NE2100.SYS2099212-13-91 9:28a
PCN2L.SYS1363210-11-91 3:46p
TOKEN.SYS2539212-13-91 4:54p
TRXNET.SYS2182412-17-91 10:47a
TRXNET2.SYS2182412-17-91 10:47a
To download PBURST.ZIP,
1.Highlight the PBURST.ZIP file and press <Enter>.
2.The screen displays the approximate amount of time
required to download the file. Select YES to continue
downloading the file.
2a.The name and path of the downloaded file appears on the
next screen.
2b.To load the file, select YES.
3.After you have downloaded the .ZIP file, use PKUNZIP to
decompress the file. PKUNZIP is available in the PKUNZIP
folder.
4.After you have unzipped the file, see the installation
instructions in PBURST.RME that was included in PBURST.ZIP.