| 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 |
Polycenter Console Manager - URGENT ISSUE
SUBJECT: PCM Fails to Communicate with 2nd Network Board
ENVIRONMENT: PCM V1.6-126 under VMS V6.1
PROBLEM: PCM will NOT communicate over the SECOND Network Controller
SYMPTOM:
PCM is used to communicate with LAT connections to more than one
extended LAN. This requires at least TWO Network Interconnect (NI) I/O
controllers for the network connections, one for each extended LAN.
PCM will initiate LAT connections to terminal servers ONLY OVER THE
FIRST LAT LINK CONNECTION THAT IS DEFINED IN THE LAT$SYSTARTUP.COM
procedure.
EXAMPLE:
SYS$MANAGER:LAT$SYSTARTUP.COM
$! ------------------------- Start LAT Protocol --------------------------
$!
$ lcp create link csc$link /device=exa0: /decnet
$ lcp create link cx1$link /device=eta0: /decnet
$ lcp set node /state=on
In this example, PCM will initiate connections over the link on the
EXA0: device. It will NOT initiate (or very seldom initiate)
connections on the ETA0: device.
If the two commands are reversed in order, only the first defined link
will be used by PCM, and connections would be made to the ETA0:
network.
OBSERVATION:
This USED to work OK on previous (patched) versions of PCM.
Jim Lind
CCS - CXO3 Datacenter Support
DTN 592-4099
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1291.1 | INCREASE Console Open Timeout | BSS::LIND | Jim Lind; 592-4099 CX03-1/N14 CNMC-West | Fri May 03 1996 14:00 | 30 |
The CXO3 PCM system has over 250 systems connected, with almost all
of them on the FIRST network controller.
PCM needs more time to establish console connections over multiple
LAT lines and where there are a large number of systems to connect to.
The "FIX" is to change the "hidden" parameter for "Console Open Timeout"
from the default value to a much larger number.
$ CONSOLE EDIT /INTERFACE=CHARACTER
PCM Edit> show hidden
Max. configurable Systems = 400 systems
Systems per controller = 4 systems
Console Open Timeout = 90 seconds
Monitor interval = 150 seconds
TELNET Status Timeout = 15 seconds
Buffer size = 256 bytes
Nulls in data stream will be ignored
Notice that "Console Open Timeout" has been increased to 90 seconds.
This will allow more time for PCM to connect to LAT devices on the
2nd NI controller.
Thanks to Dan Butterworth of the Customer Support Center for providing
this solution to the problem.
Jim Lind
| |||||