Dears,
First, I'd like to thank
Tim Tahaney,
and Bruce Kelly
for their quick replies.
Indeed, Tim seems having pointed out the problem (suggested to set console
to serial) as my console is set to graphics. I then changed the console to
serial.
It doesn't work though, and when I take a look in /var/adm/messages (the
console log) I can see the "kernel console" is still pointing to "trio0"
(graphical adapter) and the "working well" alpha's have this pointing to
"ace0". Could it be over-written by some other setting? If yes, which one?
What can I check?
I'm getting out of any idea, so...
TIA,
Cedric
----------Original Message--------
Hi Managers,
AS 2100, DU 4.0D - PK2, FW V5.3
We encounter some problems with console connection via terminal server,
using PCM as well as pure telnet connection.
When we use "console connect <alias>" on the PCM box, we get the following
(as usual):
POLYCENTER Console Manager
Connect/Monitor Interface V1.7
Connected to remote console (ECAR2A)
Type CTRL/E to exit or CTRL/G to escape to monitor
But this does not go any furhter, as to say, we don't get the login prompt.
I checked the physical connections, the terminal servers have been rebooted
and connections were interrupted/restored. The terminal server should not be
the cause as disk controller consoles are connected to it as well. PCM
configuration is OK (didn't change it anyway) as if we directly connect with
telnet via the terminal server port, problem is the same.
We updated the firmware to V5.3 (as other boxes working fine are) and as I
saw some mails in the archives about console problems after the same
update... Do you think the problem may come from the firmware update? We
plan to update one machine to V5.4 just in case...
Anybody has an idea?
TIA.
Regards,
____________________
Cedric Van Bellingen
Belgacom - ISD
UNIX System Group - DEC
mailto:cedric.van.bellingen_at_belgacom.be
tel: 02/2445996 fax: 02/2446089
Received on Mon Aug 30 1999 - 10:34:22 NZST