From: Miller, Dave (Dave.Miller@BHS.ORG)
Date: Tue Sep 03 2002 - 15:04:08 EDT
Simon,
Is it possible, that there are some device packages needed on the new node,
that
the donor node does not have?
If you can get the target node restored/booted and copy /tmp/device.pkgs
off someplace and review vs. the donor, that might show something..
-----Original Message-----
From: ANTHONY DELSORBO [mailto:delsorbo@ASC.HPC.MIL]
Sent: Tuesday, September 03, 2002 2:44 PM
To: aix-l@Princeton.EDU
Subject: Re: Cloning SP2 Node LED E105
Simon,
This sounds like a bootp/tftp issue. E105 is a network error indication.
Check that your tftp and bootp daemons are enabled. Also, check that the
MAC
address of your node is in the /etc/bootptab. Something is amiss in that
your
system doesn't know how to communicate with the node.
Tony DelSorbo
ASC MSRC, OH
On Tuesday 03 September 2002 01:03 pm, Green, Simon wrote:
> I'm planning to migrate one of my systems tomorrow afternoon and I've been
> trying to do a dummy run today to confirm it works OK and to check the
> timings. Unfortunately, it doesn't work.
>
> The source node is a 604 High node, running PSSP 3.2 and AIX 4.3.3 ML08.
> The target node is a Silver Wide node, (previously running PSSP 3.1.1 and
> AIX 433-06).
> CWS is PSSP 3.2, AIX 433-08.
> SPOT is at ML08.
>
> setup_server completed with rc=0. SDR information looks OK.
> When I run nodecond it goes pretty much as normal at first, but then it
> hangs on LED E105.
>
> I get the same result when I try a diag boot, and also when I switch back
> to the original boot image and PSSP version, (that was still with a diag).
> On one occasion, I got 4B24A110, but I haven't seen that again.
>
> Console output, (for diag) shows the following:
> BOOTP S = 1
> FILE: /tftpboot/baup139e
> Load Addr=0x4000 Max Size=0xbfc000
> FINAL Packet Count = 9140
> DEFAULT CATCH!, code=fff00700 at %SRR0: 0000d1c0 %SRR1: 00083000
> ok
> 0 >
>
> nc.3.9 is...
> Nodecond Status: network boot successful
> Nodecond Status: bootp sent over ethernet
> Nodecond Status: waiting for "Please define the System Console" menu
> Nodecond Status: will wait up to 420 seconds
> timeout waiting for "Please define the System Console"
> Nodecond Status: finished
>
> Install is similar.
>
> I've had a search of the archives and came across some references to NFS
> export problems. I've been through /etc/exports and checked with lsnfsexp
> and found a couple of oddities, in that some exports were for
> "root=baup139e:,access=baup139e:", (note the extraneous colons). I
> corrected them and re-exported. I also added explicit root access for
> lppsource.
>
> I also found a reference to ethernet, so I checked: both the node's SDR
> entry and the CWS are set to half-duplex.
>
> The target node was running happily in production up until very recently.
> Last time it was rebooted was about a month ago. There have been no
> hardware errors as far as I am aware.
>
> What am I doing wrong?
>
> Simon Green
> Philip Morris ITSC Europe
>
> AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
> AIX FAQ at http://www.faqs.org/faqs/aix-faq/
>
> N.B. Unsolicited email from vendors will seldom be appreciated.
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:11 EDT