On 26/04/2006, at 9:51 pm, Fuhrmann Anna wrote:
(in reply to me saying)
file called route-hsi0
to be created also in /etc/sysconfig/network-scripts ?
Yes, sorry, I distracted myself checking the answer and forgot to
give it! :)
I also forgot to mention that if you do nothing else other than add
the route to Linux, this will work bi-directionally (i.e. traffic
will be sent and received over the HiperSockets) *only* if the
connections are initiated by Linux, and if you are not using source
VIPA on Linux (which you have said you are not). If connections are
being initiated from z/OS, you will need to add a static route for
Linux's IP address to z/OS's routing table otherwise its outbound
traffic will go over the OSA.
This will ensure that any traffic directed to the VIPA of z/OS
goes via HiperSockets.
This is fine, I can do that in any case.
Is it also necessary if the applications (we plan to implement) use
the IP-address the HSI interface of z/os directly, and not the VIPA-
Address of z/OS? So that every conversation
from-Linux-to-z/os and back explicitly uses the HSI-Address?
You're right, if you do it that way you will avoid the need to code a
route to the z/OS VIPA on the hsi0 interface (or to Linux's IP in z/
OS TCPIP). That is indeed one way to connect directly via the
HiperSockets (and exactly what's working for Steve as suggested in
his note). Adding the static routes via HiperSockets gives you the
benefit of not having to make any application changes in order for
*all* the Linux-to-z/OS traffic to be sent over HiperSockets -- if
that is not what you want, and it's fair enough that you might only
want to send certain traffic over HiperSockets, then addressing to
the interface gives you control over what traffic will use HiperSockets.
IMO, it's probably the only situation where it's okay to use an
interface address instead of a VIPA -- if your HiperSockets isn't
available you're likely having bigger problems with your system than
whether two LPARs can talk to each other! :D
It does, however, create a temptation to use one of my "pet peeves":
hard-coded IP addresses. What happens if you need to change the IP
subnet allocated to your HiperSockets? Your applications may all
have to change. Make sure to define the interface IP addresses to
DNS to minimise the number of changes you might have to make in the
future[1]. Then give the apps people the name rather than the IP
address -- it's easier for you to change (or arrange to have changed)
one DNS entry than for several application people to make possibly
dozens of application changes...
Thanks so much ...
You're welcome! Hope we've been helpful.
Cheers,
Vic Cross
[1] Network folks often have several DNS entries for a single piece
of network kit, each different name referring to a different
interface (it's easy to come up with a usable naming convention too,
like the hostname zephyr would have zephyr-eth0, zephyr-hsi0, and so
on).
----------------------------------------------------------------------
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
