Solaris

@Perderabo........Thanks. Anyway, you know my suspicions, hence my questions to the OP. The OP is 8 hrs behind me and you are 5 hrs behind me. I'm in the UK so will be signing out soon so you are better placed to help. Unless the hardware architecture is understood (ie, the manual has been read), then pressing the power button after seeing a SC> prompt on the terminal might not be the obvious thing to do. Perhaps you'll have this sorted before I wake up tomorrow.

I will try to hit everything, sorry for my delay.

1. I believe it is something with the CPU's and unfortunately I am the hardware tech rep for this gear. Usually I'm just software, so I'm learning on the fly.

2. I did work around the case switch and all four replacements were running properly (and plugged in obviously)

3. Re-seating the RAM was the first thing I did when no OBP showed.

4. I let the SC login expire hoping to see OBP, I also removed all forms of connections to the KVM to try and force output to redirect to TTYA

5. I do have access to the ALOM and I've tried rebooting with bootscripts to change output/input and set autoboot to false. When I console -f I get the same blank screen.

6. With fans running properly, I think it would be safe to assume I applied power correctly. Interesting to note however, when I run showplatform through the ALOM, it does not correctly reflect the current state of the server. Example: When system has been powered on, it will still show system stopped.

I think you may be on to something with the CPU's being the issue, that is really the only thing that makes any sense. With both behaving the same exact way and no OBP I would have to say it is CPU's. I have pulled them out and checked to see how the pins are, and they seem fine to me... I did clear out some fuzz on one of them. Would the fuzz short the motherboard?

P.S. From what I understand, the difference in paste vs the strip that comes with it is the type of processors. (read it on my search for answers before posting)

Right, let me explain some of the basic hardware architecture here. Sorry, if you already know this but you really must understand this correctly.

First there is a Linux appliance called the System Controller (SC>) integrated underneath the full Sun hardware. The SC's job is to assist you, the Sysadmin, to manage the system. The SC is a separate machine to the main system (although integrated in the box).

When you plug in the mains power the SC will boot and you should see that output.

IF THE SC IS CONFIGURED TO, it will power up the main processor(s) but otherwise it won't. So power on the SC doesn't mean that the whole machine is powered up.

Can you login to the SC? Do you know the password?

If you can login to the SC then you can ask the SC to power up the main box by giving the command:

Code:

SC> poweron

After that is you switch to the console output:

Code:

SC> console

you should be able to see the main machine boot.

Try the first 'poweron' command and watch the front of the box for lights and the noise level (if it's not in a noisey machine room). Or get someone else stand in front of the box when you hit the return key. There should be an immediate response.

Post back the result.

I can log on to the SC, and after console this is what shows:

Enter #. to return to Alom.

and OBP never comes up. Been waiting for the OK prompt and nothing. I know for a fact the server is on, after poweron command is issued, the fans come up. This is where I've been stuck for a week. Trying to figure out why the OBP isn't there.

Yes, BUT BEFORE you issue the 'console' command tell the SC to power up the main box:

Code:

SC> poweron

Try that please.

Yes, I have done that. It shows the response SC requesting poweron and the fans kick on.

---------- Post updated at 02:32 PM ---------- Previous update was at 02:26 PM ----------

So no POST if that's what you are asking.

Right, I understand.

It's quite possible that the OBP is set to send console output elsewhere which would be why you're not seeing it. I've been involved in many a discussion on this forum regarding this; I'm off to look for these and I'll edit this post with the link(s).

Alternatively, if you have a Sun keyboard on this system then you could reset all SC parameters to default by hitting STOP-N as the SC is booting (but that might be a bit too drastic).

Watch this space.....