[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

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

555.0. "Inter-Networking a VAXFT" by CTUADM::COOKE (Vern Cooke @CTU (Western Canada CNS)) Thu Jan 12 1995 22:10

Hello:

We have a requirement to connect a system into Console Manager that is a)
physically remote and b) on a network that cannot be interconnected with the
network the PCM node is located on. Here is a description of the architecture I
plan to use plus the configuration details:

  +...............+           +..................+
  :               :           :                  :
  :  fault~~~~~D  :           :  D~~~D           :
  :  tlrnt~~~~~S-----------------S~~~S------+--  :
  :            1  :   WAN     :  2   3      |    :
  +...............+           :            PCM   :
   Remote Bldg                :                  :
                              +..................+
                               Local Bldg

In this architecture, both serial consoles from the Fault Tolerant VAX would be
hard wired into a local DECserver, DS1. The ports on this DECserver would be
identically configured in a manner as specified in the PCM documentation. The
LAN the DECserver is located on is connected between the remote and local
buildings over a WAN.

In the local building are two back-to-back DECservers, DS2 and DS3, one on each
LAN. The ports on these DECservers would also be identically configured
according to the PCM documentation. The ports on DS3 would be the ports that
appear in PCM's configuration database.

In order to achieve a "transparent" connection to the fault-tolerant's console
ports from DS3, the ports on DS1 and DS2 would be configured to auto-connect to
each other.

My questions are:
1) Is this a valid method of establishing a connection from PCM to the console
   ports on the fault tolerant?
2) Are there any special port or DECserver settings that are needed (over and
   above the auto-connection requirements)?
3) What special configuration details are needed in PCM to handle the two
   console ports on a fault-tolerant VAX, given that fault tolerants tend to
   not like ANY discrepency (characteristics, timing, etc) between the
   terminals connected to their console ports?

Any help would be appreciated.
						Thank you,
							....... Vern.

T.R	Title	User	Personal Name	Date	Lines
555.1		CSC32::BUTTERWORTH	Gun Control is a steady hand.	`Thu Jan 12 1995 22:54`	32
	>1) Is this a valid method of establishing a connection from PCM to the console > ports on the fault tolerant? I think you could simplify it somewhat with maybe DECMux's and a T1 line. The decmux on the PCM engine side would make the connection to it's conterpart on the remote side so you only got two boxes and a T1 line to worry about. >2) Are there any special port or DECserver settings that are needed (over and > above the auto-connection requirements)? I can't think of any. >3) What special configuration details are needed in PCM to handle the two > console ports on a fault-tolerant VAX, given that fault tolerants tend to > not like ANY discrepency (characteristics, timing, etc) between the > terminals connected to their console ports? Your going to want a large type-ahead buffer. I would increase SYSGEN param TTY_ALTYPAHD. Ifd you have the memory resources to support it crank it up to 32K and TTY_ALTALARM to 12K. Bear in mind that each system PCM configures will get a 32K type-ahead buffer and that this space will be allocated from non-paged pool. The philosophy here is to allow the FT's to be able to xmit data with flow control kept to a minimum and to give PCM more room to breathe as well. Regs, Dan Any help would be appreciated. Thank you, ....... Vern.
555.2	Clarification	CTUADM::COOKE	Vern Cooke @CTU (Western Canada CNS)	`Fri Jan 13 1995 14:38`	23
	Hi Dan! re .1 1,2) The communications have already been in place for a few years and the FTs are connected to local terminals. We want manage the FTs from our location and intend to make use of existing hardware (like the DECservers). My question should be: Can PCM communicate across DECservers arranged in this fashion? Would it still be possible to transmit a "BREAK" from PCM through the DECservers to the managed system? 3) I'll increase these parameters. Thanks for the info. BTW: It seems that having an icon (VAXFT_3000_DUAL.XBM) for an FT is moot since it can never be used. You would have to configure two separate systems in console manager each with their own icon for each FT zone (probably VAX_4000.XBM). Using the dual icon for each zone of the FT would give the appearance of four FT zones rather than two. Just an observation. Thanks for the quick response Dan. I'd appreciate your thoughts on my revised questions in 1,2 above. ....... Vern.
555.3		CSC32::BUTTERWORTH	Gun Control is a steady hand.	`Fri Jan 13 1995 22:58`	14
	> My question should be: Can PCM communicate across DECservers > arranged in this fashion? Would it still be possible to transmit a > "BREAK" from PCM through the DECservers to the managed system? Unfortunatley you won't be able to xmit a break all the way through to the other end. It'll stop when it hits the 2nd server on the PCM engine side. You'll get characters through but not a "break". What model of FT system are these things? I ask because I "believe" the later FT systems (4000 based and up) could be set to use ctrl-p instead of break for the halt "character" but I can't swear to it. Regards, Dan
555.4	VAXFT-410	CTUADM::COOKE	Vern Cooke @CTU (Western Canada CNS)	`Mon Jan 16 1995 16:10`	7
	Hi Dan: The system is a VAXFT-410. I'll also look into the possibility of using Ctrl-P instead of break (with a local terminal, break was always so convenient!). Thanks for the info, ......... Vern.