RE: Connect to Lan Console during D-Mode IPL?

That's funny - there's an IBM-er here in Auckland named just the same as
you....

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Wright
Sent: Monday, 20 October 2008 4:26 p.m.
To: Midrange Systems Technical Discussion
Subject: Re: Connect to Lan Console during D-Mode IPL?

Thanks Pete -- the LPAR is correct at 1. The docs are (finally) very
specific that the numbering starts at 1 now, not 0.

I have ready SO many docs the past couple of weekends I think IBM owes me a
paycheck :)

On Sun, Oct 19, 2008 at 7:51 PM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx>wrote:

Evan,

All great points !!!

Just one to add, did he have the LPAR number correct. I Always get
it mixed up, if I should put a 0 or 1 in it for a standalone machine.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Sunday, October 19, 2008 10:37 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Connect to Lan Console during D-Mode IPL?

Hi Dave

The way I read the error codes you provided is:

02C00004 <- Word 13; the 4 at the end indicates BootP status;
00000036 <- Word 14; number of BootP attempts.

If attempts are zero, then BOOTP is ready when called. If attempts have a
value, the PC did not respond.

So, I think it looks like you simply have the addresses wrong, or the
iSeries can't reach the PC. Have you verified that the cable is good ?

If you have access to SST (well, that should make things easier) then
verifying the addresses should be a snap.

If you're not doing the 11 to check the status, you are seeing the second
21
operation change the edit mode indicator onto "C" when making changes,
right
?

I guess, you've reconfigured the LAN adapter on the PC as expected as well
?

Have you checked the serial number on paper or on the system to verify

what

you have entered ? The serial number on the front of the machines is much
smaller and is very difficult to distinguish fonts these days (that, or

the

computer rooms are getting darker...)

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Wright
Sent: Monday, 20 October 2008 1:17 p.m.
To: Midrange Systems Technical Discussion
Subject: Re: Connect to Lan Console during D-Mode IPL?

I am not actually doing 11 each time, but I have ASMI up and I verify the
codes there, and I told it to use the embedded controller (E1).

I also made sure that windows firewall was turned off. I did not have

luck

even when connecting directly from the laptop to the embedded ethernet.

Something I have not tried yet, but considered on the way home:
In SST I was thinking I could clear the lan console details from the dasd
before doing the swap. Maybe it all needs to be set back to default/zeros
before the BootP will work?

And one other question regarding BootP: Should I create the connection

and

have it 'Connecting' before the IPL? Or wait until it gets to the 'search
for console' SRCs?


On Sun, Oct 19, 2008 at 3:39 PM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx>wrote:

Just to make sure when we talk about 65+21 you are sure you are

"cycling"

through all the console options (going back to 11 each time) and seeing
what
you are telling the machine to come up with as a console?

You can also tell it which adapter you are using as well when you enter
this
(like if you are using the internal adapter).

You don't have a firewall on the PC that is blocking the BootP protocol

do

you?

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Wright
Sent: Sunday, October 19, 2008 4:44 PM
To: Midrange Systems Technical Discussion
Subject: Re: Connect to Lan Console during D-Mode IPL?

12 & 13 were indeed back...

Of course, nothing can be easy, so A6005008 only returns 9 words, and

all

the troubleshooting docs talk about words 13 & 14 & 15. Doh.

Hex Word Count : 9
Reference Code : A6005008
Hex Words 2 - 5 : 04D00061 02C00004 00000036 0323416E
Hex Words 6 - 9 : 50010A03 00000000 00000000 00000000
I think I am going to call it a day (again) and see if I can get this
figured out before trying again next weekend.



On Sun, Oct 19, 2008 at 12:48 PM, David Wright <opendave@xxxxxxxxx>

wrote:

As for 12 & 13, neither is available. Not quite sure why. I just

looked

at ASMI and it posted another A6005008, so I will go over and see if

there

is a 12 & 13 now.

archives
at http://archive.midrange.com/midrange-l.