[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

1110.0. "Console ports on HSD30 & HSJ40 lock up" by 42441::WYKESJ () Wed Nov 29 1995 11:10

I have a customer who has reported problems connecting to his HSD's and HSJ's
from PCM.

He has found that when he tries to connect and then types some characters while
PCM is connecting to the HSD/J (before the status bar disappears) the console
port locks and can only be unlocked by resetting the controller. If he waits
until the status bar disappears before entering characters the port does not
lock up.

PCM version is V1.6-111
HSD version is V25D
HSJ version is V25J

Does anyone have any ideas as to why this is happening ?

Justin Wykes
CSC/UK

T.R	Title	User	Personal Name	Date	Lines
1110.1		29067::BUTTERWORTH	Gun Control is a steady hand.	`Wed Nov 29 1995 13:41`	5
	Huh? That makes no sense at all. Are you using a DECServer for the connection to the console port and if so are you using LAT or TELNET? Regs, Dan
1110.2		42441::WYKESJ		`Fri Dec 01 1995 08:34`	15
	The customer is using LAT through a XYPLEX MN1500 Terminal Server. Connecting to VAX's or even a HSC95 works OK. It doesn't matter how he connects, whether if its from MB3 on the system icon or doing a console connect, the same problem occurs. The controller still works OK, it's just the port that locks. Even connecting a terminal on the port doesn't work. Any ideas ? Justin.
1110.3		29067::BUTTERWORTH	Gun Control is a steady hand.	`Fri Dec 01 1995 14:06`	26
	>The customer is using LAT through a XYPLEX MN1500 Terminal Server. >Connecting to VAX's or even a HSC95 works OK. Could you try a real decserver by any chance? I had had problems with XYPLEX terminal servers and I'd really like them to try a real decserver. The point here is that we have sites connected to all forms of the StorageWorks controllers with no problems. I have done it using a DS200 with no problems. >It doesn't matter how he connects, whether if its from MB3 on the system >icon or doing a console connect, the same problem occurs. Just as an FYI, there is no difference between these two methods other than the method used to start. The same image runs: CONSOLE$CONMON.EXE so no surprise. What do you mean you connect a terminal tot he port and it still doesn't work? Are you unplugging the HSJ and plugging a terminal into the HSJ console or are you plugging the terminal into the server port? Is there a SHOW PORT x STATUS command on the XYPLEX server? This would be done from the equivalent of the local prompt on the XYPLEX. What Im interested to know is if it shows input or output is XOFF'D. Regs, Dan
1110.4		42441::WYKESJ		`Thu Dec 07 1995 10:59`	15
	Correction from last message. The customer is actually using TCPIP not LAT. All their servers are XYPLEX. They don't have any real ones. The customer did a SHOW PORT x STATUS the flow control was X/ON. Orther settings checked OK. I noticed a STARS article - [PLY_CM] PCM Does Not Attempt To Re-open Failed TELNET Connections and got the customer to check the CONTROLLER_xx.LOG. The only error within this file was "CM host to controller error CB code -196 error code 0 " Does this mean anything ? Justin.