Hi all,
I'm having real problems with a new HP rp2430 server I need to set up.

I've tried the LAN console on address 192.0.0.192 with no luck. I've
also built a  HP 24542G cable from a schematic from their web site but
with no luck in accessing the serial console.  I also downloaded
QCTerm to see if I could connect using that program and the created
cable but with no luck.  It just has a blank screen.

To complicate matters the Fault light is on and the Run and Attn:
lights are flashing.  What does this mean?

I've never actually accessed any type of Unix console previously by
any means so that might be one of my problems :(.

I'll be monitoring this post and reply to all questions so any help
would be appreciated.

Regards,
Julian

"Julian" <julian@sidewinderap.com> wrote in message
news:55ee8bb9.0401262026.30c3b2f8@posting.google.com...
> Hi all,
> I'm having real problems with a new HP rp2430 server I need to set up.
>
> I've tried the LAN console on address 192.0.0.192 with no luck. I've
> also built a  HP 24542G cable from a schematic from their web site but
> with no luck in accessing the serial console.  I also downloaded
> QCTerm to see if I could connect using that program and the created
> cable but with no luck.  It just has a blank screen.
>
> To complicate matters the Fault light is on and the Run and Attn:
> lights are flashing.  What does this mean?
>
> I've never actually accessed any type of Unix console previously by
> any means so that might be one of my problems :(.
>
> I'll be monitoring this post and reply to all questions so any help
> would be appreciated.
>
> Regards,
> Julian
Julian,
    From my listing that combination of lights means:
State:

  a.. Boot failed
  b.. Executing non-OS code.
  c.. Non-critical error detected (i.e.. fan failure, power supply failure)
Jim

"Julian" <julian@sidewinderap.com> wrote in message
news:55ee8bb9.0401262026.30c3b2f8@posting.google.com...
> Hi all,
> I'm having real problems with a new HP rp2430 server I need to set up.
>
> I've tried the LAN console on address 192.0.0.192 with no luck. I've
> also built a  HP 24542G cable from a schematic from their web site but
> with no luck in accessing the serial console.  I also downloaded
> QCTerm to see if I could connect using that program and the created
> cable but with no luck.  It just has a blank screen.
>
> To complicate matters the Fault light is on and the Run and Attn:
> lights are flashing.  What does this mean?
>
> I've never actually accessed any type of Unix console previously by
> any means so that might be one of my problems :(.
>
> I'll be monitoring this post and reply to all questions so any help
> would be appreciated.
>
> Regards,
> Julian
Also, you can go to http://docs.hp.com and enter "leds rp24xx" and look at
the troubleshooting document.
Jim

"Jim" <james.no.spam.poplawski@ngc.nospam.com> wrote in message news:<bv63rh$cl7$1@gateway.northgrum.com>...
> "Julian" <julian@sidewinderap.com> wrote in message
> news:55ee8bb9.0401262026.30c3b2f8@posting.google.com...
> > Hi all,
> > I'm having real problems with a new HP rp2430 server I need to set up.
> >
> > I've tried the LAN console on address 192.0.0.192 with no luck. I've
> > also built a  HP 24542G cable from a schematic from their web site but
> > with no luck in accessing the serial console.  I also downloaded
> > QCTerm to see if I could connect using that program and the created
> > cable but with no luck.  It just has a blank screen.
> >
> > To complicate matters the Fault light is on and the Run and Attn:
> > lights are flashing.  What does this mean?
> >
> > I've never actually accessed any type of Unix console previously by
> > any means so that might be one of my problems :(.
> >
> > I'll be monitoring this post and reply to all questions so any help
> > would be appreciated.
> >
> > Regards,
> > Julian
> Julian,
>     From my listing that combination of lights means:
> State:
> 
>   a.. Boot failed
>   b.. Executing non-OS code.
>   c.. Non-critical error detected (i.e.. fan failure, power supply failure)
> Jim

Thanks Jim,
I had a look at those documents from the HP site. I'll take a look
into the hardware.
Should I still be able to get a console?

Julian

julian@sidewinderap.com (Julian) wrote in message news:<55ee8bb9.0401271447.27cd97ee@posting.google.com>...
> "Jim" <james.no.spam.poplawski@ngc.nospam.com> wrote in message news:<bv63rh$cl7$1@gateway.northgrum.com>...
> > "Julian" <julian@sidewinderap.com> wrote in message
> > news:55ee8bb9.0401262026.30c3b2f8@posting.google.com...
> > > Hi all,
> > > I'm having real problems with a new HP rp2430 server I need to set up.
> > >
> > > I've tried the LAN console on address 192.0.0.192 with no luck. I've
> > > also built a  HP 24542G cable from a schematic from their web site but
> > > with no luck in accessing the serial console.  I also downloaded
> > > QCTerm to see if I could connect using that program and the created
> > > cable but with no luck.  It just has a blank screen.
> > >
> > > To complicate matters the Fault light is on and the Run and Attn:
> > > lights are flashing.  What does this mean?
> > >
> > > I've never actually accessed any type of Unix console previously by
> > > any means so that might be one of my problems :(.
> > >
> > > I'll be monitoring this post and reply to all questions so any help
> > > would be appreciated.
> > >
> > > Regards,
> > > Julian
> > Julian,
> >     From my listing that combination of lights means:
> > State:
> > 
> >   a.. Boot failed
> >   b.. Executing non-OS code.
> >   c.. Non-critical error detected (i.e.. fan failure, power supply failure)
> > Jim
> 
> Thanks Jim,
> I had a look at those documents from the HP site. I'll take a look
> into the hardware.
> Should I still be able to get a console?
> 
> Julian

I've taken a good hard look at the hardware but there appears to be no
problems.  Has anyone else encountered problems with the rp24xx
series?!!

Please help!

Thank you.

(Julian) wrote in message news:<55ee8bb9.0401262026.30c3b2f8@posting.google.com>...
> Hi all,
> I'm having real problems with a new HP rp2430 server I need to set up.
> 
> I've tried the LAN console on address 192.0.0.192 with no luck. I've
> also built a  HP 24542G cable from a schematic from their web site but
> with no luck in accessing the serial console.  I also downloaded
> QCTerm to see if I could connect using that program and the created
> cable but with no luck.  It just has a blank screen.
> 
> To complicate matters the Fault light is on and the Run and Attn:
> lights are flashing.  What does this mean?
> 
> I've never actually accessed any type of Unix console previously by
> any means so that might be one of my problems :(.
> 
> I'll be monitoring this post and reply to all questions so any help
> would be appreciated.
> 
> Regards,
> Julian

As an update:
I was finally able to get a console by attaching a generic null modem
cable and using QCTerm.

On boot up I now have the message:
************* SYSTEM ALERT **************
SYSTEM NAME: uninitialized
DATE: 01/30/2004 TIME: 00:19:37
ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents
operation

REASON FOR ALERT
SOURCE: 8 = I/O 
SOURCE DETAIL: 6 = disk   SOURCE ID: 0
PROBLEM DETAIL: 3 = functional failure

LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
       FLASH    FLASH         ON        ON         ON
LED State: Boot Failed.  Running non-OS code.  Non-critical error
detected.
Check Chassis and Console Logs for error messages.

0x000000F386001480 00000000 00000000 - type  0 = Data Field Unused
0x580008F386001480 00006800 1E001325 - type 11 = Timestamp 01/30/2004
00:19:37


Any suggestions before I continue blindly through this?

julian@sidewinderap.com (Julian) writes:

> Hi all,
> I'm having real problems with a new HP rp2430 server I need to set up.

As I understand, rp2430 has a "real" Guardian Service Processor 
(GSP) console interface. In my opinion, it's much better than the
integrated Web Console modules of the rp24xx series' predecessor.
 
> I've tried the LAN console on address 192.0.0.192 with no luck. 

Unfortunately, GSP does not answer on any address by default. You have
to use the serial port for the first time. Then you can set the
console LAN's network parameters with a GSP command (LC for LanConfig)
and enable the interface (LE for LanEnable).

When the LAN console access is enabled, the yellow "Remote" LED in the
server's front panel should light up.

> I've
> also built a  HP 24542G cable from a schematic from their web site but
> with no luck in accessing the serial console.  I also downloaded
> QCTerm to see if I could connect using that program and the created
> cable but with no luck.  It just has a blank screen.

Hmm, the standard solution would be the 3-way adapter cable (from D25
to 3 D9 connectors, marked "Console", "Remote" and "UPS"). When you
connect a normal null modem cable after that, it should "just work".
I don't have tried with a HP 24542G cable and a PC. That cable might
be intended for dumb terminals for all I know.

The default speed of the GSP serial interface is 9600 bps, 8 data
bits, no parity and 1 stop bit.

After connecting the cable, the server may not output anything until
you press Enter once or twice. If the server does not print anything,
press Ctrl-B. It should let you access the GSP: it's independent of
the rest of the server, and should work always when the server's power
cord is plugged in. The GSP should print a prompt like:

  GSP>

From there you could check the error logs (which resets the Attn and
Fault lights in the front panel, by the way). That might tell more
about the server's boot problems. "HE" is the help command for GSP:
after that you can enter any command to see what it does, or "LI" for
a list of all GSP commands. To get out of Help mode, enter Q.

If the GSP does not answer at all, check the LEDs of the LAN console
interface. If you see red lights, the GSP may be still resetting or
faulty. You can try to press the "GSP Reset" button in the back of the
server: you'll need a pen or some other pointy thing for that.

Next to the GSP reset button, there's a similar button marked TOC.
That's HP jargon for "server hardware reset". It also makes the server
create a crash dump when it boots up next time, so remember to clean
it out of your /var/adm/crash directory.
 
> I've never actually accessed any type of Unix console previously by
> any means so that might be one of my problems :(.

Fear not. There is no magic involved. :-)

-- 
Matti.Kurkela@welho.com

julian@sidewinderap.com (Julian) writes:

> As an update:
> I was finally able to get a console by attaching a generic null modem
> cable and using QCTerm.
> 
> On boot up I now have the message:
> ************* SYSTEM ALERT **************
> SYSTEM NAME: uninitialized
> DATE: 01/30/2004 TIME: 00:19:37
> ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents
> operation
> 
> REASON FOR ALERT
> SOURCE: 8 = I/O 
> SOURCE DETAIL: 6 = disk   SOURCE ID: 0
> PROBLEM DETAIL: 3 = functional failure
> 
> LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
>        FLASH    FLASH         ON        ON         ON
> LED State: Boot Failed.  Running non-OS code.  Non-critical error
> detected.
> Check Chassis and Console Logs for error messages.
> 
> 0x000000F386001480 00000000 00000000 - type  0 = Data Field Unused
> 0x580008F386001480 00006800 1E001325 - type 11 = Timestamp 01/30/2004
> 00:19:37
> 
> 
> Any suggestions before I continue blindly through this?

Ouch. Seems that you may have a bad hard disk. If the server is under
warranty or hardware support, call HP to have the disk changed to a
working one.

The internal disks are accessible through a small door behind the
front faceplate. The faceplate should come off by pulling it.

If the boot disk was mirrored, try booting from the other half of the
mirror set. Reset the server (for example, with the GSP command "RS")
and after the selftests are done, the server says something like
"press any key in 10 seconds to interrupt the autoboot process".

Press any key to get to the boot prompt. From here you can 
use the command "search" to find any bootable disks, CDROMs or tapes.
The system disks are probably listed as P0 and P1: then, you could try
to boot from the other disk with the command "boot p1".

-- 
Matti.Kurkela@welho.com

Julian,

From what the event code is telling you, you need to take a look at the BCH
(boot console handler) and verify that your primary and/or alternate boot
paths are programmed correctly.  The system is trying to do an automatic
boot and can't verify the paths that it has stored in memory.

At the bch prompt, type
pa
and take a look at what it returns.

If you are trying to boot off of the internal paths, the primary path should
be 0/0/1/1.15 and the alternate should be 0/0/2/1.15

They can be set by typing

pa pri 0/0/1/1.15 (or whatever desired path)
pa alt 0/0/2/1.15  (or whatever desired path)

Regards
Kevin Vadnais



"Julian" <julian@sidewinderap.com> wrote in message
news:55ee8bb9.0401291638.6af04653@posting.google.com...
> (Julian) wrote in message
news:<55ee8bb9.0401262026.30c3b2f8@posting.google.com>...
> > Hi all,
> > I'm having real problems with a new HP rp2430 server I need to set up.
> >
> > I've tried the LAN console on address 192.0.0.192 with no luck. I've
> > also built a  HP 24542G cable from a schematic from their web site but
> > with no luck in accessing the serial console.  I also downloaded
> > QCTerm to see if I could connect using that program and the created
> > cable but with no luck.  It just has a blank screen.
> >
> > To complicate matters the Fault light is on and the Run and Attn:
> > lights are flashing.  What does this mean?
> >
> > I've never actually accessed any type of Unix console previously by
> > any means so that might be one of my problems :(.
> >
> > I'll be monitoring this post and reply to all questions so any help
> > would be appreciated.
> >
> > Regards,
> > Julian
>
> As an update:
> I was finally able to get a console by attaching a generic null modem
> cable and using QCTerm.
>
> On boot up I now have the message:
> ************* SYSTEM ALERT **************
> SYSTEM NAME: uninitialized
> DATE: 01/30/2004 TIME: 00:19:37
> ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents
> operation
>
> REASON FOR ALERT
> SOURCE: 8 = I/O
> SOURCE DETAIL: 6 = disk   SOURCE ID: 0
> PROBLEM DETAIL: 3 = functional failure
>
> LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
>        FLASH    FLASH         ON        ON         ON
> LED State: Boot Failed.  Running non-OS code.  Non-critical error
> detected.
> Check Chassis and Console Logs for error messages.
>
> 0x000000F386001480 00000000 00000000 - type  0 = Data Field Unused
> 0x580008F386001480 00006800 1E001325 - type 11 = Timestamp 01/30/2004
> 00:19:37
>
>
> Any suggestions before I continue blindly through this?