Conference netcad::hub_mgnt

>>A customer is trying to load HUBwatch on a PC running Netware over an
>>IPX stack and cannot get it to work.  In reading the documentation and
>>some of the other note entries in this conference, it's not clear to me
>>whether or not this is a workable configuration.

IPX is DIFFERENT than TCP/IP stack. HUBwatch requires a TCP/IP stack.
IPX will not work.

>>Will HUBwatch work with ODI driver from Novell?

Yes, why not?

>>Assuming Yes, and given that Netware is running over the IPX stack, I 
>>would assume that the installation procedure selected for HUBwatch should
>>select the " Install Hubwatch and Network " option.

The HUBwatch installation does not automatically setup for ODI. It provides
a STRTODI.BAT to load the PW components that support ODI, a NET.TMP is a NET.
CFG template file that needs to be manually modified to support your 
Network Interface Card(NIC) settings(like NDIS PROTOCOL.INI), and a few NIC
drivers (*.COM). The ODI NIC drivers are from the PATHWORKS V5.1 kit.  
Refer to the READ_ME.TXT on diskette 1 of the HUBwatch for Windows 3.1 kit.
Also several notes in this notesfile provide templates for the formentioned 
files. (#1192, 1240, 2108)

>>What are the gotchas that need to be worked if this is possible?

If the customer is truly running IPX, HUBwatch will not work. Novell as
well as out HUBwatch kit provides a true TCP/IP stack.

>>Is this a supported configuration for HUBwatch?

From my perspective, NO in reference to the HUBwatch kit(since these 
configurations are not fully tested with HUBwatch). But... Since we 
include the PATHWORKS V5.1 TCP/IP stack and drivers, these are fully
tested configurations and are supported. 

Barb

    HUBwatch can be made to work with an ODI driver with just a little bit
    of manual intervention. IPX is another matter. HUBwatch does not run 
    over IPX; our SNMP only makes calls to UDP, which requires IP, not 
    IPX. These are two totally different protocols.
    
    The customer might have an easier time installing Novell's IP with 
    IPX, since they created both. Once you get anyone's Winsock compatible
    IP stack running, then just install HUBwatch only, not HUBwatch and
    network.
    

RE: .1 ...

	I guess my original question was a little confusing.

	I know that HW will not run over IPX.  

	My question was whether or not HW will run over an IP stack 
	with an ODI driver at the same time that Netware is running
	an IPX stack with ODI drivers.

	I think the reply in .1 is NO! .. but please take another look at 
	the question from the context above.

	It won't do the customer any good if he cannot run both.

RE: .2 ...
    
>>    The customer might have an easier time installing Novell's IP with 
>>    IPX, since they created both. Once you get anyone's Winsock compatible
>>    IP stack running, then just install HUBwatch only, not HUBwatch and
>>    network.
    
	Very good point!

	If the answer to .1 is 'Yes', then this certainly will be the 
	preferred approach.

Thanks for the info thus far.

Mgc

    The other day I got HUBWATCH to run, with the IP stack and NOVELL to
    run with the IPX stack at the SAME TIME.
    
    The NET.CFG file (i posted a few notes back) was the key.  Basically my
    (limited) understanding is that:
    
    
     - You have an interface that you describe to NETware in the NET.CFG
       file
    
     - For that interface you describe each protocol that can run on
       the interface
    
     - You can specify different protocols for the interface, and they
       can run at the same time. (i.e. the analogy for an Ethernet
       holds true, you can run LAT, IP, DECnet, etc. all over an
       interface, the key is to have a DRIVER for each protocol....
       similarly you can run multiple protocols out over the interface
       in NETware but you muse have a NET.CFG entry for the 
       protocol.
    
     - Other things (in the LINk section) control the maximum number of
       protocols that you can have...i.e. i think the prior example
       had 15.
    
    One "gotcha" was that when we explicitly called out IPX as supported
    for an interface it caused grief.  I think that IPX is supported by
    default.  We couldn't get NETWARE to work when we spec'ed IPX  at
    all.  But when we commented it out...but the Pathworsk TCP/IP stack
    and the Novell netware junk (er, I mean stack) worked.
    
    So, yep, it IS possible.
    
    Now there may be memory implicitations ect...but hey, what do you want
    for a piece of technology who really only knows about 640K of memory.
    
    (evil grin)
    
    ttfn,
    j

	a Netware ODI client can use Hubwatch in one of three ways:

	- use Novell's Lan Workplace/Workgroup for DOS product (their
	  TCP/IP stack orginally developed by Excelan)
	- use some other third party TCP/IP stack (DOS or Windows
	  based) that a) supports ODI and b) supports Winsock 1.1
	- if using Windows for Workgroups, use Microsoft's TCP/IP-32
	  stack (codenamed Wolverine) available *for free* via ftp or
	  WWW from MS...

	I personally use this last option for Hubwatch and Hubloader/TFTP
	and it works quite well...note that a thorough understanding of 
	how these various components work and how Hubwatch/Hubloader etc
	use them is essential for a successful installation (eg not for
	the novice).....

	_kelley