Automated Testing

  • 1.  Networking ZD&TLE in a VM

    Posted Tue July 05, 2022 11:11 AM
    My desktop Linux machine runs Pop!_OS 22.04, an Ubuntu variant. After trying to coerce it into a shape that would let the ZD&TLE license software run successfully, I gave up and installed a KVM virtual machine with vanilla Ubuntu Server 20.04. On that, I can pass through the USB token direct to the VM, and the ZD&T package comes up and IPLs z/OS 2.4 just fine. Unfortunately, I cannot get networking to the z/OS system to work.

    I'm trying to have all three systems - the host machine, the Ubuntu VM, and the z/OS system - appear no my network in the same subnet. The host machine is at 192.168.120.2, the VM is at 192.168.120.44, and the z/OS system is at 192.168.120.101. I have bridged networking set up in the VM and on the host as well. It almost works. z/OS brings up the network adapter and can talk to the DNS server at 192.168.120.1. Anything more than that from the rest of the network back to the z/OS host, though, blows up with a complaint the host is not reachable.

    The really weird thing is what happens when I ping the z/OS system from either the physical host or elsewhere on the network: 192.168.120.101 replies just fine, but 192.168.120.44 *also* replies:

    (2014) jmaynard@dot:~$ ping 192.168.120.101
    PING 192.168.120.101 (192.168.120.101) 56(84) bytes of data.
    64 bytes from 192.168.120.101: icmp_seq=1 ttl=64 time=0.943 ms
    64 bytes from 192.168.120.101: icmp_seq=2 ttl=64 time=1.10 ms
    64 bytes from 192.168.120.101: icmp_seq=3 ttl=64 time=1.73 ms
    64 bytes from 192.168.120.101: icmp_seq=4 ttl=64 time=1.51 ms
    From 192.168.120.44 icmp_seq=1 Destination Host Unreachable
    From 192.168.120.44 icmp_seq=2 Destination Host Unreachable
    64 bytes from 192.168.120.101: icmp_seq=5 ttl=64 time=0.892 ms
    64 bytes from 192.168.120.101: icmp_seq=6 ttl=64 time=0.786 ms
    64 bytes from 192.168.120.101: icmp_seq=7 ttl=64 time=2.02 ms
    From 192.168.120.44 icmp_seq=5 Destination Host Unreachable
    64 bytes from 192.168.120.101: icmp_seq=8 ttl=64 time=0.674 ms
    64 bytes from 192.168.120.101: icmp_seq=9 ttl=64 time=1.73 ms
    64 bytes from 192.168.120.101: icmp_seq=10 ttl=64 time=0.721 ms
    ^C
    --- 192.168.120.101 ping statistics ---
    10 packets transmitted, 10 received, +3 errors, 0% packet loss, time 9100ms
    rtt min/avg/max/mdev = 0.674/1.210/2.018/0.466 ms, pipe 4
    ​

    What do I need to do to get the VM to shut up and ignore traffic for z/OS, letting it flow through the bridge to the z/OS network adapter?

    ------------------------------
    Jay Maynard
    ------------------------------


  • 2.  RE: Networking ZD&TLE in a VM

    Posted Wed July 06, 2022 07:28 AM
    What does iptables -L  look like on 192.168.120.44,   if you ifconfig  on 192.168.120.44 when Z/OS is up and running,  what network adapters and address' do you see for them?

    ------------------------------
    Rod
    Penarth
    ------------------------------



  • 3.  RE: Networking ZD&TLE in a VM

    Posted Thu July 07, 2022 08:03 AM
    iptables -L is empty.

    With z/OS running, I see the virtual Ethernet adapter at 192.168.120.44, the loopback adapter looking normal, and tap0 claiming to be 172.26.1.1 with a completely different MAC address. I'm guessing that 172.,26.1.1 is just a filler value, since z/OS is actually responding at 192.168.120.101.

    ------------------------------
    Jay Maynard
    ------------------------------



  • 4.  RE: Networking ZD&TLE in a VM

    Posted Thu July 07, 2022 08:13 AM
    My understanding is that you need to route everything via that tap0 adapter

    ------------------------------
    Rod
    Penarth
    ------------------------------



  • 5.  RE: Networking ZD&TLE in a VM

    Posted Thu July 07, 2022 08:21 AM
    Everything is routed through the TAP adapter, since z/OS is responding to pings at the correct address. A tap adapter is like a tap in the wire: it sees everything and packets sent through it are sent out the wire.

    I think all I need to do is to get .44 to ignore packets sent to .101; the latter will see them anyway since they're forwarded to it at a lower level. But I don't know how to manage that.

    --
    Jay Maynard






  • 6.  RE: Networking ZD&TLE in a VM

    User Group Leader
    Posted yesterday

    Did you get this working?  I am trying to do the same thing.



    ------------------------------
    Simon Coote
    Z Technical Specialist
    IBM
    ------------------------------



  • 7.  RE: Networking ZD&TLE in a VM

    Posted yesterday

    I was never able to, and had to give up when my license expired and the program ended.



    ------------------------------
    Jay Maynard
    ------------------------------