Note, you will also need a route in the other Linux pointing back.
Otherwise you may create a situation where packets in one direction use
the hipersocket subnet, but in the other direction they use the external
LAN. This of course is dependent on the actual IP addresses used in a
given TCP connection. With this configuration, all communication between
the two Linux instances will use the hipersocket subnet, not just the
Samba communication.
Harold Grovesteen
Alan Altmark wrote:
On Friday, 12/09/2005 at 07:42 EST, Steve Gentry
<[EMAIL PROTECTED]> wrote:
Hello. I have two linux guest machines running on the same IFL I have a
hipersocket defined to both of them i.e., they are on the same subnet.
I
also have OSA ports defined to these same two machines. The OSA's are
on
a different subnet, and both Linux's (eth0) are on that same subnet.
One
of the linux machines is running Samba. I issue a mount command from
the
other linux machine. How do the linux machines determine which
interface
(eth0 or hsi0) to use? I would want both Linux's to use hsi0 because
hipersockets are supposed to be fast. Can I some how force the two
Linux's to use the hsi0 rather than eth0?
Thanks,
Steve G.
[IMAGE]
Ah. A picture. :-)
Linux doesn't care how fast the links are. He follows the information in
the routing table, in priority order:
1. An explicit "host" route. That is, a route could be placed in LNXRH03
that says "Route traffic for 10.140.1.45 through 192.168.140.65".
2. A subnet route. In your case, each host has two subnet routes. If
there are multiple eligible subnet routes, Linux takes the one with the
smallest subnet (largest mask).
3. A default route. I am guessing that each host has one default route.
The host route is workable in your case because you are using HiperSockets
and those don't get cabling errors or powered off. That is, if the
HiperSocket is not available, something larger is wrong. I say this
because a static route (entered manually, not by dynamic routing agent
like quagga) stays in place even if the remote host's network interface
goes down. If these were two OSA subnets, I would suggest VIPA and
quagga. VIPA has the further advantage of being able to be used in your
DNS and insulating clients from adapter or switch outages.
The amount of effort you expend is proportional to the importance of the
availability of the applications.
Alan Altmark
z/VM Development
IBM Endicott
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
