[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

2614.0. "Problems w/HUBwatch 4.0 and ODI drivers" by ANGLIN::CLAYTON (Merlin Clayton (314)947-6763) Fri Aug 04 1995 13:44

I'm trying to get HUBwatch 4.0 loaded and operational on a customer's 
system running Netware 3.12, but I'm running into problems.

I am trying to use the IP protocol stack that comes with HW 4.0, and have made
the necessary changes to the NET.CFG and STRTODI.BAT file as indicated in the
"readme.txt" with Hubwatch.

We boot the system up without starting the network, then run STRTODI from the
\hubwatch\ipstack directory, and everything appears to start O.K. - no error
messages after any of the startup procedures, only "successfully loaded" msgs
after each of the IP startup appls.  However, after the completion, we still 
have no IP connection - cannot ping management station, cannot connect to 
dh900 agent.  The IPX stuff works fine though.

Attached are the working copies of the NET.CFG and STRTODI.BAT files.  Is 
there anything intuitively obvious that may be wrong in either if theses 
files?



Some specific questions about the files:
 Q. Why does STRTODI.BAT have a line that starts schdk with an /ndis option?
    This seems to be inconsistent with the odi driver stuff.
 Q. What do each of the ip applications do?  Are all required to run HW?
    (we are running short on memory 24MB), and may need to delete some of 
     the ip appls if not required).

BTW the management platform is a Compaq DESKpro XL 566 w/pentium processor,
24 MB memory, and integrated Netflex enet/pci controller

-------------------------------------------------------------------------------
				   NET.CFG

;NOTE: This sample file uses IP protocol using an Ethernet II frame type. 
;       The example shows a commented out IPX protocol with 802.3 frame type. 
;       Different frame types may be required depending on the version and 
;       setup of Novell.
;
;       Some Ethernet cards require a bind statement in a protocol section of the
;       NET.CFG. Refer to your Ethernet Card Documentation for details.
;
; SAMPLE NET.CFG File
;

File Handles = 60
Show Dots = ON
	
LINK SUPPORT
	Max boards      4
	Max stacks      11
 	Mempool         2k
	buffers         2       1500

; PREFERRED SERVER = fs3    **(Your server name here edit out between *)**

NetWare DOS Requester
	FIRST NETWORK DRIVE = N
;        NETWARE PROTOCOL = NDS BIND

Link Driver PCNTNW
	FRAME Ethernet_802.2
	FRAME Ethernet_II
	FRAME Ethernet_802.3
	FRAME Ethernet_SNAP     
;        PROTOCOL        NETBIOS         8040    Ethernet_II
;        PROTOCOL        LOOPBACK        9000    Ethernet_II
	PROTOCOL        IP              0800    Ethernet_802.2
	
PROTOCOL TCPIP
       ip_address 16.77.64.169
       ip_netmask 255.255.255.0
       tcp_sockets 8
       udp_sockets 8
       raw_sockets 1
       nb_sessions 4
       nb_commands 8
       nb_adapter 0

-------------------------------------------------------------------------------
				STRTODI.BAT

rem @echo off
C:
cd \HUBWATCH\IPSTACK

if %path% == "" goto no_path
	path >c:\HUBWATCH\IPSTACK\oldpath.bat
	goto path_done
:no_path
	echo set path=>c:\HUBWATCH\IPSTACK\oldpath.bat;c:\WINDOWS
:path_done
	set OLDPCSA=%PCSA%
	set PCSA=C:\HUBWATCH\IPSTACK
	SET PATH=%PCSA%;%PATH%
save

path
pause

REM Loads NET.CFG
lsl.com
pause

REM Choose the proper ODI driver for your network card.
REM **Refer to your ODI driver documentation for details.**
REM Uncomment only one of the following, or add a line for
REM the driver for your network card.


REM COMPAQ integrated netflex enet/pci controler

c:\cpqnet\netware\compaq.drv\pcntnw.com

ipxodi.com
pause

REM PATHWORKS TCP/IP components...
schk.exe /ndis			>> why /ndis?
dllodi.exe			>> what does this do?  required?
tcpip.exe			>> does this provide ping support?
tn.exe 				>> telnet - required?
bapi.exe			>> what does this do? required?


REM some Novell network versions will use netx(Redirector) instead of 
REM vlm(Enhanced Redirector)....
vlm
REM netx

-------------------------------------------------------------------------------

Any and all help will be greatly appreciated.

Thanks
Merlin
T.RTitleUserPersonal
Name		DateLines
2614.1for details check with PATHWORKSNETCAD::WAGNERCOFFILFri Aug 04 1995 15:5550
>>We boot the system up without starting the network, then run STRTODI from the
>>\hubwatch\ipstack directory, and everything appears to start O.K. - no error
>>messages after any of the startup procedures, only "successfully loaded" msgs
>>after each of the IP startup appls.  However, after the completion, we still 
>>have no IP connection - cannot ping management station, cannot connect to 
>>dh900 agent.  The IPX stuff works fine though.

Can you PING yourself? If so check the connection, cable, management 
station config, and agent config.


>>Some specific questions about the files:
>> Q. Why does STRTODI.BAT have a line that starts schdk with an /ndis option?

Bypasses 2 elements of NDIS error checking during loading. This switch is 
neccessary for some 3rd party drivers.
	
>> Q. What do each of the ip applications do?  Are all required to run HW?
>>    (we are running short on memory 24MB), and may need to delete some of 
>>     the ip appls if not required).

Refer to "PATHWORKS V5 for DOS and Windows Client Commands Reference" and
"PATHWORKS V5 for DOS and Windows TCP/IP User's Guide" for details.
Also PATHWORKS notes file: noted::pwdoswinv5.

>>REM PATHWORKS TCP/IP components...
>>schk.exe /ndis			>> why /ndis?
SCHK(kernel only) command loads the scheduler for the network operating 
system.

>>dllodi.exe			>> what does this do?  required?
DLLODI command loads a s/w interface that enables many ODI-compliant 
Ethernet and Token Ring drivers to be used w/ PATHWORKS network transports.

>>tcpip.exe			>> does this provide ping support?
Loads TCP/IP process.

>>tn.exe 				>> telnet - required?
Loads TELNET. network virtual terminal that allows terminal emulators to 
log in to a remote host using the TCP/IP stack.

>>bapi.exe			>> what does this do? required?
Session Manager. Allows for simultaneous, multiple sessions and certain 
modifications for each session.

You could rem the TN.EXE and BAPI.EXE if you do not need to TELNET from
HUBwatch to BROUTER, ATM, and/or TERMINAL SERVER(one type).

Barb
2614.2More Info...ANGLIN::CLAYTONMerlin Clayton (314)947-6763Thu Aug 10 1995 16:5823
>>Can you PING yourself? If so check the connection, cable, management 
>>station config, and agent config.

Yes. Pinging the local host ip address works o.k.  It appears that IP is 
loading o.k., just not getting out on the wire.  The connectiopn to the network
is fine because we can run IPX over the net without problems.  The agent config 
is o.k. too because I can attach to the hub agent with my laptop on the 
network without any problems.  

The Compaq that we're trying to get running with Hubwatch cannot successfully
ping anything, including the repeater it's connected to or my laptop which
is on an adjacent port.  

It appears that IP is not binding to the network adapter board in NET.CFG, 
but I'm not sure why.  IPX binds to the board o.k. and you see it dduring
network startup. 

Any other suggestions to help get this resolved?

Thanks.

Merlin
2614.3Check driver date; post in PATHWORKSNETCAD::WAGNERCOFFILFri Aug 11 1995 11:2014
>>It appears that IP is not binding to the network adapter board in NET.CFG, 
>>but I'm not sure why.  IPX binds to the board o.k. and you see it dduring
>>network startup. 

If you have a newer driver for the network adapter than what is provided
in HUBwatch use it. It is not binding because of something in your 
NET.CFG file. 

You may want to post the NET.CFG, excerpts of the STRTODI.BAT, and bind 
error in the PATHWORKS notesfile: NOTED::PWDOSWINV5. They may be able
to help (remember the stack included in HUBwatch is PATHWORKS, we did not
write our own stack).

Barb
2614.4Ask PW about the NIC driverNETCAD::WAGNERCOFFILFri Aug 11 1995 11:325
	You may want to ask the PATHWORKS group about that NIC Card and
	driver. May be there is some problem with it and our stack.

Barb
2614.5Drver not supported in PATHWORKSNETCAD::WAGNERCOFFILFri Aug 11 1995 11:364
	I just searched the PW V5.1 kit and this driver is not included
	therefore it is not supported. I would still ask the PW group.
Barb
2614.6Problem Solved!ANGLIN::CLAYTONMerlin Clayton (314)947-6763Mon Aug 14 1995 17:5318
Problem solved!

From the original NET.CFG file that I posted in note .0, it required 2
changes:
	1. the ethernet frame type had to be Ethernet_II NOT Ethernet_802
	2. a "PROTOCOL" statement for ARP had to be added to the LINK
	   DRIVER section.

The Novell support group was able to help find and fix the problem.

Barb, Thanks for your input and assistance.


Regards,

Merlin