| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4299.1 | Keep lookin' :-) | VMSNET::P_NUNEZ | | Wed May 21 1997 10:00 | 32 |
| Valerie,
Is the server a VAX or Alpha and what's the OpenVMS version?
What IP stack (and version) is installed on the server?
Does EVERY client have multiple sessions?
Have you used:
$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS
$ @NBSHOW KNBSTATUS ! TCP/IP
$ @NBSHOW NBSTATUS ! NetBEUI
to determine the problem is occurring over both NetBEUI and IP? BTW,
the NBSHOW output will display either the server's nodename or PW
cluster alias name under the Local Name column (session status
section) - so you can confirm whether or not the PW cluster alias name
is being used (for NetBEUI and IP anyway, not so for DECnet sessions).
Does $ MC NCP SH K LINE COUNT show send/receive failures, high
collision ratio, user/system buffer unavailable?
Any errors in PWRK$LMLOGS:PWRK$LMMCP_nodename.LOG?
" " " PWRK$LOGS:PWRK$NBDAEMON_nodename.LOG?
" " " PWRK$LOGS:PWRK$KNBDAEMON_nodename.LOG?
" " " SYS$MANAGER:UCX$PWIPACP_nodename.LOG? (if using UCX)
Does $ PWVER ALL show any old versions for PATHWORKS images (especially
the PWRK$STREAMS* images)?
Paul
|
| 4299.2 | | VMSNET::P_NUNEZ | | Wed May 21 1997 10:02 | 5 |
|
Probably should also provide a general (at least) overview of the
network configuration...
Paul
|
| 4299.3 | Also | VMSNET::L_GULICK | Lew Gulick | Wed May 21 1997 10:27 | 25 |
|
Valerie,
Even more questions:
> PC's are hung
Are the PC's not able to fucntion at all? Do they need a hard reboot,
or do you mean they sit forever waiting for a command to complete?
> $net session gives multiple sessions for the same PC
> (about 4 to 10). The username is the right
> username and not GUEST. It doesn't display
> the end of the list because it displays "error 59"
> an unexpected error occured.
> VMS users can work.
> Stop and restart Pathworks : not the solution.
> Reboot is required.
Is that the VMS server you are stopping and restarting? If so, does the
restart show multiple sessions shortly after it comes up? Is the reboot
required a server or client reboot?
Lew
|
| 4299.4 | | AUBER::CORNU | Valerie CORNU - CSC Evry FRANCE | Thu May 22 1997 12:10 | 38 |
| Answers:
Pathworks installed on an ALPHA with OpenVMS V6.2
IP Stack is UCX V3.3 ECO 12
All client don't have multiple sessions. Juste some.
NBSHOW NBSTATUS : Pc's are connected to the node name (not the
Alias name). But the alias name appears
NBSHOW KNBSTATUS : Pc's are connected tot the node name (not
the alis name).
The dcl command mc ncp sh k line count reveals no problem for
send/receive failures, collisions and user/system buffers unavai-
lable.
The customer has a version limit of 3 for the log files so we
didn't have the .logs which correspond to the date when the problem
occured. Whe changed this to keep them for the next time.
$PWVER gives Pathworks V5.0-500E for all the images (PWRK$STREAMS
images are PWRK$STREAMSOS_V6 and PWRK$STREAMSOS_V7).
When the problem occurs, all the PC's are hung.
On the server, if you restart Pathworks, you always see the sessions
on the server. The unique solution is to reboot the alpha.
Network configuration:
Server ---- Decswitch --- Dechub -----PC (Twisted Pair)
It's a new installation because they're in a new building.
Thanks,
Valerie
|
| 4299.5 | | PTGSYS::SWEEP | I want a lolly... | Fri May 23 1997 04:37 | 17 |
| Don't really understand if your seeing a problem.
It could be that 1 client has 2 sessions, 1 to the alias and 1 to the
nodename. Also there could be multi-sessions for a very short time if
a client detected a disconnect (due to NW errors) and the server didn't
notice it. Then client reconnects and the other session will timeout
eventually when the keep alive timer expires.
The other problem that none of the clients do anything looks more like
a real problem. Perform some actions to see if server still runs. Most
of these problems are network related, but it could be that the server
hangs.
- Check process states.
- Check if server responds locally.
- Check the net - IRIS.
Adrie
|