[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 |
498.0. "Connection Problem after Device RECONFIGURE" by 29633::LIND (Jim Lind; 592-4099 CX03-1/N14 CNMC-West) Wed Nov 30 1994 23:47
SUBJECT: PCM RECONFIGURE may not connect to all nodes under some
circumstances
There is a situation where RECONFIGURE under PCM V1.5 may not connect
to all devices that are CHANGED/RECONFIGURED during the database
setup/edit.
PROBLEM: If a device is currently, successfully connected by PCM
through a specific terminal server and port, any CHANGE in the port or
terminal server assignment will likely cause a connection problem after
a RECONFIGURE.
EXAMPLE: Suppose device ALPHA is connected to server TS1, port VCS01.
You decide to change (reconnect) to terminal server TS2,
port VCS02 and make the change using the Console Manager
Editor.
You then RECONFIGURE with PCM.
PCM does not connect to device ALPHA after the RECONFIGURE.
SOLUTION: Stop PCM with CONSOLE SHUT
Use LATCP to SHOW PORTS. It is likely that you will
have one PORT defined for server TS1, port VCS01 that
PCM did NOT disconnect from.
Use LATCP to DELETE PORT LTAxxxx, the one which is assigned
to the problem server/port.
Restart PCM:
SUBMIT /USER=SYSTEM SYS$STARTUP:CONSOLE$STARTUP
PCM should now connect to the reconfigured device.
It has been noted that in large PCM systems, it may take several
minutes for PCM to successfully connect to all assigned, active
terminal server devices.
Jim Lind
T.R | Title | User | Personal Name | Date | Lines
|
---|