| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
Do I need NETBEUI transport? We are running Pathworks V5.0-D in a OpenVMS V6.2-1H2 cluster and are required to minimize the number of transport to TCP/IP only. On one of the nodes, Pathworks is nicely running with TCP/IP as the only transport protocol. On the other server node, Pathworks will startup but a few minutes later some of the previously started processes will just die, without any log in pwrk$logs. After that, you cannot log into the admin account (the server process is not running). Please, see the snapshots of the show system command right after the Pathworks startup and some minutes later. I'm mostly puzzled by the fact, that one cluster member just needs TCP/IP, while the other member needs both TCP/IP and NETBEUI! I'd be grateful for any explanation. Regards, Herbert Output show system right after Pathworks startup: SYSTEM_ASR2> @sys$startup:pwrk$startup PATHWORKS file server will use TCP/IP. PATHWORKS mail notification will use DECnet. Process NETBIOS created with identification 20800253 Process PWRK$KNBDAEMON created with identification 20800256 Process PWRK$LICENSE_R created with identification 20800259 The PATHWORKS V5.0D server is configured to support 50 PC clients. Process PWRK$MASTER created with identification 2080025E The master process will now start all other PATHWORKS processes. SYSTEM_ASR2> show system OpenVMS V6.2-1H2 on node ASR2 30-MAY-1997 19:08:01.75 Uptime 0 01:43:03 Pid Process Name State Pri I/O CPU Page flts Pages 20800201 SWAPPER HIB 16 0 0 00:00:11.15 0 0 20800205 CONFIGURE HIB 10 29 0 00:00:00.05 44 29 20800207 IPCACP HIB 10 8 0 00:00:00.02 28 39 20800208 ERRFMT HIB 7 101 0 00:00:00.16 46 59 20800209 CACHE_SERVER HIB 16 3 0 00:00:00.03 24 33 2080020A CLUSTER_SERVER HIB 10 15 0 00:00:00.28 55 81 2080020B OPCOM HIB 7 1295 0 00:00:00.68 79 39 2080020C AUDIT_SERVER HIB 8 182 0 00:00:00.44 147 165 2080020D JOB_CONTROL HIB 9 85 0 00:00:00.08 46 64 2080020E SHADOW_SERVER HIB 6 7 0 00:00:00.01 28 36 2080020F SECURITY_SERVER HIB 10 30 0 00:00:00.17 297 271 20800210 SMISERVER HIB 9 36 0 00:00:00.11 124 140 20800211 NETACP HIB 10 529 0 00:00:00.48 49 86 20800212 EVL HIB 6 44 0 00:00:00.07 90 91 N 20800213 REMACP HIB 8 9 0 00:00:00.02 26 14 20800214 LATACP HIB 12 11 0 00:00:00.18 68 53 20800215 UCX$LPD_QUEUE HIB 4 54 0 00:00:00.15 227 110 20800216 UCX$INET_ACP HIB 9 54 0 00:00:00.14 115 83 20800217 UCX$INET_ROUTED LEF 6 38 0 00:00:00.05 86 98 S 20800239 TNSLSNR_KKI2 LEF 5 202 0 00:00:00.27 268 219 2080023A DECW$SERVER_0 HIB 6 1511 0 00:00:12.75 683 785 2080023B DECW$SESSION LEF 6 377 0 00:00:00.82 947 506 2080023C UCX$TNSYM1 HIB 4 61 0 00:00:00.14 186 132 2080023D SYMBIONT_10 LEF 6 235 0 00:00:00.23 454 132 2080023E SYMBIONT_11 HIB 6 36 0 00:00:00.12 332 54 2080023F SYMBIONT_12 HIB 6 36 0 00:00:00.14 332 54 20800240 SYMBIONT_13 HIB 6 33 0 00:00:00.15 332 54 20800241 SYMBIONT_14 HIB 6 31 0 00:00:00.14 332 54 20800242 LPS_38M713 HIB 4 317 0 00:00:00.19 88 107 20800243 ORA_KKI2_PMON HIB 6 18 0 00:00:00.20 375 412 20800244 ORA_KKI2_DBWR HIB 6 354 0 00:00:02.35 533 521 20800245 ORA_KKI2_ARCH HIB 5 20 0 00:00:00.18 588 303 20800246 ORA_KKI2_LGWR HIB 6 208 0 00:00:00.27 478 541 20800247 ORA_KKI2_SMON HIB 6 52 0 00:00:00.47 1125 579 20800248 ORA_KKI2_RECO HIB 5 16 0 00:00:00.26 787 555 20800249 ORA_KKI2_LCK0 HIB 6 10 0 00:00:03.76 610 694 2080024B DECW$MWM LEF 4 141 0 00:00:01.22 469 335 2080024C VUE$SYSTEM_2 LEF 4 145 0 00:00:00.37 447 74 2080024D VUE$SYSTEM_3 LEF 4 151 0 00:00:00.35 447 75 2080024E DECW$TE_024E COM 4 161 0 00:00:03.49 515 531 2080024F SYSTEM CUR 7 3573 0 00:00:05.98 6488 113 20800250 _FTA5: LEF 4 2303 0 00:00:02.07 1163 63 20800253 NETBIOS HIB 5 29 0 00:00:00.05 56 72 20800259 PWRK$LICENSE_R HIB 8 66 0 00:00:00.17 266 87 2080025E PWRK$MASTER HIB 4 310 0 00:00:00.24 309 85 20800261 PWRK$LMMCP LEF 7 490 0 00:00:00.43 417 476 20800264 PWRK$MONITOR HIB 4 82 0 00:00:00.29 378 48 20800267 PWRK$ADMIN_0 RWAST 5 53 0 00:00:00.15 116 82 2080026A PWRK$LMSRV LEF 9 69 0 00:00:00.20 210 231 2080026D PWRK$LMDMN LEF 7 46 0 00:00:00.20 205 217 Output show system some minutes after Pathworks startup: SYSTEM_ASR2> show system OpenVMS V6.2-1H2 on node ASR2 30-MAY-1997 19:08:07.28 Uptime 0 01:43:09 Pid Process Name State Pri I/O CPU Page flts Pages 20800201 SWAPPER HIB 16 0 0 00:00:11.15 0 0 20800205 CONFIGURE HIB 10 29 0 00:00:00.05 44 29 20800207 IPCACP HIB 10 8 0 00:00:00.02 28 39 20800208 ERRFMT HIB 7 101 0 00:00:00.16 46 59 20800209 CACHE_SERVER HIB 16 3 0 00:00:00.03 24 33 2080020A CLUSTER_SERVER HIB 10 15 0 00:00:00.28 55 81 2080020B OPCOM HIB 7 1300 0 00:00:00.68 79 39 2080020C AUDIT_SERVER HIB 9 186 0 00:00:00.45 147 165 2080020D JOB_CONTROL HIB 10 89 0 00:00:00.08 46 64 2080020E SHADOW_SERVER HIB 6 7 0 00:00:00.01 28 36 2080020F SECURITY_SERVER HIB 10 30 0 00:00:00.17 297 271 20800210 SMISERVER HIB 9 36 0 00:00:00.11 124 140 20800211 NETACP HIB 10 529 0 00:00:00.48 49 86 20800212 EVL HIB 6 44 0 00:00:00.07 90 91 N 20800213 REMACP HIB 8 9 0 00:00:00.02 26 14 20800214 LATACP HIB 12 11 0 00:00:00.18 68 53 20800215 UCX$LPD_QUEUE HIB 4 54 0 00:00:00.15 227 110 20800216 UCX$INET_ACP HIB 9 54 0 00:00:00.14 115 83 20800217 UCX$INET_ROUTED LEF 6 38 0 00:00:00.05 86 98 S 20800239 TNSLSNR_KKI2 LEF 5 202 0 00:00:00.27 268 219 2080023A DECW$SERVER_0 HIB 6 1511 0 00:00:13.14 683 785 2080023B DECW$SESSION LEF 6 377 0 00:00:00.82 947 506 2080023C UCX$TNSYM1 HIB 4 61 0 00:00:00.14 186 132 2080023D SYMBIONT_10 LEF 6 235 0 00:00:00.23 454 132 2080023E SYMBIONT_11 HIB 6 36 0 00:00:00.12 332 54 2080023F SYMBIONT_12 HIB 6 36 0 00:00:00.14 332 54 20800240 SYMBIONT_13 HIB 6 33 0 00:00:00.15 332 54 20800241 SYMBIONT_14 HIB 6 31 0 00:00:00.14 332 54 20800242 LPS_38M713 HIB 4 317 0 00:00:00.19 88 107 20800243 ORA_KKI2_PMON HIB 6 18 0 00:00:00.20 375 412 20800244 ORA_KKI2_DBWR HIB 5 354 0 00:00:02.35 533 521 20800245 ORA_KKI2_ARCH HIB 5 20 0 00:00:00.18 588 303 20800246 ORA_KKI2_LGWR HIB 6 208 0 00:00:00.27 478 541 20800247 ORA_KKI2_SMON HIB 6 52 0 00:00:00.47 1125 579 20800248 ORA_KKI2_RECO HIB 5 16 0 00:00:00.26 787 555 20800249 ORA_KKI2_LCK0 HIB 6 10 0 00:00:03.76 610 694 2080024B DECW$MWM LEF 4 141 0 00:00:01.22 469 335 2080024C VUE$SYSTEM_2 LEF 4 145 0 00:00:00.37 447 74 2080024D VUE$SYSTEM_3 LEF 4 151 0 00:00:00.35 447 75 2080024E DECW$TE_024E COM 4 161 0 00:00:03.51 515 531 2080024F SYSTEM CUR 7 3634 0 00:00:06.03 6527 113 20800250 _FTA5: LEF 4 2303 0 00:00:02.07 1163 63 20800253 NETBIOS HIB 5 29 0 00:00:00.05 56 72 20800259 PWRK$LICENSE_R HIB 8 66 0 00:00:00.17 266 87 2080025E PWRK$MASTER HIB 4 314 0 00:00:00.24 326 102 20800264 PWRK$MONITOR HIB 4 82 0 00:00:00.29 378 48 SYSTEM_ASR2>
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4313.1 | A start... | VMSNET::P_NUNEZ | Mon Jun 02 1997 10:01 | 22 | |
Herbert,
Does the problem system have multiple physical network interfaces (ie,
2 ethernet boards; 1 ethernet, 1 fddi) - whether active or not? To be
sure, go into SDA and do SHOW LAN and press Return a few times:
$ ANAL/SYS
SDA> SHOW LAN
It could be NetBEUI (PWRK$NBDAEMON) is attempting to start over an
inactive device - you may need to define the system logical name
pwrk$netbeui_device to point to the template device of the appropriate
network interface, for example:
$ define/system pwrk$netbeui_device fta0:
Otherwise, look in PWRK$LOGS:PWRK$NBDAEMON_<nodename>.LOG for clues.
Also see if you have process dump files:
$ dir/date pwrk$logs:*.dmp, pwrk$lmlogs:*.dmp
Paul
| |||||
| 4313.2 | ... it was an ucx problem | VDEV01::MAEHNER | Fri Jun 06 1997 02:41 | 13 | |
Hi Paul, Thanks for your mail and suggestions. The system indeed has two ethernet controllers but they are already properly defined the way you suggested. The problem was that the UCX$PWIP_ACP process died after starting up (couldn't get the gethostbyname info) and since Pathworks was only configured to use TCP/IP, the processes building upon the UCX$PWIP_ACP also vanished. Unfortunately, pathworks didn't log that reason in any of the log files! Regards, Herbert | |||||