Solaris sunfire v100 goes to OpenBoot prom when we lose the Console

[kozlow]

Our sunfire v100 goes south when we lose the console. When we replace or power the console back on, it is at the OpenBoot prompt of "OK". While in this stat, no users have access to the system. I have been able to type in "go" at the prompt and we go back to multi-user mode....

Any Ideas on how to resolve this????

 

[bluelake]

perhaps you can check your /etc/inittab to see if it has the below line:

is:3:initdefault:

 

[kozlow]

Yes, we have that entry in inittab. Turns out, when the console powers down it sends a break. The break puts the sunfire in OpenBoot. When I power back up the console (IBM 3153) should be able to just hit enter and go from there. Sometimes I can, others times no luck. I moved the console over to a PC and used HyperTerm to create a console. Was able to get the "ok" and go....

Need to figure how to stop the "break" since this will be a 7X24X365 server..... What a $%&*@

I guess I can just remove the cable and plug it in when I need a console... No break is sent...

 

[SamBones]

Check a file called /etc/default/kbd. I believe there's an entry there that will disable that keyboard break. I don't have a machine handy at the moment, so I can't give you specifics.

Hope this helps.

 

[Annihilannic]

This is the one, complete with comment:

[tt]# Uncomment the following line to disable keyboard or serial device
# abort sequences:
#KEYBOARD_ABORT=disable[/tt] Annihilannic.

 

[kozlow]

That works, but now I am unable to hit the break key to go into OpenBoot. I just wrote a procedure that allows us to go back, in case we need to run diags.

Thanks for all the help...

I truley believe in simple solutions for simple minds, I mean problems....

 

[kozlow]

Changed the KEYBOARD_ABORT to alternate after finding that the alter break sequence is
"~ CTRL-B"

The console can be lost and I am still able to break into OpenBoot.