Here is the answers:
Yes it is normal. By default if you attach a terminal server/dumb terrminal to a
machine and power off the dumb terminal the machine will go down to OK prompt.
To solve this problem, we can:
1. Install patch 105924-10 on Solaris 2.6 or patch 107589-02 on Solaris 2.7.
Modify the /etc/default/kbd file, by removing the # from the entry:
#KEYBOARD_ABORT=enable
and changing it to:
KEYBOARD_ABORT=alternate
Reboot the server.
Now only the alternate break sequence
#<CR>
# ~^b
will be recognized as the abort sequence.
2. On Enterprise-type Suns, the power switch has four positions: off, on,
diagnostic and secure. With the power switch in
the secure position, the system ignores breaks generated by keyboard reconnect,
serial terminal loss, Stop-a or a
serial terminal break key
3. Tim Lindgren (Tim_lindgren@enron.net) mentioned that the other way is to
disable the break on the terminal and others
mentioned that, I can unplug the RS232 cables and turn off the terminal and
plug the RS232 cables .Although they mentioned there shouldn't be any problem
and they do this, but it shouldn't be the good way as the following document
says, even a unplug can cause a glich and sun consider it as a break.
http://www.stokely.com/unix.sysadm.resources/faqs.sun.html#sun.break.link
***********
So, a signal glitch that stays above +3.5 Volts for 4 milliseconds can
make the Sun think someone's sending a break signal. If the
terminal or terminal server is not careful to clamp its outputs when the
power supplies are charging up (power on) or discharging
(power off), such a glitch would be easy to generate.
Under certain conditions of cable capacitance and/or inductance, just
unplugging the RS232 cable can also produce a glitch on
the Sun's receive pin that looks like a break signal.
************
4. Mike Salehi suggested me to put a tape on the terminal. This is the only
thing I've already done :-)
4. Dan Brown<brown@obscure.org> suggest:
never turn off the terminal, OR, get a console serv
5. Jerry Springer <jerry.springer@vcloud.com> says, as this is break signal, you
can
easily restore the system to stable status by power up the terminal and type go.
6. Jerry also mentioned:
Get an adapter for that goes between the cable and the serial port that
supplies the appropriate signal to the sun regardless of whether the dumb
terminal is
powered on or not
Thanks to all who respond and sorry if I didn't name all of them here.
The references is:
. http://www.stokely.com/unix.sysadm.resources/faqs.sun.html#sun.break.link
Thanks for
David Evans <david.evans@oracle.com> for directing me to this document)
. man kbd
My original question was this:
The question is:
When I turn off the dumb terminal (IBM 3513) which is attached to our E5000
server via the serial port as a console, the E5000 goes to OK prompt!!!!! Is it
normal behaviour?!!!!!!!!!
It might be that with powering off the terminal, the terminal send break signal
to server. Unfortuantely, as this is the production server, I have no Maneuverr
to test.
--Nader
S
U BEFORE POSTING please READ the FAQ located at
N ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq
. and the list POLICY statement located at
M ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/policy
A To submit questions/summaries to this list send your email message to:
N sun-managers@sunmanagers.ececs.uc.edu
A To unsubscribe from this list please send an email message to:
G majordomo@sunmanagers.ececs.uc.edu
E and in the BODY type:
R unsubscribe sun-managers
S Or
. unsubscribe sun-managers original@subscription.address
L To view an archive of this list please visit:
I http://www.latech.edu/sunman.html
S
T
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:23 CDT