Prev: netstat -s ICMP
Next: rsync help
From: Sam Nelson on 10 Feb 2006 07:08

Hi all - I've been battling with an ALOM issue on a v440 for the last
week, hopefully someone can shed some light! Apologies for length.

The ALOM was working ok, then we had the system board replaced under an
FCO (FCO 245). Then the ALOM card stopped working (details below), and
was replaced with a new one. The new one still doesn't work.

We've not made any changes to the system apart from upgrading the ALOM
software to 1.5.4 from 1.5.2 (in an attempt to remedy the issue of it
not working). Box is running Sol9 117171-15 / OBP 4.16.1

Here's the meat:

I can get to the <sc> prompt over a serial connection to the ALOM card
with no issue. When I issue "console" or "console -f" however, I just
get nothing, it appears that I can't read or write from/to the console
at all. The sc card's bootmode is set to "normal".

I thought it might be an eeprom redirect issue at first. Other V440s I
have use:

input-device=keyboard
output-device=screen

And we can use the sc / console switching with no problem. This was the
setting we had on the problem v440.

I set this on the problem v440, power cycled, but this was in vain.
Other combinations I've tried are:

input-device=ttya
output-device=ttya

input-device=rsc-console
output-device=rsc-console

But still no joy.

I then reset the ALOM card (resetsc) after upgrading to ALOM software
1.5.4, alas this was in vain.

Solaris appears to see the ALOM card ok; scadm seems to return values
properly.

I've logged a Sun case, but we appear to be going round in circles (any
Sun bods on the list want to have a look at it please feel free, I'll
mail you the radiance ID) :)

Could anyone on the list shed any light?

cheers

Sam

--------------------------------------

Below are some outputs:

sam(a)jeffk# scadm version

SC Version v1.5
SC Bootmon Version: v1.5.4
SC Firmware Version: v1.5.4

sam(a)jeffk# eeprom
test-args: data not available.
diag-passes=1
local-mac-address?=false
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=ttya
input-device=ttya
auto-boot-on-error?=true
error-reset-recovery=sync
load-base=16384
auto-boot?=true
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

sc> showsc -v
Advanced Lights Out Manager v1.5.4

parameter value
--------- -----
if_network true
if_modem false
if_emailalerts false
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 0.0.0.0
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 0.0.0.0
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars #.
sc_powerondelay true
sc_powerstatememory false
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 3
sc_backupuserdata true
sys_eventlevel 3
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr ########
sys_hostname ####
sys_enetaddr ########
From: Scott Howard on 11 Feb 2006 07:54
Sam Nelson <sun(a)unix.ms.nospam> wrote:
> The ALOM was working ok, then we had the system board replaced under an
> FCO (FCO 245). Then the ALOM card stopped working (details below), and
> was replaced with a new one. The new one still doesn't work.

Sounds like a faulty motherboard. Didn't the engineer who carried
out the replacement test it before (s)he left?

> I thought it might be an eeprom redirect issue at first. Other V440s I

ALOM doesn't really use redirection like some of the other systems (ie,
RSC). You just need to configured as if you were using a standard
serial port, which it appears you have.

> I've logged a Sun case, but we appear to be going round in circles (any
> Sun bods on the list want to have a look at it please feel free, I'll
> mail you the radiance ID) :)

Send me the number and I'll try and do some prodding...

Scott.
 | 
Pages: 1
Prev: netstat -s ICMP
Next: rsync help