Re: The JS12 saga - Battle of the network scars... -- MIDRANGE-L

Subject: Re: The JS12 saga - Battle of the network scars...
From: "Lukas Beeler" <lukas.beeler@xxxxxxxxxxxxxxxx>
Date: Mon, 13 Oct 2008 22:42:55 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Mon, Oct 13, 2008 at 10:36 PM, Pete Helgren <Pete@xxxxxxxxxx> wrote:

With that physical connection issue taken care of, the IVM immediately

Nice!

So the final step is now to connect to the i. I just need to figure
that out and I should be good to go. What should I set the IP address
of the LAN Console to ? Any idea why the "Open terminal Window" in IVM
is trying to attach to 10.0.1.20?

Use an unassigned, new one then re-IPL the IBM i partition. OpsCon
acts as a BOOTP server, and the i partition will retrieve the IP you
entered into OpsCon using BOOTP.

The "Open in terminal Window" is for AIX partitions.

Follow-Ups:

Re: The JS12 saga - Battle of the network scars... , Pete Helgren

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.