RE: I5 systems in production

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Neil

Where on iSeries do you do this? It is not handled in normal TCP/IP 
configuration, AFAIK. And it uses that special direct connect cable to J14 
or J13 or whatever, which is not Ethernet. If you've made this work, 
details, please.

Thanks
Vern

At 10:13 AM 11/25/2004, you wrote:
> You should be able to connect directly to the system with the defaul
> address using either a crossover cable, or a small hub/switch disconnected
> from the rest of your network, then change the settings on the iSeries to
> use a different set of IP addresses.
>
> ...Neil
>
>
>
>
> "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 2004/11/25 08:31
>
>
>
> To
> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: I5 systems in production
>
>
>
>
>
>
> > 2. IP subnetting conflict - Ops Console direct connect insists on
> > a certain
> > subnet - 192.168.0.1 - .255, I think. If this is also your company's
> > internal subnet, Ops Console will not work. Either use a laptop or other
> > machine not connected to your network, or change your network's entire
> > addressing scheme.  ;-)
>
> What?!  Our entire LAN is 192.168.0.x.  You're telling me that won't work?
>
> --
> Jeff Crosby
> jlcrosby@xxxxxxxxxxxxxxxx
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.