Setup ALOM networking with jumpstart begin script

When jumpstarting a server you want to see the console output to make sure nothing bad happens,
this can be accomplished by logging into the ALOM over the network so you can follow your installation
from your desk in stead of the noisy datacenter.

First when the server is powered up we want to go into the ALOM/SC
when you are in the ok prompt type:

{1} ok #.

The first thing to do is to set the admin password

sc> password
password: Changing password for admin
Enter new password: *****
Re-enter new password: *****

Read the rest of this entry »


SC Alert: DHCP negotiation failed

I started getting these annoying errors on the console from the the V445 I am building, they log about once every couple of minutes:

SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server available

Searching for an answer you don’t get very much. But reading up on the ALOM that ships with the Sun Fire V445, I found the following:

All initial configuration must [be] done through the serial management port on the Sun Fire V210, V240, V250, and V440 servers and Netra 210, 240, 440 servers. Some servers (Sun Fire V215, V245, and V445) support DHCP by default on the network management port. These servers can be configured from the serial management port or network management port, if the attached subnet has a DHCP server. The default network configuration allows a Secure Shell session to be started.

So starting with the Sun Fire V215, V245, and V445 servers, it tries to associate with a DHCP server. If you are not currently using this feature you probably want to turn it off. So here is what you do.

Read the rest of this entry »