[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
|
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
528.0. "PCM Problem - System REBOOT Required" by BSS::LIND (Jim Lind; 592-4099 CX03-1/N14 CNMC-West) Tue Dec 20 1994 23:52
PROBLEM - PCM Becomes LOCKED UP and entire system must be rebooted.
OpenVMS VAX V6.1 - PCM V1.5-002
On three occasions now, there are circumstances where PCM will
not RECONFIGURE, and attempts to restart PCM will result in the
PCM system NOT able to connect to MOST consoles. The entire VAX
must be rebooted.
On the latest problem, output from a PC comm port was being
connected to PCM for logging. Initially, there was a speed and/or
parity mismatch. I suspect that some "garbage" got into the
log file.
It appeared that the PCM system would not log data, but in reality
it is suspected that the Term Server port needed to be logged out.
So it was, but the problem did not go away.
Attempts to MONITOR the log file caused the terminal screen to
be blanked out, and nothing else appeared - the monitor software
would not format the screen - just hung. After this hang, other
systems could not be monitored either, same "blank screen".
Tried to reconfigure PCM - it hung.
Tried to shutdown PCM - no joy, as it complained "reconfigure was in
progress", even when the process doing the reconfigure had been
STOP /ID.
Tried to stop all CONSOLE processes - no problem - all dead.
Tried to restart PCM - seemed OK, but would not connect to MOST
consoles terminal servers. All looked OK on the system, just PCM
would not connect properly.
Rebooted VAX system - deleted problem log file, and PCM started OK
and worked OK.
As I have said, this is the THIRD occasion of having to reboot
the entire system in order to get PCM to function properly.
Apparently, most problems are associated with a reconfigure where
many changes have been made to EXISTING devices, or where there is
a problem with the log file have "garbage" characters in it.
Jim Lind
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 528.1 | Try stopping LAT or deleting ports? | ULYSSE::WEISSBECK | | Wed Dec 21 1994 08:30 | 11 |
| Hello,
I got the same kind of problem on a big custumer site: having to reboot
to get access again to the console.
It seems that when you stop PCM process the LAT connection in not
correctly broken, avoiding PCM to have access to most of the console
lines. The shutdown will stop LAT. Perhaps stopping only lat or
deleting LTA ports could help (as a workaround)?
Jean-Marie
|
| 528.2 | NODE Reconfigure Porblem Persists | BSS::LIND | Jim Lind; 592-4099 CX03-1/N14 CNMC-West | Tue Jan 03 1995 19:34 | 48 |
| OpenVMS V6.1 w/PCM V1.5-002
PROBLEM: PCM Failure to RESTART after Node Changes
The problem with PCM lockup and failure to restart is a REAL issue.
Further investigation indicates the following is generally true:
(1) PCM will NOT deal effectively with changes in terminal server
assignments for EXISTING nodes.
(2) PCM will NOT delete LAT ports assigned to nodes that have
their server or port assignments CHANGED.
(3) After CHANGING node terminal server or port assignments, PCM
may not RESTART properly without a system reboot.
ANALYSIS:
You find that two systems are swapped and need reassignment of
terminal server assignments. Perhaps this is as simple as exchanging
the terminal server and/or port assignments on PCM for two problem
nodes.
You RECONFIGURE, and note that PCM will NOT connect to the two nodes
that were changed for terminal server info.
You shutdown PCM (CONSOLE SHUT), and LATCP shows that the same two
port assignments are NOT deleted. So, you delete them in LATCP with
a DELETE PORT command.
You restart PCM and note that it will not startup properly, either
not starting the console processes or failing to connect to MANY
systems.
THERE IS NO WAY THAT I KNOW OF TO RECOVER FROM THIS SITUATION -
A reboot of the system is often necessary.
WORKAROUND:
If you are going to CHANGE existing terminal server assignments for
a node, FIRST DELETE THAT NODE, RECONFIGURE and then re-add the node.
Generally, RECONFIGURE after node ADDITIONS or DELETE works OK.
RECONFIGURE after node CHANGES for terminal server info generally
results in a problem, as indicated above.
Jim Lind
|
| 528.3 | | OPG::PHILIP | And through the square window... | Wed Jan 04 1995 10:44 | 9 |
| Jim,
Reconfiguration in this area is know to have some problems, these
unfortunately require too much work for a patch kit, so, I am afraid that you
are going to have to wait until the next release of the product before you
see these problems go away.
Cheers,
Phil
|