SFV245 does not boot up after power outage

[lamsf]

Hi, I hv asked this before but problem still persists. After power outage, the SFV245 will wait for someone to key in "poweron" so that it will boot properly. Anything I can do to bypass this ALOM phase?

I hv set the following, yet it still won't boot up properly. Any advice?

# eeprom
...
auto-boot?=true
...
diag-switch?=false
#

sc> showsc
Advanced Lights Out Manager v1.6.4

parameter value
--------- -----
...
sc_powerondelay true
sc_powerstatememory true

Thank you.

 

[djr111]

what does auto-boot-on-error? and error-reset-recovery show in eeprom?

 

[lamsf]

auto-boot-on-error?=true
error-reset-recovery=sync

Is this fine?

Below is the complete eeprom, if it is helpful:

# eeprom
asr-policy=normal
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
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=screen
input-device=keyboard
auto-boot-on-error?=true
error-reset-recovery=sync
load-base=16384
auto-boot?=true
network-boot-arguments: data not available.
boot-command=boot
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=disk net
use-nvramrc?=false
nvramrc: data not available.
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=normal
diag-trigger=error-reset power-on-reset
service-mode?=false
diag-script=normal
diag-level=max
diag-switch?=false

 

[djr111]

the problem is with diag-switch?=false, I found some old notes of mine because this was something we did see before, I believe it is a bug, if the diag-switch? is set to false, even though sc_powerstatememory is set to true, it will make it interactive and you will need to use the 'poweron' command to cntinue to boot.

the work around is to set the diag-switch?=true

hope this helps
David

 

[lamsf]

Thanks, David.
We will try that.

 

[lamsf]

I hv set the "diag-switch?=true" as recommended.

There was a power outage last night, but this morning, when I reached the site, the server didn't boot up properly.

I could not ping or telnet to the server. When I tried to issue command "poweron" at the SC, it says that it is already running:

sc> poweron
The Host System Power is already running
sc>

I tried to go to console, and it gives me this:

sc> console
Console session already in use. [view mode]
Enter #. to return to ALOM.

Then I tried to issue "poweroff" and "poweron", but the server still would not boot up properly.

The boot process stopped at the following:

Requesting Internet Address for 0:14:4f:7b:12:1a
Requesting Internet Address for 0:14:4f:7b:12:1a
Requesting Internet Address for 0:14:4f:7b:12:1a

Lastly, I had to go to the OK prompt (by pressing Alt-B many times) and change the "diag-switch?=true" back to "diag-switch?=false", and type "boot" to boot up the server from OK prompt.

I had a scare for not being able to bring up the server!

What was the problem? Any problem with my setting:

sc> showsc
Advanced Lights Out Manager v1.6.4

parameter value
--------- -----
if_network true
if_modem false
if_connection ssh
if_emailalerts true
sys_autorestart xir
sys_bootrestart none
sys_bootfailrecovery none
sys_maxbootfail 3
sys_xirtimeout 900
sys_boottimeout 900
sys_wdttimeout 60
netsc_tpelinktest true
netsc_dhcp false
netsc_ipaddr 172.18.12.49
netsc_ipnetmask 255.255.255.224
netsc_ipgateway 172.18.12.33
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars #.
sc_powerondelay true
sc_powerstatememory true
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 2
sc_backupuserdata true
sys_eventlevel 2
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr 00:14:4f:7b:12:23
sys_hostname wmxems1
sys_enetaddr 00:14:4f:7b:12:1a
sc>

# eeprom
asr-policy=normal
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
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=screen
input-device=keyboard
auto-boot-on-error?=true
error-reset-recovery=sync
load-base=16384
auto-boot?=true
network-boot-arguments: data not available.
boot-command=boot
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=disk net
use-nvramrc?=false
nvramrc: data not available.
security-mode=none
security-password: data not available.
security-#badlogins=0
verbosity=normal
diag-trigger=error-reset power-on-reset
service-mode?=false
diag-script=normal
diag-level=max
diag-switch?=false
#

 

[djr111]

I think you also need the diag-device set to exactly what your boot-device variable is, and of course the diag-switch needs to be set to true.


my notes had this next to it, I think it is a bug id from Sun, if you have a sunsolve account, check it out.


6508448


good luck!!
-David