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.

First you need to get to the sc>, prompt. It stands for system controller.

Hit #. (pound-period)

Then you need to change some settings to turn off the the network portion of the SC. The following settings are the defaults for the other servers that ship ALOM:

sc> setsc if_network false
Change will not become active until the SC is reset.
sc> setsc if_connection none
Change will not become active until the SC is reset.
sc> setsc netsc_dhcp false
Change will not become active until the SC is reset.
sc> resetsc -y
User Requested SC Shutdown

ALOM - min post no output

ALOM POST 1.0

Dual Port Memory Test, PASSED.

TTY External - Internal Loopback Test
TTY External - Internal Loopback Test, PASSED.

TTYC - Internal Loopback Test
TTYC - Internal Loopback Test, PASSED.

TTYD - Internal Loopback Test
TTYD - Internal Loopback Test, PASSED.


Memory Data Lines Test
Memory Data Lines Test, PASSED.

Memory Address Lines Test
Slide address bits to test open address lines
Test for shorted address lines
Memory Address Lines Test, PASSED.

Boot Sector FLASH CRC Test
Boot Sector FLASH CRC Test, PASSED.

Return to Boot Monitor for Handshake
ALOM POST 1.0
Status = 00007fff

Returned from Boot Monitor and Handshake

Loading the runtime image...


Full VxDiag Tests

BASIC TOD TEST
Read the TOD Clock: WED MAY 09 14:26:02 2007
Wait, 1 - 3 seconds
Read the TOD Clock: WED MAY 09 14:26:04 2007
BASIC TOD TEST, PASSED

ETHERNET CPU LOOPBACK TEST
50 BYTE PACKET - a 0 in field of 1's.
SC Alert: SC System booted.
done.


50 BYTE PACKET - a 1 in field of 0's. done.

900 BYTE PACKET - pseudo-random data.
done.
ETHERNET CPU LOOPBACK TEST, PASSED

Full VxDiag Tests - PASSED

Status summary - Status = 7FFF

VxDiag - - PASSED
POST - - PASSED
LOOPBACK - - PASSED

I2C - - PASSED
EPROM - - PASSED
FRU PROM - - PASSED


ETHERNET - - PASSED
MAIN CRC - - PASSED
BOOT CRC - - PASSED

TTYD - - PASSED
TTYC - - PASSED
MEMORY - - PASSED
MPC885 - - PASSED


Please login: admin
Please Enter password: *****

sc> console
Enter #. to return to ALOM.

After that the message stops loggging. You could probably just set netsc_dhcp to false. I wanted to have the same defaults settings as I do on all the other machines.

Advertisements

21 Responses to “SC Alert: DHCP negotiation failed”

  1. Paul Siddall Says:

    Many(!) thanks..
    Just what I needed to do šŸ˜‰

    Paul

  2. rondua Says:

    Shame on SUN that there is no lom command on the OS level any longer (as it was on i.e. Netra t1) where you can set this more comfortable.

  3. pearcec Says:

    Rondua,

    Looks like they still do, scadm [1] is the command. I just failed to locate this when I was coming up with a fix.

    [1] http://docs.sun.com/source/819-2445-11/sadm_util.html

  4. Juan Says:

    Thanks, This was bugging me.
    I found this and fixed it.

  5. David Says:

    Thanks for this fix, it was driving me crazy!

  6. Joe Says:

    Thank You So Much!! You need to write documentation for Sun!!! This was exactly what I needed!

  7. pearcec Says:

    I would love to write documentation for Sun. I think writing Sun Blueprints would be the best. I had several authors join up but very little input. Unfortunately right now I am not on any Sun gigs so the blog is going to probably grow static unless I can get some other authors contributing.

  8. Pete Says:

    Thank for the tips folks! We don’t connect through the ALOM, but through the serial-console. We were able to set the SC configuration using ‘scadm’ as suggested by Rondua (Many Thanks!).
    i.e,

    scadm set if_network false
    scadm set if_connection none
    scadm set netsc_dhcp false
    scadm resetrsc

    Done…..

    Thanks again all…

  9. Pete Says:

    …forgot to add. If you don’t find ‘scadm’ for your specific platform, I was able to use one gleened under /usr/platform from another platform. In other words, there wasn’t ‘scadm’ under our Sun v245 platform, but the one found under the v240 worked fine.

  10. Simon Says:

    Cheers, that dhcp logging was really starting to irritate me. I must get into LOM and actually start using it properly!

  11. pianoman Says:

    Many thanks, this was just what I needed. I’m installing Solaris 10 on our first V215, and I was being driven crazy by the message. I put this information into our company Wiki so that nobody else will need to go through this nightmare again…

  12. Barry Says:

    Thank you so much. This was driving me nuts!

  13. ThirstyFish Says:

    Thanks! V215 is already EOL but in use and documentation is all there but it takes some time to figure out what pearcec did for us. Good work, keep it up.

  14. omar626 Says:

    GReat, Thanks,

  15. fatbadger Says:

    Worked a treat. Thanks.

  16. marybeth Says:

    thanks.

  17. Heather Says:

    I just decided to try the last two commands you suggested, and that worked for me:
    sc> setsc netsc_dhcp false
    sc> resetsc -y

    Thanks very much!!

  18. Chetan Says:

    Thanks Mate. It worked.

  19. psshah Says:

    Thanks a lot!!!!
    It resolved that annonying error…

  20. Alfred447 Says:

    Thanks. It fixed that issue .. even year after …

  21. misspelled ebay Says:

    Hi there very nice blog!! Guy .. Beautiful .. Amazing .. I’ll bookmark your web site and take the feeds also? I’m happy to find numerous useful info here within the submit, we need work out more strategies in this regard,
    thanks for sharing. . . . . .


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: