Topic
  • 4 replies
  • Latest Post - ‏2012-02-29T19:59:15Z by kmeka
SystemAdmin
SystemAdmin
253 Posts

Pinned topic TCPIP Problems Between RDZUT and Linux Red Hat server

‏2012-02-28T21:04:28Z |
Hello friends.

I have installed Unit test 8.0.1 in Red Hat 5.3. Actually I am using scenario 4 from Red book manual sg247722.
My Linux server has IP: 192.168.38.97
MY UT has IP: 192.168.38.98
In UT I passed correctly TSO HOMETES:
EZA0619I Running IBM MVS TCP/IP CS V1R11 TCP/IP Configuration Tester
EZA0621I The FTP configuration parameter file used will be "TCPIP.FTP.DATA".
EZA0602I TCP Host Name is: RDZUT
EZA0605I Using Name Server to Resolve RDZUT
EZA0611I The following IP addresses correspond to TCP Host Name: RDZUT
EZA0612I 192.168.38.98
EZA0614I The following IP addresses are the HOME IP addresses defined in PROFILE.TCPIP:
EZA0615I 10.1.1.2
EZA0615I 192.168.38.98
EZA0615I 127.0.0.1
EZA0618I All IP addresses for RDZUT are in the HOME list]
EZA0622I Hometest was successful - all Tests Passed]

, even I installed RDz daemons (RSED, JMON, LOCKD) using ports by default, and I passed OK every verification fekfiv* program.
I can connect from my windows RDz clients to this UT daemons. From this windows clients I can ping both machines ...97 and ...98

What is my problem? The Linux server cannot connect with UT and UT cannot connect with Linux I tried using:

ping 192.168.38.98 from linux to z, and I received: <<ping: sendmsg: Operation not permitted>>
of course th Linux server 192.168.98.97 make ping to DNSs and other machines in my net.

By the other hand, TSO PING 192.168.38.97 receives "Time out". Of course TSO PING to my DNSs or gateway is correct, even to other machines in my net.

I think my problem is in Linux, but where?, In Linux only defined my eth0 using my static IP: 192.168.38.97 submask: 255.255.255.0 Gateway: 192.168.38.1 DNSs 192.168.38.13 192.168.38.14, I have the same configuration in my TCPPARMS files.

Somebody can help me? Is it necesary define a tunnel or similar to connect both machines?

Thank you a lot.
Updated on 2012-02-29T19:59:15Z at 2012-02-29T19:59:15Z by kmeka
  • RDzJohn
    RDzJohn
    270 Posts

    Re: TCPIP Problems Between RDZUT and Linux Red Hat server

    ‏2012-02-28T21:24:46Z  
    z/OS and Linux cannot communicate on the same machine using OSA. They must use the private TAP interface, initially configured as the 10.1.1. network. Do a find_io command and make sure the chpids defined on your machine match your devmap and you should be good to go.

    RDzJohn
  • SystemAdmin
    SystemAdmin
    253 Posts

    Re: TCPIP Problems Between RDZUT and Linux Red Hat server

    ‏2012-02-29T08:12:05Z  
    • RDzJohn
    • ‏2012-02-28T21:24:46Z
    z/OS and Linux cannot communicate on the same machine using OSA. They must use the private TAP interface, initially configured as the 10.1.1. network. Do a find_io command and make sure the chpids defined on your machine match your devmap and you should be good to go.

    RDzJohn
    Hi,

    Firstly thank you for your answer.

    I checked the configuration about your note:

    ibmsys1@ladera30s ~$ find_io

    Interface Name tap0 -> MAC addr 2:a0:a0:a0:a0:a0 Flags = 0
    Interface Name tap1 -> MAC addr 2:a1:a1:a1:a1:a1 Flags = 0
    Interface Name tap2 -> MAC addr 2:a2:a2:a2:a2:a2 Flags = 0
    Interface Name tap3 -> MAC addr 2:a3:a3:a3:a3:a3 Flags = 0
    Interface Name eth0 -> MAC addr 18:a9:5:f9:4c:8e Flags = 0
    ====== Start of Chpid Registry Information =====

    Total Interfaces Found = 5
    Chpid Num Type State Slot Num Port Num Card Interface Name
    ========= ==== ===== ======== ======== ======== ==============
    a0 0 808 ff 0 Tun/Tap tap0
    a1 0 808 ff 0 Tun/Tap tap1
    a2 0 808 ff 0 Tun/Tap tap2
    a3 0 808 ff 0 Tun/Tap tap3
    f0 0 808 ff 1 Wired eth0
    ====== End of Chpid Registry Information =====

    ====== io_slot.dat file created with registry information==

    That is my ifconfig output. You can see tap0 = 10.1.1.1 and tap0 in forst table is "a0"
    ibmsys1@ladera30s sbin$ ./ifconfig
    eth0 Link encap:Ethernet HWaddr 18:A9:05:F9:4C:8E
    inet addr:192.168.38.97 Bcast:192.168.38.255 Mask:255.255.255.0
    inet6 addr: fe80::1aa9:5ff:fef9:4c8e/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:85233 errors:0 dropped:0 overruns:0 frame:0
    TX packets:512 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:9505653 (9.0 MiB) TX bytes:175641 (171.5 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:17641 errors:0 dropped:0 overruns:0 frame:0
    TX packets:17641 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:6600124 (6.2 MiB) TX bytes:6600124 (6.2 MiB)

    peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:110118 errors:0 dropped:0 overruns:0 frame:0
    TX packets:477 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:11000121 (10.4 MiB) TX bytes:173563 (169.4 KiB)
    Memory:f0500000-f0520000

    tap0 Link encap:Ethernet HWaddr A2:00:5E:8F:A6:AE
    inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
    inet6 addr: fe80::a000:5eff:fe8f:a6ae/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:8 errors:0 dropped:0 overruns:0 frame:0
    TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:480 (480.0 b) TX bytes:5305 (5.1 KiB)

    vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:512 errors:0 dropped:0 overruns:0 frame:0
    TX packets:85233 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:175641 (171.5 KiB) TX bytes:9505653 (9.0 MiB)

    virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
    inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:4427 (4.3 KiB)

    xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:84835 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:8282129 (7.8 MiB) TX bytes:0 (0.0 b)

    ibmsys1@ladera30s sbin$

    In my devmap I configured the first ose pointing to path=a0.

    manager
    name awsosa 0024 --path=a0 --pathtype=OSD --tunnel_intf=y
    device 400 osa osa
    device 401 osa osa
    device 402 osa osa

    manager
    name awsosa 22 --path=f0 --pathtype=OSD
    device 404 osa osa
    device 405 osa osa
    device 406 osa osa

    And when I do ping form linux to z:
    ping 10.1.1.2 I received:
    ping: sendmsg: Operation not permitted
    Do you have other idea?

    Thank you in advance.
  • SystemAdmin
    SystemAdmin
    253 Posts

    Re: TCPIP Problems Between RDZUT and Linux Red Hat server

    ‏2012-02-29T10:14:23Z  
    Sergio,
    As we talked, I looked at the information provided and I see lots of errors in your eth0.
    Review your Linux network configuration and try to fix this issue.
  • kmeka
    kmeka
    1 Post

    Re: TCPIP Problems Between RDZUT and Linux Red Hat server

    ‏2012-02-29T19:59:15Z  
    Hi,

    Firstly thank you for your answer.

    I checked the configuration about your note:

    ibmsys1@ladera30s ~$ find_io

    Interface Name tap0 -> MAC addr 2:a0:a0:a0:a0:a0 Flags = 0
    Interface Name tap1 -> MAC addr 2:a1:a1:a1:a1:a1 Flags = 0
    Interface Name tap2 -> MAC addr 2:a2:a2:a2:a2:a2 Flags = 0
    Interface Name tap3 -> MAC addr 2:a3:a3:a3:a3:a3 Flags = 0
    Interface Name eth0 -> MAC addr 18:a9:5:f9:4c:8e Flags = 0
    ====== Start of Chpid Registry Information =====

    Total Interfaces Found = 5
    Chpid Num Type State Slot Num Port Num Card Interface Name
    ========= ==== ===== ======== ======== ======== ==============
    a0 0 808 ff 0 Tun/Tap tap0
    a1 0 808 ff 0 Tun/Tap tap1
    a2 0 808 ff 0 Tun/Tap tap2
    a3 0 808 ff 0 Tun/Tap tap3
    f0 0 808 ff 1 Wired eth0
    ====== End of Chpid Registry Information =====

    ====== io_slot.dat file created with registry information==

    That is my ifconfig output. You can see tap0 = 10.1.1.1 and tap0 in forst table is "a0"
    ibmsys1@ladera30s sbin$ ./ifconfig
    eth0 Link encap:Ethernet HWaddr 18:A9:05:F9:4C:8E
    inet addr:192.168.38.97 Bcast:192.168.38.255 Mask:255.255.255.0
    inet6 addr: fe80::1aa9:5ff:fef9:4c8e/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:85233 errors:0 dropped:0 overruns:0 frame:0
    TX packets:512 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:9505653 (9.0 MiB) TX bytes:175641 (171.5 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:17641 errors:0 dropped:0 overruns:0 frame:0
    TX packets:17641 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:6600124 (6.2 MiB) TX bytes:6600124 (6.2 MiB)

    peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:110118 errors:0 dropped:0 overruns:0 frame:0
    TX packets:477 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:11000121 (10.4 MiB) TX bytes:173563 (169.4 KiB)
    Memory:f0500000-f0520000

    tap0 Link encap:Ethernet HWaddr A2:00:5E:8F:A6:AE
    inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
    inet6 addr: fe80::a000:5eff:fe8f:a6ae/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:8 errors:0 dropped:0 overruns:0 frame:0
    TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:480 (480.0 b) TX bytes:5305 (5.1 KiB)

    vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:512 errors:0 dropped:0 overruns:0 frame:0
    TX packets:85233 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:175641 (171.5 KiB) TX bytes:9505653 (9.0 MiB)

    virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
    inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:4427 (4.3 KiB)

    xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    RX packets:84835 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:8282129 (7.8 MiB) TX bytes:0 (0.0 b)

    ibmsys1@ladera30s sbin$

    In my devmap I configured the first ose pointing to path=a0.

    manager
    name awsosa 0024 --path=a0 --pathtype=OSD --tunnel_intf=y
    device 400 osa osa
    device 401 osa osa
    device 402 osa osa

    manager
    name awsosa 22 --path=f0 --pathtype=OSD
    device 404 osa osa
    device 405 osa osa
    device 406 osa osa

    And when I do ping form linux to z:
    ping 10.1.1.2 I received:
    ping: sendmsg: Operation not permitted
    Do you have other idea?

    Thank you in advance.
    You need to configure the tunnel interface using a different ip address. Basically one ip address to the external world and another for communicating to the Linux box.
    Try this:-
    in the device map
    name awsosa 24 --path=A0 --pathtype=OSD --tunnel_intf=y --tunnel_ip=192.168.10.1 --tunnel_mask=255.255.255.0

    In the Z/OS TCPIP profile

    DEVICE PORTB MPCIPA

    LINK ETH2 IPAQENET PORTB

    HOME 192.168.10.20 ETH2

    ROUTE 192.168.10.0 255.255.255.0 = ETH2 MTU 1492

    START PORTB

    You would need to code thse statements in the appropriate sections like Route statement should go between BeginRoutes and End routes