| Title: | ALL-IN-1 (tm) Support Conference |
| Notice: | Please spell ALL-IN-1 correctly - all CAPITALS! |
| Moderator: | IOSG::PYE CE |
| Created: | Fri Jul 01 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2716 |
| Total number of notes: | 12169 |
I recently spoke with a customer with the following problem:
A user reported a problem accessing documents in a shared
drawer. The Manage Server menu showed two of four servers
with a status of stopped. These stopped servers generated a
"%OAFC-W-NETLOST, Network connection to the FCS is lost",
message. The customer was unable to start the FCS and later
discovered that the server process was still running. By the
time the customer had returned to the Manage Server menu, the
status had changed from Stopped to Running/Enabled. This is 77a
four node cluster running VMS V6.1, DECnet OSI phase 5, and
ALL-IN-1 v3.2.
I was not able to find anything on the %OAFC-W-NETLOST error
in STARS.
I would appreciate any help in determining which layer of
DECnet it is that appears to intermitently stop talking to
the FCS.
Larry Ferrell
Atlanta CSC
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2492.1 | Maximum Transport Connections ? | UTRTSC::SCHOLLAERT | Ajax: World Champions 1995 | Wed Jan 29 1997 07:01 | 22 |
Hello,
Looks like they ran out of Maximum Transport Connections...
Check note 1822.
By the way, searching for OAFC-W-NETLOST I found 6 STARS loaded note
entries:
14-{ALL-IN-1-NOTES} Network connection to FCS lost
14-{ALL-IN-1-NOTES} %DSL-E-INVBUF, Invalid buffer
14-{ALL-IN-1-NOTES} LCB AccessAST %SYSTEM-F-UNREACHABLE
14-{ALL-IN-1-NOTES} Hanging server on AXP
14-{ALL-IN-1-NOTES} %OAFC-W-NETLOST, The network connection to the
File Cabin
14-{ALL-IN-1-NOTES} FCS and %MCC-E-FATAL_FW...
Regards,
Jan
| |||||
| 2492.2 | IOSG::STANDAGE | My hovercraft is full of eels | Wed Jan 29 1997 10:30 | 11 | |
Hi Larry,
Jan's comments are indeed the most likely explaination. As the total
network connections fluctuates under and above the maximum allowed, it
will result in the behaviour you describe (running servers accepting
connections, and then the netword rejecting them).
-Kevin.
| |||||