SUMMARY: V120: Double serial connection freezes one host

A huge thanks to everybody who responded so quickly.

In summary, the problem is resolved by changing or disabling the 
keyboard/serial break sequence. This can be done in two ways:

- Using kbd(1)(non-persistent):
# kbd -a alternate
(changes break sequence to  ~^b, that is, a tilde (~) followed by a 
control-B), or
# kbd -a disable
(disables keyboard and serial abort).

- Editing /etc/default/kbd: Uncomment KEYBOARD_ABORT=disable or 
KEYBOARD_ABORT=alternate (effects same as above, but persistent). For 
immediate effect, do
# kbd -i

Alternatively, you can use Martin Schmitt's nobreak package, available 
at http://www.scsy.de/~mas/nobreak/

Rgds

Paul


> Sunmanagers,
> 
> I have two SunFire V120, which operate side by side in a headless mode. 
> As I have no terminal concentrator, but I still need to have access to 
> the console of both servers, I planned to connect to each one's console, 
> doing a 'tip hardwire' on the other host, which would connect to the 
> console on serial a. This way I could even 'wake up' a host, sending a 
> 'poweron' to the LOM CLI.
> 
> -----------------         ------------------
> |               |         |                |
> |   serial a/lom --------- serial b        |
> |     BOX A     |         |     BOX B      |
> |       serial b --------- serial a/lom    |
> |               |         |                |
> -----------------         ------------------
> 
> This seemed to work pretty well, but there is a big drawback: Each time 
> I (re)boot a host, e.g. sending an init 6 from box a to box b, the one I 
> use for terminal access (box a) freezes into ok-prompt. So I have to 
> wait for box b to be online, log in, connect to console of box a and 
> just type 'go' at the ok...
> 
> This only happens, when both serial lines are connected as above. I 
> don't know if other systems would behave the same, as this is the first 
> time I did this kind of serial connect configuration.
> 
> Obviously the host to boot sends a break signal to the connecting host, 
> causing the freeze.
> Has anybody found out how to prevent this kind of behaviour?
> 
> The two boxes have prettty much identical setup:
> 
> # uname -a
> SunOS ub-files 5.9 Generic_112233-04 sun4u sparc SUNW,UltraAX-i2
> 
> # prtconf -V
> OBP 4.0.14 2002/07/03 09:17
> 
> # grep hardwire /etc/remote
> hardwire:\
>         :dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
> 
> # eeprom
> ttyb-rts-dtr-off=false
> ttyb-ignore-cd=true
> ttya-rts-dtr-off=false
> ttya-ignore-cd=true
> ttyb-mode=9600,8,n,1,-
> ttya-mode=9600,8,n,1,-
> output-device=ttya
> input-device=ttya
> 
> I need to get this configuration to production soon. Please help! Send 
> email and I will summarize to the list.
> 
> Thanks for assistance.
> 
> 


-- 
Mit freundlichen Gruessen

Paul Coray
Administrator Server und Netzwerk

Oeffentliche Bibliothek der Universitaet Basel
EDV-Abteilung
Schoenbeinstrasse 18-20
CH-4056 Basel

Tel: +41 61 267 05 13
Fax: +41 61 267 31 03

mailto:paul.coray@unibas.ch
http://www.ub.unibas.ch
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers