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

Conference ranger::pathworks_netware

Title:PATHWORKS for OpenVMS (NetWare) Conf.
Notice:Shipping on OpenVMS/Alpha and OSF/1 - ECOs=314.* - Kits=21.*
Moderator:DELNI::GORCZYCA
Created:Wed Nov 04 1992
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:805
Total number of notes:2930

783.0. "PW/NTWR 1.0d ec02 One Frame works another Doesn't" by VMSNET::A_MALLORY () Mon Feb 10 1997 19:42

Hi,

My customer is running DECNET/OSI Phase 4 on a 2 node cluster that shares
the same system disk.

The customer is running pw/ntwr on both nodes, 2 different node names, same
frame types and external net number.

Each node was configured for ethernet_II on a exa controller.

They took the cluster down and restarted and since then one node will not
come up.

Both nodes point to the same system disk.  They are configured exactly
alike except one node has the license server and the other doesn't.

When the second node comes up it gets this error:

PWVN$STACK.LOG :




DL_errono 0 dl_unix_errno 20

:error 0

NSPD: Configurelan: adaptor ethernett_II function failed....

We are at a impase, we can start ethernet_802.2 on the server and he is ok
but not ethernet_II, is there some reason that in the upper layer of the
stack that a link to the ethernet_ii would fail.

Since OSI and tcp/ip work fine on this controller should he reinstall?

Andrea
T.RTitleUserPersonal
Name		DateLines
783.1What was changed?CPEEDY::COOKJust say NO to that AccViO! - Java!!!Tue Feb 11 1997 12:399
    
    Are you sure that they are not configured for 802.3-raw?  802.3-raw
    is incompatible with DECNet/OSI, and fails exactly as you describe
    when NetWare is started.  (See note 676.)
    
    What has been changed?  (i.e. why did it come up ok before this
    incident?)
    
    						Dave
783.2Both were originally set to Ethernet_iiVMSNET::A_MALLORYTue Feb 11 1997 16:1621
Thanks for the reply but both were set to Ethernet_II originally, I did see the
notes and we discussed that he could not use 802.3 raw with decnet/osi.  He has
never tryed to use 802.3 period.

He says that he took the server down normally for routine maintenance but did
not change anything. Then the server would not come back up under that frame
only the 802.2 frame.

It really looks like the decnet/osi problem but I walked through the
configuration with him to make sure, and he had another node configured the same
with decnet/osi and ethernet_ii and it works fine.

Not sure where to go with this, unless the trouble is building a stack on top of
the pre-existing ethernet_ii frame that he is using for tcp/ip.  I could
recommend reinstallation but since he runs on the other node and they share a
system disk, I hesitate, why would one come up and not the other?

Could this be hardware?

Andrea
783.3Need more info...CPEEDY::COOKJust say NO to that AccViO! - Java!!!Wed Feb 12 1997 14:1024
    
    >>unless the trouble is building a stack on top of
    >>the pre-existing ethernet_ii frame that he is using for tcp/ip.
    
    	Why do you suspect that TCP/IP has something to do with the
    problem?  (Is this UCX or someone else's TCP/IP?  Do they not
    run TCP/IP on the other node that is working?)
    
    >>Could this be hardware?
    
    	I doubt it, assuming that this lan adapter is running
    	other protocols just fine.  To find out:
    
    	Please provide the following info from both nodes:
    
    	(1) Complete contents of the PWVN$STACK.LOG files.
    
    	(2) Output from the command:
    
    		$ analyze/system
    		SDA> show lan
    
    
    						Dave
783.4Ethernet_IIVMSNET::A_MALLORYThu Feb 13 1997 15:3225
Yes, we are sure that it is Ethernet_II, we went through the configuration
together and selected option #5 ethernet_ii dix.

They the pwvn$config program trys to start the process and it gives error:

Starting IPX DAEMON NPSD exited...


Process did not start completely, check configuration, Logfile, and the operator
log.

Logfile is PWVN$stack.log
Error - failed to start IPX DAEMON (NPSD)
aborting startup procedures did not complete and the PWVN$stack.LOg gives same
error as note.

Bind acknowlegement failed:

DL_errono 0 dl_unix_errno 20

:error 0

NSPD: Configurelan: adaptor ethernett_II function failed....
783.5802-3 reply from customerVMSNET::A_MALLORYThu Feb 13 1997 17:11264
Dave this is the reply from the custstomer:
13-FEB-1997 09:21:12.48 Attempting to open netbios/streams/ipx
13-FEB-1997 09:21:12.66 NPSD: Building lower mux...
13-FEB-1997 09:21:12.76 NPSD: Configuring Internal Lan
13-FEB-1997 09:21:12.85
NPSD: Configuring Internal Network: 00331010
13-FEB-1997 09:21:12.92 NPSD: Configured Internal Network:  00331010
13-FEB-1997 09:21:12.98 NPSD: Configuring LAN 1
13-FEB-1997 09:21:13.09
NPSD: Configuring: LAN 1 00331000 netbios/streams/dlpi1 0 EXA  ETHERNET_II
PAD_
AND_ADD_SAP
13-FEB-1997 09:21:13.15 NPSD: Configuring for physical controller
13-FEB-1997 09:21:13.22 NPSD: Configuring adapter...
13-FEB-1997 09:21:13.28 NPSD: doing bind protocol request
13-FEB-1997 09:21:13.38 NPSD: Putting message on data-link device
13-FEB-1997 09:21:13.45 NPSD: Getting message from transport
13-FEB-1997 09:21:13.52 NPSD: Back from getmsg, checking response
13-FEB-1997 09:21:13.58 NPSD: Bind-ack failed
13-FEB-1997 09:21:13.65 NPSD: dl_errno 0 dl_unix_errno 20
: error 0
13-FEB-1997 09:21:13.75 NPSD: ConfigureLan: adapter type ETHERNET_II function
fa
iled
%NONAME-F-NOMSG, Message number 00000004
  DGOULDHE     job terminated at 13-FEB-1997 09:21:13.90

  Accounting information:
  Buffered I/O count:              93         Peak working set size:     793
  Direct I/O count:                55         Peak page file size:      5341
  Page faults:                    849         Mounted volumes:             0
  Charged CPU time:           0 00:00:00.23   Elapsed time:     0 00:00:02.56

SL$
SL$
SL$ anal/sys


VAX/VMS System analyzer

SDA> sh lan
LAN Data Structures
-------------------
                -- LAN Device Summary 13-FEB-1997 10:52:23 --

LAN block address  = 93AD85C0  (1 stations)
LAN flags:  0002 LAN_init
SDA>
LAN Data Structures
-------------------
LSB address  = 93B466C0
Device state = 001B Inited,Run,Ctl_Rdy,Timer

                 -- EXA Unit Summary 13-FEB-1997 10:52:24 --

UCB     UCB Addr  Fmt   Value           Client     State
---     --------  ---   -----           ------  -----------
EXA0    93AB2680
EXA2    93AB3180  Eth   60-03           DECNET  0017 Strtn,Len,Uniq,Strtd
EXA3    93AB3700  Eth   60-01           MOPDL   001F
Strtn,Len,Uniq,Share,Strtd
EXA4    93AB39C0  Eth   90-00           LOOP    001D Strtn,Uniq,Share,Strtd
EXA5    93AB44C0  Eth   60-04           LAT     0015 Strtn,Uniq,Strtd
EXA9    93A10DC0  Eth   08-00           TCPIP   0015 Strtn,Uniq,Strtd
EXA11   93A0DF40  Eth   08-06           ARP     0015 Strtn,Uniq,Strtd
EXA14   93A11CC0  Eth   81-37                   0015 Strtn,Uniq,Strtd
EXA16   93A87B80  Eth   81-37                   0004 Uniq
EXA18   93AB4200  Eth   80-41           LAST    0015 Strtn,Uniq,Strtd
EXA19   939A6E80  Eth   81-37                   0004 Uniq
EXA21   93A28900  Eth   81-37                   0004 Uniq


    Press RETURN for more.
SDA>
LAN Data Structures
-------------------
EXA22   93A61E00  Eth   81-37                   0004 Uniq
EXA23   93A21580  Eth   81-37                   0004 Uniq
EXA24   93A64D40  Eth   81-37                   0004 Uniq
EXA26   93ADACC0  Eth   81-37                   0004 Uniq
EXA27   93B67300  Eth   81-37                   0004 Uniq
EXA28   93A9D1C0  Eth   81-37                   0004 Uniq
EXA40   93B34500  Eth   80-40           BIOS    0015 Strtn,Uniq,Strtd
EXA41   93B239C0  Eth   81-37                   0004 Uniq
EXA43   93A5B180  Eth   81-37                   0004 Uniq
EXA44   939FE800  Eth   81-37                   0004 Uniq
EXA45   93AC8AC0  Eth   81-37                   0004 Uniq
EXA47   93AA53C0  Eth   81-37                   0004 Uniq
EXA53   939CD3C0  Eth   81-37                   0004 Uniq
EXA55   93CB8700  Eth   81-37                   0004 Uniq
EXA57   93AAB300  Eth   81-37                   0004 Uniq
EXA58   93C6BCC0  802   E0                      0017 Strtn,Len,Uniq,Strtd

SDA>
SDA>
SDA>
SDA>  Exit
SL$ multinet version 3.5
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
 \VERSION\
SL$
SL$

  System GRUMPY is a VAX 7000-710 running VMS V6.1.
  (HW Ver=01A000000000000017000201, SID=17000201, XSID=01400201, DSN=V1.2)

H$ anal/sys


VAX/VMS System analyzer

SDA> sh lan
LAN Data Structures
-------------------
                -- LAN Device Summary 13-FEB-1997 10:33:17 --

LAN block address  = 87EE2EC0  (1 stations)
LAN flags:  0002 LAN_init
    Press RETURN for more.
SDA>
LAN Data Structures
-------------------
LSB address  = 880335C0
Device state = 001B Inited,Run,Ctl_Rdy,Timer

                 -- EXA Unit Summary 13-FEB-1997 10:33:18 --

UCB     UCB Addr  Fmt   Value           Client     State
---     --------  ---   -----           ------  -----------
EXA0    87EC1E40
EXA2    87EC2C00  Eth   60-03           DECNET  0017 Strtn,Len,Uniq,Strtd
EXA3    87EC2680  Eth   60-01           MOPDL   001F
Strtn,Len,Uniq,Share,Strtd
EXA4    87EC3180  Eth   90-00           LOOP    001D Strtn,Uniq,Share,Strtd
EXA5    87EC3C80  Eth   60-04           LAT     0015 Strtn,Uniq,Strtd
EXA11   87E4BA00  Eth   80-41           LAST    0015 Strtn,Uniq,Strtd
EXA17   87F85940  Eth   80-40           BIOS    0015 Strtn,Uniq,Strtd
EXA18   87F89AC0  Eth   81-37                   0015 Strtn,Uniq,Strtd

SDA>
SDA>  Exit
H$ set defa pwvn$logfiles
H$ type pwvn$stack.log
H$ type pwvn$stack.log
$!********************************************************************
$!*                                                                  *
$!* SYS$MANAGER:SYLOGIN.COM                                          *
$!*                                                                  *
$!********************************************************************
$!
$!
$! This command procedure is always run when anybody on the entire system
$! logs in. It is equivalent to LOGIN.COM except that the instructions
$! contained herein are executed everytime anyone on the VMS system
$! logs in to their account.
$!
$! For interactive processes, turn on Control T, and set the terminal type
$!
$       SET NOON
$       DEFINE SHUTDOWN$INFORM_NODES "HAPPY"
$       NODE_NAM = F$GETSYI("NODENAME")
$       IF NODE_NAM .EQS. "HAPPY"
$       THEN
$!       SPSS LOGICALS
$          SPSS         :==  $ SPSS
$          SPSSB        :==  $ SPSSB
$          SPSS_GRAPH   :== "@SPSSSHR:SPSS_GRAPH X"
$!         @SYS$SYSROOT:[SYSMGR]SPSSGRAPHICS.COM
$       ENDIF
$       MODE = F$MODE()
$       THRUWAY :== $THRUWAY
$       IF MODE .EQS. "NETWORK" THEN EXIT
$       IF MODE .EQS. "BATCH"
$       ENDIF
$       IF (MODE .EQS. "INTERACTIVE")
$       ENDIF
$!
$! For MicroVAX systems only, use the command INSTALL/COMMAND
$! and MOUNT/NOASSIST.
$!
$       IF (.NOT. F$TRNLNM("SYS$MICROVAX")) THEN GOTO SKIP_MICROVAX_COMMANDS
$ SKIP_MICROVAX_COMMANDS:
$!
$! Place your site-specific LOGIN commands below
$!
$       SAY = "WRITE SYS$OUTPUT"
$       SAY ""

$       myuic=f$getjpi(0,"UIC")
$       myuic   = F$IDENT(F$GETJPI(0,"USERNAME"),"NAME_TO_NUMBER")
$       myuic   = F$FAO("!%U",myuic)
$       if myuic .eqs. "[10,7]" then goto NEXT
$ NEXT:
$       GOSUB HAPPY
$ HAPPY:
$       READ/PROMPT="                    PRESS RETURN TO CONTINUE" SYS$OUTPUT
DU
MMY
%RMS-F-FAC, record operation not permitted by specified file access (FAC)
$       IF (MODE .EQS. "INTERACTIVE")
$       ENDIF
$       SET PROMPT="H$ "
$       IF  f$getjpi(0,"GRP") .nes. %o20 then return
$       set noverify
13-FEB-1997 09:12:08.95 NPSD: Novell Protocol Suite Streams Architecture
daemon.

13-FEB-1997 09:12:09.09 Attempting to open netbios/streams/ipx
13-FEB-1997 09:12:09.22 NPSD: Building lower mux...
13-FEB-1997 09:12:09.34 NPSD: Configuring Internal Lan
13-FEB-1997 09:12:09.46
NPSD: Configuring Internal Network: 03310032
13-FEB-1997 09:12:09.55 NPSD: Configured Internal Network:  03310032
13-FEB-1997 09:12:09.66 NPSD: Configuring LAN 1
13-FEB-1997 09:12:09.82
NPSD: Configuring: LAN 1 00331000 netbios/streams/dlpi1 0 EXA  ETHERNET_II
PAD_
AND_ADD_SAP
13-FEB-1997 09:12:09.91 NPSD: Configuring for physical controller
13-FEB-1997 09:12:10.02 NPSD: Configuring adapter...
13-FEB-1997 09:12:10.11 NPSD: doing bind protocol request
13-FEB-1997 09:12:10.21 NPSD: Putting message on data-link device
13-FEB-1997 09:12:10.32 NPSD: Getting message from transport
13-FEB-1997 09:12:10.41 NPSD: Back from getmsg, checking response
aa:0:4:0:8:4:
13-FEB-1997 09:12:10.53 NPSD; Configuring additional protocol modules...
13-FEB-1997 09:12:10.65 NPSD: Pushing ipxe with
13-FEB-1997 09:12:10.75 NPSD: Linking ipx to the DLPI Device
13-FEB-1997 09:12:10.85 NPSD: Notifying IPX of LAN info
13-FEB-1997 09:12:11.04 NPSD: Configured:  LAN 1 00331000
netbios/streams/dlpi1
 0 EXA  ETHERNET_II  PAD_AND_ADD_SAP
13-FEB-1997 09:12:11.13 NPSD: Configuring LAN 2
13-FEB-1997 09:12:11.27 NPSD: Configuring LAN 3
13-FEB-1997 09:12:11.41 NPSD: Configuring LAN 4
13-FEB-1997 09:12:11.52 NPSD: Configuring LAN 5
13-FEB-1997 09:12:11.64 NPSD: Configuring LAN 6
13-FEB-1997 09:12:11.75 NPSD: Configuring LAN 7
13-FEB-1997 09:12:11.90 NPSD: Configuring LAN 8
13-FEB-1997 09:12:12.02 NPSD: Configuring LAN 9
13-FEB-1997 09:12:12.14 NPSD: Configuring LAN 10
13-FEB-1997 09:12:12.26 NPSD: Configuring LAN 11
13-FEB-1997 09:12:12.37 NPSD: Configuring LAN 12
13-FEB-1997 09:12:12.49 NPSD: Configuring LAN 13
13-FEB-1997 09:12:12.62 NPSD: Configuring LAN 14
13-FEB-1997 09:12:12.77 NPSD: Configuring LAN 15

NPSD: Lan  Network   Node           Mux ID    State   Stream
NPSD: ---  --------  ------------  --------  -------  ------
NPSD:   0   3310032   0 0 0 0 0 1         0  UNBOUND    OK
NPSD:   1    331000  AA 0 4 0 8 4         A   IDLE      OK
13-FEB-1997 09:12:12.89 NPSD: Building lower mux complete!
13-FEB-1997 09:12:12.98 NPSD: Start Sap daemon
13-FEB-1997 09:12:13.08 NPSD: Spawning the SAP daemon "./sapd"
13-FEB-1997 09:12:15.53 NPSD; Sap daemon started
13-FEB-1997 09:12:15.93 NPSD: Building upper mux
13-FEB-1997 09:12:16.09 NPSD: Including SPX Version 3.0.1
13-FEB-1997 09:12:16.20 NPSD: Building upper mux complete...

This is all the information from the customer, hope it help resolve his problem.

Chet Sulek
dtn:343-2758
783.6Whose TCP/IP is being used?CPEEDY::COOKJust say NO to that AccViO! - Java!!!Fri Feb 14 1997 15:1225
    
    IPX using ETHERNET_II frame-type maps to Fmt value 81-37.  There
    are *many* instances of EXA-devices mapped to 81-37 (e.g. EXA14,
    EXA16, EXA19, EXA21, etc, etc.)  There should be only one.
    
    A guess would be that there might be competing products trying
    to register the IPX protocol type on the EXA adapter (since I
    have never seen any failure mode of the PATHWORKS NetWare transports
    that created anything like this).
    
    (My fellow transport developer's guess is that they are using
    Progress's TCP/IP product (rather than UCX), and they have
    mistakenly configured it's IPX feature...if so, have them
    disable that.)
    
    Hope this helps...
    
    
    						Dave
783.7Thanks for the helpTOHOPE::WSA128::MALLORY_ATue Mar 04 1997 12:589
DAVE,

Thanks, you were right when I finally convinced the customer that is TCP/IP
product might include IPX we did analyse/system and show lan and sure enough
8137 ipx was lurking back at us....

Thanks again, I was not aware of this product...... It is called TCPWARE.

Andrea