|
Prev: OpenSolaris User Group Möte 13 Maj kl 16:30 hos SUN Akalla Sweden
Next: Wholesale golf clubs,wedge,hybrid,irons etc..
From: Ale on 21 Apr 2008 09:13 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
From: Franco on 21 Apr 2008 11:25 On Apr 21, 2:13 pm, Ale <alessandro.fr...(a)gmail.com> wrote: > 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 Try poweroff/poweron ?
From: Ale on 21 Apr 2008 11:56 On 21 Apr, 17:25, Franco <franco_spen...(a)yahoo.com> wrote: > On Apr 21, 2:13 pm, Ale <alessandro.fr...(a)gmail.com> wrote: > > > > > 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 > > Try poweroff/poweron ? 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
From: usenetpersongerryt on 21 Apr 2008 12:20 On Apr 21, 6:13 am, Ale <alessandro.fr...(a)gmail.com> wrote: > 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 ? 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
From: pavelj on 21 Apr 2008 14:27
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. |