Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
  • 1.  RDZUt Network issue

    Posted Mon July 14, 2014 02:44 PM

    Hi Guys,

    I've been struggling almost a year, trying to put my RDZ on my local network, but I've been unlucky. I found some topics here related to similar problems, but due my lack of experience with Networking and RDZ, I wasn't sucessful trying to figure out and apply some changes suggested by some of your experienced users, then I decided to include my case and all related information as possible and hope for your comments and advices to get this thing working!... 

    Hostname: rdzserversp001

    Intel(R) Xeon(R) CPU    X5675  @ 3.07GHz with 24 cores.
    24GB Memory
    1 TB disc
    RDZ disks location: /z/v85
    Profile location: /z/v85/profile

    OS: Linux SuSE 11

    Network information:

    IP: 10.2.0.233 (ETH0 - Linux Mgnt Interface)
    Bcast: 10.2.7.255
    Gateway: 10.2.1.200
    RDZ IP: 10.2.0.234 (desired) ---> I've set this to ETH1 on TCPPARMS(PROFILE)

    Some additional information about ROUTE, HOMETEST, IFCONFIG, ETC.

     

     

    Some additional information:

     

    ifconfig 

     

    netstat

     

    /etc/hosts content

    CONTENT OF USER.TCPPARMS

    IPNODES

    PROFILE

    RESOLVER

    This is the output when I ping from another device in the same network

    When I try to connect to the RDZ IP 10.2.0.234

    TSO HOMETEST OUTPUT

    TSO NETSTAT OUTPUT

    Attached all files from USER.TCPPARMS.

    Guys, what could be wrong? I can't reach the 10.2.0.234.

    Krayher


  • 2.  Re: RDZUt Network issue

    Posted Tue July 15, 2014 12:49 PM

    Guys, solution was change the TCPPARMS(PROFILE).

    In 10.x network, you need to change the tunnel of ETH1 adapter (in my case it was TAP0), otherwise route will lost itself.

    Correct routes are:

     

    BEGINROUTES

       ROUTE 10.0.0.0    255.255.248.0  = TAP0      (WRONG if you have a 10.x network!)

    to

       ROUTE 10.1.1.0   255.255.255.0   = TAP0

    ENDROUTES

    Another solution can be changing the devmap to create a 192.168.1.1 for TAP0 instead of 10.1.1.1 

     

    Krayher