|
A *good* reason? Maybe not. Perhaps we're taking an overly simplistic
view, but this is a College network, so we don't like unsecured protocols
like FTP on the main network. It also seems cleaner to give AS/400 jobs
their own route to the file server such that they don't have to share a
path with anyone else. And both systems have extra Ethernet ports - so
why not use them??? [last statement in jest!]
I have a call into IBM support for callback during business hours. I'll
report back what they say to the list...
- Charlie
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of gogo400@xxxxxxxxx
Sent: Wednesday, May 06, 2009 11:59 PM
To: Midrange Systems Technical Discussion
Subject: Re: TCP/IP Question
Is there a good reason to have the adapters on different networks?
-JA
Hi, all! I have a question that seems simple but may not be:
A V5R4 iSeries has 2 LPARS, Production and Test, with a virtual Ethernet
between them.
Each partition also has its own connection to the main network.
The Production LPAR has an ADDITIONAL direct connection (crossover
cable)
from another NIC to a PC server (will be running FTP). That connection
is
up and working.
The main network is class B, 10.0.x.x
The Virtual is class C, 192.168.0.x
The crossover is class C, 10.100.100.x
I would like the test partition to be able to hit the PC server through
the virtual Ethernet, but I'm not sure how to get them to route (setting
a
route on the test side to the production virtual Ethernet address wasn't
enough).
Easy, hard or impossible?
I know I could replace the crossover cable with a switch and use three
physical connections, but it would be cool and use fewer parts to do it
through the virtual.
Thanks!
- Charlie
--
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.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.