U-Net Release Notes for U-Net/NT v0.9
This is the release documentation for U-Net, a low-latency
communication mechanism over ATM and Fast Ethernet.
Please see the U-Net
Home Page for general information about U-Net, including
papers and other background information. This documentation is
meant to cover the Windows NT 4.0 release of U-Net only. Addional
release information can be found in:
- The U-Net device reference
with the U-Net interface details for the NT version.
- The using U-Net guide describing
typical code sequences for sending and receiving
messages.
- A description of a simple test application
Supported Hardware
This release of U-Net supports the following network
interfaces:
- DECChip 21140 "Tulip" PCI Fast Ethernet
interface (e.g., SMC Etherpower 10/100)
- Zeitnet ATM board
The binary release requires NT4.0. To build U-Net from the
sources, you need the Win32 SDK, the WinNT 4.0 DDK, and the
typical related compilers/utilities installed.
Obtaining the release
- As a zip archive: Binaries
only: unetnt-0-9-i386.exe. Source
code only: unetnt-0-9-src.zip
- Local to CUCS: You can always obtain the release as a
.zip file. Also, if you have access to SourceSafe in
CUCS, you can do the following to obtain the the source
code of release as well as new development.
- Start Visual SourceSafe Explorer and open the U-Net
project.
- Click the right button on the v1-mm-slowtrap project,
which represents the current version of the code
(version 1 with Memory Management).
- Select "Get" and recursively get this tree.
Installing U-Net
Obtain the binary release (unetnt-0-9-i386.exe) and run it. This will bring up an InstallShield
and install all of the binaries. Registry keys are created,
therefore if this is your first time installing U-Net, you need
to reboot your machine (don't you love this).
Testing U-Net
- If you're using the DECChip 21140 then enable loop-back
as follows (more details in the notes below): in the
registry editor find
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tulip
and set both FullDuplex and InternalLoopBack
to the value 1. If you're using the ATM card, connect a
loopback fiber to the card, or set-up a loopback PVC
through your switch.
- If you didn't reboot your machine after running the
installShield, do so now.
- Pull up a command window and start the general unet
driver and the device specific driver:
- net start unet
- net start tulip (or net start zeitnet)
It is important to start unet
before either tulip or zeitnet. Also, don't issue net stop unet before doing a net stop of tulip
or zeitnet
- Run the loopback test program which should be in the test\loopback\i386\free\ sub
directory (of wherever you installed U-Net):
- loopback device adddress
num-packets packet-size
Where:
- device is the device name (tulip or zeitnet),
followed by a slash, followed by the
device index (0 being the first board, 1
being the second, and so forth). E.g., tulip/0
specifies the first Tulip board, zeitnet/0 specifies the first
Zeitnet.
- address is the DC21140's MAC
address plus a channel number for Fast
Ethernet or the loopback VCI for ATM
- num-packets is the number of
packets to send, and
- packet-size is the size of the
packets to send and should be 0..1498
- For example:
- loopback tulip/0 00:00:c0:49:47:c8.42
1000 40
- loopback zeitnet/0 101 1000 40
Notes about the DECChip 21140
The DECChip 21140 has a few configuration options that can
be turned on/off using registry keys (sorry, someday we'll
figure out how to have nice pop-ups in the network control
panel). The registry entries of interest are in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tulip:
- FullDuplex: enables (value 1) or disables
(value 0) fast ethernet full duplex mode, the
default is ON
- InternalLoopBack: enables
(value 1) or disables (value 0) the internal
loop-back for testing purposes, the default is OFF
Note that FullDuplex
must be on for InternalLoopBack
to work!
- PromiscuousMode: enables
(value 1) or disables (value 0) the promiscuous mode
which allows the interface to receive all packets on
the ether, the default is off
DECChip 21140 based interfaces are available from a number
of vendors, in particular SMC, Digital, and Asante. In our
experience, almost all of these "just work", but
occasionnally Digital produces a new rev of the 21140 which
requires a bit of fiddling :-( Let us know if you have
problems.
Building U-Net from source
- Start the "Free Build Environment" in the
Windows NT DDK Program Group.
- Ensure that the MSTOOLS\bin and DDK\bin
directories are on your PATH.
- Do setenv c:\ddk (if c:\ddk is the location of
the installed DDK)
- Do a set Include=(wherever your winsock2 include and
msdev\include are)
- Do a set Lib=(wherever your winsock2 library and
msdev\lib directory are)
- If you wish to enable debugging output from the drivers,
be sure that the appropriate #define directives
are enabled at the top of the relevant source files. For
example, in devTulip\tulip.c, if TULIP_DEBUG is #defined,
the driver will print verbose debug information to the
kernel debugger.
- Run full-install.bat, this script performs the following
tasks automatically (you could also do them by hand):
- In the libunet, test\loopback, devTulip,
devZeitnet, UTLB, and UDI directories:
- mkdir i386
- mkdir i386\free
- mkdir i386\checked
- In the top-level U-Net directory:
- Copy all the compiled drivers into %SystemRoot%
(and %SystemRoot%\symbols if it's in the checked
build environment). For example, in the free
build environment:
- copy udi\unet.sys
%SystemRoot%
- copy utrap\utrap.sys
%SystemRoot%
- copy utlb\utlb.sys
%SystemRoot%
- copy
devTulip\tulip.sys %SystemRoot%
- copy
devZeitnet\zeitnet.sys %SystemRoot%
Contacts
For questions, support, and advice, contact Xun Wilson
Huang.
Share and enjoy!
Last modified 11/04/98 by X. Huang