| re: HUBwatch and TGV Multinet:
SLINK (my workstation) has been running TGV MultiNet exclusively for several
months now, and HUBwatch for OpenVMS VAX, V2.0 has been running on it during
that time. Just about everything works together fine, with a few exceptions.
So, we decided that MultiNet is kind-of sort-of supported, with some caveats.
The SPD still calls for UCX, but the release notes *imply* otherwise.
Quoting from the HUBwatch V2.0 release notes:
------------------------------------------------------------------------------
o HUBwatch for OpenVMS VAX, V2.0 contains limited support for TGV MultiNet
version V3.2. If TGV Multinet is installed instead of DEC TCP/IP Services
for VMS (UCX), the following restrictions should be noted:
- During kit installation, or when HUBWATCH$STARTUP.COM is invoked, the
following messages will appear:
%SYSTEM-W-NOSUCHFILE, no such file
\SYS$LIBRARY:UCX$IPC_SHR.EXE\
Previous NOSUCHFILE warning may be ignored.
HUBwatch installed with TGV MultiNet.
HUBwatch first determines if DEC TCP/IP Services for VMS (UCX) is
installed. If it is not installed, HUBwatch checks for TGV MultiNet.
If the "HUBwatch installed with TGV MultiNet" message appears,
HUBwatch has been installed with MultiNet instead of UCX.
- The Find Address function in the Applications menu can find by MAC
address and by DECnet address, but cannot find by IP address.
- The Connected Stations list in the Repeater Port Summary window will
display MAC addresses and DECnet addresses and names (where available),
but will not display IP addresses or names.
-----------------------------------------------------------------------------
Note that just about all the HUBwatch testing that's been done has been done
with UCX, and the only place around here running MultiNet is my workstation.
But, I feel comfortable with MultiNet, and haven't seen any nasty side-effects.
- Tom Hood
HUBwatcher
|