Cant get the ok prompt (on Sunfire V240)

[Ale]

Hello!

This is the problem that see on a SunFire V240:

sc> break -y

(the bge0 IP correctly stop to ping)

sc> console -f

no more output from serial (or net mngt ethernet) the ok prompt do not
start.

I usually go to ALOM console also on other servers (V240 and V245) to
install
different releases of Solaris starting for the "boot cdrom" at ok
prompt.
I cannot found a reason for this behavior on this server.

Any idea ?

Regards,

Alessandro

[Franco]

Try poweroff/poweron ?

[Ale]

Yes, but if yust after poweron send a break and go to console, can see
only the bootstrap logs, and others breaks from PuTTY (or from serial)
obtain only this message:

****** POST Running ******

(one per break) ...

when the bootstrap end:

0>Interrupt Crosscall....Done
0>Init Memory....Done
0>PLL Reset....Done
0>Init Memory....Done
0>Test Memory....Done
0>Test CPU Caches....Done
0>Functional CPU Tests....Done
0>IO-Bridge Tests....Done
0>INFO:
0> POST Passed all devices.
0>
0>POST: Return to OBP.

SC Alert: Host System has Reset

Configuring system memory & CPU(s)

Probing system devices
Probing memory
Probing I/O buses
Probing system devices
Probing memory
Probing I/O buses
sc>

no ok prompt appear, and I cant only return to ALOM with #.

Regards,

Alessandro

[usenetper...@gmail.com]

If all else fails powerdown, pull the power plugs out of the wall or
turn off the
power switch, wait a bit, reconnect/power back on. This has worked for
me in the past
when the ALOM ILOM etc refuse to respond or I get no login prompt but
that assumes
it aint broke elsewhere of course in some setting or another.
And make sure your firmware is up to date...
Ciao

[pavelj]

I've had a similar problem with V240 in the past:
1) Pull off the power cables form the box for 3+ minutes.
2) Plug the power back in.
3) Check that there is no warning light on the ALOM itsel(the back end
of the box). Next to the net mgt jack. Make sure the light is green;
4) If the LED is green, reinstall the ALOM's firmware and the OBP!!!
preferably the latest of both. compliance between them is the key.
5) If LED not green open an issue with SUN.

My problem was that the OBP and the ALOM firmware versions were not
compliant. OBP too old for the ALOM FW.
Best of luck.

May rockets not fall on your home.

[Emerson Seiti Takahashi]

On Apr 21, 12:56 pm, Ale <alessandro.fr...@gmail.com> wrote:
> 0>Interrupt Crosscall....Done
> 0>Init Memory....Done
> 0>PLL Reset....Done
> 0>Init Memory....Done
> 0>Test Memory....Done
> 0>Test CPU Caches....Done
> 0>Functional CPU Tests....Done
> 0>IO-Bridge Tests....Done
> 0>INFO:
> 0> POST Passed all devices.
> 0>
> 0>POST: Return to OBP.
>
> SC Alert: Host System has Reset
>
> Configuring system memory & CPU(s)
>
> Probing system devices
> Probing memory
> Probing I/O buses
> Probing system devices
> Probing memory
> Probing I/O buses
> sc>

Now you issue a console / console -f in the SC prompt. It should
appear nothing being output to the screen. Press Enter and it should
now appear the login screen. What is showing up for you?
--
Emerson Seiti Takahashi

[Jorgen Moquist]

hope not useless info: SunFire V210/V240 Jumpers

JP4 1-2 = 1.00GHz CPU
JP4 1-2,3-4 = 1.28GHz CPU
J5 1-2 Alom/System Control off, (will get you to openboot ok prompt)
J13 1-2 Obp normal, 2-3 Halfboot
J11 1-2 Write protect OBP

/Jorgen