On Tuesday, 04/07/2009 at 11:02 EDT, Ron Wells <rwe...@agfinance.com>
wrote:
> ◄
> tcp 0 0 192.168.253.217:2049 10.239.53.126:1043 ESTABLISHED -
> tcp 0 0 192.168.253.217:2049 10.239.53.126:1042 ESTABLISHED -
> 9:05:02 AM
> Not understanding why it uses 10.239.53 path
> below is mount from z/os
>
> MOUNT FILESYSTEM('192.168.253.217') TYPE(NFS) mountpoint('/NFS/USR1')
> parm
> ('192.168.253.217:"/opt",proto(UDP),vers(3),xlat(y)')
>
> below is the home and routes on the z/os tcpip
>
> HOME
> 10.239.53.126 VIPAL06
> 10.239.53.106 LINKF800
> 10.239.53.206 LINKFC00
> 192.168.253.19 HIPERLEE
> 192.168.35.124 VIPAL26
> 192.168.35.122 LINKF900
> 192.168.35.123 LINKFD00
> 10.239.53.116 IUTSAMEHL
I see that your HIPERLEE is covered by VIPAL06, and you probably have
SOURCEVIPA. So the packets are exiting via HiperSockets, but they have
the VIPA address. Try moving HIPERLEE above the VIPA.
Unless you've got host routes over in Linux, it's going to try to return
via the 10. route.
Alan Altmark
z/VM Development
IBM Endicott
